Related
hi, I have unlocked bl, cherryblur and tenfars recovery. when I try to make a factory reset. it restarts into recovery shows an exclamation sign and nothing happens. also if I try try 3 wipes from recovery when I restart all info still there!
Sent from my MB860
diegof18 said:
hi, I have unlocked bl, cherryblur and tenfars recovery. when I try to make a factory reset. it restarts into recovery shows an exclamation sign and nothing happens. also if I try try 3 wipes from recovery when I restart all info still there!
Sent from my MB860
Click to expand...
Click to collapse
How are you wiping from recovery if you're saying you can't get into recovery?
Also, doesn't sound like you have tenfars recovery if you're getting the exclamation sign which sounds like the stock recovery instead.
whats the reason for the reset? if anything you can just reflash the rom if somethings messed up or download another one. there are also 2.3.4, 4.5.9.1 OTA roms for unlocked bl's. just look around in here and you fill find it.
Boot into fastboot and fastboot -w to wipe.
when I reflash the rom all my previous info still there so I can't add my google account cause it's already there. the problem that motoblur it's also there but not showing, also it enters tenfars and after the exclamation I can only see some chinese letters. I'll try with fastboot
Sent from my MB860
jjeffries0423 said:
whats the reason for the reset? if anything you can just reflash the rom if somethings messed up or download another one. there are also 2.3.4, 4.5.9.1 OTA roms for unlocked bl's. just look around in here and you fill find it.
Click to expand...
Click to collapse
Should always wipe when flashing a ROM.
Wipe Dalvik, cache, and factory reset/data, or fastboot -w, prior to flashing. Many people also repeat after flashing.
diegof18 said:
when I reflash the rom all my previous info still there so I can't add my google account cause it's already there. the problem that motoblur it's also there but not showing, also it enters tenfars and after the exclamation I can only see some chinese letters. I'll try with fastboot
Sent from my MB860
Click to expand...
Click to collapse
Some of the ROM's perform a wipe for you during the flash process. You could always try flashing one of those also. Just wipe Dalvik and cache before flashing.
CaelanT said:
Should always wipe when flashing a ROM.
Wipe Dalvik, cache, and factory reset/data, or fastboot -w, prior to flashing. Many people also repeat after flashing.
Click to expand...
Click to collapse
Oops forgot to post that part but i did wipe everything in cwm ty for the catch calient
Fastboot worked like a charm. My got full reset and I was able to install aliens #2 in my int'l phone with faux123 kernel. Thanks a lot
Sent from my MB860 using XDA App
I did a factory reset on 2.3.4 official after installing alien rom and theme, and now I cannot go into settings. The icon doesn't exist in the app tray. Now I can't connect to the internet or enable debug. Also it says that I have no service. And when I try to go in android recovery and tap on the bottom right corner nothing happens. Could someone tell me what I can do please? Thank you.
sounds like a bad install... did you do a full wipe beforehand?
do a full wipe, wipe cache, wipe dalvik cache, then reinstall.
note full wipe is not just a factory reset from the OS you need to wipe from tenfar's clockwork recovery, or connect via USB and run moto-fastboot -w
I didn't because in the install instructions for the rom it didn't say I had to, and I didn't know I was supposed to. (i'm a noob).
While on a homescreen, hit the menu button, and then "settings" to get in if the icon is missing.
DK
I did that then the launcher force closes and restarts
well now you know
before installing any ROM you need to (to ensure a clean start)
go into clock recovery, wipe (alternatively, connect via USB, make sure you have correct drivers I presume so if you've been flashing and unlocking BL, go to moto-fastboot directory, start command line, and do moto-fastboot.exe -w)
then in clockwork recovery, wipe cache
then in clockwork recovery, advanced - wipe dalvik cache\
THEN flash away
obviously this wipes everything so backup your info/apps beforehand
I'll remember that for the next time I install a rom, even though when I had 4.1.83 and installed greyblur I never wiped anything, it wiped everything when I installed the rom. Now I need to know what are my options... Could I flash 4.5.91, or will it brick my phone? or is there another way to fix this?
I flashed sbf 4.5.91 and it worked. Thanks for the advice.
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
omni_angel7 said:
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Click to expand...
Click to collapse
LOL, post usually note that the initial boot after flash is ridiculously long..... but I definitely waited >10 mins, almost an hour at longest on the Alien 3 beta flash just now, then I pulled batt and Fruit caked to 2.3.4.
(worried I might turn the soft-brick to a Hard-Brick if the battery died)
bamastang said:
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
Click to expand...
Click to collapse
Yup still have the unlocked text...... :-/ FRUSTRATING
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
defnow said:
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
Click to expand...
Click to collapse
lol, it seems like no-one who has had this problem has posted till now? xD
But did you finally get into the launcher? or a complete Boot animation???
do you using correct kernel?
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Jean-DrEaD said:
do you using correct kernel?
Click to expand...
Click to collapse
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Jonestown said:
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Click to expand...
Click to collapse
I used the pudding/fastboot oem unlock method for x64 windows, the application put together should do the exact same thing but without the user needing to do the actual steps individually, but any ways will give it a go
weaz_da_smel said:
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Click to expand...
Click to collapse
flash kernel after flash the rom because that... try FR an ATT kernels...
weaz_da_smel said:
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Click to expand...
Click to collapse
start from scratch...go back to stock via RSD...
DO NOT DO THIS
if the fuse is blown YOU WILL BRICK
I would fruitcake back to 1.83 then flash to the rom you want, since its voda I would try a working international rom first.
DO NOT GO BACK VIA RSD YOU MIGHT HARD BRICK.
wipe all data in fastboot -> flash stock 2.3.4 via fastboot -> wipe all data again
Not trying to hi-jack the thread but I have the exact same problem so I thought I'd post here and give a detailed description of what I've done instead of creating another thread just like this one.
I unlocked the bootloader using the latest version of pudding
Then I downloaded fastboot and installed CWM
I downloaded the ROM of my choice meaning Alien 3 and the theme, and later when that didn't work Redpill 3. Also for the record I've tried installing with Alien 3 standalone and wait for boot up, and with both - neither worked and Redpill produces the same result.
Anyway back to the process
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
The only way to get unstuck is to reflash with 183-sb-release.zip which is the fruitcake release I think. I got this from someone on a forum describing a similar problem for which this was the solution. However afterwards he was able to reinstall a custom rom without problems, while my problem remains.
*Edit - I have an AT&T phone
diviluxfloss said:
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
Click to expand...
Click to collapse
To double check -> Are you using latest unlocked CWM from xda or rom managers one?
Also to double check -> you did Wipe data / Factory reset as well?
You should do all three Wipe options before and after flashing the rom -> wipe cache, wipe data / factory reset, wipe davik.
After that reboot and give it a couple of minutes to boot.
If that doesn't work, do a battery pull and try booting again.
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
diviluxfloss said:
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
Click to expand...
Click to collapse
Alright, then the second thing I would try is flashing one of the custom ROMs via fastboot:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
p.s. and if you don't have the latest radio,-
moto-fastboot flash radio radio.img
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
diviluxfloss said:
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
Click to expand...
Click to collapse
The only truly dangerous method of flashing is SBF (RSDlite). CWM and fastboot are safe.
If you unlocked the bootloader youserlf, you already know what fastboot looks like. Often, fastboot helps where CWM fails.
Before using fastboot, make sure you have phone drivers installed, also make sure you have "moto-fastboot" version and not "fastboot", as the latter can't flash large files, e.g. - system.img.
Phone drivers for Windows x64 can be downloaded here (though your probably have them already if you unlocked the BL) -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Download moto-fastboot for your operating system here (if you don't have it already, obviously) -
http://forum.xda-developers.com/showthread.php?t=1138092
"Radio" is software that handles cellular connection, mobile data, etc.
I've read that there could be a boot problem if wrong radio is used.
Besides, the latest 2.3.4 radio includes many bug fixes and better mobile data speeds.
You can check if you have the latest one under "About Phone" -> "Baseband version". Latest one for ATT is N_01.77.30P.
It can be downloaded here - http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
(The archive contains all stock 2.3.4 partitions, but you can simply extract radio.img and flash it separately via fastboot)
Cheers.
Great
I'll try flashing the radio and then the files as mentioned in your previous post. A problem though is that when I look through the zip files I only find a boot.img file for the custom rom.
Where is the system.img file located and if I simply install these through moto-fastboot (thanks for the heads up btw as I only had fastboot) what happens to the smaller files located on the zip which won't be associated to the img files?
*Edit I compared these to the fruitcake zip and in the custom roms I have a folder called system which I believe contains all the info while the fruitcake files have an img. I'm guessing not compatible? Or can I simply make an img file with the system folder and flash thusly?
Hello there,
I've been using my Atrix (unlocked bootloader, Orange Stock 2.3.4) for over 2 weeks and yesterday, suddenly, the Wifi stopped. I can't activate the Wifi [in other words, it is not a network issue], it simply doesn't enable. When I try to enable the wifi, it takes like 20 secs and after that I recieve a "Error" msg. Just it.
Sometimes, the Atrix reboots while trying to enable the wifi.
Things I did so far:
- Wipe data (factory reset via phone and via android recovery)
- Wipe cache
- Reflashed Orange Stock 2.3.4 ROM
- Flashed another ROM (nCrust).
*edit: - Flashed another ROM (Ninja 0.4)
*edit: - Changed the kernel from INTL-MBR-d00-GB-Kernel-0.1.2-ext4-sv to INTL-MBR-d00-original-kernel
*edit: - Changed the kernel back to INTL-MBR-d00-GB-Kernel-0.1.2-ext4-sv
I've been looking around for problems like mine and a found a couple dead topics with no decisive answer.
Any suggestions? Could be a hardware failure?
I'm just asking because I want to use the warranty as my last resource.
Thanks in advance
---
Atrix International
Kernel: INTL-MBR-d00-original-kernel
---
Post that I checked, with no success:
http://forum.xda-developers.com/showthread.php?t=1180494&highlight=wifi+error
http://forum.xda-developers.com/showthread.php?t=1182852&highlight=wifi+error
http://forum.xda-developers.com/showthread.php?t=1134939&highlight=wifi+error
Try forgetting the network on your phone and renaming your wifi and connect to it.
Sounds weird, but it worked for me.
Sent from my MB860 using XDA Premium App
You need to do a full wipe and then flash a ROM.
Beamed from WinBorg 4G via XDA Premium
CaelanT said:
You need to do a full wipe and then flash a ROM.
Beamed from WinBorg 4G via XDA Premium
Click to expand...
Click to collapse
Thanks for the answer!
Full wipe? How can that be done? What's the difference between "Wipe data/factory reset" from the Android Recovery and the full wipe?
Thanks again
Mine did this before the bootloader was unlocked.. is your bluetooth working? I did a few sbf attempts and ended up rma ing mine
Sent from my MB860 using XDA App
nineismine said:
Mine did this before the bootloader was unlocked.. is your bluetooth working? I did a few sbf attempts and ended up rma ing mine
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah, my Bluetooth is working.
I'm trying to change the kernel.
I got this problem after i restored my nandroid backup with other kernel than the present one.
Anyway , i just did full wipe and installed the rom again, now everything is ok.
ofek said:
I got this problem after i restored my nandroid backup with other kernel than the present one.
Anyway , i just did full wipe and installed the rom again, now everything is ok.
Click to expand...
Click to collapse
What kernel are u using? How did you do a full wipe? I read all the "[Updated 8-2-2011] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs" topic without finding how a full wipe can be done
Faux123 OC 1.1GHZ kernel.
Get into recovery and flash cache, dalvik-cache and factory\data wipe.
Its written in that guide under ROMs & Kernels section:
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
Click to expand...
Click to collapse
I did exactly as you say and nothing changed.
This is what I did after:
fastboot -w (to wipe again)
moto-fastboot flash system ORFR234-system.img (Orange stock 2.3.4)
moto-fastboot flash boot ORFR234-tegrapart-d00100.boot.img
fastboot reboot
After the reboot, I installed the kernel "INTL-MBR-d00-GB-Kernel-0.1.2-ext4-sv" again, from the Android Recovery menu.
And still nothing... No wifi + auto-reboots ;/
Wait, the MBR-d00 is " [<{ Tegrapart=d00 Compatible with ATT U4_5.9.1 ROM}>] ", for ATT, not for Orange system.
Don't you need to install the other kernel ?
This one: "[<{ Tegrapart=1100 Compatible with Orange 4_5.2.1A ROM}>] " ???
Just flash the original kernel to see if the Wifi is working ok.
Sorry if i wrong or missing something, i got AT&T Atrix device, im not an international user.
When I type (su) cat /proc/cmdline I get this result "tegrapart=mbr:d00:100:800,kpanic:2100:400:800 ...", that's why I need a kernel d00 compatible, I think.
And thanks again for helping me out, Ofek
OK you doing fine.
After you fastboot flash the system and the boot img files, and reboots, is the WIFI working without the error? and no auto-reboots?
Nope ;/
Wifi still not working. I still can't activate it
Did you try to update the radio?
I don't think so... I'll look into it
zuperzuze said:
Thanks for the answer!
Full wipe? How can that be done? What's the difference between "Wipe data/factory reset" from the Android Recovery and the full wipe?
Thanks again
Click to expand...
Click to collapse
wipe data/factory reset only clears user data. to do a full wipe you need to do that, clear the cache, and wipe system but then you need to have a unlocked BL so you can flash a rom image right away.
I think I got the answer... It's the kernel, I believe.
When I use a terminal emulator on my device and use the command #modprobe -v /system/lib/dhd.ko it says that it couldn't load the file.
Still looking into it.
Changed to mbr_d00 GB Kernel Version 0.1.3 and still no wifi.
Trying the mbr_d00 original Kernel Version
No success so far ;/
This sounds to me like a radio problem. Just my two cents, I would look for the answer in flashing the stock radio.
Sent from my MB860 using XDA Premium App
I've recently flash Aura ROM, and it was successful. Now I want to try the Neutrino build. Do I have to flash back to my Stock Gingerbread 4.5.91.img and then flash Neutrino?
Or do I simply go ahead and flash Neutrino with these steps.
-boot to recovery
-wipe dalvik&wipe cache
-factor reset/data
-flash ROM in recovery
-wipe dalvik&wipe cache again
-reboot
Sadly I did not do a backup on CWM(Using Rom Racer's).
You don't uninstall a rom. You wipe and flash another.
Each rom's thread will give the wiping instructions that work best; I've only stuck with blur roms and have had luck with -- AFTER backing up -- booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Others recommend first wiping everything separately using fastboot (and someone will likely chime in here). If you want Neutrino, head over there and see what wipe procedures users have found the most success with.
sheeparecurious said:
You don't uninstall a rom. You wipe and flash another.
Each rom's thread will give the wiping instructions that work best; I've only stuck with blur roms and have had luck with -- AFTER backing up -- booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Others recommend first wiping everything separately using fastboot (and someone will likely chime in here). If you want Neutrino, head over there and see what wipe procedures users have found the most success with.
Click to expand...
Click to collapse
After all this time! I've always thought you'd have to go back to your stock ROM. Thanks a bunch sheeparecurious! Neurtion seems to want you to wipe everything.
Do I need to wipe dalvik and cache everytime I flash a simple mod or add on?
Depends on the rom. Does the OP in the Neutrino thread say anything specific?
I've been able to flash mods without clearing any caches. I've seen two themes "not play nicely" when flashing one after another, and others were fine to go from theme to theme.
"Wiping data may not be necessary with every update, but it's best to flash clean. However, if you regularly flash the updates, you'll most likely need to wipe data at some stage anyway."
It says to wipe when you flash updates. Does he mean updates to Neutrion updates?
Here's thread link. If you'd like to look for yourself. http://forum.xda-developers.com/showthread.php?t=1398819
Thanks in advanced. I'm headed to bed now. Very pleased as to how things went today on my phone.
Yeah, he probably means "updates to neutrino." I'd say if you successfully flashed the rom and any additional mods you wanted, and the phone is working well, make a nandroid backup so you have a good restore point.
Whenever it comes around, try the next update without wiping - either it'll work fine & life is great, or something will be screwy & you'll need to wipe clean and flash from a fresh state anyway (or restore your backup state).
Sent from my MB860 using XDA
sheeparecurious said:
booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Click to expand...
Click to collapse
fastboot -w does the same as wiping data and cache in recovery.
---------------------------------------------------------------------------
For the best results, when you want to flash a new ROM you should always perform a full wipe in fastboot per the following to make sure you will avoid any unforeseen complications:
reboot to recovery
wipe Dalvik
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
If you are updating an exisiting ROM, then you would normally just reboot to recovery, wipe Dalvik and cache, then flash the update unless the dev has instructed otherwise in the ROM's thread.
You should ALWAYS do a nandroid backup of your current ROM through recovery prior to wiping and flashing anything. Much easier to restore to a previous state than have to set-up completely from scratch again if something goes wrong.
See? Told ya someone would chime in.
and I knew "fastboot -w" did the same data/cache wipe as in CWM, something something placebo effect can never be too sure. Wouldn't feel right if I didn't do it anyway.
Now, I never erased the webtop when I started flashing roms -- I only did the 2.3.6 webtop fruitcake because it was an update compared to my original one. Granted, I stuck with blur roms but it didn't seem to cause any issues. I assume if I were to switch to a CM-based rom, it could cause glitches if I don't erase the webtop partition?
You guys are awesome thanks! I copied down the procedure you recommended CaelanT. This will help me a ton.
Sent from my MB860 using XDA
Thanks for that CaelanT thats also useful to know, I have only just entered the world of different roms.
I always do a CWM backup and then a factory reset, wipe the dalvik cache and then flash the new ROM and any add-ons or kernels. Don't forget to wipe your battery stats/calibrate your battery. (I turn off my phone, charge it to 100%, wait about 15 minutes to be sure and boot into recovery to wipe the battery stats)
Sent from my MB860 using XDA App