I flash my OB with v20o (smartflash - root), its ok, root,
Now i can flash with v20C.kdz , original p970H.
I used tool to extrat files ap and cp.
Root is a big problem.
Flash smartflash or kdz, bam my root bye.
How i can make file .zip to flash for CWM.
FLash it with R&D testtool + workaround, use cwm injection method (search for it).
Thats how you ll get your phone with the correct software + root
I found use cwm injection method, but is not clear to me.
When i flash with V20o - rooted, i used smartflash, after process reboot in cwm and install from zip superuser. Thats it i do.
After flash using smartflash phone reboot in cwm, send superuser and ok.
the question is how inject cwm. I read topic about this but is not clear for me.
Can you help me?
I can only guide you here again: http://forum.xda-developers.com/showthread.php?t=1512203
I think it doesnt work with smartflash. But if you use an already rooted version, there also is no need to inject
If you are in CWM, simply make a full wipe and you can install any custom ROM you want already.
Then there is no need to really root and boot it
in this topic
http://forum.xda-developers.com/showpost.php?p=23788913&postcount=170
File cp ap, flash smartflash, auto reboot in cwm mode, install SU.
how make cwm inject in file to flash? is the question.
Phone simple reboot in cwm after flash witch SF.
And don't send SU to phone in first boot, bye bye root, need flash again and send zip SU.
I want make this in other V20XX, its cool.
When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe
How inject cwm in my files, i have files and i need how inject cwm. that it
N00BY0815 said:
When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe
Click to expand...
Click to collapse
All this ok for me.
Simple i do, in my files, i want inject cwm. Only this so
I think is that
Op afraid that lg might know this and patch it. I call that's a bull. I don't think lg engineer didn't know how to use dd. As long as we have unecrypted bin file we can patch it. Btw, how can one conceal a patching method using simple dd when you have unpatch file and patched file to compare? Even I managed to figure it out. Op true intention known only to himself.
So, to patch your bin file: (this is done on ubuntu, i don't know if windows got dd)
1. Download cwm at http://download.clockworkmod.com/rec...8.1.3-p970.img to the folder where you keep your bin file.
2. Open terminal and cd to the same folder as above
3. What we need to find is the location where we're suppose to copy cwm into the bin file. dd is bit-stream reader and it will show us the location in term of bytes. We need to search for ANDROID! string. So type:
dd if=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin| strings -n 8 -t d| grep ANDROID!
result:
1436661 ANDROID!
1703936 ANDROID!
6422528 ANDROID!
bla..bla..bla...
4. Look of the last entry which contain the ANDROID! string and take note of its byte location (6422528 in this case)
5. Now it's time to copy cwm into the bin file. Type:
dd if=<cwm.img> bs=1 seek=<byte location> conv=notrunc of=<rom.bin>
So in this case:
dd if=recovery-clockwork-touch-5.8.1.3-p970.img bs=1 seek=6422528 conv=notrunc of=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin
6. That's it. Your rom is ready to be flash using smartflash tool. You can run the same command in step 3 to verify that cwm is succesfully copied into the bin file. If at the same byte location the ANDROID! string change to [email protected] then you're good to go.
Don't waste your bandwidth to download the op's file if you can do this yourself and beside there's nothing to test, not that op modified the rom in any way. You would be better off testing huexxx zues rom imho.
Savvy?
Edit: Forgot to add. Credit goes to people who found this rooting method. I didn't found it only take a look at it.
Sent from my LG-P970 using XDA App
Related
this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
dtbang721 said:
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
Click to expand...
Click to collapse
hi
if u have CWM then down load the RC2 put it on root of ur SD
and flash it via CWM RC2 is pre rooted
dtbang721 said:
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
Click to expand...
Click to collapse
refer to this thread
http://forum.xda-developers.com/showthread.php?t=1268695
parrkhi had explaind it well
or else go to this thread directly
http://forum.lowyat.net/topic/1985476
here loock down for the clockwork mode method
u can download these zip files directly to ur phone jst keep them in root folder
Always click thankx if u find it useful
here is the mediafire link for .zip files that u need for all this work.
http://www.mediafire.com/?evfo2dlq9m92w
go to this link download file ( i consider u have cwm already installed on your phone) if u dont have cwm dont worry give it a try in this link u will find a .zip file named as recovery,..zip jst rename it to update.zip and install it from recovery menu// u can also give this update thing a try with the su.zip files file are main for rooting
Thanks for reponse. But I mention that my phone cant connect to pc, I've tried it alot, I cant connect my phone to pc in download mode so I cant instant cwm. everything I can try is self root apk or flash a rooted rom with base stock recovery.
okk if u cant flash cwm then its quite troubling
if ur usb dosn't work why don't u rush to the service center they will solve this problem in say 15 to 20 mins... better go there and get it serviced ...
Not possible yet without getting it in download mode...
dtbang721 said:
Thanks for reponse. But I mention that my phone cant connect to pc, I've tried it alot, I cant connect my phone to pc in download mode so I cant instant cwm. everything I can try is self root apk or flash a rooted rom with base stock recovery.
Click to expand...
Click to collapse
vibhor15 said:
Not possible yet without getting it in download mode...
Click to expand...
Click to collapse
Well you can do that. I mean you can install CWM recovery without connecting your device via USB.
If you can download CWM recovery or Recovery menu directly on your device, follow these instructions.
Extract recovery.img file from downloaded zip file.
Keep it in sdcard's root directory. (/sdcard/recovery.img)
Now copy following commands and save it as Install_recovery.sh in your sdcard's root directory
Code:
#!/system/bin/sh
mkdir /sdcard/fih
mount -t vfat /dev/block/mmcblk0p1 /sdcard/fih/
cd /sdcard/fih/image/
mv /sdcard/fih/image/recovery.img ./recovery.img
cd /
umount /sdcard/fih
rm -r /sdcard/fih/
And use any script manager or Terminal emulator to run this file.
Using terminal emulator:
Code:
cd /sdcard/
sh Install_recovery.sh
Now boot into recovery. You should boot into new recovery.
P.S. Similar How-To is also posted in a thread: Restoring stock recovery: (without Download mode). I have just modified it a bit.
Thanks! I'll give it a try. But does Script manager and terminal emulator is a apk that i can install and use to run the command saved in Install_recovery.sh?
So that I run terminal emulator apk and type
"cd /sdcard/
sh Install_recovery.sh" ?
ok. I've tried but the emulator report errors. I think I must have rooted phone to install cwr with your solution. The error is
$ export PATH=/data/local/bin:$PATH
$ cd /sdcard/sh install_recovery.sh
cd: bad substitution
$ cd /sdcard/
$ sh install_recovery.sh
, Invalid argumentsdcard/fih
mount: No such file or directory
cd: can't cd to /sdcard/fih/image/
failed on '/sdcard/fih/image/recovery.img' - No such file or directory
cd: can't cd to /
failed.
rm failed for /sdcard/fih/, No such file or directory
$
So how do I get cwr on my phone to root it via cwr method?
dtbang721 said:
ok. I've tried but the emulator report errors. I think I must have rooted phone to install cwr with your solution. The error is
$ export PATH=/data/local/bin:$PATH
$ cd /sdcard/sh install_recovery.sh
cd: bad substitution
$ cd /sdcard/
$ sh install_recovery.sh
, Invalid argumentsdcard/fih
mount: No such file or directory
cd: can't cd to /sdcard/fih/image/
failed on '/sdcard/fih/image/recovery.img' - No such file or directory
cd: can't cd to /
failed.
rm failed for /sdcard/fih/, No such file or directory
$
So how do I get cwr on my phone to root it via cwr method?
Click to expand...
Click to collapse
Oh yes! I forgot.
Will try to come up with an answer as soon as possible.
Sent from my CSL-MI410 using XDA App
dude ... do you have a memory card reader ...???
if u have a card reader then jst remove ur card from phone plug into pc copy all the files i.e cwm recovery update.zip and su.zip
[Installation Instructions]
[Using CWM recovery]​
Copy CWM recovery-fb0-v5_signed.zipin sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose CWM recovery-fb0-v5_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
i suggest rename the .zip file to update.zip
and then follow rooting instruction
I mean that I've got a stock rom without root. So I havent CWM recovery installed on my phone.
My usb hub on my phone has broken and the phone waranty service not avainable in my country so I need a root solution without usb connecting.
As I know I need rooted phone first to install CWM recovery. Or I need a method to install CWM recovery by stock recovery.
I also try to flash back to 2.2 froyo version to root my phone by gingerbreak apk but not successed. When I try to flash any stock rom 2.2 or 2.3.4 the stock recovery allways report error and didnt worked. The error that stock recovery say is:
Enter lauch_image_update
Prepare failed rc= -209
PID doesnt match!
You cant download this nb0
Some error during preparing
So now I cant do anything with stock recovery only hardreset can done. No flash firmware.nb0 rom no update the update.zip
And when I try to flashing update.zip (CWM recovery-fb0-v5_signed_2.zip I renamed it to update.zip) stock recovery say error that:
verifying update package
E:signature verification failed
dtbang721 said:
I mean that I've got a stock rom without root. So I havent CWM recovery installed on my phone.
My usb hub on my phone has broken and the phone waranty service not avainable in my country so I need a root solution without usb connecting.
As I know I need rooted phone first to install CWM recovery. Or I need a method to install CWM recovery by stock recovery.
I also try to flash back to 2.2 froyo version to root my phone by gingerbreak apk but not successed. When I try to flash any stock rom 2.2 or 2.3.4 the stock recovery allways report error and didnt worked. The error that stock recovery say is:
Enter lauch_image_update
Prepare failed rc= -209
PID doesnt match!
You cant download this nb0
Some error during preparing
So now I cant do anything with stock recovery only hardreset can done. No flash firmware.nb0 rom no update the update.zip
And when I try to flashing update.zip (CWM recovery-fb0-v5_signed_2.zip I renamed it to update.zip) stock recovery say error that:
verifying update package
E:signature verification failed
Click to expand...
Click to collapse
There is still one option left.
You can create your own nb0 file (since thats the only option working), which has cwm recovery and rooted ROM.
Right now i am away from my work place so cant help you till next monday.
Sent from my CSL-MI410 using XDA App
I'm right here waitting!
dtbang721 said:
I'm right here waitting!
Click to expand...
Click to collapse
napstar is right make ur own .nb0 i m working on it too still no success having boot loops with usb when i flash it ... dont know why nd don't have plenty of time to log cat the problem ...
kshitij_bhatt said:
napstar is right make ur own .nb0 i m working on it too still no success having boot loops with usb when i flash it ... dont know why nd don't have plenty of time to log cat the problem ...
Click to expand...
Click to collapse
I have another android ( x10 mini pro) and I know that we can make a backup by stock recovery or cook a rom for flashing by stock recovery. But before public the rom the deverloper have to tested it because bootloop is the problem of flashing rom. So before flashing new rom we need do a hardreset and after flashing rom we also need a hard reset to solve boot looping problem.
because of brocken usb hub on my phone. I need tested before flashing. :'(
the test is:
1 make a nb0 file from a phone that working good.
2 try to flash nb0 by stock recovery to another phone to confirm that nb0 work good for all phone.
3 Note that some rom is working realy good for some phone but can make bootloop for another phone because of different keynell they are ussing or we dont make factory reset and do a wipe data and cache also get bootloop problem
nanana its not beautyfull life.
My First post...
dtbang721 said:
nanana its not beautyfull life.
Click to expand...
Click to collapse
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
CacingKalung said:
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
Click to expand...
Click to collapse
yes. that's my problems. Ill try to flash rc1. may be the problem is my usb cable. but i have not got any blackberry cable. I just have a stock cable and a sony erricson cable and a nokia cable. but none of them work.
CacingKalung said:
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
Click to expand...
Click to collapse
dtbang721 said:
yes. that's my problems. Ill try to flash rc1. may be the problem is my usb cable. but i have not got any blackberry cable. I just have a stock cable and a sony erricson cable and a nokia cable. but none of them work.
Click to expand...
Click to collapse
Thats a good option. I thought you have already tried it and received an error saying "### ID mismatch"
Anyway if you have not downloaded it yet, then I have one other option for you. I have created an nb0 file which contains only CWM recovery and nothing else.
This file will install Recovery menu v2 which includes both CWM and stock recovery and no system files/data files.
To install, download attached file to your device and extract firmware.nb0 file from it. (For zip file extraction, you can use ES_explorer).
And then install it using your stock recovery.
After installation system will boot in your current ROM. Reboot into recovery and you will find recovery menu instead of stock.
Disclaimer: I am not an expert in creating nb0 file. Here I have just deleted all unnecessary files from stock nb0 file and replaced recovery image with recovery menu's image. So far this works on my device. I have tried it installing when I am on stock ROM. (Though it was not necessary)
I am not to be held liable/responsible if you damage your phone by following / not following this post.
MD5SUM hash code:
0b72eea3bc419bc66d64173df193a915 firmware.nb0
Does it matter if i flashed kernel, wipe, install rom? Thats how i been doing..
Just curious cuz i seen it saying u need to wipe, flash kernel, than immediately rom.
But once i flash kernel phone reboots which means i have to force close/take out battery so the phone wont try to boot to os.
greypimps said:
Does it matter if i flashed kernel, wipe, install rom? Thats how i been doing..
Just curious cuz i seen it saying u need to wipe, flash kernel, than immediately rom.
But once i flash kernel phone reboots which means i have to force close/take out battery so the phone wont try to boot to os.
Click to expand...
Click to collapse
in fastboot, the phone will not reboot until you tell it to
Code:
fastboot flash boot boot.img
thats it, if you do a fastboot reboot command after, thats why you are getting a reboot.
after flashing the kernel, just hit 'bootloader' then 'recovery' and it will boot straight into recovery
What about when you flash a kernel that has other files with it? Example below:
bcm4330.ko
From the .bat file that came with it, it copies it over to the system modules directory. I mean I guess if you mount the /system directory in CWM then you could flash via adb. The file up above being named bcm4330 makes me think it is some kind of network driver.
unc-newbie said:
What about when you flash a kernel that has other files with it? Example below:
bcm4330.ko
From the .bat file that came with it, it copies it over to the system modules directory. I mean I guess if you mount the /system directory in CWM then you could flash via adb. The file up above being named bcm4330 makes me think it is some kind of network driver.
Click to expand...
Click to collapse
If its copying over a .ko file, you better already have a rom installed since ko files go in /system/lib/modules. If you copy that file over and then install the rom it was all for nil.
Sent from my GT-I9100
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
[My i9305 is not connecting with PC, I tried *#7284# (UART & USB > PDA), but it didn't work...
so I have to find the following way to root my device & to install custom ROMs... It worked perfectly...
But I still want to connect my phone to PC through USB, any help will be appreciated. Thanks]
First, download and install 'Framaroot.apk'. It is available at http://forum.xda-developers.com/showthread.php?t=2130276
Now, open the app and tap on 'Aragorn'. And your device is rooted .
It you want to use custom ROMs, you need custom recovery. So,
Install 'Terminal Emulator.apk' form Play Strore.
Download any TWRP/CWM recovery image for i9305 (.img file). [For TWRP images: http://techerrata.com/browse/twrp2/i9305]
Place it on your internal storage (on root directory).
Rename the .img file to 'recovery.img'
Now, open 'Terminal Emulator' and type following commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p9
or, You can use 'Mobile Odin' / 'Recovery Tools - Flasher' [available in Google Play] to flash .tar recoveries.
You are DONE .
I think it is more advisable to flash recovery using an Application rather than the command line, since one digit here and there, you have a bricked phone.
I would suggest use an app like this after rooting the phone
mtatohin said:
[My i9305 is not connecting with PC, I tried *#7284# (UART & USB > PDA), but it didn't work...
so I have to find the following way to root my device & to install custom ROMs... It worked perfectly...
But I still want to connect my phone to PC through USB, any help will be appreciated. Thanks]
First, download and install 'Framaroot.apk'. It is available at http://forum.xda-developers.com/showthread.php?t=2130276
Now, open the app and tap on 'Aragorn'. And your device is rooted .
It you want to use custom ROMs, you need custom recovery. So,
Install 'Terminal Emulator.apk' form Play Strore.
Download any TWRP/CWM recovery image for i9305 (.img file). [For TWRP images: http://techerrata.com/browse/twrp2/i9305]
Place it on your internal storage (on root directory).
Rename the .img file to 'recovery.img'
Now, open 'Terminal Emulator' and type following commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p9
You are DONE .
Click to expand...
Click to collapse
Framaroot did not work for my GT-I9305. It says 'Error #6' . Are they different from each other? Exynos? I am in UK using international edition.
after rooting using framaroot I flashed costum recovery.IMG using mobile Odin. that is safer
@ enarsee: Yeah, you can use 'Mobile Odin' too. Thanks for your suggestion.
@ shayind4: I'm getting the same error on 4.3 ROM! I think you have to try something else. You can try this http://forum.xda-developers.com/showthread.php?t=2352669
@ reymasters: Yes, you can use it. Its safe and easy. I will edit my post.
98926828
This method doesn't work with my GT-I9305 also. I'm so sorry I flashed 4.3 with odin...
elektronchika said:
This method doesn't work with my GT-I9305 also. I'm so sorry I flashed 4.3 with odin...
Click to expand...
Click to collapse
This method works upto 4.1.2