Related
Ok, so here is the situation:
I rooted my Droid 2, no problem. You guys give very easy to follow directions, so kudos.
Things worked fine once rooted for a week or so, then I installed LCD Density changer. I put in the new density I wanted, it told me to reboot. Fine, I do so. Once I do it, it goes into an endless boot cycle.
My first thought was boot into recovery and do 'restore to factory defaults', so I figured out how to do that, and it 'worked'. But once I restarted, now it reboots with an LCD density of 90 (like I set in LCD Density changer); it takes me to the initial setup screen, works for 10-15 seconds, then reboots. I repeated the 'restore to factory defaults' and same thing.
I'm at a loss as to what to do! I've read about 'flashing' a recovery...can I do that while my phone is in its current state?
Thanks so much for your help, people!
I think you can flash your phone. I don't think you need to have your phone working to flash. Maybe just having it on?
phud1066 said:
Ok, so here is the situation:
I rooted my Droid 2, no problem. You guys give very easy to follow directions, so kudos.
Things worked fine once rooted for a week or so, then I installed LCD Density changer. I put in the new density I wanted, it told me to reboot. Fine, I do so. Once I do it, it goes into an endless boot cycle.
My first thought was boot into recovery and do 'restore to factory defaults', so I figured out how to do that, and it 'worked'. But once I restarted, now it reboots with an LCD density of 90 (like I set in LCD Density changer); it takes me to the initial setup screen, works for 10-15 seconds, then reboots. I repeated the 'restore to factory defaults' and same thing.
I'm at a loss as to what to do! I've read about 'flashing' a recovery...can I do that while my phone is in its current state?
Thanks so much for your help, people!
Click to expand...
Click to collapse
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
jcsugrue said:
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
Click to expand...
Click to collapse
You're right! This let me get access to the bootloader, and flash the recovery .sbf I found in another thread. I'm keeping my fingers crossed, but this seems to be working. Thanks for your help!
Update: Fixed!
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
phud1066 said:
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
Click to expand...
Click to collapse
No problem. Glad that my tutorial can help!
jcsugrue said:
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
Click to expand...
Click to collapse
I had given up all hope of restoring my phone until I read this. Thanks you very much
phud1066 said:
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
Click to expand...
Click to collapse
RSD lite would not work while I was in the bootloader program. It would get to 100% then would go into a second flashing of image file then it would fail. I am pretty sure I have bricked my phone, but still hanging on to it hoping against hope that I can fix it. I have tried almost everything, with the exception of using Linux. I don’t know where to get it or how much it costs.
I wound up having to buy another Droid 2 from the Verizon store here in town. :/
Sent from my DROID2 using XDA App
Terri M said:
I have tried almost everything, with the exception of using Linux. I don’t know where to get it or how much it costs.
Click to expand...
Click to collapse
Linux unlike Mac and Windows is basically free. Ubuntu is free to download. I dual boot windows 7 and Ubuntu 10.04.
Sent from my DROID2 using XDA App
ok, typically i've had no problems installing custom roms. i put rubix on here last night and really don't like it that much. well, my sd card crashed somehow also so i lost all my backups. so, i went into rom manager and was going to reinstall zapx. it went through all the functions and now i'm stuck on the rubix boot screen. it just keeps reloading... i was rooted with 2.2, so what do i need to do now? please help asap. i really need my phone today!!!!
edit:
ok so from looking around i've found that i need to flash the sbf file using rsd lite 4.8. ok so i dl'd rsd no problem. i dl the sbf file and click to open and it doesn't work. i tried to "use rsd" to open and still nothing... am i missing something on my pc to run this sbf file?
edit #2:
so i got the sbf file to run in rsd... install went good and fast. phone boots up to "welcome to droidx touch the android to begin", i touch it and nothing happens... just flashes. emergency dial won't work, change language does work... thats it... please help!!!
LAST EDIT:
got it figured out... was looking in the wrong place for the file... soooo, nevermind to all help... oh wait....................
brandon2x said:
ok, typically i've had no problems installing custom roms. i put rubix on here last night and really don't like it that much. well, my sd card crashed somehow also so i lost all my backups. so, i went into rom manager and was going to reinstall zapx. it went through all the functions and now i'm stuck on the rubix boot screen. it just keeps reloading... i was rooted with 2.2, so what do i need to do now? please help asap. i really need my phone today!!!!
edit:
ok so from looking around i've found that i need to flash the sbf file using rsd lite 4.8. ok so i dl'd rsd no problem. i dl the sbf file and click to open and it doesn't work. i tried to "use rsd" to open and still nothing... am i missing something on my pc to run this sbf file?
edit #2:
so i got the sbf file to run in rsd... install went good and fast. phone boots up to "welcome to droidx touch the android to begin", i touch it and nothing happens... just flashes. emergency dial won't work, change language does work... thats it... please help!!!
LAST EDIT:
got it figured out... was looking in the wrong place for the file... soooo, nevermind to all help... oh wait....................
Click to expand...
Click to collapse
I personally like it when I get to take both sides of the conversation. I usually agree with myself (usually).
Glad you figured it out.
yeah that was fun. i'm learning sooo much about these things. it actually makes me happy when i figure it all out on my own without having to wait on answers... after all the messing with roms and everything, now that i have the 2.2 ota sbf installed, i re-rooted and its running great. not sure i'll even put a different rom on anymore. no need really. i'm overclocked and i hit a 1665 quadrant score. rubix was great except the camera app. even with the 8mp fix on the cam and 720p fix on camcorder i just hate the way it doesn't use the widescreen effect like on the stock camera... thats my 2 cents about my situation today!
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
willjohnson said:
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
Click to expand...
Click to collapse
try here http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html#comment220 scroll down towards the end (idk if you use windows or linux but the linux method of sbf'ing is alot easier ive used both) except in their directions it says an older sbf file just insert the one you have, then go here http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html to download these zip files for kernel updater, 340 system update your baseband and bootloader should already be the correct ones, (i recently bought my X too) then once you finally root your newly sbf'd X and installed droid x bootstrap etc and get into clockwork mod recovery you can flash those 2 zips (recommend flashing only one at a time, reboot, and do the next) and then you should be updated to full .340
gl
http://forum.xda-developers.com/showthread.php?t=869007
heres a thread with discussion about those update zips
Thanks for the quick replies. Gonna try your suggestion tonight or tomorrow. Now i get random lock ups followed by a boot after about five minutes. The only upside right now is that its 4 days old so if i can get some resemblance of factory back on it then i can just exchange it Thanks again will report back with results.
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
willjohnson said:
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
Click to expand...
Click to collapse
correct tho the one i used had was labeled VRZ_MB810_2.3.32_1FF_01.sbf
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Ok, so now i am starting to worry. Tried 3 different .320 full sbf's. All the same result. Failed process close to the begging. Then on the phone it says
Critical Error
FEBE
0047
Please Helppppp. I don't need a really expensive paperweight, all i need to do is get it so that GummyJar doesn't show on boot and i can take it back, its brand new.
Try removing the battery. Then boot into recovery (volume down + power) then do a factory reset/restore.
Sent from my ADR6300 using XDA App
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
willjohnson said:
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
Click to expand...
Click to collapse
ive heard there are several problems with rsd lol thats why ive stuck with my ubuntu/Linux its 10x easier
willjohnson said:
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Click to expand...
Click to collapse
i also believe you DO have to have it all in specific locations but idk i use linux to do it, if you continue to play with the X after u get new one i would read up on how to dual boot ubuntu its a whole lot easier once you find ur way around i have it booting off of a 1TB external hard drive no need to install the correct moto drives etc..just plain easy lol
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
willjohnson said:
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
Click to expand...
Click to collapse
it only takes once correctly doing it to feel comfortable lol also make sure using droid x bootstrap recovery make sure to tap the first choice and let it do its thing, otherwise it will constantly reboot to recovery EVERY time you turn it back on
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
willjohnson said:
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
Click to expand...
Click to collapse
try something blurless like darkslide, which im currently running, no random reboots
Funnyface19 said:
try something blurless like darkslide, which im currently running, no random reboots
Click to expand...
Click to collapse
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
willjohnson said:
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
Click to expand...
Click to collapse
Well I haven't overclocked yet anyway the phone gets hot enuf lol plus coming from an Eris 1k is fast lol
Um yeah it should be wright depends on what the blur clock looks like lol
Sent from my DROIDX using XDA App
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
willjohnson said:
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
Click to expand...
Click to collapse
yeah but the obsidian rom is completely blurless just not everything working
Running DarkSlide4.1 can't tell u last I had a reboot
Sent from my DROIDX using XDA App
I had an older gingerbread leak, and decided to upgrade to a newer gingerbread leak. Well that is not where the problem came from. I stupidly decided to install the crt animation zip file. Turns out after reading comments it leaves you stuck at the M logo.
Any suggestions on SBFing back to froyo so I can get my gingerbread back on. I have RSDlite, but in the gingerbread bootloader it won't recognize my Droid X.
I was running the .595 Gingerbread leak and I was able to SBF back to Froyo with no issues whatsoever. Are you certain all of the drivers are properly installed on the PC?
Yeah they installed. I have SBF'd using RSDlite before, but what exactly do I need to do to do it from gingerbread. I can get to clockwork, and from there to the gingerbread bootloader, but once there my Droid X is not recognized.
Forget about Clockwork, just turn your phone completely off. Then press the volume down and camera keys while you press the power button. Release all keys after about 2-3 seconds. This should get you right into the bootloader and RSD should see your phone.
wwwilly1986 said:
Forget about Clockwork, just turn your phone completely off. Then press the volume down and camera keys while you press the power button. Release all keys after about 2-3 seconds. This should get you right into the bootloader and RSD should see your phone.
Click to expand...
Click to collapse
Ah yes, its comming back to me now. It has been recognized and is currently SBFing I believe. If I run into any more trouble I'll let you know.
Thanks
aquaurchin99 said:
Ah yes, its comming back to me now. It has been recognized and is currently SBFing I believe. If I run into any more trouble I'll let you know.
Thanks
Click to expand...
Click to collapse
No problem glad I could help
Just finished. Phone simply boots to bootloader screen like I went to to initiate the SBF.
OK if SBF has completely finished pull the battery to power off. Then press "Home" and power until you see the Motorola logo. Release power and continue to hold "Home" until an exclamation appears. Then release "Home" and press "Search" From the recovery menu you will need to clear cache a couple of times and then reboot and all should be well. Anytime you SBF from GBread to Froyo you will need to do this or you will get boot loops. Let me know if this works for you.
Thats odd. The logo is still red. I am now downloading froyo from http://www.mydroidworld.com/forums/...id-x-gingerbread-2-3-3-release-prerooted.html
Thats how I did it when I SBF'd a while back. For some reason I downloaded a different version from another thread. I will SBF that and see what happens.
aquaurchin99 said:
Thats odd. The logo is still red. I am now downloading froyo from http://www.mydroidworld.com/forums/...id-x-gingerbread-2-3-3-release-prerooted.html
Thats how I did it when I SBF'd a while back. For some reason I downloaded a different version from another thread. I will SBF that and see what happens.
Click to expand...
Click to collapse
Yeah try that Official 2.3.340 SBF and then boot into recovery after SBF'ing and clear the cache out. The SBF you previously used may have been corrupt somehow.
Okay it is currently SBFing. Once it finishes I'll boot into recovery wipe data/cached. Then I'll boot up and see how it goes.
I never thought I'd be so happy to see the Froyo "M" xD. Just booted up. Gotta root, then do the gingerbread stuff again. How can I get to .595 again? I do have the TBH app by the way. I just want to make sure I do everything right. Rooting with Z4root right now.
Well its activating right now.
Hmm said it didnt activate. Trying again.
Activated. Now going to root.
aquaurchin99 said:
I never thought I'd be so happy to see the Froyo "M" xD. Just booted up. Gotta root, then do the gingerbread stuff again. How can I get to .595 again? I do have the TBH app by the way. I just want to make sure I do everything right. Rooting with Z4root right now.
Well its activating right now.
Click to expand...
Click to collapse
Ok once it's rooted hop into the Market and grab Droid 2 Bootstrap (Not X)
Then go to http://www.mydroidworld.com/forums/droid-x-discussion/7047-droidx-gingerbread-2-3-3-4-5-588-install-patch-root.html and pick up the 3 files for the .588 leak and flash those in order. Once booted into .588 then go to http://www.droidforums.net/forum/droid-x-roms/136891-official-thread-gingerbread-leak-root-get-now.html and grab the .595 version that you want and flash that through the Droid 2 Bootstrap as well. You cannot flash .595 directly from Froyo or it will fail when flashing.
I thought by enabling USB debugging Droid X bootstrapper would work I believe. If I am not mistaken I used the Droid X bootstrapper to get from froyo to gingerbread in the first place, and from there I went to .595 back previously.
aquaurchin99 said:
I thought by enabling USB debugging Droid X bootstrapper would work I believe. If I am not mistaken I used the Droid X bootstrapper to get from froyo to gingerbread in the first place, and from there I went to .595 back previously.
Click to expand...
Click to collapse
I can't be certain. I haven't tried the Droid X bootstrapper but if it gets you into Clockwork then you should be ok.
I thought I had z4root on my sd card still. Gotta go download it agian.
Stupid computer keeps telling me its a virus and deleting it.
My dad amped up all the security things on here lmao. Just got it downloaded. Root time.
This is taking a while, though I do remember it taking a while when I first did it.
Sweet sounds like you got it.
wwwilly1986 said:
Sweet sounds like you got it.
Click to expand...
Click to collapse
Yup I think so. You've been a wonderful help, especially since its late here. I'm pretty tired, so remembering all these things you told me was not about to happen haha.
You are a life saver.
And to think all of this could have been avoided if I read the stinking comments below the crt animation thing. THis is such a waste of time haha, but then again, I gotta do it. We all make stupid mistakes sometimes.
Wow taking forever to root.
Edit: Rebooting my phone since it was taking too long. I heard that was a problem with z4root anyway. Time to try it agian.
Okay root is working. Time to move on to the next steps.
aquaurchin99 said:
Yup I think so. You've been a wonderful help, especially since its late here. I'm pretty tired, so remembering all these things you told me was not about to happen haha.
You are a life saver.
And to think all of this could have been avoided if I read the stinking comments below the crt animation thing. THis is such a waste of time haha, but then again, I gotta do it. We all make stupid mistakes sometimes.
Wow taking forever to root.
Click to expand...
Click to collapse
I remember having issues with Z4root as well. The first time I think it force closed on me (or stopped responding and gave me the option to force close) and kept doing that until I rebooted and tried it again.
Wow phone reboots soooo fast. I guess this SBF business wasnt so bad. Really cleans things up I guess.
This is a case of "I have no idea what I'm doing. I shouldn't have messed with crap I don't understand."
I have an Epic 4g that I've rooted previously and, using Odin, installed a custom ROM (forget which one). Yesterday, I attempted to flash Legendary ROM, following the directions in the How-to video linked in the Legendary post. I have an earlier version of CWM (v2.5.1.0 if that makes a difference) than what was on the video. I wiped the data, the Dalvik cache, and the battery stats before I began the flash.
The flash consisted of downloading the zip file of the ROM to my phone, booting into CWM, and installing the zip file from the SD card. The screen said that it installed correctly, but I got an error "E: Can't open /cache/recovery/log". When I went to reboot, it got stuck at the Samsung screen permanently.
I tried to flash again the same way - same thing happened. I read on a forum post somewhere that the SD card partition may not have enough space to flash the ROM, so I partitioned my SD card. Yup, I'm that dumb. Now, when I boot it up, it goes to the Samsung screen for a few seconds, then directly to CWM screen. It even goes to CWM when I plug the phone in without turning it on.
I've searched the forums here and elsewhere for this problem and specifically the error message (E: Can't open ...) and can't really make heads or tails of anything. The replies are over my head as far as my knowledge of my phone and these processes. I don't know what the exact problem is nor how to fix it. If you could help an idiot through the steps, I would greatly appreciate. If you live around the Philly area, I could offer you $50 to fix my phone and install the Legendary ROM.
Thank you for your time in reading this.
as long as it turns on and you get some kinda life you are still good couple things you can try
1 since you are on a older version of CWM wipe data 3 times cache 3 times and dalvic 3 time then try installing your ROM again give it a shot wont hurt anything
2 if that doesnt work you will have to Odin back to stock and re-root...i know it sounda like a pain in the ass but its the best option ill find you a how to for this if you need it
http://forum.xda-developers.com/showthread.php?t=1461337
ajt167 said:
This is a case of "I have no idea what I'm doing. I shouldn't have messed with crap I don't understand."
I have an Epic 4g that I've rooted previously and, using Odin, installed a custom ROM (forget which one). Yesterday, I attempted to flash Legendary ROM, following the directions in the How-to video linked in the Legendary post. I have an earlier version of CWM (v2.5.1.0 if that makes a difference) than what was on the video. I wiped the data, the Dalvik cache, and the battery stats before I began the flash.
The flash consisted of downloading the zip file of the ROM to my phone, booting into CWM, and installing the zip file from the SD card. The screen said that it installed correctly, but I got an error "E: Can't open /cache/recovery/log". When I went to reboot, it got stuck at the Samsung screen permanently.
I tried to flash again the same way - same thing happened. I read on a forum post somewhere that the SD card partition may not have enough space to flash the ROM, so I partitioned my SD card. Yup, I'm that dumb. Now, when I boot it up, it goes to the Samsung screen for a few seconds, then directly to CWM screen. It even goes to CWM when I plug the phone in without turning it on.
I've searched the forums here and elsewhere for this problem and specifically the error message (E: Can't open ...) and can't really make heads or tails of anything. The replies are over my head as far as my knowledge of my phone and these processes. I don't know what the exact problem is nor how to fix it. If you could help an idiot through the steps, I would greatly appreciate. If you live around the Philly area, I could offer you $50 to fix my phone and install the Legendary ROM.
Thank you for your time in reading this.
Click to expand...
Click to collapse
I can fix your phone remotely do you have teamviewer?
Go download and install teamviewer and pm me your id and password and ill fix it.
Sent From My Thugnificent SPH-D700 because its more than Magnificent
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
K3VlN said:
as long as it turns on and you get some kinda life you are still good couple things you can try
1 since you are on a older version of CWM wipe data 3 times cache 3 times and dalvic 3 time then try installing your ROM again give it a shot wont hurt anything
2 if that doesnt work you will have to Odin back to stock and re-root...i know it sounda like a pain in the ass but its the best option ill find you a how to for this if you need it
Click to expand...
Click to collapse
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
You need to flash CWM5 for correct conversions
Sent from my SPH-D700 using Tapatalk
brooksyx said:
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggoron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him.... i think in this case it might be the way to go and im sure he will explain to you everything he is doing
K3VlN said:
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him i think in this case it might be the way to go and im sure he will explain to you everything he is doing
Click to expand...
Click to collapse
Yep yep I've done this quite a few times now
My record for unbricking flashing to stock and rerooting and restoring a backup is like 10 minutes xD
Sent From My Thugnificent SPH-D700 because its more than Magnificent
brooksyx said:
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Its not bricked if it turns on! And you don't have to wipe 3 times... only 1 time each on all 3 things! Update your cwm and try to flash again, if that doesn't work odin to stock and start over... this time don't use an old version of cwm use the newest (5.0.2.7)
Sent from my SPH-D700 using Tapatalk
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
here is a link for qbking77 with a tutorial for ODINing back to stock...
http://www.youtube.com/watch?v=YQ2g6J1JgjU
the links for the software are under the video.
hope this helps.
bigron is da man and can help u, but if you want to play more with ur phone, BigRon might be with one of his "Honies" and you can't disturb da playa.
K3VlN said:
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggoron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him.... i think in this case it might be the way to go and im sure he will explain to you everything he is doing
Click to expand...
Click to collapse
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I always heard it was good to know that there is a way to fix it thanks for the info
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
http://files.devphone.org/epic4g/SPH-D700-EC05-8gb-REL.tar
MD5SUM: 4ea4dfea809c1a6d59b9fccf9e939f35
That's the file you'll have to use with Odin to flash your phone back to stock 2.2. That file will go in the PDA slot of Odin. Don't bother with a PIT or repartitioning (probably not needed in your case).
Once you boot with stock 2.2, let the phone OTA to EI22 and EL30 to get to stock gingerbread with the updated modem. From there you can start the root/rom flash process again.
flastnoles11 said:
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I'm just glad no one has suggested the good o'l magical restore button anymore xD
Sent From My Thugnificent SPH-D700 because its more than Magnificent
Thank you all for your help. Man, you guys are awesome! I'm going to try to reload stock using Odin this evening. If I'm unable to do this, I'm going to get Biggoron to help me via teamviewer.
Thank you all again. It seems that the only way I'm able to learn about things is by breaking them.
ajt167 said:
Thank you all again. It seems that the only way I'm able to learn about things is by breaking them.
Click to expand...
Click to collapse
Dont sweat that... most of it is all through trial and error. Truthfully, that's how I really got to know my phone better and the stuff I can do w/ it. That and this community. That's why trying a new rom isn't no big thing. If it doesn't take... it doesn't take. That's why we have "nandroid backup" and in "bad" situations, we have ODIN...
wscott9903 said:
Dont sweat that... most of it is all through trial and error. Truthfully, that's how I really got to know my phone better and the stuff I can do w/ it. That and this community. That's why trying a new rom isn't no big thing. If it doesn't take... it doesn't take. That's why we have "nandroid backup" and in "bad" situations, we have ODIN...
Click to expand...
Click to collapse
Welcome to the Sponge club and also the halls of Asgard to visit Odin or heimdall.
It worked!
I was able to successfully set my phone back to stock 2.2 and just received the OTA updates.
Before I left work last night, my wife called and told me that I locked the cat in the office the night before and she chewed up the USB cable for the phone (I'm so "internet"). I stopped at the Sprint store on the way home and got a new USB cable. I was using Odin for the process, following the video, using my new cable, and Odin couldn't see my phone. The guy in the video was completely right about Sprint/Samsung cables being crap. The chewed cable was originally from a Blackberry. I tried the chewed cable, having to hold it stretched out and tilted to the left, and Odin saw my phone. It went smoothly from there, though my arm got a bit sore.
When I get a chance within the next few days, I'm going to root and try again to install Legendary.
You guys are fantastic. Thank you all for your help. It's obvious that the people here know a lot about this stuff, but it's especially great that you're able to explain this stuff to people who don't know much at all. That's a talent.
ajt167 said:
I was able to successfully set my phone back to stock 2.2 and just received the OTA updates.
Before I left work last night, my wife called and told me that I locked the cat in the office the night before and she chewed up the USB cable for the phone (I'm so "internet"). I stopped at the Sprint store on the way home and got a new USB cable. I was using Odin for the process, following the video, using my new cable, and Odin couldn't see my phone. The guy in the video was completely right about Sprint/Samsung cables being crap. The chewed cable was originally from a Blackberry. I tried the chewed cable, having to hold it stretched out and tilted to the left, and Odin saw my phone. It went smoothly from there, though my arm got a bit sore.
When I get a chance within the next few days, I'm going to root and try again to install Legendary.
You guys are fantastic. Thank you all for your help. It's obvious that the people here know a lot about this stuff, but it's especially great that you're able to explain this stuff to people who don't know much at all. That's a talent.
Click to expand...
Click to collapse
Replace that cable ASAP, if you had lost connection in the middle of Odin'ing to stock you could have really bricked your phone! You might need to use Odin again soon..when learning my phone I had to Odin to stock probably 15 times, especially when you start flashing between MTD and BML ROMs (if you don't know what that is, just keep reading on here you will figure it out soon)
luna_c666 said:
Replace that cable ASAP, if you had lost connection in the middle of Odin'ing to stock you could have really bricked your phone! You might need to use Odin again soon..when learning my phone I had to Odin to stock probably 15 times, especially when you start flashing between MTD and BML ROMs (if you don't know what that is, just keep reading on here you will figure it out soon)
Click to expand...
Click to collapse
I have a good cable that I'm planning on using, I just left it at work last night. I'll read up on those types of ROMs. Thank you.