Related
First off, happy holidays to the XDA community!
So, I've done the math and realized that I've flashed over 100 ROMs (yes, that is including updates) over the past year+. My phone is running really sluggish, no matter the ROM nowadays. Looking around my phone's internal storage, I notice a lot of remains left here and there from the different ROMs. Is there a way that I can wipe my phone's internal shtuff, but keep the Recovery image so that I can flash a ROM without all the other remanances that have accumulated?
If this is possible, what commands would I have to do to accomplish this? (ie, "rm -f *" or w/e).
Thanks guys!
Joe
You could just rm the directories and recreate them, yes? From recovery console? Then just flash your ROM of choice again.
I'm truly a linux noob. Mind informing me what command I would type in the terminal? And are we positive said command will not affect the recovery partition? (Can't afford to botch it up). Thanks!
Reboot into recovery, and drop to a console. Type:
su
rm -r system
rm -r data
mkdir system
mkdir data
Though I can't promise promise that if you rm system it won't screw up your recovery.... I don't THINK it will. Tell me, do you have the sdk setup on your pc? Or at least adb/fastboot?
EDIT: Don't rm system.
Oy. I'm actually embarrassed to admit that the drivers for the phone wouldn't install for me on Windows 7 . So, no I don't have the proper means to get back on my feet were it not to work. Also, where is the SU functionality housed..(ie. /system/bin/su ?).. Would hate to lose root, too
Yes, that would be where the su binary is... but that wouldn't lose you root, not in the sense you mean it. Really, "root" is all in the custom ROM, and in the ability to flash it. When you "root" your phone, you are just installing the spl that will allow you to flash any ROM. Custom ROMs almost all have su functionality built in, and flashing any of them will put that right back in bin.
Anyway, you probably shouldn't rm system... there is a lot of mission-critical stuff in there. I doubt you would do anything irreparable, but with you not having fastboot or at least adb... best to let someone else risk it first. And, sorry, that someone won't be me.
I really appreciate your help, thank you . The reason I want to do this in the first place is to improve the responsiveness on my G1. Sometimes, when the phone is coming out of sleep mode, the touch screen doesn't register where I touch it... It'll effect the touch where ever it feels. I usually turn the screen back off, turn it back on, and that usually gets me back to par... For a while, that is. It occasionally starts spazzing sporatically after I've been using it for a while. Since it decides when the screen will respond properly and when it won't, I want to believe it is a software issue, not hardware. I am running Dwang 1.17.1, processor speed under what he had set (I use 384max, 284min), 8gb Class 6 MicroSD, ext3. Funny enough, this issue occurred less on WG, but still happened. It happens more on Dwang and CM, respectively. Any insight while I have the attention of someone knowledgeable?.. Thanks for your time.
Dwang? For all the talk of that rom being so stable.... it uses the RAM-hacked kernel, which is begging for little bugs like yours. I'm guessing you also use compcache? (I don't remember if his ROMs have it enabled by default or not). Compcache can make things like waking up a little slow. Pretty much, and solo task that can be slow at times, is slower with compcache... especially if you have downclocked your cpu from what Dwang has tested with his memory setup. The thing is, compcache makes more efficient use of RAM, but it does so by compressing it, so your processor works harder, especially when loading anything: returning to browser or home screen, waking the phone, etc.
Also, on Cyan's ROMs, I've noticed something, and I think it's because of his attempts to stay legal by backing up and using whatever google apps you already have, instead of re-flashing them. Sometimes bits of my previous ROM are left over when I flash it, and I get weird bugs. So, do this for me (if you want, and are willing to wipe all your data and apps):
wipe EVERYTHING: data, dalvik, ext, everything
flash the htc image
flash cyanogen's latest
reboot, login, and get to the homescreen
Then, reboot to recovery, wipe everything again, and flash the two images again. Tell me how it works for ya.
Will do that and report back to you asap. I estimate in 30 mins or so. Thanks for the tips, btw.
joewhispers said:
Any insight while I have the attention of someone knowledgeable?..
Click to expand...
Click to collapse
I'd just like to give you the disclaimer, I'm just a geek, not necessarily knowledgeable. I'm certainly no ROM dev. I'd hate for anyone to get the idea that I know what I'm talking about here, and follow my advice to the point of messing something up for them.
joewhispers said:
Will do that and report back to you asap. I estimate in 30 mins or so. Thanks for the tips, btw.
Click to expand...
Click to collapse
No prob... I do hope you find it more stable now (Cyanogen is really the king of stability). Play with it for a day or so; I will have to come and read your results tomorrow. Forgive me, but I have to sleep. It's 3am in my timezone, and I have to be up early to go see my baby sister open her presents. Will check in tomorrow. Merry Christmas!
Alright, wiped everything.. flashed htc, cm, logged in, repeat. verdict is out for now. quick question, ext3 or ext4 preferred? Enjoy your family, sir. Merry Christmas!
joewhispers said:
Alright, wiped everything.. flashed htc, cm, logged in, repeat. verdict is out for now. quick question, ext3 or ext4 preferred? Enjoy your family, sir. Merry Christmas!
Click to expand...
Click to collapse
ext3. Also, never wipe anything but user data, and dalvik cache. To format system or w/e just flash a different rom. It will do it for you.
thank you, nephron!
joewhispers said:
thank you, nephron!
Click to expand...
Click to collapse
anytime bro
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
As usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
EDIT:When updating to a new CM rom you WILL encounter a boot loop, simply run the steps below AGAIN during the loop cycle and then reboot the phone and it should work.
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
heroskyy said:
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
Click to expand...
Click to collapse
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
nonmindo said:
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
AS usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Click to expand...
Click to collapse
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
kamasi36 said:
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
Click to expand...
Click to collapse
awesome! thank you! Ive always been confused about that
heroskyy said:
awesome! thank you! Ive always been confused about that
Click to expand...
Click to collapse
Ha. me too man. You have to learn fast on here. They expect us to know all this stuff coming in the gate. Just holla back if you need some more help. I'm a noob too but managed to figure it out.
http://forum.xda-developers.com/showthread.php?t=532719
This might help you get started. make sure you get everything updated because this is kind of dated.
kamasi36 said:
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
Click to expand...
Click to collapse
Yeah cyanogen (especially) and dhanj should be credited more than me. I didn't really do anything but add on how I got it working for me.
One thing to mention, if cyanogen doesn't implement this officially in his ROM (and for most people it's probably not needed) you'll have to redo this procedure each time you flash/update so I'd suggest keeping the 2 files saved.
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
Thanks dnanj. Just upgraded to ext. 3. apps2sd b4 now.
You betcha....as always, just sharing information whenever I can.
am i suppose to get a conformation in shell if the commands worked?
Ohal_yeah said:
am i suppose to get a conformation in shell if the commands worked?
Click to expand...
Click to collapse
When the commands complete, you should be brought back to the prompt where the shell awaits the next command.
I apologize for not looking deeper into who deserves credit here, thanks for those of you that do know!! I was simply just trying to make it easier to get the information to people that might want it...
as for the debate of needing a2sd or not, i was out of space right from the get-go because of all the apps i had on my mt3g...so to me i definitely need it out of the 1gb partition i made on my sd card i have .82 free now lol...
completed all steps but everything still saves to internal memory
JustinLoe said:
completed all steps but everything still saves to internal memory
Click to expand...
Click to collapse
a small glitch probably when you run the last command before adb reboot, it fails to create the directory as it exists, probably change the name to solve it, it happened to me once
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
jakontil said:
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
Click to expand...
Click to collapse
ext3 is essentially a ext2 file system with journaling.
Click Here to read about ext3 and it's benefits over an ext2 fs. As to why ext2 over ext3 for apps2sd, since journaling improves reliability of the fs, that makes it more ideal than ext2.
it works great thanks!
hi dnanj
thanks for the link
sorry but im stuck here
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push 04apps2sd /system/etc/init.d/
failed to copy '04apps2sd' to '/system/etc/init.d/': Is a directory
C:\android-sdk-windows\tools>
why does cmd show me this error can you help me out please..very much appreciated
Okay, I've been trying to root my sprint hero for 3 days now. I flashed it to Cricket service actually. So here are the commands I am using:
C:\Users\Ashton>cd\
C:\>cd AndroidSDK\Tools\
C:\AndroidSDK\tools>adb devices
List of devices attached
HT02AHF00747 device
C:\AndroidSDK\tools>adb shell chmod 0755 /data/local/asroot2
C:\AndroidSDK\tools>adb shell
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[+] Using new pipe_inode_info layout
Opening: /proc/627/fd/3
SUCCESS: Enjoy the shell.
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cd /system/bin
cd /system/bin
#cat sh > su
cat sh > su
# chmod 4775 su
chmod 4775 su
#
Okay, that's exactly what's displayed on my screen. I didn't put the # or $ signs in there. That's just what appeared as I was typing the commands. When I try to flash a recovery image, it won't install. I get a Signed Failure error. Any ideas? What am I doing wrong? Also, does a cricket rom for sprint hero exist? Or should I use a Non-Sprint ROM? I mean, it's a sprint hero, but it has been flashed. Thanks Everyone!
This has nothing to do with Development.
...sorry, i thought...
I'm not sure where else to post it. I thought it did, since the rooting guides and roms are posted under Development.
Would the General are be more appropriate? I'm not trying to post in the wrong places. But I don't want to post there and get the same response. lol, Just need help. Not looking to tick anyone off.
This has nothing to do with Development.
Click to expand...
Click to collapse
Not being mean but who made you the cdma hero police.. you never actually help anyone. just tell them they are wrong for posting here.
to the OP, try to type
exit
adb shell
then the rest of flashing instructions
Sent from my HTC Heroc using the XDA mobile application powered by Tapatalk
Thanks Jus10o. I'll try that. Sometimes I miss windows mobile. Lol, flashing android is a pain.
ashton2091 said:
Thanks Jus10o. I'll try that. Sometimes I miss windows mobile. Lol, flashing android is a pain.
Click to expand...
Click to collapse
I came from WinMo as well. Trust me, once you get the hang of it, it's easier and faster than RUUing every time.
Okay, I tried the above. Here's what I happened. I am rooted (i think). I used a file explorer to to backup the recovery image. It said it was successful. Then I rebooted into the Recovery Menu. Still looks like the stock one. Three lines of options with blue fonts. I try updating the image from there, but all I get is "Can't open /cache/recovery/command". fustrated, It sucks to be a noob all over again.
I forgot to mention, I also did a factory reset before trying to write the image as suggested in the instructions.
Thread moved.
Jus10o said:
Not being mean but who made you the cdma hero police.. you never actually help anyone. just tell them they are wrong for posting here.
to the OP, try to type
exit
adb shell
then the rest of flashing instructions
Sent from my HTC Heroc using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
ROFL ROFL ROFL You GO Girl! What rock have you been under? I do nothing BUT help in these forums. Also, I DID tell the OP they posted in the wrong section. Im pretty sure when I said "This has nothing to do with Development." that meant he posted in the wrong section. By the way, the mods made everyone the CDMA Hero Police. Apparently, you cant read the forum rules and guidelines either. Here, let me help you,
http://forum.xda-developers.com/showpost.php?p=6372744&postcount=2
From Ryan's quote,
Mods, including myself, are not here to keep the forum organized after the fact, we need your help to keep it organized, clean and grouped.
To the dedicated members that care to keep this forum, subforums included, clean and organized and grouped.
Please start reporting threads to the mods to take action. Using this button.
Click to expand...
Click to collapse
Look everyone, don't get at each other like that. It's not cool. Lol, it's okay. I really didn't know. I mean, the fact that the rooting section was here, I thought it was okay to post here. But hey, it's in the right place now. I understand the forums can't be trashed with everything posted everywhere. Lol, really it's cool.
ashton2091 said:
Look everyone, don't get at each other like that. It's not cool. Lol, it's okay. I really didn't know. I mean, the fact that the rooting section was here, I thought it was okay to post here. But hey, it's in the right place now. I understand the forums can't be trashed with everything posted everywhere. Lol, really it's cool.
Click to expand...
Click to collapse
Dont boot into recovery, just boot up your phone and do this....
Put the New recovery image on your sdcard, by either opening it up on your computer. Or put the file into your c:/android-sdk/tools folder and type this
adb push NameOfRecovery.img /sdcard/ (make sure you name recovery the exact name as it appears on your computer or rename it to just "recovery" so its easy to remember)
once its on your sdcard and your phone is on charge only.. Not mounted to the computer type this
adb shell
cd /sdcard/
flash_image recovery NameOfRecovery.img
Okay, I think I know what the prob is now. Even if it's not the prob, it will have to be fixed. I have the wrong stock image. I have v1.56 which I think blocks rooting. Trying to downgrade. Thanks Everyone
Hi Guys,
This is driving me crazy. A lot of people, who are too lazy to search. Well, here you go.
Allright, you brought your Xperia X1 with android. Now, there is a problem. Once in a while, the keyboard does not respond, only action is a reboot. HELP?
Allright, lets get started.
Download this package:
http://www.mediafire.com/?cp1o1glxjo145pu
Install a android of your choice(just normally).
Unpack, and copy all (yes, all) contents to you SD card.
Move the turbo or Monster kernal to the NKBoot Map, click yes to replace any excisting files.
On your computer, open up the readme, and read it carefully.
After step 4(after you entered 'su') type this:
rm /lib/modules* -rf
That will remove your current modules, and at the next boot, they will be replaced.
Reboot, and proceed with step 5 and the rest. Follow the guide excactly, then you're good!
Have a nice evening!
Not Test, But Thanks You !!!! I Need
sorry to say but when i folled your guide to just after step 4 when typing the -rf
it says cannot remove read only file system
is that normal?
thanks
yes it is. just reboot after the error, then the new modules will install!
Just thinking ... a dev might know it this is possible ...
Hm, perhaps, best solution at the moment would be, to run the unload-load-script when the phone is waking up from sleep mode. So, when keypad is lost, the user can send to sleep with the power button an immediately switch it on again ... and additionally, the script can run when a call comes in ... don't know if these events can get picked up and the event-handlers can be changed, just thinking ...
Ciao
Klaus
Kurt Krummbein said:
Hm, perhaps, best solution at the moment would be, to run the unload-load-script when the phone is waking up from sleep mode. So, when keypad is lost, the user can send to sleep with the power button an immediately switch it on again ... and additionally, the script can run when a call comes in ... don't know if these events can get picked up and the event-handlers can be changed, just thinking ...
Ciao
Klaus
Click to expand...
Click to collapse
Don't know if this could be a good option. Because I have had some freezes when runing the script. And sometimes the screen changes it orientation.
thomskipsp said:
After step 4(after you entered 'su') type this:
rm /lib/modules* -rf
Click to expand...
Click to collapse
casualt said:
sorry to say but when i folled your guide to just after step 4 when typing the -rf
it says cannot remove read only file system
is that normal?
thanks
Click to expand...
Click to collapse
Shouldn't it be?:
After step 4(after you entered 'su') type this:
rm /lib/modules/* -rf
mind the /
Anyway, I tried both ways, and rm /lib/modules/* -rf seems to work, but I can't load back into CWM if I install a kernel with seperate keyboard modules. I think I mess up the exact order of installing normal, removing modules, replacing kernel, restarting. Hope this will work
http://forum.xda-developers.com/showthread.php?t=1072387
Yes. I can restart keyboard after freeze. Although with eggy monster kernel, my screen is rotated 90degrees after that.
No. I can't get back into CWM, after I switched to a kernel with seperate modules.
The original kernels of Honeycomb v3 both worked.
I tried the kernels with seperate modules of this post and i tried the ygge kernels.
Can this be solved? No. But apparently, there is a workaround http://forum.xda-developers.com/showthread.php?t=1072387.
when I type "sh /data/opt/autostart.sh" and press Enter, I get this error:
"insmod: can't read '/lib/modiles/microp-ksc.ko': no such file or directory
insmod: can't read '/lib/modiles/microp-keypad.ko': no such file or directory"
Can you help me?.
Where is kovsky keyboard modules????
I using ygge kernels with HoneyComb Froyo V.3
PS: sorry I used the same post in several threads
Thanks to Trekfan422991 for cluing me in on the Optimus 3D recovery.
Working:
Nandroid
ADB (after special driver install, need to tweak recovery for it to work with normal drivers)
Mounting USB to computer
Flashing zip files
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
I am in the process of making a recovery specifically for our device, it is mostly done and will be posted here when it is ready!
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
If you don't understand something in that list, DO A SEARCH AND LEARN, don't clutter the thread with crap!
Lets get started!
Lets start by getting the recovery.img file on the phone. Open up a cmd prompt and type:
Code:
adb push recovery.img /data
The rest of this will be done on the phone shell. In the cmd prompt type:
Code:
adb shell
We will need to have su access, In the cmd prompt type:
(If you haven't allowed shell su in SuperUser now would be a good time to accept the root request on the phone.)
Code:
su
Now we are going to backup your current recovery to your sdcard. In the cmd prompt type:
(make sure your sdcard is not mounted to your computer)
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
After that is done we are going to flash ClockWorkMod Recovery! In the cmd prompt type:
Code:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Congrats! You now have ClockWorkMod Recovery! In the cmd prompt type:
(each line is single command)
Code:
rm /data/recovery.img
reboot
How to enable ADB access: (only if it's not working already)
Download and install: (unzip and install the 2 exe files)
http://www.mediafire.com/?j5m1plnvzb8r0zc
While booted into ClockWorkMod Recovery, go into your device manager, you should see an "LGE Android Composite Device" with a yellow triangle on it.
right click on it, update driver software...
select browse my computer for driver software
select let me pick from a list of device drivers on my computer
click the "Have Disk" button
click the "browse" button
browse to;
for 64bit:
C:\Program Files (x86)\LG Electronics\LG Android Driver\64BitADB
for 32bit:
C:\Program Files\LG Electronics\LG Android Driver
and select lgandadb.inf
click "ok"
From that list select "Android Sooner Single ADB Interface"
click "next"
click "yes" on the popup
Click to expand...
Click to collapse
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose. Good thing I am having issues with permissions with this didn't notice the SD Card Mounting issue till just now. That I can't deal with atm.
malickie said:
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose.
Click to expand...
Click to collapse
I found a few modes, but no drivers yet so I don't know what they are. Even if we break stuff the kernel and recovery are separate, so technically we should always be albe to get back into recovery to fix stuff.
thankyou DG for getting this started..
so now with my clockworkmod i just made a backup of stock rom... if i say change the framework and I get boot loop.. will this clockwork mod be able to restore the original rom without any problems???
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Trekfan422991 said:
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Click to expand...
Click to collapse
I got mixed up as to what partition to flash, you just flashed a recovery image over the kernel... its ok tho.
follow my instructions to the su part, then do this.
// this will restore the kernel
dd if=/sdcard/mmcblk0p5.backup of=/dev/block/mmcblk0p5 bs=4096
// this will backup recovery
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
// this will flash cwm
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
OP is fixed!
edit--
and you have no adb access, this is going to get interesting!
haha... i shoulda noticed
____
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Trekfan422991 said:
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Click to expand...
Click to collapse
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
47r0n1n said:
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
Click to expand...
Click to collapse
sorry just side note:
how you liking your thrill compared to the evo 3d???
designgears said:
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
Click to expand...
Click to collapse
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Komodo Rogue said:
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Click to expand...
Click to collapse
I took it down for now, working on some issues.
Woohoo, got Trekfan422991 all fixed!
its true... i tested out my framework mod and it works great!!! look sway better then stock!!!
designgears said:
I took it down for now, working on some issues.
Click to expand...
Click to collapse
Ah, gotcha. I thought I was going crazy Thanks!
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
designgears said:
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
Click to expand...
Click to collapse
After CWM is installed and working on our device, would it be safe to fix permission in "ROM Manager," or does that just fix permissions through whichever recovery is currently installed?
I'm guessing someone here knows how ROM manager works in this regard, but if not, I'd be happy to be a guinea pig... after all, I can make/restore backups now! : )
gtg465x said:
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
Click to expand...
Click to collapse
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Komodo Rogue said:
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Click to expand...
Click to collapse
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
gtg465x said:
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Click to expand...
Click to collapse
Oh, good to hear! Man I really have to sit down and try to learn some more technical stuff sometime, because ROM creation, and not even just the theming aspects, is so appealing to me.
Maybe you can create a thread placeholder and describe what you've done so far? We're really getting OT, sorry all.
timbrendelaz said:
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
Click to expand...
Click to collapse
Oh, I thought you could flash zips through adb after doing the fix? Or no? (((edit: wait, no, I was thinking about pushing .apks through ADB, not flashing .zip files))) Hopefully this is something DG's new recovery might address. If no to both, could you distribute ROMs via nandroid backup files of a fresh ROM installation? It would be incredibly inefficient, but it would work, right?