Related
I've been doing a lot of reading lately and I am finally about to flash my first ROM. Below is a list of what I've done as far as backup and prep. What I want to know is if there is anything important that I missed?
Made a nandroid backup with CWM
Backed up apps with Titanium Backup
Backed up efs directory from the phone
I have a copy of settings.db on my compuer
I have Odin 1-click on my computer
I have a jig made up just in case
Also, since I am on stock 2.1(JH7), I assume I don't need to go through the odin 1-click step, right?
Thanks in advance for your help
looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
i also put a copy of my sd card onto my computer in case something goes bad, but that's just my paranoia/ocd
and you should flash at 100% battery and reset the battery stats while flashing. you can even flash while the phone is plugged into the computer or ac outlet, so the flashing process doesn't drain from the phone battery. some ppl say this is voodoo, but i always flash at 100% and reset the battery stats while changing roms because its a convenient time to reset stats
sublimaze said:
looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
Click to expand...
Click to collapse
OK, thanks. I'm glad you mentioned that. I do have it unlocked and I didn't even think about it. I have to go to Thailand in a few weeks for work so I need it unlocked.
I think I remember reading that the unlock code is located in the nv_data.bin file and can be found by searching the file with a hex editor. I'll have to read a little more and play around with that before I flash.
I have been reading a lot lately, but could not find an answer to my noob question. I was just wondering if I flash an I9000 based ROM and lose my unlock or my product code gets messed up, can I just copy the original nv_data.bin file to the new ROM or will that cause me other problems. I know there are post as to how to fix this, but they are geared toward people who didn't make a backup and copying original would be much easier and quicker. Thanks.
^^^ Any help with above question?
I also have one other question. I've been poking around with Root Explorer and I see that all the sytem apps are naturally stored in /system/app folder, but I don't see the downloaded apps in there. I see what apperar to be my downloaded apps in /data/app folder. Is this where they are stored and if so, can I just copy them out and then copy them back after I flash a new ROM? If so, is there anything else I have to do with them to make them work again (like chown through adb)? I was wondering this because I have some paid apps and I don't know if they will automatically be available for download again once I sign on to the market and I don't want to lose them. Thanks for any help.
Is it possible to remove the CDFS partition (Verizon Mobile) without rooting the phone?
It is the company's phone, so no rooting for me but I would love to be able to use the TB as a USB stick on my JVC KD-AVX77 in the car. Right now it doesn't see any music and I suspect that's because of that CDFS partition.
Any help would be appreciated.
Thanks.
I'd like to know this as well...
Bumping this up. Even if it requires root, would still like to know how to do it period, as I can't seem to find any info anywhere.
you have to delete a file and you need to be rooted to do so because it is a system file.
/system/etc/cdrom.iso is the file that needs to be deleted
magneticzero said:
you have to delete a file and you need to be rooted to do so because it is a system file.
/system/etc/cdrom.iso is the file that needs to be deleted
Click to expand...
Click to collapse
Awesome, thanks!
magneticzero said:
you have to delete a file and you need to be rooted to do so because it is a system file.
/system/etc/cdrom.iso is the file that needs to be deleted
Click to expand...
Click to collapse
How big is the file "cdrom.iso"?
bignew67 said:
How big is the file "cdrom.iso"?
Click to expand...
Click to collapse
I dont recall offhand...it isnt that big....more annoying than how big it is
The ISO is only about 6mb. However, after removing it, the CD drive still shows up when connected, just with no data. Any thoughts, or is this something a kernel dev/CM7(lol down with Sense!) is going to have to take care of?
In the programming menu the option was removed. Take the Incredible for instance, you could disable it, but not so on the TB for now. Unless someone figures out a way to change it Im out of ideas, but removing it worked for me.
magneticzero said:
In the programming menu the option was removed. Take the Incredible for instance, you could disable it, but not so on the TB for now. Unless someone figures out a way to change it Im out of ideas, but removing it worked for me.
Click to expand...
Click to collapse
Well at least removing it gets rid of the autorun prompt. Good enough for now, and I'm sure the CM team will figure it out.
Root here. Didn't work for me. I can't mount my sd card through my phone after deleting that file.
I did flash adrenalyn's 1.9 kernal some days before which may be the cause of my having a different result from others in this thread however I think it's a good idea to DO A NANDROID BACKUP BEFORE ATTEMPTING!
or at least rename the file with a .old or .bak extension, whatever ya like... luckily I have the backup from before the kernal flash
would logcat be able to track down what's being accessed while the phone is mounting volumes while enabling disk mode?
Rather than removing it, I replaced it with an ISO of my own that has the Tether for Android setup exe and dmg, and a few other misc files I might need
Ok. I am trying to convert a very nice chinese rom for the samsung captivate, to have english on the ui buttons instead of chinese. I have an idea how to go along with this, and the software, wish me luck and I will keep you updated on my progress with the rom modding. I hope to upload a compleat rom which is satisfactory, soon'er or later. Alot of .apk modding, rom testing, and apk signing will be needed on my part. I'll try to keep it nice like they made it, and the english support is all ready there just not on all the .apk applications included, that's my main goal to get the application buttons 100% ok!.
Frustrating. I just got the rom onto my captivate and the top bar was gone, so that mean's deleteing launguage settings wont take away the chinese interface words on the buttons and also destroy's the top bar. : \ I'm working on it though, I mean it seem's to be an application only issue but I don't want to rid the rom of applications just to get rid of chinese words for english words on some buttons. Any ideas? sry for my spelling. Btw I took those launguages out of SystemUI.apk & GoogleServicesFramework.apk, and i did it with Apk Manager here on windows 7.
Well that project went down the tolit, i'm too new to be trying that just yet, i'm just messing around with adb in cmd on windows for now, it's fun trying to figure things out and mess with my phone remotely! i'll let you guy's know if i find out any thing usful, thank you! : )
Keep at it. A long journey starts with but a single step..:good:
Thank you Grant Barker. I will keep at it, my brother I use his usb cable, he get's annoyed when his hp touchpad is getting low on charge and I got the cable lol, trying to figure out and test stuff with android. I test alot of rom's I find online and a few I really like, i'm more in for flashing a new rom than using one which is strange, also more into screwing around with the files than the normal day to day end user would ever dare doing. I like the stock captivate rom, I see issues though, the old JF6 version (stock) ran smooth as silk with a few audio glitches at boot and a lil lag at first run, but otherwise an ok version even today it still run's well for day to day tasks, the kk4 version (stock) is another story, at boot it has very bad visual lagging, i mean once it get's going it's ok but still there is alot of lagging with tasks, I think the hardware was better off with the intended first rom and JF6 kernel, but then there is the outdated issue with JF6 and i'd like to see a rom made from that version to flash and test, also i want to try and make a rom my self from that JF6 stock version better suited for today's online and offline world. Clean and simple that's how I like it. :fingers-crossed:
you seem young, keep at it...you will be a recognized dev in no time :laugh:
Ok! here is a modded .apk you can install in the system/app directory of you're captivate with kk4 rom, please remember to delete or backup the SystemUI.apk from you're system/app directory before! trying this if you want to test my first fairly simple attempt using android sdk and other tools. :highfive: Hope you like it! might even get a laugh.
I forgot to say thank's 2 up ^ thanks. I have a question. How do I get a rom i've modified with the kernel into a zip ready to be flashed, using cwm or any other custom recovery for installing .zip ready made roms. I just don't know how to intigrate all that data wipe and install stuff into a .zip file, do I just? put the main / directory into the zip and hope cwm does the rest lol, I know adb can push the files and folders but it has issues trying to delete un-empty folders which is a pain in the rear end, it like says file system is read read only or says folder not empty when i try to delete a folder but it docent care if i delete system files. Under c:\adb shell , then $ rmdir /system/app , it babbles on about the folder not being empty, even after installing the latist superuser binaries and superuser.apk and busybox with all its jargon tool addons or whatever there called. I just want any advice where to look or how to try setting up a .zip with a rom i've modified, so it can just be installed through cwm or any others like that. Thanks! : )
I'm messing with this rom at the moment http://www.downloads.bombaymobiles.in/index.php?dir=Samsung%20Flash%20files/I897/&file=I897UCJE5.zip it's the erliest version I could find for captivate that's downloadable. If you can find a download link which works for I897UCJE4.tar or .rar or .zip.. my mind will be blown..
Hmm I wonder what this is :highfive: oh ya! it's the KB1 stock kernel :silly: It was so easy to get I dunno why no one else had it. Oh! and what's this :silly: http://www.mediafire.com/?i47m7nmcnd66zgr Could it really be the I897UCKB1 Rom in .tar format, my captivate say's yes! :highfive: it is!
is there any way to undo this? i tried to go to a 4.2.2(liquid) and had some issues so i went back to 4.2.1.
did some more looking into and decided to try it again. same problems plus some. now im yet again back on 4.2.1 and have 3 different "0" folders and its driving me crazy...i tried using my pc to just cut and paste everything to where it should be a merge all the like folders but that is taking absolutely forever on some folders(had to go one at a time so it would do anything) some are quick but some arent.
do i just need to stick with what ive been doing or is there an easier way?
this is all on the internal storage if that matters
I haven't had this problem yet since I haven't switched back/forth... but I wonder if you might get faster results by using the command prompt. If you're not familiar with linux commands then I don't recommend it, but if you are.. then ADB shell, su, and start mv'ing.
OMG_VTEC said:
is there any way to undo this? i tried to go to a 4.2.2(liquid) and had some issues so i went back to 4.2.1.
did some more looking into and decided to try it again. same problems plus some. now im yet again back on 4.2.1 and have 3 different "0" folders and its driving me crazy...i tried using my pc to just cut and paste everything to where it should be a merge all the like folders but that is taking absolutely forever on some folders(had to go one at a time so it would do anything) some are quick but some arent.
do i just need to stick with what ive been doing or is there an easier way?
this is all on the internal storage if that matters
Click to expand...
Click to collapse
since you are using a 4.2.2 capable recovery, EVEN if you are back onto a 4.1.2 ROM and still have the 0 folder, the recovery will still read the 0 folder regardless. lessen learned for me the hard way, always look before wiping to make sure the file u want to flash is there..
anyway, delete all the zero folders.. in fact if you don't have toooo much stuff on the internal, then do a quick format, this will remove all the 0 folders and then move what you want back.
what I do when I'm on a 4.2 and under ROM is rename my 0 folder to anything but 0, for me 00, and if I'm going to flash a nandroid of a 4.2 ROM or install one I just rename it back to 0 and all is well. make sure to always keep an extra 4tw ROM on in the 0 folder, in case your backup aren't showing up when in the 0 folder on 4.2 ROM.. u can however use the file manager built into TWRP, delete the TWRP folder, reboot recovery and you will be back in action...
yes, I've been doing a lot of testing with 4.2.2 lol so I learned it all the hard way. this should save you a good amount of time.
im just using drag and drop, but everytime i go to the original destination(root or int. storage) it takes FOREVER to load...:crying:
driving me bonkers since im at work and have limited time to devote to this increasingly menial task
OMG_VTEC said:
im just using drag and drop, but everytime i go to the original destination(root or int. storage) it takes FOREVER to load...:crying:
driving me bonkers since im at work and have limited time to devote to this increasingly menial task
Click to expand...
Click to collapse
This is the main reason I haven't left 4.1.2 yet. Pacman 19.3 running to good to fool with that mess. But that's just me
Hi. I flashed the CM 10.1 M1 rom (4.2) and decided to go back to a stock rooted TW rom (4.1). This left me with the issue mentioned in this thread.
After reading the above posts, I just want to clarify how to deal with the "0" folder issue, which remains after reverting back to a 4.1 rom. My understanding is there are 2 ways to deal with this:
1. cut and paste the files in the "0" folder (which was created when flashing the 4.2 rom) back into the original internal sdcard folder. this would result in merging some of the folders/files with the same name in the "0" folder with those with the same name in the internal sdcard folder. Might also take a while.
2. use adb...if a step by step guide on how to do it this way can be shared, it would be appreciated.
because of the hassle. i would up just copying the contents of the "0" folder which I needed onto my computer, and formatted the internal sdcard, but if the adb way is a simply way, i am willing to give it a shot.
thank you for any input.
Argh! Pulling my hair out over this one. I've been flashing custom ROMs and rooting my phones for years now, since my old HTC G1. Even had KitKat running on my HTC Desire 4G!
... but this Sidekick is proving another matter. I've been through forum after forum, all saying the same things on how to root/flash this thing, but I haven't managed to get anything to work! So, here's step-by-step of what I just did and the result I get every single time, no matter the initial method:
1: Fired up ODIN3.
2: Wiped the user data and cache from the stock recovery (Android System Recovery (3e)).
3: Connect USB cable, reboot phone into download mode (using the battery-pull method).
4: Successfully flash to stock ROM, reboot.
5: Sign in with Google, enable WiFi.
6: Run SuperOneClick, reboot.
7: Grab ES File Explorer from the Market, after it updates.
8: Attempt to replace "recovery" in /system/bin with custom
... and here's where things break. Doesn't matter what version of SuperOneClick I use (and I've tried from 1.9.1 through 2.2.3), nor does it matter what exploit I select. What happens? Well... aside from everything on-screen claiming to be okay, and everything claiming it's working, once the rooting is "successful", I reboot like it says, see that SuperUser is in the applications, it shows me an su binary version...
... but anything that tries to run super-user (ES File Explorer included) that gets added to the super-user list simply does not work. I can't over-write the recovery, can't delete or muddle with anything that requires elevated privileges, and the ROM Manager for sure won't work because I can't get CWR installed.
I love my phones with keyboards. I really do. I'd love to keep this thing, but the stock firmware is driving me up a wall (especially that stupid media scanner). So if anyone has any ideas to throw at me, care to offer some? Haven't a clue at this point what I'm doing wrong.
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
demkantor said:
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
Click to expand...
Click to collapse
Awesome! I'll give this a go once I'm all done with today's activities and see if it works.
Well, apparently I have root access for the moment, but it is denying my replacing of /system/bin/recovery - in adb shell, it states "Filesystem is read-only", so I re-mounted /system -rw and no dice. Going to attempt to try again in a moment, after a reboot.
Okay, so since there's a problem with all of this, I'm going to try that second ROM (KD2 I think it was) - but as I recall, it was on a very slow server. Plus I have a load of things to do tomorrow, so it probably won't be until tomorrow evening sometime when I'll be able to flash it. Once I've used Odin to re-flash, I'll get back to you.
Well, I had to dissect "t839-Sidekick4G-UVKG2-One-Click.jar" and remove the xml file from within it, but I acquired the necessary package to upgrade to KG2 from KD1 through Odin3. Took a while to figure out just how to deal with it, and I was successful in flashing... and I even replaced the recovery file after rooting it again!
... however, now it just sits there at the "T Mobile Sidekick 4G" start-up screen when I attempt to boot into recovery, so now I'm preparing to re-flash it again to recover the stock recovery. So... still more on this, later.
EDIT: Also, I named the tar file "KG2OdinHeimdall.tar", since I basically ripped it right off the "HeimdallPackage.tar" file from the Heimdall one-click thing. Turns out, it apparently works just fine if you remove the .xml file from the original tar.
Finally!
I ended up having to use my own method to get the KG2 update installed because the one-click program kept crashing on me when selecting "Show all devices", and I opted to use AntTek Explorer (all you have to do is go into the program's options and it'll attempt to acquire admin privileges, if the device is rooted) to copy the recovery file to /system/bin - but your post worked for everything else, once I got past not being able to copy the recovery file.
I opted for the CM6 package and it's quite fast! Thank you loads, demkantor!
Nice! I'm glad all worked out well for you!
If you get a chance try out the one gingerbread ROM, its cool to see it running but there are still driver issues so keyboard is borked, really makes it pointless to have on this phone...
But there are a few nice froyo ROMs ready to be played with, someday development will hopefully pick up again
Until then, happy flashing!