Last night I decided to do unlock and root, followed this http://forum.xda-developers.com/showthread.php?t=1202883 , it worked, then I put [ROM] Alien ★ Build #3, didnt work, then I tried [ROM] CherryBlur v1.4d and I think wiped cache?
After it was done my phone doesn't start anymore.
It's stuck at Moto screen and screen blinks.
I tried fruit cake, but I'm not sure I'm doing it right.
Any help is appreciated, I'm out of ideas.
1. Does your phone say "unlocked" in the upper left hand corner of the black screen with the red "M" on it?
2. Does the circle around the "M" pulsate at all (in other words - does it show the boot animation?)
3. When you say that the screen blinks, would it be safe to say that it is actually rebooting, getting the same spot, and rebooting again?
4. What recovery mod are you using?
The answers to those questions will greatly assist in finding a solution to your problem. My guess would be that you are in a boot loop, which is not a brick. Boot up the phone while holding the volume down button. When you see the word "Fastboot", hit volume down until you see "Android Recovery", then hit the volume up buton.
Wipe Data
Wipe Cache
Wipe Dalvik
Reboot the same way and get into Android Recovery.
Install Zip from SD Card
Choose Zip
Point recovery to the ROM of your choice
Install it
Reboot
Win
You probably just didn't wipe data, cache, and dalvik before installing the ROM, and got yourself into a boot loop because of it.
DK
thanks for reply,
1. yes it says unlocked
2. it doesn't pulsate, no animation, screen just go blank for 2 sec, then back to M logo
3. not rebooting
4. not sure?
when i hold volume down I can access the menu..
when i click "android recovery" it shows green android robot with exclamation mark in triangle.
It sounds like you have the stock recovery,
Try romracer's recovery here:
http://forum.xda-developers.com/showthread.php?t=1204500
smashcz said:
thanks for reply,
1. yes it says unlocked
2. it doesn't pulsate, no animation, screen just go blank for 2 sec, then back to M logo
3. not rebooting
4. not sure?
when i hold volume down I can access the menu..
when i click "android recovery" it shows green android robot with exclamation mark in triangle.
Click to expand...
Click to collapse
You need to reinstall RomRacer's recovery from the link provided in the response above this one.
There is a step in installing a new recovery that is often not followed, and that is manually removing the file...
/system/etc/install_recovery.sh
A quick look at RomRacer's thread shows that he didn't include this step in the install process of the recovery.
Basically, if you don't remove that file, when you boot up your android, it is going to flash the stock recovery over the recovery you have installed. For the time being... follow the instructions on RomRacer's thread to install his recovery, then boot the phone into that recovery, wipe data, wipe cache, wipe dalvik, reboot into recovery again and install the ROM of your choice.
This should break your boot loop and let you get into the phone. Luckily for you, most ROMs (all of them I believe) have the /system/etc/install_recovery.sh removed from them, so you don't have to worry about removing it yourself (unless you flash back to a stock ROM).
Good luck, let us know what happens.
DK
I'm looking at this thread [RECOVERY][2011-08-07] Custom CWM-based Recovery 4.0.1.4-atrix2 , but I'm not really sure what should I do? Download the zip file and do what?
Thanks so much for the replies.
smashcz said:
I'm looking at this thread [RECOVERY][2011-08-07] Custom CWM-based Recovery 4.0.1.4-atrix2 , but I'm not really sure what should I do? Download the zip file and do what?
Thanks so much for the replies.
Click to expand...
Click to collapse
You need to download moto-fastboot to your PC. (http://forum.xda-developers.com/showthread.php?t=1138092). Extract the moto-fastboot zip to the root of your C drive. (C:\moto-fastboot).
Download the recovery file you need from the thread. The file you need is not the zip file. You need the .img file. Download one of the following if you are AT&T:
AT&T USERS
Orange 4.0.1.4-atrix2 / ZIP version.
MD5 e34ae84c5e653781cc7fa45d4e3886d5 / f1e732ee8876b7805a4d1073fd4370b1
Cyan 4.0.1.4-atrix2 / ZIP version.
MD5 60c7697130792d2be64be7c0b6749c8b / fc83487c7c7014bde736681a387129a9
Light green 4.0.1.4-atrix2 / ZIP version.
MD5 d28a5f4db45647d47e1d5202a30a01d5 / 004e447aae1e8796d63f46470395060b
Dark green 4.0.1.4-atrix2 / ZIP version.
MD5 d217f3d50a1f2d2d491c77603e689d48 / 3315b66bcbbb7546661bf10a5cc3fab1
Blue 4.0.1.4-atrix2 / ZIP version.
MD5 1e5ec8837e367f70e2cc807c0e012929 / 1651d6460150a9f503604f318c7081fa
If you are not AT&T, download the relevant International file, etc.
Place the image file in your moto-fastboot folder.
Open a cmd prompt on your PC ( Start - Run - cmd - Enter).
Reboot your phone, and press volume down button. When you see Fastboot on the screen, press volume up button. Connect Phone to PC via USB.
Type the following at the command prompt (see this thread again http://forum.xda-developers.com/showthread.php?t=1204500):
cd C:\moto-fastboot
moto-fastboot devices (You should see your device number. This is just a check to make sure your phone is being seen)
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix2.img
moto-fastboot reboot
You should now be able to boot into recovery.
I'm on AT&T,
does it matter which img (colors?) to download?
i followed the commands
but when i write "moto-fastboot devices"
it says "is not recognized as command .....
I don't use moto-fastboot I just use fastboot. Forgot where but I donwloaded a zip tools pack somewhere on here.... anyway:
Try going into cmd and see if you have cd c:\fastboot or cd c:\moto-fastboot
smashcz said:
i followed the commands
but when i write "moto-fastboot devices"
it says "is not recognized as command .....
Click to expand...
Click to collapse
Make sure you're specifying the correct path.
Wherever you placed moto-fastboot, make sure you're placing that in first.
Ex: If you placed it in C,
cd C:\
cd C:\moto-fastboot
moto-fastboot devices
If you're still seeing an unrecognized command, make sure you don't have any spaces or extra characters in whatever you named it.
Once you see your device is recognized, follow what CaelanT has said.
I'm a bit confused now...
Your original post says that you followed instructions found here:
http://forum.xda-developers.com/showthread.php?t=1202883
That means you've used fastboot to unlock the device and you've used fastboot to flash tenfar's recovery. Also.. that guide (as well as RomRacer's) both neglect to have you remove /system/etc/install_recovery.sh.
Anyway... go into the same directory you were in when you were following those instructions. That directory has fastboot in it. Put RomRacer's recovery in that folder, then follow romracer's instructions to install it.
After you have RomRacer's installed, boot into Android recovery and wipe data, cache, and dalvik cache, then flash a ROM. Done.
DK
Got it working with this http://forum.xda-developers.com/showthread.php?t=1204500
Thank you so much guys.
Now I have CherryBlur v1.4d.
Just wondering how it happened, so I won't do the same mistake again.
If I want to install new ROMs, do I have to-
Wipe Data
Wipe Cache
Wipe Dalvik ?
before and after?
smashcz said:
Just wondering how it happened, so I won't do the same mistake again.
If I want to install new ROMs, do I have to-
Wipe Data
Wipe Cache
Wipe Dalvik ?
before and after?
Click to expand...
Click to collapse
Before you install a new ROM, always Wipe Data, Cache, and Dalvik. At times when you upgrade a ROM you need to do that as well - not always though. The Authors usually say when they release an update whether or not you need to wipe data, cache, and dalvik, so just look for it.
Now that you are running RomRacer's recovery, you can backup your phone. So before you try something new, its always good to backup since you can just restore later if you need to.
Enjoy the ROMs, there are a bunch of food ones available in the Dev section, and a pre-beta of CM7 in the general section.
DK
Fastboot won't work >256MB. It will work with smaller, and if you use fastboot you should replace all moto-fastboot comands with just fastboot.
Motorola gave us the ability to write > 256MB with moto-fastboot.
smashcz said:
Got it working with this http://forum.xda-developers.com/showthread.php?t=1204500
Thank you so much guys.
Click to expand...
Click to collapse
That's where I pointed you to with added instructions. Click thanks...............that will take less time than I took to post instructions.
Also, good rule of thumb when flashing a ROM is:
Wipe Dalvik
Wipe cache
Factory/data reset
Flash ROM
Wipe Dalvik
Wipe cache
Factory data/reset
Reboot
For Kernels:
Wipe Dalvik
Wipe cache
Flash kernel
Wipe Dalvik
Wipe cache
Reboot
It may not be needed all the time, but it takes a couple of minutes, and can save you many headaches along the way!
Cheers!
<edit> It really pays to read the dev posts more than once, and follow any links, reading those posts more than once. All the info 99% of us need is already on the forums. It is just not read and/or followed in the rush to balk phones up most of the time. I have done pretty much every mod on the Atrix forums multiple times. Only once have I had a panic, and that was actually last night flashing back to Aura from CM7 when I got stuck in a boot loop. I found the resolution which was to fastboot -w, and then flashed the boot.img from Aura and was good to go. Found all the help I needed in these forums.
Actually, I pointed him there first, I win! So thank me too. jk
CaelanT said:
That's wher I pointed you to.
Click to expand...
Click to collapse
live4nyy said:
Actually, I pointed him there first, I win! So thank me too. jk
Click to expand...
Click to collapse
<edit> post deleted......wtf ever.....next time I'll let you write the instructions for someone who obviously was struggling.
Related
i rooted my mobile using alpharev and it turned my s-off and installed clockwork recovery mod 3.0.0.6 ,later i downloaded cynogen mod 7, and while updating it hung on now it is not at all booting it just shows htc in boot screev and reeboots again and again pls help me
Go back into recovery, wipe data and cache and the reflash CM7
Its definitely not bricked, so dont worry. Firstly, make sure you have wiped all data in Clockworkmod (Wipe Data / Factory Reset Option, Wipe Cache Partition also Format /system under Advanced). Once you have done this, try reflashing the CM7 ROM File. It should work. Reboot into Recovery by turning off your phone, pressing Vol Down + Power, Navigating to Recovery, and Pressing Power Button on it.
If it still fails, it would be better to use an updated version of Clockworkmod Recovery. This solved the bootloop issue for a few users.
3xeno said:
Its definitely not bricked, so dont worry. Firstly, make sure you have wiped all data in Clockworkmod (Wipe Data / Factory Reset Option, Wipe Cache Partition also Format /system under Advanced). Once you have done this, try reflashing the CM7 ROM File. It should work. Reboot into Recovery by turning off your phone, pressing Vol Down + Power, Navigating to Recovery, and Pressing Power Button on it.
If it still fails, it would be better to use an updated version of Clockworkmod Recovery. This solved the bootloop issue for a few users.
Click to expand...
Click to collapse
i tried it several times it says installing update and it again hangs pls help
3xeno said:
Its definitely not bricked, so dont worry. Firstly, make sure you have wiped all data in Clockworkmod (Wipe Data / Factory Reset Option, Wipe Cache Partition also Format /system under Advanced). Once you have done this, try reflashing the CM7 ROM File. It should work. Reboot into Recovery by turning off your phone, pressing Vol Down + Power, Navigating to Recovery, and Pressing Power Button on it.
If it still fails, it would be better to use an updated version of Clockworkmod Recovery. This solved the bootloop issue for a few users.
Click to expand...
Click to collapse
i tried it several times i removed my battery again booted to recoverymod wipe data/reset factory reset then install from sd card then i choosed the zib file .it then shows installing updating then it hangs pls pls pls help
i tried but it still hangs saying installing update and hangs on
Nivin Abraham said:
i tried but it still hangs saying installing update and hangs on
Click to expand...
Click to collapse
Please don't multi post. Update your Clockworkmod Recovery then. The guide can be found here:
http://forum.xda-developers.com/showthread.php?p=14693680
I had nothing but trouble using recorver 3.0.0.6 . Recovery 3.1.0.2 amd 2.5.07 have worked flawless for me though.
could u pls tell me how to update Clockworkmod Recovery , i downloaded ur file but i dont know how to update it
could u pls tell me how to update Clockworkmod Recovery
- First, Download the attachment in that thread, Place it somewhere, like on your C Drive, in a Folder called Fastboot.
- Then, Download the Updated Clockworkmod Recovery (Again linked in that thread). Extract the Recovery.img file from within the Zip file and place it in the Fastboot folder created in the step before.
- Connect your Wildfire to your PC. Turn it off, and turn on in HBoot Mode. (When your phone is switched off, then Press Vol Down + Power Simultaneously. Then, Navigate to Fastboot using the Volume Keys, and Press the Power Button. Your Wildfire is now in Fastboot Mode.
- Then, Open Command Prompt, and put in the following. (I am assuming your folder is created in C > Fastboot)
cd\
cd Fastboot
fastboot flash recovery recovery.img
(In the third step, I am assuming that the file name of the updated Clockworkmod Recovery is recovery.img) It will show two steps - Sending Recovery, and Writing Recovery. After this is done, your phone has the newer version of Clockworkmod Recovery and you can flash the ROM all over again and test.
3xeno said:
- First, Download the attachment in that thread, Place it somewhere, like on your C Drive, in a Folder called Fastboot.
- Then, Download the Updated Clockworkmod Recovery (Again linked in that thread). Extract the Recovery.img file from within the Zip file and place it in the Fastboot folder created in the step before.
- Connect your Wildfire to your PC. Turn it off, and turn on in HBoot Mode. (When your phone is switched off, then Press Vol Down + Power Simultaneously. Then, Navigate to Fastboot using the Volume Keys, and Press the Power Button. Your Wildfire is now in Fastboot Mode.
- Then, Open Command Prompt, and put in the following. (I am assuming your folder is created in C > Fastboot)
cd\
cd Fastboot
fastboot flash recovery recovery.img
(In the third step, I am assuming that the file name of the updated Clockworkmod Recovery is recovery.img) It will show two steps - Sending Recovery, and Writing Recovery. After this is done, your phone has the newer version of Clockworkmod Recovery and you can flash the ROM all over again and test.
Click to expand...
Click to collapse
pls dude dont get mad i am just frustrated dude i seriously dont know how to open command prompt. i did all the steps u asked me to do. i downloaded the file which u asked me to do i saved it in c/fast boot then extracted the file recovery-clockwork-3.2.0.0-j_r0dd_mod-buzz.img then i switched on my mobile in hboot mode then connected myusb cable to it, it showed hboot usb then i selected fastboot.
now it shows fastboot usb and these r the options given below
bootloader
reboot
reboot bootloader
power down
i seriously dont know how to open command prompt ur the only one who could help me so pls help me with all due respect
Nivin Abraham said:
pls dude dont get mad i am just frustrated dude i seriously dont know how to open command prompt. i did all the steps u asked me to do. i downloaded the file which u asked me to do i saved it in c/fast boot then extracted the file recovery-clockwork-3.2.0.0-j_r0dd_mod-buzz.img then i switched on my mobile in hboot mode then connected myusb cable to it, it showed hboot usb then i selected fastboot.
now it shows fastboot usb and these r the options given below
bootloader
reboot
reboot bootloader
power down
i seriously dont know how to open command prompt ur the only one who could help me so pls help me with all due respect
Click to expand...
Click to collapse
i downloaded only the updated clockworkmod recovery ,i dont know which (Download the attachment in that thread) i dont know which file ur asking me to download from that thread
Nivin Abraham said:
pls dude dont get mad i am just frustrated dude i seriously dont know how to open command prompt. i did all the steps u asked me to do. i downloaded the file which u asked me to do i saved it in c/fast boot then extracted the file recovery-clockwork-3.2.0.0-j_r0dd_mod-buzz.img then i switched on my mobile in hboot mode then connected myusb cable to it, it showed hboot usb then i selected fastboot.
now it shows fastboot usb and these r the options given below
bootloader
reboot
reboot bootloader
power down
i seriously dont know how to open command prompt ur the only one who could help me so pls help me with all due respect
Click to expand...
Click to collapse
Command Prompt is to be opened on your Windows PC. Not on your mobile. Once you have entered into Fastboot Mode and your Wildfire is connected to your PC, thats all you need to do.
Open Start Menu. Then Select Run. Then type "cmd" (Without Quotes) and Press Enter. This will open the Command Prompt. Then follow what I said before.
(Note - If your folders name is fast boot, then replace fastboot in the commands above with fast boot. It's basically the name of your folder).
Rename the IMG file you extracted to Recovery.img, it will typing the command easier.
Lastly, my only request to you - Make only 1 post at a time. Others here are normal members and not someone with the full day free . When you continuously post something, its frustrating to read and I dont feel like replying anymore to that person.
3xeno said:
Command Prompt is to be opened on your Windows PC. Not on your mobile. Once you have entered into Fastboot Mode and your Wildfire is connected to your PC, thats all you need to do.
Open Start Menu. Then Select Run. Then type "cmd" (Without Quotes) and Press Enter. This will open the Command Prompt. Then follow what I said before.
(Note - If your folders name is fast boot, then replace fastboot in the commands above with fast boot. It's basically the name of your folder).
Rename the IMG file you extracted to Recovery.img, it will typing the command easier.
Lastly, my only request to you - Make only 1 post at a time. Others here are normal members and not someone with the full day free . When you continuously post something, its frustrating to read and I dont feel like replying anymore to that person.
Click to expand...
Click to collapse
i opened command prompt and till the second step which u asked me to type was successfull
cd\
cd Fastboot
after this u asked me to type
fastboot flash recovery recovery.img
it says fastboot is not recognized as an internal or external command,operable program or batch file.
i dont know how to proceed further ,i am really sorry for multi posting i am new to xda dude , i am terribly sorry pls forgive me
You need to have HTC driver for doing that. Install this iin your windows PC.
Link: http://db.tt/BOJCbnD
Go with the process after installing this.
Sent from my HTC Wildfire using XDA App
Nivin Abraham said:
i opened command prompt and till the second step which u asked me to type was successfull
cd\
cd Fastboot
after this u asked me to type
fastboot flash recovery recovery.img
it says fastboot is not recognized as an internal or external command,operable program or batch file.
i dont know how to proceed further ,i am really sorry for multi posting i am new to xda dude , i am terribly sorry pls forgive me
Click to expand...
Click to collapse
Dont worry about it. That was just my view.
Anyway, I hope the folder creation was correct. I hope that when you extracted the Android Win Tools folder into your C:\Fastboot folder, you deleted the original folder?
ie:, In your Fastboot folder, you shouldnt have any other folder/sub folder, and it must contain only these 4 files:
- adb.exe
- AdbWinApi.dll
- AdbWinUsbApi.dll
- Fastboot.exe
Once you have ensured this, then make sure you enter Fastboot mode on your Wildfire Correctly.
- Start HBoot mode
- Then Plug in the USB Cable
- Press Power Button, then another set 4 Options will appear, the first being Fastboot
- Then Press Power Button again
After this, try running the commands in command prompt again. Let me know how it goes.
And it you still face any issues with fastboot flashing, then see my sign for the post link to complete guide. Go there and download attached pc49img.zip and put it on your root of memory card (formatted previously with fat32 partition) . Then reboot to hboot menu to update the recovery. That's all.
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
And it you still face any issues with fastboot flashing, then see my sign for the post link to complete guide. Go there and download attached pc49img.zip and put it on your root of memory card (formatted previously with fat32 partition) . Then reboot to hboot menu to update the recovery. That's all.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
dude ur the man it worked i am so so so happy no words to express it showed
sending recovery
writing recovery
Nivin Abraham said:
dude ur the man it worked i am so so so happy no words to express it showed
sending recovery
writing recovery
Click to expand...
Click to collapse
Great, Hope they were followed by the words "OK". If so, you have the new Recovery 3.2.0.0 on your Wildfire.
Getting the hang of Fastboot is very important IMO. It helps flashing Recoveries in 1 go, and, also helps restoring Nandroid Restores, among many other features. I am glad you have experienced it, and, not gone the "PC49IMG" way.
Hey,
I am in the process of going from stock (rooted) GB and wanted to document my steps. I am not a developer, I have no idea what I am doing, everything here is from links/guides elsewhere.
If you know of a faster/easier way to do it, please respond and I will update as required!
How can I Backup text messages/missed calls etc to cyanogen?
My System:
AT&T Atrix 4g with Stock Gingerbread OTA update (rooted)
Windows 7 x64 laptop
Guide:
My general understanding is as follows:
1. Unlock Phone
2. Download and Install CWM
3. Install Cyanogen
1. To unlock the phone we need to first get a few applications installed, I am running windows 7 so below are the files.
RSDLite 5.3.1 link
x64 Windows drivers
AT&T Unlocker
After downloading, install the first two packages, the third package will be used to unlock your bootloader:
Open a command prompt window
On Windows, press Start and type “cmd” then press the enter button
Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
cd your directory here
Power down your Atrix device
Hold the power button and the downward volume button until you see “Fastboot”
Let go of the buttons and press the upward volume button once
You will now see “Starting Fastboot protocol support”
Plug your device into a USB port in the back slot of your computer
Front slots sometimes do not have enough power to stay connected to the device.
Type the following command:
fastboot oem unlock
You will now receive a warning along with a unique device ID
Type the following commands using your unique device ID in place of the ####:
fastboot oem unlock ####
fastboot reboot
Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
Click to expand...
Click to collapse
2. CWM
CWM Download
how to install:
Windows:
unzip recovery-en-goapk.zip to D:\
open a CMD in windows.
fastboot flash recovery D:\recovery-en-goapk.img
Linux:
unzip recovery-en-goapk.zip to you home
mot-fastboot flash recovery ~/recovery-en-goapk.img
mot-fastboot reboot
3. Install Cyanogenmod
Download:
Cyanogenmod *REQUIRED*
GOOGLE Applications *Install if you want Market, Gmail, etc*
Restart into CWM
Wipe Dalvik
Wipe cache
factory/data reset
flash pre-beta.zip
wipe Dalvik
wipe cache
factory data/reset
reboot
IT COULD TAKE A LONG TIME TO BOOT, JUST WAIT UP TO AN HOUR
*Cyanogenmod*
Thanks to OP's and posters in the following locations:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
http://forum.xda-developers.com/showthread.php?t=1136261
http://forum.xda-developers.com/showthread.php?t=1138541
http://forum.xda-developers.com/showthread.php?t=1206026
was this honestly needed?
You forgot the part where you have to flash pudding, which will softbrick your phone temporarily. This happens to all phones on stock GB when attempting to unlock them.
RSD flash the pudding sbf
phone will error with 0x1000 No OS found
choose fastboot
enter the documented unlock commands
firefox3 said:
was this honestly needed?
Click to expand...
Click to collapse
If it stops ONE person from asking for a guide on how to do this... it was needed.
how to install:
Windows:
unzip recovery-en-goapk.zip to D:\
open a CMD in windows.
fastboot flash recovery D:\recovery-en-goapk.img
Click to expand...
Click to collapse
This section has always bothered me because it can be confusing. Instead of referencing D:\ at all simply telling users to extract the img to the folder where they've installed the fastboot package would be clearer. Also at least some mention should be made of the fact that there is now a second CWM option running around in the dev forum which works with rom manager. It can be installed in exactly the same way as Tenfar's but to get it to work with rom manager you need to install the generic rom manager CWM through rom manager first, and then install the CWM version available in the dev forum.
sjbayer3 said:
How can I Backup text messages/missed calls etc to cyanogen?
Click to expand...
Click to collapse
search for mybackup root in the market. its free. =]
Congrats on being one of the few newbies who know how to read instructions.
It does help and I used rom manager to reinstall the updated version of cmr-at&t cmr- 4.0.1.4.atrix2 it has an sd.ext to view files in external sd and an. Asks if you want to delete s-ext during data factory reset just say no or you will ! fubar if that's were your .zip files are
Sent from outerspace from an unlocked alienv3 overclocked /faux123 kernel
Thanksyou. for all the great work !!!!!!!!
@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@
hey anything please i wiped everything and installed zip"rom" from sd and installed secussful and then i clicked reboot and it just stays on the motorola screen with unlocked in the corner and is stuck there what am i not doing or doing wrong its rooted and unlocked
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
clod007 said:
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
Click to expand...
Click to collapse
i made a back up with titanium and android recovery....
i pulled the battery installed it 2 or 3 times and same thing
what exactly do i type in my cmd prompt on fastboot
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
clod007 said:
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
Click to expand...
Click to collapse
i dont know how to reinstall it but i made back ups of everything
Enter in Android recovery mod
Backup
Chose restore
Atrix - "CM7"
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
android-DEP said:
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
Click to expand...
Click to collapse
ok it rebooted and went off the screen now its in a boot loop and flashes the motorola sign then shuts down and keeps going
ok, so the issue was partly the cache not being wiped prior the rom being installed and something went wrong with the installation of the kernel. That happens if the boot.img didnt properly extract and write to partition or its just incompatible with the rom\device.
Visit faux123's thread with kernels for ATT froyo, GB, CM7 & CM9
download the kernel that's compatible for your rom(froyo, gb, cm7 or cm9). Once you download the zip, go in there and pull out the "boot.img" file and put it into the same folder you have fastboot.exe in and boot into fastboot again.
quickly check connectivity with "fastboot devices" to verify and if that checks out, use this command.
"fastboot flash boot boot.img"
it takes like 3 seconds or something to complete so its an easy fix, after its done just do the "fastboot reboot" command.
i had this same exact issue last week plus my recovery was being erased along with this problem so i keep boot.img & recovery.img just sitting inside the fastboot folder just in case
atrix reboot project - it has every single file thats for the atrix and copies of systems, roms, tools, recovery files, mods, tweaks
Try this:
Pull battery
Replace battery while holding volume down until you see fastboot
Tap volume down to until you see android recovery, then press volume up to enter recovery
First try wiping cache/dalvik, if that doesn't work restore nandroid backup, if that doesn't work reflash rom
Hello everyone!
I tried to restore the stock image using Nexus 4 Tool Kit (both the original one and the Wug's one), and everytime I tried, the script stucked at "writing system".
I manually flashed system and userdata images with Wug's tool kit and everything went well but I only have 5Gb memory instead of 16.
Does anyone know why?
Try this http://forum.xda-developers.com/showthread.php?t=2033692
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Sent from my Nexus 4
OP...
In future, don't use a toolkit. Do it yourself
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
When going into recovery the warning sign is the splash screen for stock recovery. This likely means that you have not yet flashed a custom recovery yet, which is necessary to flash CM. First read this guide to unlock the bootloader (if you havent already), then flash a custom recovery (preferably TWRP). After you have installed the recovery, download CM as well as the latest gapps package and place them somewhere on your internal sd. Boot into recovery and go to the wipe menu, then swipe to factory reset. Finally flash the rom and gapps, and then reboot.
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I am using the .bat file... I've also tried the toolkit, and both appear to use the same basic procedure, and they stop at "writing system" no matter what.
Does anyone happen to know how the .bat file and toolkit get access to the phone? ...because I can't see it in adb (I'm guessing it's because I can't boot the phone.) However I can get into fastboot and recovery modes on the device.
I cannot get the device (nexus 4) to boot or connect in ADB mode to my computer. What can I do??
UPDATE - PROBLEM FIXED
I un-bricked my phone
SOLUTION this is what worked for me, your mileage may vary
Install ADB drivers, etc. from Android SDK (google how to do this)
Flash custom recovery (can be done easily with Nexus 4 Toolkit here on XDA) - I used TWRP Touch Recovery.
Once that is done, shut the phone off completely and boot into Fastboot (hold volume down and power)
Use volume keys to select Recovery Mode, then hit Power
In recovery mode:
Wipe > Advanced Wipe > Check off the box beside "System" > Swipe to Wipe
Go back to recovery mode main screen:
Wipe > Format Data > Follow the instructions on the screen
I think this step is what did it. When having problems with partitions, just format everything and start over
Now we should be able to write to the System partition, meaning you can flash a ROM and get your phone to boot again.
Follow the rest of these instructions to quickly flash the stock Android image from Google onto your phone.
Go back to recovery mode main screen, once again:
Reboot > Bootloader > Follow any additional instructions it gives you
Download Google Nexus 4 factory stock image "occam" (Google it)
When that is downloaded, open it with 7zip. Inside there are some files, one of which is called image-occam-jdq39.zip. Inside are some images - unzip those as well. You'll need the system.img file in a bit...
Using Wug's Nexus Root Toolkit (Google it - install it on your Windows PC):
Open the program
Launch advanced utilities
Hit the System button to permanently flash to System partition. Hit "ok" on the window that pops up.
Find the system.img file I mentioned back on step 10 and select that, when prompted, and open it.
If all went well, your device will now boot into the stock Android ROM.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Soundchasr said:
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Click to expand...
Click to collapse
The system takes awhile to write, how long have you guys wait before you say its "stuck"?
Sent from my Nexus 4 using Tapatalk 4 Beta
About 20-25 minutes.
Yea, that's way too long.
Sent from my Nexus 4 using Tapatalk 4 Beta
Stuck, but working
I was flashing the 4.3 image using the included flash-all.bat (but I edited it to remove -w parameter so that it wouldn't wipe my data).
In the 'writing system' step, the command window got stuck. In the phone screen, at the bottom, it said 'writing' for a while and then that also went away. I waited for ~40 min, and still the command window was at 'writing system', so I closed the command window, and booted my phone by selecting start from the bootloader.
And voila! It worked. Booted in under a minute, the flash was a success, I got JB 4.3 without losing any of my data.
Lost my root and custom recovery though. But I knew that would happen. Gonna try SuperSu for 4.3 now, after flashing TWRP.
Had the same problem, tried everything! With my tiny powers, but it kept stucking at "writing system" . I thought that I bricked the device, so for the last hope, I installed WugFresh's Nexus Toolkit and did a Fast Stock + unroot. It Installed everything flawlessly! I'm gonna donate to that guy! He's a godsend savior.
This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Sick man, gonna try this when i get home
I am running on 33R will this work ???
Or connect to PC.. Adb backup, root, then adb restore
Cool write-up! I re-wrote the guide for use over on the OnePlus forums: https://forums.oneplus.net/threads/...ck-the-bootloader-without-losing-data.103642/
ifg said:
This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Click to expand...
Click to collapse
Big thanks for this guide. You saved my life. And thanks also to developers for this MOD :good:
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
Dibbyo123 said:
I am running on 33R will this work ???
Click to expand...
Click to collapse
Be sure to read the steps.
philicibine said:
Or connect to PC.. Adb backup, root, then adb restore
Click to expand...
Click to collapse
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
erad1 said:
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
Click to expand...
Click to collapse
i used the steps posted here. although they needed adapting for the one.
the bones of it is there though, so if you understand it, its easy to do.
Kind of went a different route but used this as a base and got it done. It was tricky but I'm unlocked, rooted, stock recovery and got most of my data back! Thanks for heads up philicibine and OP.
someone running on 33R succeeded with this MOD ???
Medosofts said:
someone running on 33R succeeded with this MOD ???
Click to expand...
Click to collapse
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
ralphwiggum1 said:
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
Click to expand...
Click to collapse
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Hilmesh said:
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Click to expand...
Click to collapse
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
ralphwiggum1 said:
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
Click to expand...
Click to collapse
Hello ,
I am on 33 R and downloading the flash-able zip from the thread you gave. The rest of items i have already downloaded (Please see attachment). Request you to please confirm that once my 33R download is complete am i ready to proceed??? (I also have the Complete SDK Package with me)
Also can you please list me the procedure step by step. This is my very first time doing it this way as i am used to rooting my S2 and that is a totally different method using ODIN.
Hope to receive your positive reply.
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Hilmesh said:
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Click to expand...
Click to collapse
Good job!
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded.
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Worked like a charm. Thanks!
Yeah, I really wish I found this post before I wiped my OPO, and lost another day reinstalling and configuring apps.
Hilmesh said:
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded.
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Click to expand...
Click to collapse
Excellent...well done and will help many!