Related
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
qtqt710 said:
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
Click to expand...
Click to collapse
DId you replace ALL of the files and then point the RSD to the xml?
Can you boot into fastboot by holding power button and vol down.If can you just reflash it using rsd lite.Tell me more detail about your atrix 2 current rom and which version of rom you are flash with rsdlite.
Sent from my MB865 using xda premium
Exact same problem has occurred to me as well.
I did replaced the files Jim created to FXZ back to 2.3.6 from ICS
My Battery was fully charged at the time of flashing. Flashing stopped at 5/19 reboot bootloader for 15 mins then tried rebooting it manually but it didn't started.
Now I've tried everything but it is not even starting in Fastboot
Please help me with this, I don't want to start any new thread so posted my problem here.
EDIT: I think this is a common problem as the OP here also have the same problem
http://forum.xda-developers.com/showthread.php?t=1781045
http://forum.xda-developers.com/showthread.php?t=1700775
I only flashed ICS when Jim confirmed that it was possible to revert back to 2..3.5
I think there is a problem in reverting back to 2.3.5 once applied ICS update and people should be aware of that.
Everyone should stop flashing ICS leaks otherwise they might end up bricking their phone forever.
100% same to me.
Up to ICS ok, back to Fxz with RSD and stuck at 5/19 reboot-bootloader step, I disconnected cable and phone black forever.
A lot of people they failed when flash with RSD but no problem, just take battery out and return, boot again to fastboot to re-flash. I think wrong file in Fxz not makes this problem, main cause I still don't know ! Maybe we are unlucky man ?
FXZ is not wrong one as I did used it when I had to flash back to stock from lithium Rom last week. I think phone is dead because it is not even booting into fastboot.. I've tried even booting to our stock recovery by pressing 3 buttons but no luck so far.
Its just very bad few hours back I was running ICS and now my phone is not even booting up.
OMG man!! I should have make a thread about this yesterday, but maybe nobody would of paid attention. I didn't really want this to happen to anyone, when flashing from 4.0.4 back to 2.3.5 it will get stuck at 5/20, something like that saying "rebooting loader". Now my phone with a blackscreen is getting hot when I insert the battery and when I plug it without a battery into my laptop or wallcharger and I dont have warranty. I call it white LED of death, when I plug it in to my laptop without a battery hehe , so I guess i'll be paying maybe 200$ dollar for it to be repaired, well if they repair it though, they charge so much here.. But i'm still trying to look what I can do, before I take it to a repair shop.
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
vinamilk said:
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
Click to expand...
Click to collapse
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
prasannapmv said:
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
Click to expand...
Click to collapse
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
vinamilk said:
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
Click to expand...
Click to collapse
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
darkmixta said:
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
Click to expand...
Click to collapse
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
prasannapmv said:
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
Click to expand...
Click to collapse
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
darkmixta said:
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
Click to expand...
Click to collapse
yes its getting heated when connected to a wall socket or on a battery.
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
prasannapmv said:
yes its getting heated when connected to a wall socket or on a battery.
Click to expand...
Click to collapse
Hahaha, what should we do? Yesterday I felt like throwing my phone into the wall man and just %$#@ Motorola, this is like the biggest failure ever!! Hard bricked without doing something wrong.. Wish I could go back in time sometimes and I don't even have warranty which sucks, what are you gonna do?
Really hard to hard brick? http://forum.xda-developers.com/showpost.php?p=28324515&postcount=10
We hard bricked so easy..
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I was already using RSD 5.7
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I did not. It is 5.6. That may be the reason. I got my A2 from att in Nov 2011, so I guess it is the same earlier version, right?
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Fall of Enosis said:
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Nope they can not even power on anymore. This is what we all feared. The hk leak had this same thing in it...
Looks like moto will be warrantying a bunch of phones.
I am just not sure why I can still do it...
We have had way too many of these now for it to be user error or an accident.
Sent from my SAMSUNG-SGH-I747 using xda premium
Phone : unlocked AT&T
What was done : used multiple ways to get back to GB including "A2_go_bak_win". at i ended up in boot loop.... then i used RSD lite to do the same this it failed in between .... (battery was 50%)
After this the phone's screen is absolutely blank ... no powering up... just one catch if i put battery into the phone it starts getting warmer....
Any suggestions.....
sanatan said:
Phone : unlocked AT&T
What was done : used multiple ways to get back to GB including "A2_go_bak_win". at i ended up in boot loop.... then i used RSD lite to do the same this it failed in between .... (battery was 50%)
After this the phone's screen is absolutely blank ... no powering up... just one catch if i put battery into the phone it starts getting warmer....
Any suggestions.....
Click to expand...
Click to collapse
When you flashed through RSD did you use the ICS patch? The patch skips the mbmloader which is the file that bricks your phone. Also Jim's script usually has to be run twice before the phone boots (first time it just hangs on Moto Logo).
If you didn't use the patch your phone is gone. Nothing you can do besides get a replacement....
farshad525hou said:
When you flashed through RSD did you use the ICS patch? The patch skips the mbmloader which is the file that bricks your phone. Also Jim's script usually has to be run twice before the phone boots (first time it just hangs on Moto Logo).
If you didn't use the patch your phone is gone. Nothing you can do besides get a replacement....
Click to expand...
Click to collapse
exactly.
farshad525hou said:
When you flashed through RSD did you use the ICS patch? The patch skips the mbmloader which is the file that bricks your phone. Also Jim's script usually has to be run twice before the phone boots (first time it just hangs on Moto Logo).
If you didn't use the patch your phone is gone. Nothing you can do besides get a replacement....
Click to expand...
Click to collapse
I would also like to know if you tried to use the patch for ics in rsd.
Sent from my MB865 using xda premium
It looks like he tried to use my script, but got the odd flash that 1 in 10 people seem to get. All the OP needed to do was rerun the script, that is posted in my thread about the return to GB thread. If it fails the second time, all you need to do is use RSDlite, and point it to the XML file that came within my script.
I hate to tell the OP, but you are bricked.
This is why im still scared to downgrade back to GB.
Sent from my MB865 using xda app-developers app
bsballkingben99 said:
This is why im still scared to downgrade back to GB.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
lol, I know
bsballkingben99 said:
This is why im still scared to downgrade back to GB.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Look, as with everything on this board, read WHOLE threads before you attempt anything... most times people post an issue and then there are ways posted on how to get around it.
If you follow the directions and have an issue post in the thread and one of us have most likely encountered it, and give you fix... DON'T do as the OP did and just start trying things. One of us devs or Sr. members will get you you taken care of fairly quickly, but panicing and just starting to try things is the easiest way to brick.
I wouldn't want to downgrade either.. to scared I might mess up
Sent from my MB865 using xda app-developers app
jangeles323 said:
I wouldn't want to downgrade either.. to scared I might mess up
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I've done it like 8 times already... It's not too bad as LONG AS YOU FOLLOW DIRECTIONS!
Went to Motorola Service Center .... motherboard need to be changed.... INR-6800 ~ 122 USD...
I ll get it tomorrow...
sanatan said:
Went to Motorola Service Center .... motherboard need to be changed.... INR-6800 ~ 122 USD...
I ll get it tomorrow...
Click to expand...
Click to collapse
Aww that sucks? Why don't they give you a replacement? Aren't you under warranty?
It is under warranty but i bought it from US and now i am in India.... the IMEI no will change too
sanatan said:
It is under warranty but i bought it from US and now i am in India.... the IMEI no will change too
Click to expand...
Click to collapse
$122 is cheap for a motherboard replacement. Consider yourself lucky it did not cost you more.
Hey guys!
Was trying to solve the restart loop problem by installing a MIUI rom, but I am now stuck on this screen that says..
Stuck on AP Fastboot Flash Mode (S) (Boot Failure)
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG OTV(CG: webtop): Invalid SP Data
Invalid CG Version (CG: webtop)
Invalid CG OTV (CG: webtop)
Any thoughts or help would be highly appreciated
Did you find the proper fxz for your base firmware and flash it?
Need more info about where you are coming from, what you did to get this problem, and what you have tried..
Sent from my MB865 using xda app-developers app
I am not sure what fxz is...but from what I know, it was on 2.3.6 and next update was failing and it was restarting..so I rooted the phone, installed the bootstrap...tried installing miui from there.. it restarted and now I am on that screen...
Have not tried anything else after that... I was looking around and it seems, I should flash something from fastboot mode? I am currenty downloading the ics fastboot files... planing to use RSD lite to install it...
Is that right approach?
Thanks for your help through...much appreciated.
EDIT: Its an AT&T Atrix 2 if that helps..
So, you were on 2.3.6? The 4.0.4 update failed?
If so, then you should probably be using the 2.3.6 fxz/sbf/fastboot/firmware files - flash those to go back to stock GB, then ota update to ICS the normal way (unless returning to GB is important to you - if so, find ICS leak #1 and install that instead of the ota update after restoring stock 2.3.6).
And yea, you need to be on ICS base to install miui (unless there's a GB version I didn't know about).
Sent from my MB865 using xda app-developers app
Edit: you seen this thread? http://forum.xda-developers.com/showthread.php?p=32113181
Links to the att-us 2.3.6 and 4.0.4 fastboot files are there.. Just read carefully and ask if you're not sure.
It's important to know if you were on 2.3.6 or 4.0.4.. and if you just tried to install a new ROM (system only) through custom recovery, or if you flashed something else through fastboot.
I was surely on 2.3.6, but it was not stable and was rebooting quite often ...it was also trying to download the next update, each time the phone was on...but it would just restart before the download could ever finish...
I rooted the phone after that, installed bootstrap.apk to get into clockwork recovery, then tried installing the MIUI which was based on 4.xx something .... but that failed and I got stuck in that screen....
So, basically, I should download AT&T 2.3.6
http://sbf.droid-developers.org/edison/InlineFlashing_edison_5.5.175.25_cfc_p3_APBP.xml.zip
use fastboot and follow these steps?
Fastboot erase system
Fastboot erase userdata
Fastboot update romfilename.zip
Fastboot reboot
OR
Try to use RSD lite instead?
One more problem though...I tried using the fastboot erase system command...and it tells me Battery low...
I have the phone on charger now, but the Fastboot screen comes up again and I am not sure if it will charge this way?
Any thoughts?
Thanks in advance.
You need to charge somehow (wall charger, macgyver method, another battery, friend's phone, at&t store, etc).. It doesn't charge in fastboot mode.
Then try RSD lite..
Otherwise, you would need to use moto-fastboot commands. See the files in the zip package here for examples (you can look at the .bat files for the proper commands): http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Sent from my MB865 using xda app-developers app
alteredlikeness said:
You need to charge somehow (wall charger, macgyver method, another battery, friend's phone, at&t store, etc).. It doesn't charge in fastboot mode.
Then try RSD lite..
Otherwise, you would need to use moto-fastboot commands. See the files in the zip package here for examples (you can look at the .bat files for the proper commands): http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks for that, I was able to do all that and now the phone is on 2.3.6 ..but the original problem is still there...the phone keep on restarting.. any ideas what the issue might be?
jackdowsan said:
Thanks for that, I was able to do all that and now the phone is on 2.3.6 ..but the original problem is still there...the phone keep on restarting.. any ideas what the issue might be?
Click to expand...
Click to collapse
So it just reboots at random? Or it boots to Fastboot mode everytime?
If it's random reboots, you might have a hardware issue in your phone.. And you could ask AT&T for a replacement (they will most likely just give you a new Atrix HD since our A2 has been EOL'd).
If it boots straight to fastboot everytime, then there's something else.. not sure what, but I have seen others post of that issue.
alteredlikeness said:
So it just reboots at random? Or it boots to Fastboot mode everytime?
If it's random reboots, you might have a hardware issue in your phone.. And you could ask AT&T for a replacement (they will most likely just give you a new Atrix HD since our A2 has been EOL'd).
If it boots straight to fastboot everytime, then there's something else.. not sure what, but I have seen others post of that issue.
Click to expand...
Click to collapse
It reboots every 3-4 mins or so... Also noticed, it says under settings, that radio if Off and there is no IMEI number...also I cannot seem to turn off the Airplane mode..
Does that indicate something?
jackdowsan said:
It reboots every 3-4 mins or so... Also noticed, it says under settings, that radio if Off and there is no IMEI number...also I cannot seem to turn off the Airplane mode..
Does that indicate something?
Click to expand...
Click to collapse
Hmm.. Yea.. What the heck did you do to it? Did you erase your cid? Do you have a backup of it? If not, sorry to say, but you may be out of luck...
Sent from my MB865 using xda app-developers app
alteredlikeness said:
Hmm.. Yea.. What the heck did you do to it? Did you erase your cid? Do you have a backup of it? If not, sorry to say, but you may be out of luck...
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I was only doing a OTA update and I ended up in this mess of reboots, then I tried installing the 4.something MIUI, then fastboot files of 2.3.6...and now in this mess
I dont have any backup files or anything...if there any way I can go to stock maybe? or maybe if I can somehow manage to go to ICS, this might be fixed? No ideas :crying:
jackdowsan said:
I was only doing a OTA update and I ended up in this mess of reboots, then I tried installing the 4.something MIUI, then fastboot files of 2.3.6...and now in this mess
I dont have any backup files or anything...if there any way I can go to stock maybe? or maybe if I can somehow manage to go to ICS, this might be fixed? No ideas :crying:
Click to expand...
Click to collapse
You did go back to stock 2.3.6 (the fxz should have flashed all stock images/files)... but if your cid is gone (not positive though that that is your problem), there's no getting it back (it is specific to each device).
You could try forcing the update to 4.0.4 by following this: http://forum.xda-developers.com/showthread.php?t=1779968 - but not sure it will install the update if it can't recognize your phone. You are sure it is an AT&T phone, right?
Unless some other members here have some ideas, not sure what else to try... except calling AT&T for a replacement if you bought it under contract. Just tell them that an over-the-air update failed and the phone keeps rebooting..
So, I wonder, did the OTA update start installing, then fail (a while after installation started)? Maybe that messed things up.. Usually, if it fails right away at the beginning of installation during the system checks, then it should be no issue.. But if it was interrupted later during the install, then that can cause major issues.
alteredlikeness said:
You did go back to stock 2.3.6 (the fxz should have flashed all stock images/files)... but if your cid is gone (not positive though that that is your problem), there's no getting it back (it is specific to each device).
You could try forcing the update to 4.0.4 by following this: http://forum.xda-developers.com/showthread.php?t=1779968 - but not sure it will install the update if it can't recognize your phone. You are sure it is an AT&T phone, right?
Unless some other members here have some ideas, not sure what else to try... except calling AT&T for a replacement if you bought it under contract. Just tell them that an over-the-air update failed and the phone keeps rebooting..
So, I wonder, did the OTA update start installing, then fail (a while after installation started)? Maybe that messed things up.. Usually, if it fails right away at the beginning of installation during the system checks, then it should be no issue.. But if it was interrupted later during the install, then that can cause major issues.
Click to expand...
Click to collapse
tried updating to 4.0.4 but it fails ...I have attached the screenshot.. what can this be?
Hi guys!
I tried searching for a similar problem that I have but wasn't able too. So I need your help here.
So I lost my CID, didn't back it up so was using bptools for it when I was on JB leak3.
1) I flashed CM11, 4.4.2 dated 14 Dec after flashing gapps, it removed my recovery and was bootlooping
2) I reflash the same leak3 which used to work earlier using RSDlite. Now the rom isn't booting i.e. it is stuck in it's "pumping logo".
3) I again try reflashing using RSDlite, only this time, it fails and status is shown as battery low in fastboot. Now I connect charger, it boots, stuck in the white screen which is expected since I lost my CID.
So, does this mean that it's charging? If not, am I screwed??
shubham1120 said:
Hi guys!
I tried searching for a similar problem that I have but wasn't able too. So I need your help here.
So I lost my CID, didn't back it up so was using bptools for it when I was on JB leak3.
1) I flashed CM11, 4.4.2 dated 14 Dec after flashing gapps, it removed my recovery and was bootlooping
2) I reflash the same leak3 which used to work earlier using RSDlite. Now the rom isn't booting i.e. it is stuck in it's "pumping logo".
3) I again try reflashing using RSDlite, only this time, it fails and status is shown as battery low in fastboot. Now I connect charger, it boots, stuck in the white screen which is expected since I lost my CID.
So, does this mean that it's charging? If not, am I screwed??
Click to expand...
Click to collapse
If fastboot says low battery then u cant RSD.....
Google Mcgruyver method or externally charge ur battery....( ie if you get a white led )
If your in india it shouldn't be a problem finding an external universal battery charger in any cell shop....
darth_nihar said:
If fastboot says low battery then u cant RSD.....
Google Mcgruyver method or externally charge ur battery....( ie if you get a white led )
If your in india it shouldn't be a problem finding an external universal battery charger in any cell shop....
Click to expand...
Click to collapse
Thanks for your reply buddy!
But it was charging even when the screen was white. So now I'm on JB leak 3. Any idea why did my recovery uninstalled automatically?
shubham1120 said:
Thanks for your reply buddy!
But it was charging even when the screen was white. So now I'm on JB leak 3. Any idea why did my recovery uninstalled automatically?
Click to expand...
Click to collapse
Dude if fast boot says low battery RSD wont flash it............whether or not it was charging with a white screen
So u have to externally charge the battery
And from what i know u can't flash ICS once ur on the JB leak ie u can't downgrade so u will have to flash the same leak again......
shubham1120 said:
Thanks for your reply buddy!
But it was charging even when the screen was white. So now I'm on JB leak 3. Any idea why did my recovery uninstalled automatically?
Click to expand...
Click to collapse
BMM can be like that sometimes. There are a few possible ways that it could've happened. As long as you make a backup before trying anything, and have RSD lite and your FXZ handy it shouldn't be too much of a problem. It's more aggravating than anything else...
darth_nihar said:
Dude if fast boot says low battery RSD wont flash it............whether or not it was charging with a white screen
So u have to externally charge the battery
And from what i know u can't flash ICS once ur on the JB leak ie u can't downgrade so u will have to flash the same leak again......
Click to expand...
Click to collapse
If he was getting the "pumping" Motorola logo boot animation, then he was only boot looping so he was able to charge the battery. The battery would've only been an issue if the phone was booting straight into fastboot, or if it wouldn't get past the boot logo.
Also you can downgrade from jb to ICS, just not from ICS to GB.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
1BadWolf said:
BMM can be like that sometimes. There are a few possible ways that it could've happened. As long as you make a backup before trying anything, and have RSD lite and your FXZ handy it shouldn't be too much of a problem. It's more aggravating than anything else...
If he was getting the "pumping" Motorola logo boot animation, then he was only boot looping so he was able to charge the battery. The battery would've only been an issue if the phone was booting straight into fastboot, or if it wouldn't get past the boot logo.
Also you can downgrade from jb to ICS, just not from ICS to GB.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
I din know u can never tried the leaks coz of AT&T but i read somewhere that it changes or updates
the recovery or bootloader ??
Edit: My bad you can downgrade back to ICS
wangs cn leak said u might not so thats where i read it .....
Deja vu!!
1BadWolf said:
BMM can be like that sometimes. There are a few possible ways that it could've happened. As long as you make a backup before trying anything, and have RSD lite and your FXZ handy it shouldn't be too much of a problem. It's more aggravating than anything else...
If he was getting the "pumping" Motorola logo boot animation, then he was only boot looping so he was able to charge the battery. The battery would've only been an issue if the phone was booting straight into fastboot, or if it wouldn't get past the boot logo.
Also you can downgrade from jb to ICS, just not from ICS to GB.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
Hey!
IDK what was I thinking but I flashed pa 4.4.2 gapps on CM11 by altered and BOOM! Lost recovery and bootloop.
So I re-flashed leak 3 it's now stuck in boot animation("pumping"--again what was I thinking lol!) meaning a softbrick. Why is it happening? I mean is it a bad flash?
Or does it have something to do with leak 3? If so, I can't seem to find ics fxz. The superthread links are dead. My another question is-
Will I be able to us AT&T fxz? Since I've already lost my CID, it shouldn't be a problem right?
PROBLEMS PROBLEMS PROBLEMS!:silly:
Also, can anyone give me the link for asian version of ICS?
EDIT- Was able to boot! went to stock recovery, wiped data and cache partition. Thanks for help guys
shubham1120 said:
Hey!
IDK what was I thinking but I flashed pa 4.4.2 gapps on CM11 by altered and BOOM! Lost recovery and bootloop.
So I re-flashed leak 3 it's now stuck in boot animation("pumping"--again what was I thinking lol!) meaning a softbrick. Why is it happening? I mean is it a bad flash?
Or does it have something to do with leak 3? If so, I can't seem to find ics fxz. The superthread links are dead. My another question is-
Will I be able to us AT&T fxz? Since I've already lost my CID, it shouldn't be a problem right?
PROBLEMS PROBLEMS PROBLEMS!:silly:
Also, can anyone give me the link for asian version of ICS?
EDIT- Was able to boot! went to stock recovery, wiped data and cache partition. Thanks for help guys
Click to expand...
Click to collapse
If you ever want to use the JB leaks again, DO NOT flash the AT&T FXZ. Just a forewarning just in case you get stuck again and start considering it.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
1BadWolf said:
If you ever want to use the JB leaks again, DO NOT flash the AT&T FXZ. Just a forewarning just in case you get stuck again and start considering it.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
OMG you're right! Never thought of that! Thank God I acted patiently here. I was gonna flash AT&T ics just before trying that wiping data thing!
Thanks! Will keep that in mind.
One more question though(and hopefully the last..)
Can I flash PA Gapps on slimkat? Since both are based on AOSP right?
i guess i've a problem . by mistake while i was supposed to backup cid , i chose the option erase cid and it s deleted, no backup either. now whenever i reboot, my phone shows some error. since i've bmm i am being able to load into ics in system 1 . is there any possible way to get rid of this error message about cid during startup?? because it is really annoying.
As the subject states I have a Roger's Razr HD (XT925) that was GSM unlocked for use here in the US. It was rooted and bootloader unlocked and used for a while without problem. I recently decided to upgrade to a new phone and did a factory reset of the HD in preparation to sell it. It got stuck in boot loop but I was able to boot fine in recovery and everything worked fine. I forgot power it off and the battery drained. When plugged into AC it will not charge. Plug it into a PC and USB connection sounds like it's loading drivers. Device manager shows QHSUSB_DLOAD. Any attempt to boot into recovery mode when plugged in yields a couple green flashes from the LED and that's it. When unplugged, absolutely nothing. I did make a Motorola data adapter and connected the phone to the PC. The green light comes on for a few seconds and then goes out.
Any help would be greatly appreciated. I really need to revive this phone.
QHSUSB_DLOAD is a perma-brick, unfortunately. I haven't seen anyone on here recover from it.
Sent from my HTC6525LVW using Tapatalk
Would this help?
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Assuming you can substitute accordingly, of course.
CWGSM3VO said:
Would this help?
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Assuming you can substitute accordingly, of course.
Click to expand...
Click to collapse
Thanks. I'll check it out.
So I had chance to check out the link and I think the solution to the problem is simpler than that. I know the phone was booting into fastboot when it had a charge. It's possible my DIY factory cable isn't a good one. The RAZR/MAXX/AtrixHD have a simple two pin battery that can charged by opening the case. The battery for the HD has 4 pins however I cannot find the pinout for it. Can any tell me which are the positive and negative? I can cut and hook up an USB cable to them to charge the battery directly and then I should be able to boot the phone and repair the ROM.
Edit: I was able to get my hands on a multimeter and found that the there's 1 positive pin and 3 negative ones?!?!
did you try to leave your xt 925 plugged to pc for little while, then attempt to get it into fastboot?
hbenz2008 said:
did you try to leave your xt 925 plugged to pc for little while, then attempt to get it into fastboot?
Click to expand...
Click to collapse
Yes. I left it overnight.
Well then you cant do jack , i noticed battery stays ok in xt925 while on fastboot but I guess if batty is completely out, it is a different story. You will revive it man, gotta get hold of factory cable or a spare battery
OK... I have been able to charge the battery and can get to fastboot. Now I just the Rogers stock ROM because I thought I had the bootloader unlocked but don't. I found a couple links but the site is dead. The phone boots directly into AP fastboot.
truebeliever71 said:
OK... I have been able to charge the battery and can get to fastboot. Now I just the Rogers stock ROM because I thought I had the bootloader unlocked but don't. I found a couple links but the site is dead. The phone boots directly into AP fastboot.
Click to expand...
Click to collapse
Look at page 71 onwards in XT925 kitkat tracking thread. There's a link I posted for the Rogers 4.1.2 JB SBF.
EDIT: Here ya go http://forum.xda-developers.com/showthread.php?t=2760840&page=77
CWGSM3VO said:
Look at page 71 onwards in XT925 kitkat tracking thread. There's a link I posted for the Rogers 4.1.2 JB SBF.
EDIT: Here ya go http://forum.xda-developers.com/showthread.php?t=2760840&page=77
Click to expand...
Click to collapse
Awesome! Thank you! I'm downloading it now.
I just can't win!!! I tried flashing that ROM with RSDLite 6.1.4 and now I'm getting a security downgrade error. Is there a newer ROM I should be using? I cannot seem to find it if there is.
truebeliever71 said:
I just can't win!!! I tried flashing that ROM with RSDLite 6.1.4 and now I'm getting a security downgrade error. Is there a newer ROM I should be using? I cannot seem to find it if there is.
Click to expand...
Click to collapse
Comment out TZ/Partition in XML when downgrading and already upgraded device. You're gonna need the tz/partition from a 4.4.2 build and flash those I believe. There's lots of info on this here just don't have it handy to link for you.
CWGSM3VO said:
Comment out TZ/Partition in XML when downgrading and already upgraded device. You're gonna need the tz/partition from a 4.4.2 build and flash those I believe. There's lots of info on this here just don't have it handy to link for you.
Click to expand...
Click to collapse
I don't find anywhere in the XML that has a tz/partition statement. Being that this is a Canadian device I only had the stock ICS on it.
I thought I had a Rogers RAZR HD after some research I found that I have a Fido one. So, I have to find the Fido ROM