Database Info

[RECOVERY] Modified 3e Recovery

Dani897 has already made a discussion of this, but I'm moving this information over as an official post in the Infuse 4G section as well.
This is from existz/untermensch's thread. I take no credit. See here for more info http://forum.xda-developers.com/showthread.php?t=909213
Making this modification will allow you to flash un-signed .zip files due to signature verification being turned off. (3e requires root)
* Download and extract the .zip
* Use a terminal emulator or ADB Shell and mount system as read/write.
* For backup purposes, use adb or root explorer to rename the current recovery file in /system/bin to recovery.orig
* Use a file manager (Root Explorer) and copy the new recovery file to /system/bin
* Reboot and your 3e (Froyo stock) recovery will no longer require signature checking.
You can now use this recovery or use the CWM from Captivate (posted in another thread here).
I am not responsible if this bricks your phone. This is easy cheese...just follow these steps.
Download:
3e Recovery w/o signature verification
Youtube video using Root Explorer from gtg465x (Make sure to Thank him!!)

You actually tested this on an Infuse?

DarkH2O said:
You actually tested this on an Infuse?
Click to expand...
Click to collapse
Yes. it is working on mine right now.

i already tested this days ago and cwm
except using truselos super easy batch script to make it even more easy for people to use.
http://forum.xda-developers.com/showthread.php?t=1086622
still there is disbelief. yes people it works! im not sure what trouble people are having flahsing roms but cwm and 3e can flash .zip files just fine. i expected to see some flashable mods and themes by now. i have successfully flashed files for testing purposes and im not too advanced of a user. i planed to post some things like a market fix and such but i have been disrtacted.

Dani897 said:
i already tested this days ago and cwm
except using truselos super easy batch script to make it even more easy for people to use.
http://forum.xda-developers.com/showthread.php?t=1086622
still there is disbelief. yes people it works! im not sure what trouble people are having flahsing roms but cwm and 3e can flash .zip files just fine. i expected to see some flashable mods and themes by now. i have successfully flashed files for testing purposes and im not too advanced of a user. i planed to post some things like a market fix and such but i have been disrtacted.
Click to expand...
Click to collapse
Dani, i completely agree. If you notice, I made mention of your testing at the top of the article.
Now that there is a dedicated thread, its much more likely to be realized that this works FINE. I think once I get a tester for the Odin package I slapped together to get us back to stock in case we brick, and get it successfully setup, i'll put a thread out and we can REALLY get to work on some ROMs.
So far, this phone's software is nearly identical to the Captivate, meaning we will just need to port from the Captivate and we will have a mass of ROMs in no time!

h8rift said:
Dani, i completely agree. If you notice, I made mention of your testing at the top of the article.
Now that there is a dedicated thread, its much more likely to be realized that this works FINE. I think once I get a tester for the Odin package I slapped together to get us back to stock in case we brick, and get it successfully setup, i'll put a thread out and we can REALLY get to work on some ROMs.
So far, this phone's software is nearly identical to the Captivate, meaning we will just need to port from the Captivate and we will have a mass of ROMs in no time!
Click to expand...
Click to collapse
as soon as we get some kernel dev on this thing i agree. porting will be easy. thanks for the write ups too. are you planning to get a second phone? i would test if i had two of them. my captivate will go to my brother, if it weren't for that id have probably bricked it and begged some people to try making new odin packages for me to fix it.
i understand that after a brick the user hates not having the phone and may be very tempted to return it but it is helpful to everyone to try all you can to recover it. if mine bricks im using the insureance plan and saying it was stolen, then i will have a dedicated test phone.

I have an Atrix as well, but would prefer someone who may have already bricked to try this package that i wrote up this morning.
I dont mind someone wanting to swap.their phone...but i literally need about an hour or two of time with the brick's user and its very likely that we will have working Odin....and then you and i...as well as others... can do kernel and rom deving nearly immediately. We have source already, so we only need to test this safety net . PM me if you find someone who is bricked or is willing to test!!
-h8
Dani897 said:
as soon as we get some kernel dev on this thing i agree. porting will be easy. thanks for the write ups too. are you planning to get a second phone? i would test if i had two of them. my captivate will go to my brother, if it weren't for that id have probably bricked it and begged some people to try making new odin packages for me to fix it.
i understand that after a brick the user hates not having the phone and may be very tempted to return it but it is helpful to everyone to try all you can to recover it. if mine bricks im using the insureance plan and saying it was stolen, then i will have a dedicated test phone.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App

I have a bricked Infuse im not sure what caused the crash. I was running stock rooted by the super one click method and was uninstalling an app when it went all black except the bottom keys. Doesnt do much of anything else now. I attempted an odin fix someone suggested to no avail. I can get into download mode still but nothing else. Id be willing to try anything to unbrick it .

