my phone is almost new and freezez & reboots all by itself some times even when its kept aside, its been acting like this from day one
i have tried everything possible by book, even a RUU 1.24.401.4 & the OTA to 1.24.401.7, only unlocked bootloader & TWRP nothing else.
I am attaching the bug report captured by Developer options....PLEASE HELP!!
aryan_rulz_1983 said:
my phone is almost new and freezez & reboots all by itself some times even when its kept aside, its been acting like this from day one
i have tried everything possible by book, even a RUU 1.24.401.4 & the OTA to 1.24.401.7, only unlocked bootloader & TWRP nothing else.
I am attaching the bug report captured by Developer options....PLEASE HELP!!
Click to expand...
Click to collapse
Hey man glad that i found someone with the same problem as me..
well i got my phone about 4 months ago everything was working flawlessly until 1 month after purchase it freezes and reboot by itself.. it did it once in a week maybe,
i tried to unlock bootloader and install a custom system but there wasnt any yet(not that im interested in). well after i relocked my booloader and loaded an officiel RUU to the latest update. Eveything worked fine again,
before yesterday, in a night while i was using my phone it frooze and restard 5 times at least. it did so today also, i just want to f******* destroy the phone now. Got back my old S8 now
I'm having random freezes too. Need to hard reset my phone everytime it did.
Related
My device has been bricked for 3 month then just a few days ago someone here on xda posted a fix and it worked for me I was really happy.
Flashed custom recovery, then tried all new roms (missed 3 month).
Then yesterday I decided to sell it to my friend and wanted to revert all back to stock. Got US_10_6_1_15_3 from asus webpage. Flashed blob all went well.
All booted up fine, and just to be sure all is 100% clean i went to do a factory reset within the rom, it did its thing then rebooted.
Now its dead, Asus logo appears for 2 sec then reboot, same thing over and over. I cant even shut it down. Apx mode is available I think.
Hopefully this doesn't happen to anyone else Can anyone give me some tips?
echohack said:
My device has been bricked for 3 month then just a few days ago someone here on xda posted a fix and it worked for me I was really happy.
Flashed custom recovery, then tried all new roms (missed 3 month).
Then yesterday I decided to sell it to my friend and wanted to revert all back to stock. Got US_10_6_1_15_3 from asus webpage. Flashed blob all went well.
All booted up fine, and just to be sure all is 100% clean i went to do a factory reset within the rom, it did its thing then rebooted.
Now its dead, Asus logo appears for 2 sec then reboot, same thing over and over. I cant even shut it down. Apx mode is available I think.
Hopefully this doesn't happen to anyone else Can anyone give me some tips?
Click to expand...
Click to collapse
can you boot to fastboot?
Nope, this time its dead for good i think. Just a warning to all then.
Was on V10.6.1.27.1 bootloader running makelegs nightly builds. Then I flashed back to V10.6.1.15.3.
Then when booted up, went into settings and choose factory reset.
Baang bootloop.
Can only get Apx and thats usless since I don't have Nvflash.
I'm kinda sad, I just recovered it from the brick we all had back in may-apr. The new bootloader wrong recovery crap.
Then 2 days later This happens.
I think wiping from the settings is like wiping from the bootloader but what about trying this mate http://forum.xda-developers.com/showpost.php?p=44574476&postcount=9
Sent from my Nexus 7 using Tapatalk 4
Hi All,
The last few days my phone rebooted it self numerous times. Later on it had more hard cures cause it rebooted but the screen stayed black.
I then let the battery drain and I could luckily boot it up again. I then thought I should flash an update of the Rom I was running which was Candykat.
I did that but my wifi was not working . So I flashed it two more times. But after the third time that I wanted to do it I tried to get into recovery but the screen stayed black....
And now I am unable to boot it , unable to get in to bootloader. When I plug it in to my laptop it says QHSUSB_DLOAD.
I am S-OFF and on HBOOT 2.15 and my Rom was CandyKat v1.6
I already tried going through it by Ubuntu but ubuntu doesnt recognze my phone......
Hopefully some one can help me out ?
Also tried disconnecting the battery but that didnt help either :crying::crying:
Any one ..... ?
Hi all, I have a weird issue that every time I flash a ROM on my phone I get stuck on the bootloader screen after I restart for about 5-10 minutes until my screen turns off, then after the screen is off im able to wake it and use it regularly. I have this issue with almost every ROM I have tried. I used the RUU to restore my phone about a week ago if that matters. My phone is S-OFF and pre-rooted. Does anyone else have this issue or know what is wrong?
I think i found my issue im updating my firmware to the lastest see if that works..
Yea sounds like you r not on the newest firmware out.
Hi all,
Firstly I apologise for actually posting as I've spent a week trying to not be a twat and to fix it myself but alas I'm at the end of my tether.
OK I have a Tab 2 10.1 P5100 (thus with sim). I originally got it about 3 years ago in Poland and their OTAs are about as frequent as, well, they never happened. So, over the years whilst working there I flashed via Odin various official updates to get it up to scratch. Last one being Jelly Bean.
Everything has been fine until a week ago when suddenly it would boot, get to the log in screen, let me enter my pin, work for 10 seconds and then suddenly reboot. It's an endless loop but it's not stuck on booting up it just crashes ONCE started up fully.
It won't connect to Kies. Now, this is probably the rubbish cable (This is the third official cable in 3 years I've goe thru). The system restore option from manual booting does nothing and wipes nothing so I've been trying to just load an official ROM from the SD..that does nothing.
It starts to install and then goes back to the "no command" screen.
Can I simply download something onto the SD and install from there? the zip files I keep trying dont work.
Any advice is appreciated!
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.