Accidental crash - OnePlus 5T Questions & Answers

While going through the factory test pages, to check on my burn in, i accidentally switched my device in to aging mode. During Startup in Aging Mode it crashed and after a normal reboot i lost all my sensors, cameras and the system seems glichty. I tried everything including firmware up/down grade. Twrp full wipe and reinstall. newly flashed Boot.img and fresh install of Oxygen. Nothing helps. Anybody might have a wild guess ????

Malleges said:
While going through the factory test pages, to check on my burn in, i accidentally switched my device in to aging mode. During Startup in Aging Mode it crashed and after a normal reboot i lost all my sensors, cameras and the system seems glichty. I tried everything including firmware up/down grade. Twrp full wipe and reinstall. newly flashed Boot.img and fresh install of Oxygen. Nothing helps. Anybody might have a wild guess ????
Click to expand...
Click to collapse
Sry litteraly after the post and the 10 th time I tried it again and it finally worked.... DONT get to the Point were i was! Its hell and i dont wish it anyone
!

Malleges said:
Sry litteraly after the post and the 10 th time I tried it again and it finally worked.... DONT get to the Point were i was! Its hell and i dont wish it anyone
!
Click to expand...
Click to collapse
Just flash persist.img from fastboot mode
Fastboot flash persist persist.img
If it happens again:good:
https://drive.google.com/open?id=0B2p1k5sTiAMzUjkxWWZGNjlyb2c

Related

[Q] Potential hardware issues/ brick / batter issue? Please help

Hello all. Let me first thank you for your time in reading my post. I appreciate it. I'm not a fan of only posting for help but I suppose that the site suggesting to always search first is to thank for that because I am usually able to find answers. So please forgive me if this is posted elsewhere but I really have searched and asked around but haven't seen anything similar to my issue. If there is something like it I do not know what to call it. I at first thought it was a sudden death, but realized I think my device model & the symptoms have disproved this theory.
My story...
I bought my AT&T Galaxy S3 feb 2013. I have had it, spent a month or two stock everything. The past month & a half I have flashed CM 10.1 & most recently PK-2.32 for about 3 weeks. Have ran it and loved it with no issues. Used the kernel that comes with both ROMs.
4 days ago
I was charging my phone at work, picked it up after a while, and it wouldn't turn on. It was stuck in a loop of 2 of the screens in my attachments(the battery screen & the SGS3 logo). The battery screen is not in motion, it is stationary like that so that the circle doesn't move.
I have tested quite a few things in regard to what I thought might be the issue...other batteries, chargers, cables pull sim & SD and still no luck...etc.
While the phone is unplugged I get no indication of life. Only when I plug it in will it show me the battery symbol & the logo.
After some playing with it while it is plugged in I have been able to get it into download mode quite frequently with no issue as seen in the third attachment.
So yes I can get into download mode but I'm still "fairly new" and not sure where to proceed from here. I'm not sure what my options are as this is new to me and I can't find anything related, nor can my much more experience friend who is not so new at it that got me into wanting to load custom ROMs.
And yes, as you can see it has tripped my flash counter up once, from what I've read there's only one way to fix that if I need to send it in.
So...If you are able and willing to help I would greatly appreciate it and any options you might give me. I'm willing to try almost anything as my phone is of no use to me at this moment.
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
xBeerdroiDx said:
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
Click to expand...
Click to collapse
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
moose0003 said:
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Click to expand...
Click to collapse
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
Click to expand...
Click to collapse
Thanks again for your reply. I will try this and check back.
You are correct, it just did this, no kernel or anything. I will try wiping the device the data doesn't bother me. I won't lose much.
Have you or anyone else heard of this happening or know a cause? I could not find anything.
aybarrap1 said:
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
Click to expand...
Click to collapse
Thanks for your reply. I have a few backups. I will try stock first and see where that takes me and go from there.
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
moose0003 said:
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
Click to expand...
Click to collapse
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
metalsnakebite said:
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
Click to expand...
Click to collapse
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up.......
Click to expand...
Click to collapse
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
moose0003 said:
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
Click to expand...
Click to collapse
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
moose0003 said:
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
Click to expand...
Click to collapse
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
metalsnakebite said:
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
haha. i've done that before. cheers, buddy.
xBeerdroiDx said:
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
metalsnakebite said:
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
Thanks for the input guys. I'm having a difficult time to get it to stay into recovery now again. It acts like it wants to go in but it will just reboot. I will keep trying and if I need anymore help I will come back. Thanks so much again.
Back again. So I kept playing and was finally able to get into recovery as you guys suggested. Once I got in it finished the odin process and actually booted up! First time in a week. So ran through setup and then was able to determine that wifi is not working with stock ROM. Not sure if it's the phone or the ROM.
After it booted up and turned on was able actually do most functions, didn't test a lot wanted to see if it would work without being plugged in...this answer was no.
So after much testing I think what determines what will power it on and off is determined by what it is plugged into. I still think it is having hardware issues though because of the lack of powering on, but I am fairly certain that I can start it every time with a certain cable/charging dock.
I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.
Haven't done this yet but will start tonight & have it finished by tomorrow is the plan. If anyone has any better suggestions I would gladly take them.
So this should be my last post unless a question arises for me.
moose0003 said:
.....I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.....
Click to expand...
Click to collapse
This is what I said I was going to try to do. Took it to work and found time to do the above. TriangleAway worked a lot better than I ever thought it would. Flash counter reset, loaded unrooted stock and have a replacement on the way. Went very smoothly.
So doubt I will root & rom again until out of warranty. I appreciate everyone's help with my issue.
XDA is a great place.

