Related
I rooted and flash my nexus one with a rom that was based on the cm7 nightly. It installed completely and I rebooted. It gets past the static x but loops in the moving x. I've tried so many things over the past 8 hours I need help to get a rom working on this. I tried going through the fastboot. Tried using recovery to update from sdcard and I'm having no luck getting this to work again. Hopefully someone on here knows how to fix my problem so I can get a working rom on my phone. Thanks everyone.
Did u install recovery (amon or clockworkmod?? If you did just dload another rom, wipe and flash again
N1
When I originally did the install I installed clockwork and did a back up. When I go into recovery all I can do is either wipe data, update from sdcard and wipe cache. I'm about ready to pull my hair out. I have no clue what went wrong. I've installed new roms on my old phones and no problems, I follow all the instructions.
nandroid, wipe all, retry flashing.
or restore your nandroid backup.
Looking at "adb logcat" while its booting will pinpoint the error.
I've tried to go through fastboot to use my recovery image but I get failed (remote: signature verify fail). I don't know how to get into nandroid and my computer I can only use the fastboot not adb to use logcat. Is there a way to use the fastboot that doesn't come up with the signature fail. I really don't know what happened. What other ways can I use my recovery image if I can't do it from the physical phone?
Sounds like a bad backup. DId you verify MD5?
If you want to start over..
Download AmonRa Recovery 2.2.1. From thread below...
http://forum.xda-developers.com/showthread.php?t=611829
With phone in fastboot mode and connected to PC via usb:
1. Command Prompt: fastboot devices (make sure device is connected)
2. Make sure recovery image file is in your SDK/tools folder
3. Make sure your working directory is SDK/tools folder
4. Command Prompt: fastboot flash recovery recovery-RA-passion-v2.2.1.img
5. After flash is done, reboot to recovery.
6. Wipe everything.
7. Re-flash your ROM.
You can always go back to Clockworkmod if you want. Just re-flash clockwork recovery.
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Your getting this error when flashing what?
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Did you unlock your phone (fastboot oem unlock) or did you just root it?
If you haven't unlocked your phone, perhaps try that then use the previous instructions to flash clockwork or amon recovery image.
link for reference
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Make sure you add to his "Thanks" meter! BTW. That would have been my next suggestion...
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Make sure you add to his "Thanks" meter! BTW, that would have been my next suggestion...
Sorry for the Double Post
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Glad to help. I think we've all had those "OMFG HOW DO I FIX THIS" moments.
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
pplude said:
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
Click to expand...
Click to collapse
The harder this phone is to mod, the more it seems worth it Thanks for trying!
@pplude
Can you give any more detail on the root file you flashed to your droid 3?
Is it really from an Atrix? Are there any downsides to running this root partition?
The reason I ask is - the Atrix has been rooted, so perhaps this would be a good way to attack the droid 3.
Here's the Atrix root hack. Care to give it a try if you're still feeling brave?
http://www.motorolaatrixforum.com/m...s-f15/how-to-root-motorola-atrix-4g-t318.html
It's the preinstall partition from the atrix. There's no integrity check there so it flashes A-OK. I suppose the preinstall from any phone would work though.
You're the second one to do that successfully. I think it was discussed at length as a potential source for root, but we couldn't get the permissions we wanted out of it for some reason. I think it came down to nosuid, but I'm not positive. The root thread talks more about it.
thingonaspring said:
@pplude
Can you give any more detail on the root file you flashed to your droid 3?
Is it really from an Atrix? Are there any downsides to running this root partition?
The reason I ask is - the Atrix has been rooted, so perhaps this would be a good way to attack the droid 3.
Here's the Atrix root hack. Care to give it a try if you're still feeling brave?
http://www.motorolaatrixforum.com/m...s-f15/how-to-root-motorola-atrix-4g-t318.html
Click to expand...
Click to collapse
I used that on my Atrix way back (a month ago , to enable sideloading, I believe.
You want me to give it a try on the D3 (i.e., flash the /preinstall partition?)
That's what I used to break out of fastboot. Can't help us because of nosuid and noxec built in at the kernel level.
pplude said:
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
Click to expand...
Click to collapse
I see you said you've reflashed a half-bricked D3 with an image from Atrix? You said it was root.img?? Did you mean boot.img? I have an Atrix too, and don't see this partition anywhere. Did you or someone pull it with dd? If you have it, could you send it to me and tell me what command you used to flash in moto-fastboot or fastboot?
I tried flashing from the OTA and I'm **** out of luck at the moment, after borking /system trying to make the OTA update in recovery. It's been one headache after another with this fine device
rynosaur said:
I see you said you've reflashed a half-bricked D3 with an image from Atrix? You said it was root.img?? Did you mean boot.img? I have an Atrix too, and don't see this partition anywhere. Did you or someone pull it with dd? If you have it, could you send it to me and tell me what command you used to flash in moto-fastboot or fastboot?
I tried flashing from the OTA and I'm **** out of luck at the moment, after borking /system trying to make the OTA update in recovery. It's been one headache after another with this fine device
Click to expand...
Click to collapse
What the OP is describing only works with fastboot. It sounds like you're able to get into recovery, a completely different system. Start a new thread if this is the case and I'll try to help you out.
psouza4 said:
What the OP is describing only works with fastboot. It sounds like you're able to get into recovery, a completely different system. Start a new thread if this is the case and I'll try to help you out.
Click to expand...
Click to collapse
I have flashed a partition that failed the verification check and now I can't do anything but boot into BP menu. Really, my problem and his are/were pretty similar, I think.
rynosaur said:
I have flashed a partition that failed the verification check and now I can't do anything but boot into BP menu. Really, my problem and his are/were pretty similar, I think.
Click to expand...
Click to collapse
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
pplude said:
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
Click to expand...
Click to collapse
Thanks. I haven't located the /preinstall you're talking about yet, but I believe you're talking about the the /preinstall that was used to unlock the bootloader, or are you talking about the initial power cord-recovery hack? Anywho, I've been able to successfully flash /system and /boot, but I'm looping into BP menu. The fight continues . . .
EDIT: There are some partitions that the phone will not let me flash in Fastboot, and I think least one of those is my problem (like BP, for example). I keep getting a permissions error, and I am using moto-fastboot in linux or windows.
rynosaur said:
Thanks. I haven't located the /preinstall you're talking about yet, but I believe you're talking about the the /preinstall that was used to unlock the bootloader, or are you talking about the initial power cord-recovery hack? Anywho, I've been able to successfully flash /system and /boot, but I'm looping into BP menu. The fight continues . . .
EDIT: There are some partitions that the phone will not let me flash in Fastboot, and I think least one of those is my problem (like BP, for example). I keep getting a permissions error, and I am using moto-fastboot in linux or windows.
Click to expand...
Click to collapse
My success was using the Android SDK fastboot binary on Windows using PowerShell. And yes, it was the preinstall used to unlock the bootloader. I don't have a copy of it anymore, I seem to remember Ben64 on the IRC Freenode Channel #KrazyK giving it to me.
Huh -- so, despite the fact that Atrix4g won't do squat with regular fastboot, you're recommending it for this problem on the Droid3? Interesting. I did find the preinstall you're speaking of -- I actually found two, just in case. Thanks for your help so far, I will report back.
That's why I recommend using PowerShell (free download from Microsoft.com), it's a fully POSIX compliant shell and ADB/Fastboot is a lot more useful with it!
pplude said:
That's why I recommend using PowerShell (free download from Microsoft.com), it's a fully POSIX compliant shell and ADB/Fastboot is a lot more useful with it!
Click to expand...
Click to collapse
Roger that -- I've been using it since I installed Win7 two years ago. The only thing that's better is bash, in my opinion, and I have already seen where flashing a failed phone/bootloader only works with powershell, for some reason.
pplude said:
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
Click to expand...
Click to collapse
Can you help me out with a step-to-step instruction?
I cannot boot into recovery mode, it switch to AP Fastboot mode and says "BOOT FAILURE".
jchenny said:
Can you help me out with a step-to-step instruction?
I cannot boot into recovery mode, it switch to AP Fastboot mode and says "BOOT FAILURE".
Click to expand...
Click to collapse
Did you already do a factory reset? If you haven't do not!
rynosaur said:
Did you already do a factory reset? If you haven't do not!
Click to expand...
Click to collapse
I did try to factory reset...but again it reboots to the AP Fastbook screen again, and wouldn't let me reset it...
The phone still works, just somehow the camera does not work, I have tried 3 or 4 different camera Apps, and none works...
jchenny said:
I did try to factory reset...but again it reboots to the AP Fastbook screen again, and wouldn't let me reset it...
The phone still works, just somehow the camera does not work, I have tried 3 or 4 different camera Apps, and none works...
Click to expand...
Click to collapse
I'm guessing your drivers are messed up. Did you already flash the OTA or copy parts of the OTA into your /system directory?
I've been researching and trying to fix this problem all day and no luck so I need some help.
I unlocked my Atrix HD the other day and was back on stock and everything was working fine. I uninstalled SS3 because I planned on installing CWM soon. I was deleting some bloat, just the AT&T stuff, nothing important, via Titanium Backup when my phone froze and I couldn't do anything. The phone eventually restarted and it now has been stuck at the Unlocked Bootloader warning screen. It cannot go past that at all. I can get to stock recovery and fastboot. I tried to go into fastboot and flash stock per these http://forum.xda-developers.com/showthread.php?t=2226527 instructions and I am getting errors everywhere. I tried to flash stock via RSD and it failed and now it won't recognize the phone. I have all the drivers and everything obviously since I unlocked. Can anyone help me and let me know what I can do??
Can I flash anything from the stock recovery?
EDIT: I managed to install CWM. Now I just am getting an "Error mounting /sdcard" message that's preventing me from getting to my backup.
Ouch.... sorry to hear it mate. System apps shouldn't be messed with.
Sent from my MB886 using xda app-developers app
I was deleting all the AT&T crap and made sure there wasn't anything important. I must have caught something bad by accident.
Manually flash the stock kernel and devtree -- any of them -- and that should fix the sdcard error. I suspect that a lot of the CM errors are from using the RAZR HD's CM kernel and the Atrix HD devtree.
This next idea might not work if you're having mount issues, but its easier if fastboot is giving you hell.
Since you have cwm working, you can sideload this zip with the Mex Retail kernel and devtree, or follow that posts instructions and swap with the stock kernel\devtree of your preference.
Once in CWM, select install from sideload then on the PCs Command Line type "adb sideload /path/to/zipfile"
I love sideload -- best feature ever.
skeevydude said:
Manually flash the stock kernel and devtree -- any of them -- and that should fix the sdcard error. I suspect that a lot of the CM errors are from using the RAZR HD's CM kernel and the Atrix HD devtree.
This next idea might not work if you're having mount issues, but its easier if fastboot is giving you hell.
Since you have cwm working, you can sideload this zip with the Mex Retail kernel and devtree, or follow that posts instructions and swap with the stock kernel\devtree of your preference.
Once in CWM, select install from sideload then on the PCs Command Line type "adb sideload /path/to/zipfile"
I love sideload -- best feature ever.
Click to expand...
Click to collapse
I tried all that a few times but I was getting errors too, but probably my fault somewhere. Anyway, I ended up reinstalling drivers and got stock to install in RSD. I don't know why it didn't work the first time but after 7 hours of trying other methods, the RSD flash worked and everything is running fine now.
Thanks for the help!
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.
PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?
gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?
nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Sorry, meant 4.4.2.
gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.
So I had successfully used MOFO to flash the rooted 5.0 img and when using Titanium to freeze some stuff I must've accidentally added a required system apk to my custom filter and I intended to only have bloat so I deleted all of them on the list including the apk and my phone restarted and whenever i try turning it back on, it shows a black screen after the verizon logo shows up than it gets hot and burns up. I can still use fastboot and I tried reflashing rootjunkys rooted img again but that didn't work so i also tried the stock img and that didn't work either. I also tried Motorola device manager and after it checks for update it says no update is needed and my devices' system is n/a. So help please?
I also tried to factory reset but i cant even get into recovery.
sonic1675 said:
I can still use fastboot and I tried reflashing rootjunkys rooted img
Click to expand...
Click to collapse
RJ's 5.0 rooted image does not work.
Get into fastboot mode, connect your phone to your PC and use mofo.exe to flash the 5.0 pre-rooted image that is linked to in the OP of the MoFo thread.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
ok ill try that and lyk the results. Thanks.
sonic1675 said:
ok ill try that and lyk the results. Thanks.
Click to expand...
Click to collapse
quote me if you do b/c otherwise i may not notice you responded.
JulesJam said:
quote me if you do b/c otherwise i may not notice you responded.
Click to expand...
Click to collapse
So I reflashed every img available on maikos mofo page and the phone still gives me a black screen after the boot logo and whenever i try to get into recovery i get this message:
hab check failed for recovery
failed to validate recovery image
sonic1675 said:
So I reflashed every img available on maikos mofo page and the phone still gives me a black screen after the boot logo and whenever i try to get into recovery i get this message:
hab check failed for recovery
failed to validate recovery image
Click to expand...
Click to collapse
I think you are going to have to try to flash back to stock. It looks like somehow your recovery got messed up. Check out my Noob Guide for instructions on how to flash back to stock 5.0:
http://forum.xda-developers.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
JulesJam said:
I think you are going to have to try to flash back to stock. It looks like somehow your recovery got messed up. Check out my Noob Guide for instructions on how to flash back to stock 5.0:
http://forum.xda-developers.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
Click to expand...
Click to collapse
I tried it but it didn't work. I had to go delete everything through fastboot and flag each IMG separately. But though everything got deleted I got a fresh install of 5.0 and I'm not bricked Lol.