it's working for me, I unzipped, put the file in my dropbox, downloaded the file on phone from dropbox, used root explorer to mount, (I'm already rooted) copied the file, went to system/bin, renamed the original, then pasted the new file, rebooted, flashed CWM to captivate, and rebooted into recovery, and it works. I still have my HTC Inspire, i'm on a 30 day run here to see if i like the infuse. So far it's the best GPS i've had, and i've had a lot of phones. I hate to think I spent 600 bucks on a another captivate. I had that phone as well, but so far i really like it.

Realityfalse said:
I have a bricked Infuse im not sure what caused the crash. I was running stock rooted by the super one click method and was uninstalling an app when it went all black except the bottom keys. Doesnt do much of anything else now. I attempted an odin fix someone suggested to no avail. I can get into download mode still but nothing else. Id be willing to try anything to unbrick it .
Click to expand...
Click to collapse
if you can get into download mode I personally would try running the captivate odin and see what happens, buts that's just me lol. I'm a risk taker lol.

What commands do you use in ADB to mount system as read/write?

budco2000 said:
if you can get into download mode I personally would try running the captivate odin and see what happens, buts that's just me lol. I'm a risk taker lol.
Click to expand...
Click to collapse
dont do that. you dont want the captivate param.ifs on here. you may loose download mode if the boot parameters get messed up. especially dont flash anything with bootloaders, that means no one click nad no 3-button fix roms. this may be similar to the galaxy s but there are atleast a few differences in hardware layout that would make that a bad idea. for instance this can run gps and camera during phone calls. the sgs cant so the way things comunicate on the board may be differet, it may also just be differences in the kernel or framework but we cant be sure.

Dani897 said:
dont do that. you dont want the captivate param.ifs on here. you may loose download mode if the boot parameters get messed up. especially dont flash anything with bootloaders, that means no one click nad no 3-button fix roms. this may be similar to the galaxy s but there are atleast a few differences in hardware layout that would make that a bad idea. for instance this can run gps and camera during phone calls. the sgs cant so the way things comunicate on the board may be differet, it may also just be differences in the kernel or framework but we cant be sure.
Click to expand...
Click to collapse
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!

h8rift said:
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!
Click to expand...
Click to collapse
yaaay
ok now we can get all crazy with few worries. good to hear!

Dani897 said:
yaaay
ok now we can get all crazy with few worries. good to hear!
Click to expand...
Click to collapse
Yes. That's a major hurdle.

h8rift said:
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!
Click to expand...
Click to collapse
Sweet! So the dump was good then it sounds like. So just to sum it all up, odin the pda tar and it restores and wipes EVERYTHING!
Woops! AND DEODEXED!!?!?

I'm pretty new to all of this, but here is how I did it. Make sure you have busybox installed!
Extract the "recovery" file to your phone's internal SD card.
On your phone, go into your terminal emulator.
Type in "su" and press enter.
Type in "cd /sdcard" and press enter.
Type in "mount -o rw,remount /dev/block/stl9 /system"
Type in "cp -f recovery /system/bin" and press enter.
Reboot your phone.
Maybe this will help someone. Maybe it's not even the right way to do this, and my phone will soon explode. I'm a pretty big noob with this, so someone let me know.
PS: If you brick your phone, it isn't my fault.

Hi I came from iPhone 4 and like 2days owning this infuse, I am trying to follow gtg465x to install his ROM, I am done with the rooting and his next step is to "install 3e recovery" now that I am here I am totally lost, I downloaded the file here my Questions are:
1.where do I extract the zip I donwloaded from here? From the SD card root?
2. What thing will I use Terminal emulator or ADB SHELL to make it read/write is that 2 an Android apps I'm lost here. I am trying to be careful, I searched and found too much post and way different doing this. So now I am confuse.
Can anybody tell me how it install 3e recovery the easy and idiot proof way, like I said I am new to android I really have no idea about everything, and most of them too are initial I don't even know what the initials means. Anyone? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

spirikitik said:
Hi I came from iPhone 4 and like 2days owning this infuse, I am trying to follow gtg465x to install his ROM, I am done with the rooting and his next step is to "install 3e recovery" now that I am here I am totally lost, I downloaded the file here my Questions are:
1.where do I extract the zip I donwloaded from here? From the SD card root?
2. What thing will I use Terminal emulator or ADB SHELL to make it read/write is that 2 an Android apps I'm lost here. I am trying to be careful, I searched and found too much post and way different doing this. So now I am confuse.
Can anybody tell me how it install 3e recovery the easy and idiot proof way, like I said I am new to android I really have no idea about everything, and most of them too are initial I don't even know what the initials means. Anyone? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
I came from an iphone as well, about 2 weeks ago. I used the method posted in my previous reply. It worked for me, and has been doing fine so far. One thing you must do is make sure busybox is installed before you try it though. If you dont have busybox installed, none of the commands will work. Then just download "Terminal Emulator" from the market, and use that to give commands.
Sent from my SAMSUNG-SGH-I997 using XDA App

Cohdee said:
I came from an iphone as well, about 2 weeks ago. I used the method posted in my previous reply. It worked for me, and has been doing fine so far. One thing you must do is make sure busybox is installed before you try it though. If you dont have busybox installed, none of the commands will work. Then just download "Terminal Emulator" from the market, and use that to give commands.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
What command? I really have no idea, can you give me step by step if you don't mind?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Check this out...

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.

[SOLVED] Fix softbricked MB865

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...

Working custom kernel(s) for Motorola Updated system?

Hi all.
I wanted to thank all of the devs and modders on this device forum for all your hard work and feedback.
I have the unlocked/software updated/rooted/deodexed system, now I am wondering if your custom kernels will be compatible with the
system update? I tried the AdrenalineInjector sans Fugo option, ummmm.....nope. Didn't like that at ALL lol.
Let's hear it for Nandroids.
I have, well, more than my share of Nandroids and working TWRP recovery, so I am confident to the point of reckless with experimental flashes/mods. I have just tweaked out my DeOdexed system with the power boot menu, and just finished customizing my launcher, homescreen, apps, etc.
That being said, I am doing yet one more Nandroid of this one and trying both aaarrrggghhhs kernel (I apologize for the misspell) and shabby's p's and q's kernel.
I will post an update of either "woohoo!!" or "nnnyohhhhhh..."
Keep the mods coming, I am ready to try them all!
drakeheart77

drakeheart77 said:
Hi all.
I wanted to thank all of the devs and modders on this device forum for all your hard work and feedback.
I have the unlocked/software updated/rooted/deodexed system, now I am wondering if your custom kernels will be compatible with the
system update? I tried the AdrenalineInjector sans Fugo option, ummmm.....nope. Didn't like that at ALL lol.
Let's hear it for Nandroids.
I have, well, more than my share of Nandroids and working TWRP recovery, so I am confident to the point of reckless with experimental flashes/mods. I have just tweaked out my DeOdexed system with the power boot menu, and just finished customizing my launcher, homescreen, apps, etc.
That being said, I am doing yet one more Nandroid of this one and trying both aaarrrggghhhs kernel (I apologize for the misspell) and shabby's p's and q's kernel.
I will post an update of either "woohoo!!" or "nnnyohhhhhh..."
Keep the mods coming, I am ready to try them all!
drakeheart77
Click to expand...
Click to collapse
You didn't like the adrenaline injector? I just flashed that and I really don't see any negative effects so far.
What didn't you like about it?

None that work completely. You can flash arrrghhh's kernel if you'd like. You can overclock up to 1.89 GHz and underclock down to 96 MHz ... but it will break your wifi until the kernel gets updated. I'm not sure how long that will take though. Other than that, everything else works perfectly fine on it. Other than that, I believe a few options are in the works, but nothing's been finaled yet.

It wasn't that I didn't like Adrenaline, it's that it wouldn't boot lol. I don't think I did a proper clean before installing, plus my question is since my system is already deodexed, would it do more harm than good?
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Sent from my XT897 using xda premium

Please don't post question threads in the Development sections as they have no place there and we have a Q&A section designed for all your questions.
Thanks
AvRS

drakeheart77 said:
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Click to expand...
Click to collapse
The only reason the wifi won't work on the update with the old kernels is because of the changes the update made. Any ports should have that issue resolved prior to release, and once stable depending on what gets updated I doubt we'll run into kernel/wifi issues although I cannot guarantee that. I know the current OTA made changes to the modem drivers which I'm sure is part of the reason the kernels are incompatable.
I know when I was running the OTA and broke my wifi and tried restoring the stock boot.img (with original oem kernel) it wouldn't even boot the updated system. They're almost like two completely different softwares with the same UI lol.

How do we get new updated stock boot and recovery images? I rely on restoring pre-update Nandroids for whatever flub I may have yet to pull off lol. Anything I can do to help.
Sent from my XT897 using xda premium

drakeheart77 said:
It wasn't that I didn't like Adrenaline, it's that it wouldn't boot lol. I don't think I did a proper clean before installing, plus my question is since my system is already deodexed, would it do more harm than good?
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Did you replace the update binary?

Sorry for the laziness on my replies. All I did was cache/dalvik wipe and success.
However I do need some help, I am uploading to Dropbox my non-rooted system and boot images. How do I share the links to my DP URL?
Also, where do I locate the stock recovery? Wouldn't the recovery be the same, because it wasn't a total ROM/system revamp? if that is the case then shabby has posted links for stock system and boot.
Sent from my XT897 using xda premium