[Q] HTC One X keeps turning off after new rom install

Hello all,
I'm having a bit of a problem with my HTC.
Just flashed the Tripnraver CM rom. I flashed the boot.img, then went to CWM, did
a wipe data, format system, then install zip from sd..
After the first boot (welcome, choose your language), I choose my language and then
the phone just turns off without an error message.
When I turn the phone back on, it boots normally (and again with the welcome screen).
Then again I choose my language and I can complete the setup.
Once the setup is complete, it turns off again. When I use my phone for like 5 minutes,
it will also turns off with no reason..
I flashed the correct boot.img provided in the zip.
Also, i searched the forum for people with the similar problem, but I didn't found anything
that could help me.
This is driving me crazy, I can't use my phone normally, it keeps powering off all of the sudden!
Is there someone who can provide me some information or help with this problem?
Thanks in advance!
Are you certain you wiped everything properly? Do the whole process once again and flash this script instead of wiping manually : https://www.dropbox.com/s/mh1mcpe3v2y9c1a/Super wipe script.zip
and also don't forget to fastboot erase cache after flashing the boot.img via fastboot!
Thanks for your quick response!
Gonna try it again and this time with the super wipe.
I'll post again after the progress is complete.
Okay, I flashed the boot.img, then erased cache, did a full wipe with the super wipe u linked.
Phone boots normally (ofcourse first boot takes some time), did the setup (welcome blabla),
the phone didn't went off 1 time! I guess I didn't wiped the correct way.
As far of now, my phone works normally. I waited for like 15 minutes before I made a post, because
maby the problem wasn't solved.
Thanks mate, I really appreciate it! +1
**edit** Actually I still don't know what I did wrong. You think the problem was because of the ''not correct wipe''?
Dammit, it's back again.. It turns off again.. for no reason.
This is driving me crazy ...
Do you (or others) got some more tips?
Aarrghhh!! Dammit! No idea why's this happening...
try to flash a different rom and see whether it's happening or not? Repeat the same steps to flash the new rom... (even the boot.img)
Thanks again for your reply.
I flashed another rom ( RD MIUI this time), same routine, flash boot.img, erase cache, in CWM super wipe,
then install zip from sd card. Then my phone boots into the welcome screen, and AGAIN it turns off..
I really want to throw my phone out of the windows right now..
I've not seen this problem on XDA forums so far, so i think no one can help me with this one ?
I'm beginning to think it's a hardware problem now!
Post the result of fastboot getvar version-main Will find a RUU or a nandroid backup for your device...
This would be the last thing that I could help you with... Go back to stock and see whether problem persists... if so, send it to HTC for warranty!
Alright.. thats sad to hear.. ..
My version is 3.14.401.31.
I think I can't bring it to HTC because I unlocked my bootloader so my warranty is void.
Bhagwanie said:
Alright.. thats sad to hear.. ..
My version is 3.14.401.31.
I think I can't bring it to HTC because I unlocked my bootloader so my warranty is void.
Click to expand...
Click to collapse
Download this RUU: http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
lock your bootloader: fastboot oem lock
Run the ruu on PC with admin privileges! It will take you back to full stock... Now see whether the problem persists or not!
Ig it still does, send it to HTC... Yeah, unlocked bootloader might void your warranty, but I don't think there's anything that you can do to solve it by yourself...
---------- Post added at 05:23 PM ---------- Previous post was at 05:12 PM ----------
Actually the same thing happened to me a few weeks ago. I used the wipe script as suggested by @vin4yak and followed exactly as he has instructed all to no avail. Then tried something slightly different, i used the wipe script for cache, data and system but I used the PC to format the sdcard and my Hox is fine now. Don't know why it worked but it did. Format sdcard as fat32 but change allocation size to 32 in the drop down, it should be 16 as default
Bite me
I feel your pain.
I've had this issue for quite some time.
My Phone went to HTC early on for the WIFI issue, I mentioned the rebooting issue and they said there was no issue. It's a real pain as sometimes it will go away for a few days and then return. it happens when it's freshly wiped and installed, it happens when the phone has been in use for months.
Does your Front facing crash when apps try to use it. If I use ANY rom that isn't based directly from the 4.2.2 sense ROM it goes weird.
I have flashed all manner of ROMs to try and solve it. I will post here if I find anything.
it's such a shame but I won't be buying another HTC anytime soon, HTC Desire/HD/Sensation/One X all have had really severe issues. My wife had a Galaxy S2 and now a Sony Z1. I'm thinking I get a Sony Z2 and be done with the issues.

