Bricked-kernel to cm9 alpha 2.. tri boot? - TouchPad General

I went from bricked kernel(I forget which version) to cm9 alpha 2 and it put two versions of android on my tablet.
At moboot it gives me webos,cyanogenmod,and bricked-kernel...
How do I get rid of the bricked-kernel rom and have it boot into cm9 alpha 2 instead?

got into WEBOS...usinf preware to download Internalz pro....then in setting go into master mode...and in /boot folder, delete uimage for Bricked kernal...

What is preware?
Does it internalz cost money?
I've booted into webOS like once so I am not familiar with any of this stuff.

Ignore that post. Not only is that possible in android, but that would just permanently break your Wi-Fi until you do it the proper way, by following the instructions in the OP of the bricked kernel thread.

This thread details how to get rid of the extra boot option: http://forum.xda-developers.com/showthread.php?t=1511747
I actually just did this. I used to use File Expert (free version) but they started requiring an upgrade for the root permissions, and every other root-explorer app would cause crashes & restarts. If they work for you, go ahead and use that, following the steps from the link above. I couldn't figure out why, so what I did to fix this was:
Download & Install Remount from the market https://market.android.com/details?id=com.stericson.remount
Then, run that, and choose to remount /boot as r,w
Once that was done, I used Terminal Emulator to go to /boot, change to su (to get root), and edited moboot.default (vi moboot.default), changing the contents of this file to "CyanogenMod" (it was set to the old bricked kernel entry). This will set the default to boot into CM. You can stop here if that's all you want.
I finally just went ahead and deleted /boot/uImage.CM_Bricked_Kernel as well since I wasn't going to use this anymore and it was messed up anyway.

Related

