my phones 3g stopped working 1 day after i flashed a new rom so i tried flashing it again and that didnt work so i am trying to go back to stock with the how to return to stock guide on here but i cannot get my pc to recognize my phone in downloading mode
i can adb when its on and the drivers are installed but when i boot into downloading mode it just says device is unrecognized
i have tried a different computer and reinstalled the drivers more times that i can remember. what would be the next step here?
is there anyway i can start fresh even if i lose root?
There needs to be a q&a section.
The drivers suck.
What os are you using. Persistence will be your friend. Don't forget to power cycle everything.
im using win 7 64bit
The win 7 drivers are actually vista drivers if I remember correctly.
Which Odin arevyou using? Do you have clockwork?
i have tried 1.0 and 1.3 nothing works. and yes i have clockwork thats how i install my roms.
xtkxhom3r said:
i have tried 1.0 and 1.3 nothing works. and yes i have clockwork thats how i install my roms.
Click to expand...
Click to collapse
noobnl said:
1. boot into clockworkmod recovery
2. apply http://www.sdx-downloads.com/devs/noobnl/stock.epic.DI18.rom.update.zip
build 2 fixes wifi/bluetooth
older build
http://www.sdx-downloads.com/devs/noobnl/stock.epic.DI07.rom.update.build2.zip
Click to expand...
Click to collapse
I believe this flashes stock through cwm
Edit: read that thread I am not on the computer...
You should be able to flash two field and be good to go.
Good luck op
that post looks very very familiar i think i have tried that or maybe i was going to and never got around to it... ill do it right now ill keep you posted. thanks for your support man
xtkxhom3r said:
that post looks very very familiar i think i have tried that or maybe i was going to and never got around to it... ill do it right now ill keep you posted. thanks for your support man
Click to expand...
Click to collapse
yellowxboy said:
any chance of the original epic Rom? the one that came with the phone prior to DI07? i used Oden to rever to stock and then applied the update (DI07) but Android Market is not working (i'm guessing corupt (g)Talk file).
Data Wipe + Clear Cache did not seem to help when in clockrecovery, the android market wont let me download anything
Click to expand...
Click to collapse
this looks like the other file that you will need.
apparently the first one writes system the second for the modem (phone/data)
lmfao your gonna kill me for this but as soon as i finished transfering the file to my sd card 3g just started working.... maybe it was just a glitch with my signal over here? im going to let it be and if it messes up tomorrow then i will flash that stock rom and see what happens...
incase it doesnt work where can i get that 2nd file and how do i install it?
This post here.
Ok so I need to find a way to some how put my custom rom back into my phone i formatted my SD and now the phone wont pass the Google bootup screen not the system bootup screen just the one that says google and has a unlocked symbol on the bottom. please help me I'm not new to working with this stuff but this is the 1st time this has actually ever happened and I've been looking threw the forums and have came up empty handed.
ChucCTaylor said:
Ok so I need to find a way to some how put my custom rom back into my phone i formatted my SD and now the phone wont pass the Google bootup screen not the system bootup screen just the one that says google and has a unlocked symbol on the bottom. please help me I'm not new to working with this stuff but this is the 1st time this has actually ever happened and I've been looking threw the forums and have came up empty handed.
Click to expand...
Click to collapse
Assumptions: You have a custom recovery installed.
With the phone powered off, press the power button and volume up at the same time. Select recovery. Hook your phone up to your computer. In recovery, select "mount usb storage". Copy whatever ROM you want onto your phone. Unmount usb storage. Flash the ROM just you just copied over in recovery.
Thank you so much! it worked!
ChucCTaylor said:
Thank you so much! it worked!
Click to expand...
Click to collapse
Nice, glad it worked.
Wow yuur nice I would've never ever thought of that
irishrally said:
Nice, glad it worked.
Click to expand...
Click to collapse
brought to you by my iced out ns4G
=P edit topic with (Solved )
-Google
I apologize if there actually is a thread explaining what I am talking about. But I have searched all over. And I just can not figure it out.
I have the Dandiest ROM
http://forum.xda-developers.com/showthread.php?t=881937
I am using v4.31.44.12
It's my first rom flash, everything went fine and all.
The problem is that everything goes much too slow. Booting isn't an issue. but Everything regarding apps and calls and such just goes really slow.
When I get called, I can pick up. but I can't hang up because the phone just freezes.
Every app I install (which always takes roughly 3-5 minutes per app, after download) I have to constantly wipe the screen to keep it awake, if the screen sleeps during install, the phone completely freezes and I have to pull out the battery.
I wonder what is causing this, and if anyone has/had this problem before on a different ROM?
I have ext4 on my SD, shared storage or whatever it is called.
I have read some stuff about speeding that up or something, but I don't understand it.
I'm thinking it has to do with that. I installed/done everything following tutorials, so I should've done everything right.
Basementnugget said:
I apologize if there actually is a thread explaining what I am talking about. But I have searched all over. And I just can not figure it out.
I have the Dandiest ROM
http://forum.xda-developers.com/showthread.php?t=881937
I am using v4.31.44.12
It's my first rom flash, everything went fine and all.
The problem is that everything goes much too slow. Booting isn't an issue. but Everything regarding apps and calls and such just goes really slow.
When I get called, I can pick up. but I can't hang up because the phone just freezes.
Every app I install (which always takes roughly 3-5 minutes per app, after download) I have to constantly wipe the screen to keep it awake, if the screen sleeps during install, the phone completely freezes and I have to pull out the battery.
I wonder what is causing this, and if anyone has/had this problem before on a different ROM?
I have ext4 on my SD, shared storage or whatever it is called.
I have read some stuff about speeding that up or something, but I don't understand it.
I'm thinking it has to do with that. I installed/done everything following tutorials, so I should've done everything right.
Click to expand...
Click to collapse
Have you dont the following ? its in his main post . it seems like what you are experiencing is common .
1.. DON'T expect it will work out of box.
2. DON'T expect it will be as light and fast as Gingerbread.
3. DON'T expect that some legacy problem will disappear
4. Reboot your phone at lease twice after flashing or installing, after 1st boot into setting screen, long press the right button to recall the boot menu, reboot. Can not use /Update_DL method to install app before 3rd reboot.
5. For this version, due to the base has been changed throughly, can not use previous data.img or ext4, remove existing data.img and set data_img=1 to let system generate one for you, or set format_ext4=1 to format your ext4 if you are using ext4
6. DON'T set any config for 1st installation except data_img=1(for data.img) or format_ext4=1(for ext4 user). if your have tmous phone, no need the config.txt.
7. For SD or magldr, if 1st installation failed, must delete the system.ext2 file under /Desire_DL to let system convert it again.
8. Use Windows notepad create a file named config.txt, save it under /Desire_DL, only need to put the necessary config inside it, say:
data_img=1
Click to expand...
Click to collapse
My advice go here http://android.hd2roms.com/ and pick a rom without issues like hyperdroid 5.8.0. Leave ICS alone for a while.
No offence intended to Dandiest but his last post was months ago
shanman-2 said:
My advice go here *Link* and pick a rom without issues like hyperdroid 5.8.0. Leave ICS alone for a while.
No offence intended to Dandiest but his last post was months ago
Click to expand...
Click to collapse
Thanks, It was my first rom I flashed, almost bricked my phone in the process, so I'm scared to flash again. haha.
elesbb said:
Have you dont the following ? its in his main post . it seems like what you are experiencing is common .
Click to expand...
Click to collapse
I'm not sure what I'm supposed to do.
Basementnugget said:
Thanks, It was my first rom I flashed, almost bricked my phone in the process, so I'm scared to flash again. haha.
I'm not sure what I'm supposed to do.
Click to expand...
Click to collapse
Read what I've quoted and follow . Like reboot a couple of times and such things as that . And this is an sd build correct ? From the link provided that's the impression I got .
Sent from my HTC HD2 using Tapatalk
elesbb said:
Read what I've quoted and follow . Like reboot a couple of times and such things as that . And this is an sd build correct ? From the link provided that's the impression I got .
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Oh, I'm sorry. I'm using NAND. I'm using the NAND version of the Dandiest.
Also, I've had this rom for like a month now.
There are plenty of guides out there, get the nand toolkit (it simplifies things a lot,thanks to ksubedi). Read the guides carefully !!
Have a look here...
http://forum.xda-developers.com/showthread.php?t=1402975
http://forum.xda-developers.com/showthread.php?t=929324
Best of luck.
By the way have you tried a factory reset.. if you can back up your apps and data this might solve your problem!!
Basementnugget said:
Oh, I'm sorry. I'm using NAND. I'm using the NAND version of the Dandiest.
Also, I've had this rom for like a month now.
Click to expand...
Click to collapse
Ohh well that changes a lot lol . was it laggy since day one ?
I purchased a Nook Color about a month and a half ago and have been running CM 7.2 from the SD card ever since. I love it and am ready to take the plunge and put it on the device itself without running it from the card. With that said, I settled on Kang's ROM because of what others have said about it.
However, I am running into a problem when trying to start the root process...
I've tried using uNooter, Auto-Nooter and the Size-Agnostic nooter all with the same outcome. I'm placing the image on the SD card properly, because I can put Kang's ROM on there and install it to the SD card just fine. My issue is that when I follow the instructions on the CyanogenMod Wiki, I get stuck between "Gaining Root Access - Step 5" and "Install a Custom Recovery Image."
I get the driver prompts on the desktop and cancel them as instructed, then the NC just sits there; no boots, no reboots. So I pull the card out as instructed and power it up. There is no "Extras" option in the NC, so I can't go to ROM Manager and install ClockworkMod Recovery and go from there. It seems as if the nooter isn't working as intended, or I missed a step somewhere.
Any help is appreciated, otherwise I'll just continue to run it off the SD card.
Give the method in my sig a shot. Let us know.
Sent from the Center of My Mind
Many thanks, MISRy. This was pretty much a summary of what I had seen across multiple threads. My issue was with steps 4 & 5. It would not boot into Clockwork Mod Recovery no matter what I did.
Then I found the answer, and it made me feel sorta dumb I was supposed to hold down the power button with n until it booted.
I'm installing Kang now as I type this...
derekr44 said:
... I'm installing Kang now as I type this...
Click to expand...
Click to collapse
Woot!
derekr44 said:
Many thanks, MISRy. This was pretty much a summary of what I had seen across multiple threads. My issue was with steps 4 & 5. It would not boot into Clockwork Mod Recovery no matter what I did.
Then I found the answer, and it made me feel sorta dumb I was supposed to hold down the power button with n until it booted.
I'm installing Kang now as I type this...
Click to expand...
Click to collapse
Not a big deal, but just for clarity "Kang" just means "unofficial cyanogenmod build." There's nobody named "kang" (that's what your first post suggests). But yeah, we've all been there. All the complex stuff we breeze through only to spend a half hour missing the super-simple instruction. Good luck!
Whaddaya mean there's nobody named Kang?
So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
joeski27 said:
So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
Click to expand...
Click to collapse
Nobody has a suggestion? This isn't looking good...
What is strange to me is, even after doing another factory reset, it still boots to the same CM boot screen and is stuck in a boot loop. I have no idea what is going on here. And at the very least, at least I have everything still on my SDcard (backups of apps in TB, and all my other locally saved stuff...just that now I have no idea of how to get to any of it, or how to load on a working rom & gapps so I can have something to boot to!)
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
exb0 said:
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
Click to expand...
Click to collapse
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
joeski27 said:
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
Click to expand...
Click to collapse
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
exb0 said:
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
Click to expand...
Click to collapse
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Ah, it shouldn't matter that much. Instead of CMD just use terminal(that's what it's called in OSX right?).
didn't work? what error did you get?
joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
joeski27 said:
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
Click to expand...
Click to collapse
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
exb0 said:
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
Click to expand...
Click to collapse
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
joeski27 said:
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
Click to expand...
Click to collapse
sounds like a driver issue. You're gonna have to fix that or there's almost no way of fixing your phone :/
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.'
By the way when a sideload is performed where is the sideloaded file saved? Just wondering where to find it when the time comes to flash.
joeski27 said:
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Click to expand...
Click to collapse
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
joeski27 said:
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.
Click to expand...
Click to collapse
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
exb0 said:
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
Click to expand...
Click to collapse
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
joeski27 said:
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
Click to expand...
Click to collapse
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
exb0 said:
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
Click to expand...
Click to collapse
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
joeski27 said:
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
Click to expand...
Click to collapse
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
exb0 said:
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
Click to expand...
Click to collapse
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
joeski27 said:
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
Click to expand...
Click to collapse
No problem as long as you're willing to learn I'm willing to help! if you ever run into any other problems feel free to PM me. I'll try to help as much as I can. :good: