Database Users

HELP! My Atrix will not boot past the Dual Core Technology

My atrix is unlocked. As i was flashing ken's Alien ROM something went wrong and now my phone will not boot past the Dual Core Technology Screen

Daking12794 said:
My atrix is unlocked. As i was flashing ken's Alien ROM something went wrong and now my phone will not boot past the Dual Core Technology Screen
Click to expand...
Click to collapse
just boot back into CWM, wipe everything (Dalvik, cache partition & format data), then re-install ROM, and retry booting.

i am unable to boot into anything besides fastboot and RSD

Then fastboot the gingerbread. Img files. Or rsd to the preunlocked sbf or id try fastboot -w that'll wipe everything
Sent from my MB860 using XDA Premium App

Whenever i try to RSD any sbf it says "Chipset type 53 is not supported" and i am unable to find the img files

Daking12794 said:
i am unable to boot into anything besides fastboot and RSD
Click to expand...
Click to collapse
If you can boot to the fastboot menu, you can get to the recovery menu... just volume down until you see Android recovery, then volume up to enter.
Sent from my MB860 using XDA Premium App

Daking12794 said:
Whenever i try to RSD any sbf it says "Chipset type 53 is not supported" and i am unable to find the img files
Click to expand...
Click to collapse
Im not home now but somewhere in dev section look for kens gingerbread beta 4 NOT alien. it'll take you to the briefmobile site to download. There are img files at bottom of the page
Sent from my MB860 using XDA Premium App

Swiftks said:
If you can boot to the fastboot menu, you can get to the recovery menu... just volume down until you see Android recovery, then volume up to enter.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
When I try to boot into Android Recovery it says
"Magic value mismatch:
%s
Critical failure: Unable to start kernel.
Failed to Launch Recovery (0x00000002)."

Daking12794 said:
When I try to boot into Android Recovery it says
"Magic value mismatch:
%s
Critical failure: Unable to start kernel.
Failed to Launch Recovery (0x00000002)."
Click to expand...
Click to collapse
Well, if you can boot into fastboot, you can fastboot install RomRacer's recovery. Then try.
Sent from my MB860 using XDA Premium App

Boot into fastboot. Connect to computer. Open. Command prompt and use fastboot to erase recovery, system, preinstall,system,boot, user data and cache. Then use fastboot to install the new rom racer recovery. Boot into recovery and install your rom.
Sent from my MB860 using XDA Premium App

Phalanx7621 said:
Boot into fastboot. Connect to computer. Open. Command prompt and use fastboot to erase recovery, system, preinstall,system,boot, user data and cache. Then use fastboot to install the new rom racer recovery. Boot into recovery and install your rom.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
You're a life saver. I had the same problem, tried your method and it took care of the recovery problem. Thank you very much, man.

help please

cm7 started screwing up, com.android.phone fc so reflashed and then the touchscreen is out of wack. bottom buttons dont work and its like i can use the bottom black part of the screen to scroll. ive tried flashing and wiping everything, ive tried new roms and everything but nothing is working

im pretty sure that's what happens when your pds partition ( /dev/block/mmcblk0p3 ) get's screwed up.
where you messing around with partitions or anything in the root folder of your device?

no i was just flashing a backup then decided to wipe and start from scratch then bam is it fixable?

ive tried formatting that too, i just formatted it again to try
its like the screen is shifted down or something, and formatting it ddid nothing

Try a advanced restore & restore your pds.img from with in cwm backup.
Also u might have use fastboot to
Clean things up.. For doing a restore.
Sent from my MB860 using Tapatalk

XRange said:
Try a advanced restore & restore your pds.img from with in cwm backup.
Also u might have use fastboot to
Clean things up.. For doing a restore.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
where do i get a pds.img? and im on a mac, but i can boot into windows, its formatting the sd card right now, after i will try the advanced restore and see how that goes, i hope i didnt screw it up :C

alright so ive read up, and i guess i shouldnt have formatted that partition in the first place.. lesson learned, now i just need to find that file and push it back to my phone, is anyone willing to help me out here?
i got the file but im having trouble flashing it with fstboot

im stuck
Smith-Strattons-MacBook:~ Smitty$ cd ~/ moto-fastboot-osx/moto-fastbootSmith-Strattons-MacBook:~ Smitty$ cd ~/downloads/moto-fastboot-osxSmith-Strattons-MacBook:moto-fastboot-osx Smitty$ moto-fastboot-osx32 flash pdsfix pdsfix.img
-bash: moto-fastboot-osx32: command not found
Smith-Strattons-MacBook:moto-fastboot-osx Smitty$