Oh btw the files are for the 77.1.80 system update and NO root, and completely bare and odexed.
Sent from my XT897 using xda premium

http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium

drakeheart77 said:
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Seeing as its been a while since I have had to do anything manually (so spoiled these days!)
I know I can use fastboot to push the img for the recovery, but how do I go about getting the system/boot flashed over?
Thanks!
EDIT: TBQH, never had to deal with .win files...

Hammerfest said:
Seeing as its been a while since I have had to do anything manually (so spoiled these days!)
I know I can use fastboot to push the img for the recovery, but how do I go about getting the system/boot flashed over?
Thanks!
EDIT: TBQH, never had to deal with .win files...
Click to expand...
Click to collapse
You need the TWRP recovery installed. If you've never used it before, you'll need to make a backup in order to generate the correct folders necessary. The directory will be either on your memory card (/external1) or internal memory (/sdcard). The folder path will be TWRP/BACKUPS/**your**phone's**serial**number**/
Inside that folder, create a folder and name it "stock backup" or whatever you want to name it. Then put the *.win and the *.md5 files in there. Put the stock recover in whatever folder you have your adb installed.
Reboot to recovery.
Restore the boot and system partitions from this backup (will show as "stock backup" or whatever you named it)
Once the restore is complete, back out to the main menu ... go to reboot -> choose bootloader
Flash your stock recovery ( fastboot flash recovery **whatever you named your recovery file**.img )
I typically flash this twice one right after the other just in case​
Reboot your system ( fastboot reboot )
From there you should be all set.

drakeheart77 said:
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the files Drake!
However, I must be missing something because I flashed that system file and when I go to about phone it shows 7.7.1Q 8/3/12 not 7.7.80.
I'm pretty sure I flashed it right because I lost root and got back a bunch of the stupid Sprint stuff that I had removed and got your spiffy boot logo. I'm thinking about doing the OTA update from this baseline with stock recovery and then reinstalling twrp and re-running root.
*edit*
And that just put me back to infinite reboots again. I'm going to delete the stupid update from cache again and cut my losses for now, I've been up 22 hours so perhaps a fresh look tomorrow will help.

Not sure about the update not being there...don't know if that is system-specific or not all I know is that I made that back-up after the update was installed. Please leave any other feedback thank u for the reply. I may try and post a new system file.!
Sent from my XT897 using xda premium

Were u looking at the Build # or SW Version in "settings/about phone"?
The only thing simple is the belief in simplicity.

Also u cannot install Any OTA updates with ANY custom recovery on this phone. Stock recovery is necessary that's why I posted the image.
The only thing simple is the belief in simplicity.

afidel said:
Thanks for the files Drake!
However, I must be missing something because I flashed that system file and when I go to about phone it shows 7.7.1Q 8/3/12 not 7.7.80.
I'm pretty sure I flashed it right because I lost root and got back a bunch of the stupid Sprint stuff that I had removed and got your spiffy boot logo. I'm thinking about doing the OTA update from this baseline with stock recovery and then reinstalling twrp and re-running root.
*edit*
And that just put me back to infinite reboots again. I'm going to delete the stupid update from cache again and cut my losses for now, I've been up 22 hours so perhaps a fresh look tomorrow will help.
Click to expand...
Click to collapse
I'm having/had the same exact results.
Just got the phone today, rooted it, installed CWM, then decided to do the update not realizing the issue that would cause. Of course it failed in CWM and then I got into a reboot loop.
Flashed TWRP, restored the files listed here, got me back to a bootable ROM. Then, downloaded the update, told it to apply, shuts down,...bam,...boot loop. :silly:
All I want to do is get back to a completely stock (unlocked bootloader is fine), so I can update to 7.7.80, then mod & tweak from there.
This phone is so dang frustrating after coming from an Epic which was pretty brainless to flash. This Photon is kicking my butt..

Finally got past it, not sure how...then I fubar'd it again by trying to do the 1% & toggle mods. Ugh...so frustrating..

Just putting this out there, may not be true for all phones, but with my Q I got a lot of boot loops restoring backups from my external sd card, the ones I restored from internal storage worked okay. Obviously it could be corruption with the backups/sd card as well. With the toggles make sure you flash the toggles for the updated systemui and framework files and not the stock system files if you have taken the ota update. In other words make sure you match the version of the mods to your current software version. I found this phone very frustrating from a modder's perspective at first, I have really come to love the qwerty and hardware over time... the Snap Dragon s4 is fast!
Sent from my XT897 using xda app-developers app

[Q] First time rooting/S-Off/new ROM

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