Database Info

[DEV & CWM Recovery for Pantech Crossover]

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

Need some quick help

So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?

Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium

Any ideas?
Sent from my LG-LS970 using xda premium

Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.

No one can help?
Sent from my LG-LS970 using xda premium

Well that sucks...
Sent from my LG-LS970 using xda premium

Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.

I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.

[Q] Help! Searched for solution for hours.

My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!

CreativeSin said:
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
Click to expand...
Click to collapse
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app

Aceofzeroz said:
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to . Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.

CreativeSin said:
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to .
Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
Click to expand...
Click to collapse
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app

Aceofzeroz said:
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?

CreativeSin said:
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
Click to expand...
Click to collapse
Well now that you're back and rooted, if you're planning on doing any more flashing any time soon then I recommend you install boot menu manager. If you've previously installed safestrap or bootstrap, clear their data and uninstall them before installing bmm.
With that done, you've just made your phone a little safer from bricking because bmm allows multi rom booting, which are somewhat independent of the primary system. Refer to this thread for more info on how to make systems, etc.: http://forum.xda-developers.com/showthread.php?t=2115715
The first thing you'd want to do is make sure your apps/data is always backed up at all times with apps like titanium backup. Create 2 or more systems so that you can try the bmm compatible custom ROMs which are in the dev section if you want to try any of them. But please, read all instructions, warnings, requirements, etc. carefully before attempting any flashing in general.
The thread I posted in my earlier post above will have links to the specific custom ROMs. If you're doing any other kind of flashing, make sure to again, read instructions carefully and take your time with learning all of this.

Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.

kunal2711 said:
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
Click to expand...
Click to collapse
Use boot menu manager instead of bootstrap recovery
Sent from my MB865 using XDA Premium 4 mobile app

[Q] NAND Write Start Fail in Odin

