Need advanced assistance with soft brick - Atrix 4G Q&A, Help & Troubleshooting

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

Related

Data Connection Error, well, lack of!!

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!

[Q] Hacking Dispairs

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

[Q] Messed up , bricked:( p 769

Okay, so I was trying to unlock my bootloader. Completed ALL the steps up to were I had to flash Radio.zip to get my signal back. Stupid me accidently hit to install the rom I had choosen to install after unlocking my bootloader. I didn't notice untilit was already installing. So it rebooted and I just get the non animated LG logo and it says security error under it. I am able to get to the s/w upgrade screen by holding volume up and plugging usb in. I searched Everywhere and can't solve the issue. I tried re-flashing my kdz file and it only goes to 15% then says my phone is not connected, tried reinstalling the drivers and got the same message. Then I proceeded to the online method. While doing this it found my phone and proceeded to the second part where it begins downloading. It went to 13 seconds time lapsed the stopped. No bar moving across and no more counting with the time lapse. I had read were it froze on others and they let it proceed and it did its thing. So I left it for about 4 hours and nothing changed. I then checked my traffic meter on my router and nothing had even began downloading. I reinstalled and tried again. It would go threw the checking for other software part fine then when it gets to the downloading part its at the 13 second time lapse freeze again. This time it didnt count up to it. It was just instantly where I had left off. I then went to my brothers and tried to his computer. Completely reinstalled it and it did the same thing! Didnt even count up to 13 seconds was just instantly there! I then read where someone had the same issues as me and installed fastboot and flashed xloader and uboot and then the offline method reconized them. Im thinking this is my key to fixing, however when i install the driver as instructed it says install failed because lack of electronic signature. So im lost and ran out of search methods to try. Has anyone else had this issue when installing fastboot? Also I was a little confused on which fastboot file to use so I tried a few and all had the same result. Does someone have a link to the one I need or any other advice? This stinks I just bought this phone but the stock rom was driving me crazy because im use to custom! Thanks so much and please help!!!
SOLVED! flashed ics xloader and uboot and it finally found my phone on the offline method. Now I just have the wonky TS to solve. Should be fun since I lost root and cwm. I was able to get show touches and usb debugging on so that makes lofe easier. You guys have no idea how relieved I feel! I thought I pretty much threw 200 bucks away!
Okay little update. I got fastboot loaded on my phone and flashed a recovery.img but still not having any luck. Both programs are doing the same exact thing as before. I feel like im getting there since I now have fastboot. What other options do I have that I can try?
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay I got it all up and running. However when I used your commands none of them would respond and do anything except flashing the ICS u and x. Once I did this I was able to get the offline method to work. I then rooted and installed Cwm to run the ts fix because I had the wonky touchscreen. I then flashed kumas rom . I forgot to use CWM to clear my cache and such before flashing to kumas ROM. Will this effect anything? Should I go to cwn and delete it all and reflash kumas ROM? Thanks!
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
SlideShowPl said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
Click to expand...
Click to collapse
So the only this you can access is sw upgrade mode? what lead up to this? did you install fastboot drivers twice?

[Q] Soft bricked my Atrix 4g

I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.

I ****ed up...

So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.
What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.

Categories

Resources