Title says it all. Please read the whole post. I've done a lot up to this point, and I just don't want to go any further without confirming that what I'm doing is right, because everything that should have worked up to this point hasn't and I fear I'm about to hard-brick the phone.
MY SETUP:
Rooted and locked Atrix 2 (AT&T MB865)
Official 2.3.6 OTA upgrade
No backup/CWM/nandroid/anything other than stock recovery that came with the phone (but see below)
32bit Linux from which to adb and fastboot
THE PLAN:
Flash the boot.img and possibly system.img to maintain my user data so I don't have to reinstall stinkin' everything, and factory reset if absolutely necessary.
HOW I BRICKED IT:
Gained root, installed ROM Toolbox Lite, changed my boot animation, rebooted into a bootloop at the animation screen.
WHERE IT STANDS:
I can get into fastboot with Power+Vol Down, or the boot menu with Power+Vol Up+Vol Down, but I can now only select normal boot from the boot menu (see below).
WHAT I HAVE TRIED ALREADY:
I started with the noob guide: http://forum.xda-developers.com/showthread.php?t=1396650
I got the FXZ from here: http://forum.xda-developers.com/showthread.php?t=1607083
My battery was nearly dead and wouldn't charge, so I did this without actually hooking the battery to the phone: http://forum.xda-developers.com/showthread.php?t=892026
I booted into flashboot with Power+Vol Down
I tried to use the fastboot that came with the Android SDK and got "Preflash validation error" when running
Code:
fastboot flash boot boot.img
I found out about moto-fastboot and got the 32bit Linux version from here: http://forum.xda-developers.com/showpost.php?p=15024312&postcount=48
I got "INFOPreflash validation error" when running
Code:
moto-fastboot32 flash boot boot.img
I booted into the boot menu with Power+Vol Up+Vol Down and selected BP tools, which lead to the bootloop again, and I pulled the battery.
I decided to give up and booted into the boot menu again to try to just do a full factory recovery, only to discover that I was now not able to scroll through the other options, and that Normal bootup was my only option, which lead to the bootloop
WHAT I HAVE YET TO TRY:
RSD Lite, with or without the fix for the 2.3.6 OTA upgrade from the noob guide, primarily because I don't have easy access to a Windows box and I already have all the files and appropriate setup on my Linux box (but is an eventual option)
This, even though it's for a different phone: http://forum.xda-developers.com/showthread.php?t=1295839
This, even though it supposedly works for 2.3.6: http://forum.xda-developers.com/showthread.php?t=1539167
Flashing system.img before flashing boot.img
Again, the only reason I'm stopping where I am to ask for help is because everything that should have worked up to this point just hasn't, and I don't want to hard-brick my phone.
Thanks for getting me this far, guys and gals. Your work is truly extraordinary.
You're first "oops" was not having installed the ATRIX Bootstrap and the CWM Recovery. What you need to do now, is download the Return To Stock script and boot into AP Fastboot, plug in USB, and run the Stock Restore.bak -this will flash 2.3.5 back to your device. Then, you'll have to OTA to 2.3.6. and then I HIGHLY recommend you install the bootstrap.apk along with CWM Recovery.
Sent from my MB865 using xda premium
You will need to make sure you patch the fxz with this:
http://forum.xda-developers.com/attachment.php?attachmentid=887221&d=1328375358
Unzip this, then move these files into the directory with the fxz, and allow them to be replaced.
At this point it is MUCH better to use RSDlite, unless you REALLY know what you are doing here.
It is not your boot.img that is corrupted it is your system.img, that is where all of the programs, and "user level" operations sit. The boot.img is just the OS kernel, and it is not user accessible, so there is really no need to even flash it.
You will need erase the data partition, sorry but you HAVE to do this, or you WILL get FCs left and right.
Here is the exact commands to get you whole again:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash boot boot.img
moto-fastboot reboot
Apex_Strider said:
You're first "oops" was not having installed the ATRIX Bootstrap and the CWM Recovery. What you need to do now, is download the Return To Stock script and boot into AP Fastboot, plug in USB, and run the Stock Restore.bak -this will flash 2.3.5 back to your device. Then, you'll have to OTA to 2.3.6. and then I HIGHLY recommend you install the bootstrap.apk along with CWM Recovery.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Hindsight is 20/20, and I am kicking myself SO HARD for not having done the first two things. As soon as I am back up and running I will do these things. You may consider me duly chastised
I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1539167
I further assume that I can run that script from Linux, possibly with a little doctoring. I see that it uses two erase commands, and when I tried to erase boot.img earlier, I was told that the erase command was restricted. Is that only for certain images?
Sorry for nagging, but I just want to be perfectly clear. I'm pretty solid with Linux but a little green with Android and a lot nervous about the whole thing.
jimbridgman said:
You will need to make sure you patch the fxz with this:
http://forum.xda-developers.com/attachment.php?attachmentid=887221&d=1328375358
Unzip this, then move these files into the directory with the fxz, and allow them to be replaced.
At this point it is MUCH better to use RSDlite, unless you REALLY know what you are doing here.
It is not your boot.img that is corrupted it is your system.img, that is where all of the programs, and "user level" operations sit. The boot.img is just the OS kernel, and it is not user accessible, so there is really no need to even flash it.
You will need erase the data partition, sorry but you HAVE to do this, or you WILL get FCs left and right.
Here is the exact commands to get you whole again:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash boot boot.img
moto-fastboot reboot
Click to expand...
Click to collapse
I'm pretty confident that I can properly patch the FXZ and run those commands (no sarcasm intended), and I can come to terms with the wipe if it gets my device back up and running. Thanks for checking in, Jim (can I call you Jim?), from what I've seen thus far you're pretty highly respected here
EDIT: No disrespect, Apex_Strider, once I saw your avatar I recognized you from around the forum
wormmd said:
Hindsight is 20/20, and I am kicking myself SO HARD for not having done the first two things. As soon as I am back up and running I will do these things. You may consider me duly chastised
I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1539167
I further assume that I can run that script from Linux, possibly with a little doctoring. I see that it uses two erase commands, and when I tried to erase boot.img earlier, I was told that the erase command was restricted. Is that only for certain images?
Sorry for nagging, but I just want to be perfectly clear. I'm pretty solid with Linux but a little green with Android and a lot nervous about the whole thing.
Click to expand...
Click to collapse
NO!!!! do NOT erase any partitions before flashing them...
I am also a Linux user, use the commands I gave, Please be very careful, you can erase things, and not get them to flash back!
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
wormmd said:
I'm pretty confident that I can properly patch the FXZ and run those commands (no sarcasm intended), and I can come to terms with the wipe if it gets my device back up and running. Thanks for checking in, Jim (can I call you Jim?), from what I've seen thus far you're pretty highly respected here
Click to expand...
Click to collapse
Yeah It's Jim, No worries I was not trying to insult you here, I kind of have to think in terms of as if someone does not know the subject well, and make assumptions on their behalf, sort of like tech support... but more knowledgeable... LOL.
wormmd said:
Thanks for checking in, Jim (can I call you Jim?), from what I've seen thus far you're pretty highly respected here
Click to expand...
Click to collapse
Well you got that right.. he's a genius, has experience and more importantly is very helping natured.. always saying "here to help".. lucky to have him onboard..
Sent from my MB865 using Tapatalk 2
wormmd said:
EDIT: No disrespect, Apex_Strider, once I saw your avatar I recognized you from around the forum
Click to expand...
Click to collapse
No disrespect taken, and please accept my apologies if I came across in a 'chastizing' manner -I was only trying to stress the importance of having CWM (on boot, preferably), because it has saved my A$$ and many other's as well.
Sent from my MB865 using xda premium
Apex_Strider said:
No disrespect taken, and please accept my apologies if I came across in a 'chastizing' manner -I was only trying to stress the importance of having CWM (on boot, preferably), because it has saved my A$$ and many other's as well.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You misunderstood: anyone undertaking this kind of work needs to be chastised for not having backups in place before doing stupid things like I did, in my opinion. In addition, I've been doing these kinds of things with computers and software development and such for long enough that I should have known better. I need a swift kick in the butt every once in a while to get me back on the right track
I got all the way to flashing boot. It send successfully, then when trying to write spat out an INFOPreflash validation failure.
I patched the FXZ I got from the OP with the link Jim provided, but there was no boot.img in the patch.
Should I try a fastboot continue or just fall back to this method: http://forum.xda-developers.com/showthread.php?t=1539167?
wormmd said:
I got all the way to flashing boot. It send successfully, then when trying to write spat out an INFOPreflash validation failure.
I patched the FXZ I got from the OP with the link Jim provided, but there was no boot.img in the patch.
Should I try a fastboot continue or just fall back to this method: http://forum.xda-developers.com/showthread.php?t=1539167?
Click to expand...
Click to collapse
I think at this point you might need to use RSDlite, this has happened to a few of us, and there is really not a good way around it if it fails like that.
You will need a Windows 7 install to use, XP will not work, neither will Vista.
I know, I HATE windblows, but for this, it is really the ONLY way to get back to fully stock 2.3.5, and the rest of us Linux users have had to do it at least once. Once this happens, it will NOT let you fully boot, with out that nagging you, and you having to get into recovery and do a "normal" boot EVERY boot. The ONLY way around it is RSD lite and the n00b guide.
jimbridgman said:
I think at this point you might need to use RSDlite, this has happened to a few of us, and there is really not a good way around it if it fails like that.
You will need a Windows 7 install to use, XP will not work, neither will Vista.
I know, I HATE windblows, but for this, it is really the ONLY way to get back to fully stock 2.3.5, and the rest of us Linux users have had to do it at least once. Once this happens, it will NOT let you fully boot, with out that nagging you, and you having to get into recovery and do a "normal" boot EVERY boot. The ONLY way around it is RSD lite and the n00b guide.
Click to expand...
Click to collapse
Man, if that's not the second lamest thing I've ever heard, I don't know what is. The first lamest thing would be losing my phone over something silly like that, but at least it's fixable.
Will the restore script method not work, if I just ran all the commands from that .bat manually? Is it worth trying at least? Is it worth not trying for the sake of not hard-bricking the phone? This restore script method, that is: http://forum.xda-developers.com/show....php?t=1539167
If not, I'll hop on Windows when I get home today. Thanks again for all of your help.
wormmd said:
Man, if that's not the second lamest thing I've ever heard, I don't know what is. The first lamest thing would be losing my phone over something silly like that, but at least it's fixable.
Will the restore script method not work, if I just ran all the commands from that .bat manually? Is it worth trying at least? Is it worth not trying for the sake of not hard-bricking the phone? This restore script method, that is: http://forum.xda-developers.com/show....php?t=1539167
If not, I'll hop on Windows when I get home today. Thanks again for all of your help.
Click to expand...
Click to collapse
With the issue you are having, that script will most likely not fix it. RSDlite really is the best way to go at it... I have had that same thing and I tried everything under the sun and the thing is that there are some binary files that ONLY RSD lite can process correctly and get fastboot to flash, not sure what they have built into RSDlite to do it, but it does what it is supposed to.... Moto is not very "hacker" friendly, and ALL of their junk is windblows centric, at least with other phones there are ways around issues like this in Linux, but between moto locking the phone down, and thier widblows mind set this is the last moto product I buy even with google at the helm... and I LOVE my Xoom, it is unlocked and everything and I have been running CM9 on it for almost a year now. I really honestly bought the A2 for the webtop functionality, but even that was such a pain for me to get all hacked up, and working as it should... that webtop hack of mine took way more time to work out than it should have, thanks to all the "safeguards" Moto put in.
If you try the commands in the script and it works let us know, but I have heard others have issues too once the preflash fail has come up, and have HAD to use RSDlite.
jimbridgman said:
With the issue you are having, that script will most likely not fix it. RSDlite really is the best way to go at it... I have had that same thing and I tried everything under the sun and the thing is that there are some binary files that ONLY RSD lite can process correctly and get fastboot to flash, not sure what they have built into RSDlite to do it, but it does what it is supposed to.... Moto is not very "hacker" friendly, and ALL of their junk is windblows centric, at least with other phones there are ways around issues like this in Linux, but between moto locking the phone down, and thier widblows mind set this is the last moto product I buy even with google at the helm... and I LOVE my Xoom, it is unlocked and everything and I have been running CM9 on it for almost a year now. I really honestly bought the A2 for the webtop functionality, but even that was such a pain for me to get all hacked up, and working as it should... that webtop hack of mine took way more time to work out than it should have, thanks to all the "safeguards" Moto put in.
If you try the commands in the script and it works let us know, but I have heard others have issues too once the preflash fail has come up, and have HAD to use RSDlite.
Click to expand...
Click to collapse
I'm going to give it a go because I'm stubborn as a mule, and I'll be sure to let you know how it goes, but yeah, I'm basically resigned to having to use Windows. This phone had the best hardware for the money when I got it, but I'm getting pretty annoyed with most of what's annoying everyone else too.
Wish me luck!
Once again, got all the way up to flashing boot and then got an INFOPreflash validation failure. Not pleased, but hey, what can you do? Windows, here I come...
UPDATE: it boots
I can boot into the OS by booting to the bootloader with Power+Vol Up+Vol Down, and also I can access other menu option in the bootloader menu now. The new plan is to select "Recovery" from the bootloader menu to see if that'll fix my boot.img, since I'm already wiped as it is. Thoughts?
wormmd said:
Once again, got all the way up to flashing boot and then got an INFOPreflash validation failure. Not pleased, but hey, what can you do? Windows, here I come...
Click to expand...
Click to collapse
I know this doesn't help much, but the last time I tried to FXZ through AP Fastboot it was unsuccessful. I had never run RSDlite before, but had to that time. Worked like a charm...
Sent from my MB865 using xda premium
Apex_Strider said:
I know this doesn't help much, but the last time I tried to FXZ through AP Fastboot it was unsuccessful. I had never run RSDlite before, but had to that time. Worked like a charm...
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
No, it's plenty help. It's good to have confirmation that I'm not crazy and that someone else is having issues I'm having, ya know?
I'm just glad it's semifunctional now. I'll post probably once more tonight after I run it through RSDlite.
wormmd said:
I can boot into the OS by booting to the bootloader with Power+Vol Up+Vol Down, and also I can access other menu option in the bootloader menu now. The new plan is to select "Recovery" from the bootloader menu to see if that'll fix my boot.img, since I'm already wiped as it is. Thoughts?
Click to expand...
Click to collapse
jimbridgman said:
it will NOT let you fully boot, with out that nagging you, and you having to get into recovery and do a "normal" boot EVERY boot. The ONLY way around it is RSD lite and the n00b guide.
Click to expand...
Click to collapse
That is what I was referring to above ^^^
You can still work, until you RSDlite, but I would not re-install everything, because this should just let you do what you need to like make calls, until you RSDlite back to full stock.
jimbridgman said:
That is what I was referring to above ^^^
You can still work, until you RSDlite, but I would not re-install everything, because this should just let you do what you need to like make calls, until you RSDlite back to full stock.
Click to expand...
Click to collapse
Oh, of course, I'm just glad that it's working(ish) for now
On a related note, is RSDlite open source? How do they do what they do and why is it any different, know'm'sayin'? If they can do it, why can't we? Investigating...
Related
http://androidcentral.com/team-hydro-bootmanager-coming-soon-puts-end-bootloops-forever-hacking
Very interesting... so if we get stuck in a bootloop we could just recover from a Nandroid backup without having to revert to stock, etc.
Sent from my MB865 with Tapatalk... pardon my swype!
Too bad that wont work for us... it is in the boot.img, and we can't touch that until we get the bootloader unlocked.
Good find though.
Jim
Sent from my MB865 using xda premium
I am pretty sure my phone was bootloop and how would you get it into recovery right now? i had to use the fastboot files to do it. it is a good idea though
jimbridgman said:
Too bad that wont work for us... it is in the boot.img, and we can't touch that until we get the bootloader unlocked.
Good find though.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Ah, nevermind
But just wondering... if it's based off of CWM, and we can reboot into CWM, and we can get CWM to appear on every boot... then shouldn't we be able to get something like this to work without modifying the boot.img?
cogeary said:
Ah, nevermind
But just wondering... if it's based off of CWM, and we can reboot into CWM, and we can get CWM to appear on every boot... then shouldn't we be able to get something like this to work without modifying the boot.img?
Click to expand...
Click to collapse
Nope, if you use the razr boot hijack, it is exactly that, a hijack. It uses several "android/Linux" binaries that it "hijacks", to allow you get into CWM, just before the android UI comes up, but after the kernel is started. To get the particular hack you mentioned, working, you will have to modify the boot image, to include the recovery on boot, that will start just before the kernel is actually started/starting.
Like others have said, that since we have the fxz it does not really matter. Since I have really been doing some serious hacking and development on this phone, I have soft bricked or boot-looped my phone I can't count how many times, and even the razr CWM on boot does not always help. A good backup from CWM, and the fxz is where it is at, and really the best solution for things like this.
Most people on this site who have this phone really should not worry too much about these things, because the likelihood of doing this is very small unless you really are doing some serious hacking or development work like lfaber06 and I are. We will usually not release something to the rest of the world without testing it first, and giving explicit directions on how to do the job without bricking the phone. For those brave souls that are trying to do some dev work, and are new to it, until we get the bootloader unlocked, again the best bet is the fxz and a good backup from CWM.
Alright, so we all know it's confusing to differentiate the One XL from the One X, especially since Rogers and AT&T insist on calling it the One X.
IF YOU HAVE A "ONE X" FROM ROGERS/AT&T, YOU HAVE THE ONE XL. DON'T EVEN BOTHER VISITING THE ONE X FORUMS.
Now, you've gone and downloaded CWM from the One X forums and flashed it to your One XL, and you're semi-bricked. Let's get you out of that pickle. Please note that I have not done any of this to my own One XL, as there's no ROMs or custom recovery images or kernels for our phone yet. However, just this morning I performed a similar operation on my Jetstream, and the steps will be identical. I take no responsibility for any problems you experience.
First, you'll need to download the leaked RUU that can be found here: http://forum.xda-developers.com/showthread.php?t=1550930
EDIT: designgears has offered a newer recovery image. I'm not sure what advantages it would bring, but at least there's a second option: http://www.gigashare.in/53885
Please note that this is marked as the AT&T RUU, so there's no guarantee this will work for Rogers. However, your recovery mode is screwed anyway, so in my opinion, it couldn't hurt to try.
Once you've downloaded the RUU, run it. You don't need to install the RUU itself, we just have to have the application running. Once running, it'll create a "rom.zip" file in a temp folder somewhere in your user profile. While the RUU is open, just search for "rom.zip" and you should find it. Open this file and extract "recovery_signed.img" to your computer, into the same folder as your "fastboot" application. Once you've done this, close the zip file and exit the RUU.
Now, boot your device into fastboot mode
Code:
adb reboot bootloader
Once in bootloader mode, you may need to select "fastboot" from the menu.
Now that you're in fastboot mode, you can flash the recovery we extracted from the RUU:
Code:
fastboot flash recovery recovery_signed.img
Your screen will go through a couple brief steps, something like "sending recovery_signed.img" then "writing recovery_signed.img" and then "OK."
Try to boot into recovery now, and you should see the standard HTC recovery mode!
I really hope this helps everyone out. I'll iterate again that I have no tried this with my One XL, so I have no actual proof that this will work. But, if you've already flashed the wrong recovery image, you should be somewhat familiar with these steps already.
EDIT: Please post your success with this method. As I haven't tested, I'd like to know if everything's kosher, and I can change the instructions accordingly if something's wrong.
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
1.61.502.1 CL49502
designgears said:
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
Click to expand...
Click to collapse
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
craig0r said:
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
Click to expand...
Click to collapse
It's AT&T recovery.
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
For myself I will leave it for now and wait until an official rogers RUU or custom recovery to make sure I don't break it again
Sent from my HTC One X
bongd said:
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
Click to expand...
Click to collapse
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
craig0r said:
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
I feel your pain!
bongd said:
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
Click to expand...
Click to collapse
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
krepler said:
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
Click to expand...
Click to collapse
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
bongd said:
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
Click to expand...
Click to collapse
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
krepler said:
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
Click to expand...
Click to collapse
and the latest:
http://www.gigashare.in/0029e = Cingular 1.68.502.1 Radio 0.16.32.09.01 boot_signed.img
http://www.gigashare.in/03695 = Cingular 1.68.502.1 Radio 0.16.32.09.01 recovery_signed.img
Should've just waited and posted these ones... buuuuuuut, I have no patience.
Hopefully the boot.img works for you! Let me know how she goes.
bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
---------- Post added at 07:25 AM ---------- Previous post was at 07:22 AM ----------
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
Krepler, Can you tell me how did you solve your recovery? I am in your sisutation as well, flash the wrong recovery and once I boot to recovery and it will occur the boot loop, however I am still able to use the One X (Semi-bricked). Did you flash the stock recovery from Rogers or the one that you just posted from AT&T?
Elin28 said:
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
Click to expand...
Click to collapse
One does not interfere with the other. Recovery is pretty much its own operating system, completely segregated from the rest of the phone. It can neither hinder nor enhance the booting of your phone in normal mode. You could theoretically flash a random sequence of ones and zeros to the recovery partition, and the phone would continue to boot just fine. Until you try and go into recovery mode that is. Flashing the recovery_signed.img as per my instructions is safe in regards to the phone's normal operation. I can't promise that it's a working recovery, however, as I've not tried it myself.
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
bongd said:
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Click to expand...
Click to collapse
@bongd
Awesome bro!!!! Glad you got your hox up and running.
Sent from wherever I am!
yoohoohoo said:
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
Click to expand...
Click to collapse
Have you tried running "fastboot erase cache"?
What other steps have you done as well? The killer for me was the boot.img file that Leedroid created as part of his ROM installation. The AT&T recovery is what I had used. For a moment I thought I might need to try flashing the system.img file like redwreck had to, but I didn't need to.
Perhaps someone could upload that as well, please? If you need to flash that, it's "fastboot flash system system.img" and it'll flash that too. I always do "fastboot reboot" after as well.
I trust that these should work. Hopefully there'll be a full Rogers RUU so we can flash that just to be on the safe side. Best of luck! I'll keep an eye on this thread as well.
Since I posted earlier I've been setting things up and it's working like a damn charm. Tried exhausting every weird and quirky feature I thought might screw up, but I can't find anything that's not working.
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
jimbridgman said:
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
Click to expand...
Click to collapse
a few things.
1. it was not anything you did that made me wipe recovery, it was just me being a complete idiot
2. basically I think we need to figure out how to modify what you cat'd over. then we can pull an image from a similar device that has a true cwm recovery and edit what we need to like the specific partitions in order for it to work on our phone. then we can just cat it over and bingo! working full cwm.
3. why is it that stupid things I do always end up leading to great discoveries on here. this is like the 3rd time it has happened.
so any ideas on how to mount that file in a way we can actually look at it.
---------- Post added at 09:39 PM ---------- Previous post was at 09:22 PM ----------
Some more stuff I found: http://www.clockworkmod.com/rommanager
That has official cwm recovery builds for all supported devices. many have images, I think all the ones with unlocked bootloaders. those images would be flashed with fastboot, or probably could be cat'd over like we did.
others have flashable zips (all the moto devices) and i think those are all the ones with lockked bootloaders. I don't have tie to dig into what they really do right now, but i appears that they just copy some files for recovery to /etc and other places suggesting those devices have a different recovery method
I still think the biggest priority is figuring out how to see the contents of the images with our recovery stuff and those for other devices.
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
JRW 28 said:
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
Click to expand...
Click to collapse
what is BP tools even
Sent from my MB865 using xda premium
lkrasner said:
what is BP tools even
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've wondered the same thing????
JRW 28 said:
I've wondered the same thing????
Click to expand...
Click to collapse
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
lkrasner said:
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
Click to expand...
Click to collapse
Yea but even on a normal boot I could never get past the red moto screen, tried several times hopi g to get into CWM and not have to RSD back.
Just wierd that normal boot wouldn't work but BP tools did?
The only difference I could see is an app called CQATest in the drawer. Has many different tests available. About 50+
Sent from my MB865 using xda premium
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
lkrasner said:
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
Click to expand...
Click to collapse
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
lkrasner said:
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
Click to expand...
Click to collapse
I suspected that might be the case.
jimbridgman said:
I suspected that might be the case.
Click to expand...
Click to collapse
any ideas why.
Sent from my MB865 using xda premium
jimbridgman said:
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
Click to expand...
Click to collapse
mine gave me a ramdisk.cpio.gz and a kernel.gz, I didn't extract that. it was also a pearl script, so probably the same one.
Sent from my MB865 using xda premium
I know I have posted here way to many times. But I want to get this to work.
It seems motorola has done more weird **** to their recovery partitions. Normally you can use certain scripts and binaries to separate a boot or recovery image (they follow the same format) into the ramdisk and kernel. That SHOULD be all that is in them. you can then modify the ramdisk to your liking, or use the kernel with cwm or the like to make it work. However it seems there is more to our image than just the ramdisk and kernel. when I extract them and repack them it seems to work fine, but the result is 5.5MB instead of 9.4MB with no modifications.
Does anyone have any idea what the deal is with that? I think if we can figure out that part we should be able to get a true custom recovery.
P.S. are you sure we cannot replace our boot.img with this same copying method? That is if we could even figure out how to modify it. Is there a hardbrick risk in trying? if so, Any volunteers?
EDIT: so our boot image will unpack and repack to the same exact size, so I think that means we could theoretically edit the ramdisk if that would do any good. the question still remains whether the phone checks its signature on boot or only upon flash
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Harrison85 said:
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I can make a small change that would make it un verified then someone could copy it over and see if it boots. the problem is I am not 100% sure we would be able to restore to the original if it would not boot. I am 99% sure we would be fine, but I don't want to risk bricking completely. My guess is jim will know if it is safe to test or even worth trying, but if you want to be the guinea pig just tell me and I'll send you instructions.
By all means throw Me instructions and I will give it a shot right now
Sent from my MB865 using xda premium
Nevermind. I was sort of wrong. Both images separate just fine and can be recombined, but extracting the ramdisk seems to not extract the whole thing, it is much smaller when it is repacked. therefor you cannot really edit it at all.
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
lkrasner said:
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
Click to expand...
Click to collapse
That is it in a nutshell. They pack their boot image in a different way from all other phone manufacturers, and not in a standard way for android. That is why Moto has their own "special" non-standard bootloader. They use a bitblast to package the boot image files, on top of the standard tgz, so the important files are "zip blasted" on top of the others in "superbit blocks", so there is not much we can do, unless we can de-a-line them, but that is not something I even want to start poking at.
Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.
First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).
WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?
If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?
See weekends mirror thread
Sent from my Nexus 4 using xda premium
I'm lost.... Phone is stuck at the red electric eye animation. I can so a hard reset, actually did that several times, but the phone always stops in this animation. I haven't changed anything in a while other than downloading an app to reboot the device with one touch. The Phone is unlocked and rooted, but nothing beyond that.
Any ideas?
Thank you,
David
I've never seen this before. Usually only happens on bad recovery installs, ROM installation, or other flash. The only thing I can recommend is a flash of the stock image with RSD lite.
Wait for some other replies though.
Thanks, i would definitely have to research how to do that.
I can get to the boot menu, but all options... recovery, fast boot and factory all get stuck at the electric orb/eye animation.
davfed said:
Thanks, i would definitely have to research how to do that.
I can get to the boot menu, but all options... recovery, fast boot and factory all get stuck at the electric orb/eye animation.
Click to expand...
Click to collapse
If you can't even get into recovery, then definitely it means it's time to go into fastboot mode and flash a stock image back onto it.
You can get to fastboot mode by rebooting the phone (or powering on) and then immediately press vol down + power and that will get you into fastboot mode where you can use either RSDLite or House of Moto tools to flash a stock image back onto your phone.
That seems to be the only recourse.
OK, downloading RSDlite and installing now. Im in AP fastboot flashmode on my phone. I have the latest device drivers from Motorola installed.
So, this whole finding and flashing new image thing is beyond me, i will search for it, but if anyone has an easy explanation, i would greatly appreciate it.
Edit: Ok, i found the correct image to flash. I'm assuming that it is the complete OS? if that is the case, I'm going with the last version where I had almost double battery life. Am i on the right track?
So basically you are going to download a 700mb stock image. Go to http://sbf.droid-developers.org/phone.php?device=5 for that download. That will be what you are flashing
Sent from my DROID RAZR HD using Tapatalk
Thank you so much Sad Panda!!!
I'm flashing 4.4.2 instead of the last version I was planning on. It's in process now so I'll know soon.
If this works, then I will look for a custom rom without all the bloatware and other garbage. I suppose this failure has made me do something that i have always been too nervous to try.
I know that asking questions without searching is frowned upon, and I get that, but having someone to interact with is very reassuring.
Again, many many thanks to you for your time!!!!
Not a problem. I have a question out there right now waiting to be answered, so it's appropriate for me to give back
Sent from my DROID RAZR HD using Tapatalk
It worked. You are my hero Mr. Panda!!!
Thank you!!!
except sbf doesnt have the .15 update yet...but can be found here: http://www.droidrzr.com/index.php/topic/54379-fxz-442-1834615/
cmh714 said:
except sbf doesnt have the .15 update yet...but can be found here: http://www.droidrzr.com/index.php/topic/54379-fxz-442-1834615/
Click to expand...
Click to collapse
is it worth reflshing to get the .15?
I'm halfway to setting my phone back to the way it was.
davfed said:
is it worth reflshing to get the .15?
I'm halfway to setting my phone back to the way it was.
Click to expand...
Click to collapse
IMHO, nope, no real reason if everything is working well.....there was a security fix however.
http://www.verizonwireless.com/dam/support/pdf/system_update/droidrazrhd-09-09-14.pdf