Related
Hello
I wanted to backup so i ran the backup with ROM Manager and it froze when it was backing up .android secure. I had to pull out the battery so I don't think it was completed has this happened to anyone?
Yeah, it happens to everyone not posting in the right forum.
christiankk said:
Yeah, it happens to everyone not posting in the right forum.
Click to expand...
Click to collapse
You kidding me? If this isn't the place for it then where would he post it? Certainly not in the development section.
Sometimes backups get corrupt man, that sucks.. you'll probably just have to start anew
Sent from my Nexus One
ryanolson7 said:
You kidding me? If this isn't the place for it then where would he post it? Certainly not in the development section.
Click to expand...
Click to collapse
How about the forum called "Nexus One Q&A"?
As fun as it is to "act-a-mod", you both need to stop.
ANYWAYS, OP: If at first you don't succeed, try try again. If it fails again, try flashing a different recovery.
Yeah, just try backing up again. It has happened to me before. Stuck backing up at .android_secure. So I just tried to backup again, then it worked.
if you all want a recovery on which you can trust, then switch to Amon_Ra's recovery (RA-nexus-v1.7.0.1)
i keep having a similar problem. my backups can be created just fine. but when i try to restore them they ALWAYS hang at a certain file, such as event_1626573434.txt or whatever it may happen to be. sometimes i can go to advanced nand and restore each portion individually, which sometimes works. so the backup itself works. i really dont know what the problem could be. using clockwork recovery.
sstang2006 said:
if you all want a recovery on which you can trust, then switch to Amon_Ra's recovery (RA-nexus-v1.7.0.1)
Click to expand...
Click to collapse
That's not entirely true, that's pure opinion.
edit: Sorry, I guess I was too slow in writing my response
wdfowty said:
That's not entirely true, that's pure opinion.
Click to expand...
Click to collapse
You might try the quote button, otherwise, are you doubting the post above yours?
First, Make sure you have enough space on your memory card...
Thank you guys. Its all good now
Sent from my Nexus One using XDA App
I happen to have the same issue. Is pulling the battery the only way to get out of it?
Yes
Sent from my Nexus One using XDA App
wdfowty said:
That's not entirely true, that's pure opinion.
edit: Sorry, I guess I was too slow in writing my response
Click to expand...
Click to collapse
yeap, my opinion may turn out to be a fact.
njiwani said:
Hello
I wanted to backup so i ran the backup with ROM Manager and it froze when it was backing up .android secure. I had to pull out the battery so I don't think it was completed has this happened to anyone?
Click to expand...
Click to collapse
Clarkster said:
Yeah, just try backing up again. It has happened to me before. Stuck backing up at .android_secure. So I just tried to backup again, then it worked.
Click to expand...
Click to collapse
RogerPodacter said:
i keep having a similar problem. my backups can be created just fine. but when i try to restore them they ALWAYS hang at a certain file, such as event_1626573434.txt or whatever it may happen to be. sometimes i can go to advanced nand and restore each portion individually, which sometimes works. so the backup itself works. i really dont know what the problem could be. using clockwork recovery.
Click to expand...
Click to collapse
mailliw320 said:
I happen to have the same issue. Is pulling the battery the only way to get out of it?
Click to expand...
Click to collapse
mailliw320 said:
I happen to have the same issue. Is pulling the battery the only way to get out of it?
Click to expand...
Click to collapse
Nope. I'm not sure what I pressed, but I think trackball + power button. And then the phone restarted. Didn't need to pull the battery.
Okay so I updated to JI6 from KIES. I was having some problems after the update so I decided to restore my nandroid made by ROM Manager (a backup made before the update - at JFD). I restore it, phone reboots, etc. However, now it is stuck at the "Vibrant Samsung" screen -- you know the one that comes with the T-Mobile logo appears. The odd thing is I even hear the load-up sound that plays, but the phone does not go past the Vibrant screen.
Help please?
Oh and I can still boot into recovery mode...
You sure you are waiting long enough? Mine took about 5 minutes after the firmware upgrade to get past the samsung vibrant screen. I thought it was frozen at first but I guess it takes awhile after the firmware upgrade.
This is after I did the restore from ROM Manager -- not after the firmware upgrade.
This is caused by downgrading from ji6. If you nadroid on ji6 to stock it will brick. I believe the only way to fix would be through odin. Hope it gets worked out.
Sent from my SGH-T959 using XDA App
doh >.>
Why the heck can't I get into Download Mode...
EDIT: Nevermind, got into download mode. Apparently you dont hold power key for DM.
Okay i ll make sure to never help you again. Have fun with your attitude and bricked phone.
Sent from my SGH-T959 using XDA App
Huh? What did I do to you =O
Anyway, I think my phone is really bricked now. Can't get into download mode.
fcbarca17 said:
Okay i ll make sure to never help you again. Have fun with your attitude and bricked phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ha ha he did not even say anything bad xD
DarkAgent said:
Huh? What did I do to you =O
Anyway, I think my phone is really bricked now. Can't get into download mode.
Click to expand...
Click to collapse
Ever get it fixed, im having a similar problem..
Title. I haven't ventured far enough to flash roms yet, still running stock JI6. Is it even a remote possibility to completely brick your Vibrant i.e. no fix?
It seems like whenever someone creates a thread saying they bricked their phone, Odin always magically fixes everything.
Yes, it is possible but VERY unlikely. If I remember correctly, wesgarner bricked his.
I'm new here. I bricked mine up good. haha. I rooted and did a lagfix. It worked great, until tmo sent me the ota update. It softbricked it. So I flashed it with what I thought was a stock rom. then they sent me the update again. After poweroff it won't even turn on. No recovery menu, no download menu, no power. So, yes it is possible.
Yeah, I have bricked 2 of them while doing some things & messing up at like 2am
Anything can be bricked.
Sent from my GT-I9000 using XDA App
You can't brick it, is only a soft brick, the ones that get ''bricked'' are the ones that are hardware locked, they can't get flash back to stock, because recovery nor download mode work after the ''brick''.
Sent from my SGH-T959 using XDA App
Master™ said:
Yeah, I have bricked 2 of them while doing some things & messing up at like 2am
Click to expand...
Click to collapse
what are you doing exactly with it? it can't be fixed even flashing back to stock?
i bricked my first g1 Not my baby tho lots of hours of reading and re-reading
iynfynity said:
what are you doing exactly with it? it can't be fixed even flashing back to stock?
Click to expand...
Click to collapse
Same thing Wes was.
And nope, they couldnt be flashed back with Odin even.
smkr420 said:
i bricked my first g1 Not my baby tho lots of hours of reading and re-reading
Click to expand...
Click to collapse
Same here. I forget what I did wrong, but it was during the Donut hysteria.
Luckily, I've learned to read a but more with the Vibrant before flagging things.
-bZj
_____
-sent from my Samsung Vibrant via XDApp
cervantesjc said:
You can't brick it, is only a soft brick, the ones that get ''bricked'' are the ones that are hardware locked, they can't get flash back to stock, because recovery nor download mode work after the ''brick''.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Hw locked has a fix & You can brick this phone.
I bricked my vibrant by flashing haykuros danger SPL.... Lol. G1 days FTW!
Hardware locked vibrants are considered bricked. Happen to me twice now and had to send in for repair.
I've never seen the term bricked associated with a device like the vibrant.
Sent from my SGH-T959 using XDA App
You certainly can brick a Vibrant, even one that is not hardware locked. I did it last week. I did it by trying to create a custom Odin backup that flashed an incomplete boot loader, I think.
In any case, AFTER a successful Odin update the phone turned off to reboot, and will not turn back on. No amount of messing with it will get the phone to turn on. There is no way I can figure out how to even get Odin to work, because there is no power going to the phone. Bricked.
So, moral of the story:
Follow these rules and it's not possible:
If you have a hardware locked phone, FIX IT.
Don't flash anything for the wrong phone.
Don't accept OTAs if you're hacked.
Only flash things that others have confirmed (can be the dev).
If you're making your OWN stuff (Wes, cparekh), it's quite possible to completely screw your phone.
So I was told to install the deodexed [sp] of the GB leak, so I did on top of my rooted, non deodexed version, without wiping. After this I wiped my data a few times, as I heard it would be best to do. Well, after doing so... my phone won't stop bootlooping. I can't access the bootstrapped bootloader, only the stock Moterola one, and I cleared my data with it hoping it would work too...
Help please? How do I "sbf" back to stock or whatever?
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
I hope its ok to post this link here:
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
tried flashing it again, same thing happened. It failed at "switching phone to BP pass through" apparently. help me please
thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Now just do the system only sbf.it will work
Sent from my DROIDX using XDA App
Do you have the latest drivers installed? Try using RSDlite 4.9!
thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
z06mike said:
Do you have the latest drivers installed? Try using RSDlite 4.9!
Click to expand...
Click to collapse
i found rsdlite 4.9 didnt recognize my phone but 4.8 did
itzjen said:
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
Click to expand...
Click to collapse
Like what did you say to them?
tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
this is totally being lazy AND the reason why everyone is raising their prices on insurance and why ppl like motorola are locking bootloaders. if it is too much or you're too lazy to do it. dont do it in the first place. sbf isnt hard there are a gazillion guides to sbf'ing. not trying to be rude but seriously?
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
thewanton said:
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
Click to expand...
Click to collapse
you have to sbf to .340 use z4 root to root then install DX bootstraper reboot to recovery flash gbrooted.zip if you get stuck in bootloop go into factory recovery and wipe data reboot download and install D2 bootstrapper yes D2, boot into recovery and flash gbrooteddeodexed.zip and let it try and boot it SHOULD bootup after a couple of minutes, if it doesnt get into stock recovery and wipe data, reboot
also it could bootloop because of corrupt downloads
tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
itzjen said:
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
Click to expand...
Click to collapse
which is a problem that was caused by YOU because you take that and sbf
thewanton said:
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
Click to expand...
Click to collapse
most ppl overlook that as a typo
Funnyface19 said:
which is a problem that was caused by YOU because you take that and sbf
Click to expand...
Click to collapse
Yes it was a problem that I caused but at that momment I got scared and wasn't sure what I was suppose to do,and because I have no internet at home because i'm never home I use wireless tether when im there and my phone was messed up so wasn't able to look at guides to fix it.....So the easiest thing I thought of is calling them.I wouldn't have mind fixing it but again I wasn't able to at that momment.
I had the same thing happen. Put the letter p at the end of the file name and move it to c:\ this worked for me on rsd lite 4.8 I just kept pulling the battery and retrying until it went through
Sent from my Xoom using XDA Premium App
meshdub said:
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
Click to expand...
Click to collapse
I'd just like to point out that you don't actually need rsd lite 4.8 or higher. 4.7 has worked perfectly for me the several times I have SBF'ed
I have come across at least 10 people now that the below method of restoring your phone, after trying EVERY other way that you can think of, works for
I can not, and will not, guarantee that this will work for you, but, it does seem to work when all else fails..
Now, i can expect of you to have tried at least a few of the following before doing this:
- a CWM Data Wipe
- a CWM Backup Restore
- a (EC07/DL17) clean rom flash (from within CWM)
- a (EC07/DL17) ODIN Restore (Be Careful, heed and read my warning i posted within this same thead before doing this)
IF you have exhausted your creativity with trying to fix your phone, try this:
First, download the following:
Heimdall Frontend: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
Samsung Fascinate's Stock Param.lfs: http://dl.dropbox.com/u/18259212/Phone/stock_param.lfs
Continuum Original Recovery [EC07]: http://www.mediafire.com/?pz8p4axk114092j
Continuum Original Param.lfs [EC07]: http://www.mediafire.com/?7isd5m1dbze6a0t
7-zip (or Winrar for the losers ): You find it!
I am going to make this part quick
Put the phone is Download mode, and install the driver for Heimdall with ziag.exe within that zip... (you will need to check options --> list all devices).
Put the fascinate param.lfs into the param.lfs section.
Extract the original recovery with 7-zip (or other such programs)
Put the extracted file in the Recovery Section in Heimdall.
Click Start
From there, the program should flash the files, and your phone should reboot... You should see scrolling yellow text, and then.... Rejoice
Your phone should be working okay now, but Just to be safe, make sure you restore the original param.lfs before you get too comfortable
If you experience any difficulties, just post them down there vvv ... Again, this is only to be attempted if you have tried everything else
First I can say this method works to get it back up and running (see threads below on what I went through.) With that trailblazer. I haven't re-activated this phone yet because I'm waiting to make sure it works this time. I wanted to turn on wifi to verify I have root (i.e setcpu, titanium, something to that affect.) I can see the wireless signals but I can't connect, any ideas. I would like to have this "stock" version working with a workable nandroid in case, but I guess I dont have to.
edit: you may also want to put this in development instead, probably doesn't matter but I look there first personally for fixes.
yeah, i have heard of this issue with other people...... What other people did to finally fix it was restore a Nandroid backup.... In your case, you can't do that
I would suggest getting blue cwm up and working, and flashing any of the Clean Roms within it.... Making sure you do a data wipe... That's all i can really say :|
trailblazer101 said:
yeah, i have heard of this issue with other people...... What other people did to finally fix it was restore a Nandroid backup.... In your case, you can't do that
I would suggest getting blue cwm up and working, and flashing any of the Clean Roms within it.... Making sure you do a data wipe... That's all i can really say :|
Click to expand...
Click to collapse
Yeah I just did and its up and working now, i used this one http://forum.xda-developers.com/showthread.php?t=1008848, linked to http://forum.androidcentral.com/samsung-continuum/73450-rom-3-30-11-clean-continuum-dl17.html that for the DL. only problem is the browser fix link is broken now, you dont happen to have it lol, and I like how you had your crack at me about winrar
spursrchamps2007 said:
Yeah I just did and its up and working now, i used this one http://forum.xda-developers.com/showthread.php?t=1008848, linked to http://forum.androidcentral.com/samsung-continuum/73450-rom-3-30-11-clean-continuum-dl17.html that for the DL. only problem is the browser fix link is broken now, you dont happen to have it lol, and I like how you had your crack at me about winrar
Click to expand...
Click to collapse
Sweet! Glad it is working for you now
And I do in fact have it Lemme Upload it to OP for everyone
and lmao, i had to You understand bahaha
trailblazer101 said:
Sweet! Glad it is working for you now
And I do in fact have it Lemme Upload it to OP for everyone
and lmao, i had to You understand bahaha
Click to expand...
Click to collapse
hmm do you run the broswer fix through cwr im guessing I ran it and still getting the FC, sorry for the questions btw
Yeah, i was half expecting that... You need to do a browser wipe... Go to settings, Applications, Manage Applications, Browser, then "clear data" and "clear cache"
trailblazer101 said:
Yeah, i was half expecting that... You need to do a browser wipe... Go to settings, Applications, Manage Applications, Browser, then "clear data" and "clear cache"
Click to expand...
Click to collapse
done thanks and you jsut got a lot of thanks lol,
Lol, thanks for that man!
Sent from my SCH-I400 using XDA Premium App
hey, I don't know how to extract the original recovery from 7-zip. can someone please help me?
EDIT: okay, I extracted the recovery file and it turned into a .bin file and I cannot flash it on heimdall because it says my phone is not recognized.
Did you install the drivers?
Sent from my SCH-I400 using XDA Premium App
yeah, I finally got it up and running. I kept trying to flash the new edify rom and things weren't working, so I flashed another rom and it works fine now.
EDIT: well, nevermind. now I'm getting a bunch of force closes. just about everything works except titanium backup, social networks, and ATK. any ideas?
Did you do a data wipe?
Sent from my SCH-I400 using XDA Premium App
nope, forgot about that. I should probably do that, eh?
Lmao, yea you should xP
Sent from my SCH-I400 using XDA Premium App
shameless bump....
Ahaha it happens to the best of us lol
Sent from my SCH-I400 using XDA App
stuck as requested
Thanks for this man xD
still hoping there is someone will porting an ICS for this lovely handset