Develop Bugs

[Q] bootloader bypass?

I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097

masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.

how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?

RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App

crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community

littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it

crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.

Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium

Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.

eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium

eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App

crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d

If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/

Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.

crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.

Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.

Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....

mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.

Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.

mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..

Where's all the ROMS!

We need more development!
Sent from my LG-P930 using XDA App

I mean WHERE ARE ALL THE ROMS! terrible grammar
Sent from my LG-P930 using XDA App

Instead of asking. Why don't you learn to develop one? Then, there would be more.

Was that a question? Cause last time I checked a question supposed to end with a question mark: "?"
Anyhow, first thing first, we need figure out what's the deal with boot loops, when that solved then we could move on forward with the roms.
Right now I'm on stock rom, and I know if I reboot or shutdown the phone, I'll need go through CWM to restore last backup, because it will boot loop. Fortunately unbricking process still works on my phone, my understanding that few people already hard bricked their phones after installing a custom rom...

[email protected] said:
Was that a question? Cause last time I checked a question supposed to end with a question mark: "?"
Anyhow, first thing first, we need figure out what's the deal with boot loops, when that solved then we could move on forward with the roms.
Right now I'm on stock rom, and I know if I reboot or shutdown the phone, I'll need go through CWM to restore last backup, because it will boot loop. Fortunately unbricking process still works on my phone, my understanding that few people already hard bricked their phones after installing a custom rom...
Click to expand...
Click to collapse
I'm in the same boat too. I've customized my stock rom, but can't really reboot. The best thing I can do is quick boot to CWM then reboot from CWM.

[email protected] said:
Was that a question? Cause last time I checked a question supposed to end with a question mark: "?"
Anyhow, first thing first, we need figure out what's the deal with boot loops, when that solved then we could move on forward with the roms.
Right now I'm on stock rom, and I know if I reboot or shutdown the phone, I'll need go through CWM to restore last backup, because it will boot loop. Fortunately unbricking process still works on my phone, my understanding that few people already hard bricked their phones after installing a custom rom...
Click to expand...
Click to collapse
I was having a bunch of problems with bootloops after a reboot. Since I formatted /data through ADW and reflashed a rom, i havent had any more
Sent from my LG-P930 using XDA App

red_solo_cup said:
I was having a bunch of problems with bootloops after a reboot. Since I formatted /data through ADW and reflashed a rom, i havent had any more
Sent from my LG-P930 using XDA App
Click to expand...
Click to collapse
But you didn't restore your data after that, correct? You just started fresh?
The factory rest and formating /data is the same thing as far as I could tell...

@[email protected]
That is correct. Right after flashing I restored backups through titanium backup. It solved the problems I was having, but I can't say for sure it will work for everyone.
Sent from my LG-P930 using XDA App

I'm gonna hijack this thread and derail it, for now. Red_solo_cup, was your username inspired a certain song sang by a certain quirky country singer by the name of Toby Keith? hehe

aquariuz23 said:
I'm gonna hijack this thread and derail it, for now. Red_solo_cup, was your username inspired a certain song sang by a certain quirky country singer by the name of Toby Keith? hehe
Click to expand...
Click to collapse
Haha, no way. I may have to retire this handle...
I don't listen to country.

I gave up on looking for anyone to support this phone, much less the Bell version. I'll wait for ICS to be released, and revert back to a manufacturer that has developer support within the next year or so.

red_solo_cup said:
Haha, no way. I may have to retire this handle...
I don't listen to country.
Click to expand...
Click to collapse
LOL! Dang! Well, it's a funny song nonetheless.
---------- Post added at 09:25 AM ---------- Previous post was at 09:10 AM ----------
LiViD said:
I gave up on looking for anyone to support this phone, much less the Bell version. I'll wait for ICS to be released, and revert back to a manufacturer that has developer support within the next year or so.
Click to expand...
Click to collapse
I haven't really given up just yet, but the slow down we are currently experiencing after the excitement of achieving CWM backup and Custom ROMs is eating me up inside. We have lost momentum on the development of new ROMs or Kernels or Mods for this phone, and in all honesty, is quite disheartening. I am grateful for the things we have obtained for this phone and to the Devs and Users who have come over to help us achieve them, but we need more, and I know we can get more. There must be something we can do, people we can speak with. I know it is hard for Devs to create something without physically having the phone in their hands so I understand why things are progressing so slow, and hopefully soon some of them will pick up this phone as well.
Let's try to reach out again to Devs that we know from other threads to help us out with new things to use. We seem to especially need custom Kernels for this phone, so let's find those who can do kernels. Let's not give up hope yet, let's keep trying and jump start this forum back to life.

