Database Info

[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] I knew this day would come...Son's TF300 won't boot

I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.

Feedback
chromegsx said:
I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.
Click to expand...
Click to collapse
I have a solution, but your not going to like it, all data will be lost....:crying:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
B. For the TF101: E101_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Let me know if you need any help along the way.... Thx as always lj

lj50036 said:
I have a solution, but your not going to like it, all data will be lost....:crying:
...
Let me know if you need any help along the way.... Thx as always lj
Click to expand...
Click to collapse
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks

SKU
chromegsx said:
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks
Click to expand...
Click to collapse
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....

lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Hey congrats on Recognized Contributor!

Happy
cmendonc2 said:
Hey congrats on Recognized Contributor!
Click to expand...
Click to collapse
I am happy about it.. Still so much to learn... Im not trying to let it go to my head...LOL:silly:

lj50036 said:
... NEVER select the WIPE DATA.. Bad things will happen...
Click to expand...
Click to collapse
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?

Data Wipe
Graiden05 said:
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?
Click to expand...
Click to collapse
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj

lj50036 said:
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj
Click to expand...
Click to collapse
Yep when I first got my tablet i was so scared about going into that menu because I learned that it was only 3-4 clicks away from a brick.

lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.

Feedback
chromegsx said:
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.
Click to expand...
Click to collapse
Yes, that is correct..but its not a ota.... So the process will wipe all data....Thx always lj

You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.

UndisputedGuy said:
You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.

chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Try installing the universal naked drivers.

cmendonc2 said:
Try installing the universal naked drivers.
Click to expand...
Click to collapse
Same result. Still nothing in Device manager.

chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.

UndisputedGuy said:
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.
Click to expand...
Click to collapse
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.

chromegsx said:
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.
Click to expand...
Click to collapse
Just wanted to follow up on this...lj50036 is top noctch helper here. going above and beyond does not even come close to explaining what he has tried to do for me. Ultimately it was after we hit a brick wall, that I suggested flashing back to an earlier version that finally worked. I'm not convinced flashing to the latest version (like I first tried) would not work, as I didn't personally create/rename the SD card to do the flash. but re-flashing the original firmware got the tablet to boot finally. Of course all was lost other than what had been automatically backed up via google servers. Pictures/videos back to exactly one year from when the pad stopped booting were recovered. Everything before a year was gone. No game data or installs were saved. I thought maybe it had to do with a space issue, but after re-installing every app my son had before and about 1GB worth of pics/videos restored, there is still 16GB left, I doubt game/user data would have consumed that much...so I still have no idea what might have cause the pad to stop booting. Other than it was trying to do something important when he ran the battery dead. So at this point I'm having my son clean out unwanted apps, and we are going to unlock and root after a proper backup is done. Thank you to all that have had input on my dilemma. I've learned a ton.

[Q] HELP! Verizon Galaxy S 5 Bricked / Stuck In Boot Loop

Problem resolved thanks to bweN diorD!

Dark System said:
Hey everyone, I figured this was the right section to post a question, sorry if I was mistaken.
So I recently rooted my phone and tried to install a custom ROM on it, turns out the ROM I selected was probably for the wrong model or something because my screen was just black. So I booted into recovery to try and restore it on the ROM I backed up and it was gone so now I'm kinda ****ed on a phone for now, before I look into buying a new one I wanna see if there's any way I can resolve this and unbrick it.
When I turn the phone on it just loops the booting screen and when I boot into recovery it just has the droid dude with an exclamation mark on it then turns off and does the boot loop.
I was wondering if maybe there's a file I can put on an external drive and it will automatically restore back to stock like on other devices.
I've done a lot stuff like this to my PS3 just never tried it for my phone so I'm just hoping there's a method out there for me, please provide any feedback or questions about it, I'm just trying to get this resolved and I have no time really to research it because of work and a newborn baby plus you guys would know more about it than me so yeah. Thanks!
Click to expand...
Click to collapse
usually when you flash the wrong software to a phone it is toast, but you may be in luck as it still turns on.
video here.
further instruction here.
if that doesnt work... well its not good unfortunately.