[GUIDE] ROOT | xRecovery | TIPS&TWEAKS to install custom Rom`s

IMPORTANT NOTE: Because people do not have respect for the work of other people or to the point of thanking all the links to the alternatives are "down" until further notice. Over 200 downloads and not a thank you?!
Thanks.
After receiving several PM `s trying to get my help in the installation of Froyo ROM` s i decided to create this little "How to" for the avoidance of doubt.
This is a guide based on the Windows XP System.
This guide is ONLY for Xperia X10.
This guide was based on information gathered and based on my own experience and presents, in my opinion, the best way to get what you want. Whenever possible I will present alternatives.
This guide has a starting point of the original ROM SE (no root) if you already have root access please go to step 2.
---------------------------------------
---------------------------------------
What you`ll need before proceeding:
- Download SDK from google (need help for this? go HERE)
- Make sure you`ve just one partition on your sdcard and on FAT32. More info HERE
- Before each and every step make sure you have USB Debugging checked (settings>applications>Development)
---------------------------------------
---------------------------------------
I WILL NOT BE RESPONSIBLE IF ANYTHING GOES WRONG​
1. Getting Root Access
1st mode
- Download file rootme.tar.bz2 HERE and follow the instructions or use as an alternative SuperOneClickv1.5.5-ShortFuse;
- Reboot.
2nd mode
You can alternatively use THIS pre-rooted and with xRecovery allready instaled rom. Saying this, if you choose to install this rom can proceed to step 3
Use THIS tool if you have any trouble with Bin4ry one.
Bin4ry realease a new tool you can try it HERE.
2. Installing xRecovery
1st mode
- Download xRecovery HERE and do the installation by following the instructions.
2nd mode
For the case of having problems installing the xRecovery do the following:
- Download THIS version of xRecovery;
- unzip it and copy the content (3 files) to the root of your sdcard;
- Open cmd prompt (start>run and type cmd) - From now on i will call this adb shell. I also recomend that you create a shortcut to this on your desktop, since you will use this many times;
- Now go to tools folder where you install your SDK. In my case (C:\Program Files\Android\android-sdk-windows\tools>);
Now type:
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/busybox of=/system/bin/busybox
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/xrecovery.tar of=/system/bin/xrecovery.tar
reboot
Check your screen and give permition
- Reboot
- Press several times after "sonyericsson" appear on back button to confirm if xRecovery it`s installed. If it`s corrected installed you wil see your screen as the images bellow.
Although this guide is described for the installation of zhizu rom`s the process is exactly identical to the TripNRaVeRs and jerpelea rom`s
3. Installing Rom`s
This guide is for every rom that supports xRecovery process. I will not answer questions from other method.
- Choose the rom you want.
ZHIZU / TripNRaVers v2.1 / TripNRaVers vMIUI / jerpelea
3.1.
zhizu rom:
- Download-FreeX10 beta1.zip;
- Download gapps_latest_FreeX10.zip;
- Download FreeX10-beta1-hotfix4a.zip (at this point this is the last version, if a newer version exist please download that one. The process is identical);
- Create a folder at the root of the sdcard named ROMS;
- Create a folder inside ROMS called zhizu, TripNRaVers or jerpelea (dependind witch rom you`ll use);
- Copy the downloaded files to that folder;
- Reboot;
- Enter on xRecovery and:
3.1.1.
- Install custom zip;
- Choose custom zip from sdcard;
- ROMS (folder you created earlier);
- zhizu;
- Run the FreeX10-beta1.zip;
- Run the FreeX10-beta1-hotfix4a.zip;
- Reboot;
---------------------------------------
---------------------------------------
NOTES:
After that, probably you won`t have network and screen is crazy... do this:
Open adb shel again and type:
HTML:
adb shell
killall servicemanager
Your phone will reboot.
HAVE REAL ISSUES REGARDING "killall: not found"? type this instead (thks to NeoInc):
HTML:
adb shell
busybox killall servicemanager
If you`ve installed the TripNRaVers rom and if you have issues with wireless run this command on adb shell (thks to rodak ):
HTML:
adb shell
setprop net.dns1 192.168.1.1
If you having problems with su permission type (thks to AzureNightwalker ):
HTML:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
chmod 4755 /system/bin/su
---------------------------------------
---------------------------------------
(back on topic)
- After reboot enter on xRecovery again and go where you put your files again but this time you will run the gapps_latest_FreeX10.zip
- DONNE
If after instaling gapps_latest_FreeX10.zip you still don`t have google apps, please install THIS and then gapps_latest_FreeX10.zip
4.
If you want to install new market, please do this:
- Enter AT LEAST once in the old one;
- Copy THIS to the folder you`ve created earlier and run it from xRecovery.
---------------------------------------
---------------------------------------
CREDITS:
None of this would have been possible without the incredible work of our devs.
All the credit should be directed to them. Not for me. Just tried with this guide to help young (or not) to get phones rooted, install xRecovery and for installation of these incredible ROM `s.
Thanks to (in alphabetical order): (sorry if i forgot someone)
Bin4ry;
CLShortFuse;
jerpelea;
MarylandCookie;
rodak
th4r;
TripNRaVeRs;
XperiaX10iUser;
ZHIZU;
and all XDA users
|tips & tweaks|
some commands that you may require at some point
Copy to/from sdcard
HTML:
adb push /mnt/sdcard/<filename> - to copy the file to SD
adb pull /mnt/sdcard/<filename> - to copy the file from SD
Fix Facebook Sync (at the present TripNRaVeRs Rom may need it)
Please make back up first
Install to your Android using push command
HTML:
adb push ContactsProvider.apk /system/app/ContactsProvider.apk
adb reboot
Download ContactsProvider from HERE (thks XperiaX10iUser )
This will fix the Facebook sync, you might need to remove and add the Facebook account again.
If you loose root access for some reason, please open ADB shell and issue this command:
HTML:
chmod 4755 /system/bin/su
--------------------------------------------
--------------------------------------------
some tips & tweaks to play with
Let`s play with build.prop shall we?
CAUTION WITH THIS!!! ALL CHANGES MUST BE DONNE AT THE END OF THE DOCUMENT!!!
What will you get with this...
Well. In my opinion and only that, i think this way i can preform a much stable version of 2.2 Froyo released by zhizu.
After all apps installed (more or less 35) i get a very stable and fast rom (more or less 1500 on quadrant) and rarely had a FC.
So...like i said...that`s my 2cents.
1st mode - root explorer
You can make changes directly through RE by going on \system and then:
- Press and hold on build.prop file;
- Check all Permitions on the drop down menu;
- Press and hold on build.prop file (again);
- Choose open in text editor;
- After changes were made save and exit;
- Reboot.
2nd mode - Through Text Editor
To edit this one you must do this on a UNIX system base. You can use THIS to do that.
- Copy your build.prop to your sdcard and then to your pc;
- Open build.prop through NOTEPAD++;
- Now check all permitions for build.prop in \system folder
- After you made the changes proceed in reverse way and check all permitions again;
- Reboot.
This is your build.prop of your phone. Here we can do some tweaks in it.
Look carefully some already exist somo you have to add.
ro.sf.lcd_density=XXX (here you can put any value between 180/240) - This will affect the way you see your screen;
wifi.supplicant_scan_interval=XXX - This is how often your phone search for wi-fi spots and obviously will afect your battery life. Choose whatever you want in seconds. For instance, i have 360. Witch means my phone will search for wi-fi every 360 seconds.
dalvik.vm.heapsize=XXX (here you can put any value between 12/40) - This is how Android lead with apps. Lower value faster phone but big apps will crash. Higher value slower phone on small apps but faster on big ones). I have this to 40.
windowsmgr.max_events_per_sec=XXX (here you can put any value between 30/300) - This affect screen responseness of screen. You may try this if you have any problems with lag. I have this to 200.
mot.proximity.delay=XXX (here you can put any value between 0/300) - This will affect the time your screen goes off when receive a call. I have this to 150.
--------------------------------------------
--------------------------------------------
| Rom`s | Themes |
THIS ONLY WORK AFTER RIGHT INSTALATION OF THE ABOVE ROM´s
What is the joke of having rooted phone if we do not install anything to envy to our friends. Right?!
SEMPITERNAL THEME
XperiaX10iUser
wesvista
Whats wrong with my guide?
http://forum.xda-developers.com/showthread.php?t=908791
rodak said:
Whats wrong with my guide?
http://forum.xda-developers.com/showthread.php?t=908791
Click to expand...
Click to collapse
nothings wrong with it. if you read it goes further. root/xrecovery/rom`s and since so many people has sent me pm`s to explain them...
don`t get offensive
rendeiro2005 said:
nothings wrong with it. if you read it goes further. root/xrecovery/rom`s and since so many people has sent me pm`s to explain them...
don`t get offensive
Click to expand...
Click to collapse
From my guide:
"Feel free to help me improve this guide, just post here and I will update this post with all good tips!"
But hey, let´s have a lot of guides spread all around this forum just to get some credit
Hmm. Sorry. Got a question here.
Step 1 and 1a, is it the same? Or i need to do step 1 and then do step 1a?
And partition on my sdcard is already on Fat32, do I need to reformat it again to Fat32?
wanmeow said:
Hmm. Sorry. Got a question here.
Step 1 and 1a, is it the same? Or i need to do step 1 and then do step 1a?
And partition on my sdcard is already on Fat32, do I need to reformat it again to Fat32?
Click to expand...
Click to collapse
Hi,
1st. Like i said "alternatively". 1 is one way and 1a is another way. The diference between the two is the fisrt one you have to root after install and the second one came pre-rooted.
2nd. Since you`ve sdcard on FAT32 don`t have to do it again. Just be sure there`s ONLY ONE partition.
Hope it helps
Oh. sorry. I miss the "alternatively".
Which one is the best? 1 or 1a?
wanmeow said:
Oh. sorry. I miss the "alternatively".
Which one is the best? 1 or 1a?
Click to expand...
Click to collapse
depends on what you want. root or not rooted.
for the installation of above Rom `s you need to have root access.
Oh, ok. Thank you. I go download the files and try it first.
wanmeow said:
Oh, ok. Thank you. I go download the files and try it first.
Click to expand...
Click to collapse
you`re wellcome
tell me how it goes
nice guide.
tnx
Tehouster said:
nice guide.
tnx
Click to expand...
Click to collapse
wellcome
no need to thk me just click thks
Im stuck at SE white logo. If im not pressing back button, it will boot normally. Im thinking like giving up. >.<
wanmeow said:
Im stuck at SE white logo. If im not pressing back button, it will boot normally. Im thinking like giving up. >.<
Click to expand...
Click to collapse
Wicth process you follow?
From stock ir zhizu rom?
If you start from stock witch process you usr to install xrecovery?
As you know i've two possibilities on eatch one if you dont tell all things youve donne i cant help you
sent from my ****up X10 running amazing zhizu rom

[ROM] B&N 1.4.1 upgrade through CWM [Dual Boot/Single Boot Compatible]

I had downloaded a version of this file from a post embedded deep inside one of the threads over here (sorry can't find it right now), but upon examination of its contents, I discovered some issues:
1. The checksums on the files in contained in the the original zip file showed that B&N had at least two versions of 1.3.0 update you can download from them, and the zip I got contained an older version so I put in the latest files in there.
2. There were unnecessary files included inside the original zip file, I deleted those, and only included what was needed.
3. There were errors in the script syntax, which I corrected, so that the proper commands are run during the update, and the proper sed substitutions are made during the editing of the unpacked init.rc inside the ramdisk.
What this zip will do is replace any older version of a B&N ROM on the alternate eMMC partitions of a dual booting configurations to the latest versions. This will prevent B&N from pushing the 1.3.0 update to you OTA, and messing up your dual boot setup. Just put the zip on your sdcard, boot into CWM recovery, and apply the zip. I apologize in advance for not giving credit to the original creators of the scripts here.
Note: There have been two different protocols for a dual booting u-boot.bin, with an older one relying on the files u-boot.altimg, and u-boot.altram to specify the names of the secondary boot ramdisk and kernel, and a newer one assuming that they are named uAltRam, and uAltImg respectively. This update conforms to the new u-boot.bin protocol. If you are still using the old one, you will have to get root access to /boot and edit the two files to point to uAltRam and uAltImg.
So if you want try it out, here it is:
http://www.mediafire.com/?gcrpzzc0kdoxcjx
MD5 Sum: 51e24c1e5eff11ba5ea481a63f7404eb
Update
I have now uploaded files for B&N Update 1.4.1.
The first file (MD5 Sum: 4ff1d9764663278c3f51e2e2c9d841a6) is meant to update a pre 1.4.1 Stock B&N ROM on secondary /system through CWM:
https://rapidshare.com/files/52135913/secondary_update_NC_stock_1_4_1.zip
The second file (MD5 Sum: c1506816fbfb8c419fbbc4afe1b12887) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM without messing with recovery;
https://rapidshare.com/files/869435270/primary_update_NC_stock_1_4_1_keep_CWM.zip
The third file (MD5 Sum: ab1307c55a2c35c91d339c8037ce9a78) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM, replacing recovery and all:
https://rapidshare.com/files/2059644016/primary_update_NC_stock_1_4_1.zip
None of these files will wipe user apps and data, so if you wish to do that, boot into recovery and wipe from there. [This will work on primary /data partition only]
Please note: If the B&N Stock ROM is rooted, you will lose root upon updating.
Thanks!
This worked beautifully! I flashed it from my sdcard after booting into CWM on my primary partition on emmc.
I'm betting you got the original from jasoraso in this dual boot thread: http://forum.xda-developers.com/showpost.php?p=17122342&postcount=142
What I would love is a straight CWM-flashable 1.3 ROM, to include in my up-to-date (for now) guide for setting up the dual boot, rather than having to set up and move 1.2, then update to 1.3.
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
Click to expand...
Click to collapse
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
rajendra82 said:
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Click to expand...
Click to collapse
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Taosaur said:
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
Click to expand...
Click to collapse
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Taosaur said:
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Click to expand...
Click to collapse
No way to get around having to register the primary partition image first. Once that is done it could be moved to secondary and then updated straight to 1.3 instead of going 1.2 first.
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
yelloguy said:
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
Click to expand...
Click to collapse
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
rajendra82 said:
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Click to expand...
Click to collapse
I wouldn't know what to change and what to leave alone, myself, but I think you're making this more complicated than it needs to be. I'm talking about installing 1.3 using CWM, regardless of how the device is partitioned or what was on the primary partition previously. Like the files in this thread, but 1.3: http://forum.xda-developers.com/showthread.php?t=1050520.
I understand that you were just cleaning up jaso's update-dualboot-to-1.3 file. I used the original and it worked fine, but it would have saved me a couple steps (and would be more useful in a guide for setting up dualboot) to simply install 1.3 rather than 1.2 to the primary partition when setting up. The reason I started with 1.2 is because it is the most current stock ROM available for CWM. What I would like is to avoid a historical re-enactment of stock OS development altogether. A general-purpose, CWM-flashable 1.3 ROM would be broadly useful, but is so far lacking as far as I've seen.
1. Do you envision this to be an uprooted stock 1.3 update ROM (either as primary or the only boot option) ? I just don't see the need for this to be CWM flashable. It is very easy to get there by resetting the device to stock, and then updating the device to 1.3.0 using the B&N file, and restoring dual boot as need be. If one has any older stock ROM running on primary, the B&N update will get them to 1.3 while losing root. There is no need to apply 1.2 update first.
2. Do you envision this to be for already rooted single or primary booting 1.1/1.2 users? There is once again no need to create any file for this. One can simply apply the B&N update, and then rerun manual nooter, and restore dual booting to the secondary.
3. The only users with no clear upgrade path are those who have already moved the B&N ROM to secondary. That's why I fixed up the zip file, and shared it. I am glad the original file worked for you despite the script errors. I can see other setups where it would have failed though.
I am not trying to make this more complicated than it needs to be. The Nook Color is just capable of being set up in so many ways, there isn't simply going to be a single update method that will work in all scenarios.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Taosaur said:
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Click to expand...
Click to collapse
Then the best bet is two step process:
1. Wipe device and restore to factory stock.
2. Download B&N 1.3 update file from website and place it on the root of SD card. Let the device recognize it, and apply it.
Once the 1.3 update gets applied, you are free to reroot, install CWM, set up dual booting, or whatever the next step may be.
It is the only method that will work in all circumstance as it involves starting from scratch regardless of setup. If want to preserve any of your current setup, no one step file will work for all circumstances. Some people have the stock firmware rooted, others do not. Some have the stock as the only internal boot, others have it as primary option of a dual booting configuration, while others have it as a secondary option. Some have stock recovery and run CWM off the sdcard when needed and want to update their recovery to the latest stock version, others want to keep the CWM recovery, and not update the recovery. There simply is no way file to cope with all these options.
rajendra82 said:
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
Click to expand...
Click to collapse
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
rajendra82 said:
1. Wipe device and restore to factory stock.
Click to expand...
Click to collapse
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------
yelloguy said:
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
Click to expand...
Click to collapse
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Taosaur said:
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Click to expand...
Click to collapse
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
Click to expand...
Click to collapse
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
Click to expand...
Click to collapse
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0p1 at the temporary location you created using the command:
mount /dev/block/mmcblk0p1 <full path to the directory you created>
4. Now use Astro to go over to the directory you created and mounted mmcblk0p1 into. You should see:
u-boot.bin which is the bootloader
u-boot.bin.stock which is the backup of the old stock bootloader
uImage and uRamdisk which are your primary kernel and ramdisk
uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)
u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam
5. Rename uFImg to uAltImg, uFRam to uAltRam. And edit the contents of u-boot.altimg and u-boot.altram to match the new file names.
6. Reboot as usual into primary or secondary.
Now if an CM7 update ever replaces your u-boot.bin, you will not lose dual boot, as you have it set up as uAltImg and uAltRam per the new protocol.
Sent from my SAMSUNG-SGH-I897 using XDA App
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
Taosaur said:
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
Click to expand...
Click to collapse
I am sorry if you think I am rationalizing, but that was not my intention. I just wanted to point out that the files you linked to do not meet your own criteria.
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible IMO, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------
Taosaur said:
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
Click to expand...
Click to collapse
It would work. If you apply my zip, there will be a uAltImg and uAltRam in /boot (in addition to uFImg and uFRam). If you apply another update that pushes the CM7 bootloader, it will then look for these files with trying to do an alternate boot, and would boot into a unrooted stock 1.3.
rajendra82 said:
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0 at the temporary location you created using the command:
mount /dev/block/mmcblk0 <full path to the directory you created>
Click to expand...
Click to collapse
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
yelloguy said:
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
Click to expand...
Click to collapse
I see a typo in my command (stupid Swiftkey X). It should be:
mount /dev/block/mmcblk0p1 <some directory>
Also try typing just mount in terminal to see if /dev/block/mmcblk0p1 is already mounted somewhere else.
rajendra82 said:
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter will lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
Click to expand...
Click to collapse
Riiiiight... it would install stock 1.3 to the device. That's the intended behavior. The point is to avoid the unnecessary step of updating in any process that includes flashing stock to the sole or primary partition. One example of such a process would be a fresh dual boot setup. That it does not update or otherwise rely upon an existing install is the point.
Granted, such a file would not repartition the device, but it would install up-to-date stock in one step regardless of how a device is partitioned (1/5, 2/5, 5/1 or dual boot).

