I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
absoluterebirth said:
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
Click to expand...
Click to collapse
I haven't screwed this phone up but I remember when I first started rooting phones I bricked my Vibrant (Galaxy S). I think I bricked it because I flashed the wrong radio or something. After that I have never bricked another phone. **Knock on wood**
Now I take extra caution and read extensively before rooting, flashing Roms, kernels etc.
sent from my neXus 5
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
eastpac said:
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
Click to expand...
Click to collapse
Yeah, ripping cables is probably not going to turn out "all good". Just my opinion
markdapimp said:
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
Click to expand...
Click to collapse
Please accept this Thanks as your post is very accurate and straight to the point.:good: Many of us have had that experience before whether it's forgetting to charge it over night by not plugging it into a charging source or it running out of battery power from heavy/extented usuage and not being able to charge it immediately after.:highfive:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
FuMMoD said:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same!
Sent from my Nexus 5 using Tapatalk
I've only totally bricked one device, that was a sprint HTC evo (og evo). I got a replacement device via insurance and due to new firmware, I bricked it trying to root it/set s-off. No fix possible, only a new phone.
As far as nexi, nexus 5 specifically, I've soft bricked it a ton of times. But, one of the reasons I love the nexus brand, its never taken any more than a nandroid restore or only once a revert to stock. Unless you Dev test (and knowingly flash untested fw) or just start randomly picking zips and flash a modem or boot loader from a different device I've found it damn near impossible to make a nexus device unrecoverable.
I did initially flash the multi-boot mod w an incompatible ROM (beanstalk) and a kernel that really didn't like the multi-boot idea either (don't remember which ver of which kernel ATM). I was stuck on the "Google" boot loader screen for hours til I tried flashing a different ROM (which also changed the kernel) and trying again. Frustrated the hell out of me, kept phone unusable for almost a whole day, and wasted a ton of my time due to my laziness to read the whole thread.
Best advice ever given on XDA, whether you are a novice/learning/a noob or a android pro many years of experience or even a skilled developer.....
ALWAYS, ALWAYS, ALWAYS... did I say ALWAYS read the whole op or even better whole op and hopefully 90%+ of the thread before you try something you are unsure of.
Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2
helioXverse said:
As far as nexi
Click to expand...
Click to collapse
Nexuses
Had the device perfectly set-up, with a few twrp backups as well and then for no reason...moved those backups from the device to the pc (probably in order to free some space). Then in a sequence of screw-ups, downloaded Flashify and wiped the cache and and dalvik cache from within the app (thinking it would be cool)...AND...bootloop! No backups...nothing! Booted to recovery...wiped cache/Dalvik the usual way, still nothing! Wiped data...nothing! Couldn't get ADB to work in the recovery. Finally -> Bootloader -> Fastboot Flash Stock ROM!
Did not stop though. in the next 5 minutes I was back with custom recovery, root and Titanium backup...ready to get back the device in shape (done and dusted as I type )
Reading the undervolting thread I decided to go -75 across the board. I succeeded but then tried to push it lower. Bootloops occurred. Backup copied back to SD card from PC failed to restore (said data failed. This was my first time restoring a ROM on the Nexus 5. If someone has insight as to why this happened it would be appreciated). Decided to go aosp and flash Rasta + trinity kernel but for some reason my mobile data wouldn't activate nor could I update PRL or profile by clicking on the usual option even after reboot and continuously clicking. Now I'm just getting my phone back to the original state it was in before I screwed up my UV values. Cataclysm + ElementalX #Life of a Phone Nerd
Sent from my Nexus 5 using XDA Premium 4 mobile app
gee2012 said:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
Click to expand...
Click to collapse
I actually used a toolkit to return mine back to stock after i shipped it out to LG for repair after my son dropped. It was much easier for me than to write out the commands. took me about 10 minutes and that was because I locked the bootloader before flashing a zip. and i had to go back yada yada but worked out fine.
Screwed up 2 Galaxy S2's, first one because I didn't pay close enough attention to the brickbug, second one because it just died... Due to the brickbug. Other than those I've never killed a phone. I thought I had broken my friends Nexus 5 though, I unlocked it and went to root it for him but TWRP/CWM couldn't mount any partitions because it's "encrypted". Got it fixed though.
I've killed xbox's, PSP's, everything. It's all part of the learning process.
...When I first got my Nexus 5 in MTP on my Windows PC I had my phone hooked up to, on Internal Memory I saw a folder called sdcard that was not there before that was supposedly empty according to MTP. Deleted it. Turns out it was a symlink screwup in MTP, and it deleted my entire SD card including photos, luckily the important ones were already uploaded to Facebook and such. Now I backup my phone almost daily just in case.
I bricked my Archos Home Connect 35 once. Kinda my fault. I had set the bootloader to boot SDE firmware for it defaultly on boot. (Dev edition firmware from Google that was rootable). I updated from .82 firmware to .83 firmware, forgot to change that. It took the SDE firmware out, normally youd have to reinstall it, and since it was set to boot from that in Archos. mess of a firmware and bootloader, it would just bootloop because the SDE firmware wasnt there. No way to get out of it. RMA'd it and got a new one from Archos though. Never again, will always just manually select the SDE Dev Edition firmware when/if i ever reboot it. (Its just a Alarm clock mostly that plays Pandora occasionally. it last went 300 days without a reboot until it hard locked and I had to reboot. )
Never had a unrecoverable problem with my Galaxy S4, or my Nexus 5.Worst case with the S4 I Odin'd back to stock firmware. Nexus 5 got a corrupt data or cache partition once, i could have ran fsck but I flashed stock images instead.
I was having an issue having my phone seen on my PC. This is after I've rooted... Transferred music and pics from PC to phone, so I knew my drivers were installed. So I tried going back to stock. I downloaded the stock image and tried fastboot flashing. My download was corrupted. It got froze sending the radio. Froze for 30 min... Just kept saying sending. So I finally unplugged and rebooted to bootloader as everything else has been wiped. Tried again and it froze again at sending the boot loader. Froze for 30 min. I unplugged and tried rebooting. It never turned back on. No charging indication or anything. Officially bricked. I had tmo send me a new one and I'm returning the old one today. Wish me luck
First brick of my life and I've been rooting and modding since the OG Nex1
Sent from my Nexus 5 using Tapatalk
My GPS was working intermittently so I applied the cardboard fix and now its great. But in the process I damaged my back cover and now NFC and wireless charging don't work.
Really wishing I just RMA'd it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Related
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Creepazoid said:
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Click to expand...
Click to collapse
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Creepazoid said:
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Click to expand...
Click to collapse
I wasn't being sarcastic, however this is me now saying you're probably screwed.
Sent from my DROID BIONIC using xda premium
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Haha, alright, well thanks again for the heads up on the one-click, definitely going to come in handy in the future.
Sent from my MB860 using XDA App
beidave said:
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Click to expand...
Click to collapse
He said he's tried a few different batteries.
Sent from my DROID BIONIC using xda premium
So what was the verdict? Mine just did the same thing. However, I Have followed all of the directions everytime i've flashed and never had an issue til right now.
If you can't get the phone on at all, no fastboot or anything. No hardware buttons do anything, nothing comes up on the screen with anything you try....
That's a hard brick.
= requires a new phone
No way to fix it.
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
When I messed up my flash and my phone was stuck at the dual-core logo, I followed the steps below.
Pull your battery.
When you put it back in, hold down the power and volume down to access fastboot mode.
From there you can do a one-click restore method.
That is how I solved my problem. I hope it helps you.
Sent from my DROID BIONIC using xda premium
nickbeisher said:
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
Click to expand...
Click to collapse
have you triedf pulling the battery and putting it back in. the hold volume key down and power at the same time? if that works then just restore using fxz. if it does not work your phone is bricked
Brick!!
This is my third droid, I had The D1, the X, and now the bionic. By far I like this one much better than the the others. I have rooted all of them, and done the basic app freezing, overclocking, and other basic mods. This is my first go round with the custom rom flashing. I Flashed R3blurr3d, and every new update ( each update a new flash ). I also flashed D3blurr3d, and Liberty, just to check them out. I personally like Reblurr3d. When I flashed I always followed every direction to the letter, and if I was unclear on something rather than ask a stupid question, or ask something that had already been covered. I read and search until I find the answer I need and it is clear to me, sometimes that means searching for hours on end. I do this for the fear of ending up with a "Brick".
Now with everything I have read about any of these phones to "Brick" It is an error on the user's end while flashing or something of that sort, ( not following directions ).
So with everything operating butter smooth, and flashing dozens of times before this. What would cause a "Brick" during everyday use?
My guess is....he didn't know what he was doing. You rooted it for him and left it rooted for a user that knows nothing about root access. He probably did something using root access to fck something up.
When someone asks you to root their phone for them, the answer is always no.
Unless they know what they're doing, never give someone root access.
my first bionic did same thing. it was not rooted yet. just started rebooting it self. got more frequint then just quit the way you talked about. hardware problem.
Yes. That is what it is. It is a hardware issue, after talking to tech support it is a capacitor or something like along those lines, it stores battery power for times when more power is needed, like turning on the phone for instance. And when it randomly boots it is because it runs short on power due to the faulty hardware.
But apparently it is a known issue with Verizon, so if it happens to anyone else they should not have any trouble getting a new phone. I talked to a very nice tech support agent, and I will have a new phone by noon on Saturday.
And also I didn't have anyone root my phone, I do all of it on myself, Im no computer genius, but like I said I take my time and follow directions. And until now I have had no issues, and this had nothing to do with root access, flashing custom rims, or any other tweaking just a bad part Anthe phone. The thread was started by someone else. When I searched the threads, I found this and it was the same exact problem as I had, so that's why I asked what the end result was.
So with all that being said maybe this will be informative to someone else.
Pulled a rookie mistake this am and since then 2 more... smh.
I just got my day of release bionic working two days ago after i had left it at a friends house overseas, which forced me to go back to my og Droid for a month. I forgot about the internal SD vs ext SD thing on the bionic and flashed the new ics rom . Now I'm stuck at the motor screen. Would do a fast boot restore but power supply on my PC went up in smoke last week..
Anyone slip and pull a bone head move while flashing?
Nope I am extra causious especially when dealing with a non Odin phone
Sent from my XT875 using XDA App
Yeah I SuperBricked(battery dead, AND Stuck on "FlashBoot Failure") my Bionic 3 times in 1 DAY!!!
I just had two in a row. Lucky for me I never update until there's a recovery file. I just got my RAZR Maxx and flashed nitro's eclipse rom and bricked twice, then I realized I forgot to wipe data. It was really late and I was extremely tired, I actually didn't realize what I was doing wrong until I woke up this morning. Then I tried all day to activate it after going into Verizon and getting a new micro sim for it, I went back into Verizon, and I called tech support twice (tier 2) and spent 25 minutes the first time and 30 minutes the second time. Turns out I was trying to activate my wife's phone with my sim. Let's hope I don't screw up too bad finishing up my theme tomorrow (I started yesterday and planed to finish today but couldn't due to stupidity activating the phone)
eraursls1984 said:
I just had two in a row. Lucky for me I never update until there's a recovery file. I just got my RAZR Maxx and flashed nitro's eclipse rom and bricked twice, then I realized I forgot to wipe data. It was really late and I was extremely tired, I actually didn't realize what I was doing wrong until I woke up this morning. Then I tried all day to activate it after going into Verizon and getting a new micro sim for it, I went back into Verizon, and I called tech support twice (tier 2) and spent 25 minutes the first time and 30 minutes the second time. Turns out I was trying to activate my wife's phone with my sim. Let's hope I don't screw up too bad finishing up my theme tomorrow (I started yesterday and planed to finish today but couldn't due to stupidity activating the phone)
Click to expand...
Click to collapse
Lol
Sent from my DROID BIONIC using Tapatalk
iNsAnEmOd said:
Lol
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
It gets better, I was experimenting with restoring SMS with appextractor and it worked perfect from my bionic nandroid but not my wife's DX nandroid. I then updated CWM on the X and made another backup, that didn't work. I assume its because of the file system, the X has the froyo style file system where as the RAZR and Bionic have gingerbread file system setup. Then I restored a nandroid to undo all of the experimenting, BRICK! I forgot to swap back to my SD card and instead restored her X nandroid on the RAZR so I used rsd (and the same file that I successfully used the night before) but it failed 3 times, then the battery died so I'm waiting on a factory cable.
Dude ive been there...seems i only want to futz with my phone after work and on two+days no sleep... i flashed the stock rom but cant update... i get 1/4 through and it stops with an error... i dont have a pc atm.
I think its dumb that you cant get adb or an rsd type program to flash android stuff using an another android device. This asus transformer with dock keyboard has two powered usbs and an sd slot. Wtf! Wammbulance
Sent from my DROID BIONIC using xda premium
I also get confused with safestrap lol ive more than once forgotten which was which and flashed over the safecopy...only i can bonehead that hard i swear.
Sent from my DROID BIONIC using xda premium
I don't even have safestrap lol. I usually know what I'm doing. And I have system backups saved on my computer as well as my SD ext.
If you seem to be making human errors over and over again back to back, take a break. Go back to stock and leave it that way for at least a day. Then come back, read a tut or 2, and try again
Hi,
Got a Note in the UK just last week, brand new, and within two days I flashed it to the German stock ICS update. I can't say that I noticed issues in the first few days, but that could be because I didn't get a lot of time with it.
Since then, however, now that it is all set up and configured, I'm noticing random spontaneous reboots during sleep on the device, anything between every 2 to 6 hours, no warning, just the phone suddenly flashing into life with the model splash screen, followed by startup animation.
Reading around I've followed all kinds of anecdotal cures... I've removed Apex Launcher and Widget Locker, and returned to TWLauncher and stock dialer. I've moved all my apps from external SD to phone internal and deleted App2SDpro. I've cancelled all automatic syncs. I'm not rooted and don't have any iffy software on it.
Does anyone please have any ideas on this?
No ideas?
Since the update mine does exactly the same thing. Sometimes it reboots after every hour or so but then sometimes it happens every 5 hours. Its completely random and has started happening since the ICS update.
Hmmm. I'm wondering if I should do another full install, or if this is a bug that will be absent in the official UK version of the new OS/firmware update.
I wonder if it is somehow specific to UK users?
It annoys the pants off me, because it will happen, then I'll delete a load of software and restart manually, then it will behave sometimes (like today) for 11-12 hours. And then it does it again. And again. I've had 12 hours between reboots from yesterday to today, and then today I've had three in four hours, including one after just an 11 minute interval, while the phone was on standby.
Is there anything that can be a 'variable' on an 'international' Note which might be an incompatibility in one territory but not another?
Sim? Network? Wifi?
I'm in UK, and was on German Ics official until today . Started experiencing fcs on random apps, from what I've read elsewhere that can be the start of a superbrick. I would highly recommend flashing back to stable GB immediately.
Sent from my GT-N7000 using xda premium
Well... We may be seeing an improvement.
When I installed German ICS on my UK Note I did it as an upgrade. So yesterday afternoon I put the note to sleep and then rebooted into hard reset. I got myself a nice clean system and after lots of restoring files and reinstalling apps, I now have a Note that spent all night charging and hasn't restarted itself since 6am. It still could... But hasn't yet.
Something else odd I noticed...
When I first installed ICS (without tweaks, messing, only on stock ROM) and came to install SwiftKeyX for Phone it refused, allowing me only to install the tablet version... This depressed me a little because the skin I use is nicer on the phone version than tablet. Oddly, this time, after the reinstall, the note would only install the phone version of SwiftKeyX, and not the tablet.
Not sure what changed and why, but I can only imagine that something was broke and is now fixed...
Time will tell. I think battery might be a little better now too. And I use JuiceDefender.
If I get a full 24 hours without reboots I might dare to try App2SD again and move some apps to card storage.
So far so good.
Arse. 19 hours later and the reformed Note spoiled itself with a random reboot during sleep.
Back to the drawing board.
So is this a hardware or software fault. Its so new that I could do with knowing... I can insist it be swapped. But am I going to get the same again? Has anyone been able to trap this erroneous reboot in logs or anything? Do we know what it is?
Are there just a few of us, or many? Former would suggest hardware, latter could be software.
I'm having this issue too. We need help here
Sent from my GT-N7000 using Tapatalk 2
Mine hasn't rebooted all night while on charge. I would also like to know if there are any logs that can pin point the issue
Sent from my GT-N7000 using xda premium
I would suggest turn it off (be sure, it is turned off)
Remove the battery
Leave it this way for an hour
Insert the battery
Perhaps it would be good idea to go back to your area GB also (following drKetan guides).
I had the same anectodal thing happening with my new note just when i purchased it. After 1..2 days it went grazy. Then it blacked totally out. But just by chance it woke up after resting without battery for a day.
Personally, I think, the cache should be cleaned - BUT i definitely will not recommend a wipe cache in LPY (though it worked with me - but then again, it COULD NOT work with you - and the loss... what a loss it would be). (worked with me - that means it did not brick my phone when i upgraded few days ago and that did not have anything to do with my troubles when I purchased the note (few months ago)).
I'm discouraged that there are either so few people suffering this that we're simply 'on our own' with it, or so many people who have it but have learned to accept it.
It seems preposterous to not have attention to such a big fault.
And I realised that I've seen this before, and have the sneaky feeling that it is a dirty little secret of Android....
I bought an ASUS Transformer last June. It had this issue from day one on Honeycomb. Random reboots at unpredictable times, at least two per day. Over the last 9 months it went back to ASUS three times and each time they 'fixed' something totally unrelated to the problem before eventually telling me that they had no replacement units to give me and were authorising a full buy back - a refund.
I had anecdotal indications that it only occurred when I had an SD card installed. That was my growing suspicion, but I now no longer have a unit to test it.
Other Galaxy range users have been reporting random or looped reboots, and have pinned blame on using an sd card, especially in conjunction with App2SD.
I have an HTC Flyer with an SD card installed, running App2SD, and have no random reboot problems. Its as solid as a rock on stock Honeycomb.
Similarly, though, some users have reported that their Galaxy phone model has random reboots relating to having a sim card installed...
You see where this is going. Its getting to the place where we're accepting that the only way our expensive device works is if we disable key functionality and surrender our expectations of its advertised features doing the job they were intended to.
It is scandalous that this device should malfunction as a result of using the advertised features, and that no fix would be found nor explanation offered.
I now have an SD in the unit, but have not moved apps with App2SD. I have established that the reboots occur with all three of my SD cards of varying sizes, soit is not caused by a corrupt or faulty SD... If it is caused by an SD at all, it is 'all' SD's. Since so many users have the Note with SD's installed, and they run perfectly, I can't believe there is an issue with SD cards, although I did wonder if the manufacturers are now phasing out SD slots in their devices because 'cloud computing' is all the rage, or rather because this volatility caused by SD in the now unfixable evolving Android code means that they are minimising their embarrassment by simply dispensing with the faulty variable.
I have also begun setting static IP's for all my stored wlan's in case this is a DHCP issue caused during momentary wakes from sleep for polling or sync. If only we had an app that could store, like a seismograph, a persistent record of device events which trigger the reboot and then capture the reboot events also. Closest I've found uses ram to store the events log and then blanks the log on reboot starting from the reboot instead of maintaining the record prior to the reboot.
Getting close to wits end with this, and now deeply regretting my purchase.
Nothing like this on my Xperia Arc S.
Even an iPhone is better than this!
opsakas said:
I would suggest turn it off (be sure, it is turned off)
Remove the battery
Leave it this way for an hour
Insert the battery
Perhaps it would be good idea to go back to your area GB also (following drKetan guides).
I had the same anectodal thing happening with my new note just when i purchased it. After 1..2 days it went grazy. Then it blacked totally out. But just by chance it woke up after resting without battery for a day.
Personally, I think, the cache should be cleaned - BUT i definitely will not recommend a wipe cache in LPY (though it worked with me - but then again, it COULD NOT work with you - and the loss... what a loss it would be). (worked with me - that means it did not brick my phone when i upgraded few days ago and that did not have anything to do with my troubles when I purchased the note (few months ago)).
Click to expand...
Click to collapse
Can you direct me to that guide?
And is it likely that it is the DE ICS release that just doesn't like UK devices? Why would that be so?
Looks like i'm going to get stuck with this problem until I move on to a next phone. What a waste
Sent from my GT-N7000 using Tapatalk 2
Maybe you should have waited for a stable release built using the UK or wwe equivalent rom? You didn't even give the stock more than a couple of days, what was the rush?!
Sent from my GT-N7000 using xda premium
Maybe, yes.
Naivete, perhaps.
I'll tell you exactly why.
I had an Xperia Arc S on ICS which I loved. I was tempted by the Note. I bought one expecting a Samsung flavored ICS experience, and got tossed back to GB. I basically had 7 days to return the Note or learn to like it, and during that period DE f/w was released and I had to know...
Note was rebooted using static ip's and is nowraring to go...
So far so good @ 18 hours
BashyUK said:
Maybe you should have waited for a stable release built using the UK or wwe equivalent rom? You didn't even give the stock more than a couple of days, what was the rush?!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Did you even read my other posts? Problem started when i was still in gb.
Sent from my GT-N7000 using Tapatalk 2
Still going... No reboots. And excellent battery performance to boot.
l0rd_almighty said:
Did you even read my other posts? Problem started when i was still in gb.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
But if that was when your phone was still new why didn't you just return it for a replacement rather than root and flash a phone that wasn't stable in the first place? For all you know it may be a hardware issue and likely so as I've not heard any apart from you and the op mention it.
Anyway, your phone, your call what you do with it but it makes no sense to me to blame the manufacturer and model when you've not even followed basic steps to deal with an issue.
Sent from my GT-N7000 using xda premium
The first note I had in December 2011 rebooted at random. It was a hardware issue. It only started after owning it for 3 weeks, stock GB. Not roiled or modified in anyway. I had it replaced.
G
Sent from my GT-N7000 using Tapatalk 2
BashyUK said:
But if that was when your phone was still new why didn't you just return it for a replacement rather than root and flash a phone that wasn't stable in the first place? For all you know it may be a hardware issue and likely so as I've not heard any apart from you and the op mention it.
Anyway, your phone, your call what you do with it but it makes no sense to me to blame the manufacturer and model when you've not even followed basic steps to deal with an issue.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Basic steps i didn't follow? Enlighten me... I never mentioned that this happened when my phone was new. I said this started when i was still in GB. Notice the difference? If you can't help us figure out what's causing this just go troll on somebody else's thread.
Sent from my GT-N7000 using Tapatalk 2
I was hoping someone could give me a step by step on how to completely reset my phone back to the state it was in when I first pulled it out of the box. I just wanna completely start fresh.
My phone is running so damn slow and is all sorts of messed up cause my friend ****ed with it and tried to put one of the custom ROMs he made on it even tho I told him not to and he didn't remove the current ROM I had running first and it just made everything messed up. Which is why I don't want anyone messing with rooting or custom firmware on my phone except for me. I had my phone running the ROM I liked and had my phone running nice and smooth and fast. It ran perfectly. And when he did it he failed to make a nandroid backup beforehand and someone reformatted my sd-card so all the backups I had of my own are gone and now its all sorts of ****ed up.
I've never done a full reset except for on motorola phones and all you had to do with that is get the proper SBF file and run RSDlite. But I don't know what to do on this phone. So a detailed step by step or a link to a detailed guide would be very much appreciated. Thanks in advance for the help.
Sent from my VS910 4G using xda app-developers app
The only way I know of to fully get that "out of box" look and feel is to flash a tot, then factory reset.
Try this Then do a factory reset or vice versa. it's best to do the factory wipe from cwm. essentially wiping data, cache, and dalvik.
http://forum.xda-developers.com/showthread.php?t=1337386
Factory reset
Flash v9 Firmware
then Wipe SD and Internal Storage
Out of box.
I know its been awhile since I posted this, but I unfortunately went to jail shortly after posting this and finally got acquitted of the charges and released from custody just 4 days ago, because the witness refused to testify and all he would tell the Prosecutor was that I didn't start the fight and was only defending myself.
Which was the truth. I was sucker punched twice in the back of the head and after that I completely just saw red as they say, and I don't really remember much of what happened between the getting sucker punched and then being in hand-cuffs with blood on me that wasn't my own, but I apparently broke the dudes jaw and left eye socket. And they, they being the police, tried to say that even tho he swung first, I used excessive force in response and therefore it no longer was self defense lol which is bull****, and it took about 4 months in jail for me to prove that......Well technically I didn't prove anything, the prosecutor just didn't have a case since their so called eye witness ended up backing my story up and wouldn't testify, so they had no choice but to drop it.
And since no one I knew could afford 4,500$ in bail and even tho I had the money in savings, more then enough, they wont let you pay your own bail, unless you have the cash in your property but I only had my debit card and they wouldn't let me release it to anyone so they could pull the money out and since they don't have ATMs in jail lol I got ****ing stuck in there
Anyways, now that I explained my interesring story as to why I am having to resurrect a thread from like 4months ago, my question is, where can I get the current V9 firmware that the most recent poster mentioned. So I can do what I wanted to do 4 months ago lol
Sent from my VS910 4G using xda app-developers app
Give thanks to capt
http://forum.xda-developers.com/showpost.php?p=34196277&postcount=248
So, I've been using this wonderful device for a while now, since early October. I've finally got it set up the way I like it and all. Now, I'm just flashing ROMs to see which I prefer. Just a few hours ago, I decided to revert to the T-Mobile ANK3 (or AN-whatever) stock ROM because on Lollipop 5.0.1+ the battery dies much quicker than I'd like it to. Yet, that ROM would constantly either:
A) Die whenever it wanted to
B) Freeze and just not respond
C) Require a battery pull
D) Send me to D/L mode with "mmc_read fail".
So I decided to revert back to stock 5.0.1 because I was tired of all the bugs I was encountering with 4.4.4.
Now, every hour or so, the phone dies and gets stuck on the splash screen (with the obvious SEAndroid not enforcing + Set Warranty Bit). Or if it isn't that, the phone just outright freezes when I'm using a light application (i.e. Kik Messenger).
I'm starting to think that my eMMC is dying, because the phone was not acting like this when I first got it in early October. Every once in a while D/L mode keeps repeating my fears. I cannot send it in to Samsung because I already voided my warranty, and I am a prepaid subscriber on T-Mobile. (So, no, T-Mobile will not help me, likely.)
Any ideas on what's happening, or what I should do?
First thing I would do Is flash a different kernel
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Did that, ended up having the same problems. I said screw it, and am now using CM12.1...
Although I really don't like it (because TW is now a good thing as opposed as to how bad it was on the S3), I'll settle with it. It's not so bad.
---
LMAO OOOOO I LIED TO MYSELF
even CM is force rebooting itself wwwwhat
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
sqmala4321 said:
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
Click to expand...
Click to collapse
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Good news...since they know that the eMMC chip is bugging out, they'll do a free repair. Success! Now, time to go into the repair shop and hope they accept my reference ticket, since I'll be a walk in.
I can't call right now, seeing as my phone has difficulty doing ANYTHING now...
eduardog131 said:
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Click to expand...
Click to collapse
actually i am having the same exact problem....i had the tmobile note 4, and its doing the same thing about 1 month ago...reboots, black screens; and all that you have mentioned. so i started to look into rooting/flashing tekxodus hd onto my phone...still the same problem...phones restarts to boot loop time to time...bad screens....i'm still trying to find outwhat the hack is going on...and the phone's warranty expireds about 1 month ago right before the phone start to act up....let me know if you find a solution to that..lol...thanks:good:
---------- Post added at 11:25 PM ---------- Previous post was at 11:17 PM ----------
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
yes, i did that too...odin back to stock, still same problem...my phone was on stock when these problems started. i hoping different roms would solve the problem...so i started rooting and intalled tedxodus and the same problems...hopefully someone could help please.