I use a MacBook Pro and I use fastboot, apkmanager, and the Android SDK all fine.
Move the fastboot file to /Users/Smitty
Then go into the terminal and do
# fastboot wipe system
# fastboot wipe userdata
# fastboot wipe cache
# fastboot wipe webtop
# fastboot wipe preinstall
# fastboot wipe boot
Then load directly into recovery. Wipe Data/System Reset, Wipe Cache and Dalvik Cache, then install whatever ROM you wwant and let me know
Sent from my MB860 using XDA App

There is fastboot for mac & Linux. In 32 bit & 64 bit version.
Also if you was using romracers cwm you find pds.img in cwm backup folder..
Which you can restore from the Advanced Restore Option..
Here link for fastboot all OS options.
http://forum.xda-developers.com/showthread.php?t=1138092
Erase System with Fastboot
Code:
./moto-fastboot-osx64 erase system
./moto-fastboot-osx64 -w
./moto-fastboot-osx64 erase webtop
./moto-fastboot-osx64 erase preinstall
./moto-fastboot-osx64 erase boot
Sent from my MB860 using Tapatalk

jakew02 said:
I use a MacBook Pro and I use fastboot, apkmanager, and the Android SDK all fine.
Move the fastboot file to /Users/Smitty
Then go into the terminal and do
# fastboot wipe system
# fastboot wipe userdata
# fastboot wipe cache
# fastboot wipe webtop
# fastboot wipe preinstall
# fastboot wipe boot
Then load directly into recovery. Wipe Data/System Reset, Wipe Cache and Dalvik Cache, then install whatever ROM you wwant and let me know
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
XRange said:
There is fastboot for mac & Linux. In 32 bit & 64 bit version.
Also if you was using romracers cwm you find pds.img in cwm backup folder..
Which you can restore from the Advanced Restore Option..
Here link for fastboot all OS options.
http://forum.xda-developers.com/showthread.php?t=1138092
Erase System with Fastboot
Code:
./moto-fastboot-osx64 erase system
./moto-fastboot-osx64 -w
./moto-fastboot-osx64 erase webtop
./moto-fastboot-osx64 erase preinstall
./moto-fastboot-osx64 erase boot
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
YOU ARE MY HERO!!!!!!!!!
i was trying to type moto-fastboot-osx32 flash pds pdsfix.img
i needed the ****** ./ ****** in the front!! im soo happpy now that my phones working again, you guys are my heros so happy now

Stuck on the Google Splach Screen

I unlocked and rooted. I then installed the update from Google. Upon reboot, it went back into Clockwork Recovery and then asked about installing the untrusted update. I try to install but it errored and restarted into Clockwork Recovery. I tried to wipe cache and wipe data/factory reset. When I select restart it gets hung on the Google Splash Screen. How do I fix this? Also, everytime I go into Recovery now it is Clockwork and not stock. I thought it would only flash Clockwork Recovery temporarily.

xda6969 said:
I unlocked and rooted. I then installed the update from Google. Upon reboot, it went back into Clockwork Recovery and then asked about installing the untrusted update. I try to install but it errored and restarted into Clockwork Recovery. I tried to wipe cache and wipe data/factory reset. When I select restart it gets hung on the Google Splash Screen. How do I fix this? Also, everytime I go into Recovery now it is Clockwork and not stock. I thought it would only flash Clockwork Recovery temporarily.
Click to expand...
Click to collapse
Go here and download the factory firmware for the Nexus 10:
https://developers.google.com/android/nexus/images
Then follow these steps:
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Its for a Nexus 7 but they helped me fix my Nexus 10 too after I got stuck in the bootloop. Just use the different file names for the Nexus 10. You will need something to extract a tgz and a tar file for this process. You will also have to manually boot into the bootloader by powering the 10 off, then hold down volume up + volume down + power until you get the bootloader screen. Then follow those steps. It took me a few tries to get into the bootloader, not sure what that was about.
Initially, flashing a bad recovery got mine stuck, so make sure you grab a confirmed working recovery before you flash it. You will just have to start over, with the exception of unlocking as that would be sticky through this process.
Good luck!

When I flashed the image as in step 8, it said archive does not contain boot.sig, recovery.sig, system.sig. Then when it completed, it rebooted on its own and then it was still stuck on the Google Splash. I went back into stock recovery and did a Wipe Data/Factory Reset and now it works again. Thanks a lot!

xda6969 said:
When I flashed the image as in step 8, it said archive does not conatin boot.sig, recovery.sig, system.sig. Then when it completed, it rebooted on its own and then it was still stuck on the Google Splash. I went back into stock recovery and did a Wipe Data/Factory Reset and now it works again. Thanks a lot!
Click to expand...
Click to collapse
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command

bigdwg71, thanks a million! :good:

beama said:
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
Click to expand...
Click to collapse
I also had to flash system.img manually as well...

