Need Help, bricked after Sonya 2.5 - Motorola Atrix 2

Guys, Igot my phone bricked after flash this upgrade of Sonya 2.5. After the wipes, I had flashed normaly this rom, I havent got any error, everything has just happend perfectly, but after reboot, i got the big M forever and I cant put it in fastboot mode becaude ive got low battery, please a i need help. Sorry my english.

robovp said:
Guys, Igot my phone bricked after flash this upgrade of Sonya 2.5. After the wipes, I had flashed normaly this rom, I havent got any error, everything has just happend perfectly, but after reboot, i got the big M forever and I cant put it in fastboot mode becaude ive got low battery, please a i need help. Sorry my english.
Click to expand...
Click to collapse
here follow this tread worked for me when i was rsd lite my phone and it died on me
http://forum.xda-developers.com/showthread.php?t=892026

Charge your battery and just try flashing the FXZ or another rom if you have CW on boot.

chrisn91 said:
here follow this tread worked for me when i was rsd lite my phone and it died on me
http://forum.xda-developers.com/showthread.php?t=892026
Click to expand...
Click to collapse
Thanks a lot dude. I got it and it works perfectly for me.

mine also got bricked too....after flashing the fxz i got everything back, however my phone will randomly shut off, sometimes in the middle of the boot, other times while on the charger, and sometimes just random...... could there be something funny that did not reset all the way with the fxz?
on one note, after i bricked it, i had too hot wire my battery to get enough of a charge to flash the fxz, i wonder if i touched some of the contacts together?
EDIT: when it does it while on the charger it wont charge once its off.....

Buy a external charger....
Sent from my MB865 using Tapatalk 2 Beta-5

Related

Bricked/Soft Brick?

Hi, my Atrix seems to be stuck in a boot loop although I don't think it's totally bricked.
My phone was unlocked, rooted, and running CM7 fine for several months and then the other day while charging it via USB, several apps kept started to force close so I thought I would try rebooting the phone. Upon reboot the got to the CM7 splash screen and automatically rebooted then it would only load up the Motorola symbol then reboot again and every time after it would reboot after the moto symbol. I thought no problem I would just flash back to stock via .sbf
I plugged in the phone and RSD Lite detected it. I loaded the 2.3.4 ATT SBF file (used it before 2 or 3 times safely) then started the flashing process and waited. I got to where it said reboot phone manually, so I did. After restarting the phone, it showed the Motorola creen then the ATT screen so I had thought I fixed it. While on the ATT screen it froze for a few minutes then it entered the boot loop process again getting to ATT screen each time.
I thought maybe it was a bad flash so I tried flashing the SBF again (in hindsight, probably not a good idea). It got to same place it did before and asked me too reboot and the boot loop process started again. I tried to manually restart it by holding volume down and power, but I would get the RSD Protocol Support message.
Is my phone recoverable or is bricked? If bricked, what are my options regarding obtaining a new phone since I am out of warranty, no insurance and cant upgrade till September and don't exactly have $500 for a new smartphone?
i think your phone is recoverable soft bricked
Yes soft bricked, hey you ride a 450?
Sent from my HTC Wildfire S using xda premium
Yes, soft bricked. If you can get into download mode just flash back to stock and try again. If not, use a jig. You can also buy a jig from ebay for less then $4 buy it now , free shipping.
There might be other ways but I cannot think of any atm. Its almost 4am here lol.
Sent from my Serendipity 6.4 flashed Captivate using xda premium
soft bricked...majorly due to kernal problem..reflash the kernal
Thanks all and no I don't "ride a 450" sorry (I'm assuming by that you mean motorcycle or ATV with a 450cc engine)
oh sorry I meant to ask that question to dirtbikerr450, but yes a 450cc engine
Android311 said:
oh sorry I meant to ask that question to dirtbikerr450, but yes a 450cc engine
Click to expand...
Click to collapse
No i dont sadly i ride a 125
I was finally able to get into Android Recovery by unplugging the battery then plugging in the usb then simultaneously holding volume down and plugging in the battery, I wiped the data and cache then rebooted, to my suprise it booted back up but, only to where I could make emergency calls. Tried to reflash stock with RSD Lite again this time it said passed though but I can still only make emergency calls. Any suggestions?
dirtbikerr450 said:
No i dont sadly i ride a 125
Click to expand...
Click to collapse
125s are great, I ride a crf450 great bike
Sent from my HTC Wildfire S using xda premium
whenemusattack said:
I was finally able to get into Android Recovery by unplugging the battery then plugging in the usb then simultaneously holding volume down and plugging in the battery, I wiped the data and cache then rebooted, to my suprise it booted back up but, only to where I could make emergency calls. Tried to reflash stock with RSD Lite again this time it said passed though but I can still only make emergency calls. Any suggestions?
Click to expand...
Click to collapse
Nice man! Why don't you flash cm7?
Sent from my HTC Wildfire S using xda premium
I took out the sim card and wiped it and then reinserted it and the phone booted. I don't know if I want to unlock and root again, at least probably not until ICS is here. How is CM9, stable enough for everyday use?
Im not sure, but most cm9 here are still nightlys (I think) which would be stable for everyday use, so maybe next month you will start to see stable versions out
Sent from my HTC_A510c using XDA

