Related
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
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
D0UBLEJUMP said:
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions: https://developers.google.com/android/nexus/images
krs360 said:
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions
Click to expand...
Click to collapse
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
D0UBLEJUMP said:
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
Click to expand...
Click to collapse
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
theesotericone said:
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
Click to expand...
Click to collapse
Bootloader always relocks when the phone restarts :/
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
BirchBarlow said:
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
Click to expand...
Click to collapse
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
D0UBLEJUMP said:
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
Click to expand...
Click to collapse
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
nexus.freak said:
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
Click to expand...
Click to collapse
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Niflheimer said:
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Click to expand...
Click to collapse
Woohoo! Flag reset!
Judging by what I found when I was looking around it doesn't seem like bad emmc is too common, couldn't find many suffering the same issues as me.
As for triggers, my brother's Nexus worked completely fine just like mine, then powered off, powered on, and broken. So...I guess the message of the story is to never turn them off (or try reflash) and they'll be fine?
If you bought phone of play store you can send it to google, there was a tread here some time ago and it said that google accept to replace phones with temper flag and unlocked bootloader.
Good luck
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
EDIT: More googling today. Looks like my E:/Persist partition is corrupted or something, trying to figure out how to repair it right now.
Anjo_Smash said:
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
Click to expand...
Click to collapse
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
bitdomo said:
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
Click to expand...
Click to collapse
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Anjo_Smash said:
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Click to expand...
Click to collapse
I made a thread about it. Here it is http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
I made a thread about it. Here is it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Anjo_Smash said:
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Click to expand...
Click to collapse
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
bitdomo said:
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
Click to expand...
Click to collapse
Thanks for the offer. I'll try on my own and get back to you maybe tomorrow if I can't get it down.
Alright so I am definitely having problems running adb shell. even if I change the directory in cmd to my adb.exe location (android\android-sdk\platform-tools) I keep getting the error adb shell is not a recognized blah blah blah....
NVM got it working. Whenever I get frustrated enough to make a post I end up finally finding a solution.
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Anjo_Smash said:
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Click to expand...
Click to collapse
Just copy them to the root of your internal storage, then follow the guide.
I mean you just open the phone's internal storage from your PC and you dont open any folder. You just copy it there.
The guide is for nexus 5, but some people refer to the internal storage as sdcard too. I know it is a bit confusing. Thanks to point it out. I will make clear in my guide now.
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Anjo_Smash said:
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Click to expand...
Click to collapse
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
bitdomo said:
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
Click to expand...
Click to collapse
Should I try formatting it again?
Anjo_Smash said:
Should I try formatting it again?
Click to expand...
Click to collapse
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
Ok I'm going to install team viewer then.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
I'm all set up, so let me know when you are available friend, thanks for your help.
Anjo_Smash said:
I'm all set up, so let me know when you are available friend, thanks for your help.
Click to expand...
Click to collapse
I am here, send the login infos -> [email protected]
HI I have 1+1 and its 2 years 3 month old. Presently its on CM13 MM(oxygen OS I guess) and rooted and have a recovery also. I did root and recovery around 8 months back.
2 days back when mobile was in pocket and 35% battery it went in to bootloop. after lot of stuffs like clearing cache and dalvik cache nothing worked.
Later at night i found out that mobile is working fine when its connected to charging (either by lapi or Mob charger). Hence I didn't go back to old recovery.
yesterday fully drained my battery and later charged to full and found same issue.
I am not able to make out whats the issue and how to move forward if I don't want to loose my resent data state. PLs guys help me to solve this issue.
will do whatever needed to restore my mobile. TIA
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Hunting_Party10 said:
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Click to expand...
Click to collapse
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
praveen4u13 said:
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
Click to expand...
Click to collapse
Try a factory reset?
Mr.Ak said:
Try a factory reset?
Click to expand...
Click to collapse
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
praveen4u13 said:
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
Click to expand...
Click to collapse
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Mr.Ak said:
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Click to expand...
Click to collapse
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
praveen4u13 said:
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
Click to expand...
Click to collapse
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Mr.Ak said:
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Click to expand...
Click to collapse
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Mr.Ak said:
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Click to expand...
Click to collapse
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
is it not strange that so many people (including) have started facing this issue suddenly in the past two months?
I too am facing this issue. Has anyone managed to find a fix for the issue?
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Did flashing cos13 fixed the issue? I'm also facing the same issue
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
praveen4u13 said:
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
Click to expand...
Click to collapse
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
piez97 said:
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
Click to expand...
Click to collapse
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
praveen4u13 said:
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
Click to expand...
Click to collapse
I contacted my nearest customer care. They said that they have to analyze the phone and it would take almost 15 days. Did you get a new battery?
praveen4u13 said:
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
Click to expand...
Click to collapse
Same issue, start from 3 days ago...
Without charger or power bank i can't use phone [emoji19]
My phone is old around 2.5+ year
Sent from my A0001 using Tapatalk
Me too having the same issue. Seems like OnePlus one devices have some kind of kill switch to ruin it after 2.5 years. Quite a few number of people seems to have this issue all of a sudden.
Hello guys, I'm having trouble unlocking the bootloader, I tried all the possibilities on YouTube, and I waited 168 hours, but in the end the same problem
Hi, what exactly have you done?
I am still in waiting list... on tuesday I will be able to tell if I have been successful or not...
Never touch the unlock option in Developer options once 168hours countdown is started. If you do this, countdown will reset.
What you can do is simulate the the unlocking thru your pc every day in order to review the remaining hours
Beside of the unlock option, you should never remove the sim card.
Guys. Try this one, it worked for me. It took me a number of attempts. I cound not get a countdown until I used this one.
mi unlock - KKWorld.in
kkworld.in
Bryceicle1971 said:
Guys. Try this one, it worked for me. It took me a number of attempts. I cound not get a countdown until I used this one.
mi unlock - KKWorld.in
kkworld.in
Click to expand...
Click to collapse
doesn't work...
Morello12 said:
doesn't work...
Click to expand...
Click to collapse
I'm sorry man. Took me about 28 days. If you get a countdown an leave you sim untouched it should work
I used https://forum.xda-developers.com/t/tool-xiaomitool-xiaomi-rom-changing-made-easy.3627081/ and worked perfectly. I got troubled using it only because when the phone was in fastboot mode my user had no permission to access it.