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
Related
Hi, I'm almost ready to release a working version of the recovery for this tablet.
It works properly with adb, but it has a UI glitch, as the stock kernel does not fully support framebuffering swaps.
It will probably be released within the next couple of days... just waiting for some final touches.
Sent from my HTC Desire using XDA App
Awesome! Ty! Will eagerly wait.
Sent from my Ideos S7 using XDA App
Lets do it
Sent from my Ideos S7 using Tapatalk
Sweet.
Sent from my HTC Vision using XDA App
Just got my S7 and dying to unlock and flash! Looking forward to all the fun hidden in this monster!
Sent from my Ideos S7 using XDA App
some news about recovery ?
Sent from my S7 using XDA App
Is this similar to ClockWorkMod?
Topic seems dead, no more news about the tools...
Sent from my X10i using XDA App
Any update?
Sent from my HTC HD2 using Tapatalk
I put together a partially working version of Clockworkrecovery that works better, but it renders only around 50% of the screen. It on my external + internal SD version of S7:
http://www.multiupload.com/0JBBOE4NAL
Changes were made to graphics.c in the recovery source code to workaround the framebuffer issues.
I was able to make a successful nandroid with this.
I am not a developer, so this is not just unfinished, but buggy.
I posted details here: http://www.androidtablets.net/forum...-recovery-help-needed-lcdc_panel-s70-c-2.html
I want to know if there is a good way to deploy this to pre-rooted users. If not, it might be better if we put together something.
This can be flashed in fastboot, or with a flash_image binary. .
xaueious said:
I put together a partially working version of Clockworkrecovery that works better, but it renders only around 50% of the screen. It on my external + internal SD version of S7:
http://www.multiupload.com/0JBBOE4NAL
Click to expand...
Click to collapse
THANK YOU! (pointless comments but i know our battle here!)
Loading though fastboot would be a pain for most new users, I wonder if we can get something simular to the archos SDE running on the huawei then we could load the custom rom and ditch the main kernel. ideas?
Someone will figure something out.
For now, you can fastboot boot this recovery image to make a working nandroid and restore as well.
I have tested nandroid now, and it works. Not tested for apps2sd though, because I do not have that setup.
I recommend that everyone would this first though: http://forum.xda-developers.com/showthread.php?t=968850
this is working on my s7 too
i tested today and recovery is working the fact that it only uses a third of the screen is not an issue in my view.
i did a nandroid backup of my system and have all mtd files saved on my desktop
my device get on a zombie state after power off the 18d1:d00d google inc appears on lsusb but the device doesnt do anything i had to reboot and do the volume and power aggain for it to respond.
on ubuntu 64 at least on my system i had to run fastboot as root
this is nice work thanks xaueious
I fixed the weird misc bug. I was using razor950's device files, which has BOARD_HAS_NO_MISC_PARTITION := true defined. My Singapore ROM has the misc partition.
Anyhow, working S7 recovery now for BestBuy version:
http://www.androidtablets.net/forum...lockworkmod-recovery-port-xaubeta-0-11-a.html
Hello there.
I own a Kyocera M6000. I believe our recovery partitions act in a similar way, in that upon reboot to recovery (of the stock recovery, that is), the device will wipe data/cache.
This is preventing clockwork recovery from loading when flashed to our recovery partitions.
I was wondering if someone here would be able to explain this issue in more detail, and any steps taken for a work around?
Much Appreciated.
HTC Dumlock
HTC Dumlock is a workaround for devices with HTC's unlock that cannot flash boot from recovery. Put simply, we make backups of recovery and boot, then we flash the backup of recovery to boot. When you reboot normally, you'll be in your recovery, but since your recovery is flashed to boot, you can make changes to boot. Head on over to our website for download links and instructions.
NOTE: The Rezound does not have TWRP, so you will be using the universal version!
New v2 version scans / compares the backups of boot and recovery to help ensure that you don't run it twice and wipe out your backup of boot.
I believe I can unify all of the zips into a single one that is touchscreen based It would make it extremely easy and useful.
con247 said:
I believe I can unify all of the zips into a single one that is touchscreen based It would make it extremely easy and useful.
Click to expand...
Click to collapse
Con,
I hope your professor's appreciate you ! I was hoping you would simplify it.
Quick question, so reading through the website a few times. It is my understanding once this is properly set up when we make backups it will be backing up the kernel and when we restore backups we wouldn't have to reflash kernel or am I taking it to far ?
Also would our backups from Amon Ra still work or better to just delete them and just make fresh backups of current rom with TWRP recovery.
There's 2 versions, one is the universal version that works with any recovery. The other, the TWRP version, is only available for a handful of devices and that doesn't include the Rezound. I don't have a Rezound, so I can't speak for it myself, but I would imagine that your existing backups would be fine (you could read boot, just not write to it) unless you chose not to back up boot.
I believe once I rebuild it specifically for the Rezound it will clear the confusion surrounding the purpose and use of the tool.
I look forward to seeing where this goes...
This may be huge. Invaluable tool if used properly.
I wonder if this same technique would work using "fastboot boot recovery.img" instead of actually having to save / flash / restore the boot.img?
I've been asking the same question
Sent from my ADR6425LVW using XDA Premium App
RustyNailz said:
I wonder if this same technique would work using "fastboot boot recovery.img" instead of actually having to save / flash / restore the boot.img?
Click to expand...
Click to collapse
nolimit78 said:
I've been asking the same question
Sent from my ADR6425LVW using XDA Premium App
Click to expand...
Click to collapse
Yes, but the point is to avoid fastboot.
con247 said:
Yes, but the point is to avoid fastboot.
Click to expand...
Click to collapse
True. But I would think there would be a way to duplicate the fastboot behavior and boot from an alternate image file without requiring the use of a PC.
You can only issue fastboot commands from an external device via USB while your Rezound is in fastboot mode in the bootloader.
RustyNailz said:
True. But I would think there would be a way to duplicate the fastboot behavior and boot from an alternate image file without requiring the use of a PC.
Click to expand...
Click to collapse
This is that way lol
Sent from my ADR6425LVW using XDA App
Not quite. I don't believe the fastboot method actually flashes anything to the boot image, so this method leaves more room for error due to the process of saving / flashing / restoring the boot image.
Totally awesome gentlemen. I cannot wait to install this on my phone.
RustyNailz said:
Not quite. I don't believe the fastboot method actually flashes anything to the boot image, so this method leaves more room for error due to the process of saving / flashing / restoring the boot image.
Click to expand...
Click to collapse
That is the only way to do it without fastboot.
---------- Post added at 07:18 PM ---------- Previous post was at 07:17 PM ----------
Irieone said:
Totally awesome gentlemen. I cannot wait to install this on my phone.
Click to expand...
Click to collapse
I am building a GUI for this so it will be pretty sick. Should be out tomorrow night.
Sent from my ADR6425LVW using Tapatalkwa
RustyNailz said:
Not quite. I don't believe the fastboot method actually flashes anything to the boot image, so this method leaves more room for error due to the process of saving / flashing / restoring the boot image.
Click to expand...
Click to collapse
Sure, but this method doesn't require a computer (or other external device) for those times when you are away from a computer. You can't do the fastboot method without a second device.
The 3D had a program called Flash Image GUI. It did what we're trying to accomplish here. Interestingly enough the program "worked" but it wasn't nearly as reliable as the fastboot method
Sent from my ADR6425LVW using XDA Premium App
And please don't take any of what I say a hating. I am merely discussing and spitballing. Lord knows that with the drama over at the 3D forums and Chad kernels I am not trying to bring that hate here. Not in the slightest.
I will post this in the other thread too. Thanks for all your hard work sir!
Sent from my ADR6425LVW using XDA Premium App
I have a Nexus 4, and my ultimate goal is to get a custom kernel running on it. After the first attempt failed (predictably), I tried to boot a stock boot.img - one pulled from my device's boot partition, and the other downloaded from the Google stock images.
I am using 'fastboot boot' to boot the image, on Windows 7 64-bit. The command outputs that the downloading and booting process went OKAY, and the phone continues booting, but after the Google logo disappears I just get a black screen. The phone does start though, since my computer then picks up the adb interface, and I set up an SSH server to start when the phone starts. So the phone still works, just I get a black screen with backlight on.
Obviously the first step is to get a stock image booting properly. After that I can attempt to get a custom-built kernel working, but that is a whole other problem. Is there any way to figure out what is going wrong during boot? I can get any log files from the device if needed. It is running stock Android, rooted, with CWMR v6.0.2.3.
Thanks!
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Click to expand...
Click to collapse
Well ideally I want to keep the stock ROM - while the N4 is supported by Google I don't want to mess with it too much. The kernel can be 'easily' tested without flashing, which is why I don't want to flash just yet. Are you saying though that the ROM could be to blame for this? Surely though, if the kernel, initrd and configuration are identical the boot should just work straight away? It works fine booting normally - just when fastboot is used graphics don't work.
So you are saying you are running a stock ROM and kernel and when you take the exact kernel from this ROM and use fastboot to boot that kernel you have no GUI?
Something is wrong here then as this should cause no issues. Well first step is to pull a logcat and see if it will show you why there's only a black screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
My exact procedure:
Get a boot.img by cat'ing the boot partition
Start adb logcat
Use fastboot boot boot.img to boot the image
Hopefully I got that right. Unfortunately since I'm under 10 posts I can't post links, but if you put this at the end of the Pastebin URL you can access the logcat: C2Q0eR4k
I'm not sure what cating the boot partition means and logcat hast to be started after booting the kernel, but here is what I would do
Take stock ROM source and take boot.img from it
Be sure I'm using the exact same stock ROM as this kernel
Boot to fastboot
fastboot boot boot.img
Now it will start booting and in the terminal/cmd I would then run adb logcat (probably define my logcat more but whatever)
And then see what happens
But again, there is no reason that an untouched stock kernel won't boot through fastboot or give you issues as its the exact same kernel you are currently using so with this I'm confused as there must be something else missing here, either using a different ROM that the kernel booting is not meant for (different versions or whatever) or really not to sure whatelse.
Try the above again and when I get near a PC I'll peek at your logcat
Sent from my Nexus 4 using XDA Premium 4 mobile app
I have already tried using a boot.img taken directly from the Google Nexus 4 stock, but with exactly the same results. I could post a logcat of that if you want, but I strongly suspect it will be exactly the same. It wouldn't be the recovery changing something, would it? CWMR asked me if I want to prevent Android from overwriting it - I answered 'yes', naturally, but I don't suppose it broke something?
I can rule out the software on my PC being a problem, since both Linux and Windows do the same thing. It could possibly be the USB cable, but I highly doubt it.
'cat' is a utility on Linux that reads files - that's why logcat is called what it is, since it reads the logs. By cat'ing the boot partition I literally read the boot partition, then saved the result into a file - boot.img. A form of copy, if you will.
Recovery should have no effect when booting a kernel through fastboot, I highly suspect the kernel you are trying to boot is for a different stock ROM than you are running right now. Feel free to post logcats and I can look when I'm near a pc
Sent from my Nexus 4 using XDA Premium 4 mobile app
It is the identical stock ROM to the one I'm using on my phone at the moment. For that reason, and based on the fact that the symptoms are exactly the same, I can guess that the logcats will be identical.
How is the logcat looking, by the way? I wish I knew more about Android...
Still haven't gotten near a PC, most of the time I'm mobile but hopefully tonight if I don't get back too late
Is your phone running properly when booting normally then? Or if you flash rather than boot the kernel.img with fastboot?
Sent from my Nexus 4 using XDA Premium 4 mobile app
The phone works perfectly normally - using the same boot.img that I have been unsuccessfully trying to fastboot. It is really strange, almost as if the phone is rejecting the fastboot. And I don't dare flash using fastboot, in case my phone boots without graphics and forces me to flash a new ROM. Although it wouldn't be disasterous, I don't have the time at the moment to go about fixing it if something does go wrong.
Just make a backup of ROM in recovery, then fastboot flash the kernel you've been trying to boot, if there is an issue then just wipe clean and install the nandroid
This whole process will take less than 10 min and will let you know if there is an issue with your kernel.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hmm, assuming fastboot isn't lying to me, it seems to have worked. I ran 'flashboot flash boot boot.img' (to which fastboot reported OK) and then continued with the boot in the bootloader. It booted, graphics work, along with all other basic functions like wireless and touch input. To confirm, that is with the boot.img that previously did not work with 'fastboot boot', and the one that I pulled from the device itself.
Any ideas why 'fastboot boot' isn't working properly, while 'fastboot flash boot' works? I guess I can test my custom kernel by seeing if the device boots without graphics, but ideally I would like to test the whole system, not just the kernel after booting. Besides, what happens if my kernel change does in fact break the graphics - I would assume that the fastboot broke the graphics, but when it comes to flashing it would still be broken.
I'm not marking this thread as solved until some kind of answer is to be had over this problem, but I will give 'thanks' to you for giving me the courage to properly mess with my phone and come out of the other side unscathed. Having that backup there will certainly give some reassurance in case something does go wrong!
This is indeed very strange and I can't attest to why flashing the boot works while booting it doesn't as I've never experienced this issue
Its possible you may need to update fastboot on PC but I doubt this
Maybe try to boot another kernel, a recovery would do
Grab a compatible recovery.img for your phone but different than the one you currently have installed and do the same procedure you did for the kernel
fastboot boot recoveryname.img
Now see if it boots you to a different recovery temporarily
Sent from my Nexus 4 using XDA Premium 4 mobile app
I just tried with TWRP 2.6.3.0. Same issue - it seems like the recovery has booted (Windows starts trying to install device drivers) but I just get a black screen.
Then this issue is baffling, never seen it before. I would update or reflash bootloader and update or reinstall fastboot.exe, the issue seems to lie in here but I can't say what it is off hand
Sent from my Nexus 4 using XDA Premium 4 mobile app
As mentioned earlier, I doubt it is the fastboot binary, since I get exactly the same problem on both Windows and Linux (different binaries, from different places). I don't really want to start messing around with the bootloader since as far as I'm aware if something goes wrong with that the only method of recovery is JTAG on the board.
True but it is hard to brick a nexus.
the phone side of fastboot resides within the bootloader so if your issue is here flashing a new one will be the only remedy I can think of, I will say I have flashed bootloader literally hundreds of times (used to buy and sell android phones) and never once bricked one. I used fastboot most every time for this purpose as it is the safest method and even though you seemed to be having an issue with fastboot I can't imagine flashing an appropriate bootloader through fastboot will cause you a brick but it also may not fix anything
But of course this choice is yours to do (I have flashed bootloaders many of times on my n4 without fail) and I can't think of anything else that would cause the problems you're having
Sent from my Nexus 4 using XDA Premium 4 mobile app
Where should I get the bootloader image from? Just from the Google stock ROMs, or is there a thread here on XDA?
In related news, by using the 'fudge' testing method (the kernel works if Windows starts installing drivers and the backlight fluctuates), I have managed to create a working custom kernel! At last I should be able to run LXC on it. Just need to work out why the display keeps tearing...
Great news!
Either extract the hboot from stock ROM (linked at Google dev) or look in the nexus 4 threads for someone who posted it ( they usually do) just be sure to check md5sum or sha1 first
Another note i see I never posted this
http://forum.xda-developers.com/showthread.php?t=2277112
May not help you much anymore but there will be a few tips for fastboot for ya
Sent from my Nexus 4 using XDA Premium 4 mobile app
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
Does anyone have a quick write up of how to do this? I have an HTC one and I have been running the Insert Coin roms, but now the new roms require TWRP and I dont want to end up with a bricked phone.
sjorge3442 said:
Does anyone have a quick write up of how to do this? I have an HTC one and I have been running the Insert Coin roms, but now the new roms require TWRP and I dont want to end up with a bricked phone.
Click to expand...
Click to collapse
Easiest way is to install GooManager > Grant SuperUser access > Menu > Install OpenRecovery Script > Confirm > Wait for it to download & finish.
https://play.google.com/store/apps/details?id=com.s0up.goomanager
http://teamw.in/project/twrp2 > It's explained here, along with the other methods. Just click on the Get TWRP for Your Device box at the top right and put in HTC One, then make sure to pick the right one. The recoveries are different between manufacturers and the M7/M8, obviously.
Pretty hard to brick install recovery on these things.
I would suggest just using fastboot, fastest and safest method
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
I would suggest just using fastboot, fastest and safest method
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's my preferred way to do it too, but TWRP themselves have the app install as their preferred way on their site.
So does clockwork and 4ext but I prefer fastboot. Choice is for the user I guess
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So does clockwork and 4ext but I prefer fastboot. Choice is for the user I guess
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Indeed. Another reason to suggest the app as it is more friendly to the timid ones.
It really does pay to get familiar with both fastboot commands and adb though, if you plan to mod your phone. At least to make sure that the drivers are loaded in worst case scenarios.
As far as I understand it, CWM or TWRP run in temporary partitions and in the RAM, much like boot tools on a PC such as Pmagic.
I started off with CWM via Odin on the PC and have since managed everything from there. I tried out TWRP by using a flashable zip in CWM, rebooted the usual way via the gui, tried out TWRP, then flashed CWM back and everything is fine.
It seems to me there is no danger and you just flash it the way you would a custom firmware. Plus you can back up and restore your recovery using either CWM or TWRP. In my short experience with it so far, you don't need an app, just flash and be happy. But always remember to have a backup or the original zip in case you wish to go back.
And if somehow you do mess something up (I guess it happens sometimes), make sure you have the right md5 to reflash in Odin. Simple. Just never delete anything you could need again.