Galaxy Nexus Boot Loop

Hey, i flashed CM11 about half a year ago. The last Saturday (20/12), it started to go in an infinite loop. First it could boot in apps, but then it crashes all the time. So What I 've tried:
Reset factory data/davlik/cache
Flashing another rom via Recovery
Bring back to stock via bootloader (cmd+fastboot)
Downloading mode (ODIN)
OmapFlash
Nothing made even a little change to my phone. It boots in the same OS, and it crashes all the time. It's like its in a readonly mode. It's like it has the program for PC Deep Freeze, that restores your phone to its first condition in every simple reboot. Can you help me plz?
dannaros said:
Hey, i flashed CM11 about half a year ago. The last Saturday (20/12), it started to go in an infinite loop. First it could boot in apps, but then it crashes all the time. So What I 've tried:
Reset factory data/davlik/cache
Flashing another rom via Recovery
Bring back to stock via bootloader (cmd+fastboot)
Downloading mode (ODIN)
OmapFlash
Nothing made even a little change to my phone. It boots in the same OS, and it crashes all the time. It's like its in a readonly mode. It's like it has the program for PC Deep Freeze, that restores your phone to its first condition in every simple reboot. Can you help me plz?
Click to expand...
Click to collapse
Forget about #1 and #2 in your list.
In #3, what happens when you try to flash the images?
efrant said:
Forget about #1 and #2 in your list.
In #3, what happens when you try to flash the images?
Click to expand...
Click to collapse
Nothing, still the same CyanogenMod OS. Even if I run oem lock, after rebooting to bootloader it will shown as unlocked again.
dannaros said:
Nothing, still the same CyanogenMod OS. Even if I run oem lock, after rebooting to bootloader it will shown as unlocked again.
Click to expand...
Click to collapse
If the images appear to flash properly in fastboot, but you are still on the same ROM, then I would suspect your NAND is toast.
efrant said:
If the images appear to flash properly in fastboot, but you are still on the same ROM, then I would suspect your NAND is toast.
Click to expand...
Click to collapse
What is NAND. Is NAND phone's internal memory? And what can I do now? Is it a solution or is it a hardware issue? Thank you for your help btw
dannaros said:
What is NAND. Is NAND phone's internal memory? And what can I do now? Is it a solution or is it a hardware issue? Thank you for your help btw
Click to expand...
Click to collapse
Yes, it's your devices internal flash memory. It looks like there is something wrong with it. (Others have had similar issues in the past.) So, yes, it looks like it's a hardware issue and there's nothing you can do yourself to fix it.
efrant said:
Yes, it's your devices internal flash memory. It looks like there is something wrong with it. (Others have had similar issues in the past.) So, yes, it looks like it's a hardware issue and there's nothing you can do yourself to fix it.
Click to expand...
Click to collapse
Ok mate. thank you so much. have a nice happy new year for you and your beloved ones. Plz reply me to my pm.