Rooting Gnex GSM/HSPDA v4.0.2 Optus Stock

Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)

Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.

Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)

Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.

Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!

I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium

Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.

What does stock stand for?

udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.

mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App

Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.

El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App

Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.

mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....

Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.

Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)

Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.

Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)

Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.

I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.

[RECOVERY] TWRP-2.7.0.0-moto_msm8960-hdpi.img YOUR, pre Nov 8, TWRP IS BAD!

Update twrp 2.7, see Dhackers link for the img. Use Recovery Tools from Play to flash from home.
Seems that only Dhackers latest TWRP is the one to use.
Thanks to cyanidium for making it evident to me anyway.
Dhackers msm8960 goodies: http://androidhosting.org/Devs/Dhacker29/msm8960/
BTW Does anyone know what "twrp263-M44.img" is?
Attachments: the ...M44 is 1 day newer & works.
Just extract these to get the fastboot img.
More details
http://forum.xda-developers.com/showthread.php?t=2612883
More conformation http://forum.xda-developers.com/showpost.php?p=49978993&postcount=79
This one is not Dhacker latest anyway :
http://forum.xda-developers.com/showpost.php?p=45688558&postcount=1
Md5 starts with 791.
Want to try Philz.
http://forum.xda-developers.com/showthread.php?t=2545120
Want The latest 2631? w/ SDext usb mount. What is the rub?
This Photon Q TWRP, with full SD mount & more, works on the M! See attachments for the flash-able ver. Now for the rub: screen input requires the mirror of the buttons. I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL.... It is really not that hard to use. Think of it as a game also.
Md5 : 7630baf88ec9d6c2a144a2ee86ec9bb7

I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
No settings, just bad! Thanks for the conformation Watson! We on a train with a new engine!!!

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
How long have you known about it?

aviwdoowks said:
How long have you known about it?
Click to expand...
Click to collapse
I came across this issues first time trying to flash Paranoid and Pacman.
Which left me soft Bricked or in Bootloops. At the time i was just too fed up and went back to stock
second time i encountered that, was with the first stable KitKat by Dhacker.
That's when i decided to start clean and deleted all my Pre downloaded files and I was forced to download the new E33 from Dhacker.
And along with that all my other Roms and Files. I kind of figured something was bad with my TWRP file. But never thought of it since 791 wasnt found by my search engine.
And this December when I was flashing my GFs phone that's when I confirmed that the 791 didn't work for any of my roms.
Because I couldn't find Dhackers E33 through Google.De search (Some odd way searches come up differently if you search from different country)
And it did the same issues I had the First time around. That's when i dug around more and found Dhackers TWRP.
After using that I was able to flash Roms like a mad man until I found a Rom that my GF was comfortable using and liked.

Germanese said:
I came across this ....GF was comfortable using and liked.
Click to expand...
Click to collapse
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Ohh well now we all know!
Thanks again for the history.
This screwed up my data partition & I could not determine if it was philz or this. Then I decided the stop one, as I would go to the other & then data restore failure, so I used just philz & the problem went away!

aviwdoowks said:
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Click to expand...
Click to collapse
Nah i didn't post about it back then and recent we were side tracked ahahaha.
And I actually just got back couple days ago ... work ugh hate it already ...
There maybe a post few months back, me asking somewhere about which TWRP people are using,
because I had my doubt on which one to use; but no one really bothered to respond.
Then i just decided to flash away with what ever, since most errors resulted in an Harmless SoftBrick.
Since i figured a way around to that soft-brick, my thought was, what worse could happen, I did worse before LOL
I won't take credit, just stumbled upon it... That's all you. Just here to Confirm that i did have issues with that version.
Since then I been trying to see CWM for KitKat LOL

Hmm...
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?

Twilla said:
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Click to expand...
Click to collapse
Yes or the e33.
Not sure which is better. Philz is newest & I have an ini file to help you set it up see #2 post.

Update.
Haha. But not a joke. PHOTON Q twrp 2631 up.

