Related
Ok this is probably a noob question,
i have a vibrant 2.2 tmobile, i just did the 3e recovery mod so that i could root the phone, i finally got it rooted and Im positive it is (terminal emulator says # when i type su,and superuser is working so Im pretty sure its rooted) so when i go into rom manager and flash clockworkmod recovery it always says it works but i cant get into the new recovery only the stock and i cant backup my original rom, does anyone know how to fix this so i can get into clockworkmod recovery?
Im new to rooting so sorry if this is a extremely noob question.
from stock recovery, select "reinstall packages"
I tried reinstalling the packages from the stock recovery but it takes me back to the stock recovery, Ive tried that many times but i never get the clockworkmod recovery, i have no idea why it wont enter the clockworkmod recovery? Can i install it without rom manager?
Download "update.zip" that is attached to this post....place it on the ROOT of your sdcard (not in any folders)
now this is the voodoo edition of clockwork....we are going to want to disable this to avoid issues (sorry, i dont have a normal clockwork available). so also download the disable voodoo .zip attached to this post.
DONT UNZIP EITHER FILE. DOWNLOAD THEM, AND PLACE THEM BOTH ON YOUR SDCARD AS IS!!
follow these instructions exactly:
1. place both files on root of sd
2. reboot into stock recovery
3. "reinstall packages"
3a. if it brings the red clockwork recovery, move onto step 4.
3b. if you dont see clockworkmod, choose reinstall packages again...if you see it move onto step 4.
3c. if you still dont see it, i cant help you further
4. now that you are in clockwork, DONT REBOOT OR FLASH ANYTHING YET, we need to disable voodoo
5. in clockwork choose "install zip from sdcard"
6. choose "choose zip from sdcard"
7. scroll to the disable voodoo zip and select that...confirm install, select "yes"
8. it should take less than a second, youll see "installation complete". (if you see "installation aborted" dont worry, just move on with the steps...see my explanation below)
9. Reboot before flashing anything, very important
10. you are now ready to flash using clockwork mod
PS - im not sure if youre familiar with voodoo, what it is/how it works....but the disable voodoo zip is just a precaution. im not sure if voodoo is built into this edition of clockwork, or if you actually have to have a voodoo kernel to actually be able to activate it. even though i think you need to have a compatible kernel, its better to play it safe.
with that said THERE IS A POSSIBLILTY THAT WHEN YOU FLASH THE DISABLE VOODOO, YOU MAY GET "INSTALLATION ABORTED"....dont worry continue on with teh steps, that just means that voodoo does not actually exist for you, which is probably ideal anyway
It still didn't work, i must be doing something Ive tried everything but it just wont go to clockworkmod.
perhac88 said:
It still didn't work, i must be doing something Ive tried everything but it just wont go to clockworkmod.
Click to expand...
Click to collapse
Have you tried the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
No i haven't tried toolbox yet but ill give it a shot.
I had a similar issue...
Are you getting the error "signature verification failed"?
No I haven't gotten a single error message, i flash clockworkmod recovery and it says success, I reboot into recovery i get the stock recovery, so Ive tried reinstall packages several times and i never get an error message although when I do hit reinstall packages it goes through in like 2 seconds but It never lets me into clockworkmod.
Use AIO Toolbox (recomended) -> install USB Vibrant drivers (if you don't have them, included with AIO Toolbox) and flash stock 2.1 rom (included in AIO Toolbox), after that use rom manager (from market) and install clockwork recovery, then download any kernel (for 2.1 rom of course) with root and flash it thru already installed CWM or flash ANY rooted custom rom - that's all (and it will take about 0,5h - not big deal).
toolbox is the way to go it will do everything for you just simply follow the steps from top to bottom. and you will be fine but before you go with tool box do read the noob guide it will surely make u understand the functionality of the toolbox. good luck
Hmmm......
Ok ill give that a try hopefully that will work.
edx009 said:
I had a similar issue...
Are you getting the error "signature verification failed"?
Click to expand...
Click to collapse
This is the issue I am getting, even when using the files mentioned on this post.
How did you solve this problem?
EDIT: Just used the AIO Toolkit, restored to stock, rooted, installed ROM Manager, then went ahead and installed my custom ROM! HoneyGinger is talking to me and getting itself set up. Lovely!
Hey guys,
I was running 2.2 on my vibrant and was having issues with cwm as well. I followed the advice here and it worked great. Flashed Nero v3 and my phone is running like a champ!
Thanks again to everyone for their expertise.
\m/ Clef \m/
Andreal said:
Use AIO Toolbox (recomended) -> install USB Vibrant drivers (if you don't have them, included with AIO Toolbox) and flash stock 2.1 rom (included in AIO Toolbox), after that use rom manager (from market) and install clockwork recovery, then download any kernel (for 2.1 rom of course) with root and flash it thru already installed CWM or flash ANY rooted custom rom - that's all (and it will take about 0,5h - not big deal).
Click to expand...
Click to collapse
Worked for me too! Thanks everyone!
I had this same problem hopefully this works
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
Hello,
I recently tried to install custom firmware for my dell streak, However, my device
is android 2.2.2, and I tried to install superboot ver 2.1 (Cuz a misleading
comment on a web site mentioned its ok to root the system by it), my dell
suddenly rebooted in an infinite loop. I tried to enter the recovery menu by
holding the volume buttons and then choosing recovery. Also, I downloaded
Streak_309_11548_00.pkg and hoped this would work, but a stupid error
had occurred, bad, just bad file at the middle of verification process.
Anyway, I cant install clockworkmod because there is no way to root the
device, besides I dont have any back-up image of the streak.
please forum help me, the phone is almost new ( 2 tweeks of use only)
and I will pay if your solution work.
Regards and dont flame me, Im a new android user.
tried an older update, new error
Status 2???!!!
You do not have to be rooted to install a custom recovery. You do have to 'catch' the phone as it reboots by holding the volume up and volume down buttons as it reboots after the fastboot reboot command. If you let it boot into a stock rom the stock recovery will overwrite the custom ROM.
Use StreakMod Recovery if you want a custom Rom.
You need to slow down and do some reading before you go any further.
Suggestions;
Streak Wiki
Universal instructions for flashing any ROM and FAQ
Making a custom recovery stick
Using StreakMod Recovery
Do you know what baseband is on your phone? If you do DL the rom from the Streak WiKi, rename it update.pkg and put in on your SD Card, do not put it into a folder. Start recovery and select to install the update.pkg. You probably got the error when you attempted to use BB 309 because the recovery and the rom you attempted to flash did not match. They need to match so keep trying until you get the correct rom for the version of the recovery that is on your phone.
You could also use fastboot to install StreakMod Recovery, use the fastboot command to rebot the Streak, As soon as the reboot process starts hold down both volume buttons to get to StreakMod. If you use StreakMod you could install SimpleStreak or StreakDroid 1.9.1.
There are links to useful references in my signature.
Good luck.
PS - your Streak is not bricked as long as you can get into recovery, fastboot or your can connect to your computer and the QDLTool will see it.
Im in recovery menu now and If I click
Software upgrade via Update.pkg
the screen goes blank and then just nothing.
K clockworkmod works now
tell me what to do next.
I tried to install streakdroid 2 and its works WOW, thanx to you.
one last question how to install the latest baseband from the following link.
http://forum.xda-developers.com/showthread.php?t=1091236
sadly the link isnt available.
Don't worry about the latest baseband. If it boots up for you, I would stop there for now. If you were on 2.2.2, then you have either 351-354. Any of those will work for you.
tenorntex said:
Don't worry about the latest baseband. If it boots up for you, I would stop there for now. If you were on 2.2.2, then you have either 351-354. Any of those will work for you.
Click to expand...
Click to collapse
First, I would like to thank you and the forum for your help.
I have experienced a low graphical performance, and Im thinking to roll back
to the latest DJ_steave's custom firmware (2.2.2), However, I can access to
clockworkmod by pressing both volume buttons and then choose the recovery
option, thats weird since almost all tutorials mention that if you want to access
that mod, you have to press the volume up button along the power button.
For now Im waiting for a response whether to downgrade the firmware or
keeping the streakdroid 2.
Regards.
if everything is working then i suggest before trying anything else. do a nandroid backup first, (by going into recovery then advanced and then you see a nandroid backup option)
And i feel streakroid recovery package is preferred for streak as it is designed for streak only and works great.
lesson = homework
Hi, I'm hoping somebody might be able to shed some light. My phone isn't rooted or unlocked and last night I did the OTA update. Upon the first reboot, the phone is stuck at the "Dual Core Technology" screen and won't go any further. I can hold volume down and power to get to Fastboot, a bunch of other things, and Android Recovery.
Within Android Recovery, I've tried the wipe options as well as the apply sdcard update.zip but the wipes don't help anything and the apply update resutls in a signature error.
I feel like if I could just get the .zip update onto the internal SD storage, the apply update would work (maybe the OTA download was corrupted somehow). Is there anyway to use Fastboot or Moto-Fastboot to copy files to the internal SD storage?
Any help would be much appreciated.
hi
Try putting the OTA on a micro SD card (thats where it looks for it anyways) rename it to update.zip and try to flash that update.
y2whisper said:
hi
Try putting the OTA on a micro SD card (thats where it looks for it anyways) rename it to update.zip and try to flash that update.
Click to expand...
Click to collapse
Thanks for the reply.
Tried and this is what happened (which is more than before):
Install from SDCARD
Finding update package
opening update package
Verifying update package
...installing update
Verifying current system
.....assert failed: apply_patch_check("preinstall/app/gameloft_3games.zip","5428aeff....."
Not sure what that means, but I'll google and search here for a bit.
Edit: Just noticed that there was more to the output:
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
either you removed some apps before or the install updated some of the files and now doesn't pass the verification check.
search on here for a bit possibly flash cwm recovery and then the 2.2 gobbstopper. or you could try to go through bell as everything you have done is through official methods.
Okay thanks a lot for the help. I have since Unlocked using the Pudding IHOP thread and next will install Gobstopper 2.3.4 Bell (http://forum.xda-developers.com/showthread.php?t=1195922), though the CWM (tenfar's) post only shows that it's only for AT&T, which is odd since it's linked from the Gobstopper Bell thread).
Any idea if I can safely use Tenfar's CWM Recovery from here?:http://forum.xda-developers.com/showthread.php?t=1138541
Actually i would recommend only using that one for gobstopper purposes.
Although I would either wait until the 2.3.4 version is updated or get the 2.2.2 version and upgrade your device with the official rom as there have been changes since the 2.3.4 leak
Would you recommend another recovery instead of Tenfar's CWM? I'm currently now using the one that came in the CWM_INT_Recovery.zip (recover-d00.img).
Seems really hard to find a recovery that is definitely safe with Bell Atrix, and I'm never sure if just "moto-fastboot flash recovery %recoveryfile.img% is all I need to do now that it's unlocked. I might have to find another ROM since the download isn't working so well.
to install the gobstopper? no only use the latest tenfar cwm for that. after which, you could go with romracer and it will be fine
Okay great, thanks. The latest Tenfar CWM says at the top of the thread that it's only for Unlocked ATT users in bold red text so I was hesitant to use it.
I have the same issue. I have tried EVERYTHING I can think of to get it to boot.
The only difference in my case is I have run the update multiple times all finishing successfully with no errors.
This is really bugging me, any help would be appreciated.
Thanks
Jeff53765 said:
I have the same issue. I have tried EVERYTHING I can think of to get it to boot.
The only difference in my case is I have run the update multiple times all finishing successfully with no errors.
This is really bugging me, any help would be appreciated.
Thanks
Click to expand...
Click to collapse
I'm an extreme novice Android/Atrix user but I would recommend doing what I did:
Use the Pudding IHOP instructions to RSDLite flash the unlocker SBF for Bell
Use moto-fastboot to flash recovery with Tenfar's latest CWM recovery (updated June 30)
Use Tenfar's CWM recovery to mount your USB storage, download the GobStopper 2.3.4 zip to your sdcard, then again using CWM, update from the zip.
See the GobStopper 2.2.2 thread for some pre-cleanup steps before trying to update with the 2.3.4 zip, all using Moto-Fastboot or regular fastboot from the Android sdk.
Thank you
You saved my life
Woot woot!
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted