So I've been running my Atrix on several roms, radios, kernels etc since getting the device in late July. Was running cm7 last week, then changed to darkside 2.1 to get blur amongst others back. Now on Saturday I upgraded to darkside 2.2, following all the usual procedures of clearing cache/wipe data/dalvik and so on in CWM (RomRacers).
Since then I've had no luck in getting a connection on ANY rom or ANY radio. All the correct info is there in the apn settings, everything enabled in blur roms under battery and data settings, so I'm stuck for ideas.
I've just flashed back to my stock sbf (T-mobile uk, Froyo 2.2.2) and still have the same problem. Any thoughts on this? Hardware issue maybe?
All thoughts are appreciated, cheers guys.
fastboot erase system
fastboot erase user data *or just data if user data doesn't work for you*
fastboot erase webtop
fastboot erase boot *this is important*
fastboot erase cache
fastboot reboot
Do ALL of that, and then re-flash SBF.
jgc121 said:
fastboot erase system
fastboot erase user data *or just data if user data doesn't work for you*
fastboot erase webtop
fastboot erase boot *this is important*
fastboot erase cache
fastboot reboot
Do ALL of that, and then re-flash SBF.
Click to expand...
Click to collapse
I'll give it a try although I always do the the same procedure in CWM. This is a more thorough erase process though I take it?
*Edit* Tried doing so in fastboot - cache, user data and reboot work - boot, webtop and system commands do not.
*Edit Edit* I "Re-Unlocked" the bootloader in RSD using the IHOP-intl-fix.sbf and can now perform said commands in fastboot. Will report back.
Got everything erased usuing fastboot and reflashed the sbf, still a no go. Only thing I can think of is something hardware related? I thought it might be the sim but have signal and can make calls/texts.
Looks like a trip to the T-Mobile store is in order to try get the handset changed, luckily know a member of staff so hopefully no questions asked!
Related
Hi,
I seem to be bricked more than usual. Don't ask me how, I was doing something, rebooted and now I can't get into early usb mode or android recovery. I have no clue what half the other boot options are.
I can use rsd lite to flash sbfs, no problem. Phone is stuck at initial m, no animation. I suspect it is something dumb like the internal memory having an error, something is causing the linux bit to loop. Not reboot, not crash, just hang there.
i can use fastboot, but since it uses names for partitions, I don't know how to flash exact partitions or know what they all are, I have system, webtop, boot, recovery, cdrom, other things like pds are not allowed.
I have a dev usb cable made up, can do everything without a battery, which is cool, have an extra battery and external battery charger. Obviously, I have all the partitions available as backups.
Somehow, I need to get the partitions restored, and internal memory formatted perhaps.
Any ideas? Short of trying to send it back?
Thanks.
for my little experience a full wiped pds let you run the os...and you know better than me which are the others partitions not overwritten by a flash with full sbf
I had a backup of my pds, but no way to flash it or erase it.
Thanks!
in milestone i was having your problem when changing builds (froyo,ginger, eclair) via update.zip without the correct boot.img
but if you already flashed the sbf...
have you tried flashing boot and recovery partition, and then entering it? maybe you regain adb access
I think I am getting blocked before I even get to recovery, early usb, android recovery, etc.
I have fastboot access and nvflash, so in other words I have fastboot.
I can flash boot, recovery, system, webtop, cdt, cdrom, preinstall, but not pds, and I can't erase boot etc.
Thanks.
...i searched for nvram in android:
maybe it's useful (from droid incredible dev area)
dknlght said:
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
www megaupload . com /?d=RCZBCDDA
Click to expand...
Click to collapse
hope it helps somehow
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
NFHimself said:
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
Click to expand...
Click to collapse
i did not say that file was for you.
but if you can flash boot recovery system and your system won't boot it's something else in the bootstrap process (excluding hardware failures, you could not access fastboot then).
as i read you can flash (already flashed?) almost every partition except pds (useless for your needs) and nv.
i reported a case of other guys experiencing your same problem, with i guess the same cause.
i give you an idea, unfortunately i'm not a dev to give you solution
cheers
So i became a hacker (Obvoiusly) and ive had some issues but i always find a way to fix them and im glad i became a hacker ! <3 but alas i have problems once more :'/. See i was using cm7 BATF2 Or something along those lines, and ive had multiple problems but kept it due to lazyness of backing up and restoring my phone. but now it seems my phone keeps bootlooping unless i flash a new rom, so i flashed cm9 0.3.1. Sure i lost everything but i need a phone and quickly </3 :/.
But there seems to be a problem.....
Whenever i try to use cwm recovery (Button only 5.0.2.8 i believe) i cant factory restore because it cant reach a certain part of android (If im right its android secure.) and skips the format.
So i have literally no space on my phone.
Can someone help me with this and maybe some other issues??
Thanks in advance
-heyhey24 <3
This may work for you:
reboot to recovery
wipe dalvik
wipe cache
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
Hello Friends,
I have Moto Atrix 4G with Alien#4 Android version installed on it with following details.
System Version: 4.5.91.MB860.ATT.en.US
Android version: 2.3.4
Kernel version: [email protected]#2
Build number: Alien#4
Click to expand...
Click to collapse
I tried flashing CM7 but it does not work
http://forum.xda-developers.com/showthread.php?t=1463386
http://forum.xda-developers.com/showthread.php?t=1398819
Phone gets stuck on boot screen
When i again install Alien#4 from recovery it works fine.
kindly help to sort out this problem.
thanks in advance
Pull your battery out on boot logo stuck just for 1-2 sec and put it in.
always works for me
Also,
1. Are you using the latest Romracer's recovery?
2. Did you wipe properly before and after the installation?
How long are you letting your phone sit and reboot for after flashing CM7?
You may just be not letting it sit long enough. It can take a while on first boot.
LOCKDOC_UA said:
Pull your battery out on boot logo stuck just for 1-2 sec and put it in.
always works for me
Click to expand...
Click to collapse
Tried It Does Not Work
xploited said:
Also,
1. Are you using the latest Romracer's recovery?
2. Did you wipe properly before and after the installation?
Click to expand...
Click to collapse
Yes Using Romracers Recovery
Yep Wiped All Factory, Cache & Dalvlink Still No Go
CaelanT said:
How long are you letting your phone sit and reboot for after flashing CM7?
You may just be not letting it sit long enough. It can take a while on first boot.
Click to expand...
Click to collapse
Must Be More Than 15 Minutes.... Will Try Flasing Agin Tomm And Post back
Try a full fastboot wipe:
reboot to recovery
wipe dalvik
wipe cache
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
Helping?
yes as said above try pulling battery i had the same problem with mine and that helped also i have read on the dev forums about this and it may help be sure you have the newest rom racers and recovery, try waiting for a while after first boot it is a long one much longer than other roms i have tried, be sure to factory reset, wipe cache, go to advanced and delete the cache in there, and do a battery stat wipe (for the heck of it). Install the rom and let it load if it does get stuck just pull battery and try again it usually loads on the 2nd try on mine with some other roms as well.
Also you should try the aura roms and cm9 (although cm9 currently isnt playing music on my phone) it is based off of Ice Cream Sandwich)
CaelanT said:
Try a full fastboot wipe:
reboot to recovery
wipe dalvik
wipe cache
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
Click to expand...
Click to collapse
Is It necessary to erase webtop too?,
What If In Case I Want To Go Back To The Previous Rom Or The Stock Rom
CaelanT said:
Try a full fastboot wipe:
reboot to recovery
wipe dalvik
wipe cache
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
Click to expand...
Click to collapse
Tried Your Method Still Stuck At Start Screen..
Any Idea?
Wipe everything again, then try installing the ROM a few times in a row. I had the same problem with the joker's CM9 ROM.
Inspiredwire said:
Wipe everything again, then try installing the ROM a few times in a row. I had the same problem with the joker's CM9 ROM.
Click to expand...
Click to collapse
is your bootloader unlocked?
pienne said:
is your bootloader unlocked?
Click to expand...
Click to collapse
Yep, I'm not having any problems.
I was just explaining to the OP that they may need to flash the ROM twice in a row for it to take. I had to do it with jokers CM9 ROM in order for it to work. Joker just posted about it last night.
Though, if you're asking the OP, Ken's Alien ROM didn't require an unlocked bootloader so that may be the problem.
I am having issues with my ear speaker. For some reason when I flash a rom it works for 5 minutes then cuts out. I really do not want to use my loudspeaker to answer calls. It started after I flashed Neutrino 2.5p2, then I flashed CM7.2 CR and it keeps doing the same thing. Sometimes when I turn the speaker on and off it kicks on the ear speaker. Anyone have this issue before, I am prepared to replace the ear speaker, but will be disappointed if it was a software issue not a hardware issue.
I have already:
Factory Reset
Restored Roms
Cleared Cache and Div Cache
I think it might have to do with programming. The reason why is because the speaker does work for a few minutes after factory reset and rom restore. And when I turn speaker on and off it sometimes triggers the speaker to work.
Please Help me!!!!!!!
Try a full wipe and flashing again:
reboot to recovery
wipe dalvik
wipe cache
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
If you are unsure about fastboot, there are several threads which will help you if you do a search in the Atrix forums.
CaelanT said:
Try a full wipe and flashing again:
reboot to recovery
wipe dalvik
wipe cache
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
If you are unsure about fastboot, there are several threads which will help you if you do a search in the Atrix forums.
Click to expand...
Click to collapse
Fastboot has to be done through command prompt right? Do you have a link to erasing all the fastboot.
The problem is internal going to try to repair first. Then replacement
Sent from my MB860 using xda premium
Android The Greek said:
The problem is internal going to try to repair first. Then replacement
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Have you had any luck with this?
I had the same issue for the past few days and I assumed it was due to my ear speaker hardware. I ordered a new cable with those parts on it and replaced it this morning. $16 later, NO LUCK! GRRRR... So apparently it is a software problem at some level.
On the + side, my new front facing camera takes much clearer pictures now! haha.. (The camera was part of the same ribbon cable)
I've been having a few issues with the root and rom as time has went on. First my fingerprint reader went, then I would have random crashing and shutdowns. Those errors began to get more frequent, and now the internal memory card decided it will wipe itself clean. So I'm done with what ever I had installed. According to the phone that was on April 4th.
I've read some confusing stuff on here about rooting and unrooting, and none of the information is the same. I imagine thats because of all the updates the phone has gone through.
I would like to install cm7 or cm9 since it seems much more stable.
Any help at all to even simply unroot the phone would be appreciated. I need full functionality back.
Atrix 4g
android ver. is 2.2.1
kernel ver is 2.6.32.9
Build number is 1.5.7
Rom: GingerBlur
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
terminator1983 said:
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
Click to expand...
Click to collapse
Actually, if you want the cleanest and least likely to cause problems method, you should do a full fastboot wipe prior to installing any new ROM. Just wiping data, cache, and dalvik does not give you a completely clean wipe and prep properly for the new ROM.
If you are updating a ROM from a previous release, you are usually OK with just wiping Dalvik and cache. The dev will normally state what to do in their thread.
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
21q said:
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
Click to expand...
Click to collapse
We couldn't unlock the bootloader a year ago. Was around end of June we had this ability.
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
terminator1983 said:
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
Click to expand...
Click to collapse
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
21q said:
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
Click to expand...
Click to collapse
Download CM7.2 RC1 > http://forum.xda-developers.com/showthread.php?t=1556246. It has full FP reader support, both security and navigation. (No webtop though).
After unlocking the bootloader (assuming you will be following these instructions > http://forum.xda-developers.com/showthread.php?t=1136261) You will need root again (instructions also in the previously linked thread), and then you will want to flash Romracers recovery through fastboot before flashing any ROM >
http://forum.xda-developers.com/showthread.php?t=1204500
After this you will be able to get into recovery and flash whatever you want. There is an automated script here for unlocking the bootloader also located here > http://forum.xda-developers.com/showthread.php?t=1182871.
Been a while since I did all this myself, but I think I covered everything!
Good luck.
***Ignore this post***
So I don't need to run any of those fastboot commands??
And should I update my phone to 2.3.4?
I just updated it to 1.8.3 by flashing the sbf so I've lost root and everything.
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
CaelanT said:
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
Click to expand...
Click to collapse
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Does doing a full fastboot wipe delete the cwm recovery?
arpit85 said:
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I don't believe it was ever unlocked
When I flashed the sbf via rdslite it would go to 100% but would be stuck saying "in process"
I made a new thread though since my problem is completely different now
http://forum.xda-developers.com/showthread.php?t=1568347
21q said:
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
Click to expand...
Click to collapse
If you flashed sbf with rsdlite and text unlocked is gone, thats mean that you have relocked BL.
You can unlock again by flashing via RSDLite this:
ATT ONLY(It works for 4.5.91 and 4.5.141- Tested myself yesterday) - http://diamantephoto.com/pudding.rar
It is from post:
http://forum.xda-developers.com/showthread.php?t=1136261