Related
Can anyone definitively explain the reason why some can and some can not unlock their bootloader? I've searched all over the forums and see reasons the span from left to right. I typically just lurk in the background and figure out methods to install custom ROMS on my own, but this unlocking situation is starting to chap my my arse. I've been trying for about two weeks to use the ASUS tool, but it ain't working for me.....I keep getting the same connection message that other's are getting.
Anybody got a good answer or an even better solution?
From what I've read it seems to be because of their method to track who unlocks. It takes your serial number and then they know so they can void the warranty. However a certain amount of numbers also got put on that list. So when you go to use it it doesn't work because it's only a one time deal to prevent from relocking /unlocking. I'm not 100% sure on this because there isn't really any information available but that's what I've heard from a bit of looking around.
Sent from my ASUS Transformer Pad TF300T using xda premium
All I did was download the apk from asus and installed on my tablet and bam unlocked the tablet took 5 minutes if that. What methods are you doing?
Ok so I found this looking around.
http://forum.xda-developers.com/showthread.php?t=1669328
That thread seems to show/explain a lot. Plus maybe reading it will stop double posting.
Sent from my ASUS Transformer Pad TF300T using xda premium
Yeah, saw that post. Tried it too......nada. I've got a C30KCT S/N too.
Just curious for those of you that have successfully unlocked your tablet.....did you happen to register your device's S/N with ASUS?
No registering necessary. Just go here:
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
choose android as your OS and click on Utilities and download the Global link and transfer that apk file to your tablet and run it. You should be be unlocked after running the program and following the on screen instructions.
vel0city said:
No registering necessary. Just go here:
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
choose android as your OS and click on Utilities and download the Global link and transfer that apk file to your tablet and run it. You should be be unlocked after running the program and following the on screen instructions.
Click to expand...
Click to collapse
The app you just told people to download is the same one that isn't working. The problem they're having with the app is that they get a network error when they run the app. The error is because the user's serial number isn't in the Asus database. This wouldn't be a big deal if you could just tell Asus and ask them to fix it. Unfortunately, the instant you run the app, you lose your warranty, so when you tell them that you ran the app and it didn't work, they tell you you're out of a warranty, and they can't help you.
The only solution anyone's found so far is to keep trying and hope Asus adds your serial to their database.
EndlessDissent said:
The app you just told people to download is the same one that isn't working. The problem they're having with the app is that they get a network error when they run the app. The error is because the user's serial number isn't in the Asus database. This wouldn't be a big deal if you could just tell Asus and ask them to fix it. Unfortunately, the instant you run the app, you lose your warranty, so when you tell them that you ran the app and it didn't work, they tell you you're out of a warranty, and they can't help you.
The only solution anyone's found so far is to keep trying and hope Asus adds your serial to their database.
Click to expand...
Click to collapse
Thanks for the heads up did not know that I guess my friends and I have been lucky then unlocking our bootloaders I mean I unlocked and rooted about 10 tablets and didnt come across this lol.
Yeah, the problem first got attention when a bunch of people weren't getting OTA notifications. Some folks went to devicetracker.asus.com and entered their serial numbers and were told that the serial number was invalid. These same people got tired of waiting for the OTA and decided to just unlock their tablets and install custom ROMs. Unfortunately, they just got a network error. Someone, at some point, called Asus support about the OTA and was told about the database problem. Apparently, it hasn't been completely fixed yet. Eventually, I think, most people either got their OTAs and/or the unlocker started working. There were also reports that downgrading to .17 and doing a factory reset solved the problem for some people but not others. Other people said that clearing data for certain services made it work, but not everyone got that to work, either. The only options you have are to either wait or return the tablet and hope the replacement doesn't have the same problem.
So, if you've received OTA's and registered with device tracker it'd be a safe bet they have you in the their db, right?
Yup. I meet both criteria and just unlocked successfully.
[Q] Error during boot-up after firmware upgrade: "No certificate to inject".
I updated my firmware to V10.4.2.17 WW manually. My tablet is not rooted or unlocked. The first thing I noticed was that my Transformer 300T now gives some sort of error message in the upper left corner (below the power button) during boot-up, the message is "No certificate to inject". It happens at every boot-up and doesn't seem to give any problems, but I'm curious if other people get it. Also I'm curious what it means exactly.
Any ideas?
Same issue here. I also cannot unlock bootloader or update vía OTA.
Help me too No certificate to inject, a new tablet
Same here, thanks for helping...
Same here:
I waited 2 weeks to see if I was getting it via OTA, ...but nothing, ...not even when manually asking for it via Settings -> Firmware update.
So I decided to go the manual way via the Micro SD card; all went fine BUT, now I have for 5 seconds, every time I boot, the same message:
No certificate to inject
Why ?
Thanks for your help !
Id like to add that I have the same issue with my new tf300t. Only did an update because I wanted to have the latest firmware but I kinda regret it. Has anyone found a solution?
Sent from my Samsung Epig 4G using Tapatalk Pro
Same problem
I have the US version and mine is brand new. The firmware update which was pushed to my tab VIA OTA has rendered it completely useless. I get the error, " no certificate to inject" and it does nothing but crash. If it goes to sleep or if I hit the power button to turn the screen off it will not wake up and I have to long press the power button to reboot. I can't even use it, it's basically a paper weight now. Does anyone have a clue how I can fix this? Should I try to flash the old firmware? If so can someone point me to a link on how to go about it.
I called Asus and they did not want to walk me through flashing firmware. They want to set up an RMA.
I've tried a cold boot, factory reset and data wipe.
guyute said:
I have the US version and mine is brand new. The firmware update which was pushed to my tab VIA OTA has rendered it completely useless. I get the error, " no certificate to inject" and it does nothing but crash. If it goes to sleep or if I hit the power button to turn the screen off it will not wake up and I have to long press the power button to reboot. I can't even use it, it's basically a paper weight now. Does anyone have a clue how I can fix this? Should I try to flash the old firmware? If so can someone point me to a link on how to go about it.
I called Asus and they did not want to walk me through flashing firmware. They want to set up an RMA.
I've tried a cold boot, factory reset and data wipe.
Click to expand...
Click to collapse
Wow that really sucks. If its a paper weight and they offered to do an RMA why wouldnt you? Im still waiting on ASUS to reply to my email! lol. Look it's brand new and its basically a brick. Unless they can give you a solution thats easy i would just go through the return process.
edit: they emailed back saying that doesnt sound right and to do a factory reset. While i knew that wouldnt fix it i did it anyhow since i didn't have much data to lose. Long story short they want to RMA mine as well. Ugh.
RMA
So yep I sent it in for RMA, Very disappointing that and update did this to my brand new tab.
guyute said:
So yep I sent it in for RMA, Very disappointing that and update did this to my brand new tab.
Click to expand...
Click to collapse
same here, dont feel so bad. It sucks.
So I got it back today from RMA and guess what? On the very first start up it still says no certificate to inject. Unreal, why didn't they correct this? It seems like the only thing they did was flash the old firmware back. Now my tablet is asking me to update and I don't want to because the last time it turned it into a pile of crap.
guyute said:
So I got it back today from RMA and guess what? On the very first start up it still says no certificate to inject. Unreal, why didn't they correct this? It seems like the only thing they did was flash the old firmware back. Now my tablet is asking me to update and I don't want to because the last time it turned it into a pile of crap.
Click to expand...
Click to collapse
Jesus. Mine is sitting at my house right now as it was delivered from Fed ex today and i am worried it will be the same ridiculousness. ugh.
nyr35blue said:
Jesus. Mine is sitting at my house right now as it was delivered from Fed ex today and i am worried it will be the same ridiculousness. ugh.
Click to expand...
Click to collapse
They want me to RMA it again. I wish I never bought this thing. It seems to be working fine, but I have a bad feeling about letting it do the firmware update.
Why didn't they fully update it when they had it? Also are they blind? It's completely obvious the error message is still there during boot up and I was very specific about it.
guyute said:
So I got it back today from RMA and guess what? On the very first start up it still says no certificate to inject. Unreal, why didn't they correct this? It seems like the only thing they did was flash the old firmware back. Now my tablet is asking me to update and I don't want to because the last time it turned it into a pile of crap.
Click to expand...
Click to collapse
guyute said:
They want me to RMA it again. I wish I never bought this thing. It seems to be working fine, but I have a bad feeling about letting it do the firmware update.
Why didn't they fully update it when they had it? Also are they blind? It's completely obvious the error message is still there during boot up and I was very specific about it.
Click to expand...
Click to collapse
apparently they ARE blind. The message is quite easy to see when you turn it on. To be honest i wish i never did the firmware update when i first got it for Xmas. Thats when this all started for me. I'll let you know what happens with mine so you can either hate me or feel a little better knowing my predicament.
HAHAHA, I hope your doesn't have the error. Now I don't want to do the firmware update, because I know what happened last time. But on the other hand what am I supposed to do, never update my tablet ever again?
Would I even be able to skip the firmware update but still take any OS update they may push in the future?
The RMA is good for 30 days so I think I'm going to see what happens. It seems perfectly fine right now, no issues with it not waking back up.
Ok little update, it still has the error message, but is working very well. It's reading my SD card (which it didn't before) and no issues with it waking back up. I also ran the update and all seems fine. I'm going to mess around with it for the next few days and see if misbehaves. If it works perfectly fine and still has the message then so be it, I'm not going to send it back in.
guyute said:
Ok little update, it still has the error message, but is working very well. It's reading my SD card (which it didn't before) and no issues with it waking back up. I also ran the update and all seems fine. I'm going to mess around with it for the next few days and see if misbehaves. If it works perfectly fine and still has the message then so be it, I'm not going to send it back in.
Click to expand...
Click to collapse
Well i got it back shockingly no error message anymore but i also notice it wasn't factory restored. No problem i did that myself. Of course it downloaded the firmware update and wants to install which i chose NOT to. Not sure if and when i will decide to do it. lol. How annoying.
nyr35blue said:
Well i got it back shockingly no error message anymore but i also notice it wasn't factory restored. No problem i did that myself. Of course it downloaded the firmware update and wants to install which i chose NOT to. Not sure if and when i will decide to do it. lol. How annoying.
Click to expand...
Click to collapse
Well I ran the update, and it seems perfectly fine. I wish they had cleared up the error message, but I've been going at the thing all day and it seems perfect. They gave me a new RMA, but if it continues to run perfectly I'll just take that as a win.
I unfortunately am having the same problem..
I have gone through 2 tablets now at Best Buy.. The first one went from stock to .20 release and started getting the error.. So I get another one.
I figure that I'll be smart now and I have 2 other TF300's and the one that I had previoiusly all had no issues.. So I figure I will update to the previous release first..
Now I'm getting the message..
It did download the latest release but when it goes to install the OTA it fails.. EXTREMELY frustrating.. A TOTAL waste of my time.. I really want to kill myself right now.
Anyway... I'll manually update to the latest version and maybe pick a different Best buy..
I of course also put my Armor Shild on this one because I figured there was no way that I got two doing this in a row..
Yeah.. 40 bucks down the drain.. .I will call Asus and make some tech supports ears bleed tomorrow.. Yeah I know it's not his fault but.. well it's his fault.
Any new info on this?
Hello everyone, just got back into tech toys and having time to play around etc. Anyway got the same error after OTA update, also Keyboard spacebar does nothing anymore and the mouse pad doesn't work at all either. Looked online everywhere and figured if there was an answer for this it would be in these forums and haven't found one. Had to make a new account on here and haven't had the time to mess with anything in a while so it's all new to me again. Any help would be great, kinda scared to try anything after reading so many different ways to brick this thing- have an email in to asus, 3 acually, and no responses back on any of them and it's been months..thanks for any info - really want to unlock/root/recover and try some of these awesome looking ROMS but am stuck with this error and no response back from asus.
Hi there!
So I yesterday received my TF700 from my brother and now I'd like to try some Custom ROMs for it. However with the Asus unlocking tool is giving this 'unknown internet problem' error.
As far as I have read the forums there is no way around it, is this correct? I've also read that some users have managed to pass the error by just trying again and again, is this also correct?
Latest JB update, no root whatsoever.
inSaN1Ty_X said:
Hi there!
So I yesterday received my TF700 from my brother and now I'd like to try some Custom ROMs for it. However with the Asus unlocking tool is giving this 'unknown internet problem' error.
As far as I have read the forums there is no way around it, is this correct? I've also read that some users have managed to pass the error by just trying again and again, is this also correct?
Latest JB update, no root whatsoever.
Click to expand...
Click to collapse
Yes all correct.
maxal said:
Yes all correct.
Click to expand...
Click to collapse
And no magic tricks to rapid success? Just pressing da button?
inSaN1Ty_X said:
And no magic tricks to rapid success? Just pressing da button?
Click to expand...
Click to collapse
I cannot tell you how many times I pressed that button before I was unlocked. To be clear, my error message was the connection problem.
I doubt this makes any bit of difference, but here are the steps I went through to unlock the Infinity:
Day 1: Downloaded unlock tool. Tried to unlock and was not successful. I tried several times (20? 30?) over the entire day without luck.
Day 2: Registered my Transformer Infinity with ASUS Device Tracker. The registration process was successful. I did not receive any errors regarding my serial number. Tried unlocking again (20 or 30 more tires) during the day. Still unsuccessfully.
Day 3: Turned off Google Location in the settings. Tried unlocking for ~1/2 a day. I was not successful. I called ASUS Customer service who were not helpful. Two people spoke with me. The first person said the problem was a "rare" occurrence. The second person opened a ticket for me and told me to continue trying.
Day 4: I successfully unlocked my tablet.
In my opinion, I don't think ASUS Customer service did anything or turning off Google Location did anything. I think I was finally able to connect to ASUS' servers to unlock.
My advice, keep trying like everyone else suggests. It can be disappointing, but it eventually worked.
I just got mine unlocked, had been trying for about 3 days of pressing the button in the unlock APK. My device had the OTA Jelly Bean update.
I also have an RMA device (I sent it in late last year for screen lifting and backlight bleed) - so you do NOT have to re-RMA it to get the unlock tool to work. Just patience.
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
adelancker said:
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
Click to expand...
Click to collapse
Really just a guess ... but I think I have read something in other threads about MAC address and mainboard serial number not matching any more once the board has been exchanged. As far as I know, the unlock process contacts the Asus servers and does some kind of checking. I have read from others that had success in contacting Asus support and have them match all the items again.
Please take this with all care, just guessing here ... but maybe you can carry on your search in this direction.
adelancker said:
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
Click to expand...
Click to collapse
FordPrefect said:
Really just a guess ... but I think I have read something in other threads about MAC address and mainboard serial number not matching any more once the board has been exchanged. As far as I know, the unlock process contacts the Asus servers and does some kind of checking. I have read from others that had success in contacting Asus support and have them match all the items again.
Please take this with all care, just guessing here ... but maybe you can carry on your search in this direction.
Click to expand...
Click to collapse
This ^^ sounds about right -- I'm sorry, adelancker, but you're the latest in a loooooong line of TF700 owners who got their repaired device with a permlocked bootloader. (And to add insult to injury: I've never heard of anyone getting into contact with ASUS and resolving it -- although one guy tried three times over, and then reported he had contacts within ASUS now that could help resolve the issue. He was selling that unlock ability, but you had to pay a pretty amount in advance... Nice scheme, huh? ) Actually, I've heard of only three XDA-ers having it returned to them with the ability to unlock retained.
Man, this sucks. I really do feel sorry for you!
MartyHulskemper said:
This ^^ sounds about right -- I'm sorry, adelancker, but you're the latest in a loooooong line of TF700 owners who got their repaired device with a permlocked bootloader. (And to add insult to injury: I've never heard of anyone getting into contact with ASUS and resolving it -- although one guy tried three times over, and then reported he had contacts within ASUS now that could help resolve the issue. He was selling that unlock ability, but you had to pay a pretty amount in advance... Nice scheme, huh? ) Actually, I've heard of only three XDA-ers having it returned to them with the ability to unlock retained.
Man, this sucks. I really do feel sorry for you!
Click to expand...
Click to collapse
If this is true, this takes a whole lot of the joy of getting it back away!
Hopefully I will be able to convince them to set things straight.
I'll keep you posted, but I fear the outcome...
Any trick you know of that'll speed my infinity up, without going to custom roms?
I guess rooting should still be succesful? And then what? Install systemtuner, fstrim, browser2ram and see if that's enough?
Doesn't seem like I have an option here
adelancker said:
If this is true, this takes a whole lot of the joy of getting it back away!
Hopefully I will be able to convince them to set things straight.
I'll keep you posted, but I fear the outcome...
Any trick you know of that'll speed my infinity up, without going to custom roms?
I guess rooting should still be succesful? And then what? Install systemtuner, fstrim, browser2ram and see if that's enough?
Doesn't seem like I have an option here
Click to expand...
Click to collapse
Yes, rooting should still work -- I haven't really looked into the downgrade path options and if it requires a custom recovery, though. I'd root it if possible, and then tweak the hell out of it.
I fear as you do, but you might drop ASUS a line anyway -- you've got next to nothing to lose. Take care, and good luck!
I can post up a few build.prop tweaks but without a custom kernel you may still suffer.
Best thing you can do is update to 10.4.4.25 and disable all the asus bloat for now.
What has been said about the MAC address is correct. The success rate of people shipping their tablets into RMA to fix the MAC address issue does not seem very high. People are reporting they get the tablet back with the same issue regarding the unlock tool and unable to get the device tracker or OTA updates to work.
Email Asus support and flat out ask them to check the servers in Taiwan and find out if the MAC address listed in your tablet is the same one on the servers. They have the serial number already will just need you to supply the MAC address. If it comes back saying it is not and you need to RMA it, good luck. Question then becomes did the person responding to the email really check or just saying to RMA it so they can close out your email ticket.
The response I got last week was my tablet not matching what they have on the server and send it in. I'm debating if it's worth spending 15-20 bucks to mail it in, wait 2-3wks, only to get it back with them saying there is nothing wrong with the tablet and still be unable to unlock. That seems to be general outcome. In the email I explained I'm unable to use device tracker, receive OTA updates, or use the unlock tool. I explained the issues with MAC addresses for devices being incorrect on the servers in Taiwan as a known issue causing these problems. I supplied my MAC address that the tablet gives and asked to have them verify what they have.
Sorry to say but only Asus can fix this problem. If you search the forums for this topic you will find threads on it. Some had mentioned trying it with the sd card removed has worked. Give that a try. If you disabled the two tracking programs Asus has in their stock build, turn them back on when you try to unlock. Just keep trying a few times randomly and you might get lucky.
If I ever get my issue resolved I will for sure post in the forums for others.
We had already a thread for this, albeit for new devices:
http://forum.xda-developers.com/showthread.php?t=2146543
Mine works now.
The only success I have read about is 2-3 people asking Support to contact Taiwan / transfer the ticket to Taiwan as they seem to be able to correct the MAC in the systems.
After a week or so they fixed the MAC in their systems and the unlocking works again.
I have requested ASUS Germany to contact Taiwan 1,5 week ago but no luck yet. Still hoping they can work things out and I will keep on pushing.
sbdags said:
I can post up a few build.prop tweaks but without a custom kernel you may still suffer.
Best thing you can do is update to 10.4.4.25 and disable all the asus bloat for now.
Click to expand...
Click to collapse
Thanks! That's what I have done right now Except for the build.prop tweaks.
I can't do those all by myself
adelancker said:
Thanks! That's what I have done right now Except for the build.prop tweaks.
I can't do those all by myself
Click to expand...
Click to collapse
Wary of you doing the build.prop cos if you cause a boot loop you can't restore form recovery. You could reflash the full asus update though right? You comfortable with that?
Also don't forget to force gpu in developer settings.
DarkFire1985 said:
The only success I have read about is 2-3 people asking Support to contact Taiwan / transfer the ticket to Taiwan as they seem to be able to correct the MAC in the systems.
After a week or so they fixed the MAC in their systems and the unlocking works again.
I have requested ASUS Germany to contact Taiwan 1,5 week ago but no luck yet. Still hoping they can work things out and I will keep on pushing.
Click to expand...
Click to collapse
Be careful here - the problem is not always the MAC-address.
For my TF700, Asus had the correct MAC-address stored, but OTAs, Device Tracker and unlocking did not work nevertheless.
From my Logcat entries I saw that the server refused to 'talk' to my tablet, so I assume that the Asus server in Taiwan just didn't know my tablet.
The issue is fixed now BTW, Asus Germany forwarded the ticket to Taiwan.
So if you talk to Asus support, do not insist that the problem is the MAC-address - if your MAC address is correct and you still insist that it is wrong the Asus support won't take you serious anymore.
sbdags said:
Wary of you doing the build.prop cos if you cause a boot loop you can't restore form recovery. You could reflash the full asus update though right? You comfortable with that?
Also don't forget to force gpu in developer settings.
Click to expand...
Click to collapse
Already did! Checked force gpu, disabled all animations,etc.
Just doesn't match up to what did with CRomI
I'll first need to get root, but my tablet isn't recognising the EP201_768_SDUPDATE.zip as an update, I am afraid.
And without that, I can't even get root lol
By the way: I sent a mail to Asus, and they told me to send it in to get the unlock bootloader issue fixed.
Why on earth would they need me to send it in (once again!)?
adelancker said:
Already did! Checked force gpu, disabled all animations,etc.
Just doesn't match up to what did with CRomI
I'll first need to get root, but my tablet isn't recognising the EP201_768_SDUPDATE.zip as an update, I am afraid.
And without that, I can't even get root lol
By the way: I sent a mail to Asus, and they told me to send it in to get the unlock bootloader issue fixed.
Why on earth would they need me to send it in (once again!)?
Click to expand...
Click to collapse
To get that $125 from you a second time?
MartyHulskemper said:
To get that $125 from you a second time?
Click to expand...
Click to collapse
Hahaha ^^
They haven't charged me yet!
Maybe because I was super mega angry in my mail and mentioned the EU-consumer law a million times.
doesn't unlock and presumably void your warranty? I'm surprised they even let you send it in? Or are all of these instances non warranty repairs?
NegativeOne said:
doesn't unlock and presumably void your warranty? I'm surprised they even let you send it in? Or are all of these instances non warranty repairs?
Click to expand...
Click to collapse
What can I say? I am a good negotiator I guess...
Just kidding. If you're European, you can always use this EU consumer protection law, which always has your back for the first 6 months after purchase.
Well I'm just asking because I just got my tablet yesterday and am still deciding whether or not to unlock it.
It seems like asus is pretty nice about repairing unlocked devices though.
And no, I'm in the USA
NegativeOne said:
Well I'm just asking because I just got my tablet yesterday and am still deciding whether or not to unlock it.
It seems like asus is pretty nice about repairing unlocked devices though.
And no, I'm in the USA
Click to expand...
Click to collapse
If you're from the US, I can only recommend you to buy a third party warranty such as the Square Trade one.
After that, you can do whatever you want and you'll never have to worry about losing warranty after unlocking your tf700 ever again.
As a side note, unlock your device as soon as you have time! It makes your device that much quicker.
Just sucks that Asus somehow prevents me from unlocking it after the RMA.
I've followed directions in the following two forums (and sifted through many, many others here):
http://forum.xda-developers.com/oneplus-one/general/fix-carrier-wifi-wrong-date-time-t2922849
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I've contacted OnePlus support and received new persist.img and other 38R files directly from them. I've flashed EVERYTHING in any number of ways. I've even tried CM nightly's...
But no matter what I do this phone constantly reboots. All the friggin' time. Randomly. Sometimes up to a few dozen times a day. It'll just be sitting there and it'll reboot. It'll happen when I'm using Chrome, checking my email, or when I look at it wrong. OnePlus keeps telling me it'll be fixed with the next update, but I have my doubts (since they said that before 38R was pushed).
Does anybody have any ideas on how to debug this? I am not new to android, but I'm also not all that knowledgeable about it. I'd love to see some system logs or something that'll point to what is causing these crashes, but I'm at a loss. Beyond debugging does anyone have any ideas about what could be causing it? Bad spot of memory, storage, anything? I'm at my wits end. I love the device, but can't stand these reboots that seemingly nobody else has to suffer.
Have you tried any other ROMs apart from CM?
Transmitted via Bacon
No, and I don't particularly want to. If it doesn't work with what it is supposed to then I would rather have my money back and move on to a different device. Personally I can't stand most ROMs. I like plain android and CM, but otherwise I haven't ever used one I liked. As far as it goes I may try another one just to see if the issue persists, but that's a whole lot of hassle over what would ultimately have me ask for a refund anyway.
Why not try Paranoid Android?
I'll give that one a try. Assuming the issue continues to happen, what then?
revjtanton said:
No, and I don't particularly want to. If it doesn't work with what it is supposed to then I would rather have my money back and move on to a different device. Personally I can't stand most ROMs. I like plain android and CM, but otherwise I haven't ever used one I liked. As far as it goes I may try another one just to see if the issue persists, but that's a whole lot of hassle over what would ultimately have me ask for a refund anyway.
Click to expand...
Click to collapse
revjtanton said:
I'll give that one a try. Assuming the issue continues to happen, what then?
Click to expand...
Click to collapse
There really isn't very much difference between CM and other ROMs anyway. If it continues then I'd suggest starting the RMA process.
Transmitted via Bacon
I just tried Paranoid Android. I couldn't even get past the Welcome screens without a reboot.
goddamn it.