So, I have successfully bricked my phone (not by choice). I am a long time WinMo user and I have never even come close to bricking a phone. Today was exactly one week from when I bought my first android phone and I bricked it.(not blaming android, I love android)
I have tried EVERYTHING, to no avail.
My phone is on the phone++!++computer screen.
So, first thing tomorrow morning, I am headed to the AT&T store for replacement (I will act dumb and get the phone).
My questions are -
1.Will my information (contacts,emails,etc.) on the phone be checked or in any way violated?
2.If they do find out that I had rooted the phone, after I have already walked out of the store, can they do anything about it?
1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".
TehDave said:
1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".
Click to expand...
Click to collapse
I have tried everything. I don't want to return this phone, but there is no option left.
None of the methods work and I am pretty experienced in this stuff. So, its not that I am messing up on the methods, its just that there was a batch of phones that had the key combos disabled.
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
I can tell you that by flashing ONLY the pit file in odin another user and myself were able to succesfully make the phone unresponsive to all buttons, all methods and all pulls of the battery. it literally turned into a brick...then again i would call this an illegitimate method after realized how simple it is now. as long as i can get power to the phone thou i have to agree ive been able to save it every time now
ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
Seriously?
I was up for six hours last night trying to fix the damn thing. I don't want to replace the phone just because I want to beat the system. I have never ran into problems when I am modding. I always figure it out, but when the phone is absolutely unresponsive to all keys, what am I going to do?
Anyways, this thread can be closed now.
That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216
seems pretty complicated to flash this phone. My last one-Nokia N900- is very easy to work with. It never get bricked.
alec5216 said:
That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216
Click to expand...
Click to collapse
I tried that too, nothing. I got it exchanged. No hassle.
AT&T store rep just said the phone will be factory reset and there is nothing to it.
Anyway thanks for the help folks, really appreciate it.
Lets hope, I don't bust this one because the phone I just got is also impervious to key combos. I tried getting into recovery (just for the heck of it), it didnt work with the keys, had to do it with "adb reboot recovery".
Related
Have been reading all the forums and had used the info here to put a custom ROM on my T-Mobile Wing. Unfortunately my Wing is now suffering a hardware problem and has to go back for a warranty replacement. This could obviously be a problem if it has a non-standard ROM on it. Because of this, I went ahead and grabbed the RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship.exe file via the threads and attempted to reflash my phone.
I am running the flash attempt from a physical Windows XP system. My phone is fully charged. I have an active partnership set up with the phone and active via ActiveSync. I start the flash process and the phone reboots into bootloader mode as expected. The flash process gets to 1% then the phone reboots into regular mode again and the RUU reports that the flash failed.
Am I missing something?
Update: apparently I was missing something. I had read the thread indicating the phone reboots at 1% and 30% (though mine only rebooted at 1%), but I assumed it would go back into the boot loader automatically which it didn't. On a hunch I tried forcing it into the boot loader and the RUU continued. Weird.
Have you HardSPLed your phone before? If you have, you have to bypass the SPL... Rumor goes, flashing the stock RUU WITH USPL will do this for you. I haven't tried it so I don't know if this will work or brick the device.
I had my phone picked up for warranty this very day. It was running Itje's latest ROM before the 6.1 update, but it totally died on my the other day. So now I'm hoping they won't mind too much about the hard-spl ing and the flashing and the overclocking *cough*
Good luck restoring your phone though. Maybe they won't care, I'm hoping for that
I basically took ivanmmj's advice and wrote a lil guide, I hope it gets sticky'd. http://forum.xda-developers.com/showthread.php?t=364543
DaMyth said:
I basically took ivanmmj's advice and wrote a lil guide, I hope it gets sticky'd. http://forum.xda-developers.com/showthread.php?t=364543
Click to expand...
Click to collapse
Glad to hear it worked. ^_^ I think that's the second account I hear of it working, so it must be something that DOES work.
Not to raise the dead but good thing I found this thread, worked or me too. Anyone know anything about the warranty replacements tmobile sends out? I'm assuming a refurbished model but anyone know the type o condition they are in?
The model that I got as a replacement, oh so long ago, has been working like a champ since I got it. It looked brand new, but then again, the original had problems not too long after I first got it, when the Wing was still a pretty new device.
Thats good to know, should only have to last me a month or two seeing how tmobile in their infinate wisdom lost the cell tower near my house a few months ago and contract is done on the 29th.... hello tilt!! (or touch pro )
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
I'm on Darky's ROM since 9.2 and I've been flashing different stuff with 100% success rate... So far.
My girlfriend also bought a Galaxy S (the I9000, just for info) and me, considering myself a "veteran flasher" (but in real life, still being a tutorial-following guide monkey) told her "Hey, you know what - I can make your phone ten times better, just give it to me overnight".
So I prepared the phone... factory reset, etc. The 3-button combo didn't work (hmm, strange) but I looked around for a solution anyway - found one involving Odin, ADB and updating the bootloader, but since a lot of people bricked their devices this way, I skipped it.
I got the phone to boot into download mode via ADB and then started the guide to instal Darky's Ressurection Edition. Connected to Odin, the phone was recognized and added, then I started it and Odin spat out an ERROR message, then the phone was stuck at the "black screen of death" (a phone and a PC connecting).
So... why the hell did this happen?
I've already flashed my own Galaxy S so I've done this maybe even twice... got drivers, Odin, everything! What went wrong and can I even fix this or I gotta buy a new phone?
you can probably use a jig to get the phone back to download mode.
buy one on ebay or make one yourself. theres plenty of guides online for that.
as for odin having an error im thinking you might have a corrupt file? try downloading it again.
can you go into recovery mode or any 3 button won't work?
But why did you just dont installed the 3 button method which gives you the change to flash other roms e.g.
Yes you risk to brick but you also risk but in my mind much bigger to brick your phone without 3 button so if something went wrong you have the change to go with the 3 buttons to the recovery menu...
Sent from my GT-I9000 using XDA App
Try getting the battery out for 1-2 seconds, put it back in and then try getting into download mode manually by holding first volume down+home and then also the power button.
If you can get into download mode, which is something I've found not to be pretty easy to erase, as it's independant from boot settings and files, all is still OK.
Yeah, I'll be out in the morning to buy the mats for a JIG, found a pretty easy guide how to make one, with pictures and everything.
The files being corrupt is something I didn't even think about, I'll re-download them if/when I manage to get the phone working.
Battery pull didn't do the trick, left it out of the phone for 4 hours, no dice.
After all, the phone is still under warranty and was recently 2.1 untill my gf updated it. Maybe I can tell that it's her fault, messing up Kies update or what? Then I'll get a free service/replacement, but I'll need a solid excuse to tell them. Any ideas? (yeah I know I'm an awful person but I can't afford a second Galaxy S, and the thought of giving her *my precious* because of my stupidity is just as awful)
rolfmao you made my day bro, my gf just bought a SGS as well but she saw me almost crying with the bricks i created, so as soon as i asked her if i could update her phone
she almost kicked me in the nutsack.
building a jig is pretty easy, you just need to practice touching the correct pins and you will be good to go.
as for the odin, it happends....i bricked my phone so many times
i just forced download mode and then reflashed with THE SAME FILES and it worked
my guess is that the connection is interrupted or something...causing it to abort or fail
FYI: Bricking means turning it to a brick, you can't revert from a "bricking"... Bad flash, ok! Black screen, ok! Brick, hum... if you can "unbrick", well, that's not bricking my friend!
All this to say the SGS is ALMOST unbrickable! With Jig, download mode, ADB, etc, there's so many way you can undo/redo things right!
You can say a lot of thing about the SGS, but the thing is made for developpers and flashers!
dikime said:
Yeah, I'll be out in the morning to buy the mats for a JIG, found a pretty easy guide how to make one, with pictures and everything.
The files being corrupt is something I didn't even think about, I'll re-download them if/when I manage to get the phone working.
Battery pull didn't do the trick, left it out of the phone for 4 hours, no dice.
After all, the phone is still under warranty and was recently 2.1 untill my gf updated it. Maybe I can tell that it's her fault, messing up Kies update or what? Then I'll get a free service/replacement, but I'll need a solid excuse to tell them. Any ideas? (yeah I know I'm an awful person but I can't afford a second Galaxy S, and the thought of giving her *my precious* because of my stupidity is just as awful)
Click to expand...
Click to collapse
Build a jig and do it yourself. Then if you run into trouble in the future - hey! you have a jig, no problem. Warranty situation is a bit iffy, sometimes they see that you screwed it up yourself....
t1mman said:
FYI: Bricking means turning it to a brick, you can't revert from a "bricking"... Bad flash, ok! Black screen, ok! Brick, hum... if you can "unbrick", well, that's not bricking my friend!
All this to say the SGS is ALMOST unbrickable! With Jig, download mode, ADB, etc, there's so many way you can undo/redo things right!
You can say a lot of thing about the SGS, but the thing is made for developpers and flashers!
Click to expand...
Click to collapse
Yeah, I know, but I read in another thread that if I get this screen AND can't get into download mode then I'm toast. That's why I used the word brick.
I decided I'll send her return the phone, equipped with her cutest and n00biest face so that they won't even think that there's a real idiot involved (me). And if they don't fall for that, I'll build a jig and try myself.
THIS IS WHY I HAVE NO GIRLFRIEND!!!
nah j/k!
But man... I didn't think you could actually brick the SGS. I mean, I always screw my rom up somehow, but the 3 button combos always work... Guess I'm just lucky... I'll try to be more careful from now on lol.
You bricking your SGS has taught me a valuable lesson! So thanks for that ^^
Sinotek said:
THIS IS WHY I HAVE NO GIRLFRIEND!!!
nah j/k!
But man... I didn't think you could actually brick the SGS. I mean, I always screw my rom up somehow, but the 3 button combos always work... Guess I'm just lucky... I'll try to be more careful from now on lol.
You bricking your SGS has taught me a valuable lesson! So thanks for that ^^
Click to expand...
Click to collapse
LOL, np
Anyway, I just sent her to return the phone, maybe it's a common problem because the guy there didn't even listen to her explaining the crude story I made her tell ("PC froze and then rebooted itself while updating" - yeah right!).
They said it'll be ready next week (hopefully).
This also thought me a lesson - maybe even two.
1) Never try crazy stuff on a Galaxy S without 3 button combo working properly.
2) Always have a JIG ready for use
When she gets it back next week I'll see if the 3BC works and if it does - yeah, I'll try to flash a custom ROM again
Thanks for this highly amusing thread lol the moral is.....don't mess with the womans phone if you want to live AND love
GTi 9000 insanity007/insane glitch
dikime said:
I decided I'll send her return the phone, equipped with her cutest and n00biest face so that they won't even think that there's a real idiot involved (me). And if they don't fall for that, I'll build a jig and try myself.
Click to expand...
Click to collapse
Best I've heard all day
But I must ask - how the ... did you manage to talk her into returning the phone herself...?? If that would have been me screwing up my gf's phone, she wouldn't let me in the house until I had fixed the darn thing myself.
I gave her mine - already heavily tweaked and loaded it with games like Plants vs. Zombies and Let's Create! : Pottery (she just loves that game). Plus I equipped MY cutest and n00biest face when I showed up to tell her the *cough* results.
This made my day. Apparently I thought only girls can put on a cute face and disarm anyone. LOL!
Regarding the brick, what I did was to repeatedly tried doing the 3BC then held all of it until the brick icon goes to download mode. Held it for 5minutes. No jig needed! If you keep it held down for some time, the phone resets itself. MAKE SURE THAT YOUR SGS IS CONNECTED VIA USB!
Good luck!
Sent using this XDA App thing from my awesome SGS
i think this is why all flash posts say make sure 3 button combo is working before you start... but I have had to use a jig to get mine back from the brink/brick once, almost made me cry as i needed my phone in 2 hours to meet up with friends
Oh yea... you will have to let us know what they said when she took it back. I am curious if they ask questions about how it got there and if they believed her... don't want to make things difficult in there but I know some companies who have products that are highly customisable (if "hacked like this") are suspicious of most software related problems
But getting the soft-bricked phone back to a new state with a new ROM would have been a great gift while returning the phone!
Dont u think so?
The whole idea was to get rid of the stock firmware and flash something epic ( in my case - Darky's 9.2).
They didn't ask her anything at the service centre so I/we got lucky with that, and even better - I formatted the internal SD card before flashing so even if the phone isn't hard bricked there won't be any evidence of software modifications (because I rooted the phone to backup everything with TB and to be able to put it in download mode via ADB).
Next week I'll report what happened and if I finally managed to flash a custom ROM (if not, expect a new thread: "Can't believe I bricked my Galaxy S... again!")
So my phone technically works but everything force closes the second I get into the OS so its basically inoperable.
I know exactly what caused the issue, I was rooted and I saw a service that an app called myscript had installed, even after I had un-installed the app itself. I figured I'd kill it, and it caused my phone to have pen input seizures every three seconds. Reinstalling the app, and factory resetting did not help. I have tried to recover the phone but all my efforts have failed thus far (including kies 3 emergency firmware recovery).
Reference for my original problem:
http://forum.xda-developers.com/showthread.php?t=2469681
So I need to get back to stock by following this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
but I can't get past the "detect phone" step. Heimdall keeps crashing despite having correctly installed the drivers. I made a post in that thread but I doubt that will garner any help at all, so I figured I'd make a thread begging for help. I've had this phone a scant few days! Please help!
Any other known method of getting back to stock would be acceptable as well.
-Luceid
Luceid said:
So my phone technically works but everything force closes the second I get into the OS so its basically inoperable.
I know exactly what caused the issue, I was rooted and I saw a service that an app called myscript had installed, even after I had un-installed the app itself. I figured I'd kill it, and it caused my phone to have pen input seizures every three seconds. Reinstalling the app, and factory resetting did not help. I have tried to recover the phone but all my efforts have failed thus far (including kies 3 emergency firmware recovery).
Reference for my original problem:
http://forum.xda-developers.com/showthread.php?t=2469681
So I need to get back to stock by following this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
but I can't get past the "detect phone" step. Heimdall keeps crashing despite having correctly installed the drivers. I made a post in that thread but I doubt that will garner any help at all, so I figured I'd make a thread begging for help. I've had this phone a scant few days! Please help!
Any other known method of getting back to stock would be acceptable as well.
-Luceid
Click to expand...
Click to collapse
I read about another guy who just did the same thing, but all is not lost.
He sold his N3 on the interweb for "parts" last Monday and got $110 and his deductible was $200 so it only cost him $90 to get a new one, so don't fret.
XiphoneUzer said:
I read about another guy who just did the same thing, but all is not lost.
He sold his N3 on the interweb for "parts" last Monday and got $110 and his deductible was $200 so it only cost him $90 to get a new one, so don't fret.
Click to expand...
Click to collapse
Eh I'd rather just get my "like new" replacement for free. Everything is still official and knox is 0x0. Still I'd prefer to fix this is anyone knows how.
used this thread to try and return to stock:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
My **** turned off, now it wont turn on period. Cant go into any kind of download mode NOTHING. I have no warranty, I got the phone off the street. Tried to flash a custom rom did it wrong then tried to return it to stock because I didnt make a backup. I'm ready to throw it at a wall.
It WAS a boost moto e4 plus owens xt1776
If it won't turn on, there's not much you can do. The battery is technically removable, so you COULD try removing it and putting it back in, but I doubt it will help. You might want to see if Motorola will repair it. It's a longshot, but they might help you. I wouldn't tell them you bought it off the street. Just say you don't have a receipt.
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
ATTACK said:
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
Click to expand...
Click to collapse
You're right, I forgot about that one..
ATTACK said:
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
Click to expand...
Click to collapse
If he temper any of the device partition than probably it will be a soft brick and should be resolved by the service center guy like i did this before three times with my Moto E4 and it won't turn on. No fastboot mode, no recovery, Just the notification light when connecting to a power source and nothing else. I also got the new IMEI number.
TheHitMan said:
If he temper any of the device partition than probably it will be a soft brick and should be resolved by the service center guy like i did this before three times with my Moto E4 and it won't turn on. No fastboot mode, no recovery, Just the notification light when connecting to a power source and nothing else.
Click to expand...
Click to collapse
We don't know if he messed with his partitons, though. Without further details as to what he did, all we're doing is guessing.
Sorry about my delay had some stuff go down. Uhm, I followed that thread, ran the commands listed, used a sprint factory instead of a boost, from what i read in that thread, it should have worked. But now I dont even get a notification light when i charge.
I'm having the same problem as him and I feel like I'm making some progress, but I still can't fix it. Here's my posts on what I found from that thread. They are probably better suited here anyway. https://forum.xda-developers.com/showpost.php?p=76459007&postcount=21
doodalydoo said:
I'm having the same problem as him and I feel like I'm making some progress, but I still can't fix it. Here's my posts on what I found from that thread. They are probably better suited here anyway. https://forum.xda-developers.com/showpost.php?p=76459007&postcount=21
Click to expand...
Click to collapse
Don't forget that the OEM files are labeled differently for Boost Mobile users, messing that labeling up during fastboot will cause it not to boot as well..
bcrichster said:
Don't forget that the OEM files are labeled differently for Boost Mobile users, messing that labeling up during fastboot will cause it not to boot as well..
Click to expand...
Click to collapse
I have the carrier unlocked version. I think the way I bricked my phone is that I OTA updated my phone and then tried to revert back to stock. I've seen a video on youtube of somebody who did the exact same thing and was able to unbrick his phone. I think the main problem right now is I can't find the right firmware files to use in QFIL. The stock firmware zips don't have the right files that QFIL needs