Sooper-N00b broke his phone. please help. - Motorola Droid X2

Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.

Croda said:
Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.
Click to expand...
Click to collapse
ok, noob found thread about activation and fixed that part.
now I'm hoping I can just go back to 2.3.5 and apply my backup.

Lol, first take a deep breath. Your phone is not hosed, it's actually working like it's supposed too.
After you sbf, you phone is back to it's factory state right? So remember when you got your phone for the first time you had to have it activated/programmed. If you're on Verizon then dial *228 and follow the directions, takes about 5 minutes. This will give you back service and your phone number.
Second, the droid x2 is unique and requires a few different steps than most phones to flash things because it has whats called a locked, encrypted bootloader. So with the X2 you will NEVER want to use Rom Manager (Clockwork Mod Recovery) or Rom Toolbox. They just do not work with our phone yet.
Your going to want to read this link: http://www.droidxforums.com/forum/droid-x2-support/41785-common-x2-questions-answers.html
It gives a good overview of how the X2 works and explains a lot of things.
Then go here: http://forum.xda-developers.com/showthread.php?t=1318083
This explains how to install and get into the X2's special Bootstrap Recovery. This is where you will make backups, restore backups, and flash new roms. The thread explains in great detail how to make and restore backups in Bootstrap Recovery.

oh man, thanks a bunch lead off.
that whole deal with the boot strap is something that I never saw in all the reading I did and probably solves a lot of my problems. I'll do what you said (starting with the deep breath) and begin again.
thanks again for the help.

Yea no problem

Related

[Q] Factory reset not resetting everything?

