Related
All,
Noob here as far as Android goes. I picked up a Galaxy S Captivate a few months ago from AT&T and I got a notification saying Froyo was available. Of course, Samsung made it near impossible to do, so I figured "I'm a computer programmer, I can do these kinds of things".
Using Odin, I put on a version of Froyo. It was... not a good ROM by far (I didn't know all the great ones were here) and after the 4th or 5th random crash, I decided to try something different. However, at one point the phone bricked. I was finally able to get Odin to push back 2.1 Eclair (the stock AT&T version), but since then, I get a "SIM Network Unlock Pin" prompt. I followed the instructions to grab the unlock code from the bml3.back file, but it doesn't work. I've tried upgrading to various Froyo's, but they don't work either. AT&T tried a new SIM card, but that didn't work.
At this point, my Android abilities are done. I have no idea how to fix my phone. AT&T can't help and of course, Samsung will charge me for a repair (I have no idea how much that is).
Can anyone think of a way to get rid of the SIM Network Unlock PIN thing? This is a legitimate phone on a legit plan. The Continuum 3.5 Froyo runs great, it just can't see my SIM Network card and a phone without that is...well, bunk
Thanks for the help, I wish I could retrace all my steps but I was an idiot and didnt write it all down.
R
I have never heard of anyone overcoming a lost PIN issue without completely reformatting the phone and reinstalling a ROM.
Try flashing a new 2.2 rom and using the froyo unlock method in the dev section (http://forum.xda-developers.com/showthread.php?t=831569).
Since you mentioned you're a programmer, I'm going to assume you're comfortable with adb. Make sure you back up /efs/ to your sd card, then again to your computer before you try it as rom flashes will typically not overwrite this partition. I suspect your nv_data.bin or some other part of your /efs partition is messed up, which is why flashing most roms won't fix it. I'm not sure if the one click stock odin will do anything, but it's also worth a shot if you haven't tried it yet.
There's also a backup of nv_data.bin in /efs, you can try copying that over your existing nv_data.bin and rebooting to see if it helps.
modest_mandroid said:
Try flashing a new 2.2 rom and using the froyo unlock method in the dev section (http://forum.xda-developers.com/showthread.php?t=831569).
Since you mentioned you're a programmer, I'm going to assume you're comfortable with adb. Make sure you back up /efs/ to your sd card, then again to your computer before you try it as rom flashes will typically not overwrite this partition. I suspect your nv_data.bin or some other part of your /efs partition is messed up, which is why flashing most roms won't fix it. I'm not sure if the one click stock odin will do anything, but it's also worth a shot if you haven't tried it yet.
There's also a backup of nv_data.bin in /efs, you can try copying that over your existing nv_data.bin and rebooting to see if it helps.
Click to expand...
Click to collapse
Thank you thank you thank you thank you. That was exactly it. I now have a phone again!
This place is great, but it's a bit overwhelming when you first join. Couldn't find that article on my own, but it was there!
Cool, glad to hear you got it running again.
Hello:
I'm having a frustrating experience attempting my first root of my G2X.
I've had a previous thread from yesterday, attempting to do things from the Mac side:
http://forum.xda-developers.com/showthread.php?t=1172487&highlight=velanche
As of now, I've decided to revert to Windows 7 on my Mac to try and rectify things. I'm able to use One-Click Recovery Flasher, following the instructions, to flash the phone. I then downloaded an earlier nightly version of CM7, installed it on my flash drive, and did the install via ClockworkMod.
I had no errors from CWM, from the wipe to the install. I then choose the reboot open, and it powers off my phone.
Upon attempting to turn on my phone, I would get the LG screen, followed by a quick flash, followed by another LG screen with some horizontal blue background behind it. I'm taking it that it means that it's stuck, because I've waited 10 minutes before having to do a battery pull.
I did at one time attempted to flash back to the stock T-Mobile, but when the LG screen came it, it would just remain there without any progress.
At this stage, I don't know where else to go. I'm not sure if there's something amiss, because my phone, as far as I know, as been erased. If there's a way to progress to CM7, I'm game. But one thing I really need to do is to get my phone back.
I didn't backup my phone's contents initially because I was going to recreate everything anyway. Now I'm in a not-so-good place, save having to get a phone exchange.
Any assistance would be appreciated; thanks so much.
V.
Download one of the "Stock Rooted Nandroid Backups" from the development section, stick it on your SD card and do a Nandroid restore from CWM. That should get your phone working again...
On the CM7 installation problem, I have no idea what that could be. I've been flashing ROMs on Android devices since the G1 first came out a few years ago and the only reasons I had bootloops were from me trying to flash without wiping or flashing an unstable build.
Sorry to digress for a second here, but you DO have the T-Mobile branded G2x and NOT the Optimus2x, right?
Working on It
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
Sent from my Nexus 5g using XDA Ultimate App
velanche said:
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
Click to expand...
Click to collapse
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
Sent from my LG-P999 using XDA Premium App
LordButtersI said:
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
I don't know if this might have anything to do with why I've had problems getting CM7 to work, but I've noticed that when I plug the phone either into Windows or OS X, I've somehow lost the internal drive. I know that it's there because I've found a whole bunch of files on it while in CWN, but I'm suspecting that there's some link between neither computer seeing the internal drive and the issue with getting the phone to boot.
Yes, I can mount the external drive, either from CWM's mount on both platforms or when I press both volumes on my phone and plug in to Windows 7 via USB.
Do you have any insight on this? I was watching a few of The Unlockr vids, and I noticed that even though the guy's phone was rooted and flashed, he still could boot into his phone until he was ready to put on the new ROM (CM7, in this case).
Thanks!
Click to expand...
Click to collapse
scooter247 said:
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
I tried on the OS X side to do this, having to download an RAR app. I found the LG file, and told the app to extract it to the backup directory on my phone. I tried the restore again in CWM, but still a mismatch.
I will try it in Windows 7 tomorrow, and will let you know the outcome.
I'm beat; spent the whole weekend on this phone modding biz. I suspect I'll be really good by the time I finally am able to get things working.
V.
Click to expand...
Click to collapse
Is this an old SD card? Perhaps some bad sectors on it? Without holding the phone in my hands I can't think of anything else. Other than double check your steps, re-copy the files and try, try again.
The SD card is not old; about 2 months old. I tried formatting the card via Windows 7, but did it in FAT32. I take it that it's supposed to be formatted differently? The card is 16GB, but when I looked into CWM it's limit is 4GB.
I tried the steps again, and still get the same md5 mismatch. Is my guess correct that the card is supposed to be formatted a certain way? Unfortunately, I can access the previous OS via my phone, nor will the internal memory appear when the phone is plugged into the computer. However, I am able to mount the SD card within the computer's OS.
I almost feel like walking away from it for a week, but that means I'll be stuck without phone access for awhile. Tips or suggestions are most welcome.
BTW, there's apparently alternate instructions to deal with the md5 mismatch error. Though in Windows the NDIVIA driver is loaded for the phone, I tried the adb shell command but my device isn't detected by the software.
Thanks again,
V.
A day or two ago I unlocked my ChaCha using the HTCDev.com instructions. I then used DooMLoRD_v4_ROOT-zergRush-busybox-su to root it. Everything was going fine until I apparently deleted one too many system apps and now my phone is in extremis.
The problem: As the phone boots up and reaches the HTC logo screen, just when the main interface should appear, an error pops up. It says:
Code:
Sorry!
The process com.htc.bg has stopped unexpectedly. Please try again.
[Force close]
When I close it, the HTC logo appears again as the main GUI is reinitialised, which leads to the same error popping up again, thus entering into an infinite loop.
I can just about manage to connect the phone to my PC as a disk drive, but it's not connected in such a way that RUU or unrooting applications can "find" it from within Windows, so if I'm to fix this it's gotta be from the SD card/Hboot.
Details:
* HTC ChaCha with the latest Android firmware.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
* Factory resets and recovery boots don't seem to have any effect.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Is there any hope of fixing this issue given my obvious lack of critical faculties?
Thank you for reading this.
You can always install clockworkmod recovery and from there a custom rom. Check the relevant thread, it is pinned.
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
Click to expand...
Click to collapse
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
Click to expand...
Click to collapse
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
Click to expand...
Click to collapse
You can't restore a system app if there is a conflict. Try and identify the conflict.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
Click to expand...
Click to collapse
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
* Factory resets and recovery boots don't seem to have any effect.
Click to expand...
Click to collapse
See above about freezing.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
Click to expand...
Click to collapse
Doesn't matter, you'll fix it, guarantee it.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
Click to expand...
Click to collapse
See what I said above.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Click to expand...
Click to collapse
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
For a safe to remove list, check the Themes and Apps section.
skezza said:
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Click to expand...
Click to collapse
Music to my ears!
skezza said:
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
Click to expand...
Click to collapse
In Titanium Backup I tried restoring the backups I made; the "Recovering Backup" notice would just hang indefinitely until I forced TB to close. This only happened with system apps. The backed up files are still on my PC hard drive from when I copied them from my SD card, but I'm not sure they're of any use at this stage.
skezza said:
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
Click to expand...
Click to collapse
Ahhh, this is probably my problem then. I ignored most of the fixes and workarounds listed as [S-OFF] because I didn't think they'd work for my device haha.
skezza said:
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
Click to expand...
Click to collapse
I'm disappointed in myself for being so haphazard in my deleting, I'm usually not that stupid but I think I was a little overexcited to have finally gotten rid of some of the bloatware that'd irritated me for so long haha. I was like "oh boy, I can save even more battery power and internal space if I just remove a little more!". Lesson learnt
skezza said:
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
...
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
Click to expand...
Click to collapse
As I said above I didn't realise I could make use of [S-OFF] materials so I didn't even attempt them for fear of making matters worse. I just now attempted to flash CWM and it hung on "parsing" which is what happened with previous flash attempts. If a flash attempt doesn't hang on "parsing" it parses for a second and then goes back to the main menu, apparently having no effect.
I'd be lying if I said I'm not overwhelmed by all of this; the tutorials I've read seem to assume a fair degree of prior knowledge that I definitely don't have haha. I hope I don't stretch anyone's patience here, but if you could explain it to me like a 6-year-old whose mother drank heavily during pregnancy I think it will help move things along!
Thank you for the thorough reply, much appreciated
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
dapaua said:
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
Click to expand...
Click to collapse
Unfortunately I can't do anything via my computer; my phone isn't "discovered" by the command line, unrooting tools or anything else. It does allow me to access the SD card as a hard drive but that's all it does. Obviously this wasn't the case before my problems started, because I used my PC to root and unlock the phone originally, but now the phone's boot process can't reach a point where it becomes receptive to the PC's commands. I don't know why it lets me access the SD card though.
Is there any way to do this without my PC being involved beyond transferring files to the SD card? If not, am I screwed? haha
Thanks mate!
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
The fastboot binary is here C:\Program Files (x86)\Android\android-sdk\tools , if you installed the android SDK, which I asume you did.
Good luck, I hope this works!
dapaua said:
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
Click to expand...
Click to collapse
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
dapaua said:
Good luck, I hope this works!
Click to expand...
Click to collapse
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
PaddyM said:
Dear CHRIST thank you for that - I didn't...
Click to expand...
Click to collapse
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
PaddyM said:
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
Click to expand...
Click to collapse
I'm happy it worked. Let's hope WiFi technology improves in the future
skezza said:
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
Click to expand...
Click to collapse
I knew about the recovery menu (the stock one, at least) but I didn't realise I could go into the Fastboot option and for the phone to then be recognisable to the PC, thus making it possible to flash via the command line. If I had known that I probably wouldn't have needed to post this thread at all haha.
skezza said:
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
Click to expand...
Click to collapse
Yeah... I think if it happened to one of you guys you probably would have had it sorted in about 6 minutes. 3 days isn't bad for my first attempt though! hahaha
skezza said:
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
Click to expand...
Click to collapse
Thanks for the advice man, I'll definitely be looking into the Nandroid backup option, although I hope I've learnt enough from this experience to have no need for it
Thanks to everyone who posted here, I appreciate the patience and the tolerance of my noobery.
Funnily enough, I tried TitaniumBackup today and the original poster is correct. While you can freeze, remove apps etc, you can't return them. especially system. I've not tried any of the alternative install methods that TB uses, but it's quite interesting.
TB is a bit quirky, I think. The system apps won't restore at all, but sometimes apps that I've downloaded myself will restore and other times they won't (the "Restoring App" notice just hangs there indefinitely). I usually find that forcing TB to close and then trying again does the trick, but I can't figure out why it happens in the first place.
Im wondering if anyone else has worked out a good configuration that will allow it to work every time?
Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it
And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA
Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?
crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.
Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?
Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.
Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse
Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk
Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk
Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2
anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware
Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.
formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Have you tried flashing different radios (baseband)?
http://forum.xda-developers.com/showthread.php?t=1785999
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Take a look at this thread, it may help. http://forum.xda-developers.com/showthread.php?p=25172599#post25172599
thanks for the replies...
I've flashed UCM1 and UCLL3 radios, they flash fine but no change...still can't flash to stock and no imei/baseband/service.
That fix thread was one of the first I found, but as I still have my keystr file in the efs folder, I didn't think it would apply to me...I suppose I could make an external backup of my efs, delete it and try one of those methods from scratch.
read through the restore to stock sticky http://forum.xda-developers.com/showthread.php?t=1652398 and go through the trouble shooting sections, if that doesn't help u could have bad hw
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
Just factory reset when it boot loops
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
causticfix said:
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
Click to expand...
Click to collapse
Yes I have two files in my imei folder i,e keystr and mps_code.dat!
I tired changing them from root explorer! pasted someones else's efs folder! but still I cant fix my imei is stays 0.
i donno how to get to diag mode with this rom, otherwise i could have tried my luck with QPTS.
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
lingowistico said:
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
Click to expand...
Click to collapse
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
causticfix said:
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
Click to expand...
Click to collapse
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
lingowistico said:
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
Click to expand...
Click to collapse
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Vgkiller said:
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Click to expand...
Click to collapse
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
lingowistico said:
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
Click to expand...
Click to collapse
This totally defeats the purpose of this forum then. Its sad.
Vgkiller said:
This totally defeats the purpose of this forum then. Its sad.
Click to expand...
Click to collapse
People want money for it because it's mostly used for making stolen phones work again.
That means real life risks like fines, jail etc.
Of course there are lots of examples when people experiment with this or that and delete their imei accidentally, or want to change the imei for some other reason. But these are more rare.
An update...
I managed to finally get flashed to stock...still null/null imei & baseband unknown. Efs folder is still there with files, keystr file is on...not sure what else I can do myself at this point so, I guess its time for the Polish dude or mobiletechvideos.
Hi People,
Did any1 found any solution?
talk2sharn said:
Hi People,
Did any1 found any solution?
Click to expand...
Click to collapse
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
causticfix said:
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
Click to expand...
Click to collapse
Ohkies.
Did you ask the polish guy about the reason why he was not able to fix your mobile. Coz, I'm just having similar problem like yours. I tried working with all the local samsung service centre guys, nothing worked. One guy said that my mobile IMEI is locked in some database, so it is not picking or detecting my SIM, hence locked. I know that my mobile is unlocked and is valid, I ignored his comments.
I assume you changed your MotherBoard of the mobile with the new cracked SR's, so that it could take new IMEI instilled in new board. Is it so?
Also, please suggest me about any alternatives on how to fix this problem.:crying: