Database Info

[Q] Bootloop after Flashing OC Metallice Kernel

Downloaded the Kernel from this website below:
http://rootzwiki.com/topic/25777-kernelaospv2updated-519-gt-p3113-kernel-ocucuvgpuoc-448mhz-etc/
Installed through CWM with zip
Now stuck on a bootloop (when I press the power button, it only reboots it self. doesn't turn off)
The bootloop doesn't go on to my ROM. Stuck on the Samsung GALAXY TAB 2 7.0 logo. My GTab is GT-P3113.
Thankfully, still can go to CWM with ease. (Power + Vol Up) Everything still accessible. Just how to boot to ROM. If going back to stock kernel fixes it, fine. Just give me the link and I'll give it a try(I feel bad for not backing up my kernel). Please help ASAP:crying:.
P.S. I'm on CM11 for P3110. Works fine, even the IR blaster. Just if anyone needs this information
Late Question: Does re-flashing CM11 on the tab restore the stock kernel? If so, is the appdata going to be saved if I re-flash the ROM?

Fixed: booted to ROM
Anyone facing the same problem, just re-flash your ROM (in my case CM11) and GApps if needed. To my surprise, it reboots back to the home screen. Now, I have the problem of android.process.acore crashing. Help?:crying:

That kernel and link are ancient, I wouldn't flash even if you paid me $809,786.00 dollars. There's plenty 0f roms around forum with proven track records. Update you recoveryand your odin try flashing again.
Pp.

Also this Kernel is from 2012 - CM 11 wasn't released
Send from OnePlus One using Tapatalk

[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:

black screen

hi there! my opo shows me only a black screen, I've experienced this problem before and all it took to fix it was to keep power button pressed for about 20 secs for 3 or 4 times and then it normally boot, but this time it doesn't seem to work. (I've been using the latest cyanhacker with lollipop for a few days, don't know if it's involved somehow).
any suggestions?

Were you previously on a KitKat ROM? If so did you update your firmware and modem appropriately when moving to Lollipop?
Transmitted via Bacon

timmaaa said:
Were you previously on a KitKat ROM? If so did you update your firmware and modem appropriately when moving to Lollipop?
Transmitted via Bacon
Click to expand...
Click to collapse
I was on a kitkat ROM, I installed cyanhacker v3 via twrp recovery and it worked just fine for a week or so. Then I had a crash and, when booting up the phone, I couldn't see the 1+ logo. As i said, it's something I had experienced when I was on stock cm11s, and I could fix it just keeping power button pressed - 'though this time it didn't work (maybe due to the custom rom installed). So I tried the "colorOS method" as described here http://forum.xda-developers.com/one...nel-black-screen-fastboot-adb-t2835696/page14 , I can correctly flash it, but when I boot up I still see black with retroillumination. Last i tried to intall stock rom via http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418 , phone gets correctly identified and goes through the flash procedure, but then it stays black. what can i do?

VERY Slow Boot after flashing Nethunter

Hi guys hope you are having a nice sunday.
I am facing a quite annoying issue after flashing Nethunter on my Oneplus One: every time I boot the phone, the device gets stuck for about 6/7 minutes on the 1+ logo, then the animation appears for few seconds before it finally boots.
I have had this issue with stock CM12.1+Nethunter 3 for OPO CM12.1, and now I am having it with a CM13 nightly + a custom Nethunter that works on CM13. In both cases the device boots up in seconds until flashing nethunter.
I did try to reflash once again (just in case) and I still have the same problem.
Scenario:
Wipe the whole device
Flash CM13 (or 12.1)
Flash Gapps
Reboot and configure android
Reboot again to test boot speed - it boots up super fast
Go to recovery again and flash Nethunter
Wipe dalvik+cache
Reboot
From now on it takes 6/7 minutes to boot
Liveboot Log (only appears during kali animation though, not sue it's logging what happens during the kernel logo):
txt log file > drive.google.com/file/d/0B7y82quVQHh6elliMmFXdUJFSjQ/view?usp=sharing
virus check > virustotal.com/it/url/60a0f8536b0053f104a5d8dcf06a8cc27f89736d0fd915572b75790e12cad031/analysis/1456660030/
Tried with many versions of TWRP (from 2.6 to 3.0.1), nothing. Also, when I boot into recovery, I see the recovery logo for about 5 minutes before I can actually get into the recovery.
I hope someone has got an idea about how to fix this, as you can understand it's very frustrating having a phone that takes half of a big bang theory episode to boot.
Let me know if I can provide more info about my device!
Thanks a lot.

pLx_ said:
Hi guys hope you are having a nice sunday.
I am facing a quite annoying issue after flashing Nethunter on my Oneplus One: every time I boot the phone, the device gets stuck for about 6/7 minutes on the 1+ logo, then the animation appears for few seconds before it finally boots.
I have had this issue with stock CM12.1+Nethunter 3 for OPO CM12.1, and now I am having it with a CM13 nightly + a custom Nethunter that works on CM13. In both cases the device boots up in seconds until flashing nethunter.
I did try to reflash once again (just in case) and I still have the same problem.
Scenario:
Wipe the whole device
Flash CM13 (or 12.1)
Flash Gapps
Reboot and configure android
Reboot again to test boot speed - it boots up super fast
Go to recovery again and flash Nethunter
Wipe dalvik+cache
Reboot
From now on it takes 6/7 minutes to boot
Liveboot Log (only appears during kali animation though, not sue it's logging what happens during the kernel logo):
txt log file > drive.google.com/file/d/0B7y82quVQHh6elliMmFXdUJFSjQ/view?usp=sharing
virus check > virustotal.com/it/url/60a0f8536b0053f104a5d8dcf06a8cc27f89736d0fd915572b75790e12cad031/analysis/1456660030/
Tried with many versions of TWRP (from 2.6 to 3.0.1), nothing. Also, when I boot into recovery, I see the recovery logo for about 5 minutes before I can actually get into the recovery.
I hope someone has got an idea about how to fix this, as you can understand it's very frustrating having a phone that takes half of a big bang theory episode to boot.
Let me know if I can provide more info about my device!
Thanks a lot.
Click to expand...
Click to collapse
My 2013 nexus 7 hangs on the google logo for about 5 minutes as well so I guess it's normal :/

What are the main purposes of NetHunter? It seems like it's some kind of counter offensive security tool or some network backdoor discovery tool. I've never heard of this before.

@noahvt it is not normal, I have tried to reproduce the same situation on a friend of mine's device which is exactly the same as mine, same baseband, same kernel, same nightly rom, same file for Nethunter, an exact copy of my phone. His phone boots in seconds.. It's not normal, especially when boot to recovery it shouldnt hang for 5 minutes on the recovery logo.
-
@SirSoviet
https://www.offensive-security.com/kali-linux-nethunter-download/
Nethunter is basically a Kali Linux port for Android, which allows you to pentest your network. A bit of googling will give you more info about it.

pLx_ said:
@noahvt it is not normal, I have tried to reproduce the same situation on a friend of mine's device which is exactly the same as mine, same baseband, same kernel, same nightly rom, same file for Nethunter, an exact copy of my phone. His phone boots in seconds.. It's not normal, especially when boot to recovery it shouldnt hang for 5 minutes on the recovery logo.
-
@SirSoviet
https://www.offensive-security.com/kali-linux-nethunter-download/
Nethunter is basically a Kali Linux port for Android, which allows you to pentest your network. A bit of googling will give you more info about it.
Click to expand...
Click to collapse
Just built my own version of it and it boots slow as well on my one+ so don't know what's wrong :/

I have the same issues also, the main OS feels pretty unstable (had it freeze on me twice and had to hard reboot it), gonna try a different base maybe Calkulin's or a previous CM 12.1 build.

nfusion77 said:
I have the same issues also, the main OS feels pretty unstable (had it freeze on me twice and had to hard reboot it), gonna try a different base maybe Calkulin's or a previous CM 12.1 build.
Click to expand...
Click to collapse
I wish you good luck, though I've tried both CM12.1 and CM13 and unfortunately had the same issue. Hope it will do the trick for you!

hello pLx_, i got same trouble, but i install patch "kernel-nethunter-flocm-marshmallow-3.1.0" from "https://idlekernel [dot] com/nethunter/nightly/" (flocm, not flo!) and its works fine.
hope it will help you.

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?