Hi all,
for the last three days I've been carrying around a paper weight that looks remarkably like my Galaxy S3...
Anyway, I'm at a point where I don't know what else I could (or should) try. Today I thought I had a winner when I came across this thread: http://forum.xda-developers.com/showthread.php?t=1840030
I thought wrong. Flashing the bootchains works but then when I try flashing the root66.tar in Odin it always fails during NAND Write Start. I have seen people in the above thread with the same problem and then "never mind, I fixed it"-posts without explanations what they actually did... So, if you managed to fix it or know how to fix it, how does it work?
(I can't post in the same thread because I have less than 10 posts..)
Any input would be highly appreciated!
Thanks a lot and happy new year!
Cheers

In detail what did you do before this problem.

ThePagel said:
In detail what did you do before this problem.
Click to expand...
Click to collapse
Hm... a lot of (probably not very wise) things... Let's see...
It all started when I updated CM10.2 to a nightly release. Something went wrong, not sure what. I was talking to someone and when I checked my phone again it was just sitting there in TWPR and wouldn't boot up anymore (stuck in Cyanogen splash screen). I was still able to boot back into recovery and then tried flashing the stable CM10.2, which it didn't do. I factory reset the phone, tried flashing again, to no avail. The error message was that E: data something was missing or not accessible. From then on it's kind of a blur what I actually did, the list includes:
- trying to flash back to stock in Odin
- trying to flash new recovery in Odin
- trying to flash a pit file
- trying to install new firmware in Kies (after downloading the firmware Kies would just quit (PC), or not even download it and tell me that it's not posfible with my phone (Mac))
- trying the method described in the linked thread
At some point I wasn't even able anymore to boot into recovery (I think that was when I tried to flash a new recovery).
Thanks

I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe

joeinternet said:
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
Click to expand...
Click to collapse
Interesting. I am indeed running Windows in a VM... Need to try that later today. I'll report back later in the pm. Thanks!

IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!

Mungo Park said:
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Click to expand...
Click to collapse
Be careful using kies in the future. If they start pushing 4.3 you will be screwed.

Haven't thought about that. It was still 4.1.2 and I'm back on CM10.2.
Thanks!

[Q] Need help rooting, unlocking BL and flashing - new R HD owner!

Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers

niksy+ said:
Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers
Click to expand...
Click to collapse
have a look at this post.

bweN diorD said:
have a look at this post.
Click to expand...
Click to collapse
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :

niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
The official BL unlock is still available as far as I know, but its not available for all phones. You basically have to try it to know if it will work.
I think the official way is reversible, it has always been said motopocalypse is not. Those facts may be wrong though. There was discussion about it in one of the threads but I don't recall exactly what was stated. If you don't care about ever locking it back, it wouldn't be relevant then.
About cm, I still have my rmhd but haven't used it other than for testing since last year. So I can't provide any current help on that, sorry.
Sent from my LG-VS980 using XDA Premium 4 mobile app

niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
Just go to the Motorola web site and look for the unlocking program and attempt it there. Here is the link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You'll have to either sign in with your Google+ ID or register an account with Motorola. It's free and then you can attempt to unlock your phone.
The XT925's are always unlockable since they are not in the US. It's Verizon that won't allow it and the XT926s are US phones.

Okay, guys, I've ran into some problems :/
Current status: bootloader loads fine, CWM (6.0.4.4, touch version) loads fine, but the system wouldn't boot after making a backup. I've tried flashing CM11 (cm-11-20140710-NIGHTLY-moto_msm8960-epinter.zip which is supposedly with the 3.0 kernel) and it still will not boot. (I've wiped /system /data and /cache before flashing) All it does is sit at the "Warning bootloader unlocked" screen and it doesn't even become warm...
What I've done: basically, followed all the steps from the thread @bweN diorD posted. Rooted with MotoChopper, unlocked bl with MotoPocalypse and flashed CWM via adb. That was all fine. Then I noticed that CWM keeps disappearing, so I said yes when it asked me if I want it to remove that script from the stock ROM . It also asked "Fix root?" at the same time to which I said yes... Since then the system will not boot. Does anyone know what's gone wrong and what can I do to fix it? Is RSD the only way now?
@bweN diorD @iBolski and everybody else... pretty please :/
*EDIT* Got my stock firmware and flashed it via RSD-lite. Had to remove that check in the xml, but that was it, it has come back to life
Now what puzzles me... Why did the system die after saying yes to "remove the recovery remover script" and "fix root"? And why was CM11 dead on boot, too? Any ideas? :/
*EDIT #2* Nevermind, I'm on CM11 now Rooted again, the bl was still unlocked, installed latest PhilZ recovery and flashed CM11 straight up without even booting stock ROM after installing recovery. All is well! CM11 is so smooth on the R HD that I came a little bit. I loved my petite DEFY+ but this is freaking awesome!

glad you got it worked out

Drivers issue
Guys, I've now got a freaking drivers issue I cannot resolve... Need assistance
I am currently on CM11, on the jbbl. Last time I flashed an sbf was at the time of my previous post in this thread, so 5 months ago. Since then, I have changed my system drive (to an SSD, yay!) and lost the drivers set-up. Back then I was on Win7 x64, now I'm on Win8.1 x64.
At the moment, I cannot get ADB to work (it lists my device, but says it's offline) and cannot get RSD Lite (it's v6.1.6) to detect the phone when in fastboot. I'm attaching a screenshot of device manager's current status. The mot composite adb interface driver is fine, but the two in other devices remain question marks.
Motorola Device Manager (2.4.5) just looks for updates for my device and then quits after finding none. No matter if the phone is connected or not. Not sure if it's incompatible with win8.1 or just normal behaviour since my phone's not on the stock rom.
Does anyone know the right steps for setting up ADB and Fastboot drivers on win8.1 for our device? MTP works fine, no problems there.
*EDIT* Tried using [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer and ADB connects now, but RSD lite still doesn't detect the phone in fastboot. The device manager list looks the same... I hate driver issues >_< And just to be clear, RSD lite does not show anything while the phone is connect as MTP with debugging enabled, too.
*EDIT 2* All fine now. Just uninstalled everything and started from scratch. Drivers that come with Moto Manager are the only requirement.