twrp 2631 maybe provided by arrrghhh!
http://forum.xda-developers.com/showpost.php?p=49857073&postcount=176
If you want to be synched to his Q versions, go thank him!
That means a good screen version for our m.

Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!

Coronado is dead said:
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Click to expand...
Click to collapse
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.

aviwdoowks said:
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
Click to expand...
Click to collapse
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.

Coronado is dead said:
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Click to expand...
Click to collapse
May I suggest philz new version just out.
Allows you to format many /'s now.
I use only it now.
Not pocket proof like twrp. Beware

New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907

aviwdoowks said:
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
Click to expand...
Click to collapse
It works fine (I have flashed Dhackers *img) but if we want to flash any ROM we must change updater.script and add moto_msm8960 to device list on it.
I have success flashed BeanStalk after I add moto_msm8960 to updater.script
P.S. Also unified ROMs flashed great!
P.P.S. Gummy is most stable for me from unified ones

Flash TWRP-2.7.0.0-moto_msm8960-hdpi.img with Recovery Tools. See OP.

Would anyone know if Dhacker's TWRP works on the XT905 model as well?

Yes. But that is just good advice. I do not have one.

Help with rooting Samsung Galaxy Light T399 - T-Mobile

Its been a while since I have rooted anything manually and i need some expert advice here.
I have someone unlocking my T399 and he gave me this guide -> http://rootmygalaxy.net/root-galaxy-light-sgh-t399-install-twrp-recovery/ the problem is the TWRP link is dead and i cant find another of that version anywhere. Does anyone have this or can I use http://androidforums.com/threads/recovery-team-win-recovery-twrp-2-7-0-0.836658/ or https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604 ? Im assuming yes but wanted to double check with you guys before off and doing something catastrophic to my phone.
Any help is much appreciated.
Thanks
Phonecapone

TWRP Themed Recovery
phonecapone said:
Its been a while since I have rooted anything manually and i need some expert advice here.
I have someone unlocking my T399 and he gave me this guide -> http://rootmygalaxy.net/root-galaxy-light-sgh-t399-install-twrp-recovery/ the problem is the TWRP link is dead and i cant find another of that version anywhere. Does anyone have this or can I use http://androidforums.com/threads/recovery-team-win-recovery-twrp-2-7-0-0.836658/ or https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604 ? Im assuming yes but wanted to double check with you guys before off and doing something catastrophic to my phone.
Any help is much appreciated.
Thanks
Phonecapone
Click to expand...
Click to collapse
There you go
I upload TWRP Themed Recovery on Android file host there you find (IMG,zip,tar) file choose what you want:good:
https://www.androidfilehost.com/?w=files&flid=157735

I used the second one you linked just a couple weeks ago, and it appears to work just fine:
https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604

A140 said:
There you go
I upload TWRP Themed Recovery on Android file host there you find (IMG,zip,tar) file choose what you want:good:
https://www.androidfilehost.com/?w=files&flid=157735
Click to expand...
Click to collapse
Hey A140 thanks a million! Hopefully I wont have any issues downloading it. For some reason I have had a lot of corrupt downloads from androidfilehost. I know they said they are in the process of moving servers? So perhaps that's why. Can you upload to one more place so we all have a backup here? So in the event others run into the same problem I am having we're all covered. =]
http://www.multiup.eu is good
I will try and download soon as I just got back around to this phone again and give it a try and let you know what I think. Right now I have TWRP ver 2.7.1.0 for Galaxy Light T399 ? which appears to be custom and themed? I just now noticed it when rebooting into Recovery from ROMs restart options. It is white, brown and orange with a list menu. I haven't seen this before though again I haven't flashed any other versions of TWRP besides the touch so maybe it's the standard? I did have TWRP ver 2.8.4.0 for this phone which was the grey, black and blue big button themed touch interface I loved so much.
Aside TWRP matters im also toying around with Lightwave-V3 Rom by user @root@ which I switched to from TigerLillly by user DJBoxer. Both seem to be pretty good although Lightwave was suppose to have came preconfigured with a bunch of useful utilities / mods and it appears they weren't configured in the Rom's configuration. I'll have to take a look and see what needs to be modified if they exist within the build seems same with TigerLilly also. I'd suggest these 2 ROMs to anyone with this phone. Smooth, no bloat and no problems so far. However I am always up for trying any others if anyone has some to suggest. Post and let me know.
First post back here in some months. Now back into androids more and attempting root on a few unknowns so hopefully I will have some good material to contribute in the near future. Still hitting that learning curve hard trying to get with the future. I'm still oldschool @ heart stuck with knowledge of the past flip / feature phones, java, crackberries, outdated unlocking boxes and about 100 pre android phones lol. Have the parts to the first android still but unfortunately incomplete. Some interesting times I tell ya. Thanks to XDA and HOFO I'm picking up where I left off quite quickly.
Lightwave - https://forum.xda-developers.com/galaxy-light/development/rom-lightwave-v1-t2825253
TigerLilly - https://forum.xda-developers.com/galaxy-light/development/rom-tigerlilly-v2-1-4-4-2-t3400659
I will post a TON of information on this phone, recovery, rooting, stock/custom rom links and much more in the appropriate thread when I get time free from work. Have done a lot of researching since this post. https://forum.xda-developers.com/galaxy-light - seems to have most of my work done lol. I keep forgetting how old this phone is and that it's been ran through by quite a few dev's already.

