Related
I know we have no way of getting back to stock since we don't have an FXZ yet but why couldn't we use the stock Android recovery upon boot then use our nandroid backup from the ATRIX 2 bootstrap incase someone is stuck on a bootloop or messes their phone up? Would this work?
It sounds plausible, we just need someone that is still within their 30 day return time that has the nerve to try it. They would have to do a nandroid then purposely soft-brick and hope and pray I guess.
Well I dont remember being able to do this on my OG Atrix but today I was messing around and powered my phone off. I was wanting to get to the boot option screen so I could boot into stock recovery. Well I did and got the usual green man with a triangle. Then I proceeded to push the same buttons that got me to the boot option screen and then the stock recovery menu showed up just like CWM recovery. Was we able to do this on the OG Atrix because I dont remember?
In the Droid razor forums they have a way to boot cwm on power up. Ill post the link later. Why couldn't we port that to our phones?
Sent from my MB865 using Tapatalk
lfaber06 said:
In the Droid razor forums they have a way to boot cwm on power up. Ill post the link later. Why couldn't we port that to our phones?
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
If what I have just done will work we can do the same thing upon boot without having to port anything.
We should be able to flash any zip located on the sd card upon boot via the stock android recovery.
Hoping someone with a lil more knowledge of this stuff will chime in here
The stock recovery wont work for a few reasons the biggest is you cant backup and restore. We need cwm no question about it. we need this on our phones.. http://forum.xda-developers.com/showthread.php?t=1385283
I have been talking to hashcode about porting his safestrap method from the droid 3 to our a2's. That would work even better because then we'd be able to restore to stock w/o an fxz or sbf.
Why can't you restore with the stock recovery? We can create backups through our bootstrap so that isnt a problem and it works just fine. But we have no option at boot which is the problem. Look at my last pic. That is my nandroid backup through our bootstrap.
I'm Uploading a video to youtube of what we need.. Hold tight. And I thought you couldn't use backups created from other recoveries?
http://youtu.be/H3fIdf5fQ70
So this is the droid 3 safestrap from hashcode working on my A2. I have been able to make backups that are actually 300mb more then the bootstrap cwm backups. I have Not tried restoring backups using it. I have replaced my phone 4 times now with best buy I don't want to try again.. I have sent hashcode some files he requested to hopefully port this over to the A2.
Check it out!
http://forum.xda-developers.com/showthread.php?t=1315982&highlight=safestrap
I'm not trying to spam the board here it just looks like this would really work for us.
lfaber06 said:
And I thought you couldn't use backups created from other recoveries?
Click to expand...
Click to collapse
THAT is what I don't know?
Yes I'm familiar with hashcodes safestrap and if he can get it ported to our A2 then that would be exactly what we would need. I was thinking hard about asking him for help myself. So I'm glad you did
I know just enough about this stuff to be dangerous, as in making paperweights with phones
LoL
DONE SOME DIGGING AROUND AND I've ANSWERED MY OWN QUESTION. NO IT WON'T WORK. STILL LEARNING EVERYDAY :/
JRW 28 said:
THAT is what I don't know?
Yes I'm familiar with hashcodes safestrap and if he can get it ported to our A2 then that would be exactly what we would need. I was thinking hard about asking him for help myself. So I'm glad you did
I know just enough about this stuff to be dangerous, as in making paperweights with phones
LoL
DONE SOME DIGGING AROUND AND I've ANSWERED MY OWN QUESTION. NO IT WON'T WORK. STILL LEARNING EVERYDAY :/
Click to expand...
Click to collapse
Was bout to say I'd give it a shot for you guys was exchanging my phone today but guys you got it figured out anything changes before end of day lemme know
Sent from my MB865 using xda premium
JRW 28 said:
If what I have just done will work we can do the same thing upon boot without having to port anything.
We should be able to flash any zip located on the sd card upon boot via the stock android recovery.
Hoping someone with a lil more knowledge of this stuff will chime in here
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1349439
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.
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...
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
DX2Trip said:
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
Click to expand...
Click to collapse
Hey, and sort of welcome back...
But I hate to be the bearer of bad, bad news... you have a softbrick, and there is NOTHING you can do.
Next time, read everything in an OP... LOL, look who I am telling this to....
The CM10 installs come with their own CWM built in, and flashing bootstrap is what bootlooped you, so after you get another warranty replacement (yes, you HAVE to do this), I would install leak #1 ONLY, then flash cm10 with bootstrap, then do not reinstall any boot hijacks or CWM "like" recovery (bootmenu), because all you have to do it hit the vol down button right as you see the blue led flash during the M dual core logo.
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
tcf38012 said:
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
Click to expand...
Click to collapse
he can't, he installed bootstrap while on cm10m, so he can't get to cwm anymore.
Scratch that ----- Deleted
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
DX2Trip said:
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
Click to expand...
Click to collapse
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
jimbridgman said:
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
Click to expand...
Click to collapse
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
lkrasner said:
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You know, I was seeing in recovery how youbcan flash an update through sd AND system which has a lost and found folder and recovery folder. Dont know if this is of any info but either way because I wouldnt know how to put anything in system since I cant seem to get adb to recognize or moto-fastboot...I'm in a very confused state of mind and almost came to the point of hard brick but I refuse. I'll leave it up to ya devs. Thanks againg everyone.
Sent from my MB870 using xda premium
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
justdrew said:
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
First Softbrick it seems In Trouble
jimbridgman said:
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
Click to expand...
Click to collapse
Guys need your urgent help i am into a trouble what is it called technically may be a Soft brick but this is what has happened.
I was trying the Magic mod the installation went superb booted the phone it worked properly and then i used the bootstrap :silly: and tried starting the phone in recovery after which my phone is now stuck at magic mod boot animation. PLEASE HELP.
I am upto a point where have installed drivers latest rsd lite 6.0 ready with the extracted fxz 6.7.2_EDEM-18-SEARET_cfc.xml but phone is not showing up in rsd lite so that i can flash my phone. Phone says USB connected in AP Fastboot mode have a look at the attachment of my desktop. Please HELP guys....
Thanks & Regards,
Beginner Android (Ravi D)
havent you just posted this in the any question answered here thread and getting help there ??
Wow, almost forgot I made this thread lol. But sounds like your drivers need a good updating. Reboot PC after updating and try again is all I can say. Hope this helps.
Sent from my MB865 using xda premium
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