Database Info

[Q] TF300T RCK issues after reflashing stock ROM

So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.

Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!

Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.

tobdaryl said:
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Click to expand...
Click to collapse
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
flumpster said:
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
Click to expand...
Click to collapse
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD

Rojikku said:
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Click to expand...
Click to collapse
The twrp mentioned above can be found here.

tobdaryl said:
The twrp mentioned above can be found here.[/URL]
Click to expand...
Click to collapse
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.

Rojikku said:
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Click to expand...
Click to collapse
Wrong twrp! You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off stock 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Unless the rom you flash is also for 4.2 bootloader. Both are located at teamwin.
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock.
As far as flashing a new rom look at the op and determine if it is for the new stock 4.2 bootloader. If not do not flash over 4.2 but downgrade first. I have upgraded from 10.4.2.20 to stock 4.2 and downgraded from stock 4.2 to 10.4.2.20 several times without issue.
Stock 4.2 includes an assert to only allow upgrade from 10.4.2.20.

tobdaryl said:
Wrong twrp! [/URL]You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Both are located at teamwin.[/URL]
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock and hold a minute or you are going right back where you were or worse. You need slightly more info before going forward and I need to check my notes while you get the proper twrp flashed.
Click to expand...
Click to collapse
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.

Rojikku said:
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Click to expand...
Click to collapse
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.

tobdaryl said:
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
Click to expand...
Click to collapse
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.

Rojikku said:
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Click to expand...
Click to collapse
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?

tobdaryl said:
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
Click to expand...
Click to collapse
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?

I decided to take the risk and reboot it. Everything fine. I flashed the tool, ran the reboot command(Which actually didn't work... >>; But I rebooted it manually and it seems fine...)
On that note, is it actually possible to destroy a device beyond repair accidentally? And the TWRP tool said it flashed fine but I still have the old version. Odd....
I do have the image you said currently installed, I checked the version against my download.

Rojikku said:
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
Click to expand...
Click to collapse
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.

tobdaryl said:
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
Click to expand...
Click to collapse
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?

Rojikku said:
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Click to expand...
Click to collapse
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.

tobdaryl said:
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
Click to expand...
Click to collapse
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.

Rojikku said:
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Click to expand...
Click to collapse
When it asks for the password hit cancel and just ignore the error.

tobdaryl said:
When it asks for the password hit cancel and just ignore the error.
Click to expand...
Click to collapse
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)

Rojikku said:
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Click to expand...
Click to collapse
Thanks for the link. I looked at the info provided for that rom. You don't want to flash that over an encrypted tablet which you now have. The only safe way I have found to go to or from stock 4.2 rom is with stock 10.4.2.20.
To do that you would flash 10.4.2.20 with twrp, boot into os, reboot back to the bootloader which will now be four icons, select usb, use fastboot to flash twrp again, and now flash your new rom.
This sounds long but removes encryption from your tablet and you should be able to flash the jb rom of choice that does not require stock 4.2 bootloader.

[Help!] XT926 Mega Bricked

Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.

kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style

I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.

kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57

scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.

kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks

bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.

kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style

Failed all the way.

kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.

I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:

Did you try the manual steps that I posted in my links?

i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.

So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.

kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)

penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.

What do you mean with recovery?

kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.

Keeps saying it can't mount anything.

kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen

[Q] Activation Problem - Boot Loop

So I sold an unopened, sealed Nexus 5 to someone last night and he's having a problem activating the device.
Here is his description of what happened:
"I popped in the SIM card, the loading proceeded as normally. It said it was activating and then a box popped up saying that "android is upgrading system files" or something like that. It restarted and went back to the language selection screen. I pressed English, next and then it went to the connect to wifi screen, froze and then restarted before I could even connect. Now it just loads on the boot"
I had him boot into recovery and do a factory reset, but the result is the same. I had him do a 2nd factory reset just be sure, but again, same result.
My thought is the system upgrade didn't happen correctly and not is corrupted.
What's the best course of action? Can I use the WugFresh toolkit to flash stock and unroot, or would I have to do it through ADB since the phone can't boot into the system?
I don't want to leave the buyer hanging, he seems like a nice guy, but I'm just not sure how to proceed?

