Related
Hi,
I am just wondering, i am rooting my Nexus one 2.3.3 and in the instruction it says "Also download and copy the SU program to your SD card and name it sd.zip."
My question is where do i get this file from?
Thanks.
masantula said:
Hi,
I am just wondering, i am rooting my Nexus one 2.3.3 and in the instruction it says "Also download and copy the SU program to your SD card and name it sd.zip."
My question is where do i get this file from?
Thanks.
Click to expand...
Click to collapse
Go to the "rooted" link in my signature, and take the Eclair/Froyo version
Isnt the Su file in your signature for froyo? And isnt 2.3.3 gingerbread? or it works?
Thanks.
masantula said:
Isnt the Su file in your signature for froyo? And isnt 2.3.3 gingerbread? or it works?
Thanks.
Click to expand...
Click to collapse
The file in the thread that you want is: su-2.3.6.1-ef-signed.zip It works for Eclair, Froyo and Gingerbread.
efrant said:
The file in the thread that you want is: su-2.3.6.1-ef-signed.zip It works for Eclair, Froyo and Gingerbread.
Click to expand...
Click to collapse
Great, thanks alot for the help
im also rooting but grj22 build, what do i need to download to my sd before i unlock my boot loader?
To unlock your bootloader, you don't need anything on the sdcard. To continue with rooting, you would need to have a custom recovery on your computer and use fastboot to install it after you unlock it, then flash the zip that was mentioned above (which would need to be on the sdcard) to actually root your phone from the custom recovery.
bassmadrigal said:
To unlock your bootloader, you don't need anything on the sdcard. To continue with rooting, you would need to have a custom recovery on your computer and use fastboot to install it after you unlock it, then flash the zip that was mentioned above (which would need to be on the sdcard) to actually root your phone from the custom recovery.
Click to expand...
Click to collapse
can i use adb to put the file on the sd card i tried unsuccessfully and now my phone wont boot. but i still have bootloader and fastboot, also adb devices works? ugh , such a newb but it seems all is not lost, right?
Install recovery, boot into recovery, mount the SD from recovery, then move the file over to the SD using windows...
danger-rat said:
Install recovery, boot into recovery, mount the SD from recovery, then move the file over to the SD using windows...
Click to expand...
Click to collapse
ok col, now heres the kicker...i flashed recovery-RA-nexus-v2.1.1.img as my recovery , and im pretty sure i put cryogen 7 on the sd so i fudged it up pretty good.whats the best recovery to flash i, if had gingerbread 2.3.4 which came ota au natural? also im finding the su-2.3.6.1-ef-signed.zip file either, anyone have a proper link to it?
If you're going to flash cm7 or ANY pre-rooted rom you do not need to bother with the su.zip. Just flash the rom from custom recovery.
i keep getting the no img wrong img message in fastboot when i try to hboot?
Fastboot is used to flash the custom recovery. The recovery flashes the rom.
I can't understand your post in the first place so I dont know what is your actual issue.
But read the wiki.
Sent from my Xoom using Tapatalk
yes!!! it worked i knew i was close.
albundy2010 said:
Fastboot is used to flash the custom recovery. The recovery flashes the rom.
I can't understand your post in the first place so I dont know what is your actual issue.
But read the wiki.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
well i used my girls htc 3g slide and loaded a the file before mentioned to my sd and BLAM! im so happy i almost cried a lil bit! so excited thanks to albundy and everyone else who walked me through this and gave me helpfull tips will post photos of my success!
big al,so now i have tested a few roms didnt like cm7 to much nightly or stable but i found an 2.3.4 ota vanillia and i like it of course cause its what im used to stock basicly. Well now im having problems running my gallery or music player or camera? seems like im missing something again? is it cause im rooted> i think i rooted?hmmm uh help. thanks
nevermind got it worked out downloaded a root version and wipe wiped flashed and Blam! im back.
Hi All,
1. Will unlock the bootloader wipe out the phone? If so how to root 2.3.6 without losing data?
I want to backup my data in the N1, then do flash the CM7 mod onto that.
It's in retail 2.3.6, I want to backup my data first.
sms, did with sms backup and restore.
call logs and bookmarks, how I backup them?
apps, want to backup with titanium backup, but hasn't root the phone yet.
I found the root guide for 2.3.6 here
https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
But it wants me to unlock the bootloader first, unlock the bootloader will wipe the phone so I will lost my data right?
apps can be redownloaded, so how I backup my call logs and bookmarks without root (yet)?
--
another question is I see the note for the latest N1 CM7 build is
'The latest radio is needed to run CyanogenMod 7'.
I can see my phone already has baseband of 5.08.00.04, do I need to do anything related to the radio while I flashing CM7?
Regards,
Sorry, there is NO way to back up your data if you are on 2.3.6 with a locked bootloader and without root.
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Bexton said:
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Click to expand...
Click to collapse
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Bexton said:
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Click to expand...
Click to collapse
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
efrant said:
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
Click to expand...
Click to collapse
Well, as said: actually there's no big difference. And yeah, indeed you're right about the recoveries. But to address one of your (/my) points:
The SDK is an application package that needs to be installed.
Fastboot, as well as the ADB are standalone executables; there is nothing to be installed. These executables are just a tiny part of the whole SDK Package. There's no need to download and install all the SDK Package, if you'd need just the adb, the fastboot and the drivers. Thus you'd save at least some time (and bandwith).
Also, when i'll include the install script tomorrow (as it has been with v1), it will reduce the number of commands you have to type in the terminal to two.
So the bottom line: eventhough you're right about (almost all of) your contras, if you'd need to start with an untouched phone and computer it's definitely faster - and i think, also just simpler - to do it "my way".
But.. anyway.. it's the same way.
---------- Post added at 10:46 PM ---------- Previous post was at 10:34 PM ----------
PS: And therefore - to re-answer your initial question:
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Depending on your working environment, it simply can save some time.
Howdy y'all!
I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.
It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.
This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one
So, without further ado:
What is this?
This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.
Click to expand...
Click to collapse
How do I use it?
You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)
Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
Code:
fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
You need to replace the stuff in brackets with the path to the img file you downloaded from here...
Alternate Installation Method (ph39img)
Much easier installation once unlocked with HTCDev...
Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!
Click to expand...
Click to collapse
How is this different from the ClockworkMod image that's floating around here?
Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.
Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device )
I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
Changelog
recovery-take1 : initial release
recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks
Click to expand...
Click to collapse
Tips and Tricks (what works, and what doesn't)
Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...
The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://forum.xda-developers.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint
Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
Sorry about that!
Some rom.zip's don't work...
This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version
If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
HELP! I CANT GET INTO RECOVERY! *new!
If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.
Click to expand...
Click to collapse
How can I contact (chastise, praise, call names) you?
On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.
I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...
Click to expand...
Click to collapse
Standard "it might not work" clause
This software hasn't been thoroughly tested, and it might not work.
It might not backup things correctly, and it might not restore them right.
Please don't trust this software with anything sensitive or life-alteringly important.
I'd hate to say "I told you so!"
That's not to say this software doesn't work, it's just the standard disclaimer.
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
Thank you in advance!
Click to expand...
Click to collapse
Credits / Thank You's
IanWizard-cloud (testing, moral support )
Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
joeykrim
toastcfh
fattire
BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
..and lots of others!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!
Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.
already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now
Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.
Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!
well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?
Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium
Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC
Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.
for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.
Just put your new recovery in the superguide and gave you credit. Keep up the good work!
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100
Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks
Since some people asked me, I'm providing rooted system.img to be flashed by nvflash, an easy way to get v28g installed from kdz or smartflash rooted, for those who prefer to keep it as stockish as possible. The only mods I did from stock kdz backed up from my phone was to push su and superuser.apk.
This procedure did not wipe anything, so as a rule you shouldn't worry about backups, but I recommend you to use nvflash tool to make backups of all your partitions before trying this. Search here on dev's section to "nvflash toolkit", an excellent work from rmein, and use it to make backups.
Put the .img extracted from downloaded 7zip file on any functional nvflash folder, connect your phone in apx mode (without battery, BOTH vol up and down and plug it to usb), go to your nvflash folder and execute the following in cmd prompt.
nvflash.exe --bl fastboot.bin --download 23 rooted_system_v28g.img
Actually, I don't know if this command works on windows. Since I'm linux user (I'm sure that command syntax is useless to penguin's users), I didn't test this on win. So, if you used nvflash before on your win box and the previous didn't work, please let me know.
Download: http://db.tt/Qe6iLjpl
It's my personal dropbox folder. Please, feel free to mirror it and I'll update this OP, since I use my dropbox space to work.
Edit: leclanpim made an easy way to flash this system.img, putting a .bat file with nvflash.exe and the system itself in one zipped file, sharing it at https://docs.google.com/open?id=0Bw9sO0__Wuu-THkzcHpaeERmMHM
Thanks to him.
The easiest way to get root, imho, is to flash bootloader, cwm, and then root zip from cwm. All files are small and no data loose at all.
Sent from my LG-P990 using xda app-developers app
wfd said:
The easiest way to get root, imho, is to flash bootloader, cwm, and then root zip from cwm. All files are small and no data loose at all.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
You're right, but as I said, there's people like me that don't want touching bootloader and/or recovery.
Sent from my LG-P990 using xda app-developers app
Thank you louis, that's what I was looking for last weeks, then I found Homero's rooted 28G with some adds/mods. Now I'm downloading your system.img which is pure leaked 28G with the root as the only mod.
I'll tell you more.
Since some days I decided that from now on I'll test only custom 28G roms distributed in nvflash format: I nvflash the custom system.img, don't wipe my data, don't change bootloader, get rid of cwm and rom manager. It looks like the cwm round but I think it's faster and cleaner (maybe less risks of brick?), in addition, since I was used to copy my cwm backups on PC, using nvflash backup I have the full image of my rom straight on PC and I don't fill my external SD with neverending backups. Of course, using nvflash backups you cannot open and look inside like it is with cwm backups, but maybe some dev will find the way to do it.
I understand that SuperSkill, too, thought the same solution.
EDIT: just flashed from win7 and all is working.
Thanks, Man!...:good:
louiscypherbr said:
I'm providing rooted system.img to be flashed by nvflash, an easy way to get v28g installed from kdz or smartflash rooted, for those who prefer to keep it as stockish as possible. The only mods I did from stock kdz backed up from my phone was to push su and superuser.apk.
Click to expand...
Click to collapse
After trying V28E and G (Stefan's release with wkpark's unlocked bootloader and custom CWM) with different babsebands, I also decided to flash a "clean" stock V28G with the original bootloader, just to see if it resolves an in-call audio bug for me. So, this image came in handy, thank you! I backed up and restored my data partition using the nvflash toolkit. No problems with flashing, everything came up fine, with all my data intact. Hopefully, this setup will work with no audio issues until the ICS release (or a new leak... )
Thanks for this, now what's left are flashing it yes Walsh, I think this is a great way of supplying "roms". This method let's you keep locked bootloader and you can increase system partition, then flash only system.img with nvflash, correct? I'm just about to get Ubuntu into my desktop to extract the img and modify it as I like it......but what you guys have done lately are very respectful
Sent from the new smoothly LGP990
Hi,
I am on CM10 latest directly from GB official, i want to try your rom and downloaded the second file on your first post, but i cannot install it! when i click on flash.bat it does something and then says " coise" is not recognized as an internal or external command etc....
Pleae help me, do i need to do anything before hand?
kamiar said:
Hi,
I am on CM10 latest directly from GB official, i want to try your rom and downloaded the second file on your first post, but i cannot install it! when i click on flash.bat it does something and then says " coise" is not recognized as an internal or external command etc....
Pleae help me, do i need to do anything before hand?
Click to expand...
Click to collapse
Do not flash this over cm10!
It's not a Rom, it's a mod, as stated on topic. It should be used only on already flashed stock ICS.
Sent from my LG-P990 using xda app-developers app
louiscypherbr said:
Do not flash this over cm10!
It's not a Rom, it's a mod, as stated on topic. It should be used only on already flashed stock ICS.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Oh thanks for quick reply, can you guide me to a stock rom that has no or less audio bug please? and a little help to how flash it if it need any changed to partition etc...
kamiar said:
Hi,
I am on CM10 latest directly from GB official, i want to try your rom and downloaded the second file on your first post, but i cannot install it! when i click on flash.bat it does something and then says " coise" is not recognized as an internal or external command etc....
Pleae help me, do i need to do anything before hand?
Click to expand...
Click to collapse
First of all, this is NOT a ROM! This is the rooted system partition image for the clean leaked ICS Stock, which has a different partition layout from CM10. So, unless you already installed a stock V28E or V28G ROM and repartitioned your phone, it will not work for you.
Second, I would recommend always launching batch files from a command window instead of double-clicking them -- this way, you can always see all messages...
Oops... Didn't notice the previous reply, sorry!
wals46 said:
Of course, using nvflash backups you cannot open and look inside like it is with cwm backups, but maybe some dev will find the way to do it.
Click to expand...
Click to collapse
Actually, you can! I have no idea how to do this on win box, but on linux it's very simple (that's how I pushed root on this img).
All you have to do is mounting it with loop in an empty folder, than you can not only look into the system dir but also modify it, and when you unmount it, your img will be updated (maybe even before, don't know).
Supposing you have the system.img in the folder were you're, just run as root:
mkdir modsystem
mount -o loop system.img ./modsystem
Than you can go into modsystem with any file manager, and you'll see that this folder is the system folder. There you can modify what you would to, and after that (be careful with permissions, they will be there after flashing), just run:
umount modsystem
Than you can flash it by nvflash and see the magic happening! And welcome to the free penguin world.
Sent from my LG-P990 using xda app-developers app
kamiar said:
Oh thanks for quick reply, can you guide me to a stock rom that has no or less audio bug please? and a little help to how flash it if it need any changed to partition etc...
Click to expand...
Click to collapse
I'll tell the way I prefer, because in this way you flash Rom and baseband art the same time without losing any data.
-Download the v28g kdz image here. MD5SUM: a7d0e9763e4029484358f46936fe0099
-After downloading the kdz, flash it using instructions found here AND here. Note that on the instruction to edit the "C:\windows\system32\drivers\etc\host", its actually "hosts", with an S at the end. Also use the www,zip attached for the instructions on the post (not the shttp3.zip).
-following these instructions, you should be able to flash the kdz without losing any data, even with the baseband flashed.
-after that, start your phone as usual, then follow the instruction on the first post to get your newly stock v28g rooted.
If you can't find the related topics, just be patient and I'll update here with the links after I get time on my pc.
edit: links added
louiscypherbr said:
I'll tell the way I prefer, because in this way you flash Rom and baseband art the same time without losing any data.
-Search here in dev's for the Stephan's p990 leaker
-There, search for the v28g kdz image. I didn't test it, but I'd read that the link from lg is not working, so search for a mirror
-after downloading the kdz, flash it using instructions found on general section. It's not to much easy, but you can do it, just be patient.
-after that, start your phone as usual, then follow the instruction on the first post to get your newly stock v28g rooted.
If you can't find the related topics, just be patient and I'll update here with the links after I get time on my pc.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Thanks, i will wait for you to post the links, i never flashed kdz and need to learn! is it possible to go back to cm10 later on if i want to?
louiscypherbr said:
-after downloading the kdz, flash it using instructions found on general section. It's not to much easy, but you can do it, just be patient.
Click to expand...
Click to collapse
As a possible alternative to the described method, I can suggest using a KDZ Converter for P970. It will extract two files from a KDZ (the ROM itself and the baseband), which you can then flash with SmartFlash. Contrary to what you may read, this tool DOES work for P990, as long as you don't select patching option for CWM (just answer "n"). This process is easier than flashing a KDZ, but some people prefer direct KDZ flashing (I am not aware of any differences in the end result, so, being lazy, I just do it the easier way ).
Decided to go this way as well to see if it prevents the loss of sound in calls. The cmd command did however not work for me, got stuck on 'nvflash started'. Very strange, first time I encountered something like that.
Anyway, thanks to leclanpim for the repack! And thank u for providing the image :thumbup:
Will now restore my Titanium backups and get back to business.
louiscypherbr said:
Since some people asked me, I'm providing rooted system.img to be flashed by nvflash, an easy way to get v28g installed from kdz or smartflash rooted, for those who prefer to keep it as stockish as possible. The only mods I did from stock kdz backed up from my phone was to push su and superuser.apk.
This procedure did not wipe anything, so as a rule you shouldn't worry about backups, but I recommend you to use nvflash tool to make backups of all your partitions before trying this. Search here on dev's section to "nvflash toolkit", an excellent work from rmein, and use it to make backups.
Put the .img extracted from downloaded 7zip file on any functional nvflash folder, connect your phone in apx mode (without battery, BOTH vol up and down and plug it to usb), go to your nvflash folder and execute the following in cmd prompt.
nvflash.exe --bl fastboot.bin --download 23 rooted_system_v28g.img
Actually, I don't know if this command works on windows. Since I'm linux user (I'm sure that command syntax is useless to penguin's users), I didn't test this on win. So, if you used nvflash before on your win box and the previous didn't work, please let me know.
Download: http://db.tt/Qe6iLjpl
It's my personal dropbox folder. Please, feel free to mirror it and I'll update this OP, since I use my dropbox space to work.
Edit: leclanpim made an easy way to flash this system.img, putting a .bat file with nvflash.exe and the system itself in one zipped file, sharing it at https://docs.google.com/open?id=0Bw9sO0__Wuu-THkzcHpaeERmMHM
Thanks to him.
Click to expand...
Click to collapse
Dude, thanks a lot for your help. The trick for nvflashing the whole SystemImage work flawless under Windows7 X64 with the same set of commands as you write. Again, thanks.:good:
Louis, many thanks for your explainations.
If you can open system.img under linux and modify files as you already did rooting original 28G maybe, if you want to, you could do something more dangerous. Here it is.
download the latest CM10 nightly + JB Gapps,
merge gapps \system in CM10 \system,
replace the 28G system folder of your system.img with the created CM10+gapps \system folder and save a new CM10 system.img,
nvflash CM10 system.img
load battery and at last
with vol- and power you can do a hw factory reset and (maybe) you could boot new CM10 with locked bootloader, new partitions and without cwm recovery.
Do you think it could work?
LG Bugs?
Hi all,
I am currently on Stefan's deodexed V28g (with V28g BB & new unlocked bootloader)
I am having the following two little bugs (which I also had when I was on V28E odexed too)
1) Additional keyboard languages don't stay permanent. After reboot only english is checked.
2) Under Advanced Wifi settings"Keep Wi-Fi on during sleep" options: Whichever of these two options I select ("Only when plugged in" or "Never (increases data usage)") the wifi disconnects OK when it should, but after device stays locked for a long time,
it never reconnects (as it did in GB). It is showed on but disconnected. You have to switch it off & then back on.
Probably they are LG's bugs but I would appreciate if someone being on this one (stock-stock ICS), could confirm.
Thank you
spyrosk said:
Hi all,
I am currently on Stefan's deodexed V28g (with V28g BB & new unlocked bootloader)
I am having the following two little bugs (which I also had when I was on V28E odexed too)
1) Additional keyboard languages don't stay permanent. After reboot only english is checked.
2) Under Advanced Wifi settings"Keep Wi-Fi on during sleep" options: Whichever of these two options I select ("Only when plugged in" or "Never (increases data usage)") the wifi disconnects OK when it should, but after device stays locked for a long time,
it never reconnects (as it did in GB). It is showed on but disconnected. You have to switch it off & then back on.
Probably they are LG's bugs but I would appreciate if someone being on this one (stock-stock ICS), could confirm.
Thank you
Click to expand...
Click to collapse
I am on Stefan's 28g odexed and I can confirm both bugs.
Enviado desde mi LG-P990 usando Tapatalk 2
Hey guys,
strange thing happened to me yesterday.
After I got fed up with Paranoid, I decided to pick one of the other AOKP derivatives.
Although I had initial problems with mounting sdcard1, I somehow managed to flash from there
and do have SOKP with android 4.4.4 running on my honami
the thing is, when I want to access recovery through vol+ or vol-, my phone freezes on boot,
otherwise everything is working fine.
Unfortunately I need to flash GAPPS and I need to find some kind of workaround...
What I have tried is flashing TWRP and Z1DualRecovery via fastboot with no success.
Any ideas?
Thanks in advance
What is SOKP? Any link you can give us?
Did the kernel for that ROM include a recovery?
TWRP cannot be installed via fastboot on xperia devices. Z1dualrecovery kernel is for stock based roms only.
Maybe you should flash a FTF and start again.
you have unlocked bootloader, let flash pimp kernel to have working recovery, so you can reflash the rom to check it.
Sent from my C6903
gregbradley said:
What is SOKP? Any link you can give us?
Did the kernel for that ROM include a recovery?
TWRP cannot be installed via fastboot on xperia devices. Z1dualrecovery kernel is for stock based roms only.
Maybe you should flash a FTF and start again.
Click to expand...
Click to collapse
SOKP is Sonic Open Kang, a newer AOKP derivate.
It is one of the top posts in Android Development Forum.
Thought you heard of it.
Ok thanks will try it with pimped kernel. Hope it works with AOKP.
lauchrecords said:
SOKP is Sonic Open Kang, a newer AOKP derivate.
It is one of the top posts in Android Development Forum.
Thought you heard of it.
Ok thanks will try it with pimped kernel. Hope it works with AOKP.
Click to expand...
Click to collapse
I have seen it now, try flashing and wiping again
Hey, thanks for the fast response guys.
So I've just flashed Pimped Kernel to this ROM
http://forum.xda-developers.com/xperia-z1/development/xperia-z1-t2834169
I am still getting stuck on boot when I'm trying to get into recovery.
Neither vol+ not vol- works, I hit it when the purple light flashes and the orange one comes up and stays like forever.
So unfortunately I cannot flash nor wipe.
And Android without GAPPS kinda sucks... especially when they have the new material design...
EDIT: And I don't want to stay on pimped kernel cuz it somehow causes battery drain for me...
Only possibility would be to somehow install the zip via ADB/Fastboot... does that work somehow?
Just keep pressing it throughout the boot sequence, don't forget you have to press, let go, press, let go etc..... Its not just one long press
gregbradley said:
Just keep pressing it throughout the boot sequence, don't forget you have to press, let go, press, let go etc..... Its not just one long press
Click to expand...
Click to collapse
Just tried that out, in both directions.
Same result - no success.
Really unusual since it was always a long press and I should also be getting into the recovery
by rebooting into recovery from inside the ROM.
What other possibilities are there to get gapps on your phone?
lauchrecords said:
Just tried that out, in both directions.
Same result - no success.
Really unusual since it was always a long press and I should also be getting into the recovery
by rebooting into recovery from inside the ROM.
What other possibilities are there to get gapps on your phone?
Click to expand...
Click to collapse
push them with adb
but that's not the point
have you booted into system and check to see if quick boot is enabled in developer options - root
gregbradley said:
push them with adb
but that's not the point
have you booted into system and check to see if quick boot is enabled in developer options - root
Click to expand...
Click to collapse
I dont seem to have that option,
all I have is the point "Update CM Recovery when installing system updates"
@gregbradley how do I push and flash those via ADB?
Check in the gapps zip where each file should be installed (Proabably all to system/app) and the associated permissions (Should be 0755 or 0644, I don't have time to check just now)
Then put all the files in the same folder where you have adb installed.
then
Code:
adb push "[I]name of file here[/I]" system/app/"[I]name of file here[/I]"
adb chmod 0755 system/app/"[I]name of file here[/I]"
Replace the name of the file with the extension where I have said, change the "0755" to "0644" if that's what it says in the updater script, and if the apks should be installed somewhere else (for example syste/priv-app) change the commands to that.
This method would take you a long time, proabably best to just push the play store and then download the google apps you want, or better still, fix your recovery
Ok guys, many many thanks for your help.
I solved the problem and got my recovery back.
I flashed PhilZ and I like it. Way better than regular CWM.
You can close the thread now.