[Guide] Easy method to removing UImage (Bricked, CN, etc) & Choosing Default OS

Hi.
First, a disclaimer... I will not be responsible for you messing this up and bricking your device. I am only outlining a guide which I figured out and used to get my TP setup the way I wanted. DO NOT come to me for support, as I am not a dev and really have no time to save anyone from their doom...
I used RootExplorer (Paid App -
https://market.android.com/details?...sImNvbS5zcGVlZHNvZnR3YXJlLnJvb3RleHBsb3JlciJd) to do the steps outlined below. You may use any file manager of your choice, granted that it gives you root access with read/write access to /boot folder. Please make sure you backup anything you plan on changing by making copies and moving them to a safe location... Don't way I did not warn you... ^_^
With that said... I hope this helps some one... ^_^
I have just figured this thing out and soon after noticed that there is a thread with a video showing the methods to remove the extra UImage from the moboot boot menu.
The video shown here http://forum.xda-developers.com/showthread.php?t=1511050 is a great way to remove the redundant UImages from the list except I figured out a easier method and also a way to choose the default OS (WebOS or CM or CN) to load when TP boots, which the video does not get into.
Once I updated to the latest CM9 V2, I rebooted and my TP wanted to boot into the Bricked_Kernel which I did not want. I would, in this case as many of you, scroll (within 3 seconds) to the right entry to boot or else, I would be needing to reboot again.
So here is what I did.
Boot into your Rom (CM9 in my case)
Install RootExplorer from the market.
Launch RootExplorer. You will be asked to grant SU. Press Yes.
Navigate into /boot folder.
Click on the Mount R/W. This will change to Mount R/O. Now you have read and write (important) access to the contents of this folder.
Find the entry UImage.Bricked_Kernel (It might be UImage.ClassicNerd or something else).
Long press the UImage you want to delete (or modify).
Delete (rename, if you want to keep it for some reason) the UImage of the old kernel
Click on the Mount R/O to set the folder for read only access before you exit.
Now when you reboot, you will notice that the MoBoot menu is missing the entry for the extra kernel that was there before. The problem now is that the default boot selection has been set to WebOS. This is because the device is looking for the missing default entry in the boot menu. So it's just going to the top of the list. If this is what you want, you can stop here but if this is not the OS you want to load by default, follow the next few steps.
Launch RootExplorer
Navigate into /boot
Click on the Mount R/W to set write access.
Find the entry moboot.default
Long press moboot.default and choose Open in Test Editor.
The entry in this text file will show the OS that MoBoot will choose to load by default. Mine had an entry "Bricked_Kernel"
Delete the entry in this file and retype the OS of your choice. Mine was "CyanogenMod" (without the "").
Exit. You will be told that RootExplorer made a moboot.default.bak was created for safety. If you are using other file explorers you might not get the automatic backup. So please make a back up of this file before you change the entry.
Click Mount R/O to set the permissions to read only before exiting.
Reboot.
Now you will see that the MoBoot has the right OS as the default OS.
For those of you that desire to make the WebOS as the default OS you can type WebOS in the moboot.default. Well, good luck.
PLEASE DO NOT CHANGE FILES IN THE /BOOT IF YOU ARE NOT SURE WHAT YOU ARE DOING!!! Only follow this guide if you are comfortable doing so!!!
Good stuff, man.
The major difference between my tutorial and yours is that Root Explorer is a paid app, whereas my tutorial uses ES File Explorer which is free.
If you have Root Explorer though, this is definitely easier.
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
nomadman said:
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
Click to expand...
Click to collapse
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
cvcduty said:
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
Click to expand...
Click to collapse
well there's more than one way to skin a robot. i personally think it's even easier running the commands in android terminal than plugging into a pc.
what if i dont have the moboot default file?
phonetec said:
what if i dont have the moboot default file?
Click to expand...
Click to collapse
Ok... can you describe your situation with bit more detail?
Are you running CM9? Or any other ICS or GB custom rom?
How did you install your android rom?
I am not aware (since I am not a dev and no where near an expert on the matter) a way to install Android other than the CM7 or CM9 method using MoBoot to push the files to TP...
So if you can outline some details of your situation, I hope someone can shed some light for you...
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
phonetec said:
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
Click to expand...
Click to collapse
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
cvcduty said:
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
Click to expand...
Click to collapse
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
phonetec said:
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
Click to expand...
Click to collapse
I think if moboot is still installed, it's probably looking for the moboot.default file but since in your case, it's missing, it's booting what ever is on the top of the list of the UImages. I think you can simply create a text file and name it moboot.default in the /boot directory. As the content of the text file put CyanogenMod. Change the permissions of this file once it's placed in the /boot directory to rw_r__r__ (same as other files in the folder). Change the folder to R/O and reboot... I think it will work.
Worst case I guess you will have to push moboot via pc again...
Good luck...
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
phonetec said:
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
Click to expand...
Click to collapse
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
itsDefying said:
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
Click to expand...
Click to collapse
Good catch. I missed that one. He should have used the new moboot. If he used CM7 acmeinstaller he probably meant he also used the old moboot also.
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
dirtyfrog said:
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
Click to expand...
Click to collapse
Very good point. As some one said, there is more then one way to skin a cat.
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
travisross69 said:
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
Click to expand...
Click to collapse
That's perfect! The point is for people to able to fix this easily on the fly. So if you don't have access to Rootexplorer, this method can be used to change the default OS the TP would load at reboot. Thanks.

[Q] Too many booting options, how to remove them?

Basically on my moboot, I have the option to boot into about 6 different things and that's unnecessary.
I have the options to boot into:
WebOS
Cyanogenmod
AOKP
CM Bricked Kernel
Clockworkmod
WebOS Recovery
How I got it this way, I'm not entirely sure because the way the TP works is different than anything else I've used.
How can I delete all the extra boot options besides WebOS, AOKP, CWM, and Recovery?
Do I have literally like 6 partitions going on or what?
A bit lost here.
Go into /boot and delete the uimage.* for the boot that you want to remove for example uImage.AKOP that should do the trick.
I would use the Terminal emulator, and issued the following commands:
Code:
- su
- mount -o rw,remount /boot
- cd /boot
- rm uImage.CM*
- rm uImage.Cyano*
- echo "AOKP" > moboot.default
- cd /sdcard
- umount /boot
- reboot
Then you'll have those two images removed, and be back to booting by default to AOKP.
haxin said:
Go into /boot and delete the uimage.* for the boot that you want to remove for example uImage.AKOP that should do the trick.
Click to expand...
Click to collapse
You should be able to do this from a root explorer in Android. This is what I do, but generally in IntrnalzPro in webOS (make sure to enable master mode). When I get too many boot items they usually fail to boot android. It might be because I have CWM and TWRP. There is only so much space for those uImage files, when that space is full they don't get created right and it won't boot. Since CM9, this has been my only reason to boot into webOS.
Sent from my Galaxy S II (i777)
So all I have to do is go delete the .image in /boot?
I had messed around in there before and didn't know it was that simple.
I Am Marino said:
So all I have to do is go delete the .image in /boot?
I had messed around in there before and didn't know it was that simple.
Click to expand...
Click to collapse
Yep, that hard part is getting r/w access to the folder.
The files will be uImage.[ROM name] not *.image
Sent from my Galaxy S II (i777)
I have Root Explorer so it shouldn't be too hard I'd imagine.
I got it fixed, so thanks everyone.
moboot uimage and tga cleaner
download the moboot uimage and tga cleaner under beta on classicnerd.net then flash that. It should clean it up.

[Q] Mounting trouble, bloatware removal only.

Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!

Categories

Resources