Use ADB and flash the factory image for him.

Synyster06Gates said:
Use ADB and flash the factory image for him.
Click to expand...
Click to collapse
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.

SeanPlunk said:
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
Click to expand...
Click to collapse
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!

switchfo0t said:
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
Click to expand...
Click to collapse
Hello, I am the buyer of this Nexus device. I was able to successfully do these steps above, and reload the stock image for the Nexus 5. However, I am still running into issues.
WITH SIM:
I was able to get to the home screen after the initial setup, sent a few test text messages to my Google Voice number successfully, and browse on Chrome for a little bit before the device froze and restarted. After it restarted, I let it load up again, tried setting up my Google account on the device, then it froze again. All of the freezing happens within 3-5 minutes of using the phone.
So I decided to go into the bootloader, and do a factory wipe/cache wipe, and proceed without having the sim card in. I was able to get to the wifi selection screen, select my router, but as soon as the keyboard was suppose to pop up, the device froze and restarted. I am now just stuck on the welcome screen.
Any ideas now?
---------- Post added 29th November 2013 at 12:45 AM ---------- Previous post was 28th November 2013 at 11:56 PM ----------
Update: So I'm not sure what happened, but I ended up locking the device through Wug's Nexus Toolkit, inserted my sim card, and proceeded to set up the phone normally. So far everything has been working perfectly fine. I can receive/send texts, make and receive calls, and do normal functions with the phone without it locking up and restarting. Fingers crossed it'll stay like this.
Any idea on why this would've happened in the first place with the device?
---------- Post added at 01:38 AM ---------- Previous post was at 12:45 AM ----------
Update 2: Well, I noticed that it will randomly reboot every half hour or so it seems. It's kind of random, but I'm not sure what else could be causing these random reboots. The phone itself is working fine, but I just started experiencing random restarts.

Are you still on the stock rom or custom?

neomorphix said:
Are you still on the stock rom or custom?
Click to expand...
Click to collapse
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
Jaybot said:
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
Click to expand...
Click to collapse
It was working fine earlier. I put it on the charger and got it to about 50%, used it for a little bit, then bam. It froze, and restarted all over again. I can use the phone maybe 5 - 10 minutes before it starts to recharge. Sometimes It'll automatically reboot after even unlocking the device.

I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.

Jaybot said:
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Click to expand...
Click to collapse
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.

neomorphix said:
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
Click to expand...
Click to collapse
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.

Jaybot said:
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Click to expand...
Click to collapse
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.

neomorphix said:
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
Click to expand...
Click to collapse
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.

Jaybot said:
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Click to expand...
Click to collapse
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.

Jaybot said:
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
Ok. This just sucks. But as with any mass produced product there is bound to be the ocasional issue.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.

theesotericone said:
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
Click to expand...
Click to collapse
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.

Jaybot said:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
neomorphix said:
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Click to expand...
Click to collapse
Just saw that. OP by your earlier symptoms I rules out a stuck power button. With the new info I'd look into it further. If the phone is just looping over and over it could be a stuck power button, Mash the power button repeatedly for a minute. Then try and reboot. A few other people have had this on the N5 already and it's a notorious issue on some Samsung phones.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
If it comes to that, how do I go about transferring the warranty over?
I feel really bad, I just don't get it. I bought two of them, the other buyer hasn't had any problems. Both brand new, sealed, in the box. Go figure.

[Q] Did my M8 self-destruct?

Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.

Settings and command prompt pics showing problem

bb1981 said:
Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.
Click to expand...
Click to collapse
bb1981 said:
Settings and command prompt pics showing problem
Click to expand...
Click to collapse
Do you always run it in airplane mode?
?

