I tried installing the Gingerbread update, and when I installed both Parts 1 & 2, then rebooted, my phone only goes to the bootloader screen. Tried using RDS and that, and couldn't find my phone. So I'm stuck.
My phone boots now with a red Moto logo and then goes to the error screen.
My question is, what will Verizon say when they see it? I'm going to take it there later today. I'm under insurance but hacking voids that I believe.
What should I say to get it replaced at no cost?
I was going to say that I put it down, and then when I checked it later it was off, and then when I tried to boot it, this happened, saying I didn't hack it, maybe someone else got it.
Would that work?
Speedy answers would be great.
Thank you so much.
DO NOT TAKE IT TO VERIZON.
Look at the stickies, there is a thread about fixing your phone. You need to find the stock firmware and flash it with RSD.
Sent from my DROIDX using XDA Premium App
Also, the "I put it down" excuse will only work if you get a retard. Anyone who knows about Android will know what you did
Sent from my DROIDX using XDA Premium App
Did you install the Motorola drivers before attempting an SBF, just Google "Motorola drivers".
Well I have funny news for you guys.
I actually saw your messages after I got back..but thank you for your time.
But the guy...bought the story. He said I was probably recieving a bad update, and was able to fix the phone.
The guy was awesome though, after, he could tell it had ben rooted, and said, "yeah just know that root won't work on Gingerbread", which he installed for me.
So problem solved.
The extent of how lucky I was is amazing.
Well good deal. I'm glad he was cool. You can root, you just have to sbf back to froyo first
Sent from my DROIDX using XDA Premium App
If you mess up your phone when you are messing with it, you are responsible for fixing it. Not Verizon.
salsabettis said:
If you mess up your phone when you are messing with it, you are responsible for fixing it. Not Verizon.
Click to expand...
Click to collapse
Not sure why you're posting this now.
And I think i'm gonna stay away from rooting right now.
If you do ever decide you want root get the bootable linux cd with the automated scripts to sbf with. It is totally painless.
My DroidX Thrives on the DarkSlide!!
Related
i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?
hard reset may work
Sent from my Incredible using XDA App
i tried hard resetting it. this did not solve the problem.
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.
Are you root?
When and how did this start happening?
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.
JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App
JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App
Try the RUU that was posted.
jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen
theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App
Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.
I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure
Just jumped ships from sprint and got my facinate. Today rooted with one click and tried installing clock work. Thmanage rom manager. All seems well then suddenly my phone freezes for ten minutes I have to do a battery pull. Phone wont boot in anyway or form now. No lights or signs of life other than if I hold the power button as long as its pressed. A device labeled SEC S5PC110 Test B/D appears in device manager. And that'd all it will do. Thinking about exchanging it tomorrow afternoon. Just letting the community know what happened to me any thoughts as how or what happened might be able to help future mishaps
I'd try doing an odin flash. Just search the forums for the step by step. If u can get the phone into flash mode.
Yeah dude, definitely try Odin. Did you try flashing cwm from within ROM manager? I ask because that doesn't work for our phones yet, and it wouldn't surprise me if that could cause problems. I would use Odin to flash it back to stock, and then use the very thorough guide on here on how to get cwm going.
Sent from my SCH-I500 using XDA App
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
illtema said:
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
Click to expand...
Click to collapse
Hard for him to do a backup when he got bricked installing CWM LOL
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
I would think that if newer fascinates were boot locked, so would mesmerizes and I first flashed the stock files for Verizon on my phone then went to elements zinc (which is awesome BTW) installed voodoo 1200 kernel and everything is working great for me. Could just be that he got a bunk phone or something
PhoenixPath said:
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
Click to expand...
Click to collapse
I'm thinking it's just Noob users who are bootlocked...
My phone is only a week old everything went fine root,cwm...
wisconsinated said:
I would think that if newer fascinates were boot locked, so would mesmerizes
Click to expand...
Click to collapse
Why would you think that? Same hardware!=same software...or we'd all be running USC's kernel/ROM.
Could just be that he got a bunk phone or something
Click to expand...
Click to collapse
Could be...which is why I said "possibly" instead of "definitely".
Couldn't get to the flash mode even to use odin, went back today and bestbuy swapped it out for me thinking I just got a bad phone, I could also shake the thing and hear raddling with the usb door shut to so im not really surprised. The new one seems to be working better already, eill try root tonight,
Jwahlg said:
I could also shake the thing and hear raddling with the usb door shut
Click to expand...
Click to collapse
Volume toggle. I bet the new one does it.
good day.
chopper the dog said:
Volume toggle. I bet the new one does it.
good day.
Click to expand...
Click to collapse
He's right, the volume rockers rattle like a sumbitch.
Sent from my SCH-I500 using XDA App
My Fascinate is just twp weeks old and One Click and CWM worked just fine for me. BTW I am running JTs super clean rom. Lovin this phone!
Sent from my SCH-I500 using XDA App
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
ksizzle9 said:
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
x10
This is counter development long term.
I further submit that in the future, all root processes require a ten question exam on the users knowledge to work.
Sent from my SCH-I500 using XDA App
Mine crashes sometimes. Even with all original OS. I just pull the battery and all is good.
My volume rocker doesn't rattle, so there is that plus.
Sent from my SCH-I500 using XDA App
I was updating my buddy's DX to GB using the same method I used on my phone. Only difference was i used the rooted and deodexed version for his phone and just rooted on mine. I installed the zip update went to reboot and it won't move past the M screen. I called up tech support just to see what they would say and they said send it back and they'll send a new one. I made sure to be clear that the phone was rooted and they still said that they would replace it. I was shocked but happy. I have a feeling my friend won't let me try again on the new phone
Sent from my DROIDX using XDA App
"YOU CAN ONLY USE THIS FILE IF YOU HAVE ALREADY UPGRADED TO GINGERBREAD"
any chance you missed that step?
I'm sure you could SBF it to 2.3.340,
Root
Install DX Bootstrap
Wipe Data/Cache
Install Rooted GB vie Clockwork
Install D2 Bootstrap
Install Deodexed Rooted GB via Clockwork
I have exactly same problem as you days ago.
and I spent overnight and finally solved the problem myself, I was so upset and felt sad that my Droid X maybe turn to a brick. but lucky It's now alive.
How I recoverd was:
1. Turn off your Droid X
2. Press Camera + Volume Down + Power buttons simultaneously and wait until to USB mode
3. Use RSD Lite 4.8 to flash to official 2.3.340
Yeah I was doing it on little sleep and just grabbed the first gb file I found. Oh well he is getting a new phone
Sent from my DROIDX using XDA App
Vettesfan said:
Yeah I was doing it on little sleep and just grabbed the first gb file I found. Oh well he is getting a new phone
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Well it will be the same process for the new phone, minus the SBF part. Be sure to install rooted GB first, then Deodexed after.
this s*** is getting old ppl, read directions, brick my a$$ reasons like this are why we keep getting locked bootloaders and increased insurance claims. it you dont know how to f'n do something find out how before you do anything or DONT do it
exactly!!!!!! ever hour another thread is posted stating the same thing. is it really that difficult? I understand the process is complex for a noon, but at least reading the op's directions in full and comprehending them before continuing isn't.
You can SBF yourself out of almost any non hardware issue. All it takes is research, patience, and a little bit of thought.
SharkBaitDave said:
You can SBF yourself out of almost any non hardware issue. All it takes is research, patience, and a little bit of thought.
Click to expand...
Click to collapse
dont make fun. some ppl cant read
Your an idiot and the reason they lock phones down. All you have to do is sbf back to stock. Thanks for sharing so now we can all make fun of you.
Sent from my Xoom using XDA Premium App
It is nearly impossible to brick your phone.. bet he feels smart now.. read directions! !!!
Sent from my DROIDX using XDA App
DroidzFX said:
Your an idiot and the reason they lock phones down. All you have to do is sbf back to stock. Thanks for sharing so now we can all make fun of you.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
+1
SBF back and tell VZW to cancel the new phone. If you had read the directions the first time this wouldn't have been an issue. Instead you f-ed it up, called VZW to get a warranty replacement, and VZW locks down new phones even more.
SBF back and don't f it up for the rest of us who can follow directions!
unfortunately this is why verizon and other carriers are starting to track root users. People that root and violate the TOS, warranty, etc then lie and send their phones back are stealing and committing fraud. If you dont know what exactly is happening when you do something, and dont know how to fix it if you **** up (if it violates TOS), then dont do it.
I did not lie to them. I did call tech support, but I made it clear that the phone was rooted and I was attempting to install an unofficial update. They told me that I could still do a warranty return so I took them up on it because it is cheaper than insurance deductible which I was planning on using and was the reason I purchased insurance. I don't believe that is fraud. If I told them its never been rooted and it just crashed that would be another story.
Sent from my DROIDX using XDA App
Rooting voids your warranty. So, if you manage to get a warranty replacement on a rooted device, its technically fraud, irrelevant to the fact that VZW tech support let you return it.
Is talking the cable guy into giving you extra channels for free fraud?
Need to take my phone back to att for a faculty gps and after reading around here i found out it might hard brick it.
Well i didn't hard brick, but i am stuck on boot loop.
Any help?
It goes to the att boot animation, then goes back to the Motorola logo one...
I used a File called 2.3.4_pudding_preroot or something like that.
I had a similar problem once and re flashing fixed it, which ill try when i get home from errands, but i wanted to post and ask for suggestions i til I get back to try it.
Im gonna stop at an att store and see if they can give me a replenished one, but i doubt that...
There is probably a thread related to this somewhere too, but im posting from Tapatalk so its hard to look around. Lol
Thanks in advance!
Sent from my Xoom using Tapatalk
Sent from my Xoom using Tapatalk
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
yokozuna82 said:
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Is there a number for motorola warranty you have? How do I start the process?
Sent from my Xoom using Tapatalk
Just left the att store. There is apparently a DSC (device support center) about 10 miles from here and they'll just replace the phone on the spot. Hopefully they won't say anything about the 'unlocked' text.
Let you know what happens
Sent from my Xoom using Tapatalk
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
CSharpHeaven said:
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
Click to expand...
Click to collapse
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Got a new phone. GPS works. Gonna have to sbf again for Unlock and pre root now. Hopefully this one will work out. Lol...
Is there a way to Unlock and root without sbf??
Sent from my Xoom using Tapatalk
razorseal said:
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Good to hear that. Please make sure you will read the following thread once you got your new Atrix. I get GPS lock in the UK within seconds. I even managed to get GPS lock indoors. A must for every handset really.
http://forum.xda-developers.com/showthread.php?t=1239713
so I have a bricked MF3 build.
I've read up and down, and at this point it can't be fixed. bootloader locked, etc.
I had an idea of flashing the 4.3 leak onto the S4 in hopes of fixing the /system/ partition since only one file is messed up that is causing the phone to bootloop.
if I could locate the 4.3 leak -- will it fix my soft-brick?
hypothetically speaking it should, right?
all directions that speak of flashing the file ask that the phone be ON the MF3 baseband.
is the odin file for JWR66V on the i337 signed so that I could flash it in Odin and get my phone working again?
sounds like it should work, please any input?
Nope. MF3 baseband is the modem needed. That can be flashed to MDL. The MF3 OTA completely locks your bootloaders... You're screwed.
Sent from my SAMSUNG-SGH-I337 using xda premium
grammar gripe
graydiggy said:
Nope. MF3 baseband is the modem needed. That can be flashed to MDL. The MF3 OTA completely locks your bootloaders... You're screwed.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Needed for what? graydiggy, please fix that partial sentence "That can be flashed to MDL."
Solidus636 might be screwed like you say, but your answer leaves me wondering why.
That is not a partial sentence. OP cannot flash anything on the MF3 firmware update.
The MF3 baseband can be separately flashed onto MDL. At that point, one would be able to flash 4.3.
Since there is no way to flash using MF3, OP goofed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
That is not a partial sentence. OP cannot flash anything on the MF3 firmware update.
The MF3 baseband can be separately flashed onto MDL. At that point, one would be able to flash 4.3.
Since there is no way to flash using MF3, OP goofed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for the clarification.
Why are these people that took the OTA MF3 update from AT&T trying to flash in the first place?
How are they getting root or a recovery? It makes no sense to me.
Solidus636? What did you do (please include details) how did you do it? It would be helpful for everyone to learn what not to do.
We are able to get root with no issues. Just no recovery.
Why? People don't read. They don't care that they could brick a $650 phone. They deserve it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
root
graydiggy said:
We are able to get root with no issues. Just no recovery.
Why? People don't read. They don't care that they could brick a $650 phone. They deserve it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, I read up on getting root for MF3 OTA and it says right up front CAUTION THERE IS NO RECOVERY
and rooting looks like it's more complex, I remember the Android Debug Bridge, and I'm glad I was able to get in early with motochopper and then casual and I'm pleased with the GoldenEye Rom. Just a tap and a swipe bar in the TWRP recovery. I see how I dodged a bullet back in June when I froze AT&T Update service with Titanium Backup. I'm lucky. And it took me a long time to grasp all the terminology and what the difference is between root and getting a custom recovery, and I'm sure that it's not the amount of reading one does, but rather comprehension. That's why when I print in here I try not to leave anything out.
Whiz kids like yourself forget what it's like to wonder if there is a difference between installing a zip or flashing one and could care less on articulating the details you take for granted.
There's not a fix in the world for solidus636's handset cuz he blew the E fuse huh? Not sure what that is and barely understood it when I read about it.
I loathe AT&T. Now they locked the bootloader. What a bunch of creeps. I almost didn't get the S4 because of the shrunken SIM but I found an adapter so I can light up all those old phones in my gun safe. It's how I roll. I would never buy a handset you couldn't pull the battery on. And everytime I see a new connector plug I go on a rant about UL listed and deregulation. Instead of making a one size fits all battery, almost every device has a different shape size and fit.
Ok all done complaining now. Beg pardon for bending your ear. I think you like it tho, and will find something to be smart alec about.
fukenbiker said:
Thank you for the clarification.
Why are these people that took the OTA MF3 update from AT&T trying to flash in the first place?
How are they getting root or a recovery? It makes no sense to me.
Solidus636? What did you do (please include details) how did you do it? It would be helpful for everyone to learn what not to do.
Click to expand...
Click to collapse
i Rooted the phone.
then i messed with the /framwork-res.apk and accidentally renamed it to /framework-res.apk.bak and now there is NO framework-res.apk file inside /system/framework/ meaning i am soft-bricked until I can get the MF3 Odin file or a file higher than that....
i also didn't accept the RSA keys to default to accept on my computer, meaning I can't access ADB it says OFFLINE. if I could access ADB this would've been an easy fix by renaming the framework-res.apk.bak file back to framework-res.apk, but I messed up:/
graydiggy said:
We are able to get root with no issues. Just no recovery.
Why? People don't read. They don't care that they could brick a $650 phone. They deserve it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i don't deserve anything. i made a mistake and forgot to take precaution. i'm not blaming anyone, i asked a simple damn question....so get off your damn high horse. LOL..... sigh.
fukenbiker said:
Thanks, I read up on getting root for MF3 OTA and it says right up front CAUTION THERE IS NO RECOVERY
and rooting looks like it's more complex, I remember the Android Debug Bridge, and I'm glad I was able to get in early with motochopper and then casual and I'm pleased with the GoldenEye Rom. Just a tap and a swipe bar in the TWRP recovery. I see how I dodged a bullet back in June when I froze AT&T Update service with Titanium Backup. I'm lucky. And it took me a long time to grasp all the terminology and what the difference is between root and getting a custom recovery, and I'm sure that it's not the amount of reading one does, but rather comprehension. That's why when I print in here I try not to leave anything out.
Whiz kids like yourself forget what it's like to wonder if there is a difference between installing a zip or flashing one and could care less on articulating the details you take for granted.
There's not a fix in the world for solidus636's handset cuz he blew the E fuse huh? Not sure what that is and barely understood it when I read about it.
I loathe AT&T. Now they locked the bootloader. What a bunch of creeps. I almost didn't get the S4 because of the shrunken SIM but I found an adapter so I can light up all those old phones in my gun safe. It's how I roll. I would never buy a handset you couldn't pull the battery on. And everytime I see a new connector plug I go on a rant about UL listed and deregulation. Instead of making a one size fits all battery, almost every device has a different shape size and fit.
Ok all done complaining now. Beg pardon for bending your ear. I think you like it tho, and will find something to be smart alec about.
Click to expand...
Click to collapse
i didn't blow the e-fuse. i messed up one single file within /system/framework/ and the moment an odin flash file is released with mf3 , even only the system.img will be the moment I can fix my device... but i asked if we could do this or not. seems it's bricked for now.
solidus636 said:
i don't deserve anything. i made a mistake and forgot to take precaution. i'm not blaming anyone, i asked a simple damn question....so get off your damn high horse. LOL..... sigh.
i didn't blow the e-fuse. i messed up one single file within /system/framework/ and the moment an odin flash file is released with mf3 , even only the system.img will be the moment I can fix my device... but i asked if we could do this or not. seems it's bricked for now.
Click to expand...
Click to collapse
You are educated and knowledgeable beyond my own level of intelligence. If I could help I would. If anyone comes up with a petition for a class action against AT&T for locking their bootloader I'm all in. Too bad you can't boot all the way up and get root explorer to fix your file name.
fukenbiker said:
You are educated and knowledgeable beyond my own level of intelligence. If I could help I would. If anyone comes up with a petition for a class action against AT&T for locking their bootloader I'm all in. Too bad you can't boot all the way up and get root explorer to fix your file name.
Click to expand...
Click to collapse
there is!
https://www.change.org/petitions/samsung-usa-at-t-unlock-the-bootloader-of-the-galaxy-s4-sgh-i337-2
sign it!
solidus636 said:
there is!
https://www.change.org/petitions/samsung-usa-at-t-unlock-the-bootloader-of-the-galaxy-s4-sgh-i337-2
sign it!
Click to expand...
Click to collapse
I signed it. Thanks for the link
solidus636 said:
there is!
https://www.change.org/petitions/samsung-usa-at-t-unlock-the-bootloader-of-the-galaxy-s4-sgh-i337-2
sign it!
Click to expand...
Click to collapse
I didn't sign it because I don't do "facebook". It would appear my wife just signed it. LOL
fukenbiker said:
I didn't sign it because I don't do "facebook". It would appear my wife just signed it. LOL
Click to expand...
Click to collapse
you don't need facebook to sign it.........
fukenbiker said:
You are educated and knowledgeable beyond my own level of intelligence. If I could help I would. If anyone comes up with a petition for a class action against AT&T for locking their bootloader I'm all in. Too bad you can't boot all the way up and get root explorer to fix your file name.
Click to expand...
Click to collapse
The only posts I have seen from you are trying to get people to file a class action lawsuit against AT&T and to start petitions. Why don't you either shut the hell up about it or do it yourself.
First:
AT&T does not have to provide unlocked bootloaders . Those are not open source. They can do whatever they damn well please with THEIR bootloaders. A lawsuit would be fruitless.
Second:
Stop trying to get people to do what you want. If you want it, do it yourself. If you are too lazy to do it, shut your mouth. You sit here and preach all this BS but are too lazy to even sign a petition that was linked to you. You act like you're 12. Only a kid would put forth so much talk but absolutely no action.
I will start reporting every post from you that has anything to do with you trying to get people to do what you want in regards to this topic, if i see one more. I and many others are tired of seeing it. You are spamming the forums with it.
OP Google the odin file you are looking for or use the search function here in the forums
Sent from my SPH-D710 using xda premium
graydiggy said:
The only posts I have seen from you are trying to get people to file a class action lawsuit against AT&T and to start petitions. Why don't you either shut the hell up about it or do it yourself.
First:
AT&T does not have to provide unlocked bootloaders . Those are not open source. They can do whatever they damn well please with THEIR bootloaders. A lawsuit would be fruitless.
Second:
Stop trying to get people to do what you want. If you want it, do it yourself. If you are too lazy to do it, shut your mouth. You sit here and preach all this BS but are too lazy to even sign a petition that was linked to you. You act like you're 12. Only a kid would put forth so much talk but absolutely no action.
I will start reporting every post from you that has anything to do with you trying to get people to do what you want in regards to this topic, if i see one more. I and many others are tired of seeing it. You are spamming the forums with it.
OP Google the odin file you are looking for or use the search function here in the forums
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
An EXCELLENT scolding! I KNEW you would find my prattle fodder for discussion!
You're dead wrong however, as I am busy.
I have a day job being a g*[email protected] lineman that I won't bore you with, but something up your self righteous research and document alley would be the web page that I constantly try to improve: http://lango.us
If they start the revolution, it might be without you and your own laziness, but I do not intend to be counted out.
So go ahead. Tell me to shut the hell up again.
I bet you're a profile picture of a Libtard.
fukenbiker said:
An EXCELLENT scolding! I KNEW you would find my prattle fodder for discussion!
You're dead wrong however, as I am busy.
I have a day job being a g*[email protected] lineman that I won't bore you with, but something up your self righteous research and document alley would be the web page that I constantly try to improve: http://lango.us
If they start the revolution, it might be without you and your own laziness, but I do not intend to be counted out.
So go ahead. Tell me to shut the hell up again.
I bet you're a profile picture of a Libtard.
Click to expand...
Click to collapse
Congrats on being nothing to me. I could care less how busy you are or what you do. I also noticed you brag about being a lineman... Cool story, bro. Another worthless piece of info. You sound like a conspiracy theorist. Everyone is out to get you, man. We gotta get this revolution rolling, bro. I don't even care to look at the link. I'm too busy with the real world. So... With all that said, shut the hell up. (see? I said it again.) No one cares. If you want to start a revolution, keep it off of XDA. This is not the place for your political agendas or views. This is not the place to get people to join your uprising against AT&T or anyone else for that matter. Take it to Facebook.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
google it
Do a search for" [AT&T][How To][FIX] Did you root MF3 then try to flash a custom recovery"
hopefully it works for you guys.
smcabete said:
Do a search for" [AT&T][How To][FIX] Did you root MF3 then try to flash a custom recovery"
hopefully it works for you guys.
Click to expand...
Click to collapse
This really did work, thanks! Only allows booting into the os and trying factory reset doesn't work but arty least I can use it again until a fix for mf3 is found.
Yup.. I fell right into that trap too... just happens when you think about it too much. Just be happy with your phone and live with it till a dev can make it better in the future.