Anyone have a solution for me?

Maybe i'm posting in the wrong section but here's the thing.
Okay so I tried searching everywhere for a solution and I didn't find anything.
So this is what happened, I was on ICS leak 4.0.4 ICS.672.1.13.en.03 then I tried to Fxz to AT&T 2.3.5 InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip and it got stuck at 5/20 saying "Rebooting bootloader" the screen stayed black for a long time, so I clicked close and this is where all this happened. My phone doesn't turn on, not even Fastboot, when I plug it into the charger it doesn't do anything, but when I plug it into my laptop without battery the white led turns on but still it doesn't do anything, the laptop doesn't detect anything and when I press the buttons it doesn't react nor do anything. I don't know anymore what to do, I bought this overseas so I have no warranty and it's not an AT&T phone. If anyone went through this, I really don't know what to do.. I know it's not softbrick as I can see it. I'll be very thankful if there is a solution, but my hopes are really down..
I know I read all the guides, it said "Don't pull battery or unplug. So I didn't unplug or remove battery, I just clicked close. I really didn't know this could happend. Didn't see it in any thread or post that you can't Fxz from 4.0.4 to AT&T 2.3.5
darkmixta said:
. My phone doesn't turn on, not even Fastboot, when I plug it into the charger it doesn't do anything, but when I plug it into my laptop without battery the white led turns on but still it doesn't do anything, the laptop doesn't detect anything and when I press the buttons it doesn't react nor do anything.
Click to expand...
Click to collapse
what phone model /where did you get that zipped rom from/ do you have a stock rom ?
If you start phone and screen is black ( no bootloader image) then it's possible to be really bricked
ruscan.calin said:
what phone model /where did you get that zipped rom from/ do you have a stock rom ?
If you start phone and screen is black ( no bootloader image) then it's possible to be really bricked
Click to expand...
Click to collapse
I got an Atrix 2 and I was on ICS leak 4.0.4, I tried to Fxz to this InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip which I found at this site http://sbf.droid-developers.org/edison/list.php. I have locked bootloader. Btw it got stuck at 5/21 "rebooting bootloader" with a black screen after that nothing worked for me, before I tried it I had 90% of battery.
darkmixta said:
I got an Atrix 2 and I was on ICS leak 4.0.4, I tried to Fxz to this InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip which I found at this site http://sbf.droid-developers.org/edison/list.php. I have locked bootloader. Btw it got stuck at 5/20 "rebooting bootloader".
Click to expand...
Click to collapse
never flash a rom without instructions if you are not an experienced user you have to use RSD Lite to get back to working conditions
ruscan.calin said:
never flash a rom without instructions if you are not an experienced user you have to use RSD Lite to get back to working conditions
Click to expand...
Click to collapse
But I was told that if you have a locked bootloader it's really hard to hard brick your phone.
darkmixta said:
But I was told that if you have a locked bootloader it's really hard to hard brick your phone.
Click to expand...
Click to collapse
pull out battery then back and try to boot/recovery/fastboot or flash a rom by RSD Lite
also read here
ruscan.calin said:
pull out battery then back and try to boot/recovery/fastboot or flash a rom by RSD Lite
also read here
Click to expand...
Click to collapse
I tried booting into fastboot, but the phone even turn on. Only white led when I plug it without battery into my laptop. So it isnt really dead but something is wrong, I tried the invisible boot, but I guess it isnt working.

[Q] My Tab 7 Plus is possibly hard bricked after JB ROM flash

I flashed the JB ROM on my Tab 7 Plus. After the "succeess" of the flashing as said by Odin v1.85, I tried to turn on the device, but it didn't. I tried to access download mode or recovery mode but it didn't work either. I tried to hold the volume down button and connect the cable to the tablet. That opened the download mode but the screen was "flashing". The rate at which the screen "flashes" keeps increasing until it becomes very fast and the device turns off. I tried to flash a ROM, but Unfortunately it turns off fast that there will be no time for the flashing process to continue.
Any idea what should I do?
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Reply
chrisrotolo said:
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Click to expand...
Click to collapse
My Device is GT-P6200 and I got the GT-P6200 JB ROM for it.
______________
I left my device to charge all night. When I woke up I tried to see if the 'flashing' of the screen still occurs, but it didn't happen. I think I can flash a ROM now
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
yes, also a faulty or non-OEM cable would be the culprit.
SudoHalt said:
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
Click to expand...
Click to collapse
yess. flashing(blinking) screen is how download mode tells you that your battery is low. probably less than 10% since it even turned off by itself.
This Happend To me and I got it BACK
Hello... I totally understand your frustration... This exact same thing happened to me after my battery went dead just after I installed JB...
well here is the kick and it's kind of tricky...
If you want you can call me and I can tell you the instructions, it's complicated but if you follow the steps it will work...
I can also take the time to write it down, but i'm bad a typing.
let me know if you are interested...
Sorry for the late reply. It was fixed after less than a day from starting this thread.
Sent from my GT-I9001 using xda app-developers app

Phone wont start after restoring boot partition through TWRP

Guys,
Have been running MIUI V5 on my d2vzw (ported from d2spr) for a couple of days now. Noticed today that the videos were playing reversed (probably due to the ROM running on sprint kernel, correct me if i am wrong). So i flashed one of the kernels for vzw and had a bootloop.
So, in a moment of inspiration :crying:, i restored the boot partition from my MIUI v4 backup in TWRP (thinking that must be the kernel part) and the phone wont boot. No Download mode, no vibration, get the red indicator on for some seconds but thats it. I get QHSUSB_DLOAD error when connected to my computer.
Guess this is a hard brick. Would i be able to get into download mode with USB JIG (i would need to make one, if there is no chance i will not try it). Is JTAG my only option? I have no warranty between since i am using this phone in India.
Guys,
Any Help??
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever.
Sent from my SCH-I535 using Tapatalk 2
What is the reality of this thought anyone have the truth?, ThanksQ
Is this statement TRUE for certain? Quote: "I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever."
Thanks in advance! moi
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
Pull battery and let sit an hour so everything discharges and try again. If still blacked out most likely J-Tag. QHSUSB_DLOAD error is a bad sign.

[Q] I believe I broke it.....

Hello anyone out there who reads this. I know this may have been covered before but I am in a unique situation. I purchased a T869 from ebay. Well I was googling and reading on Xda about how to get phone capabilities with my Family mobile sim card. Well I was reading a post about Using Odin to put P6200 Firmware on it. And I did.... It worked perfect booted no issues I played with it abit this morning and then plugged it up to charge and took a nap. When I woke It was off and refuses to boot. I can get into ODIN mode but nothing else. I did manage to flash CWM and get to clear and reset it once but nothing else. So Have I killed it? Or is there anything I can do? Yes I have tried to flash back to stock and no it wont work.
I am a moron...
I switched to the OEM cable and let it sit. It booted......
Angelouse said:
I switched to the OEM cable and let it sit. It booted......
Click to expand...
Click to collapse
Glad you got it working. I am experienced with installing roms but had a bad scare when I fell asleep while installing a ROM, it bootlooped until it ran out of batteries. Was very difficult to boot even to download mode or recovery.

Categories

Resources