I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.

bb1981 said:
I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.
Click to expand...
Click to collapse
Which method did you use for the RUU? Exe or sd?

Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.

bb1981 said:
Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.
Click to expand...
Click to collapse
Did you try a factory reset from stock recovery/hboot yet?

I'll try that next. I just tried it but it seems like I don't have a recovery installed. Instead of saying recovery booting, it just bootloops.

just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.

bb1981 said:
just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.
Click to expand...
Click to collapse
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.

dottat said:
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.
Click to expand...
Click to collapse
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:

bb1981 said:
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:
Click to expand...
Click to collapse
Did you try flashing the newest twrp 2.8.0.3 recovery ?

Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.

Roefastford said:
Did you try flashing the newest twrp 2.8.0.3 recovery ?
Click to expand...
Click to collapse
Twrp does work although I haven't tried it this time just to see if I could try a factory reset to maybe get back my lost baseband and IMEI.
smeejaytee said:
Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.
Click to expand...
Click to collapse
I wish I could. The phone once booted will reboot itself after a few minutes.

Oh ok sorry that didn't help.

smeejaytee said:
Oh ok sorry that didn't help.
Click to expand...
Click to collapse
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?

bb1981 said:
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?
Click to expand...
Click to collapse
Partitions can get corrupted but as far as I'm aware the only way to fix it is with soff I'm not positive because there is an option in twrp to repair partitions also you may be able to use that without soff.

