[Q] Bricked or not - One (M8) Q&A, Help & Troubleshooting

So A new update for HTC sense came out this morning. And now my phone refuses to connect to wifi I already reset it through the soft ware then I did a Hard reset using the power button and still. Won't connect to a wifi help????
Also the device is now never able to mount and make the storage accessible

M1keILL said:
So A new update for HTC sense came out this morning. And now my phone refuses to connect to wifi I already reset it through the soft ware then I did a Hard reset using the power button and still. Won't connect to a wifi help????
Also the device is now never able to mount and make the storage accessible
Click to expand...
Click to collapse
You are not even close to being bricked.
You'll have to give me more information if I'm going to be able to help you. I assume you're rooted. Are you running a custom ROM or stock? Custom recovery? Have you updated your firmware by flashing a file?
When did you first notice you didn't have wifi? Did you do any mods around that same time?
Don't worry dude, we'll get this fixed.

xunholyx said:
You are not even close to being bricked. .
Click to expand...
Click to collapse
Yeah I don't know where these guys get their definition of "bricked" from. Phone still works but no wifi "BRICKED!!!". As far as I'm concerned a device is "bricked" if it's about as useful as a "brick" in other words, it ain't doing sh!t. You can only use it to keep the door from slamming shut, or as a paper weight.
Completely dead = Bricked
Can go into recovery/bootloader = Not even close to anything related to any "brick"

BerndM14 said:
Yeah I don't know where these guys get their definition of "bricked" from. Phone still works but no wifi "BRICKED!!!". As far as I'm concerned a device is "bricked" if it's about as useful as a "brick" in other words, it ain't doing sh!t. You can only use it to keep the door from slamming shut, or as a paper weight.
Completely dead = Bricked
Can go into recovery/bootloader = Not even close to anything related to any "brick"
Click to expand...
Click to collapse
Not rooted nothing custom. I am bone stock sprint htc one m8. It gave me a prompt to update sense then it stopped working

M1keILL said:
Not rooted nothing custom. I am bone stock sprint htc one m8. It gave me a prompt to update sense then it stopped working
Click to expand...
Click to collapse
That is super weird dude. I would call your service provider or HTC. If you call them on a landline, they can probably push a fix directly to your phone. If you don't have a landline, they will guide you through the steps to fix it.
If it is having issues when it is unmodded and because of an OTA, you don't want our advice. You would have to modify your phone and void your warranty.
There may be/probably is a solution that someone here has that will fix it, but your best bet with 100% stock is to go to the source for a fix.
Good luck buddy!

xunholyx said:
That is super weird dude. I would call your service provider or HTC. If you call them on a landline, they can probably push a fix directly to your phone. If you don't have a landline, they will guide you through the steps to fix it.
If it is having issues when it is unmodded and because of an OTA, you don't want our advice. You would have to modify your phone and void your warranty.
Good luck buddy!
Click to expand...
Click to collapse
Alright thanks i'll try tomorrow then

M1keILL said:
Alright thanks i'll try tomorrow then
Click to expand...
Click to collapse
Let me know how things go. You can quote me here (so I get a notification), or send me a PM. I'm interested in hearing about your results and the fix, in case anyone else on this forum comes across these same problems.

xunholyx said:
That is super weird dude.
If it is having issues when it is unmodded and because of an OTA, you don't want our advice. You would have to modify your phone and void your warranty.
!
Click to expand...
Click to collapse
I've seen a couple cases of OTA killing WiFi lately. Most of us are used to seeing broken WiFi as a result of flashing a custom ROM and outdated firmware, so yes its a bit odd to see it after an official OTA.
I agree, that aside from trying a factory reset, the OP shouldn't tinker with a phone that is stock and still on warranty. Just contact your warranty department for a repair/replacement.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
M1keILL said:
I already reset it through the soft ware then I did a Hard reset using the power button and still.
Click to expand...
Click to collapse
"Reset" or even "hard reset" is a bit vague. Did you do a factory reset to delete user data, or just rebooted the phone? Factory reset will sometimes clear up random bugs after an OTA.