beama said:
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
Click to expand...
Click to collapse
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.

xda6969 said:
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
Click to expand...
Click to collapse
Those images act like a wipe for the /data & /cache partitions... similar to using fastboot -w
Also, this thread does not belong in the Development forum... Mods, please move this!!

xda6969 said:
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
Click to expand...
Click to collapse
Also, how do you flash Clockwork so it is not there permanantly? I only want to use it to install Superuser and then I want to be able to go to stock recovery.

xda6969 said:
Also, how do you flash Clockwork so it is not there permanantly? I only want to use it to install Superuser and then I want to be able to go to stock recovery.
Click to expand...
Click to collapse
From fastboot, you type something like "fastboot boot RECOVERY.img" instead of "fastboot flash RECOVERY.img"

espionage724 said:
From fastboot, you type something like "fastboot boot RECOVERY.img" instead of "fastboot flash RECOVERY.img"
Click to expand...
Click to collapse
I've used fastboot flash RECOVERY.img on my Galaxy Nexus many times and it was always temporary.

You can use the "fastboot boot" command to boot to CWRM temporarily. "Fastboot flash" will flash it permanently. I think there some devices that would reinstall the default recovery image if I recall. The Nexus 10 is not one of them.
Sent from my Nexus 10 using XDA Premium HD app

bigdwg71 said:
You can use the "fastboot boot" command to boot to CWRM temporarily. "Fastboot flash" will flash it permanently. I think there some devices that would reinstall the default recovery image if I recall. The Nexus 10 is not one of them.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the clarification.

[Q] Taking forever to boot after flashing factory images

Hi, I have a 8GB Nexus 4 I have just flashed the factory images onto it to do a factory reset and it seems to be bootlooping
Anyone else done this know how long it should take? Didn't take long on the Galaxy Nexus to bootup after flashing factory images

Reboot into recovery and factory reset and wipe cache.
Sent from my Nexus 7 using xda premium

El Daddy said:
Reboot into recovery and factory reset and wipe cache.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Ok, so get into fastboot using the hardware keys flash a custom recovery factory reset and wipe cache?
Will give it a try, thanks

Nope don't flash a custom recovery. Boot into the bootloader. Scroll to recovery using the volume buttons and press power to enter.
When you are there press volume up and power to open the menu. Then wipe cache and reset.
Sent from my Nexus 4

El Daddy said:
Nope don't flash a custom recovery. Boot into the bootloader. Scroll to recovery using the volume buttons and press power to enter.
When you are there press volume up and power to open the menu. Then wipe cache and reset.
Sent from my Nexus 4
Click to expand...
Click to collapse
Ok that did it \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/
Thank you

No problem. Not really sure why that is needed. It must be a bug with the bootloader not wiping data and cache correctly.
Sent from my Nexus 7 using xda premium

People should really learn fastboot commands. it really helps especially times like these.
I completely wipe my phone using fastboot only then using the format command on each partition. the phone will then wipe itself after a reboot. after flashing new images of course. not saying you ^^ just saying for people in general who don't know any of them

daddioj said:
People should really learn fastboot commands. it really helps especially times like these.
I completely wipe my phone using fastboot only then using the format command on each partition. the phone will then wipe itself after a reboot. after flashing new images of course. not saying you ^^ just saying for people in general who don't know any of them
Click to expand...
Click to collapse
The problem is for some reason the fastboot erase command and -w sometimes isn't formating userdata properly and causing bootloops.
There have been a lot of reports. Check efrants return to stock sticky.
Sent from my Nexus 7 using xda premium

hmm its been working well for me
I'll do it all manually
I think the erase command actually kills the partition. and the format command will ready the area for data. correct me if I am wrong?
but i'll use the "erase" command first for all partitions. then i'll format them
fastboot format system
fastboot format cache
fastboot format userdata
then i'll go ahead and flash all the image files. then once I reboot the phone actually does a factory reset on its own.
but I know what you mean. I read that as well. but this method ^^^ has been working for me.

daddioj said:
hmm its been working well for me
I'll do it all manually
I think the erase command actually kills the partition. and the format command will ready the area for data. correct me if I am wrong?
but i'll use the "erase" command first for all partitions. then i'll format them
fastboot format system
fastboot format cache
fastboot format userdata
then i'll go ahead and flash all the image files. then once I reboot the phone actually does a factory reset on its own.
but I know what you mean. I read that as well. but this method ^^^ has been working for me.
Click to expand...
Click to collapse
You're probably right.
I'm pretty sure with "fastboot flash userdata" it will rebuild the partition properly.
But possibly the reason people are running into issues is when using the command "fastboot erase cache" This was never a problem with the galaxy nexus but for some reason it might be for the N4.
Others have claimed bootloops when using "fastboot -w update" which shouldn't be happening. That makes me think its a bootloader bug.
Sent from my Nexus 7 using xda premium