_)(_(45466_!!$$%[¥|[]®]«¥°]<<° xda app...why do I not have permission to post? [/rant]
I picked up a replacement gunmetal gray m8 on swappa and am considering putting the red one up on the boneyard there to give someone a chance to poke around with it. I was wondering if a partition that twrp doesn't have in the repair section like the one for radio/modem for instance could get damaged. The RUU should take care off any problems like that though so I'm officially stumped and haven't really had any extra time to do any troubleshooting.

bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse

dottat said:
bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse
I finally got wise and did a copy and paste after something like 5 times saying I didn't have permission lol....that sounds like a great idea. More (and better) support and understanding is always good.
Click to expand...
Click to collapse

Restoring TWRP backup resulted in QCom Crash dump screen

I had some problems regarding google not syncing contacts and wanted to restore my TWRP backup I made yesterday. I have been on Official Pie with magisk. I simply restored my backup and now the phone immediatly crashes to the qualcom crash dump screen. I still have access to custom Recovery though, using latest blue_spark. Why did this happen and how can I fix it? Did I restore something wrong? I used the original settings. Is it the weird partitioning which is causing this?

So I had this happen to me a couple of times last weekend when attempting to upgrade to Pie. On a couple of occasions I couldn't get past the Dump screen, no matter what I did - just used the MSMTool to restore my phone to factory. However, in one instance, I could boot into recovery. Unfortunately, this happened to me so many times last weekend, I forget how I solved it when I could boot into TWRP. I may have just flashed the OnePlus Pie 9.0 zip again. I assume your backup was also Pie?

azsl1326 said:
So I had this happen to me a couple of times last weekend when attempting to upgrade to Pie. On a couple of occasions I couldn't get past the Dump screen, no matter what I did - just used the MSMTool to restore my phone to factory. However, in one instance, I could boot into recovery. Unfortunately, this happened to me so many times last weekend, I forget how I solved it when I could boot into TWRP. I may have just flashed the OnePlus Pie 9.0 zip again. I assume your backup was also Pie?
Click to expand...
Click to collapse
Yeah, I'm in a similar situation. I was just able to boot into TWRP several times back and forth, wiped everything and installed clean Pie.zip. Now I get a screen saying device is corrupt press power button. If I press the power button twice, it boots into the rom just fine. So the phone works and all, to bad you can't restore backups anymore though. Now I just need to remove this darn corrupt screen, its super annoying.

baxtex said:
Yeah, I'm in a similar situation. I was just able to boot into TWRP, wiped everything and installed clean Pie.zip. Now I get a screen saying device is corrupt press power button. If I press the power button twice, it boots into the rom just fine. So the phone works and all, to bad you can't restore backups anymore though. Now I just need to remove this darn corrupt screen, its super annoying.
Edit:
Reflashed TWRP and the corrupt screen disappeared. Now all is well again. Now where did I put that titanium backup...
Click to expand...
Click to collapse
I had that happen too. It was an absolute mess and I wasted my Sunday fixing it. I think the only way to get rid of that message is to use the MSMTool. I believe I read that in one of the posts on the Pie thread.
EDIT: Just read your Edit - that's good news. Wished I would have tried that.

azsl1326 said:
I had that happen today. It was an absolute mess and I wasted my Sunday fixing it. I think the only way to get rid of that message is to use the MSMTool. I believe I read that in one of the posts on the Pie thread.
Click to expand...
Click to collapse
Darn it... I'l think I'l pass for now. I briefly looked at the unbrick guide thread but there wasn't any clear instructions on how to do it.
Funny thing, this is the first timeI had so much problems with flashing stuff on, and here I thought it would be easy, that this was a "developer friendly" phone. :S
Edit: I was mistaken, probably only fixed it temporarly when I flashed new recovery.

baxtex said:
Darn it... I'l think I'l pass for now. I briefly looked at the unbrick guide thread but there wasn't any clear instructions on how to do it.
Funny thing, this is the first timeI had so much problems with flashing stuff on, and here I thought it would be easy, that this was a "developer friendly" phone. :S
Click to expand...
Click to collapse
Yea, the whole a/b partition messed up developer friendly....at least initially. I have spent more time fixing flashes gone bad than I have for all of my other android phones combined. It seems to have settled down now though. Although, I haven't tried any other ROMs outside of OOS. On my prior phones, I would have no problem switching between them often.
The MSMTool isn't that hard. The instructions look intimidating. However, here's what I did when I got the Qualcomm dump screen.
- Open MSM Tool
- Open Device Manager and looked for Ports and the phone.
- Held down Power + Volume Up on the phone
- Waited for the Port (for the phone) to change under the Ports tab in Device Manager
- MSMTool should start downloading. Just let it finish and then you should be good to go

azsl1326 said:
Yea, the whole a/b partition messed up developer friendly....at least initially. I have spent more time fixing flashes gone bad than I have for all of my other android phones combined. It seems to have settled down now though. Although, I haven't tried any other ROMs outside of OOS. On my prior phones, I would have no problem switching between them often.
The MSMTool isn't that hard. The instructions look intimidating. However, here's what I did when I got the Qualcomm dump screen.
- Open MSM Tool
- Open Device Manager and looked for Ports.
- Held down Power + Volume Up on the phone
- Waited for the Port (for the phone) to change under the Ports tab in Device Manager
- MSMTool should start downloading. Just let it finish and then you should be good to go
Click to expand...
Click to collapse
I agree.
Oh really? Because there were links to all shady chinese files all over the place. I'm refering to this thread:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Thanks a lot for your help!

baxtex said:
I agree.
Oh really? Because there were links to all shady chinese files all over the place. I'm refering to this thread:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Thanks a lot for your help!
Click to expand...
Click to collapse
Yea, I saw that thread too. I just download the tool, MsmDownloadToolV4.0InternationalVersionOxygenOS5.1 .5.rar and ran it. Didn't need anything else and everything fell into place.

azsl1326 said:
Yea, I saw that thread too. I just download the tool, MsmDownloadToolV4.0InternationalVersionOxygenOS5.1 .5.rar and ran it. Didn't need anything else and everything fell into place.
Click to expand...
Click to collapse
Again, thanks a million! Will try it next time I mess up this phone. (soon probably)