Well, I downloaded this file: http://dl.dropbox.com/u/4347574/Android/SamsungMoment_Update.exe
and then after I downloaded it, I ran the program, figuring it would be fine. Well apparently it flashed the stock for the moment (I think from what it looks like anyways) to my phone, and now it is inoperable. I could explain why I did that but it won't help anything, I misread and I messed up. Anyone know how to go about fixing this? Or have I lost all hope?
I know Im a lil late but yeah if you flashed that you are 100% bricked. No way to recover. You have to patch SWUpdater and use a tar that was made for the intercept. As far as I know there have been alot of people that have made that same mistake and no one has been able to recover from it. Sorry bout your luck man
Related
I have one of those Legends that require a downgrade before you root, but I decided to chicken out and after I downgraded to 1.31 or whatever it was, I decided to debrand my Bell Legend and chicken out to get the worldwide Froyo OTA. Plus, it was getting late, I didn't want to accidentally screw up the rooting because I was tired.
Anyway, after I downgraded, I installed a system update that brought me to Eclair-update-1. I don't think that was a really good idea.
Because afterwards, when I tried installing the debranded RUU from the debrand thread, it resulted in an error and I have to keep what I have right now.
UNLESS YOU GUYS HELP.
What did I do wrong? I'm only still a kid. Hell, I thought I bricked my phone halfway through installing the first RUU because there was something wrong with the drivers, I ALMOST TEARED UP FFS.
Oh yeah, and wtf is up with this BS where you format the SD card to turn it into a Goldcard, and HTC Footprints just decides to move its crap into the SD card RIGHT AFTER I FORMAT IT. It's not important, but I was just wondering.
I might have been missing some details (it's late) so please post below and tell me what I'm missing.
Thanks in advance!
PS: Oh yeah, have I voided my warranty yet? Technically, I mean. I COULD still clean it up somehow, and make it seem like I didn't do anything to it, right?
PS2: OK, now I'm getting USB errors 171 and 170 when installing RUUs. I can't get out of the RUU I'm on. Oh crap.
PS3: I just got Error 140, BOOTLOADER Error. What did I do wrong here?
At least I'm at the phone's home screen now, no more unfamilar scary-ass HTC LOGO territory.
Basically the update to "2.1-update1" brought you back to where you were before the downgrade. Your phone is stock right now.
So first relax and get some sleep
Do the downgrade again. DO NOT UPDATE.
Continue the debranding/gold card procedure.
good luck
p.s. your warranty might technically be void when you install another ROM or debrand or root, mostly they don't care as long as you didnt drop it in water . There is always a way to bring it back to stock/unroot
Oh my goodness I love you. I just noticed (while I was tired, wow, that's strange) that the strange ROM number within the About Phone menu finally clicked with what I've been doing! NO UPDATE.
So I decided to call it a night after I try once more.
So I downgraded to w/e. It was fine.
And I tried the debranding RUU. Then I got a bootloader error. I guess I'll try to find out what that means when I wake up, I'm super sleepy. (Unless you guys can help me 'til then )
It was error 140 or something like that, but it booted me fine to my downgraded ROM, so I'm good for the time being.
Good night!
EPIC ACHIEVEMENT EDIT:
Alright, I rooted it. Sweat all over the place, but hey, don't blame me. The problem above is still experienced by many people all over the internet, unfortunately. Too bad I can't answer it.
Just a question before I flash my first ROM with ClockworkMod: What about fixes? How do I flash those? Super noobish, but yeah.
Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!
Grimacexl said:
Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!
Click to expand...
Click to collapse
Whatever you do DO NOT USE THE ATT SBF! That is not meant for bell devices and will definetly make your situation even worse!
Yeah, I figured that would be the case.
Working on trying to push my backup files to my device atm
Grimacexl said:
the tutorial site didn't mention anything about not using it on a Bell Atrix,
Click to expand...
Click to collapse
dude, it's in CAPITAL RED LETTERS on both the tutorial website and the forum thread.
this guy had a similar situation, but i don't know if he got it fixed.
http://forum.xda-developers.com/showthread.php?t=1033184&highlight=bell+sbf
EDIT: attached
Yeah, the tutorial I used didn't say to not use it on bell atrix, but when it messed up, I went to all the other tutorials that have it in red, so I do feel pretty stupid.
Well, it's all good now, After pushing bell backup app and framework folders, I managed to get a working device (all be it with some force close crap which I'll iron out later) The device is working.
Hello,
I was directed to http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader for unlocking my stock AT&T atrix phone.
After step 11, pressing start it began to do its thing.
THen I got an error that said something about cant restart. (Sorry hit show phone button and it erased the error msg)
But now I can't even turn on the phone?
Is there anything I can do to fix it? I am not even really sure whats broken now.
Any help would be appreciated got a dead phone now... lol that was easy to mess up even following the directions i was sent to... crap!
Can you get the phone back into RSD mode? If so, I think this happened to me. I just had to start over, and I ended up renaming the SBF to something shorter. After that, it flashed just fine for me
However, I'll let you know I'm not a dev or anything, just another end user and honestly I was so flustered when I kept messing up my install that I don't exactly remember
Man, I'm the very first person to download Joey Krim's Original 2.0.1 Deodex! It's loading now. I can't wait to see what it looks like. I'm wondering if my smelkus recovery will block the update of this too. Lol... I'm about to find it with SD Maid and delete it. Anybody know what file folder it is housed in? I'm gonna BAR-B-QUE this phone tomorrow if I can't get it fixed. ha... I'll post a video of the ROM ROAST. I'm sick of this b.s. I wish I never tried anything different than what I had been doing. Now my phone is a piece of crap. But I got this Throwback to get me to sleep tonight. It just booted. Can't wait to see the old stuff.
Yeah, you really screwed up your phone somehow. Idk if you'll be able to get it fixed, but just go with one of the few roms that you said worked and you'll have to live with it. Sorry, i don't know what else to tell ya.
nate234 said:
Yeah, you really screwed up your phone somehow. Idk if you'll be able to get it fixed, but just go with one of the few roms that you said worked and you'll have to live with it. Sorry, i don't know what else to tell ya.
Click to expand...
Click to collapse
Man, I fully unrooted my phone. Then rooted it again, and it's supposed to be like new again. I had no issues during this process. Everything went according to the outlined procedure. No deviations. Well guess what, it still does the same thing with the Pacman ROM. I was convinced that there must be something wrong with my phone, but I'm not sure now. Surely to God, nothing could still exist past an unroot and fresh flash right? I mean, the file system was completely reset with the PC36IMG right?
I tried to flash it but it only bootloops for me. Have tried almost everything it seems. Have never had so much trouble flashing a phone.
I have tried Lieage os 15.1 but after i tried to flash N2G48B_4Cores.img from this side https://www.xda-developers.com/nexus-6p-bootloop-fix/ Lineageos bootloops even faster. Even tried the twrp from the side who requires a password I cant find so it it is useless.
I have tried Aquatios but it bootloops.
I have tried to flash stock android but it says something about the zip is wrong.
Someone who knows what I should do or am I stuck? I forgot to make a backup to so I am a bit desperate. Never forget it usually but only because it's not my phone I do forget.
I hope someone knows what I should do.
*EDIT* [SOLVED]
Trie this and got a bit further: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
Only that the screen flashes soon after after the settings come up and turn itself of after a while.
I have not flashed the radio though. Is that necessary?
*EDIT 2* [NOT SOLVED]
The radio were necessary for wifi.
Now is the problem with signing in to google.
Never can anything go smoothly.
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
orrebo said:
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
Click to expand...
Click to collapse
Good to hear. So what did you do wrong and what did you do to fix it?
Aimless Rambler said:
Good to hear. So what did you do wrong and what did you do to fix it?
Click to expand...
Click to collapse
Yeah. What did I do. Tried until I found a solution that worked. Think I mentioned it (did not). This thread I looked at to solve that problem: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
I had to flash a bootloader file and after that it worked better.
But I can't sign in to google how I do. Will try a couple of other gapps. Hopefully someone will work.
I have seen this before but don't remember how I solved it back then.
It even bootloops if it don't like the gapps.
New problems every time. A new one again where it crashes in the initial settings.
It stopped suddenly and is now back to checking info and this time it said it can't connect to google servers.
Have never ever worked with such a ****ty phone.
*EDIT*
I give up. It is as good as it gets.
If someone else of her friends wants to try so be my guest.
Over and out for this time.
If it's toast from the infamous bootloop issue can't blame you for setting the phone aside. But if you venture back to it I'd suggest flashing stock Google firmware then doing the 4cores fix if needed.