[Q] Strange bootloop problem - ONE Q&A, Help & Troubleshooting

I have been successfully running custom lollipop rom's from november, but couple of weeks ago it changed.
I installed some new rom to my OPO, can't remember what. It installed and run fine, but when I disconnected the usb cable connected to pc it freezed and started bootlooping. Phone sometimes boots to os but freezes immediately and bootloops again. If I connect it back to pc, everything works fine.
I managed to get it working by restoring to stock and locking bootloader with OneToolkit for OS X. But there were some problems; the screen wouldn't rotate, battery drains a lot faster, like in 10 hours with very little use, and many more. I unlocked bootloader, installed custom recovery and rooted, nothing changed, but when I installed different rom bootloop starts again. I've tried with many roms. It does'n matter if I install the rom with usb connected or not.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
With these two guides the phone works normally, but still can't use any other roms.
"make_ext4fs /dev/block/mmcblk0p15" fix didn't do anything.
Any similar problems?
Sorry for my bad english.

I am facing the same problem.
Someone please help us fix this problem.

Do you have the latest firmware flashed? That is a requirement for most LP ROMS lately. It normally posted on the first post of the ROM's forums, its also included in the lastest CM12 nightlies from what I've read.

Related

[Q] Galaxy S - MIUI ICS problem

Hey xda.
Recently I flashed my GS with this rom (http://forum.xda-developers.com/showthread.php?t=1449156&page=), but just in a older version(pre-alpha) and after probably a month of use I began to experienced at lot og bugs and suddenly crashes in apps and programs. I decided to do a reboot,battery pull or wipe cache to see if that clould do it, but nothing help. On the contrary, my phone would not start. The Galaxy S logo showed u, but when the miui xiaomi.com logo showed it bootlooped. Several reboots did not work, so i decided to mount usb from recovery and download the newest version of the rom and then try to flash. I did not wipe, but i worked just fine and i thought i had my phone back, but after little over a day of use the screen began to flicker and blink, and no programs nor apps worked, just crashed. I flashed again again but nothing worked, and now i'm stuck with the same problem as before. bootloop..
So have anyone experienced the same or does anyone have a solution for this problem?

[Q] How-to restore a TF300T with the newest firmware that is not starting up

Dear guys and girls,
I have a problem. Since 2 days my tf300t is for some reason not starting up anymore. The start screen does not go away. Before it worked like a charm. I have tried almost everything, I can think of. As far as I know the latest firmware is installed. The problem is also that the tablet isn't in developer mode. So my options are limited afaik to fastboot. I have installed the naked drivers version 0.73. But windows is saying that the device is not started. Only fastboot is started as device. I have tried to reinstall the firmware by usb, but to no avail. It sends but doesn't write... I have drained the battery to zero level. Can anyone help me with this? What am I missing?
<>< A Dieu
Jaco Oversluizen
I'm also having this same issue. Tablet was working fine and then froze up. After rebooting we are now stuck on the Asus screen with the circular logo going. Waited over an hour with no change. Tried to boot into recovery and recovery crashes and gives me Error! This is a stock tablet that hasn't been unlocked or anything.
Update: Did a Data Wipe and the device rebooted and came up. Doing all the updates again. Hopefully it wont mess up again.
So you have an unlocked bootloader ?

[Q] Asus TF300T boot loop CM11/OMNIROM logos

(backstory) Hi, ive had an Asus TF300T, for about 3 years now, unlocked, rooted it pretty early on... cycled between cyanogenmod and omnirom quite a bit, without really any major issues. Until today, i was running Cyanogenmods latest nightly build (CM11 Nov 5 2014), it worked just as any other nightly does a few bugs here and there, but nothing major and i hadn't done any major flashing or modding to the device. On my home from university, I turned my tablet off. And when i got home i plugged in the charger, and just as always the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.5
I had TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Edit: I dont know why, but when i try using fastboot or adb, the device isnt recognized. It doesnt show up on device manager either. I dont know if its the cable cause i bought it new, it says its can sync data, or a faulty charge/sync port....
razr9622 said:
(backstory) the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.1 (I know that theres a newer version 10.6.1.27.5, but when i try to flash it, the recovery says error and fails)
I have TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Click to expand...
Click to collapse
^THIS!
I was just to open a similar thread, then i saw your post. I join your request for help!
A month ago i have done a favor to a friend by unlocking his tf300t and installing CM11 on it. A few days ago he comes to me with this problem. I've tried anything but still no success:
- restore a backup done before flashing CM11 --> restore ends correctly but the problem remains
- flash a rom (CM11 and OmniRom) --> flash ends correctly but the problem remains
- flash the stock firmware found on asus website (WW_epad-user-10.6.1.27.5.zip, the SKU is correct for my version) --> the flash process stuck (i had to force restart the tablet after almost 2 hours of "flashing")
Since the boot animation changes according to the rom, i suppose the flashing process works. But the problem remains: after a few seconds the animation freeze and the device restarts, in loop.
Informations on the system:
- build 10.6.1.27.5
- TWRP v2.7.0.1 (working!)
- adb works (i managed to set /data as rw and push the .zip file to flash)
- fastboot should work
Please help! I feel a bit responsible for bricking my friend's device
SOLVED!
Finally!
I had already tried this method, before requesting for help, but the first time didn't worked... I don't know why this evening the tablet decided to collaborate:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
That worked for me! :victory:

Flashed wrong recovery. Re-flashed correct recovery. Installed ROM. Phone turns off randomly while plugged out of charger and says no battery left.

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?

Phone Freezes On All ROMS

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.

Categories

Resources