I've been flashing roms and kernals from about five months and never had a problem til now. I was running CWR v2.5 orange. Today I flashed Imnuts 0523 _50_vodoo kernal which changed me to CWR v3.0.2.8 which is yellow (I've neve seen that before) Now the phone is stuck in recovery I'm getting error messages E:can;t mount/cache/recovery/command. E:can't mount/cache/recovery/log. E:can't open /cache/recovery/log. E:can't mount /cache/recovery/last_log. Also I can get into download mode but now my computer is not seeing my phone however the drivers are on it. PLease help as I am out of options. Thx in advance
Try heidemall or what ever it is called. Also try another computer
Sent from my heinz57 mesmerize
Fixed
Thx I got it fixed. Not sure why but Odin finally worked Thx again.
In this case you have to Odin back to something else. The problem is that scripting for some rom/kernels are not compatible with others, the whole ammend and edify thing. And there are a few meant to work with both but in any case sometimes a rim or kernel won't play nice with others, so just Odin back, make sure rom and kernel are compatible and try again.
Also if tour machine is not seeing your phone, first try a reboot of machine, don't forget sometimes the easiest fix is the right answer. If that doesn't fix it then start looking at drivers.
Sent from my SCH-I500 using XDA Premium App
Thx I'm aware of the different recoveries and edify/amend I had never see a yellow recovery and normally I'd just get struck in a bootloop. Now for so reason my computer seeing my phone is hit or miss, and my phone no longer ask to connect in the notification bar, (and yes I have debugging on) other than that phones is working fine now. I may Odin back to stock and start over to see. Again thx for the info
try navenrobs formaters they picked my phone up compared to even voodoo
Related
So...I welcome all the NOOB comments but in reality I'm hoping to learn from the wise ones in this field. I bought a Dell streak for learning purposes (own an MotoAtrix) so that I can really get behind the weels of learning android the meant it was meant to be FREE so here's my problem so far with with the dell streak. Since it got updated to the ATT 2.2 build 353 it has been restarting on it's own any time after 4-6 mins of real usage. I can leave it on it's own charging or just on standby and no issues but it freezes and resets itself to then hang on the Dell Logo before the colorful Dell Logo. Now here's the steps I've tried to resolve. like i said I want to learn not a solution to my problems.
I tried first the simple get in and reset from the Settings screens. reset still issues.
Then I tried a hard reset and still issue.
3.) I tried uploading the "Update.pkg" and then it tells me Update.pkg.dec out of date error 7....resets back to 2.2
after 5 mins of usage resets on own and hangs on dell black and white logo.
keep in mind sometimes the hang is so big I have to do a battery pull for at least half hour to get it back (makes me think that there's something going on with flash memories sort of like bios on a main computer)
replace battery restart and back to 2.2 reset okay tried to root with superoneclick 1.7 and it gives me this as I tried to root...and keep in mind I've tried both way trying to get the password first and then doing the super rage root.
GET UNLOCKED CODE SCRIPT
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Preparing to copy nv_data.bin to sd...
OK
Copying nv_data.bin to sd...
/efs/nv_data.bin: No such file or directory
OK
Pulling nv_data.bin...
OK
Reading nv_data.bin...
Unlock Code: OK
then I went ahead and tried to root.....and got this message...
so no luck still having issues reseting..so I went on to the next step...MULTIFLASHER RECOVERY TOOL v.08 wich by the way is super sweet for someone to come up with this....but I do this still (SR #11) option and still once it resets it hangs in the Dell black and white logo screen. I guess another half to an hour battery pull. Hopefully I've given enough info or detail for someone to guide me in the right direction. as the next step from this is getting more android devices to root and modify to learn the process better before I start hopefully someday writing my own rom. Thanks Everyone!
Read this post all the way through:
http://forum.xda-developers.com/showthread.php?t=1292859
Basically, flash the recovery for a stock rom, i.e. 354
upgrade from update.pkg
See if this fixes your issue.
Going to try this as it has been sitting on standby with out a battery for about an hour now so hopefully it will start no probs will post results from there. Thank You Much will reply once I have results in the AM
UPdate...
SO I tried your suggestion and I'm stuck at the point of adding the Drivers manually, (which may be the reason why flash and the rooting didn't work to begin with since it's not recognizing the device in the port that is connecting to. I've tried all 4 ports on this toshiba but guessing that I'm running a 64 OS also may be the reason for the issues. but I've tried adding the Qualcom HS USB Diagnostic device 9002 and I get the following error.
Driver is not intended for this platform and for some reason it always wants to assign driver for Qualcomm Diagnostic device 1937, if you know the manf of your device please contact ... yeah right like DELL will know how to fix this issue. So once I hit close it just gives it a Com14 or Com# depending on what port is plugged in.
64-bit OS has nothing to do with it, since I can successfully run Fastboot commands on my 64-bit Windows 7 laptop without issues.
I believe your best approach is to intall Dell's sync software from Dell.com if you haven't already done so. That has the proper drivers for the Streak as well as creating the registry entries for the drivers. Once installed you actually can uninstall the sync software if you wish and the drivers will remain.
After that, do NOT run SuperOneClick or ANY one click rooting solutions. The recommended procedure is to copy Superuser.zip to the external SD, then flash Streakmod Recovery. Complete instructions and the Superuser.zip file can be downloaded here. Too many issues have been caused by one-click solutions, while the Superuser.zip/Streakmod Recovery method works flawlessly.
reinstalling the sync method...
I had already installed the sync software from dell and it was not connecting before I tried all the other methods I even tried reinstalling and have the program try to self fix install errors. So I'm going to uninstall completely and then reinstall see if that works. off tomorrow so i'm going to be burning the midnight oil to get this fixed am i crazy to think this is fun...? or is it the nerdiness in me that finds the challenge of restoring a hanging on a dell logo unstable 2.2 on a dell streak fun?
If I read correctly on the link that you posted, in order for me to do the streakmod recovery, I must have the streak rooted, now here's a problem with that since the computer hasn't been able to install the drivers I haven't been able to root the streak, and it keeps reflashing itself at boot to stock recovery so I don't get custom recovery boot. I will keep trying and post any updates or resolved issues in the hope that this can also help anyone out there. Thanks for all the imput I appreciate it!
Chamo4u2 said:
If I read correctly on the link that you posted, in order for me to do the streakmod recovery, I must have the streak rooted, now here's a problem with that since the computer hasn't been able to install the drivers I haven't been able to root the streak, and it keeps reflashing itself at boot to stock recovery so I don't get custom recovery boot. I will keep trying and post any updates or resolved issues in the hope that this can also help anyone out there. Thanks for all the imput I appreciate it!
Click to expand...
Click to collapse
Rooting and custom recovery are two separate things. You need a custom recovery to root using superuser.zip. You said it keeps rewriting the recovery when you reboot. I take it you have been able to flash recovery on it? If so, flash StreakMod again and instead of rebooting, pull the battery when finished. Put the battery back in and hold the volume keys (both) while powering on the device. Choose option 2 and you'll boot into streakmod. From there you should be able to flash superuser.zip and/or a custom rom. Note: Nearly all, if not all, custom roms are prerooted.
If you have flashed a custom recovery, what makes you think you have driver problems?
well...I tried the Multirecovery tool to try to get the Streakmod recovery on but when I tried to retry to load the streakmod.zip I couldn't get the other files on the sd but only the option to load from .pkg so I was under the assumption since I couldn't get the custom flash tool to read the zip i wanted to load that it didn't work. but here I go again. another thing I'm trying to start fresh I just formatted the sd card and I'm going to start fresh. will update once I try the next step. Going to load the right files onto sd then streakmod with multirecovery tool and then try to boot into streadroid by pulling the battery out and not letting it self reboot.
Under the advanced option in streakmod is an option to mount your sd card. Choose it and your sd card will appear in windows explorer.
You do not have to have root to flash and use StreakMod - you do have to flash it and then either reboot using the fastboot command and go right into recovery mode or do a battery pull and restart.
some reading:
Using StreakMod
Prevent overwriting of custom recovery
So...update...I tried to multirecovery tool option 11 Streakmod recovery in fastboot mode it kept giving me this message cant upload/admin user/... then it would proceed to succesful... so thinking that it successceded so I figure lets try this one more time load from sd update.pkg
message given was...
Assert failed: !less_than_int(1297160324. getprop("ro.build.date.utc"))
E:Error in /sdcard/update.pkg.dec
(Status 7)
E:Can't mount CACHE:recovery/log
E:can't open: recovery/log
it restarted gave me the good ol white and black dell then the multicolor flash and then hanged on the white dell logo for 10 mins before i decided to pull the battery and see what now.
UPDATE: i did a battery pull for 20 mins restarted and it finally booted into froyo 2.2 (att rom) hmmm...? now to finally root to a more stable and better rom let the rooting and modding begin! hopefully this wont be an issue still wondering why it said error on this and status 7 anyone?
here's the problem with doing that. Something is putting such a drain on the phone that by the tim i have to boot if I don't give it a good five to ten mins to reset when I do reset it hangs on the dell screen or when I try to boot into a flash recovery mode it only gives me the stock recovery screen....? confused at this point where to go from this point. but if I have to brick I have to brick and rebuild again here's the current numbes.
android version 2.2
baseband version GAUSB 135331-US
Kernel 2.6.32.9 perf
OEM version GAUSB 135331
Build 15697
without touching it or using any features that would use the GPS it hasn't reset for over an hour 1:45 time on to streak mod preferably something more stable than the ATT Rom
I tip my hat to you. I am happy to see someone wanting to genuinely learn how to mod their streak without being spoon fed every answer. I have been getting sick of seeing all the incompetencies on the Streak forums. Thank you for brightening my evening with your desire to learn.
Good luck in your Streaking endeavours.
Sent from my Dell Streak using XDA App
Only way to learn is to actually do something...you can't learn to fly if you don't jump, but I'm pretty sure that when people slam into the ground I'm sure they had more imput on how to stay in the air longer or eventually to not slam back into the ground...Question if I change the rom that I put in the sd card and relabel it as update.pkg with the stock recovery will that give us bad results aka as BRICKING the phone my question really is the rom more like the OS on a pc system and the recovery more like a bios?? reason why I'm asking is this streak is so unstable at times that I have to do battery pulls for hours before I can get a full restart. So I wanted to load a rom in there and restore from update.pkg but start with a rom that doesn't use as much system such as 1.6 to see if the reset comes from having a 2.2 that from what I've read ATT never tested enough to send out. to see if I could actually use it or if it's hardware causing all the restarts (guessing a bad internal sim) from what I've read. And thank you to everyone's imput that has made me learn a ton about this device. hopefully someday I can use it as my main device but working in a market where I'm required to have a working cell for straight 9 hours means I'm pushed to the awesome atrix wich I have to say it's a tough lil phone. Again thank you and to streaking I go!
so the Streak has gone streaking...
Apparently is not what we were doing wrong but we really had a bad streak The cpu was overheating anytime it had real heavy load on it and it will shutdown and reset over and over and over as it kept restarting everytime it needed to cool down so DELL AMAZINGLY HAS STEPPED UP and sent me a replacement device! since the STREAK is no longer being replaced they are sending me a Venue HEY I could complaint but the fact that it was out of warranty and they are doing everything in power to replace the unit wich should arrive soon is the only reason why I'm not continuing on working on the streak but!!! streak and Venue look like they are carrying the same software so ON TO A MORE RELIABLE PHONE AND MORE LEARNING THANK YOU FOR EVERYONE AND THEIR IMPUT! I can't wait till I have a flashed Rom at work and people say WAIT MY ANDROID DOESN'T DO THAT! SO ON TO LEARNING OTHER THINGS BY READING! ANY GOOD GUIDES TO READ OVER ALL PLEASE PLACE YOUR " YOU SHOULD READ THIS TO LEARN MORE ABOUT THE WORLD OF ANDROID DEVELOPING"
I've tried to look for this problem and haven't found anything similar. If it's already been addressed please direct me to the previous thread, if this is in the wrong place please move it.
I rooted my Galaxy S II a while ago and it's been working great. I wanted to try Cyanogen mod 7 and so I followed the instructions on their website. Trying to use ROM manager gave me a weird error message telling me that there was an invalid signature or something, despite toggling everything and wiping the cache to turn it off. So I followed the "method via recovery" instructions. I did everything exactly as it is there, including the Google apps stuff, and it all seemed to work perfectly. Then I rebooted it hoping for it to boot into CM7, and instead, when it turns on it goes to the screen saying Samsung Galaxy S II with the yellow triangle underneath, and stays there. Every time it turn it on it goes to that screen and doesn't change. It's now been like that for half an hour. I can start it up into download mode, and I've tried flashing zImage to it again, but no change.
I have a NANDroid backup (it's backed up with CWM anyway), and I've copied the backup to my computer, but I have no idea how to apply it when the bloody thing won't turn on.
I'm using Linux with Heimdall (the cross-platform Odin clone).
Please help me. Unfortunately I have no internet in my flat so I won't be able to see any advice until tomorrow unless it;s given in the next ten minutes. God I really hope the thing's ok.
Hi
Do you have jigg? ( if you don't have it buy it from ebay or ask some friend of you )
With jigg you can enter download mode and then flash the stock rom.
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Sent from my Transformer TF101 using xda premium
TheGhost1233 said:
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Click to expand...
Click to collapse
I can't believe it was this simple, I knew power+vol-down+home got tme to downloading but I didn't know that got me into recovery. Everything's recovered now.
Thank you Dutch people!
I have a fascinate and have successfully rooted it, flashed the cricket info (i got talk and text) and had 3g at one point. All of the sudden 3G went out. I put CYANOGEN on there, latest 7.1 i believe for the fascinate.
Upon trying to revert back to the original ROM so I can get in there with PST and CDMA WS, I encountered a very strange set of problems and now I am just stumped. I tried to ask a couple of other people and no one seems to know what is happening.
Here is what happens, I try to put the original ROM on there, by using ODIN and doing the atlasv2.2 pit file, and the original ROM, froyo, and the other one eclair i think.
When I use odin it gets to the system part, then right after it goes to the part that would take the longest, and I forgot what its called, dataFS? it has FS at the end, and then the phone (while odin is still going) will go to either a blue screen or a green screen with no words. If you look closely, it appears there is a clock at the top right just like if the phone was on.
I have not overclocked this device at all so thats one thing that can be ruled out.
I've tried odin using both battery in and battery out method as different guides have stated different things. When the battery is out, I get a blue screen. When its in, i get a green screen.
The screen appears right after the normal odin screen, with the status bar, but it will dissapear when it comes to the dataFS part (right after system) then it will take about 20 - 45 minutes and I will get an error screen on odin.
Funny thing is i've used odin and that method and it worked the last time. It works fine if I need to flash a clockwork recovery. However, upon booting into recovery, half the time I will get an error that has to do with BUILD.prop and SCH-I500. This is when I try to flash any rom except MIUI. For some reason, MIUI kicks this phone around and its the only rom that works. CM7 wont work, stock won't and every other rom wont.
So, to sum it up, my main problem is ODIN and its funky behavior, and not being able to go back to stock so I can see if my 3g settings are correct. If you have any information, even if its just something to help get my wheels turning, then please post it up, any and all help is greatly appreciated folks, thanks.
I dont know if this would work but if u think the problem is Odin then I would uninstall odin and reinstall the newest version available. Also, make sure the phone driver software get done the same.
Then after that I would try odin again. Phone off, battery out. Open odin. Plug in usb. Make sure phone set usb to debug. Hold vol down button. Odin should see your phone.
Im sure u know all the steps up to this point but try again.
Good luck
Or u can try running odin as Admin on the comp.
Also if the problem persits I saw a user had a similar problem and of turned out to be his usb cable so try a different one if you can't fix it.
Sent from my ADR6350 using Tapatalk
See, thats what I thought too, but I will give it a shot and see. I doubt its the drivers, odin or the program, file or anything else because it does work with clockwork, and i've downloaded it several thousand times, plus it works great when I do anything but flash the original rom, odin will go fine. Drivers seem fine, it communicates and all that perfectly so I also highly doubt that.
I will get another cable and just try it on a whole different PC to see what happens. I was really hoping someone had this happen and had a fix but I might have to do some heavy delving. THANKS GUYS! I will try this and report back.
It was the cables, used a brand new USB cable and it worked, strangest thing that a cable can work but not work and its just a bunch of wires, but almost all my audio cables have to be bent or else you will loose a channel. I guess its just poor quality materials. So thank you, it works now and it was just the USB cables.
Hello Everyone, it's just sad that my first post on this forum had to be a frustrating one. First of all I would like to start off with a few general points that you guys should know before (commenting or raging at me):
1. My HTC legend was only purchased 3 months ago.
2. I HAVE looked around the forum for answers but I cannot seem to find a suitable solution.
3. My phone has already been rooted.
4. This problem has not occurred before.
5. I am in desperate need of help...
Anyway, I've recently rooted my HTC Legend (like 3 days ago) using this method http://forum.xda-developers.com/showthread.php?t=1223950&page=3 . Everything worked well and I was impressed with how smooth everything was going (flashed cyanogen mod 7 and OC'ed). However only just recently (like 3 hours ago) I connected my phone via the USB cord (provided by the phone itself) and the usual connection status where we can choose (Charge only, disk drive, sync etc) was not coming up. I pulled down the notification bar and nothing was there. Only the USB DEBUGGING sign was there. I tried rebooting my PC and my phone a couple of times but the connection status is still not coming up . I have also tried turning off and on USB debugging mode, re installing/updating SDK and HTC sync (but I doubt that's the problem because I could view the connection status before I downloaded SDK). For some reason there is no "Connection PC" thing that I was pretty sure the stock HTC legend had but I don't know if Cyanogen mod 7 removed that or something.
I went across this forum and tried many of the threads that displayed a similar problem (most were unanswered..). I hope that my USB is not bricked because I don't want to go through the tedious process of unrooting my phone and waiting for my phone from repairs. PLEASE CAN ANYONE HELP ME?!
If it would help: my pc can detect the phone but I cannot change to hard drive mode because the status isn't showing..... Damn this is annoying
Sent from my Legend using xda premium
Anyone?
Sent from my Legend using xda premium
With CM7, or any Android phone using a stock ROM, you have to select disk drive from the notification bar. With that said, in the case that that won't appear, have you tried changing ROMs?
There's also a way to nudge disk drive into working without changing ROMs, and I doubt it'll work, but it's always worth trying.
Reboot into CWM and mount the SD from there. That'll hopefully get 'er going.
Before I say anything, thanks for replying
Okay so what you're suggesting is what most people have been saying about this issue. The problem is that I don't know how to flash a different rom without using the computer
So of you wouldn't mind can you explain in clear (to the best of your abilities lol) how to go about that step? Sorry, but this is my first smartphone and I'm a noob this clockwork recovery thingy. Sigh, the weird thing is cm 7 worked perfectly for a few days (till I oced it).
Cheers
And how do you reboot to CMW? Is that recovery mode, cause if it is I can't do anything once it goes to that red triangle with exclamation mark thingy.
PS: And just in case I have resolve to flashing a new rom, which one do you recommend?
1st of all google that red triangle with exlamation mark thingie. Use these exact words... you'll see, it's amazing...
Sent from my HTC Legend
Don't mind it when people don't reply to your thread. It's a problem with the Legend not being as highly regarded this far into a smartphone's life.
When you get to the screen with the Android device and red triangular exclamatory point, you've reached the first step into booting into recovery. From rooting, an update.zip file should've remained on your SD card. If not, use it from ROM Manager. From that screen, simply press VOLUP + Power to reach HTC's recovery. From there, apply the update.zip from the root of your SD (it'll do it automatically), and you'll be booted into CWM.
Another method, and useful if you already don't have a different ROM loaded onto your external storage, would be to use ROM Manager: https://market.android.com/details?id=com.koushikdutta.rommanager&feature=search_result
From your phone, download a different ROM like you would on your computer, it's a smartphone after all! Leave the rest to the app. It will not only keep ClockworkMod Recovery up to date, but also provides a more simple interface to access basic recovery functions.
First of all I already have rom manager installed because it came with the CM 7 rom after I flashed it. What I don't understand is what update.zip you are talking about because I have one already on the root of my sd card (are you talking about that one). And do I need to do a nandroid back up before doing this procedure? And how do I mount the sd card from CMW lol.. soz FOR the noob questions.
EDIT: I just went to CM Recovery and mounted it onto my PC and pressed one of the options that says "mounts and storage" but when I do, all that happens is that the screen turns into the weird Hat logo with a dark background screen and nothing happens (I can't access the mass storage still). I pressed home which brought me back to my original CMW recovery page and I pretty much tried all of the options and it does the same thing WUT THE HECK! I don't know if its the version of my CMW (v5.0.2.0) or if its something that I'm doing wrong......
EDIT2: OMFG I was freaken pressing the power button to choose my options when I should have been pressing the scrolls button LOL *awkies*. Anyways, USB storage now shows up but what do I do now lol? Do I just reboot and the Mass Storage works again or do I have to reflash it (is it the same steps as flashing a new rom or are the steps different now?). Either way I'm glad that the USB storage still works thanks man I would have given you like a thousand likes or something but can only do it once lol.
Well problem fixed, just reflashed my Cm 7 rom and the USB storage is up and running again Thanks Asovse!
PS: MERRY CHRISTMAS TO EVERYONE READING THIS POST
Sent from my Legend using xda premium
Glad I could help!
Happy holidays, mate!
Hi everyone,
First of all, thanks for all the help/development done here, it is really awesome. I am new to rooting/rom so, I've spent a lot of time reading forum threads and looking at people's issues and it's been really helpful.
Yesterday, I spent all day trying to update my Bell Mobility Samsung Galaxy S Vibrant GT-I9000M from Froyo 2.2 to 4.2+
I sucessfully rooted the device, installed SpeedMod kernel(with Odin 3.04) and got CWM Recovery working when I restart the cellphone.
Afterward, I tried to update with different ROM(CyanFox, CM11, Mackay OmniROM...) but always got Status 7 error at CWM. So I figured I'd try to upate to a recent Kernel and installed GearKernel_JBPlus_Vibrant_1.0.3v.tar trought Odin. The phone got in an installation loop. Here is a poor webcam photo of the error(sry couldn't get better) : http://i.imgur.com/L3b0RmF.png. It says something like Estimating(?) volume for path [grep], Can't mount grep, Installation Aborted. Restart, splash screen, installation aborted, loop.
I had this loop at other occasions trying to update Kernel. The solution had been to put the cellphone in Download mode and reinstall Speedmod Kernel with Odin. This is what I did again.
It allowed me to get in Recovery mode but I couldn't go passed it. Attempt at restoring backup didn't worked. So I decided I'd go back to everything stock and followed this thread http://forum.xda-developers.com/showthread.php?t=1047087 and used Odin with the PIT and TAR files.
This got me in my worst position so far. If the cellphone is plugged, it loops between dark screen and the little "loading thingy" before the battery, but nothing more, no battery charge. If I try to open it without the plug, it display the GALAXY S GT-I9000 splash screen(which is weird cause I'm using I9000m) for a couple second then goes dark.. Then splash screen.. then dark... pretty quickly.
I can go in Download mode but I haven't succeeded to get in Recovery mode. I have adb on my computer but I haven't been able to call anything from it at the point I am.
I have found different threads showing different solution for various problems but I feel like I tried enough and I'd like to avoid bricking my cellphone so I decided I'd make my own post detailing the steps I took.
What should be my next step to get out of this loop? It seems like I only have Odin/Download mode to help me.
Thanks again.
If you have the gt-i9000m that is not the vibrant. The vibrant is the sgh-t959. Thats probably your problem
Sent from my Nexus 4 using xda app-developers app