I'm fairly new to the whole rooting business, and got my phone rooted the first day I had it and customized it how I wanted. Now I want to wipe it to try some new stuff. I've already backed everyone up with Titanium Backup and made a Nandroid recovery, but when I performed a factory reset/data wipe, I reset my phone and it still loaded my rom (the dasBAMF 3.0). Since I wiped but my Rom loaded (my assumption at least) something isn't working correctly and my keyboard won't pop up when I need to type in text for anything. Did I miss a step to completely wipe my phone...?
EDIT***
Really, I just want to try and get my phone either back to stock, or as close as I can (since I don't know what they check for when trying to exchange at the verizon store, if possible) so that my warranty is voided and stuff....
Yeah... You missed the who step of flashing another ROM. It's going revert back to the last ROM that was there if it isn't replaced.
Oh :/ Where would the vanilla TB rom be? Cause I might just be missing it, but I can't seem to find it in Android Development.
I would prefer to exchange it for another phone, so I'm trying to get it back to stock (or as close to it as I can if all they do is look at it without checking so I can exchange).
You're gonna want what's called an RUU. I'm not sure where the most recent OTA RUU is or who's been taking care of those. It should be in the dev forum. The version number should start with 1.70. To flash it, change the name to pg51img.zip and flash it like you would a radio. It will snap your phone right back to factory stock. If you can't find it, let me know and I'll try to hunt it down.
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
iImmortality said:
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
Click to expand...
Click to collapse
That last link, got to restore to stock for root and non-root users... That will work. Basically, after you flash the first one you'll be stock without root. The second flash will restore S-on.

Need Pro Help Here, HW Issues or SW issues with this Phone

OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks

Why Oh Why??

There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
MathiasKnight said:
There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Click to expand...
Click to collapse
Okay, looks like you created a new thread about the same issue...but moving on.
RSD Lite is a Motorola tool, that was initially just supposed to be used by retailers (like VZW and Radioshack) so that they could reset people's phones rather than having to ship the to Moto and send them back to the customer, or for VZW and others to wipe devices and resell them as "refurbished" units. The reason we can't use RSD to create ROM's is the SBF files are signed by Motorola. So if we were to modify them in anyway or try to make our own, it would refuse the files and not flash the device.
Now, from your other thread you posted this:
MathiasKnight said:
Sorry about that, I must have been excited. Unfortunately I spoke too soon. Either that or I'm not meant for this, which I hope is not the case seeing that I'm getting my degree in IT. I finally get bootloader, with ROM and GAPPS placed accordingly(I opted for Eclipse). When the zip is finished uploading and I see confirmation that all was installed correctly, I begin the reboot......and it takes new to an unactivated Droid X2. I've created nandroid after nandroid, with different methods and different ROMS, and I either land there or with a signature error, even in bootstrap. I'm gonna try one more time before I hang up my guns. Maybe.....
Click to expand...
Click to collapse
Could you please outline everything you do, step by step? After you SBF you should have to activate your phone anyway, so that after you root, install bootstrap and then boot into that and apply the ROM and GAPPs the phone should already be activated.
Travisdroidx2 said:
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
Click to expand...
Click to collapse
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
MathiasKnight said:
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
Click to expand...
Click to collapse
Okay, so you've SBF'd to 2.3.4. Rooted using whatever method, and you have the BootStrap recovery installed yes? Then you boot into recovery, wiped data, wiped cache and wiped dalvik cache, then tried installing a zipped ROM from you sd card, and upon restarting you get stuck at the moto M screen?
A couple things. First, when you wipe the dalvik cache (for roms or any mods) the phone has to rebuild that before it can actually boot into Android. This can take anywhere from a few minutes to 5 minutes or upwards. If you've gone 10 minutes and still nothing, all you need to do is pull the battery (so the phone powers off), reinstall the battery, DONT TURN THE PHONE ON, and then plug your phone into your wallcharger. After you plug in your phone, it'll turn itself on, go to the M screen and then go back into the BootStrapRecovery. From there you can redo the steps, wipe everything and then reinstall. However, IF you boot into the stock Android Recovery and wipe cache and data from there, you mucked it up and you'll have to SBF and restart the process.
ALSO, from your previous thread you said you were trying to install Eclipse. What version are you trying? 1.xx eclipse will work on 2.3.4, but Eclipse 2.xx will only work on 2.3.5, which could be another reason you are having issues.

[Q] Was stuck at boot, rooted s Razr. Have recovered. Need original ICS rom/HELP

Here's the story.
Rooted Stock RAZR.
Changed Build Prop to Galaxy Nexus and google.
Overwrote system files with the huge GAPPS 4.2 pack, excepting the apps folder. (My biggest mistake)
Backed up my launcher, transferred 4.2 launcher to system/app.
Overwrote some app files, not all.
Downloaded a Safestrap, -I do not believe I properly set this up.
Downloaded Clockworkmod, told it I had setup a recovery, then created a backup of rom.
The phone rebooted. I assumed that meant the backup was successful.
Nothing happened. Like the genius I am, factory reset phone.
Phone successfully loaded, but I got stuck at the welcome screen.
Put myself into bootloader, hit recovery, I think I wiped the cache and then did another factory data reset.
Somehow got back to the main screen. Phone was working properly.
Went and installed some more apps, including velvet chrome gmail gms and others.
Downloaded boot something or other app (cant remember name) redownloaded clockworkmod and safestrap. (Still not set up properly, obviously.)
Rebooted.
Got stuck in boot for hours. Could not get recovery up
Finally got into recovery.
Phone still sitting here, I do not dare touch it.
Yes, I made every possible wrong choice I could have. I did not have any clue what I was doing and tampered with a phone I don't have the money to replace.
The question is, can you help me xda forums. My phone can safely boot I hope as it is now in recovery.
I need to get this safe again. I do have an original copy of.my old.build prop, but not one of the original system files/some apps.
I would also really like to turn my RAZR into a Nexus
Maybe just the homescreen.
Going to my buddies house tonight. He has a computer I can use.
IDKHow2ShaveWithaRAZR:/ said:
Here's the story.
Rooted Stock RAZR.
Changed Build Prop to Galaxy Nexus and google.
Overwrote system files with the huge GAPPS 4.2 pack, excepting the apps folder. (My biggest mistake)
Backed up my launcher, transferred 4.2 launcher to system/app.
Overwrote some app files, not all.
Downloaded a Safestrap, -I do not believe I properly set this up.
Downloaded Clockworkmod, told it I had setup a recovery, then created a backup of rom.
The phone rebooted. I assumed that meant the backup was successful.
Nothing happened. Like the genius I am, factory reset phone.
Phone successfully loaded, but I got stuck at the welcome screen.
Put myself into bootloader, hit recovery, I think I wiped the cache and then did another factory data reset.
Somehow got back to the main screen. Phone was working properly.
Went and installed some more apps, including velvet chrome gmail gms and others.
Downloaded boot something or other app (cant remember name) redownloaded clockworkmod and safestrap. (Still not set up properly, obviously.)
Rebooted.
Got stuck in boot for hours. Could not get recovery up
Finally got into recovery.
Phone still sitting here, I do not dare touch it.
Yes, I made every possible wrong choice I could have. I did not have any clue what I was doing and tampered with a phone I don't have the money to replace.
The question is, can you help me xda forums. My phone can safely boot I hope as it is now in recovery.
I need to get this safe again. I do have an original copy of.my old.build prop, but not one of the original system files/some apps.
I would also really like to turn my RAZR into a Nexus
Maybe just the homescreen.
Going to my buddies house tonight. He has a computer I can use.
Click to expand...
Click to collapse
To restore your phone you need to SBF (Check out this guide if you are unfamiliar with how to use SBF forum.xda-developers.com/showthread.php?p=23453478) back to stock using the SBF 4.04 ICS build 6.7.2-180 which can be found here from http://www.droid-life.com/2012/07/1...azr-ice-cream-sandwich-4-0-4-build-6-7-2-180/. Next take a look at this guide forum.xda-developers.com/showthread.php?t=1840296 particulary the sections on root and recovery. These sections will explain how to root (http://forum.xda-developers.com/showthread.php?t=1710871) the ICS build you installed and how to use recovery (http://forum.xda-developers.com/showthread.php?t=1720351) and the latest version of ICS safestrap (http://forum.xda-developers.com/showthread.php?t=1391900) for the Droid Razr.
Unfortunately you can't turn your Droid Razr into a Nexus. However if you want to make the homescreen look like a Nexus I would recommend installing Apex Launcher (http://www.google.com/url?sa=t&sour...-IHIDw&usg=AFQjCNEjKp_sMjweNbIvuXE_fTXHQj4-Gg) along with the AOSP Jelly Bean icon theme for Apex launcher either this one http://www.google.com/url?sa=t&sour...24CgDA&usg=AFQjCNEt0DOlpK-8ubEx4QCLgcD4g8cj4w or this one http://www.google.com/url?sa=t&sour...24CgDA&usg=AFQjCNHrWglN-UU1hQBxmGgFbEzN76pDhw.
Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
shimp208 said:
To restore your phone you need to SBF (Check out this guide if you are unfamiliar with how to use SBF forum.xda-developers.com/showthread.php?p=23453478) back to stock using the SBF 4.04 ICS build 6.7.2-180 which can be found here from http://www.droid-life.com/2012/07/1...azr-ice-cream-sandwich-4-0-4-build-6-7-2-180/. Next take a look at this guide forum.xda-developers.com/showthread.php?t=1840296 particulary the sections on root and recovery. These sections will explain how to root (http://forum.xda-developers.com/showthread.php?t=1710871) the ICS build you installed and how to use recovery (http://forum.xda-developers.com/showthread.php?t=1720351) and the latest version of ICS safestrap (http://forum.xda-developers.com/showthread.php?t=1391900) for the Droid Razr.
Unfortunately you can't turn your Droid Razr into a Nexus. However if you want to make the homescreen look like a Nexus I would recommend installing Apex Launcher (http://www.google.com/url?sa=t&sour...-IHIDw&usg=AFQjCNEjKp_sMjweNbIvuXE_fTXHQj4-Gg) along with the AOSP Jelly Bean icon theme for Apex launcher either this one http://www.google.com/url?sa=t&sour...24CgDA&usg=AFQjCNEt0DOlpK-8ubEx4QCLgcD4g8cj4w or this one http://www.google.com/url?sa=t&sour...24CgDA&usg=AFQjCNHrWglN-UU1hQBxmGgFbEzN76pDhw.
Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
My only question is if I can accomplish all of this with my phone and a ******* MAC.
Thank you so much. I literally have asked around the web for hours with little to no help of any kind, and have been unable to come across resources on my own. I had completely forgotten about SBFing. That will be my savior. Not only that, but you have provided the links I have so. Needed. I am going to boot up my phone now, leave it on the charger, and go to sleep now...I hope it's there when I wake up.
also, someone recommended I flash Cyanogenmod. I found these two resources on my own:
http://www.droidforums.net/forum/htc-rezound-roms/224442-rom-cyanogen-mod-9-cdma.html
http://forum.xda-developers.com/showthread.php?t=1751826
and this is where I messed everything up from:
http://forum.xda-developers.com/showthread.php?t=1966302
I'm wondering, are my system files still ok after overwriting? Could the problem only be based on the changes to the build prop or something similar, so that I don't have to destroy my phone further?
shimp208 said:
To restore your phone you need to SBF (Check out this guide if you are unfamiliar with how to use SBF forum.xda-developers.com/showthread.php?p=23453478) back to stock using the SBF 4.04 ICS build 6.7.2-180 which can be found here from http://www.droid-life.com/2012/07/1...azr-ice-cream-sandwich-4-0-4-build-6-7-2-180/. Next take a look at this guide forum.xda-developers.com/showthread.php?t=1840296 particulary the sections on root and recovery. These sections will explain how to root (http://forum.xda-developers.com/showthread.php?t=1710871) the ICS build you installed and how to use recovery (http://forum.xda-developers.com/showthread.php?t=1720351) and the latest version of ICS safestrap (http://forum.xda-developers.com/showthread.php?t=1391900) for the Droid Razr.
Unfortunately you can't turn your Droid Razr into a Nexus. However if you want to make the homescreen look like a Nexus I would recommend installing Apex Launcher (http://www.google.com/url?sa=t&sour...-IHIDw&usg=AFQjCNEjKp_sMjweNbIvuXE_fTXHQj4-Gg) along with the AOSP Jelly Bean icon theme for Apex launcher either this one http://www.google.com/url?sa=t&sour...24CgDA&usg=AFQjCNEt0DOlpK-8ubEx4QCLgcD4g8cj4w or this one http://www.google.com/url?sa=t&sour...24CgDA&usg=AFQjCNHrWglN-UU1hQBxmGgFbEzN76pDhw.
Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
About to read through the articles. My battery is dead. I've looked through advice including hotwiring the charger to the battery but...Razr batterys can't be removed without voiding warranty.
IDKHow2ShaveWithaRAZR:/ said:
My only question is if I can accomplish all of this with my phone and a ******* MAC.
Thank you so much. I literally have asked around the web for hours with little to no help of any kind, and have been unable to come across resources on my own. I had completely forgotten about SBFing. That will be my savior. Not only that, but you have provided the links I have so. Needed. I am going to boot up my phone now, leave it on the charger, and go to sleep now...I hope it's there when I wake up.
also, someone recommended I flash Cyanogenmod. I found these two resources on my own:
http://www.droidforums.net/forum/htc-rezound-roms/224442-rom-cyanogen-mod-9-cdma.html
http://forum.xda-developers.com/showthread.php?t=1751826
and this is where I messed everything up from:
http://forum.xda-developers.com/showthread.php?t=1966302
I'm wondering, are my system files still ok after overwriting? Could the problem only be based on the changes to the build prop or something similar, so that I don't have to destroy my phone further?
Click to expand...
Click to collapse
It is possible that the build.prop edits you made caused your problems, but I would still recommend SBF'ing back to stock so you have a clean slate to start with. Also don't install anything else that could make things worse, until you are back to stock like I suggested. While you can use a MAC to flash SBF's its a lot easier and more reliable to use a computer running Windows.
IDKHow2ShaveWithaRAZR:/ said:
About to read through the articles. My battery is dead. I've looked through advice including hotwiring the charger to the battery but...Razr batterys can't be removed without voiding warranty.
Click to expand...
Click to collapse
Did you try plugging your phone into your charger and leaving it plugged in for a little while to let it charge? Also try plugging the phone into your computer and having it charge off of one of the USB ports.
shimp208 said:
It is possible that the build.prop edits you made caused your problems, but I would still recommend SBF'ing back to stock so you have a clean slate to start with. Also don't install anything else that could make things worse, until you are back to stock like I suggested. While you can use a MAC to flash SBF's its a lot easier and more reliable to use a computer running Windows.
Did you try plugging your phone into your charger and leaving it plugged in for a little while to let it charge? Also try plugging the phone into your computer and having it charge off of one of the USB ports.
Click to expand...
Click to collapse
Ok. Thank you. You have no idea how much less stressed I am about this. I have been trying to let it charge. I don't have a standard charger, I use a broken lapdock, which does charges the same exact way. Will charging with a computer give me different results? (This is not a priority question, I don't NEED you to answer it asap or anything.) Please stick around if I encounter more issues. It's nice to receive help rather than being flamed for being a noob. I had to get started somewhere. With yours and others help, I have gained many resources for flashing/rooting. I am still going to avoid trying to SBF if I can(Though I believe it is the avenue I'm taking, the only way I wouldn't is if I can safely recover and fixing build prop fixes my issues), as I REALLY don't want to lose root, as I had someone else root for me in the first place. I really need a god damn pc. Thanks again.
IDKHow2ShaveWithaRAZR:/ said:
Ok. Thank you. You have no idea how much less stressed I am about this. I have been trying to let it charge. I don't have a standard charger, I use a broken lapdock, which does charges the same exact way. Will charging with a computer give me different results? (This is not a priority question, I don't NEED you to answer it asap or anything.) Please stick around if I encounter more issues. It's nice to receive help rather than being flamed for being a noob. I had to get started somewhere. With yours and others help, I have gained many resources for flashing/rooting. I am still going to avoid trying to SBF if I can(Though I believe it is the avenue I'm taking, the only way I wouldn't is if I can safely recover and fixing build prop fixes my issues), as I REALLY don't want to lose root, as I had someone else root for me in the first place. I really need a god damn pc. Thanks again.
Click to expand...
Click to collapse
If your lapdock is broken then it may not allow your phone to charge correctly, I would recommend trying to charge it through your computer's USB ports as it will probably make a difference. And don't worry about asking questions heck we all start out knowing nothing and needing to ask questions, and what's good is your exploring and asking good questions not just demanding people do things for you. I understand SBF'ing back to stock may seem scary but as long as you follow the directions properly you'll be fine. Also by going to back to stock it will give you a clean build.prop free of any changes you made. For future reference always make a nandroid before making any build.prop changes no matter how small it may seem. As always I'm happy to help out and will be around for any questions you may have .
shimp208 said:
If your lapdock is broken then it may not allow your phone to charge correctly, I would recommend trying to charge it through your computer's USB ports as it will probably make a difference. And don't worry about asking questions heck we all start out knowing nothing and needing to ask questions, and what's good is your exploring and asking good questions not just demanding people do things for you. I understand SBF'ing back to stock may seem scary but as long as you follow the directions properly you'll be fine. Also by going to back to stock it will give you a clean build.prop free of any changes you made. For future reference always make a nandroid before making any build.prop changes no matter how small it may seem. As always I'm happy to help out and will be around for any questions you may have .
Click to expand...
Click to collapse
This is what I've been trying to do. I can't seem to get it to work. ► 1:50
www.youtube.com/watch?v=qs2t-7ALT7U
IDKHow2ShaveWithaRAZR:/ said:
This is what I've been trying to do. I can't seem to get it to work. ► 1:50
www.youtube.com/watch?v=qs2t-7ALT7U
Click to expand...
Click to collapse
Try the procedure again, other then that you could also try this guide by ifixit Installing Motorola Droid RAZR Battery.

[Q] CyanogenMod 10 A3 didn't install correctly... need some help

Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Dasoccerguy said:
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Click to expand...
Click to collapse
Did you get it working then? Were you running A2 before hand?
Dasoccerguy said:
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
Click to expand...
Click to collapse
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Simpsons11 said:
Did you get it working then? Were you running A2 before hand?
Click to expand...
Click to collapse
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
Lorenzo VonMatterhorn said:
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Click to expand...
Click to collapse
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Dasoccerguy said:
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Click to expand...
Click to collapse
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
http://www.youtube.com/watch?v=HJdvyufvYp0
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Lorenzo VonMatterhorn said:
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
youtubelink
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Click to expand...
Click to collapse
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Dasoccerguy said:
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Click to expand...
Click to collapse
a nandroid backs up the OS as well as all apps and data, but that only helps you if you are modding/messing with that specific rom. so yes, TB is the way to go for restoring apps across roms. glad to point you in the right direction! report back once youve made the jump. :fingers-crossed:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Dasoccerguy said:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Click to expand...
Click to collapse
thats awesome. i loved the feeling when i first flashed a new rom on this phone. glad you got it figured out. make sure to thank Tomsgt for his videos as well . hes a cool dude and put a lot of time into it.
as for battery life, its kinda a bit rough on cm10. i wouldnt say twice as good. that would be too good to be true...lol . but if you limit your apps, it shouldnt be that much worse.
one thing, to improve performance, under settings, go to developer options, and near the bottom there is background processes. its set at standard limit by default. change it to three at most. this will make a noticeable improvement in performance, but will also need to be re-set at 3 at most if you ever reboot/power off.
glad i could help! :highfive:

Categories

Resources