Hi guys I used PixelExperience 11 rom for 4-5 months last week phone freezed while charging I force rebooted it, after reboot, it freezed again I waited for the respond but phone turned off and not responded to anything until (charging, odin mode etc) phone charge finished and I booted with stock rom same thing happened again today. now I will wait again but I don't want this to happen again. what do you think is the problem? (so sorry for bad englsıh)
Note: this problem not happens on OrangeFox or TWRP recovery, only on system
please guys help
Try using some stable rom, kernel and recovery. Also while installing custom rom clear the system and other data neatly.
Related
Hi guys,
My tablet suddenly went crazy since i installed Cm 10.1 , used to crash everywhile till yesterday where it crashed if failed to boot the room where only it gets stuck at the M motorola Logo screen, i decided im going to reflash the rom with its compatible Gapps thats when i faced another problem where my Rogue xm Recovery cant mount either cache or sdcard or internal memory, i kept restarting recovery but with no hope , till i found out i have to open recovery and wait like 3-5 mins till recovery can read device memory-internal memory, cache etc- - LIKE DEVICE WENT TOO SLOW- , i reflashed the rom but again doesnt boot, tried another EOS rom with its Gapps but also same result stuck at motorola boot screen - I FLASH LIKE A PRO wiping everything before flashing- i tried to flash another recovery TWRP but it couldnt read internal sdcard although its modded for that. Please give me some clues this tablet carries sweet memories of 2+ years :/
khafaga said:
Hi guys,
My tablet suddenly went crazy since i installed Cm 10.1 , used to crash everywhile till yesterday where it crashed if failed to boot the room where only it gets stuck at the M motorola Logo screen, i decided im going to reflash the rom with its compatible Gapps thats when i faced another problem where my Rogue xm Recovery cant mount either cache or sdcard or internal memory, i kept restarting recovery but with no hope , till i found out i have to open recovery and wait like 3-5 mins till recovery can read device memory-internal memory, cache etc- - LIKE DEVICE WENT TOO SLOW- , i reflashed the rom but again doesnt boot, tried another EOS rom with its Gapps but also same result stuck at motorola boot screen - I FLASH LIKE A PRO wiping everything before flashing- i tried to flash another recovery TWRP but it couldnt read internal sdcard although its modded for that. Please give me some clues this tablet carries sweet memories of 2+ years :/
Click to expand...
Click to collapse
hi please let me know if you got xoom fixed ?
I have similar issue after installing CM10.1 , tablet stucked on boot logo and because none of my volume buttons work I have no idea how to fix is ! ?
have this tablet for 3 years , it's a lot of stuff there
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!
Thread closed / Duplicate
Hi, I don't know what to do anymore, I can't flash any rom because phone reboots by itself when im in recovery, after 15-20 second it restarts, I tried to flash stock rom using odin but same thing happens, when new stock rom booted when I come to that part where I need to setup a langugage it shuts off all by itself and reboot, I can't charge him because same thing happens and I have about 30% battery left so don't have much time to fix this problem, did anyone had that kind of the problem?
after flashing new rom, go to recovery and do factory reset or wipe all data. and try new charger
Sent from my E6653 using Tapatalk
what about this, it says there is some bug and phone turn off in the middle of backup or when I'm installing new rom? I think that the same thing is happening to me, I tried fixed recovery but no luck, phone is still turning off after 20 seconds in recovery, I would like to install cm 11 but as soon as installation starts phone turns off in recovery
i think this could be some problem with hardware, i have galaxy s plus for 6 years, and few days ago i played it, and flashed pacman rom 4.2.2, all i had is some problems with newer twrp recovery, but after i flashed twrp 2.2.2.1 and everything was fine later.
gs+ was one of my favorite android phone, so easy to flash custom roms.
Sent from my E6653 using Tapatalk
everything was ok 4 years until I flashed cm 12, it was slow and I wanted to flash cm 11 but when I tried to flash it after 30% installation phone shut off, from then I can't flash nothing normally
in order to flash cm 12 I had to format data partition to ext4, maybe that is the problem with restarting?
it could be, I dont have that phone anymore, my sister's son is using this phone right know as a toy
Sent from my E6653 using Tapatalk
Please help me out as I messed my phone up real bad recently and I need to fix it as soon as I can as I have interviews right now and need to be updated with them.
So here's what I did:
I was using Pixel Experience ROM on Android 12, with OrangeFox recovery, it was working fine with no major issues.
I really wanted to try out Android 13 though it's still in Beta but I have heard good things about it, specially the one by Project Elixir.
But since I was already using Pixel Experience and loved the ROM so much, I decided to be on the safer side and look if they have a Android 13 ROM for my phone.
That's where the story began, I mistook the Redmi Note 7 forum (lavender) as Redmi Note 7 Pro forum, I forgot how they were two separate devices.
So I flashed the Redmi Note 7 recovery on my phone and it it didn't boot into recovery when I tried it to, then I downloaded the original (correct one) from OrangeFox's official site and flashed it after which the recovery works. But then as I tried installing the new ROM, my adb sideload kept getting stuck at "Starting ADB Sideload feature" and I couldn't make it work, so I flashed the new OS from my sdcard. It was all fine, I set it up and was loving the experience until I plugged it out of the charger. After a few minutes of plugging it out of the charger, it literally started rebooting and it restarts just in the middle of the boot animation. And when I manually power it on by pressing and holding the power button, it displays that It has no charge left.
I tried flashing quite a few other ROMs too, even Android 12 and 13 both, and at a point for some reason it also showed "system has been destroyed. press the power button to shut down" while booting into recovery but it went away once I re-flashed the recovery, and after no luck, I flashed MIUI but the same thing still persists.
I read in a few forums that it might be a battery issue which I too thought at first but the fact that it happened exactly after I flashed the wrong recovery bothers me. I thought installing the stock MIUI rom through fastboot would solve it by replacing every corrupted files and partitions but the issue seems to persist.
What might have been the issue and what can I do to fix it, and can flashing a wrong recovery cause this even if I have flashed the right one just after that?