Sprint has basically said that they don't know what's wrong with it and I need to send it to them.

M1keILL said:
Sprint has basically said that they don't know what's wrong with it and I need to send it to them.
Click to expand...
Click to collapse
For a stock device (not modded) if you've tried a factory reset, and the issue persists, they I would agree that warranty service is the best solution.

Related

[Q] Inaccessible OS after (Slimbean) ROM setting mistake

Long story short, with above average ROM knowledge, and two previous successful flashes under my belt, I flashed Slimbean JB 4.2.1 Beta1 for my Sprint GS3 SPH-L710, and all was quite fine until I messed with menu/security/SIM PIN. Though I thought I was setting it for extra phone security, I actually implemented an unknownst-to-me feature that upon the following reboot, the phone requested a PUK code for a now-locked SIM card (my phone doesn't have a SIM card by the way).
After a long CS call to Sprint, including International Sprint, I was told to go to a local store. The short part of this story is that no one has been able to help. You see, since I DON'T have a SIM card, I have no ID to provide to Int Sprint for them to find a PUK code for me to enter. Although, I've had many troubles in doing so, I have since been able to reset the phone to stock factory settings; HOWEVER, this has NOT removed the PUK code screen, which prevents me from using the phone at all.
I am out of ideas of things to change, alter or fix to get rid of this issue. I have tried CWM and TWRP solutions with no success. In a sense, although I can do anything with the phone - recovery, download, flashing - except actually use the OS, I would consider this phone as useless as if it were bricked at this point. Any ideas from out there would be appreciated. Thanks.
Have you tried Odin
Sent from my SPH-L710 using xda premium
I would try flashing an odin stock tar, then re-rooting.
Nothing in recovery, such as a full wipe, factory and system reset fixed the problem?
This is good info to know. Please let us know of a solution if you find one - good luck!
Have you tried Odin
Click to expand...
Click to collapse
I can use and have used Odin - no problem. I have full access to the device, just none to the OS.
I would try flashing an odin stock tar, then re-rooting.
Click to expand...
Click to collapse
I have successfully returned boot, system and recovery to stock, but this has not resolved the overriding issue. I don't believe I have tried to re-root since doing so. Perhaps that is worth a try.
EDIT: rerooting after Odin stock flash did not help the issue.
Nothing in recovery, such as a full wipe, factory and system reset fixed the problem?
Click to expand...
Click to collapse
I am afraid none of these tasks worked. This issue must reside somewhere recovery can't get to, and only the OS can. The software is likely built so that a regularly performed task can't override a security issue - even if it is a false issue.
GRazor71 said:
I can use and have used Odin - no problem. I have full access to the device, just none to the OS.
I have successfully returned boot, system and recovery to stock, but this has not resolved the overriding issue. I don't believe I have tried to re-root since doing so. Perhaps that is worth a try.
EDIT: rerooting after Odin stock flash did not help the issue.
I am afraid none of these tasks worked. This issue must reside somewhere recovery can't get to, and only the OS can. The software is likely built so that a regularly performed task can't override a security issue - even if it is a false issue.
Click to expand...
Click to collapse
Have you tried wiping internal storage through twrp? I saw a solution for wiping encryption by wiping internal storage through twrp,
Mcluvin
Sent from my SCH-I800 using Tapatalk 2
Have you tried wiping internal storage through twrp?
Click to expand...
Click to collapse
Tried it last night. Though promising, this too failed.
GRazor71 said:
Tried it last night. Though promising, this too failed.
Click to expand...
Click to collapse
Do you have insurance on your phone?
Sent from my SCH-I800 using Tapatalk 2
Do you have insurance on your phone?
Click to expand...
Click to collapse
Nope.
This happened on my nexus and I had to get a new phone because your phone is basically locked at that point and I did try random codes and one of them worked but my lte didn't work after that neither did MMS so I just kept calling sprint non stop for a replacement and they finally gave in and gave me an exchange for free
Sent from my SPH-L710
jazz995756 said:
This happened on my nexus and I had to get a new phone because your phone is basically locked at that point and I did try random codes and one of them forked but my lte didn't work after that neither did MMS so I just kept calling sprint non stop for a replacement and they finally gave in and gave me an exchange for free
Click to expand...
Click to collapse
Did you have to contact International Sprint CS or just regular? How long exactly did you badger them? Had you flashed the phone, increasing your Binary count? If so, did Sprint not hit you with a bill after replacement? Just curious, as I have really upped my count due to recovery flashes to try to fix the phone. I think I can still get a Samsung E-ticket through Sprint store for about $37.00. But again, I am concerned about the flash count, and being unable to reset it. Perhaps I should do what I can to really brick it once and for all before I turn it over.
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
ChaseBroyles said:
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
Click to expand...
Click to collapse
Awesome! Thanks, will give it a go.
ChaseBroyles said:
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
Click to expand...
Click to collapse
I don't think this will work seeing as he's already flashed an odin stock tar which brought the phone back to stock everything. :/
mstrmscn said:
I don't think this will work seeing as he's already flashed an odin stock tar which brought the phone back to stock everything. :/
Click to expand...
Click to collapse
He wanted to reset the flash counter and go to pure stock so he could take it to the Sprint store.
He wanted to reset the flash counter and go to pure stock so he could take it to the Sprint store.
Click to expand...
Click to collapse
Correct, and it worked like a charm. Thanks again!!!!!
Handsfree Activation?
I don't think Sprint even implements that rule anymore so he should definitely be fine. Have you tried handsfree activation ------>
http://forum.xda-developers.com/showthread.php?t=1670131
Maybe give that a whirl. I believe you must be on stock tw for this to work effectively which it sounds like you should now be on.
On second thought, your phone may not even allow you get as far as being able to dial the activation number, but just thought I'd throw it out there.
RS7JR said:
I don't think Sprint even implements that rule anymore so he should definitely be fine. Have you tried handsfree activation ------>
http://forum.xda-developers.com/showthread.php?t=1670131
Maybe give that a whirl. I believe you must be on stock tw for this to work effectively which it sounds like you should now be on.
On second thought, your phone may not even allow you get as far as being able to dial the activation number, but just thought I'd throw it out there.
Click to expand...
Click to collapse
Yeah, I don't have any access to the phone OS whatsoever. Sprint tech has it now; doing some kind of process which includes a 40-minute file extraction and a 30+minute flash. Perhaps that will finally reset everything. If not, Sprint has already said it will then replace the phone.
Received a new GS3 today and I'm back in the game. Thank you to everyone who tried to assist me. In the end, no one on any forum, not Sprint, and not even Samsung could correct the original phone problem. The moral - be very cognizant and careful when flashing any CMDA variant of a native GSM ROM, as there could be settings within them regarding the SIM cards that GSM's do have, but CMDA's do not, or perhaps other harmful settings if messed with or changed. This warning is really nothing new to anyone flashing custom ROM's; it's simply another hard-learned lesson by one person whose adding more truth to the usefulness of such warnings.

[Q] Help with my broken phone please!

I bought a Galaxy S Glide (I think the same as the Blaze) from an outlet in Hong Kong on import from Canada (on boot it says "Rogers" so I can assume it's from Canada).
After using it for a week it suddenly stopped using the network and said that I need a lock code.
I went back to the shop where I bought it and they said they couldn't do anything immediately and would I like a replacement, which seemed like a nice thing to do.
However, after a couple of days I notice a glitch on the screen happen a couple of times.
I refused to believe it was a big problem (because it was my new phone right!) within a week the screen started to totally crash to the point that it would freeze in the boot up process.
You can see a picture attached of how the screen looks after I managed to do a hard reset.
When it starts to go like this, you cant do anything with it.
The guy at the shop wont change it or refund it, he claims I dropped it.
Samsung Hong Kong don't support it because it's from Canada and the only shop that knows what to do with it is the guy that sold it to me.
I'm taking the guy to the small claims court, but I'd rather have a fixed phone.
Any ideas please?
Thats happen to me, is a problem with the roger version. Everything in internet say the problem is hardware, but now mines works perfect. So, is like a bug in the rogers, maybe hardware problem, but if can be fixed with software i dont think so.
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
links
lorddavid said:
........... problem with the roger version. Everything in internet say the problem is hardware, but ..............
Click to expand...
Click to collapse
I have searched for more information about this problem, but couldn't find anything, do you have any links to anything?
Thanks again for your help.
they dont say exactly, but if you see users with similar problem, they have rogers version, at least all the user that i see with this problem.
Just do what i say, install ICS; and the problem will solve.
Follow this http://www.theandroidsoul.com/andro...ich-update-for-att-captivate-glide-i927uclg9/ for installing the one click.
Sent from my SGH-I927 using xda app-developers app
lorddavid said:
Thats happen to me, is a problem with the roger version. Everything in internet say the problem is hardware, but now mines works perfect. So, is like a bug in the rogers, maybe hardware problem, but if can be fixed with software i dont think so.
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
Click to expand...
Click to collapse
I strongly doubt this, that looks and sounds like a hardware fault. But hey, if there's no warranty option, you've got nothing to lose...
-E- FWIW, I would boot it into download mode, and let it sit on that screen for an hour. Then plug it into your computer and make sure Odin sees it. If it hangs while in download mode DO NOT FLASH ANYTHING. You REALLY don't want your phone to hang mid-bootloader-flashing, that's an automatic fullbrick...
roothorick said:
I strongly doubt this, that looks and sounds like a hardware fault. But hey, if there's no warranty option, you've got nothing to lose...
-E- FWIW, I would boot it into download mode, and let it sit on that screen for an hour. Then plug it into your computer and make sure Odin sees it. If it hangs while in download mode DO NOT FLASH ANYTHING. You REALLY don't want your phone to hang mid-bootloader-flashing, that's an automatic fullbrick...
Click to expand...
Click to collapse
That was all say, but, in odin my glide never freeze, only freeze while booting or charging too. But not in odin. And right now is working without any screen freeze.
lorddavid said:
users with similar problem, they have rogers version, at least all the user that i see with this problem.
Click to expand...
Click to collapse
So you have seen others with this problem? Where have you have seen these?
lorddavid said:
Just do what i say, install ICS; and the problem will solve.
Click to expand...
Click to collapse
Can this be rolled back ?
hkcharlie said:
So you have seen others with this problem? Where have you have seen these?
Can this be rolled back ?
Click to expand...
Click to collapse
If the device is no more under warranty, I would say trying this would not harm the device anymore. Also this is a samsung released update so nothing unofficial about it.
Sent from my SGH-I927 using xda app-developers app
if you search in internet about freeze problem in glide you will see. Can be roll back with odin. But, if you have no warranty on your device, you dont have nothing to lose, and much to win if the problem solve
My brother had this same problem on his glide (bought at newegg). I got him to install galaxym unlock (galaxsim? Something like that), and you purchase an inapp unlock for $3, and it runs, reboots your phone and you regain unlock. They claim its permanent. So far my brother didnt get locked again.
Is cheap, fast and you can also see in the reviews that there are more glides that used it and worked.
Hope this helps!
Sent from my SGH-I927 using Tapatalk 2
luquiyahni said:
My brother had this same problem on his glide (bought at newegg). I got him to install galaxym unlock (galaxsim? Something like that), and you purchase an inapp unlock for $3, and it runs, reboots your phone and you regain unlock. They claim its permanent. So far my brother didnt get locked again.
Click to expand...
Click to collapse
This helped with the frozen screen as shown in the picture?
thats for unlock, is possible that your phone will lock again when update to ICS. my phone was too from newegg and is rogers, thats why i say is a problem with rogers version.
Do what i tell you, you have nothing to lose
lorddavid said:
thats for unlock, is possible that your phone will lock again when update to ICS. my phone was too from newegg and is rogers, thats why i say is a problem with rogers version.
Do what i tell you, you have nothing to lose
Click to expand...
Click to collapse
Thanks for thinking about my problem, but this solution misses one very big point, the phone that was locked was changed for the phone that has a screen that doesn't work.
I do not have the locked phone any more.
probably will lock again after you flash ICS via odin, thats happen to me. Is not a screen problem, again, if you want to try to solve, do what i say before.
I have the exact same problem, was just about to post in the other thread about this: http://forum.xda-developers.com/showthread.php?t=1953672
Bought my phone from Amazon US marketplace about a month ago (but live in the UK), and suddenly the phone did that on start up one day. However, I agree with lorddavid, it is not a hardware fault as it does not freeze in download mode. Samsung service centres won't repair as it does not have a UK warranty, and although I can get a refund by returning I would rather have a working phone.
lorddavid said:
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
Click to expand...
Click to collapse
Was very happy to read this, seems like I'll have to try it. Have been putting it off as it will wipe my phone which I did not want to do just yet - I have a lot of photos and clips which I can't exactly back up as it does not boot normally. Really annoying. Any way to access these/back up before flashing?
And another question, that ICS update is the first leaked one which carried a few bugs (as did the official UCLH2 one) - can I install the fixed UCLJ3 straight away? And do I need a rooted phone in the first place? In Rawr0w0's initial post it seems to suggest I do. Sorry for all the questions, and thanks in advance.
dont remember, i think is the UCLH2, and i think that there was a odin flashable of the latest version (with bug fixes), you can try that (but dont know where download it :/ )
Do you have the photos in your internal storage? i think if you flash with one click, it will delete it, but if you flash the firmware via odin, it doesnt delete it (but i am not 100% sure)
And no, you dont need root to install roms via odin
This is UCLH2 without one click
http://androidromupdate.com/2012/09...-firmware-upgrade-official-kiesota-stock-rom/
And here is the latest version with bug fixes (like keyboard light)
http://androidromupdate.com/2012/11/10/i927uclj3-new-ics-4-0-4-for-samsung-sgh-i927-captivate-glide/
These are the officials. But the second link i never try it to flash because when i has the problem there wasnt that version
Thanks, yeah that's where I was getting the files from, I'll try it tonight, will probably go for the second link, the UCLJ3 rom.
lorddavid said:
And here is the latest version with bug fixes (like keyboard light)
These are the officials. But the second link i never try it to flash because when i has the problem there wasnt that version
Click to expand...
Click to collapse
YES WAHOO!! My phone works! Thank you for the advice! I mainly got it from the other thread but without having read your attempt at flashing I would never have tried it - I'm so happy! I managed to make a back up and copy my media via CWM anyway, but everything was still on there including all my texts and whatsapp messages, and now I have ICM 4.04 too!
Phew I thought I would have to send it back, get a refund and order another one which is a massive pain and lose everything on my phone.
Hkcharlie, you need to try this!
lyricalwax said:
YES WAHOO!! My phone works! Thank you for the advice! I mainly got it from the other thread but without having read your attempt at flashing I would never have tried it - I'm so happy! I managed to make a back up and copy my media via CWM anyway, but everything was still on there including all my texts and whatsapp messages, and now I have ICM 4.04 too!
Phew I thought I would have to send it back, get a refund and order another one which is a massive pain and lose everything on my phone.
Hkcharlie, you need to try this!
Click to expand...
Click to collapse
thats cool Enjoy the phone, is a great phone

[Q] Greetings, I understand I have a hard brick?

I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Jtag
Hey buddy i recent hard bricked mine last month got it back today PM this guy tomy1986.nt only charged 25$ and had it back in 7 days sucker working good now hes in texas only cost me 5.80$ shipped from Phx Az hope that helps Sounds like a defint hard brick!!!
JahJahLoO said:
I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Click to expand...
Click to collapse
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Praise!
tomy1986.nt said:
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Click to expand...
Click to collapse
All praise Tomy for his swift and kind work in helping a poor Samaritan. Thoust good deed shant go unnoticed.
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
-DarkKnight- said:
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
Click to expand...
Click to collapse
Good morning guys
tomy1986.nt said:
Good morning guys
Click to expand...
Click to collapse
How would I prevent my device from getting bricked?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
Do not flash modified Rom. :laugh:
tomy1986.nt said:
Do not flash modified Rom. :laugh:
Click to expand...
Click to collapse
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
-DarkKnight- said:
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
Click to expand...
Click to collapse
Alway flash phone with Stock rom.
tomy1986.nt said:
Alway flash phone with Stock rom.
Click to expand...
Click to collapse
What about custom ROMs like cm10.1 or JediMindTrick?
I'M BATMAN
The note 1 SGH-i717 of Keith_Dallas,TX member has already fixed today give it back only about a hours.

Need to completely reset phone back to box settings for resale.

As the title says. I'm selling this phone (not for performance issues, just I want the iPhone ), and I need a step-by-step
guide on how to COMPLETELY wipe it. No logs, nothing. Back to original out-of-the-box phone. Thank you!
Here you go.
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
kgs1992 said:
Here you go.
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
Click to expand...
Click to collapse
Will this completely remove any hidden files that may have my personal information?
ohsn said:
Will this completely remove any hidden files that may have my personal information?
Click to expand...
Click to collapse
Performing a full data format with a custom recovery multiple times will leave no personal information. Then you can go do your restore to stock ROM
ohsn said:
As the title says. I'm selling this phone (not for performance issues, just I want the iPhone ), and I need a step-by-step
guide on how to COMPLETELY wipe it. No logs, nothing. Back to original out-of-the-box phone. Thank you!
Click to expand...
Click to collapse
Is this your first phone? First android phone? I mean a quick google search would of told you how to reset as well. Also factory reset is just that a factory reset that puts your phone back to factory specs like when you first got it. Also better information in your post would of been to let us know if you were rooted or not and not your bad phone purchasing choice.... j/k not really LOL
Hope you got it all sorted out if not let us know we will be more than happy to send you off the right way :good:
playya said:
Is this your first phone? First android phone? I mean a quick google search would of told you how to reset as well. Also factory reset is just that a factory reset that puts your phone back to factory specs like when you first got it. Also better information in your post would of been to let us know if you were rooted or not and not your bad phone purchasing choice.... j/k not really LOL
Hope you got it all sorted out if not let us know we will be more than happy to send you off the right way :good:
Click to expand...
Click to collapse
This is my first android phone, yes. It was rooted as well. I'm having a problem resetting though. I oem locked, flashed to stock recovery, and tried to do the adb usb thing. However, it keeps saying that it cannot read file. Please help! I reinstalled the drivers already. Thank you!
ohsn said:
This is my first android phone, yes. It was rooted as well. I'm having a problem resetting though. I oem locked, flashed to stock recovery, and tried to do the adb usb thing. However, it keeps saying that it cannot read file. Please help! I reinstalled the drivers already. Thank you!
Click to expand...
Click to collapse
did you do all this after flashing a stock rom?
playya said:
did you do all this after flashing a stock rom?
Click to expand...
Click to collapse
No. I followed exactly how the video said above.

getting "your device is corrupt and cannot be trusted pixel"

So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.

Categories

Resources