daddioj said:
hmm its been working well for me
I'll do it all manually
I think the erase command actually kills the partition. and the format command will ready the area for data. correct me if I am wrong?
but i'll use the "erase" command first for all partitions. then i'll format them
fastboot format system
fastboot format cache
fastboot format userdata
then i'll go ahead and flash all the image files. then once I reboot the phone actually does a factory reset on its own.
but I know what you mean. I read that as well. but this method ^^^ has been working for me.
Click to expand...
Click to collapse
El Daddy said:
You're probably right.
I'm pretty sure with "fastboot flash userdata" it will rebuild the partition properly.
But possibly the reason people are running into issues is when using the command "fastboot erase cache" This was never a problem with the galaxy nexus but for some reason it might be for the N4.
Others have claimed bootloops when using "fastboot -w update" which shouldn't be happening. That makes me think its a bootloader bug.
Click to expand...
Click to collapse
Thanks both for this, but bookmarked the thread now in case it happens again. I know better now

Advice please

Sent from my Nexus 4 using xda app-developers app

Can I please have some advice guys
I am on stock 4.2.1 at the moment I want to install the minco ROM with Francis kernel to do this
1. Unlock boot loader
2. Root & install cwm recovery
3. Make a backup (don't known how)
4. Add the ROM and kernel into internal storage on laptop
5. Go into recovery mode and flash ROM and kernel (can I flash both at the same time or does it have to be done separately)
6. Reboot
Guys am I right or have I missed something's
Apologies its first time for me and I'm going to do with without toolkits
Sent from my Nexus 4 using xda app-developers app

Looks pretty good.
3.Once you're in recovery, you'll see the backup option.
5. Wipe system, data, cache and dalvik cache and flash ROM, then kernel.
Good for you for not using a toolkit.

Thanks very much for that
Sent from my Nexus 4 using xda app-developers app

I would highly recommend twrp recovery instead. It is what most developers use these days.
Do you know how to setup the usb / adb / fastboot on your computer?
If so, all you need to do is download the .img file from the twrp website for the n4, boot into the bootloader (from power off, hold volume down and then press power while holding vol down), and the commands are:
Fastboot oem unlock (then look at your phone...choose the option with volume, select with power)
Fastboot flash recovery insert_name_of_recovery_file_here.img
Then reboot, put minco and the newest Franco kernel on your sd card, reboot to bootloader, choose recovery, make your backup there(will be obvious how to do this), wipe data / factory reset, and then install minco and the newest Franco.
Let me know if you need more help
Sent from my Nexus 4 using Tapatalk 2

bongostl said:
I would highly recommend twrp recovery instead. It is what most developers use these days.
Do you know how to setup the usb / adb / fastboot on your computer?
If so, all you need to do is download the .img file from the twrp website for the n4, boot into the bootloader (from power off, hold volume down and then press power while holding vol down), and the commands are:
Fastboot oem unlock (then look at your phone...choose the option with volume, select with power)
Fastboot flash recovery insert_name_of_recovery_file_here.img
Then reboot, put minco and the newest Franco kernel on your sd card, reboot to bootloader, choose recovery, make your backup there(will be obvious how to do this), wipe data / factory reset, and then install minco and the newest Franco.
Let me know if you need more help
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply I thought if I download CWM recovery I would get auto update features? e.g installing ROM update
Do I save the TWRP image file anywhere on the c:\ or do i move it into my phones sd card
I take it the command oem unlock- unlocks my phone -
does fastboot flash recovery root my phone or does it install the recovery
Do I need to root my phone what would the command be for it
Thanks again

bash156 said:
Thanks for your reply I thought if I download CWM recovery I would get auto update features? e.g installing ROM update
Do I save the TWRP image file anywhere on the c:\ or do i move it into my phones sd card
I take it the command oem unlock- unlocks my phone -
does fastboot flash recovery root my phone or does it install the recovery
Do I need to root my phone what would the command be for it
Thanks again
Click to expand...
Click to collapse
You put the twrp image file in the same folder as your fast boot binary.
Fast booting recovery will not give you root. You need to flash the recovery, have the su zip on your phone and then go into your custom recovery (twrp) and flash the super user zip. Then you will obtain root.
Rooting your phone is simply flashing that zip file.
Custom rom is simply flashing that zip.
Kernel is simply flashing that zip.
Except for custom rom you need to wipe factory settings before flashing to have the phone to boot up.
The way to fastboot recovery is the command,
Fastboot flash recovery name-of-recovery.img
Replace name of whatever with the file you downloaded (don't actually type name of recovery lol)
Sent from my Nexus 4 using xda premium