Dark System said:
Hey everyone, I figured this was the right section to post a question, sorry if I was mistaken.
So I recently rooted my phone and tried to install a custom ROM on it, turns out the ROM I selected was probably for the wrong model or something because my screen was just black. So I booted into recovery to try and restore it on the ROM I backed up and it was gone so now I'm kinda ****ed on a phone for now, before I look into buying a new one I wanna see if there's any way I can resolve this and unbrick it.
When I turn the phone on it just loops the booting screen and when I boot into recovery it just has the droid dude with an exclamation mark on it then turns off and does the boot loop.
I was wondering if maybe there's a file I can put on an external drive and it will automatically restore back to stock like on other devices.
I've done a lot stuff like this to my PS3 just never tried it for my phone so I'm just hoping there's a method out
for me, please provide any feedback or questions about it, I'm just trying to get this resolved and I have no time really to research it because of work and a newborn baby plus you guys would know more about it than me so yeah. Thanks!
Click to expand...
Click to collapse
Boot into bootloader and flash stock rom using odin..

bweN diorD said:
solution
Click to expand...
Click to collapse
Alright thank you! I'm pretty confident this will work, once the stock ROM file finishes downloading, which it doesn't seem that it wants to work. I've downloaded it 5 times now and every time it's done it's a fail.. I'll keep trying though.

bweN diorD said:
if that doesnt work... well its not good unfortunately.
Click to expand...
Click to collapse
yeah it didn't work, did everything right but when it tries to reboot I get the dead little droid guy.

[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

Defective ONnePlus 7 ? Help me out pls

Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .

The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.

@PriPhaze is your device stock(bootloader locked) or modified in any way?

aaycce said:
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
Click to expand...
Click to collapse
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
strongst said:
@PriPhaze is your device stock(bootloader locked) or modified in any way?
Click to expand...
Click to collapse
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.

PriPhaze said:
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
Click to expand...
Click to collapse
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?

strongst said:
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
Click to expand...
Click to collapse
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.

PriPhaze said:
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
Click to expand...
Click to collapse
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.

strongst said:
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
Click to expand...
Click to collapse
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS

PriPhaze said:
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
Click to expand...
Click to collapse
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.

strongst said:
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
Click to expand...
Click to collapse
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.

PriPhaze said:
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
Click to expand...
Click to collapse
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...

strongst said:
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
Click to expand...
Click to collapse
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US

PriPhaze said:
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
Click to expand...
Click to collapse
Yes, everything is on board. It's the worst case for, sadly...
Or you buy a device with broken screen and exchange the board /display. Depends how much you have to spent for this at all.

PriPhaze said:
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
Click to expand...
Click to collapse
Ah yes, the common misconception that power shuts it off. Nope, not this phone. You have to hold power and volume up together to power off the phone when it crashes. Make sure you're using the latest platform tools (adb/fasboot) to unlock your phone. Make sure oem unlocking is enabled in developer settings after you've unlocked, having it disabled for some reason does screwy things. Mine was disabled once when I downgraded to Android 9 using the all in one tool available on xda, I thought I bricked the phone because it wouldn't boot after a reboot. Flash the latest oos twice through the system local upgrade feature, this will put the current oos on all partitions. Use the correct twrp, the unified versions found on xda 3.3.1-75 and 3.3.1-76 work well for me. The installer zip for those can be used in magisk to flash twrp after an OTA update before reboot. So, local upgrade 100% -> magisk modules "+" twrp 3.3.1-75 unified installer zip -> reboot to recovery -> flash magisk 20.3 at least (20.4 is available now). Do this twice so that everything is the same version on all the partitions. Lastly restore apps with swift backup without data, I know it's not ideal but may be necessary because some app's data may be corrupt and causing this. Good luck. Of course at any time you have it running you can reboot in safe mode (touch and hold restart until the dialogue pops up) and see how long you can use it without any third party apps to confirm that it is an app you installed.

Man I had the exact same problem as you and I got it fixed this morning after nights of fastboot commands trial and error found this thread forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Tried a few times before it worked but saved my phone all I had was fastboot mode and no recovery make sure to manually flash all fastboot commands you will then get stock recovery back wipe using all 3 options go 1st 2nd 3rd and then 1st wipe again after reboot phone might hang just force reboot and fixed

I really appreciate all the replies really but hmm im guessing there's a misunderstanding on what im saying.
I do know how to flash and recover one plus devices using MSM tool if neccesary, also to flash the fastboot rom .
The thing here is that everytime i recover the phone and all seems stable and working good , after a2 days more less it will random freeze of death and you cant even reboot holding power button NOTHING! is completely freezed.
So yea, thats pretty much it, i have tried already all that you said so far :c.