Upload it
I upload both themed 2.7 and 2.8 to your favorite site I am giving the link down you can download from it I upload zip file you can flash using costom recovery that you have right now if you want img file you can extract zip file you find Img file and if you want to flash through odin than use zarchiver on your Android phone and compress img file to tar and rename it tar.md5!?
Themed 2.7 link
http://www.multiup.eu/bd3fdc8bee0f678b90df62a1376ed1e6
TWRP 2.8.4 link
http://www.multiup.eu/en/download/9...14bc32/openrecovery-twrp-2.8.4.0-gardalte.zip
phonecapone said:
Hey A140 thanks a million! Hopefully I wont have any issues downloading it. For some reason I have had a lot of corrupt downloads from androidfilehost. I know they said they are in the process of moving servers? So perhaps that's why. Can you upload to one more place so we all have a backup here? So in the event others run into the same problem I am having we're all covered. =]
http://www.multiup.eu is good
I will try and download soon as I just got back around to this phone again and give it a try and let you know what I think. Right now I have TWRP ver 2.7.1.0 for Galaxy Light T399 ? which appears to be custom and themed? I just now noticed it when rebooting into Recovery from ROMs restart options. It is white, brown and orange with a list menu. I haven't seen this before though again I haven't flashed any other versions of TWRP besides the touch so maybe it's the standard? I did have TWRP ver 2.8.4.0 for this phone which was the grey, black and blue big button themed touch interface I loved so much.
Aside TWRP matters im also toying around with Lightwave-V3 Rom by user @root@ which I switched to from TigerLillly by user DJBoxer. Both seem to be pretty good although Lightwave was suppose to have came preconfigured with a bunch of useful utilities / mods and it appears they weren't configured in the Rom's configuration. I'll have to take a look and see what needs to be modified if they exist within the build seems same with TigerLilly also. I'd suggest these 2 ROMs to anyone with this phone. Smooth, no bloat and no problems so far. However I am always up for trying any others if anyone has some to suggest. Post and let me know.
First post back here in some months. Now back into androids more and attempting root on a few unknowns so hopefully I will have some good material to contribute in the near future. Still hitting that learning curve hard trying to get with the future. I'm still oldschool @ heart stuck with knowledge of the past flip / feature phones, java, crackberries, outdated unlocking boxes and about 100 pre android phones lol. Have the parts to the first android still but unfortunately incomplete. Some interesting times I tell ya. Thanks to XDA and HOFO I'm picking up where I left off quite quickly.
Lightwave - https://forum.xda-developers.com/galaxy-light/development/rom-lightwave-v1-t2825253
TigerLilly - https://forum.xda-developers.com/galaxy-light/development/rom-tigerlilly-v2-1-4-4-2-t3400659
I will post a TON of information on this phone, recovery, rooting, stock/custom rom links and much more in the appropriate thread when I get time free from work. Have done a lot of researching since this post. https://forum.xda-developers.com/galaxy-light - seems to have most of my work done lol. I keep forgetting how old this phone is and that it's been ran through by quite a few dev's already.
Click to expand...
Click to collapse

Thanks again! For conversions and archiving I have been using 7zip and a few simple batch files to convert .tar + calculate sum to .tar.md5 and and .img to .tar then .tar to .tar.md5 calculating sum.