Hi there!
I have a droid x2 and tried and failed many times to install cyanogenmod 10 alpha 3 because of a status 7 error. I removed asserts and proceeded to install but i have been starring dumbly at a probably bricked phone. It has been saying "Installing Update" for about half an hour in CWD. I can't afford to brick this thing. I verified the os version. No one else seems to have this error. Please Help!!!
explosivejarvis said:
Hi there!
I have a droid x2 and tried and failed many times to install cyanogenmod 10 alpha 3 because of a status 7 error. I removed asserts and proceeded to install but i have been starring dumbly at a probably bricked phone. It has been saying "Installing Update" for about half an hour in CWD. I can't afford to brick this thing. I verified the os version. No one else seems to have this error. Please Help!!!
Click to expand...
Click to collapse
I failed a restore of a cm10 A3 nandroid over a 2.4.4 stock and the same cm10 nandroid over a fresh cm10 A3 install abd got it stuck on the motorola logo twice this morning.. restored it both times with sbf without a hitch.
Dunno what status 7 error is.. but I think it's safe to breath
explosivejarvis said:
Hi there!
I have a droid x2 and tried and failed many times to install cyanogenmod 10 alpha 3 because of a status 7 error. I removed asserts and proceeded to install but i have been starring dumbly at a probably bricked phone. It has been saying "Installing Update" for about half an hour in CWD. I can't afford to brick this thing. I verified the os version. No one else seems to have this error. Please Help!!!
Click to expand...
Click to collapse
Guessing you didn't remove the lines correctly.
If you have a dx2 you don't need to remove lines.
Sent from my Amazon OtterX using Tapatalk
sd_shadow said:
Guessing you didn't remove the lines correctly.
If you have a dx2 you don't need to remove lines.
Sent from my Amazon OtterX using Tapatalk
Click to expand...
Click to collapse
Thanks! I fixed it by "sbf"ing back to 2.3.4 even thought cm10 is "supposed" be compatable. Now the thing is really bricked. I tripped on the cable during the sbf procces and screwed it, so R.I.P Driod X2. :crying:
explosivejarvis said:
Thanks! I fixed it by "sbf"ing back to 2.3.4 even thought cm10 is "supposed" be compatable
Click to expand...
Click to collapse
what does that mean?
. Now the thing is really bricked. I tripped on the cable during the sbf procces and screwed it, so R.I.P Driod X2. :crying:
Click to expand...
Click to collapse
does it do anything? any sign of power?
sd_shadow said:
what does that mean?
does it do anything? any sign of power?
Click to expand...
Click to collapse
No sign of power what so ever even with a battery that was fully charged or on the charger. It won't even show the moto logo.
Related
So I am pretty new to these forums, as well as the whole android hacking community. I recently got a droid x 2 and thought I would take a shot at the whole rooting thing. I used the Motorola 1 click Root process and was able to root with no problems. I then downloaded the droidx2 recovery bootstrap and created a backup. After creating the backup, I attempted to flash eclipse (v 0.5). After it installed, I rebooted from the bootstrap and now I am stuck in a bootloop. The startup animation has changed to the droid bionic(one of the features of eclipse) so I am assuming the ROM installed somewhat correctly. Just wondering if anyone can help me here.
Thanks
-Noob D:
Did you wipe data / cache? If not, do so.
Sent from my DROID X2 using XDA App
morlakai said:
So I am pretty new to these forums, as well as the whole android hacking community. I recently got a droid x 2 and thought I would take a shot at the whole rooting thing. I used the Motorola 1 click Root process and was able to root with no problems. I then downloaded the droidx2 recovery bootstrap and created a backup. After creating the backup, I attempted to flash eclipse (v 0.5). After it installed, I rebooted from the bootstrap and now I am stuck in a bootloop. The startup animation has changed to the droid bionic(one of the features of eclipse) so I am assuming the ROM installed somewhat correctly. Just wondering if anyone can help me here.
Thanks
-Noob D:
Click to expand...
Click to collapse
does it actually bootloop, aka do a restart after a while? or does it just sit at the bionic boot screen for a really long time?
cash_back said:
Did you wipe data / cache? If not, do so.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Haha that's exactly what my friend told me to do. Working now, finally got my first ROM to start working...took me 3 days
Thanks for the help though!
morlakai said:
Haha that's exactly what my friend told me to do. Working now, finally got my first ROM to start working...took me 3 days
Thanks for the help though!
Click to expand...
Click to collapse
Whenever flashing a ROM, even an updated version, usually do a wipe/data reset by default. If you get a bootloop after that, then that's something to worry about possibly.
I had the same problem when i flashed version .04. I pulled the battery after it bootlooped, and went into stock recovery and did factory/reset and it fixed it.
I get the message failed to boot 0x1000 Entering NVFLASH RECOVERY MODE.
I had installed Cyanogen Mod 2.3.4 and didn't like it at all and tried to flash the sbf to 2.3.3 . Now that I am reading it seems like a dumb move.
This message comes up when I turn it on and disappears quickly to remain at a black screen.
Is there anything I can do?
ghostdog662 said:
I get the message failed to boot 0x1000 Entering NVFLASH RECOVERY MODE.
I had installed Cyanogen Mod 2.3.4 and didn't like it at all and tried to flash the sbf to 2.3.3 . Now that I am reading it seems like a dumb move.
This message comes up when I turn it on and disappears quickly to remain at a black screen.
Is there anything I can do?
Click to expand...
Click to collapse
Yes, it was a dumb move. You should have read all the warnings that said NOT to sbf flash after bootloader unlock.
Anyway, now you need to SBF flash 2.3.4 with pudding and you should be good to go.
How can I flash sbf 2.3.4 if RSD Lite doesn't show anything? Or should I be using a different program like fastboot?
Do I just redownload the 2.3.4 cyanogen and install with the program you suggest? I am unsure how this will work because the computer doesn't beep or anything like that when I connect it.
Thanks for your help.
We don't have the program to nvflash our devices. You can try to get motorola to replace it but but otherwise i believe you're screwed
Sent from my MB860 using xda premium
So which is it ?
ghostdog662 said:
So which is it ?
Click to expand...
Click to collapse
the only two sbf's that are safe to flash for people who installed the OTA update to gingerbread is the 2.3.4 sbf and the pudding sbf.
any others have the possibility of hard bricking your device, and nvidia hasn't released the nvflash program; therefor we're stuck at this step. no way to recovery from it.
What about these people I read about hacking up a usb cable ?
ghostdog662 said:
What about these people I read about hacking up a usb cable ?
Click to expand...
Click to collapse
That is to rsd flash without a battery, in case you flash when your battery is too low and the phone dies mid flash
Sent from my MB860 using xda premium
I have another battery that I can use and a friend has an Atrix I can stick the battery in to charge up. Does that improve the chances?
ghostdog662 said:
I have another battery that I can use and a friend has an Atrix I can stick the battery in to charge up. Does that improve the chances?
Click to expand...
Click to collapse
We don't have the program to NVflash an atrix. If you can get into rsdlite mode to flash an sbf you can fix it, but if
nvflash is your only option then you are hard bricked
Sent from my MB860 using xda premium
So what are people doing these days withe effed Atrix's?
ghostdog662 said:
So what are people doing these days withe effed Atrix's?
Click to expand...
Click to collapse
Using then for spare parts I'd guess
Sent from my MB860 using xda premium
I guess I'll try my luck with Motorola.
I sent my phone in for repair and they sent me a new one. Took the full 7 working days after they received it but I am happy. No more rooting / messing with this until nvflash is working.
ghostdog662 said:
I sent my phone in for repair and they sent me a new one. Took the full 7 working days after they received it but I am happy. No more rooting / messing with this until nvflash is working.
Click to expand...
Click to collapse
Nvflash may never be released...
Rooting should never give you any problems. Unlocking the bootloader and putting on a custom rom just requires some reading and more reading beforehand but isn't too hard if you follow the instructions.
Regarding dragonzkiller's thread http://forum.xda-developers.com/showthread.php?t=1912280 on [ROM][ALPHA][JB]CyanogenMod 10 Alpha 3 for the Droid X2. I've rooted two devices, the OG Droid and my X2 so I'm not unfamiliar with the process but some of the items I need to get CM 10 on my X2 I'm not sure where to find. In the article it's said I need the following:
-Install the BSR (patched if on an AOSP based ROM, unpatched if on BLUR)
-Reboot into the BSR
-NANDROID
Where can I find BSR and NANDROID? I have Rom Manager and Titanium Backup Pro on my X2 currently. Rom Manager never reboots into recovery for me for some reason and TB Pro does but I don't see an option to select NANDROID.
Any help would be really appreciated! I'm tried of running 2.3.5 all this time.
Dont use ROM manager for that kind of stuff. Best not to use it at all with the Droid X2 actually. The BSR IS the recovery for the X2. It can be found in the CM7 thread. And a nandroid is just a backup of your ROM that you make yourself within the recovery. Its not a file provided. Its a good idea to backup your ROM before installing stuff. That way you can restore it if things go wrong.
jsgraphicart said:
Dont use ROM manager for that kind of stuff. Best not to use it at all with the Droid X2 actually. The BSR IS the recovery for the X2. It can be found in the CM7 thread. And a nandroid is just a backup of your ROM that you make yourself within the recovery. Its not a file provided. Its a good idea to backup your ROM before installing stuff. That way you can restore it if things go wrong.
Click to expand...
Click to collapse
Thank you for the reply jsgraphicart.
Good to know on Rom Manager, never has worked right.
I'll go look in the CM7 thread for the BSR, now that you say what it is I might actually have that somewhere after reading when it initially became available.
So if TB Pro can get me into recovery what else do so I can do a nandroid backup? I don't see an option to do that?
poguec said:
Thank you for the reply jsgraphicart.
Good to know on Rom Manager, never has worked right.
I'll go look in the CM7 thread for the BSR, now that you say what it is I might actually have that somewhere after reading when it initially became available.
So if TB Pro can get me into recovery what else do so I can do a nandroid backup? I don't see an option to do that?
Click to expand...
Click to collapse
You are probably booting into the stock recovery, which doesnt have that option. You need to install the custom recovery (BSR) to do that.
jsgraphicart said:
You are probably booting into the stock recovery, which doesnt have that option. You need to install the custom recovery (BSR) to do that.
Click to expand...
Click to collapse
And I get the BSR from the CM 7 thread correct? Once I have that file how do I get that installed and does it wipe my phone before I get a chance to save it as is?
Thank you for your patience and help by the way!
poguec said:
And I get the BSR from the CM 7 thread correct? Once I have that file how do I get that installed and does it wipe my phone before I get a chance to save it as is?
Thank you for your patience and help by the way!
Click to expand...
Click to collapse
Yes, get it from the CM7 thread. Just install it like you would install an app from your SD card. Its the same thing. Use a file browser app and navigate to the apk file then tap it. It will walk you through the rest. Once you have it installed you will have the app in your app drawer called system recovery or something like that. Open it and follow the directions to get into BSR. You have to have your phone plugged into an outlet though. Even though it says plug your phone into nothing. If your are on CM10, you need a file called hijack.zip and will have to place that in a certain location before using BSR. Check out the CM10 thread. The last few posts were talking about that. And the file was posted on the last page. I hope I'm not forgetting anything.
jsgraphicart said:
Yes, get it from the CM7 thread. Just install it like you would install an app from your SD card. Its the same thing. Use a file browser app and navigate to the apk file then tap it. It will walk you through the rest. Once you have it installed you will have the app in your app drawer called system recovery or something like that. Open it and follow the directions to get into BSR. You have to have your phone plugged into an outlet though. Even though it says plug your phone into nothing. If your are on CM10, you need a file called hijack.zip and will have to place that in a certain location before using BSR. Check out the CM10 thread. The last few posts were talking about that. And the file was posted on the last page. I hope I'm not forgetting anything.
Click to expand...
Click to collapse
This is great information, thank you!
poguec said:
This is great information, thank you!
Click to expand...
Click to collapse
I'm sorry to ask more questions but I'm finally ready to update and I'm getting an error. First thing I'm wondering is this is one of those things where I have to be on 2.3.4? I'm on 2.3.5.
The error is:
assert failed: run_program("/tmp/check_kernel") == 0
E:Error in /sdcard/cm10.zip
(Status 7)
Are you running CM on your X2? Why is there so little available for the X2?
poguec said:
I'm sorry to ask more questions but I'm finally ready to update and I'm getting an error. First thing I'm wondering is this is one of those things where I have to be on 2.3.4? I'm on 2.3.5.
The error is:
assert failed: run_program("/tmp/check_kernel") == 0
E:Error in /sdcard/cm10.zip
(Status 7)
Are you running CM on your X2? Why is there so little available for the X2?
Click to expand...
Click to collapse
yes it needs to be 2.3.4 , not 2.3.5 you will have to SBF
Lorenzo VonMatterhorn said:
yes it needs to be 2.3.4 , not 2.3.5 you will have to SBF
Click to expand...
Click to collapse
I had a feeling you'd say that. Well, know what I need to do now.
Thanks again for all the assistance on this! I should be on my way now.
poguec said:
I had a feeling you'd say that. Well, know what I need to do now.Thanks again for all the assistance on this!I should be on my way now.
Click to expand...
Click to collapse
Well I'm here again asking/begging for assistance. I've been trying all afternoon to get back to 2.3.4 without no luck. Each time I use the CW7 recovery to apply the older ROM it just sits on installing. I'm at a loss, I've even factory reset the thing.
poguec said:
Well I'm here again asking/begging for assistance. I've been trying all afternoon to get back to 2.3.4 without no luck. Each time I use the CW7 recovery to apply the older ROM it just sits on installing.I'm at a loss, I've even factory reset the thing.
Click to expand...
Click to collapse
Got to 2.3.4 finally but trying CM10 or the new AOKP build 6 I keep getting messages about signature verification failed. I feel like I'm so close! If I could just get past this latest error.
you flash SBFs with rsd lite
or use ezSBF
if on stock 2.3.4, install bsr/system recovery not cm7 bsr
once rom is installed use cm7 bsr
watch tomsgt's videos
Sent from my XT894 using xda premium
I should have wrote back last night but it got late, I think I ended up at the same result as you posted. That's again, I think I finally got a handle on this.
Hey there me again. It's there an equivalent of the CM7 bsr for CM10?
use cm7 bsr
Sent from my XT894 using xda premium
I tried that, never seems to boot into it. I get it installed and says it was successful but when I hit boot into recovery it just goes to the Motorola screen and freezes.
normally even using reg bar on stock
I connect charger after phone has shut down
Sent from my XT894 using xda premium
Wish I could say I wasn't plugging in as well but I am. So basically it should be working for me but it's not.
http://forum.xda-developers.com/showpost.php?p=37433321&postcount=1519
Sent from my XT894 using xda premium
it is rare that I ever ask for help around these parts. But I just recently got my droid x2 back and wanted to try cm10 alpha 3. The problem is it doesn't seem to want to root. I have SBF'd numerous times and tried both Motorola one click root tool and Pete's Motorola root tool (which actually has worked every time when I used the DX2 as my daily driver with no problems). No matter how many times I run the programs, it seems to stay stock, unrooted gingerbread. Now remember, I have been around these forums for a long time and know what I'm doing. The only difference is that the phone has no number attached to it. Meaning its a WiFi only device. I have tried to bypass the activation which was successful. But I have not been able to root it and install the bootstrap recovery. It just goes through the process and stays the same. I have USB debugging on and checked the unknown sources box. It's been a while since I've done this so I may be missing something. All these tools are the same ones that I've always used with no problems. The only difference is that its a WiFi only device now. So is there any reason why the normal process wouldn't work now?
Have you tried zerg rush?
AKShotgun said:
Have you tried zerg rush?
Click to expand...
Click to collapse
Just tried it with no luck. Its saying it failed to copy over the files because its a read only file system.
its on 2.3.4?
try the ezSBF root option or magic md5
Sent from my XT862 using xda premium
sd_shadow said:
its on 2.3.4?
try the ezSBF root option or magic md5
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yep, I never had this phone on 2.3.5. And these same tools always worked in the past. But I will try this other method.
you check windows device manager, for missing drivers?
Sent from my XT862 using xda premium
Just to double check, after an SBF, you get the activation screen. To bypass that, you have to turn off the phone, hold volume down and power then select "boot android (no bp)"? Thats what I'm doing and I'm just wondering if thats what is causing the phone to not be able to root. Thats the only difference there is from when I had this phone as a daily driver.
sd_shadow said:
you check windows device manager, for missing drivers?
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
I'll double check the next time I do it. But I have attempted this on two different computers. Both of which I have successfully rooted on in the past.
Finally got it rooted and cm flashed on it. Don't know how. Just kept trying until it took. Lol
jsgraphicart said:
Finally got it rooted and cm flashed on it. Don't know how. Just kept trying until it took. Lol
Click to expand...
Click to collapse
sounds alot like the patch and pray method. in a way its the flash and pray.
Hi All,
I have a Droid Razr Maxx (Verizon) which was on 4.1.2 OTA update. I tried to edit the build.prop and messed up. The phone turns on to the Red Moto logo, later goes into the typical Droid Razr graphics and is stuck there for ever (Stuck on Booting?). I am able to enter into recovery, thankfully.
Now can anyone suggest a way to flash only the build.prop to restore it?
Else, can you point me to stock XT912M 4.1.2 so that I can flash getting into recovery?
Or is there is a better way that I could get out of this mess?
Many thanks in advance.
Regards,
Sid
I found this, but it is for Sony.
http://forum.xda-developers.com/showthread.php?t=2212168
Something similar to this would be very helpful !
Regards,
Sid
sidswami said:
Hi All,
I have a Droid Razr Maxx (Verizon) which was on 4.1.2 OTA update. I tried to edit the build.prop and messed up. The phone turns on to the Red Moto logo, later goes into the typical Droid Razr graphics and is stuck there for ever (Stuck on Booting?). I am able to enter into recovery, thankfully.
Now can anyone suggest a way to flash only the build.prop to restore it?
Else, can you point me to stock XT912M 4.1.2 so that I can flash getting into recovery?
Or is there is a better way that I could get out of this mess?
Many thanks in advance.
Regards,
Sid
Click to expand...
Click to collapse
you might want to try using rsd to fully restore the phone. That would also fix your issue. I have done this lots of times. Before you start make sure your phone is charged. Or you will have to buy a USB cable that allows the phone to work with the computer with out charging.
Sent from my XT912 using Tapatalk
In order to flash only build.prop you need to be able to start an adb session and then push the file, or use aroma which executes after boot menu manager so it is not a choice since you can't pass from red logo.
Easier way is rsd flashing a service rom so it will not delete so many files.
Sent from my XT910 using xda app-developers app
Resolved.
tydiamond11 said:
you might want to try using rsd to fully restore the phone. That would also fix your issue. I have done this lots of times. Before you start make sure your phone is charged. Or you will have to buy a USB cable that allows the phone to work with the computer with out charging.
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
angrist said:
In order to flash only build.prop you need to be able to start an adb session and then push the file, or use aroma which executes after boot menu manager so it is not a choice since you can't pass from red logo.
Easier way is rsd flashing a service rom so it will not delete so many files.
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
Used RSD and flashed stock ROM 4.1.2.
Worked perfectly! Thanks all. :victory:
I got the stock ROM from here.
http://sbf.droid-developers.org/
It has links for all Motorola devices and for all versions. Hope it will be helpful.
sidswami said:
Used RSD and flashed stock ROM 4.1.2.
Worked perfectly! Thanks all. :victory:
I got the stock ROM from here.
http://sbf.droid-developers.org/
It has links for all Motorola devices and for all versions. Hope it will be helpful.
Click to expand...
Click to collapse
Great! Glad you did it . Have a great time working with your phone now that it is fixed.