stuck on boot screen!help!(yes,it's a bit generic)

so,i have the ze551ml,and right now, i can boot it up,but it gets stuck at the asus logo,and the spinning circle below it. i see lots of people clearing cache,going into safe mode,or simply reinstalling the firmware.
first method doesn't work,i don't know how to clear device cache without actually being inside,i.e. actually have android properly loaded up
second method,just seems to get me nowhere.
third method,i tried power,then up rocker,then the recovery tab,just gives me the dead android thing with error written below.
help,this is my daily driver,so everything's on it!
also,forgot to mention,so this is a quick edit,i have adb installed(i think) on my pc,but whenever it launches,it justs has text running quickly,too fast for me to read,then self exits.
i also have to disconnect it from my pc or else it would not reboot.
umm..quick update,the recovery function now somewhat works, i managed to get the firmware from asus's webpage,put it in a ,microsd card,renamed it MOFD_SDUPDATE.zip. it seems to recognize it,at least no dead android with error sign,but after the install,it just does nothing.
it also never seems to actually finish the update,as it just gets about one third of the way,then vibrates twice,and reboots.
i did somehow manage to get it to boot up to the lock screen yesterday before i went to sleep,but then,after i woke up,it just seemed to have rebooted itself,and is stuck on the asus logo with the spinning wheel below again.
if u facing the continuously rotating circle problem in boot screen, then there is very easy solution. it is a very common problem happens for mainly low memory ,sometimes other.. it happens very often to me..
1.first clear user data then clear cache from recovery. u can also use adb from pc.
2. just restart.
[if you dont know how to open recovery, thenopen fastboot & select recovery as u mentioned in ur question, next when the dead android logo appears, dont worry. Then PRESS & HOLD VOL UP+POWER for 3 sec. it ll take few trying as it needs perfect timing to press those keys at a same time. from there you can clear data and cache.]
#PRESS THANKS IF IT HELPS YOU.
sounak1 said:
if u facing the continuously rotating circle problem in boot screen, then there is very easy solution. it is a very common problem happens for mainly low memory ,sometimes other.. it happens very often to me..
1.first clear user data then clear cache from recovery. u can also use adb from pc.
2. just restart.
if there is important data in internal memory,then try with flash the firmware. dont know if it ll solve or not as i always do the above steps and it becomes OK.
#PRESS THANKS IF IT HELPS YOU.
Click to expand...
Click to collapse
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Jasper1224 said:
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Click to expand...
Click to collapse
Try to install custom ROM, like SuperZen. I think the is when you update your ROM and it doesn't finish due to a bad download.
24imelqui said:
Try to install custom ROM, like SuperZen. I think the is when you update your ROM and it doesn't finish due to a bad download.
Click to expand...
Click to collapse
But you have to unlock bootloader for that. Not everyone wants to do that...
Perhaps it's better to install Asus Flash Tool on your computer and flash raw firmware. You could even try without clearing user data.
Jasper1224 said:
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Click to expand...
Click to collapse
just delete the internal memory..then clear cache..then restart
nothing else
sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?
sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?
Jasper1224 said:
sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?
Click to expand...
Click to collapse
sir can you help me with this please? i have the same problem right now with my asus zenfone 2 z00ad. im stuck on the asus logo with this circle. please help me.

Vibe K5 doesn't boot up

hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do
Gabriel337 said:
hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do
Click to expand...
Click to collapse
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
I tried that now, it didn't work, still on bootloop :/
Gabriel337 said:
I tried that now, it didn't work, still on bootloop :/
Click to expand...
Click to collapse
Use Qualcomm Flash tool or QFIL then ..
soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
soldiersz said:
Use Qualcomm Flash tool or QFIL then ..
Click to expand...
Click to collapse
I tried that with QFIL and Lenovo Smart Assistance. and bootloop.
But I think i've made some progress:
I tried to flashed a new rom (I flashed CM/RR/AOCP before, is with these roms the frozen lenovo screen happens), CRDROID, and it appears crdroid bootanimation, and load until it frozes and phone turn off.
Gabriel337 said:
I tried that with QFIL and Lenovo Smart Assistance. and bootloop.
But I think i've made some progress:
I tried to flashed a new rom (I flashed CM/RR/AOCP), CRDROID, and it appears crdroid bootanimation, and load until it frozes and phone turn off.
Click to expand...
Click to collapse
Wipe everything except system. It should work
soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
soldiersz said:
Use Qualcomm Flash tool or QFIL then ..
Click to expand...
Click to collapse
soldiersz said:
Wipe everything except system. It should work
Click to expand...
Click to collapse
First of all, thanks for you help!
So, I wiped, and nope, the same error happens. This is a problem that I've never seen before
Gabriel337 said:
First of all, thanks for you help!
So, I wiped, and nope, the same mistake it happens. This is a problem that I've never seen before
Click to expand...
Click to collapse
Yeah me too :crying:
Gabriel337 said:
hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do
Click to expand...
Click to collapse
I am facing the same problem :crying: Got any solution? How did u flash stock ROM?
I have flashed using qfil now device works fine
Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?
kaka9876 said:
Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?
Click to expand...
Click to collapse
You can go for Vibe k6 power. Why k5 plus?
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
kaka9876 said:
Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?
Click to expand...
Click to collapse
1) Main problem is Battery backup. It won't last long a day.
2) Stock ROM Really sucks
There is no heating issue though. It has been solved by latest updates
K5 Plus flash recovery
hey guys , I've been trying to flash a custom rom through TWRP recovery menu but by my mistake i wiped the system. now it just keeps booting up over and over on the lenovo logo. please help me with this
Youzpalang said:
hey guys , I've been trying to flash a custom rom through TWRP recovery menu but by my mistake i wiped the system. now it just keeps booting up over and over on the lenovo logo. please help me with this
Click to expand...
Click to collapse
Try entering to TWRP by using the hardware keys. Do this:
Pull down the battery.
Insert again.
Press power key, volume up and volume down at the same time, until lenovo logo dissappear.
If luck, you are into TWRP now.
connect phone to computer via usb cable. you should be able to access to internal memory.
So, copy into it any custom ROM previously downloaded from your computer, and flash it. That's all.
walterfuster said:
Try entering to TWRP by using the hardware keys. Do this:
Pull down the battery.
Insert again.
Press power key, volume up and volume down at the same time, until lenovo logo dissappear.
If luck, you are into TWRP now.
connect phone to computer via usb cable. you should be able to access to internal memory.
So, copy into it any custom ROM previously downloaded from your computer, and flash it. That's all.
Click to expand...
Click to collapse
Thanks man , What custom rom would you suggest? Is bootlegger OK?
Youzpalang said:
Thanks man , What custom rom would you suggest? Is bootlegger OK?
Click to expand...
Click to collapse
Bootleggers has some bugs, like WhatsApp not being able to play GIFs or videos. Also, after a while in the day, launcher becomes laggy (maybe a kernel settings issue). You have to reboot and becomes smooth and fast again.
I highly recommend LOS 15.1 or AEX 5.6 from Harry (yes, he is continuing the development!) Both of them have June updates.
I'm on AEX right now, which is such a marvelous ROM. It has a looot of customizations than any other ROM I've tried.
How to get them?
Search into the Harry8242 profile from AFH.
walterfuster said:
Bootleggers has some bugs, like WhatsApp not being able to play GIFs or videos. Also, after a while in the day, launcher becomes laggy (maybe a kernel settings issue). You have to reboot and becomes smooth and fast again.
I highly recommend LOS 15.1 or AEX 5.6 from Harry (yes, he is continuing the development!) Both of them have June updates.
I'm on AEX right now, which is such a marvelous ROM. It has a looot of customizations than any other ROM I've tried.
How to get them?
Search into the Harry8242 profile from AFH.
Click to expand...
Click to collapse
LOS 15.1 is fine but has some bugs too(camera zoomer not working).
I've finally decided to use a STOCK ROM and there is a complication, here is the problem:" I'm using lenovo downloader software to flash and once my phone is connected, the progress bar gets stuck at the begining level and says:"Flashing" below the status bar and " Sahara "- which have no idea what means- below the step bar and it also takes too much time to do the flashing which is never done! I have the same problem with QFIL( Sahara Fail )!
Youzpalang said:
LOS 15.1 is fine but has some bugs too(camera zoomer not working).
I've finally decided to use a STOCK ROM and there is a complication, here is the problem:" I'm using lenovo downloader software to flash and once my phone is connected, the progress bar gets stuck at the begining level and says:"Flashing" below the status bar and " Sahara "- which have no idea what means- below the step bar and it also takes too much time to do the flashing which is never done! I have the same problem with QFIL( Sahara Fail )!
Click to expand...
Click to collapse
I figured out , Problem solved!
Youzpalang said:
I figured out , Problem solved!
Click to expand...
Click to collapse
Glad to hear that! So, you've decided to stay on stock ROM. OK, it has sense. stock firmware is free of bugs, right? Now, do you know being on stock LL you can "update" to MM and thus get doze and adaptive storage?
How?
Follow this guide:
https://forum.xda-developers.com/k5-plus/how-to/guide-a6020l36-official-lenovo-andoid-6-t3596733
and you'll get the most updated official stock ROM available four our device. Actually, it's a backup made by an Brazilian user, where you should restore only system and boot partitions, in order to keep your data.
This update was only released for Brazil region, but, users from other regions in the thread, reported it worked for them.
I've tried it once, and worked like a charm.

Categories

Resources