Related
I read as much as I can about installation of a custom ROM. I think I'm confident enough to do it now, but I just want someone to review these steps before I start.
I have a Rogers I896 currently running the stock froyo that I upgraded via Kies with a build 10.10.
Because this is on a build 10.10 I can't follow the steps vertabim with the guide in the android development forum.
1. Root with SuperOneClick
2. Titanium Backup
3. Use Odin3 v1.7 or later to restore to stock with this http://forum.xda-developers.com/showthread.php?t=905042 and the 512 pit file. (I understand this is unnecessary as I'm already stock, but in case I need to revert back to stock from a custom ROM, this is what I'll do)
4. Reroot with SuperOneClick
5. Get the ROM and put it in the root of the phone
6. Download ROM Manager and install Clockwork Recovery
7. Boot into recovery and install zip from SD card and choose the zip file that I downloaded.
8. Titanium Backup to restore
Please let me know if I'm missing something. I think I read something about Nandroid backup somewhere in the forums. I'm not exactly sure what that is and it didn't really say that in the guide. Should I do that and how do I perform that?
I'm thinking about installing either Paragon, Serendipity, or di11i. Perhaps someone can also maybe list some differences, issues, pros and cons about these ROMs.
Thanks in advance!
your steps are good enough for you to flash to a new rom.
You may have trouble with installing Clockwork. If you do, follow this link.
Also, once you reboot into clockwork, remember to do a backup of your current ROM and move it and your TiBu backups to your HD. Clearing your cache before you install your new ROM isn't a bad idea either
Goodluck!
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
integrasaurus said:
You may have trouble with installing Clockwork. If you do, follow this link.
Also, once you reboot into clockwork, remember to do a backup of your current ROM and move it and your TiBu backups to your HD. Clearing your cache before you install your new ROM isn't a bad idea either
Goodluck!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App
likiud said:
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
I do not think "clear cache" is necessary when you install a new rom, since most of rom will format the related partitions first. You can clear the dalvik cache in the cwm.
A master clear is recommended since it will reset your phone to factory default and delete all the data in your built-in sdcard.
Click to expand...
Click to collapse
mengbo said:
likiud said:
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
I do not think "clear cache" is necessary when you install a new rom, since most of rom will format the related partitions first. You can clear the dalvik cache in the cwm.
A master clear is recommended since it will reset your phone to factory default and delete all the data in your built-in sdcard.
Click to expand...
Click to collapse
It doesn't hurt AFAIK. I do notice after restoring apps with TiBu some apps require you to clear their cache in order to work properly, so I do it as a preventative measure.
Another tip: do NOT restore all system data with TiBu after you flash!
Click to expand...
Click to collapse
I started on Rogers stock 2.2.
Used superoneclick to root. Installed rom manager. Used a script to modify my recovery 3e file. Rebooted into recovery. Flashed cwm. Installed my custom rom.
Pretty awesome.
Sent from my SGH-i896
Hey I don’t mean to hijack/bump the thread but I’ve got an I896 which I’m attempting to flash a custom ROM onto, but I’m a complete phone newbie and could use some assistance when it comes to clarifying some instructions. This thread seemed to be the most “laid out” instruction guide for the I896 which I could find.
Currently my phone is running 2.2 Froyo / I896UXJL1 / Kernel 2.6.32.9 which I got via Kies early January when the update was released by Rogers.
I downloaded SuperOneClick 1.7 and rooted it without problems, but that’s as far as I’m clear/comfortable.
1. Do I need to use Odin (http://forum.xda-developers.com/showthread.php?t=905042) to restore to stock? Since I’m on the default Rogers technically that is already stock, no? Can I simply continue on from where I am?
a. If I don’t need to use Odin, do I need to make a backup with titanium?
2. Does step 6 of the OP’s list simply involve hitting the “Flash ClockworkMod Recovery” option in ROM Manager v3.0.1.0?
3. After that is it simply a matter of downloading my ROM of choice (Serendipity 5.12) and putting the .zip into my root folder, booting into recovery via the “Reboot into Recovery” option in ROM Manager, and then selecting to install the ROM .zip file?
4. Is my above three points everything I need to know or is there anything else I should know/be considered?
Also, when rooting I simply turned USB debugging on, ran the two .exe’s in order and then hit root after plugging in my phone. Was I supposed to go into download mode or anything or is that only for other modes of rooting (I have superuser installed and titanium backup was able to get root access so I assume my phone rooted properly).
That being said, I’ve read a ton of threads and a ton of stickies but things tend to seem either old/outdated or focusing on the AT&T i897, with there being limited information on a newbie friendly “explain all” way from A to B for the i896, unless I missed it. Some mention rooting with X, and using path ABC to root/flash a custom rom, and others mention rooting with Z and using patch DEF to do the same; all of which have left me feeling uneasy about flashing. ><
I'd be more then happy to provide any information in which I may have left out, and would appreciate any help I can get as I'm more then enthusiastic about flashing my first custom ROM but would like have the knowledge to do it right instead of being left with a brick. Yes, I know it seems almost all "bricked" captivates are unbrickable, though I would prefer to avoid that road at all costs either way haha.
mengbo said:
Another tip: do NOT restore all system data with TiBu after you flash!
Click to expand...
Click to collapse
I'm curious to know why not to restore system data?
Is "missing apps with data" ok to restore?
Restoring system data messes things up. Restore "missing apps with data" only. no system data.
If you restore system+data your home screen will fill up with force closes faster than you can clear them out, I know this Because I did it...twice, this is where my aww.W.T.F? sig came from. Don't panic if this noobish brain fart happens to you, just re-flash the rom and only restore missing apps+data as studacris said and enjoy.
Please read this post in its entirety before downloading and flashing.
THIS IS FOR I9020T ONLY! IF YOU DECIDE TO GET BRAVE AND TRY THIS ON AN I9020A, I9023 OR D720, MAY THE FORCE BE WITH YOU. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO ANY PHONE BY USING THIS ROM.
YOU MUST FLASH THIS ROM USING CLOCKWORKMOD RECOVERY. THIS WILL NOT FLASH USING THE STOCK ANDROID 3E RECOVERY AS THE ZIP FILE IS NOT SIGNED. I HAVE NOT TESTED IT ON OTHER RECOVERIES.
This is probably more for posterity now than anything else, however I have created a CWM-flashable full on ROM for the Nexus S Gingerbread firmware, version 2.3.2, build GRH78C. This is built exactly the same way that the full OTA ROM packages for 2.3.3 and 2.3.4 were built.
Some notes:
1. Flashing this ZIP will remove ClockworkMod Recovery on first boot. Android 2.3.2 contains a script that automatically overwrites alternate recoveries with the stock Android 3e recovery each time you reboot your phone. The script is located in /system/etc/install-recovery.sh. If you root the ROM, you can rename this file to avoid flashing the stock recovery on each reboot.
2. Flashing this ZIP will overwrite your bootloader and radio, restoring them to I9020XXJK1 and I9020XXJK8 respectively. These are the versions that came stock with GRH78C.
3. GRH78C is receiving OTA updates. As of this writing, the latest version of Android is 2.3.4, and Google is pushing an OTA update for 2.3.2 to 2.3.4.
4. This ZIP will NOT clear your user data or cache. For users running a stock ROM, I would highly suggest clearing your data and cache manually as sometimes downgrading without clearing data and cache can cause problems. If you are coming from a non-stock ROM, you are required to clear your data and cache or the ROM will not boot.
5. Since writing NFC tags wasn't introduced until GRI40/2.3.3, the Tags app is read-only.
6. There is no video chatting through Google Talk. This feature was not introduced until GRJ22/2.3.4.
Instructions:
1. Download the Stock GRH78C ROM package here.
2. Copy it to the root of your USB storage.
3. Reboot into ClockworkMod Recovery (or flash it).
4. Select "Install ZIP From SD Card"
5. Select "Choose ZIP"
6. Find the ZIP file and select it.
7. Wait for it to finish.
8. Wipe data and cache (optional but HIGHLY recommended for stock ROM users and REQUIRED for non-stock ROM users)
9. Reboot and have fun.
Reserved...just in case.
Thank You will post results if needed,i doubt it,again thank you very much,ping33tx
I can access the bootloader, I can access the clockwordrecovery, odin recognizes the device, but I can not access the intern sd.
I can only try to restore by odin
I'm looking rom to use the odin.
My nexus s is bricked, anyone help-me
I'm Brazilian and I used google translate, sorry.
i was googling for stock roms and found this
i had no idea if i have the i9020t or not
now my phone wont even turn on, no life
any ideas?
*EDITED: not sure which version i do have actually
SS2006 said:
this rom was bad...i was googling for stock roms and found this
i have the i9020t
now my phone wont even turn on, no life
any ideas?
Click to expand...
Click to collapse
Wanted to flash this ROM, just wanted you to confirm that yours is an i9020A, not i9020T, therefore that's the reason why it won't turn on now.
Sorry for your phone by the way.
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Can you boot it to bootloader?
From off position, try Vol UP + Power.
If you can see the Android logo and 4 menu options, you got yourself a great deal.
SS2006 said:
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Click to expand...
Click to collapse
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
al_madd said:
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
Click to expand...
Click to collapse
He doesn't need to. If he can get to the bootloader, he can flash and boot a recovery via fastboot.
No guys, seems i got myself in a mess. It is indeed a i9020a (the info under battery was erased so i didnt know0 and i flashed the i9020t rom in this thread (different radios)
so this thing is HARD bricked, screen won't turn on, no bootloader, nothing, tried to get it into download mode (even without screen turning on) assuming it was working, but odin doesn't realize its there
so i think my only solution is jtag. I can buy a usb jig but I think that usb jigs dont do anything for hard bricked phones, am i right
Much thanks for your help.
This seems to be the only place I can post.
Basically the title.
Here is some info to avoid some easy questions:
Rooted D3 (obviously)
5.6.890 (I think those were the numbers, I am sure it wasn't 5.7 something)
Using the Droid 3 bootstrapper. NOT safestrap, though in Hashcode's post, he said he updated it to be compatible with boostrap.
Flashed Steel Droid v3 about 2 weeks ago, week later flashed to the Bionic Blue theme.
Ran the "Safe bloat removal script (50+ apps) [UPDATED 9/1/2011]" script.
Ran the script to get my bloat back.
No problems until....
Tried to flash to CM7.1 Alpha using Droid 3 Bootstrapper
Bootloop.
tl;dr: How do I correctly install CM7.1?
you may just need to boot into andriod recovery and clear cache. i dont use bootstrap anymore, but its essentially the same. boot into recovery, format /system (under mounts and storage) then install CM7, factory reset (wipe data/cache) then boot her up. Safestrap is the way to go though
So I tried again, wiping my cache and /system, this time I ended up with a soft brick (Only thing appearing is the Motorola Dual Core screen). Clockwork Recovery doesn't appear on startup anymore.
How do I:
a) Unbrick and
b) Correctly install CM7.1?
Thanks to anyone who responds in advance.
EDIT: I should have read more closely, the order I performed the actions was:
1. Install CM7.1
2. Install Gapps
3. Format cache
4. Format /system.
5. Factory reset
slayer621 said:
So I tried again, wiping my cache and /system, this time I ended up with a soft brick (Only thing appearing is the Motorola Dual Core screen). Clockwork Recovery doesn't appear on startup anymore.
How do I:
a) Unbrick and
b) Correctly install CM7.1?
Thanks to anyone who responds in advance.
EDIT: I should have read more closely, the order I performed the actions was:
1. Install CM7.1
2. Install Gapps
3. Format cache
4. Format /system.
5. Factory reset
Click to expand...
Click to collapse
Ya formatting /system after flashing removes the cm7 rom. Try
Format /system
Install cm7/gapps
Wipe data/cache
xt860, android 2.3.5, Monster rom
Endoroid said:
Ya formatting /system after flashing removes the cm7 rom. Try
Format /system
Install cm7/gapps
Wipe data/cache
xt860, android 2.3.5, Monster rom
Click to expand...
Click to collapse
Thanks for that. Any idea on how to unsoftbrick though?
Also, the link in this thread http://forum.xda-developers.com/showthread.php?t=1255198
is dead.
if you formated /system after installing the rom, then you need to SBF. start the phone with m+pwr, use vol down to reach AP Fastboot, then use vol up to select. download RSD 5.5 and the sbf file. check out the RSD thread in the dev section. and you are on verizon, correct?
edit: dang i see what youre referring to. the 5.6.890 download isnt working. i have it, but i dont know i dont have an account to upload to. And on my 5meg pipe itll still take a few min lol
2ndedit: i cant upload. sorry i dont have a professional account and its 455MB.. check this out it works http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/
MrJudylicious said:
if you formated /system after installing the rom, then you need to SBF. start the phone with m+pwr, use vol down to reach AP Fastboot, then use vol up to select. download RSD 5.5 and the sbf file. check out the RSD thread in the dev section. and you are on verizon, correct?
edit: dang i see what youre referring to. the 5.6.890 download isnt working. i have it, but i dont know i dont have an account to upload to. And on my 5meg pipe itll still take a few min lol
Click to expand...
Click to collapse
hxxp://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/
(replace xx with tt)
I'm following this guide, figured I'd just re root and install cwm again and restore my back up. Will that work?
lol yes youve got it. follow the instructions. also, do not freak out if after you SBF it still does not boot up. Even after the SBF (RSD will show rebooting) and you could bootloop on the animation. if that happens, boot into recovery using M+pwr, select android recovery, when you get the android with the !, use vol up and down and you'll get another menu, and clear cache. then you'll be ok
and also, dont use cwm, use hashcodes safestrap. read up on safestrap, and then you can flash without worrying about bricking
MrJudylicious said:
lol yes youve got it. follow the instructions. also, do not freak out if after you SBF it still does not boot up. Even after the SBF (RSD will show rebooting) and you could bootloop on the animation. if that happens, boot into recovery using M+pwr, select android recovery, when you get the android with the !, use vol up and down and you'll get another menu, and clear cache. then you'll be ok
and also, dont use cwm, use hashcodes safestrap. read up on safestrap, and then you can flash without worrying about bricking
Click to expand...
Click to collapse
Alright thanks man, after I get back up and running I'll be sure to switch to safestrap. Thanks for all the help.
glad i could help. ive been there lol
I apologize if this has been covered already, but the search feature finds more noise than signal and I just don't see it.
I have safestrap on my xt860 with cm9 on the safe side of things, and I have a messed up and broken "stock" on the unsafe side. I'm pretty happy with cm9 in general, however there are still some known limitations, so I'm thinking of putting something else on the non safe side. Obviously I'd rather not break cm9 in the process.
Is doing this as simple as switching back to non safe and flashing the zip for what I want to try? Or is it more complicated than that?
You got to put back bootstrap. I think though that safe mode backs up to your internal storage so you should be good.
Sent from my XT862 using XDA
I believe that, when you have switched into non-safe mode, safestrap will not allow you to select the "install zip from sdcard" menu option. I am running safestrap 1.08d tweaked and just tried to do it. It says ".zip install is only available while safe System is enabled."
I don't think rick has gotten non safe flashing functional on any version.
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
That's how I do it anyways
Sent from my XT860 using xda premium
Endoroid said:
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
Click to expand...
Click to collapse
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)
I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip
LaZiODROID said:
I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip
Click to expand...
Click to collapse
Yeah, got the SBF loaded. Still have no idea why i couldn't get CM9 in to my non-safe. right now though I seem to have a bigger issue, for some reason my recovery can no longer mount my SD card (though the OS can) I've tried bootstrap, and safestrap, neither can read from my external SD... it's rather odd!
I found with safestrap 1.08f (ricks version) it wouldnt mount mine either.
I started from scratch and installed 1.08d and it works just fine.
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Sent from my XT860
thanks for the tip about 1.08f... maybe that's it, I'll investigate...
LaZiODROID said:
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Click to expand...
Click to collapse
I know sticking to safe is safer, but sometimes I don't want "safe" I want functional. seems a waste to me to have stock loaded on non-safe when I don't plan to ever, under any circumstances, use stock.
I like CM9, I'm quite happy with it as my every day rom. I'd like to put it in non-safe so that I can play with new ones in safe. unfortunately I'm not having much luck with that right now...
I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D
ve6rah said:
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)
Click to expand...
Click to collapse
There is indeed a sbf. Theyre called fastboot now. There's a thread for it
Sent from my XT860 using xda premium
LaZiODROID said:
I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D
Click to expand...
Click to collapse
well, others have reported success, but none of them seem to be using CM9 in the non-safe, so maybe it's something specific about that one rom?
I think I'll give it one more try today before giving up and going back to root/cm9 so that I don't end up without a phone for the next 2 weeks until I have time to play again!
seems to me that the trick is to find a bootstrap/recovery that is NOT safestrap, install it, install whatever you want, uninstall it, install safestrap, and go on with life as usual.
Unfortunately I can only find one non-safestrap recovery, and it doesn't seem to work too well. most are dead links now as everyone moved to safestrap.
Anyone have a link to a non-safestrap recovery I can try?
I have uploaded 2 bootstrap versions to DepositFiles. Sometimes when you root, a complete version of BusyBox isn't included, so:
1) Root
2) Install Busybox Installer from the market (it's free)
3) Run BusyBox Installer and install whatever highest version installs successfully. (I found that after using the Bell SBF, the highest version wouldnt install properly, so I just chose the next one in the list)
4) Install whatever bootstrap app, and click its button to do the recovery install.
Droid3 Bootstrap:
Link: http://depositfiles.com/files/5qcaay2e7
(This one's for the Droid3 - I believe that if you're using an XT860, the only way this will boot is if you have USB plugged in!)
Milestone3 Bootstrap
Link: http://depositfiles.com/files/o248gldkm
(For the XT860, this should just boot normally, without USB cable)
Well, the solution continues to elude me.
With Milestone3 Bootstrap I simply can't get cm9 to boot. it flashes ok, but then it just freezes on the motorola logo and won't go any further.
With Droid3 Bootstrap (and USB plugged in) I can boot in to cm9, but USB has to be plugged in EVERY time you boot up (not much of an option for an every day phone)
After getting cm9 working under Droid3 bootstrap though I decided to try to change to safeboot. Unfortunately that way it boots up to "android is upgrading... optimizing applications" followed by "starting applications" and it never gets past there.
I think part of the problem is that I have no way to uninstall the droid3 bootstrap before installing safestrap. anyone have any ideas how to do that properly?
So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)
LaZiODROID said:
So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)
Click to expand...
Click to collapse
yes CM9 worked on Droid3 Bootstrap. but not once I installed safestrap (without tweaking anything in safestrap.)
it doesn't so much "freeze" as it decides to "optimize applications" and then just can't seem to get past there. (only solution is a battery pull at that point) I do get the safestrap flashscreen, and can get in to safestrap.
After wiping cache, dalvik cache, and data (factory reset) I reboot, go through the safestrap boot screen, and get to... nothing. blank screen, refuses to boot further.
So something obviously went wrong between when I had Droid3 Bootstrap loaded, and when I installed safestrap. I'm just not sure what other option I have at that stage to make things go more smoothly. theoretically if it works under the Droid3 bootstrap, then it should work as the non-safe for safestrap, but it just doesn't, and I have no idea why.
well, still didn't figure out CM9 in the non-safe... so I've gone a different route.
I now have mavrom in the non-safe, and I'm in the process of installing steeldroid in safe...
Nice. So there was nothing special you had to do after your fresh MavROM install to get safestrap going?
Sent from my XT860
No, went smoothly.
- SBF to stock
- root
- install milestone3 bootloader
- flash mavrom
- remove miletone3 bootloader
- install safestrap
- switch to safe
- install steeldroid
Spent quite some time searching through the forum but I'd still like a few pointers on where to start particularly (in which order).
Like;
1) Root
2) CWM
3) ROM Manager
4) SuperUser
5) Odin
6) Data wipe
7) Binary count reset
8) Recovery Manager
9) Custom ROMS
(EVEN THOUGH I'VE NUMBERED THEM, IT'S NOT LIKE I KNOW THE ORDER, JUST IN CASE YOU'RE WONDERING)
So here are my main questions:
1) In which order do I install them ?
2) Is there any relationship between them? (i.e. I thought ROM Manager let you install CWM and with CWM you can get to Recovery manager or something...)
3) Do I need the Recovery manager for recovery or for installation of custom ROMS?
4) What is the point of getting custom ROMS when I get root ?
Phone: GT-I8190
Android: 4.1.1
Baseband/Build: I8190XXALJL
Thanks in advance, and apologies for asking same question if there is a thread around here about it.
I'd prefer ppl to explain rather than referring to other threads as that got me a little confused before. (you may still refer if that thread is clear enough)
Ok. The order is
1- Root (superuser comes with it)
2- CWM
3-see the right rom for u
4- wipe data, cache, and dalvic in advanced, to flash rom
5-reset counter when u flash anthing in odin u will have a yello triangle to remove u have to reset counter ( does not effect the phone
Press like if i helped u
Sent from my HTC One X
mhoss48 said:
Ok. The order is
1- Root (superuser comes with it)
2- CWM
3-see the right rom for u
4- wipe data, cache, and dalvic in advanced, to flash rom
5-reset counter when u flash anthing in odin u will have a yello triangle to remove u have to reset counter ( does not effect the phone
Press like if i helped u
Sent from my HTC One X
Click to expand...
Click to collapse
Could u explain 3 a bit more ?
Also is there any relationship between CWM, ROM manager, custom ROMS and Recovery Manager ?
Go to development forum, pick one of the pre rooted firmwares and flash via odin. Then install rommanager app from tbe play store and flash cwm recovery. Don't worry about binary count coz triangle away app works on our phone. If you want to wipe the phone reboot to recovery and wipe data. To boot into recovery use the quick boot app from play store.
Sent from my GT-I8190 using Tapatalk 2
...and most important.. Don't forget to make a full nandroid backup in recovery before you start to apply mods and other things
Might come in handy if the phone fails to boot!
Should note that after custom rom you can't get access software update through kies air. At least I can't :-\
Sent from my GT-I8190 using Tapatalk 2
Sv: Where to start ?
Who needs Kies when there is XDA?
Sent through time and space from my s3mini.
vonuzu said:
Go to development forum, pick one of the pre rooted firmwares and flash via odin. Then install rommanager app from tbe play store and flash cwm recovery. Don't worry about binary count coz triangle away app works on our phone. If you want to wipe the phone reboot to recovery and wipe data. To boot into recovery use the quick boot app from play store.
Sent from my GT-I8190 using Tapatalk 2
Click to expand...
Click to collapse
So if I understand this the right way; CWM recovery has custom ROMS or am I getting the wrong idea ? - Why do I need it ?
(It's just that I've been a little confused because of the mass information available on XDA, so bear with me if I'm a bit annoying
tys0n said:
...and most important.. Don't forget to make a full nandroid backup in recovery before you start to apply mods and other things
Might come in handy if the phone fails to boot!
Click to expand...
Click to collapse
Which would you prefer; Nandroid or Titanium ?
Do I need "busybox" for anything ?
Do I need Kies to connect my phone to PC btw ?
Another question: There are two recovery images on the official site of CWM, do we need to choose the normal one or the touch and what about the ROMS, do I need to install those seperately ?
Mystique03 said:
So if I understand this the right way; CWM recovery has custom ROMS or am I getting the wrong idea ? - Why do I need it ?
(It's just that I've been a little confused because of the mass information available on XDA, so bear with me if I'm a bit annoying
Which would you prefer; Nandroid or Titanium ?
Do I need "busybox" for anything ?
Click to expand...
Click to collapse
With cwm or any other custom recovery you will be able to install zip files with mods, tweaks, roms, and so on. Simply put, non-samsung-signed-things + other functions as well.
You wont find many custom roms for s3mini yet wich it to be flashed through cwm. For now i think theres only BenzRom but I guess more will come
Nandroid or Titanium ? BOTH!
Nandroid for restore if something goes really bad, and remember to make sure you have a backup before you apply changes or mods. If you dont like it you can easily go back to previous state without flashing new firmware and have to install all your apps from scratch.
You will be just where you were at the time the nandroid was made.
Titanium backup to backup your apps and appdata. When installing new rom you can simply restore all your apps and appdata without downloading everything again. Do not restore systemdata. It often leads to alot of trouble.
Just make sure you save all your backups on your external sd, so it won't get wiped by mistake.
Busybox is needed if you want more than just root so go ahead and install.
tys0n said:
With cwm or any other custom recovery you will be able to install zip files with mods, tweaks, roms, and so on. Simply put, non-samsung-signed-things + other functions as well.
You wont find many custom roms for s3mini yet wich it to be flashed through cwm. For now i think theres only BenzRom but I guess more will come
Nandroid or Titanium ? BOTH!
Nandroid for restore if something goes really bad, and remember to make sure you have a backup before you apply changes or mods. If you dont like it you can easily go back to previous state without flashing new firmware and have to install all your apps from scratch.
You will be just where you were at the time the nandroid was made.
Titanium backup to backup your apps and appdata. When installing new rom you can simply restore all your apps and appdata without downloading everything again. Do not restore systemdata. It often leads to alot of trouble.
Just make sure you save all your backups on your external sd, so it won't get wiped by mistake.
Busybox is needed if you want more than just root so go ahead and install.
Click to expand...
Click to collapse
Last couple of questions for now (apologies ) ;
1)Do I need Kies to connect my phone to PC btw, cuz I read something about USB debugging mode to be turned on and ADB...
2)There are two recovery images on the official site of CWM, do we need to choose the normal one or the touch and what about the ROMS, do I need to install those seperately ?
3)So every time we flash another ROM it has a chance to brick or are we safe if we made a backup beforehand ?
4)What format should I format my card to ? - FAT32, NTFS, ext4 or ...?
5)Does data wipe erase all data on phone or phone and sd card ?
6)Given both CWM and Odin flash what would be more recommended ?
Mystique03 said:
Last couple of questions for now (apologies ) ;
1)Do I need Kies to connect my phone to PC btw, cuz I read something about USB debugging mode to be turned on and ADB...
2)There are two recovery images on the official site of CWM, do we need to choose the normal one or the touch and what about the ROMS, do I need to install those seperately ?
3)So every time we flash another ROM it has a chance to brick or are we safe if we made a backup beforehand ?
4)What format should I format my card to ? - FAT32, NTFS, ext4 or ...?
5)Does data wipe erase all data on phone or phone and sd card ?
6)Given both CWM and Odin flash what would be more recommended ?
Click to expand...
Click to collapse
No worries. Better be safe than sorry
1. No, you dont need keis unless you want to look for official updates.
For filetransfer I use Airdroid or box/dropdox/4shared. Official updates will be available to download anyway
Adb (Android Debug Bridge) is just a terminal. I won't go in to details here but you will find lots of threads on how to install and use it if you search xda.
2. They both do the same thing, but in touch-version you make your choices on touch screen while the other one is managed with phones physical buttons. I prefer the latest.
Roms for cwm are packed as .zip & are downloaded separately. As I said before there isn't much to chose from for our device yet.
3. Everything done after root is a risk. Even root can be dangerous if it's not done right.
Usually if something goes wrong it will just lead to a softbrick wich can be fixed in download mode or recovery.
Once rooted, make sure you do that cwm-backup to keep on your external sd. It's also a good idea to keep an odin flashable firmware on your computer, just to be sure.
4. Go for fat32. It can be changed later if you want to explore link2sd, sd-swap etc..
5. Factory reset will wipe all internal, but not your external sd.
6. cwm makes it possible to flash custom roms while odin can't. You need odin to flash official samsung firmware, but cwm to flash custom roms, mods, and so on. Can't really compare those two with each other, as they are used for different things.
:good:
Dated, but still very relevant.
tys0n said:
No worries. Better be safe than sorry
1. No, you dont need keis unless you want to look for official updates.
For filetransfer I use Airdroid or box/dropdox/4shared. Official updates will be available to download anyway
Adb (Android Debug Bridge) is just a terminal. I won't go in to details here but you will find lots of threads on how to install and use it if you search xda.
Click to expand...
Click to collapse
What should I do for wired transfers only, I mean.
Do I need to search for the phone specific driver for pc at Official Samsung site or is there no driver ?
Any other things I need to turn on except USB debugging mode when wired ?
Edit: Nvm, just got on the right track again