Related
Here are the Steps I took to convert the data folder to ext 2. I'm sure we can do more folders but I'm unable to write (anyone?) the update scripts.
Start with a fresh install of Team Whiskey's Rom
Goto to the I9000 thread and follow the instruction on uploading a kernel to be repacked.
I selected all the check marks before re packing and downloaded the new kernel.
Download the ext2 update zip from the thread. Rename the zip file to update.zip.
Grab the kernel(tar file) you downloaded from the site and use odin to install.
After booting back up rename the z4mod.ext2.update zip file to update.zip.
Reboot into clockwork and apply update.zip
After booting back up your data file should now be ext2.
To check use terminal emulator our adb and type mount. The data line should now say ext2 instead of rfs.
Note: When I tryed to use the ext2 update zip file without renaming to update.zip it did not work. I continuously recieved SD mount errors.
I can't stress enough to read the topic in the I9000 development thread titled z4mod breaking free from rfs(link below) so you understand what you are doing and the process that is required.
My instruction does not detail that whole process. I'm not responsible for you or what you do by following this brief instruction.
Very Snappy after this mod. Absolutely no issues for me.
Quadrant = 1700
Enjoy!!!
Credit goes to RyanZA and the z4ziggy ; not me.
Source: [z4mod] Breaking free from RFS [Stage II - version 0.3 Alpha - With online patcher!]
Files I used to get this to work.
zImage.tar (The Zimage I used to repack was taken out of Obsidian V2. (DO NOT USE THIS FOR IMAGE FOR ANY OTHER ROM THAN OBSIDIAN V2)
Also, XDA does not allow uploads of tar files so I compressed the tar into a zip format. Make sure you extract this file and use the .tar file within Odin.
Update.zip - This file was downloaded from the I9000 Z4Mod Thread entitled z4mod.ext2.update.zip. All I did was renamed to update.zip which for some reason allows this conversion process to take place.
Sent from my SGH-T959 using XDA App
I would highly suggest posting links to the threads you refer to as well as any files you have available. Good post though, I plan on using this.
Sent from my SGH-T959 using XDA App
Thanks - 1632 Quadrant on Onyx 2.2
Does your kernel have the stock or clockwork recovery? Easy way to check is do adb reboot recovery. If it goes into clockwork then the stock recovery was replaced.
The file you attached is ready to use or do we need to repack?
Greenarcher707 said:
The file you attached is ready to use or do we need to repack?
Click to expand...
Click to collapse
Ready to use.
Sent from my SGH-T959 using XDA App
Ashex1 said:
Does your kernel have the stock or clockwork recovery? Easy way to check is do adb reboot recovery. If it goes into clockwork then the stock recovery was replaced.
Click to expand...
Click to collapse
I'm using cwm. But I could not use "select zip option" you can try it though.
Sent from my SGH-T959 using XDA App
Bugger, from what I know ClockworkMod has some compatibility issues with JK2 unless the version that z4build uses is compatible.
Great, this broke busybox. Now I'm in 2.2 w/o root...
Xencer said:
Great, this broke busybox. Now I'm in 2.2 w/o root...
Click to expand...
Click to collapse
Use Titanium Backup to fix busybox.
Is there one for ext4?
funkyu00 said:
Is there one for ext4?
Click to expand...
Click to collapse
Seconded. It'd be great to get /dbdata, /cache, /system onto ext4 too (I thought that was the main benefit of z4mod?)
jamesyl said:
Seconded. It'd be great to get /dbdata, /cache, /system onto ext4 too (I thought that was the main benefit of z4mod?)
Click to expand...
Click to collapse
Unlikely as the kernel does not support Ext4.
Also, to anyone who has tried this: Is the kernel from the op already patched? I tried throwing it into the the online patcher and the patcher just spit out a message informing me that what I uploaded was already patch. However, when I jump into recovery, I get recovery 2e and not clockwork, which leads me to believe otherwise.
Perhaps odin did not actually install it?
how did u boot into clockwork? 3 button or through rom manger? it doesnt work for me with three button still says can not mount
hoipefully someone adds to the script so it can convert more partitions.
How did you get into Clockwork recovery if you replaced the update.zip file the stock recovery uses to get into it?
I booted through RomManager. It gave the little green Android dude with the download box and got right into recovery. Working great so far.
RobBull69 said:
I booted through RomManager. It gave the little green Android dude with the download box and got right into recovery. Working great so far.
Click to expand...
Click to collapse
Yes, I figured out that the Z4 patch kernel replaces the stock recovery with clockwork.
kangxi said:
How did you get into Clockwork recovery if you replaced the update.zip file the stock recovery uses to get into it?
Click to expand...
Click to collapse
the way this phone is set up has the recovery image packaged with the kernel in the file called zImage. when u use the z4mod to modify that zImage file, the website unpacks the whole zImage file, does its thing with the kernel modding, and now (i say now because this is a newer feature) replaces the standard 2e recovery with clockwork recovery. when you flash the zImage, whether repackaged in a rom or as a tar in odin, the new clockwork recovery is flashed to '/system/bin/recovery' replacing the 2e recovery. i have confirmed this by running the command 'recovery' from terminal while booted after flashing a z4modded kernel. i do not recommend trying to run recovery while booted as the phones display started going crazy.
the problem with having clockwork mod as the primary recovery is the fact that there is a major issue with mounting both the internal sd and external sd (even one at a time as well as both together) as clcokwork mod reports it doesnt recognize device at 'mmcblk0' or 1 when clockworkmod recovery is the primary recovery.
jmart211in said:
the problem with having clockwork mod as the primary recovery is the fact that there is a major issue with mounting both the internal sd and external sd (even one at a time as well as both together) as clcokwork mod reports it doesnt recognize device at 'mmcblk0' or 1 when clockworkmod recovery is the primary recovery.
Click to expand...
Click to collapse
That's why I backed out of it and went back to the stock kernel - that and the fact there was a weird flicker at the top of the screen when booting.
hey guys right now im using darchstar's godspeed recovery.. but whats the most recommended recovery mode that everyone uses?
My personal favorite is Clockwork Mod Recovery. You can find the latest for our phone in the Andorid Development section, on the first page of the aospGBmod thread. Should be easy to find as it is right on top 99% of the time due to popularity.
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
laie1472 said:
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
PMGRANDS said:
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
sent from my twopointtwo themed hero
thoughtlesskyle said:
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
sent from my twopointtwo themed hero
Click to expand...
Click to collapse
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
I currently use ClockworkMod Recovery 2.5.0.1 for recovery mode.
Specs of my Sprint HTC Hero/APA6277 are...
Android version: AOSP
Baseband version 2.42.02.10.29,
Kernel version 2.6.29.6-aospMD [email protected] #1
Mode version: aospMOD-0.9.9.2
Build number: FRG83
I plan on flashing the AOSP GB Mod to my device as soon as a stable version of it becomes available.
kyouko said:
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
Click to expand...
Click to collapse
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
Thanx A lot Kyouko!!
I Downloaded It....
But I Wanted To Pick Your Brain A Bit, Before I Flashed It.... Lol!
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Sent from my HERO200 using XDA App
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
PMGRANDS said:
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Click to expand...
Click to collapse
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Darch's Recovery is an overclocked version of AmonRa with EXT4 Support. See here for more info
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
PMGRANDS said:
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
kyouko said:
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
Click to expand...
Click to collapse
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
thoughtlesskyle said:
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
Click to expand...
Click to collapse
Weird.. Do this for me, open up terminal emulator and type:
Code:
su
flash_image
you should get a return line saying:
Code:
usage: flash_image partition file.img
*see attached picture for example*
Make sure you're inputing it exactly the way I had it in the previous post - underscores and all. If the recovery.img name is different make sure whatever you type is exactly what the img is called.
If it's not in the /sdcard/ directory enter the correct one.
Example) /sdcard/downloads/oldrecovery.img
On my second attached picture you can see that the command worked, but since I already have that recovery flashed it aborts.
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
I'd just use CW for Gingerbread, RA doesn't wipe boot or system I believe.
Does anyone know if you are able to Wipe Data/cache/dalvik from adb shell?
just making a script to automate the process.
anyone know the commands?
thanks
i've been through the developers thread for three days, and don't understand all the lingo, if i could please get step by step or links please. i appreciate all the work you developers have done with the new rom and kernal tweaks. really interested!! can you please help..thanks, donations coming for all
First, get openzio's clockworkmod recovery if you are a cricket user, then setup the Android SDK, then use fastboot to boot our recovery, BACKUP YOUR CURRENT ROM, after the backup is complete, choose install zip from SD, choose openzio rom 2.1 by Spz0 and once complete reboot. Dial *228 and enjoy.
Sent from my Zio using XDA Premium App
Fastboot is in the rom. All he has to do is open it and copy it to where ever and then navigate there in Command Prompt. I am assuming you are on a Windows 7 machine? You'll also need like Mattix said, a copy of the recovery, which also means you need a copy of 7zip or something like that to unpack the rar and get the img out. This is a want vs know how thing.
sinisin said:
Fastboot is in the rom. All he has to do is open it and copy it to where ever and then navigate there in Command Prompt. I am assuming you are on a Windows 7 machine? You'll also need like Mattix said, a copy of the recovery, which also means you need a copy of 7zip or something like that to unpack the rar and get the img out. This is a want vs know how thing.
Click to expand...
Click to collapse
I think you got ur roms/zips mixed up m8.
My Fastboot recovery pack is all you need to use clockworkmod recovery.
Use Clockworkmod Recovery to back up your current rom
Download OpenZio v2.1 ROM, dump it to your SDcard, boot into clockworkmod recovery and "install zip from SDcard"
Hi to all.
I have a rooted Incredible S (through HTCDev), stock ics rom and S-ON.
Is there a way to install a modded kernel on stock rom?
jauffre said:
Hi to all.
I have a rooted Incredible S (through HTCDev), stock ics rom and S-ON.
Is there a way to install a modded kernel on stock rom?
Click to expand...
Click to collapse
theres a guide in xics kernel thread
Can you give me the link, please?
I tried XS ICS 2.2, and followed some advices to make it work, but it didn't.
jauffre said:
Can you give me the link, please?
I tried XS ICS 2.2, and followed some advices to make it work, but it didn't.
Click to expand...
Click to collapse
l0st.prophet said:
Changelog
Instructions for S-OFF Users
Simply flash XS-ICSvX.X.zip in your favourite recovery!
Instructions for manual flashing (HTCDev.com unlocked S-ON Users)
Thanks to MrToastbrot for instructions
Step 1: Download the XS-Kernel.zip, then open the Zip on your computer and extract the file mkbootimg.sh in "kernel"
Step 2: Open mkbootimg.sh in a texteditor like notepad++ or notepad, then edit the following in line 3:
Code:
output /tmp/newboot.img
to
Code:
output /sdcard/newboot.img
Step 3: Save your edited file and place it back in your zip, copy your modified zip to your phone-sdcard and install it in the recovery. Then reboot your phone and connect it to pc and take the newboot.img from the root of the sdcard.
Step 4: Now reboot your phone into bootloader and flash it via fastboot flash boot newboot.img
Step 5: Once you phone has booted, mount the system as r/w using something like ES file explorer or Root explorer, then type the following:
Code:
adb push bcm4329.ko /system/lib/modules
Set permissions to rw-r--r--, reboot and enjoy!
Sweep2Wake: Q&A
Q: How do I disable / enable the feature?
A: Two options
Change the value in the file /sys/android_touch/sweep2wake to either 0 for disabled, 1 for enabled and 2 for enabled with backlight. This will be reset upon rebooting.
If your ROM supports init.d scripts, then flash the zip to enable or disable, this will stick over a reboot.
Q: It keeps taking screenshots when I lock the screen!?
A: This is due to an incompatibility with this feature and the native screenshot in Sense. TO stop the screen shots, you need to edit your build.prop and change the property ro.htc.framework.screencapture to false, and then reboot.
Click to expand...
Click to collapse
there
Thanks!
The problem is that although i changed the mkbootimg.sh file, i cannot find the newboot.img.
jauffre said:
Thanks!
The problem is that although i changed the mkbootimg.sh file, i cannot find the newboot.img.
Click to expand...
Click to collapse
Try looking on your sdcard. Assuming you followed the guide correctly...
I followed the guide as it is, i modified the file as the guide says, and there's no newboot.img file on sdcard.
jauffre said:
I followed the guide as it is, i modified the file as the guide says, and there's no newboot.img file on sdcard.
Click to expand...
Click to collapse
Upload your modded zip file.
Nonverbose said:
Upload your modded zip file.
Click to expand...
Click to collapse
here it is
jauffre said:
here it is
Click to expand...
Click to collapse
Your modded zip is working on my phone but It's s-off. I found the newboot.img on sdcard root. Run your flashable zip again then go to tools>copy recovery.log to sdcard. It will be in your 4ext directory. Have a look and see if you can spot any errors. Upload here if you need any help.
Nonverbose said:
Your modded zip is working on my phone but It's s-off. I found the newboot.img on sdcard root. Run your flashable zip again then go to tools>copy recovery.log to sdcard. It will be in your 4ext directory. Have a look and see if you can spot any errors. Upload here if you need any help.
Click to expand...
Click to collapse
This is the log.
I don't understand it very much, but it seems that it copies the boot.img file, and then there are some errors.
could you upload the newboot.img file?
jauffre said:
This is the log.
I don't understand it very much, but it seems that it copies the boot.img file, and then there are some errors.
could you upload the newboot.img file?
Click to expand...
Click to collapse
I'm not on stock Rom, so my newboot.img will not work on your phone because it has a different ramdisk. You might want to try changing your recovery to 4ext touch.
Nonverbose said:
I'm not on stock Rom, so my newboot.img will not work on your phone because it has a different ramdisk. You might want to try changing your recovery to 4ext touch.
Click to expand...
Click to collapse
ok; i changed recovery to 4ext, and here is the log.
jauffre said:
ok; i changed recovery to 4ext, and here is the log.
Click to expand...
Click to collapse
Wow still got that BOARD_KERNEL_CMDLINE error happening. Try flashing tpbklakes unsecured boot.img and then update http://forum.xda-developers.com/attachment.php?attachmentid=1238549&d=1343964381
Nonverbose said:
Wow still got that BOARD_KERNEL_CMDLINE error happening. Try flashing tpbklakes unsecured boot.img and then update http://forum.xda-developers.com/attachment.php?attachmentid=1238549&d=1343964381
Click to expand...
Click to collapse
Thank you Nonverbose!! It worked!!
Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.
Click to expand...
Click to collapse
Please Lock!
Placeholder reserve
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)
Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu
Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror
Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.
Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?