After installing kitkat ~1 month ago my tablet was fast. But then a week before it started being slow as hell, so i finally decided to install a custom rom. I installed revolt but the home button didnt work. Then i tried installing PA3.99 but in the recovery menu it said failed. I tried a couple of other roms but they also failed(all 4.3 roms). Then i thought it was because of 4.4 and installed factory 4.3 by using the bat inside the image. It formats userdata. Everything gone(but i got a backup of apps so it doesn't matter too much). Tried installing a few roms. Again mistakes. Then finally installed stock 4.4 rom and everything works. My question is why is this happening? (my recovery is twrp 2.6.3.1) I want to install other roms
P.S. has anyone else had these kinds of problems?
Related
Hi,
i have a problem flashing the Sentinel 5.0 Rom with the latest Trinity kernel to my rooted Nexus 10 via recovery. I tried twice now and once it booted fine but 30 minutes after restoring my apps with Titanium backup, it stopped at the google font following a reboot.
Then i wiped everything and formatted data in recovery, flashed rom, gapps, kernel and wiped dalvik/cache and fixed the permissions.
This time around it doesn't even boot to the rom, but is stuck on the google font from the beginning.
What am i doing wrong?
Something i noticed is that TWRP tells me my device does not appear to be rooted and if i want to install supersu, not sure if this
is significant.
Thank you
edit: apparently it is not the rom. I tried another rom and another kernel and the same thing is happening.
Anything else to try other than flashing stock recovery and rom?
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.
Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...
Hi, like a month ago I Installed 10.2 CM but now I want to go back to stock 4.4 but everytime I try to do smoething, I encounter another problem.
I found a 4.4 stock ROM so I thought I will just install it, Wipe date and cache, and then just flash the rom, But It didnt work for some reason. I thought the problem was my outdated TWRP so I tried to install the latest TWRP but then I understood that I formated my computer so the fastboot drivers are not installed, so I tried to install them, but no matter what I do, It just doesn't work. I dont really know what to do so If someone can tell me stage by stage what should I do to revert back to stock, I'd be happy to hear because I Dont really know
Thanks!
Hi all,
For the past few days I've been trying to flash new ROMs. I'm a noon but have previously flashed probably 100 times with no problems at all.
Ive stuck with psx for about 3 months and live it, but as updates for the ROM have become a hasstke to get, I thought I'd try something else, but this time move on to KitKat custom ROMs instead of 4.3.
Now here's the problem. I'm doing everything the same as I usually would, d/l ROM, appropriate gapps, use latest twrp, factory reset, flash and then..... FAILED update : ( : ( Now I am a noobso am I missing something big time???, do I need to completely wipe phone when flashing from 4.3 to KitKat??, pls help, I'm sick to death of going through the fail/restore process
Thanks in advance : )
Are you updating the bootloader and radio when moving from 4.3 to 4.4? Did you try formatting the system before installing?
I transitioned from jellybean to KitKat too yesterday and had that same problem. From what i remember, what I did was when I got that failed update message in twrp, i first clicked home, then click reboot, then select to recovery. It should then warn you're about to reboot w/out a ROM/system. I swiped yes. Then it should prompt u to install supersu. Go ahead and swipe yes. It should then reboot u back to recovery and u can proceed to do your normal install routine. Now I'm adjusting myself to KitKat life!
Sent from my Nexus 4 using Tapatalk
I had that problem flashing ROMs with TWRP as well. I had to unmount the system, then everything flashed successfully!
Use cwrm instead , brotha from another motha twrp has issues with kitkat
Sent from my Nexus 4 using Tapatalk 4
You need a custom boot image for kitkat
Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.