Well, its an old streak 5, but it is new to me.
Just got the streak from someone today. Going to use it as a tablet. Any rom recommendations (not going to use it as a phone)?
Is this still the best rooting/recovery/flashing guide?
http://forum.xda-developers.com/wiki/Dell_Streak_5/Flashing_Guide
Tell me if I have this order right --
First Root,
Then flash custom recovery, then custom rom of course.
Is there any 'one click root method'? Or 'clockwork mod recovery' equivalent?
Actually, the order is...
Install StreakMod Recovery
Install Superuser from zip
Flash custom ROM
One-click root methods aren't recommended and really aren't required. I already gave the name of the CWM equivalent in my list. Do not let the Streak boot normally after installing StreakMod or else the stock ROM will overwrite the recovery.
thanks. does streakmod look the same as the default recovery? cause that is what i am seeing. is there a way to reboot into recovery from fastboot?
do you really have to name the file update.zip and put it in root? so, i would rename superuser.zip and the customrom to update.zip eventually?
ok, figured out what i was doing wrong. im rooted. i just installed longhorn, and DSC and i get nonstop FCs -- rendering both roms unusable. why am i getting nonstop FCs? do i have to update the baseband?
For the Gingerbread ROMs you do have to change the baseband. The only other possibility is that you didn't do a factory reset (option 1 in the recovery image) before rebooting.
nevermind. my problem was i had to do a "factory reset"... which seemed like a strange thing to call it
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!
Hi all,
I rooted my SGS2 (KE7) with CF-Root ages ago and haven't done much since then, aside from take regular backups.
Looking at the Cyanogenmod stuff, I fancy giving it a go. All the guides talk about using the kernel at http://forum.xda-developers.com/showthread.php?t=1118693 .
Does anyone know if I can flash the cyanogenmod ROM using the recovery mode I have with CF-Root, or if I need to get use the kernel from the above patch first?
This morning I tried installing the kernel (from the CF-Root CWM), when my phone rebooted, the touchscreen worked on the unlock page but not once I unlocked (I use LauncherPro as my launcher). Rebooting into recovery mode didn't work (the phone just booted normally) so I reflashed CF-Root but still had the same problem however I could boot into recovery mode and restore this morning's backup.
Now, the phone boots (with the warning triangle, expected) but there is no response after I unlock for a minute or so. Setting the stock launcher back works but I'm confused about why this should happen and what I should do next.
Does anyone know why my non-stock launcher is now being non-responsive for the first minute after boot / what I can do to get it back?
Am I able to install cyanogen with CF-root, or do I need to use the kernel in the above link? and if so, do I need to do anything other than just flash and if not why didn't the phone boot into recovery when I tried it earlier?
Any suggestions gratefully received!
-Jeff
The cf-root kernel is all you need to install cm7.
peachpuff said:
The cf-root kernel is all you need to install cm7.
Click to expand...
Click to collapse
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Electroz said:
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Click to expand...
Click to collapse
Don't quite understand this. I've got the cm_galaxys2_full-39.zip (100MB), I was going to put this on the SD card, boot into recovery mode and install from there. Are you saying I need to do this same process twice? (and if so, why does it only install the kernel the first time when it is the complete zip file?)
Cheers,
-Jeff
CF-root => Cyanogen mod
Hello everybody,
There are a few threads that discuss this question, but they all draw a different conclusion.
This one for instance : http://forum.xda-developers.com/showthread.php?t=1367933 (or if the link is broken, search for : How can i use cf-root kernel for cm7?).
In the thread above they claim that CF-root is not compatible with CM7, however in this very thread there is said that when installing the .zip file twice, it should work just fine. As i'd like to install CM7 on my CF-rooted S2, i have to know for sure:
Is there a way to install CM7 on a CF-rooted device?
Many thanks
Rom manager doesnt work with cf root, so to flash cm7 download the zip, boot into recovery, and flash the zip twice, and it will work.
Make sure you wipe data and cache, and take backups before you do.
Sent from my GT-I9100 using Tapatalk
Ok, i'll give it a go .
Thanks for the quick response, it is much appreciated!
I have a rooted TMo Vibrant running 2.1. I want to install a custom ROM and have the paid version of ROM mgr installed. I have downloaded the new ROM and I also have a (separate) zip of a different ROM on the SD card. The beginning steps of the installation go smoothly. But when I get to the point where ROM mgr says "Do you want to go into recovery mode to continue installation?" and I Select YES, the phone reboots into NORMAL mode and the installation ends. Same thing happens if I try to install manually from the SD card. I scroll down and select "install zip ...". Then the next screen that pops up has "reboot", " delete data", "reinstall packages", etc . I have tried all those options. But ultimately I end up back at the point where the only option I haven't chosen is "reboot system now". When I select reboot, the phone reboots in normal mode again. What am I doing wrong?
Not sure if this is your problem, but sounds like you need clockwork mod recovery update.zip on your phone.
Here is the trick though, when you get into normal recovery, sometimes you have to apply the cwm recovery update.zip TWICE to get into cwm recovery.
Boot up phone into stock recovery
apply the cwm recovery update.zip
phone reboots into stock recovery again
apply the cwm recovery update.zip again.
Hope that helps.
I would suggest doing this.
First and foremost make a nandroid backup, you can use cwm to do this. place a copy of the backup on your computer.
Backup your /efs folder which contains your nv_data.bin and imei information. You loose this you are f*cked.
Get the cwm recovery update.zip and put it on your internal sd root. If you have multiple update.zip files, just delete them all, just make sure the cwm recovery update.zip is there.
Also place the zip file of the rom onto your internal sd root also.
Disable voodoo lagfix if you have that installed.
Odin back to stock jfd 2.1. When finished next..
Apply cwm recovery update, apply TWICE to get into cwm recovery.
Then you can go into cwm recovery and select the zip of the rom you want to flash.
Follow all install directions of the ROM developer, they may want you to be on 2.2 first, which would mean odin to stock jfd 2.1, flash stock 2.2, then install whatever rom you are trying to.
That is how I do it.
I have a question about Clockwork recovery and this phone. Above you say that if any .zips are on internal sd to delete them and leave CWR on there only. I have this. Then if we want to go into the CWR we have to apply the update.zip twice. I do this also. Why can't we just replace the stock recovery with the Clockwork one and bypass the having to reinstall the packages twice. Maybe an sh init_hijack or something like that. I have been trying to find where the stock recovery "lives" to no avail. If you know where it is, then I can work on this and post the results.
Seems reasonable that if we replace the stock files with the CWR files and hijack the rocvery at boot it should work to boot right into CWR directly.
Woodrube said:
I have a question about Clockwork recovery and this phone. Above you say that if any .zips are on internal sd to delete them and leave CWR on there only. I have this. Then if we want to go into the CWR we have to apply the update.zip twice. I do this also. Why can't we just replace the stock recovery with the Clockwork one and bypass the having to reinstall the packages twice. Maybe an sh init_hijack or something like that. I have been trying to find where the stock recovery "lives" to no avail. If you know where it is, then I can work on this and post the results.
Seems reasonable that if we replace the stock files with the CWR files and hijack the rocvery at boot it should work to boot right into CWR directly.
Click to expand...
Click to collapse
Well with MiUi and CM it goes directly into clockwork mod recovery. I guess that's the stock recovery on MiUi and CM.
For me, only on 2.1 and 2.2 roms did I have to apply cwm recovery.zip twice.
SamsungVibrant said:
Well with MiUi and CM it goes directly into clockwork mod recovery. I guess that's the stock recovery on MiUi and CM.
For me, only on 2.1 and 2.2 roms did I have to apply cwm recovery.zip twice.
Click to expand...
Click to collapse
I have not used either for this phone but have with other phones and I think that it is b/c they reworked the services and framework.jars into an expanded power menu. I will see it that hack works on this one, so it will be easier on 2.1 and 2.2 for "relative" noobs. I have done it once for another phone and then my computer crashed (not issue related). I'll let you know what I find out this weekend b/c it'll take some time to get the pathways correct.
I appreciate you quick replies and have taken the first part of the advice and tried to backup everything (Which I thought I did using CWM). Just to be safe I have now installed Root Explorer and will back up everything this evening. Can't do more right now. Need to get back to work. Wayne
That did it. I now have my new ROM installed and a back-up of my efs file (which I mistakenly thought was included in my Nandroid back-up). BTW my nandroid, back-up produced by CWM doesn't include a boot image (or at least there is no image called "boot"). I thought there should be a boot image. In any case, I'm finally over the problem I've been trying for days to overcome. Thanks sooooo much. Wayne
I'm having a lot of trouble deleting install-recovery.sh. As many of you know, this resets the Android recovery, flashing the stock recovery over the Custom CWM-based recovery that I had. I'm trying to install Ubuntop.
I very well know I could simply install it once, install ubuntop, and go along on my merry way, but I need CWM for piece of mind, access to my backup, etc.
According to Romracer's post:
[quote user=mrinehart93]The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it.
Rename or delete the file and the CWM should stick.[/quote]
I've tried Terminal Emulator with root access, a root file explorer, everything. Unless theirs some hidden ADB method.
I also know I could get rid of this problem by installing a custom ROM.
However, I'm not so in tune with all the ROMs and kernels like I was with my EVO.
Any type of solution that doesn't involve me changing my stock ROM and kernel is appreciated.
If their isn't a solution, point me towards a nice deodex'd ROM. Please no undervolting/overvolting/OC'd stuff. Thanks~
To any of you wondering, I fixed it by installing Alien ROM.
To anyone who may fall into this problem later: Download This.