Help on retail 2.3.6 backup, root, unlock then to CM7.1 - Nexus One Q&A, Help & Troubleshooting

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.

Related

[RECOVERY] Easy Recovery for Optimus 2X (CWM & Stock)

ROM Manager now supports the O2X, use that instead!
---------------------------------------------------------------
This is a tool to easily switch recoveries on the Optimus 2X - this is simply a frontend for the .bat file that paul posted (same adb functionality), some people just prefer a GUI for these things and I had some time to kill. It includes the both the stock & clockworkmod recovery images and you get to choose which one to write to the phone.
Thanks to paul for both the clockworkmod & stock recovery images.
Notes:
- This will NOT work on the T-Mobile G2X - dont even try.
- You do not need a rooted device.
- If for some reason all hell breaks loose and the process fails or the program crashes, you can simply use pauls .bat file to overwrite the recovery image or try the program again.
Guide:
1. Make sure you have the LG mobile driver installed for your O2X (You need to be able to run adb commands).
2. Connect your phone to your computer and enable USB debugging (Settings->Applications->Development).
3. Open the program and follow the 3 steps.
Problems?
1. The program needs to create a folder to extract needed files, place the program in a folder with read & write access. (or run as administrator).
2. Your phone needs to be turned on.
Download:
REMOVED - Use ROM Manager instead.
While we are at it, would it be worth it to create a GUI to manage kernels and small tweaks?
Great job and... good idea!!!
nice and easy.
just the way i like it
thank you
Works flawlessly. THX!
nice
wow nice job,
you make it easy for everybody.
thanks allot.
a question, if I'm Rom Modaco ext4 or another, I click the stock and gives the mobile factory (stock ROM)?
What if I have more than one backup in CWM? And what exactly means Stock Recovery? Will it reset my phone to stock? without any CWM and stuff installed afterwards?
Slash75 said:
a question, if I'm Rom Modaco ext4 or another, I click the stock and gives the mobile factory (stock ROM)?
Click to expand...
Click to collapse
atm this program just lets you easily switch recovery images, so no it does not flash the stock rom.
Slash75 said:
a question, if I'm Rom Modaco ext4 or another, I click the stock and gives the mobile factory (stock ROM)?
Click to expand...
Click to collapse
As stated above, this tool only overwrites the recovery partition, it does not touch any other partitions - to get a stock ROM image you need to flash one using either nvflash or smartflash.
http://forum.xda-developers.com/showthread.php?p=12890619
Mehrsau said:
What if I have more than one backup in CWM? And what exactly means Stock Recovery? Will it reset my phone to stock? without any CWM and stuff installed afterwards?
Click to expand...
Click to collapse
This does not touch your sdcard or any of the backups made by ClockworkMod recovery. This is a tool to change between ClockworkMod recovery and the stock recovery provided by LG.
wonderfull! +1
this has completely ****ed my phone.. wont even boot now.
jangomango said:
this has completely ****ed my phone.. wont even boot now.
Click to expand...
Click to collapse
Same problem here. Had to flash with NVFlash again...
This should not do anything that will prevent your phone from booting :/
It does the same as the .bat provided by paul that installs CWM. (Overwrites the recovery partition).
This does not touch the system or boot partitions, only the recovery. I don't know if the phone stops booting with a broken recovery (should only prevent you from entering recovery).
Could you try pauls installer? Also, what firmware did you guys try it on? I have tried on the V10a and V10b from LG plus the MCR. (This will NOT work on the T-Mobile G2X).
EDIT: Since ROM Manager is supporting the O2X, you should use that instead.

"LOOK" Here First {List} Roms/Kernels/Mods/Themes/FAQ'S *Update 27/09/11*

This thread is here to make the lives of every one just that much easier. Will try to keep the first and reserved posts as up to date as humanly possible.
Please ask all questions in relation to issues you are having following the FAQ instructions to make it easier to answer your questions and easier for us to track the solutions that way the FAQ post is as up to date and accurate as possible.
As the GT10.1 landscape changes this thread will get updated. I will try and keep everything as simple and to the point as possible. Contributors will be much appreciated.
THE BASICS
BOOTLOADER MODE
Turn device off. Then hold down power + volume down button (the button closer to power button) until you see two icons appear then let go. Left icon (box) is recovery and right icon (Android robot) is Download. Use Vol. down to navigate then vol. up to select.
DOWNLOADING MODE
Just tap volume up when you have highlighted the android robot icon. You should see downloading appear under the icon.
RECOVERY MODE
Vol. up/down to navigate up or down and power button to select.
This is what you use to install ROMs/KERNELs and even themes for your specific roms when they become available. Just highlight the box icon and hit Vol. up. What we are doing now is replacing the stock recovery on your device with Clockwork Mod Recovery which allows you install unsigned ROMs/Kernels/Updates. When in recovery mode you can also back up whatever current ROM you have on your device so if you install a new ROM and something goes wrong you could always use recovery to restore. Whenever you install a new ROM it's advised to always wipe the device using cwmR to ensure a more stable install. Install new ROMS will also mean you will be losing all the apps on your device. It will look like you have a brand new device after the install unless its an update.zip for whatever rom you are currently on and the developer of that rom supports it.
Don't worry about losing your apps as you can always re-download them once you sync your device with your google account. However, the state of those apps and your settings will be lost, so I strongly suggest that you use an app like titanium back up and always make a back up of your apps before flashing any new ROMs. Check in the Recommended Apps section for a direct link to Titanium backup.
Here is the clockwork mod menu
- Reboot system now (self explanatory )
- Apply update from SDcard. (when you connect your device to your computer it will show up as tablet. The SDcard that cwm refers to is simply your device storage. Always make sure to copy install.zips to the root directory of your tablet storage.) You use this when applying an update for a specific ROM if that is what the ROM developer says.
- Wipe Data/ Factory Reset You should always do this before you install a new ROM or if you are having minor issues with your device.
- Wipe cache partition Think of this as the lite version of whats above . If you do above though it doesn't hurt to do this too.
- Install zip from SDcard Use this to install new ROMs.
- Back up and Restore
- Mounts and Storage use this to connect your device to your computer when in recovery mode. It is also possible to transfer files to your device while in this mode.
- Advanced What you are interested in here is something called dalvik cache, you want to wipe this too before installing any new ROM
- Power off
CLICK ME FOR ALL TERMINOLOGY DEFINITIONS
NVFLASH
Nvflash is a low level formatting and imaging tool. If you don't have a working recovery, or have broken the actual boot-loader on your tablet, this is the tool you will need to turn to. For those with unlocked bootloaders (and no fastboot capability), its the best way to root your device. Nvflash is pretty much NVida's version of say an ODIN program but done through cmd prompt. It can save a tablet if one is soft/semi-bricked or maybe full-bricked. To use nvFlash you must first put your tablet in APX mode (think of it as a way to allow you use commands on your computer to control your tablet).
Refer to this thread for downloads and instructions.
So off we go.
ROOTING YOUR TAB
GO TO SamsunFirmware.com AND DOWNLOAD A STOCK FIRMWARE FOR YOUR TAB VERSION> KEEP IN SAFE PLACE!!!!!!! You are already on the right page just scroll down.
Courtesy of RoboBear
GOOGLE I/O & RETAIL WIFI VERSION
[GTP7510]
DOWNLOADS compiled and hosted by tphillips
Content - GT-p7510_USB_Driver | hc-3.1_ota-full_sam_tab_10.1.zip(StockROM) | Odin3_v1.85 | recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 | stockretail.tar.md5(recovery) | Samsung_Galaxy_Tab_10.1_root
Download FilesForDummies.zip here
Mirror 1
Mirror 2
DONT WIPE during any part of this process. Make sure to put the stock rom from the download package on your device/use CWM and do a backup of your rom before you start anything in case something goes wrong. You have been warned!!!!!
1. Install samsung USB driver or download samsung Kies and install on your computer which will in turn install the drivers for you.
2. Run Odin.exe, choose PDA and point it to recovery.md5 file.
3. Connect tab via usb to your computer while in downloading mode then hit start in Odin on computer after connection has been established. Run, wait then reboot.
4. Connect tab to computer in usb storage mode (make sure usb debugging is off in tab settings) copy root exploit (Samsung_Galaxy_Tab_10.1_root.zip) to you tablet and take note of where it is. You can skip this part i fyou downloaded this file with your tablet.. Turn off tab. Reboot into bootloader again but this time go to recovery. Select to install zip from SDcard. navigate to where the root.zip is. Install the root.zip. Reboot into android. Your tablet is rooted.
5. Done.
You can also refer to this well made Video showing the whole procedure or this other awesome video by Dansan682.
RETAIL 3G
[GTP7500]
1. Download this Root.zip file to your tablet and move it to root directory of tablet storage. (you can also download on comp. then transfer to tablet)
2. Reboot tab and go into recovery mode and apply the root.zip you just downloaded.
3. Then reboot
rooted already
For CWM
1. After rooting download and install Rom Manager from market.
2. open Rom Manager app and have it install clockwork Mod to your device, you should see your device listed within Rom manager.
3. Done.
Courtesy of Robobear
RETAIL 4G
[GTP7500] courtesy of poitee
Downloads
Kernel.zip
Recovery.zip
1. Copy Files to root of device storage.
2. Boot into Bootloader mode and navigate to and enter recovery mode.
3. Apply Kernel.zip then recovery.zip
4. reboot.....Done.
UNROOTING & RESTORING STOCK RECOVERY
1. Using CWM Flash the stock rom for your device. This unroots your device and basically makes it like a brand new tablet.
2. Use Odin to flash the stock recovery from the filesfordummies.zip.
3. Done, your device is exactly how it was when you picked it up.
FLASHING ROMS AND KERNELS
This is pretty easy as long as you have CWM on your device.
Simply boot CWM recovery, navigate to either update/instal zip from SDcard (pls adhere to ROM/kernel install instructions) and flash the .zip file of the ROM or kernel.
I will update this section with links to all the existing and stable ROMs and kernels as the become available. I will advice that you hold off on the kernels if you can as every stable kernel will eventually get cooked into a ROM unless of course you want to help test them or be on the bleeding edge .
AVAILABLE ROMS & KERNELS
LEGEND
★ - WIFI
★ - 4G
★ - 3G
★ - Custom ROM
★ - Kernel
If your Device is supported the stars will tell you all you need to know.
★[ROM]Stock US Retail WiFi in case something goes wrong
[Solution] HC 3.1 OTA Stock ODIN
★[ROM]Stock|EU|Wifi|Retail|Touchwiz
★ [ROM][STOCK][ARABIC][AUG'13]W/ Official TOUCHWIZ
★★ [ROM][CWM] 3.1|WiFi|Touchwiz UX|DEODEXED
★★ [ROM][CWM] 3.1|WiFi|Touchwiz UX [UPDATE: New WiFi Base Rom]
★★ [ROM][CWM]3.1|WiFi|Bonsai ROM|ToucWiz option|
★★ [ROM][CWM]3.1| Blazar TW Rom|OC 1.6GH Kernel|Prerooted| by Poitee
★★ [ROM] [CWM]3.1|StarBurst ROM| by PhantomHacker
★★ [ROM][CWM][EUR][3G] BroodComb G-P7500 XWKG9 [ALPHA]
★★ [ROM]Task650's KME ROM UEKME Touchwhiz
★★ [KERNEL] 3.1|WiFi|OC 1.4GHZ| by Pershoot
★★[ROM] LiquidSpeed>>> New!!!
★★[KERNEL] 3.1|WiFi|OC1.6GHZ|Voltage Control|Voodoo Sound|CIFS-NTFS| by Poitee
[TABUNTU] Galaxy Tab 10.1 NATIVE Ubuntu WIFI now with a video
IRC ONLINE CHAT
Drop in HERE if you need some Help . #gtab
ROM/KERNEL/THEMES/UPDATES BETA TESTING!!!!
Ever wanted to get whats coming before anyone else (never mind the small issue of being a guinea pig ) Well here is your chance. In this section I will put up the contact info of any dev currently looking for testers and for a limited duration, once the devs has all their testers his link will be closed. You can also think of this section as a great way to see what is coming and what stage of development its in. So stop just downloading stuff people, now you can actually really contribute to making what gets released the best it can be and as bug free as possible.
FAQ
Be sure to ask whatever questions you have in relation to anything and any problems you come across. But please start every question you have with either a
(Q) basically letting me know its a question or a
(P) letting me know its a problem
I will put up all your questions or problems on here so everyone can see them and the answers or fixes . this way people won't have to filter through tons of pages to get help.
(Q) Should I follow these instructions for an IO edition tab? Or should I just use the fastboot flash [cwm recover] and flash the zips through that?
(A) This method will work on the IO version.
(Q) kernel 2.6.36.4 is a NO-GO for the 3G version?
(A) Yes, it doesn't work on the 3G version yet.
(Q) If my tab ins locked does that mean i cant flash kernels on it?
(A) You can flash anything as long as you have a recovery that will support it. In our case CWM. Being locked and unlocked really only stops you from flashing stuff "easily" but since we can change the recovery, we can flash anything.
(Q) Does the Odin file wipe tab?
(A) No. All Odin is doing here is flashing a new recovery to your tab. Nothing more.
(P) Can't see tablet as USB storage device on Mac.
(A) Unfortunately Android and Macs don't play nice... you best bet is to use dropbox or a simple bluetooth transfer to transfer files from your mac to your tablet. Then on your Tab use a file manager app to move your files to where you want them to be. For now. Another option is to download everything that requires you using CWM with your tablet so its all already there. So in CWM all you have to do is navigate to your downloads folder. I just created a folder called mods and I have them all there.
(P) Stuck in BootLoop after Flashing ROM via Odin.
(A) You should use nvFlash to falsh CWM if you don't still have it then do a full wipe of your device including reformating all partions in mounts and storage except the boot partition then using Odin install a stock Rom on your device.
(P) I messed things up on my LTE tab and I now somehow dont have a recovery mode anymore!!!!!
(A) Go Here and scroll to post #4 and follow tijayz instructions.... make sure to thank him!!!
USER TIPS AND RECOMMENDED APPS
TIPS
1. Working Hulu
2. How to utilize the entire screen for setting widgets and icons without the 1inch gap on the sides? Use ADW launcher EX
3. Rotation Lag Fix
4. Look here for a Mod to permanently set your browser user agnet to desktop. No more mobile sites.
RECOMMENDED APPS!!!!!go on!!, find an awesome app and suggest it to be added to this list!!! Only android market or direct .apk links so isers can download and install straight from their devices
Titanium BackUp
Circle Launcher
ADW Launcher EX
Beautiful Widgets
CNN
Minimalistic Text
Thumb Keyboard
Tablet Keyboard
XBMC
PLEX
Playstation Emulator
SNES emulator
Multipicture Live wallpaper. Kiss weirdly cropped wallpapers goodbye
Wallpaper Slideshow
Dolphin Browser HD
Pulse news Reader
AutoDesk SketchBook Pro
Feedly
File Manager HD (honeycomb)
All credit goes to all the awesome devs and members of xda. I have done nothing but make this thread.
DEV CENTRE
This section will have a host of developer specific tools and even tutorials. XDA making it easier for XDA??????
Good Times....
To start things off
APK Manager: Honeycomb Edition by tphillips
Thanks so much. But the download link doesnt work. Would appreciate it if you could get it working! Looking forward to flashing roms!
EDIT:Nevermind-its working
rvrugg90 said:
Thanks so much. But the download link doesnt work. Would appreciate it if you could get it working! Looking forward to flashing roms!
EDIT:Nevermind-its working
Click to expand...
Click to collapse
Sorry, try again... its working on my end though.
Nice, should be stickied.
(Q) Should I follow these instructions for an IO edition tab? Or should I just use the fastboot flash [cwm recover] and flash the zips through that?
The so-called "Mount device as USB Mass storage" thread has nothing to do with mounting the device as Mass Storage. It only tells you how to mount as MTP, which can be done without any of the steps mentioned in the thread. Seriously, it doesn't belong on this list.
Also, you should include instructions for using nvflash to install a custom recovery. I found it much easier and safer to root through this method than through Odin.
[Q] kernel 2.6.36.4
Many thanks for preparing this post.
Just wanted to add a question here: can you confirm that kernel 2.6.36.4 is a NO-GO for the 3G version?
Or is it related with TW versus plain HC?
I'm running the stock TW rom on a rooted 3G tab. Tried to flash the above kernel with OC purposes, had to recover through a CWM backup.
Thanks for clarifying
ca110475 said:
Many thanks for preparing this post.
Just wanted to add a question here: can you confirm that kernel 2.6.36.4 is a NO-GO for the 3G version?
Or is it related with TW versus plain HC?
I'm running the stock TW rom on a rooted 3G tab. Tried to flash the above kernel with OC purposes, had to recover through a CWM backup.
Thanks for clarifying
Click to expand...
Click to collapse
the oc kernel is not supporting tw at this current time.
I'm just going to copy exactly waht I typed in the IRC -- I'm stuck without being able to reboot into recovery with an I/O tab. Also cannot get fastboot to work
- i got some help from here earlier but now i'm stuck again in rooting/flashing a custom rom on the IO edition
<slobdogg> i went through the ODIN process to revert to 3.0.1, then was able to adb reboot recovery and install the root file
<slobdogg> afterwards i installed clockwork mod using RM, and then did the update to a 3.1 OTA file on XDA
<slobdogg> now i'm supposed to reboot into recovery to reinstall root but i cannot
<slobdogg> even in ADB if i reboot recovery it just restarts the device...also, I cannot enter recovery through the Vol Down + Power method, just fastboot and odin
<slobdogg> so im right back where I was (3.1 with no root)
ralexand said:
I'm just going to copy exactly waht I typed in the IRC -- I'm stuck without being able to reboot into recovery with an I/O tab. Also cannot get fastboot to work
- i got some help from here earlier but now i'm stuck again in rooting/flashing a custom rom on the IO edition
<slobdogg> i went through the ODIN process to revert to 3.0.1, then was able to adb reboot recovery and install the root file
<slobdogg> afterwards i installed clockwork mod using RM, and then did the update to a 3.1 OTA file on XDA
<slobdogg> now i'm supposed to reboot into recovery to reinstall root but i cannot
<slobdogg> even in ADB if i reboot recovery it just restarts the device...also, I cannot enter recovery through the Vol Down + Power method, just fastboot and odin
<slobdogg> so im right back where I was (3.1 with no root)
Click to expand...
Click to collapse
in order to do adb reboot recovery you need a rooted boot.
flash the latest tools pack, and you will get root/adb root shell/busybox,dropbear,ssh,etc.,etc.
you need to get CWM or the stock IO recovery on the device, prior to being able to flash.
pershoot said:
in order to do adb reboot recovery you need a rooted boot.
flash the latest tools pack, and you will get root/adb root shell/busybox,dropbear,ssh,etc.,etc.
you need to get CWM or the stock IO recovery on the device, prior to being able to flash.
Click to expand...
Click to collapse
What tools pack are you referring to? Can't seem to find something relating to that on the forum.
I feel like an idiot because it just seems like if i restart the process, I'll lose CWM again and be back where I am right now. If I could just get fastboot to work this whole thing would be a lot easier because I could just flash CWM without root.
ralexand said:
What tools pack are you referring to? Can't seem to find something relating to that on the forum.
I feel like an idiot because it just seems like if i restart the process, I'll lose CWM again and be back where I am right now. If I could just get fastboot to work this whole thing would be a lot easier because I could just flash CWM without root.
Click to expand...
Click to collapse
http://droidbasement.com/db-blog
XDA:
[Tools] – SU/BusyBox/Misc – Galaxy Tab 10.1 (Update: 6/18/11)
this sends you to droidbasement.
pershoot said:
in order to do adb reboot recovery you need a rooted boot.
flash the latest tools pack, and you will get root/adb root shell/busybox,dropbear,ssh,etc.,etc.
you need to get CWM or the stock IO recovery on the device, prior to being able to flash.
Click to expand...
Click to collapse
As with most issues, mine turned out to be user error. I forgot to re-flash the root.zip file after flashing the 3.1 update. That prevented me from being ablet o reboot into CWM.
Started from step 1, and flashed the root file after the 3.1 update and now i'm fine.
Thanks!
ralexand said:
(Q) Should I follow these instructions for an IO edition tab? Or should I just use the fastboot flash [cwm recover] and flash the zips through that?
Click to expand...
Click to collapse
This is only really known for certain to work on a retail locked or unlocked version. Not certain about the google i/o version but will ask around for you. But nothing here says that version is supported using this method.
However, i see no reason why it won't work though, assuming you only flash the root exploit.
For instructions specific to your model though, refer to this thread
Berner said:
The so-called "Mount device as USB Mass storage" thread has nothing to do with mounting the device as Mass Storage. It only tells you how to mount as MTP, which can be done without any of the steps mentioned in the thread. Seriously, it doesn't belong on this list.
Also, you should include instructions for using nvflash to install a custom recovery. I found it much easier and safer to root through this method than through Odin.
Click to expand...
Click to collapse
Thanks, removed the usb thingy, however, it would be nice if you also contributed a link to the nvflash method so i could update the thread. its not my thread you know? it belongs to all of us. How good this thread ends up being all boils down to how helpful we all are.
ralexand said:
As with most issues, mine turned out to be user error. I forgot to re-flash the root.zip file after flashing the 3.1 update. That prevented me from being ablet o reboot into CWM.
Started from step 1, and flashed the root file after the 3.1 update and now i'm fine.
Thanks!
Click to expand...
Click to collapse
Glad to see you are sorted
Please everyone... carefully follow the instructions!!!
On another note, does this mean that this process works on a google i/o device already on android 3.1? Please let me know so i can update
however, it would be nice if you also contributed a link to the nvflash method so i could update the thread. its not my thread you know? it belongs to all of us. How good this thread ends up being all boils down to how helpful we all are.
Click to expand...
Click to collapse
Posts 1 & 2 of them most viewed thread in this forum. http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2
Berner said:
Posts 1 & 2 of them most viewed thread in this forum. http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2
Click to expand...
Click to collapse
Well, i put it up and took it out again, there is currently a much, much, much easier and direct method to root the device. And one that I am sure you will agree is by far more straight forward.
Lorddeff07 said:
This is only really known for certain to work on a retail locked or unlocked version. Not certain about the google i/o version but will ask around for you. But nothing here says that version is supported using this method.
However, i see no reason why it won't work though, assuming you only flash the root exploit.
For instructions specific to your model though, refer to this thread
Click to expand...
Click to collapse
I'm not sure if it's just my version of the I/O Tab, or all I/O Tabs, but one key thing is that I could NOT boot into recovery on a non-rooted 3.1 Edition.
On 3.1, adb reboot recovery would simply reboot my device. I cannot use the POW + VOL DOWN button combination because I am presented with a USB icon on the left (which takes you to fastboot - which would not work for me), and the ODIN Download Icon on the right.
So, the only changes to the instructions with regards to an IO tab is to remove any reference to "POWER + VOL DOWN" as the method of getting into recovery. IT MUST be done via a command -- either adb reboot recovery or using Rom Manager to boot into CWM.
Exact steps for me (brief):
1. ODIN to revert to 3.0.1
2. reboot the device, turn on USB Debugging
3. connect to computer and use ADB to "adb reboot recovery" then install root zip file once you get into the stock recovery
4. Reboot - install Rom Manager and Clockwork Mod.
5. Reboot into CWM
6. Install the 3.1 Update AND [before rebooting] re-install the root zip file
7. Voila!
Only thing is -- now that I am on 3.1, the only way for me to get into recovery is via Rom Manager because the 'adb reboot recovery' function only reboots the devices, and the button combination trick still does not work.
EDIT: paragraph above is not entirely true -- i can open a terminal on my Tab and type 'reboot recovery' to get back into recovery. So, it's just adb & the button combination that does not work.
I still cannot figure out why I cannot get fastboot to work. My computer even seems to recognize that I have a fastboot device connected, but I cannot send any fastboot commands; even fastboot devices returns nothing.

[DEV] ClockworkMod 5.5.0.4 [UPDATED: Can't get to CWM? Here's the fix!]

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

[mod][stock ics] Rooted v28g system.img

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

[Q] Rooting Rage

Trying to root z1 c903 but nothing works
T:ried
http://rootmyandroid.org/root-sony-xperia-z1-click-root-2-minutes-process.html
It copied the files over but I coudn't get into recovery. des[ite the face t my phone serial doesnt appear in adb devices.
{*}Using flash tools to flash the C690X files but it couldn't even find them, I re installed it and tried to open it again but it wants the content of C:\Flashtool\firmwares copied to C:\Users\Justin\.flashTool\firmwares which I did but it keep telling me to copy the files and wouldn't close till I force closed it.
Kingo Root
Root Genius
Both almost worked to 99% but then said failed
I have tried all the solutions to fix ADB but doesn't seem to work.
I also used Sony's OEM unlock which said it worked too.
USB debugging mode is on.
The drivers are installed, device manager shows: Android ADB Interface under Android phone.
Any ideas?
@bustinjussell Try another pc...
---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------
Also try this
http://forum.xda-developers.com/showthread.php?t=2933298
Update
//delete this post
Not sure how to delete this post
Update
The .zip.exe wants to use another program that installs crapwware and requests my my mobile number
Click to expand...
Click to collapse
I found the file on [URL="https://www.androidfilehost.com/[/URL] which doesnt have any crapware
Everything works now but I can't access recovery menu, if i try ROM toolbox it just reboots the phone.
Should there be a default recovery menu?
bustinjussell said:
I found the file on [URL="https://www.androidfilehost.com/[/URL] which doesnt have any crapware
Everything works now but I can't access recovery menu, if i try ROM toolbox it just reboots the phone.
Should there be a default recovery menu?
Click to expand...
Click to collapse
Use Nut's dual recovery it installs an app called ndr utilities there you can set primary recovery or default recovery...
[facepalm]
I installed the wrong ROM and had to reflash ftf file with full file (kernel, system etc.] the only one I could find is jellybean, (C6903_14.1.G.2.257_CE) installing the newer [C690X_14.4.A.0.157_KernelOnly.ftf] just gets stuck in a boot loop. I put back the working jellybean but am downloading the full ftf, about 900mb, so hopefully I will be back to normal soon. I wouldn't mind JB but it won't connect to my network.
bustinjussell said:
I installed the wrong ROM and had to reflash ftf file with full file (kernel, system etc.] the only one I could find is jellybean, (C6903_14.1.G.2.257_CE) installing the newer [C690X_14.4.A.0.157_KernelOnly.ftf] just gets stuck in a boot loop. I put back the working jellybean but am downloading the full ftf, about 900mb, so hopefully I will be back to normal soon. I wouldn't mind JB but it won't connect to my network.
Click to expand...
Click to collapse
C690X_14.4.A.0.157_KernelOnly.ftf means it's the kernel only. You're installing a 4.4.4 kernel on your JB system, of course it won't work...
Install the full 157 TFT, you can get it from here: http://forum.xda-developers.com/xperia-z1/general/ftf-c6903-14-4-0-157-central-europe-1-t3018526
Make sure it boots and runs. Then follow the rooting procedure described here: http://forum.xda-developers.com/xperia-z1/general/root-14-4-0-157-lb-ubl-t2933298
Steve_max said:
C690X_14.4.A.0.157_KernelOnly.ftf means it's the kernel only. You're installing a 4.4.4 kernel on your JB system, of course it won't work...
Install the full 157 TFT, you can get it from here: http://forum.xda-developers.com/xperia-z1/general/ftf-c6903-14-4-0-157-central-europe-1-t3018526
Make sure it boots and runs. Then follow the rooting procedure described here: http://forum.xda-developers.com/xperia-z1/general/root-14-4-0-157-lb-ubl-t2933298
Click to expand...
Click to collapse
I have rooted and when I restored too KK I am on build number 14.3.A.0.757, there is an update for 14.4.A.0.108 which downloaded but says 'could not verify'

Categories

Resources