Hello everyone on xda
This is a guide for all those who are absolute noobs, who don't know what Root is, but have heard of it. Let's get into it.
This guide is a WORK IN PROGRESS. Will be continuously adding things
BASICS:
"Stock" is the unrooted, unmodified state of your device running on the original OS.
Your device may get "bricked" while rooting, which means that your device will not boot back.
There are many ways to unbrick a device.
Flash means installing a new firmware via recovery
Root:
Whenever you buy a new Android device, the manufacturer makes sure that you, the buyer cannot access system files. By rooting an android device, you get access to the system files, tweak them and can manage them with many applications. Rooting can make your Android device much cooler than it was before. There are many modifications you can do, and you can even put a totally new operating system. You can add multi window, gravity box (which allows lot more tweaks) etc. (No limit exists in the Android world.
Superuser is when you grant access to the system files to an app
Pros:
1) Ability to upgrade Android version and have a billion more features
2) (Well... It's a never ending list )
Cons:
1)Bricking
2) In some cases, losing all oem apps
How to Root:
Search for the method on internet.
YOU WILL VOID YOUR WARRANTY, WHICH DOES NOT COME BACK ON UNROOTING
Recovery
This is the most important tool for any android device. It comes on many android phones even without rooting, but the
"stock" recovery is not so useful. Custom recoveries like TWRP or CWM are the ones I'm talking about. These recoveries can back up, restore, or /and replace the whole system. In most cases, if your OS just blows off your device, you can still boot into recovery and flash a rom.
Pros:
1)Nice and easy way of making an android device
2)Nice way of bringing a device back to life.
Cons:
None I guess
Bootloader:
When you boot up your Android device, you see the device name or manufacturer name for a few seconds, when there is no animation. This part is the bootloader, which is the initial few seconds of fastboot. Here, you can retain fastboot and flash/update recovery. The bootloader is the toughest thing to delete. This bootloader is the software that interacts with the kernel to boot the device up. This is also responsible for booting into recovery .
Brick:
A brick in the toughest terms means a totally unresponsive.device, one that had no life.
Soft Brick: This means that your OS somehow got wiped off, But you still have the recovery to flash a rom. 90%of the bricks are soft bricks. To recover from it, perform a full wipe and then install a rom for your device.
Hard Brick: This means that your device does not have an OS, recovery. You can recover by entering fastboot(bootloader) and flashing a recovery and then a rom.
Bootloop:
This is a kind of soft brick in which, the OS starts booting but never finishes. Just perform a wipe, and if that does not help, Reflash.
If this guide helped, please press the thanks button.
Reserved
Sent from my Amazon Kindle Fire using xda app-developers app
Another for more writing
Sent from my Amazon Kindle Fire using xda app-developers app
One more please
Sent from my Amazon Kindle Fire using xda app-developers app
Thanks dude last one
Sent from my Amazon Kindle Fire using xda app-developers app
I have nexus 4 kitkat 4.4.2
I can root it
Sent from my Nexus 4 using XDA Premium 4 mobile app
Did not understand.. If you want to root it check on the nexus 4 forums
Sent from my Amazon Kindle Fire using xda app-developers app
This explanation was amazing. Is there one like it for the rooting process itself and newbie guide to what customizations cam be done and how? I've rooted one device before... Short term memory loss I don't remember the first steps... Which you kinda explained here.
Sent from my Nexus 7 using XDA Free mobile app
Excellent tutorial for begginers!
Thx! :laugh:
speedo866 said:
Excellent tutorial for begginers!
Thx! :laugh:
Click to expand...
Click to collapse
gypsyjbird said:
This explanation was amazing. Is there one like it for the rooting process itself and newbie guide to what customizations cam be done and how? I've rooted one device before... Short term memory loss I don't remember the first steps... Which you kinda explained here.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Whoa guys thanks! I thought no one read it so I didn't bother adding to it. Thanks
Sent from my A114 using XDA Free mobile app
Bump
Sent from my Amazon Otter using XDA Free mobile app
androvista said:
Bump
Sent from my Amazon Otter using XDA Free mobile app
Click to expand...
Click to collapse
No One needs this thread?
Thanks for making this simple to follow rooting guide.
@Judge Joseph Dredd please close this thread, I put it in the wrong forum. Already made a duplicate in Android General
Related
Well, I have tried to flash my phone with cm7 for the last 3 days and when I go to reboot recovery it freezes at the LG screen and I am forced to pull my battery possibly bricking my phone. Does anyone, I mean anyone have a safe sure way to flash my phone? And I have no pc access.....srry
Sent from my VM670 using XDA Premium App
You need a computer. Either you didn't install recovery right. Or you're too impatient. Sometimes it hangs for a minute or so.
Sent from my VM670 using XDA Premium App
omgpk said:
Well, I have tried to flash my phone with cm7 for the last 3 days and when I go to reboot recovery it freezes at the LG screen and I am forced to pull my battery possibly bricking my phone. Does anyone, I mean anyone have a safe sure way to flash my phone? And I have no pc access.....srry
Sent from my VM670 using XDA Premium App
Click to expand...
Click to collapse
use terminal emulator and reflash your recovery with flash_image. you got a bad flash or a bad download of the recovery it sounds like.
there is a slim chance you aren't rooted correctly too, in which case it won't let you flash the recovery until you get permanent root. hopefully this isn't the case.
Pretty dumb question what's flash image n just incase how do I check. For a permanent root?
Sent from my VM670 using XDA Premium App
omgpk said:
Pretty dumb question what's flash image n just incase how do I check. For a permanent root?
Sent from my VM670 using XDA Premium App
Click to expand...
Click to collapse
My advice is not to do ANYTHING until you are at a computer and have at least a half an hour available. This sounds like your first time flashing a ROM, take some time to look up key terms and such, your patience will reward you greatly. It is difficult to flash without a computer. Go to a friends house, a library, something and do it from there. To check if you have root, download the app root checker from the market. Then, after confirming root status, work from there and flash a new recovery by pushing it through ADB. Then, place the ROM on the sd card and flash it through your recovery, then Google Apps. If you follow everything I say, and it still doesn't work, come back to this thread or send me a PM and we will go from there. Look into guides before posting, not trying to be mean, but they are there for a reason.
Hi.
Why the mother flipping heck won't my Prime root?
I've tried the Zedomax 1 click script and ViperMODs method for devices running 9.4.2.11 and later (which mine is as its 9.4.2.28).
The first time I ran ViperMODs script I did all the tasks including number 3 to install the unlocker which seems to have run successfully as my Prime says 'this device is unlocked' in small white letters in the top left hand corner of the splash screen when booting.
But nothing has root privileges (I use Titanium backup to check).
What is going on, other people have rooted their .28s so why won't mine?
I have installed the USB drivers for the ADB interface and I've even done a full system restore on the Prime so that I'm working with a stock ROM but nothing helps
If anyone can help me to root my Prime I will let them marry my daughter* or take my son* as a slave (*as soon as I have one)
Thanks:crying:
thintin said:
Hi.
Why the mother flipping heck won't my Prime root?
I've tried the Zedomax 1 click script and ViperMODs method for devices running 9.4.2.11 and later (which mine is as its 9.4.2.28).
The first time I ran ViperMODs script I did all the tasks including number 3 to install the unlocker which seems to have run successfully as my Prime says 'this device is unlocked' in small white letters in the top left hand corner of the splash screen when booting.
But nothing has root privileges (I use Titanium backup to check).
What is going on, other people have rooted their .28s so why won't mine?
I have installed the USB drivers for the ADB interface and I've even done a full system restore on the Prime so that I'm working with a stock ROM but nothing helps
If anyone can help me to root my Prime I will let them marry my daughter* or take my son* as a slave (*as soon as I have one)
Thanks:crying:
Click to expand...
Click to collapse
I guess the first question would be, are you planning on putting a custom rom on the prime? If you are, they are all pre-rooted If you want to stick with a stock .28 rom look at virtuous....
If you are going to put a custom recovery on, which I am guessing your going to do since you have unlocked it, either go for an earlier version of twrp (2.1) or go the nvflash route, get the modified bootloader and then put on the latest twrp (2.2)...
I was going to root, use titanium to backup my user data and then try some custom ROMs. But I'm using another app backup program that doesn't require root now so I guess I can just go strait for a custom ROM lol. I got so hung up on why this thing wouldn't root that I forgot why I was doing it; D'oh!
So, on to flashing recovery then... why did you say to flash an older version first?
Thanks.
Sent from my Transformer Prime TF201 using XDA Premium HD app
thintin said:
I was going to root, use titanium to backup my user data and then try some custom ROMs. But I'm using another app backup program that doesn't require root now so I guess I can just go strait for a custom ROM lol. I got so hung up on why this thing wouldn't root that I forgot why I was doing it; D'oh!
So, on to flashing recovery then... why did you say to flash an older version first?
Thanks.
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
because the latest version requires you have the mobi modified bootloader which is only available if you follow through with the whole nvflash process. Not being familiar with your level of comfort/expertize if you use the older version you don't "need" to go the nv flash route right away... just gives a guy some breathing room.....
I have attached the older version or if you feel brave enough take the nvflash road..... it aint that hard if you follow the instructions... I can give some pointers to make it easier if you decide to go that way....
thintin said:
Hi.
Why the mother flipping heck won't my Prime root?
I've tried the Zedomax 1 click script and ViperMODs method for devices running 9.4.2.11 and later (which mine is as its 9.4.2.28).
The first time I ran ViperMODs script I did all the tasks including number 3 to install the unlocker which seems to have run successfully as my Prime says 'this device is unlocked' in small white letters in the top left hand corner of the splash screen when booting.
But nothing has root privileges (I use Titanium backup to check).
What is going on, other people have rooted their .28s so why won't mine?
I have installed the USB drivers for the ADB interface and I've even done a full system restore on the Prime so that I'm working with a stock ROM but nothing helps
If anyone can help me to root my Prime I will let them marry my daughter* or take my son* as a slave (*as soon as I have one)
Thanks:crying:
Click to expand...
Click to collapse
The method below works on 9.4.2.28
http://forum.xda-developers.com/showthread.php?t=1706588
success????
Gage_Hero said:
I guess the first question would be, are you planning on putting a custom rom on the prime? If you are, they are all pre-rooted If you want to stick with a stock .28 rom look at virtuous....
If you are going to put a custom recovery on, which I am guessing your going to do since you have unlocked it, either go for an earlier version of twrp (2.1) or go the nvflash route, get the modified bootloader and then put on the latest twrp (2.2)...
Click to expand...
Click to collapse
i have this problem re rooting, i have tried the vipermod primetime and DebugfsRoot_Generic_v2.3 both say once tablet reboots it will be rooted. then i try and ope cwmr and busybox and no root error message comes up, the device is unlocked as far as the top left tells me on boot, it is running 4.0.3 build no 9.4.2.28 the issue is this inverted x-axis problem but i cant even get the dam thing rooted to do anything with it. i have galaxy note 2 s3 and nexus 7 all rooted so i really am baffleld why this is so hard, if anyone has found a foolproof idiots guide please feel free to mail it to me. ..
i thank you all in advance and thanks for reading this request.
kindest regards
phil
philsmusic2000 said:
i have this problem re rooting, i have tried the vipermod primetime and DebugfsRoot_Generic_v2.3 both say once tablet reboots it will be rooted. then i try and ope cwmr and busybox and no root error message comes up, the device is unlocked as far as the top left tells me on boot, it is running 4.0.3 build no 9.4.2.28 the issue is this inverted x-axis problem but i cant even get the dam thing rooted to do anything with it. i have galaxy note 2 s3 and nexus 7 all rooted so i really am baffleld why this is so hard, if anyone has found a foolproof idiots guide please feel free to mail it to me. ..
i thank you all in advance and thanks for reading this request.
kindest regards
phil
Click to expand...
Click to collapse
You should go here and install this rom, the support here is very good. The rom is already rooted so there is nothing but install and play... since it looks like you are on an old rom play close attention to updating the bootloader first.....
http://forum.xda-developers.com/showthread.php?t=1674827
I just want to say a massive thanks for the help. I have now managed to get hairy bean 4.1 on it andnit is now fully unlocked and rooted. I still unfortunately habe thw inverted x-axis problem and from what I understand from what I've read the official jb4.2 will rectify this problem.
I can boot into the hairy recovery but not twrp I do the same reset/clear data as in the hairybean install instructions but then try to install jb4.2. The blue line goes to the top thwn it reboots but back into hairybean.
What am I doing wrong for this to keep happening?
Your help so far has been great and very much appreciated.
I thank you in advance for any further help that coukd direct me.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
Anyone?
Sent from my GT-N7105 1.8ghz using xda app-developers app
philsmusic2000 said:
Anyone?
Sent from my GT-N7105 1.8ghz using xda app-developers app
Click to expand...
Click to collapse
1. Unlock device
2. Install TWRP
3. Install Hairy Recovery & Upgrade Bootloader
4. Install Hairybean 2.2
But be sure your bootloader is 4.1.1 first before flashing TWRP(JB)、Hairy Recovery & Upgrade Bootloader
Did you upgrade to stock Jellybean before doing these procedures?
I just did these procedures 2 days ago from stock JB to Hairybean 2.2
Ok. I have managed to get stock 4.2.15 installed. But I am still lost ad to where I go to get this inverted x axis fixed. Its not at least not bricked so im relatively happy. But would really enjoy being able to press on what I want rather than opposite.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
philsmusic2000 said:
Ok. I have managed to get stock 4.2.15 installed. But I am still lost ad to where I go to get this inverted x axis fixed. Its not at least not bricked so im relatively happy. But would really enjoy being able to press on what I want rather than opposite.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
For HB2.2, there are kernels in the install options for the Reverse Axis
http://forum.xda-developers.com/showthread.php?t=1674827&page=931
Maybe it can fix your inverted x axis
Hmmm I downloaded the 2.2 but I believe that I have managed to brick it in the worst possible way. It wont boot into recovery. When I get it into apx mode. My pc wont see it as driver installed. So I cannot push any files to it or do anything. Dohhhhh.
Sent from my GT-N7105 using xda app-developers app
Any possibility of getting some advice on how to get this working again? Sorry to be a pain in the a$$ guys.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
philsmusic2000 said:
Any possibility of getting some advice on how to get this working again? Sorry to be a pain in the a$$ guys.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
You need to at least get into the bootloader. What happens when you keep holding volume down and power button the same timer for about 20 seconds. Do not stop holding them when the prime restarts after 10 seconds.
If you get to some icons on the screen then we might be able to help you.
Sadly if I hold vol dwn and pwr it just goes to the asus logo screen. Not boot loader options what so ever I have bought a new mobo off ebay thinking that would have helped. But this one seems to just jam on the rck loader. Try the rck mode it reboots to the same option screen. Trying usb mode does the same. Factory wipe wnds up the same and the android option just boots back into the asus logo. I cannot get my head around the way these are built. With any windows os unless you somehow screw the bios you can pretty much reinstall from any situation. Why is Android so different? I enjoy a challenge as much as the next guy but this is ludicrous. I have just done 6 16 hr days at work so I am not the most patient person with this right now so I think on tues on my day off work I will start again and see if I can get this working and redeem myself. I do just want to say thanks for the help off this forum though as people do seem very helpful and friendly.
Cheers guys.
Sent from my GT-N7105 using xda app-developers app
Sadly if I hold vol dwn and pwr it just goes to the asus logo screen. Not boot loader options what so ever I have bought a new mobo off ebay thinking that would have helped. But this one seems to just jam on the rck loader. Try the rck mode it reboots to the same option screen. Trying usb mode does the same. Factory wipe wnds up the same and the android option just boots back into the asus logo. I cannot get my head around the way these are built. With any windows os unless you somehow screw the bios you can pretty much reinstall from any situation. Why is Android so different? I enjoy a challenge as much as the next guy but this is ludicrous. I have just done 6 16 hr days at work so I am not the most patient person with this right now so I think on tues on my day off work I will start again and see if I can get this working and redeem myself. I do just want to say thanks for the help off this forum though as people do seem very helpful and friendly.
Cheers guys.
Sent from my GT-N7105 1.8 Ghz using xda app-developers app
Bump....
Does anyone have a spare tf201 mobo for sale?
Kindest regards
Phil
philsmusic2000 said:
Sadly if I hold vol dwn and pwr it just goes to the asus logo screen. Not boot loader options what so ever I have bought a new mobo off ebay thinking that would have helped. But this one seems to just jam on the rck loader. Try the rck mode it reboots to the same option screen. Trying usb mode does the same. Factory wipe wnds up the same and the android option just boots back into the asus logo. I cannot get my head around the way these are built. With any windows os unless you somehow screw the bios you can pretty much reinstall from any situation. Why is Android so different? I enjoy a challenge as much as the next guy but this is ludicrous. I have just done 6 16 hr days at work so I am not the most patient person with this right now so I think on tues on my day off work I will start again and see if I can get this working and redeem myself. I do just want to say thanks for the help off this forum though as people do seem very helpful and friendly.
Cheers guys.
Sent from my GT-N7105 1.8 Ghz using xda app-developers app
Bump....
Does anyone have a spare tf201 mobo for sale?
Kindest regards
Phil
Click to expand...
Click to collapse
When you say that the new mobo can get to where the icons are, when you press volume up on the usb icon does it say starting fastboot and then freeze?
If it does we have a chance.
Yes. Thats exactly what happens. Is there light at the end of the tunnel?
philsmusic2000 said:
Yes. Thats exactly what happens. Is there light at the end of the tunnel?
Click to expand...
Click to collapse
If it freezes there then you are in fastboot mode. Look in your device manager in windows and see if you have an unknown device or a fastboot device (names could have been changed to protect the innocent =] .)
If you have an unknown device then install the "naked drivers" from the dev thread to get fastboot working on your pc.
Let me know if you get this far and you see a fastboot device in your device manager.
If you are rooted (assuming you are) with busybox and Android Terminal Emulator installed I was wondering if the flash_image binary could actually flash a recovery image to the device, of course there is no recovery image for our device yet BUT maybe we can start building it if this flasher alternative does work.
yes,i think it is possable
and there is some flash recovery in official roms,it named as hidden.img
and hidden.img have more than one version
hidden.img will be flash to partion 6 (mmcblk0p6 UP)
by now, we can not decrypt it's content
Well, we can't create an standard type of recovery as we wouldn't be able get that to boot. However there are ways to hi-jack the Android boot process and start a recovery that way, look at Safestrap for Motorola RAZR.
This way we can boot another rom from the internal storage (image files) and keep the original safe.
I'm very interested an trying to port it over to the XTS, however when playing with the hi-jack there is a risk of bricking so I need to first find out how to un-brick the tablet when the system partition is broken (boot partition would still be fine).
We can even boot to a custom kernel using kext however that one can be quite difficult to get working properly.
But just the ability to boot an Paranormal Android rom would be fantastic (I don't know if that rom requires changes in the kernel. But CM and AOKP doesn't).
If anyone could assist in Safestarp work it would be great. At this stage it's mostly to find out how to un-brick.
I haven't even been able to boot the tablet into recovery or bootloader mode. I have tried both ADB (reboot recovery, reboot bootloader, reboot-bootloader) and holding volume up on boot but whatever I do it still boots into Android.
With this technique I would also expect to be able too boot into the backup system partition or whatever mmcblk0p3 is (contains the system of the firmware the device where preloaded with, mmcblk0p4 is the current system that gets updated) I would hope Sony have built a whay to boot to this partition using the standard bootloader but I can't seem to find any.
EDIT: I were able to reach the recovery by mashing the volume up button on boot so now I feel much better. However I'm still interested in any information that might be interesting.
pajn said:
Well, we can't create an standard type of recovery as we wouldn't be able get that to boot. However there are ways to hi-jack the Android boot process and start a recovery that way, look at Safestrap for Motorola RAZR.
This way we can boot another rom from the internal storage (image files) and keep the original safe.
I'm very interested an trying to port it over to the XTS, however when playing with the hi-jack there is a risk of bricking so I need to first find out how to un-brick the tablet when the system partition is broken (boot partition would still be fine).
We can even boot to a custom kernel using kext however that one can be quite difficult to get working properly.
But just the ability to boot an Paranormal Android rom would be fantastic (I don't know if that rom requires changes in the kernel. But CM and AOKP doesn't).
If anyone could assist in Safestarp work it would be great. At this stage it's mostly to find out how to un-brick.
I haven't even been able to boot the tablet into recovery or bootloader mode. I have tried both ADB (reboot recovery, reboot bootloader, reboot-bootloader) and holding volume up on boot but whatever I do it still boots into Android.
With this technique I would also expect to be able too boot into the backup system partition or whatever mmcblk0p3 is (contains the system of the firmware the device where preloaded with, mmcblk0p4 is the current system that gets updated) I would hope Sony have built a whay to boot to this partition using the standard bootloader but I can't seem to find any.
EDIT: I were able to reach the recovery by mashing the volume up button on boot so now I feel much better. However I'm still interested in any information that might be interesting.
Click to expand...
Click to collapse
Well there is two system partitions and you can use the backdoor thingy from Condi's tools to avoid a soft brick BUT if it writes to the bootloader then we have ourselves a brick.
Sent from my Nexus 4 using xda app-developers app
;42754576 said:
yes,i think it is possable
and there is some flash recovery in official roms,it named as hidden.img
and hidden.img have more than one version
hidden.img will be flash to partion 6 (mmcblk0p6 UP)
by now, we can not decrypt it's content
Click to expand...
Click to collapse
I have the hidden.img BUT the MD5Sum is badf0628deff7f47b1148e5ae662aa26
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Well there is two system partitions and you can use the backdoor thingy from Condi's tools to avoid a soft brick BUT if it writes to the bootloader then we have ourselves a brick.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Of course as the boot partition requires a signature. Safestarp only writes to the system partition and it only does that once under install, after that in only touches the storage. You can have four ROM slots in the storage where you can installed custom ROMs, the system partition shall always contain the stock system. If I can get kexec to work there aren't any noticeable problems with having a locked boot loader.
Sent from my XT910 using Tapatalk 4 Beta
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
pajn said:
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
Click to expand...
Click to collapse
Holly crap, you got the recovery installed, will this work with the original Sony Tablet S and how did you manage to do such thing?
EDIT: I see you used Safestrap but from where?
Sent from my Nexus 4 using xda app-developers app
pajn said:
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
Click to expand...
Click to collapse
What device are you using? STS or XTS?
Sent from my GT-S5830 using xda app-developers app
jumper62 said:
What device are you using? STS or XTS?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
That is the Sony Xperia Tablet S, I can tell by the branding near the screen and the IR Blaster plastic cover is smaller.
Sent from my Nexus 4 using xda app-developers app
jumper62 said:
What device are you using? STS or XTS?
Click to expand...
Click to collapse
Definitely an XTS. Notice the Multi Port connection at the bottom center of the tablet.
WOW! coooool. btw, how did you manage to boot safestrap in XTS? probably same method could be done on STS
As some saw it's a XTS. The recovery is safestrap and it works using 2nd-init. I found a good text describing it using normal language here http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
It should be portable to STS aswell. Every rooted Android should be able to run it. I can't promise anything as I'm working but when I'm done I can take a look at the STS aswell but I would need help from someone with at least basic adb and linux knowledge as I don't have a STS.
It wore actually easier to get this far than I expected so that's good but there are more work needed so I can't relax yet.
Sent from my XT910 using Tapatalk 4 Beta
Just contacted Chainfire on Google+ for any ideas how this is going to work.
UPDATE: Nothing yet...
Sent from my Nexus 4 using xda app-developers app
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i think you need to contact Hashcode, original developer of Safestrap for that
andyabc said:
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I do have recovery working on XTS, should be quite simple to port to STS. Things left is hijack (simple but scary) and manager app (simple but can ne time consuming)
Sent from my XT910 using Tapatalk 4 Beta
pajn said:
I do have recovery working on XTS, should be quite simple to port to STS. Things left is hijack (simple but scary) and manager app (simple but can ne time consuming)
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
How did you do it though?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
How did you do it though?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Studied safestrap to see how it worked and applied the same
techniques to the XTS. Where things don't work I work around them
by googling, studying others work or just testing. A pretty good
knowledge of Linux, it's boot process and programming does
help quite a bit
pajn said:
Studied safestrap to see how it worked and applied the same
techniques to the XTS. Where things don't work I work around them
by googling, studying others work or just testing. A pretty good
knowledge of Linux, it's boot process and programming does
help quite a bit
Click to expand...
Click to collapse
Can't wait for recovery on sts good job on the xts dude!
Sent from my LT28i using xda app-developers app
I have Htc one and the phone is TWRP rooted,
when i tried to do the system update android 4.4.2,
the phone reboots and enters the recovery mode and gets stuck there.
when i rebot again system update message is still there.
could any one please help me to the system update for android please.
thank you in advance
You will need to at the very least remove twrp if you want to do the ota, check your device forum for specifics as I'm sure a quick search there will give you all the info needed
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
You will need to at the very least remove twrp if you want to do the ota, check your device forum for specifics as I'm sure a quick search there will give you all the info needed
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much after removing twrp i was able to update the android. i have another problem now, removing twrp is done by flashin to stock rom, so when i normally start the phone it updates from htc backup account. this time it didnt update so i when to back up and reset and choosed backup now instead of choosing restore. now my back up point is lost, could you help me to reterive my old back up point please.
Thank you in Advance
Hello All,
I am currently trying to flash TWRP onto my phone, and booting into the Operating system is not possible at this point. I can get the phone into download mode and stock recovery (The phone has never been rooted or flashed, it is bone stock). I cannot figure out for the life of me how to get TWRP flashed onto the phone with either download mode OR ADB commands via the stock recovery. I cannot figure out how to successfully format the LAF partition to access fastboot. Can anyone provide some assistance? I will paypal you money if necessary. I need this phone up and running ASAP. Please help!
Meshuggah27 said:
Hello All,
I am currently trying to flash TWRP onto my phone, and booting into the Operating system is not possible at this point. I can get the phone into download mode and stock recovery (The phone has never been rooted or flashed, it is bone stock). I cannot figure out for the life of me how to get TWRP flashed onto the phone with either download mode OR ADB commands via the stock recovery. I cannot figure out how to successfully format the LAF partition to access fastboot. Can anyone provide some assistance? I will paypal you money if necessary. I need this phone up and running ASAP. Please help!
Click to expand...
Click to collapse
This is your option. http://forum.xda-developers.com/showthread.php?p=55225699 The links are all there.
You MUST have a "Bumped" TWRP.
Sent from my Nexus 5X using XDA-Developers mobile app
engine95 said:
This is your option. http://forum.xda-developers.com/showthread.php?p=55225699 The links are all there.
You MUST have a "Bumped" TWRP.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey engine95,
I cannot get into the operating system to do stump root or install flashify. I am not sure how this would work
Meshuggah27 said:
Hey engine95,
I cannot get into the operating system to do stump root or install flashify. I am not sure how this would work
Click to expand...
Click to collapse
The BEST way to do it is to flashtool zv4. Root and unlock it.
As for rooting zva-e, there are procedures linked in the thread. Unlocking the boot loader are there too, I believe. Doing it this way may cause issues. So I all depends how much work you want to go through.
Personally, just use ZV4, root/unlock. Then flash modem and whatever ROM you want.
Sent from my Nexus 5X using XDA-Developers mobile app
engine95 said:
The BEST way to do it is to flashtool zv4. Root and unlock it.
As for rooting zva-e, there are procedures linked in the thread. Unlocking the boot loader are there too, I believe. Doing it this way may cause issues. So I all depends how much work you want to go through.
Personally, just use ZV4, root/unlock. Then flash modem and whatever ROM you want.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey engine,
I did use flashtool to restore to ZV4, but it will not boot into the OS and just keeps powering itself off at either of the LG bootup screens
Meshuggah27 said:
Hey engine,
I did use flashtool to restore to ZV4, but it will not boot into the OS and just keeps powering itself off at either of the LG bootup screens
Click to expand...
Click to collapse
And that's just stock? Straight from flashtool? That shouldn't happen unless you wiped something out trying to do the laf partition.
Are you sure you have the Sprint 990?.
There's other threads here, one is stickied in "General", that you might need to read then. They're about fixing other issues that might feel you.
Sent from my Nexus 5X using XDA-Developers mobile app
engine95 said:
This is your option. http://forum.xda-developers.com/showthread.php?p=55225699 The links are all there.
You MUST have a "Bumped" TWRP.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
engine95 said:
And that's just stock? Straight from flashtool? That shouldn't happen unless you wiped something out trying to do the laf partition.
Are you sure you have the Sprint 990?.
There's other threads here, one is stickied in "General", that you might need to read then. They're about fixing other issues that might feel you.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I appriciate your help! Yes, the phone restores just fine using flashtool with the ZV4 .tot file, but once it reboots it wont make it past the LG logo bootup screen. One time it made it all the way into the OS, and went through the activation process, then powered itself off. Now it wont reboot past the second animated LG logo.
engine95 said:
And that's just stock? Straight from flashtool? That shouldn't happen unless you wiped something out trying to do the laf partition.
Are you sure you have the Sprint 990?.
There's other threads here, one is stickied in "General", that you might need to read then. They're about fixing other issues that might feel you.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I should also mention that sometimes when restoring the .tot with Flash Tool, it powers itself off in the middle of it and just keeps booting into download mode. It always happens anywhere between 30-60% when it says SYSTEM in the progress log. Could it be that my phones internal memory that stores that information is bad?