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...
So I was on a early January build of Mahdi Roms. I decided today to update it. I was told to wipe everything flash the radio zip, cloudy rom. let it boot up then flash the new mahdi rom.
However, im on twrp 2.6.3. and when i flashed the radio and flashed the stock rom it booted up into twrp instead. I tried wiping and reflashing but it failed. I tried to reboot but it said my device isnt rooted and need to install SU so i swiped to continue however my device froze on the LG logo for about 10+ minute. So here I am still with no working phone for about 2 hours
any idea as to what to do?
I have been using CM12.1 on an LG G2 D802 and decided to upgrade the device to CM 13 today. As the device was running the stock 4.4 ROM before I initially switched to CM 12.1, I figured it would already have the Kitkat bootloader installed and proceeded to download the latest CM 13 nightly from the CM page as well the stock OpenGapps package. I then booted into TWRP (v2.6.3.3), wiped system, dalvik, data and cache and then flashed the ROM and the Gapps package which worked just fine.
However, when I selected "reboot system", the screen went black. I turned the phone off by pressing the power button. turned it on again and found that the LG logo flashes up for less than 1 second, then the screen goes black again. Gladly, I am still able to boot into TWRP. I then searched the forums, decided to try the latest Lollipop bootstack from this thread and reflashed the ROM and the Gapps package, but the problem still persits.
I am now thinking if my seriously outdated TWRP version is causing the problem, but I hesitate to update that (as it is basically the only working thing on the phone right now) without making sure that it really could be the problem.
Do you have any tips for me what could be the problem and how I can fix the phone?
Thank you very much!
Any help is appreciated
lg g2 bricked
YassinTP said:
Any help is appreciated
Click to expand...
Click to collapse
bro does ur phone goes in download mode? if yes flash tot. if not i will solve ur issue through teamviewer. dont worry it will be solved.
YassinTP said:
Any help is appreciated
Click to expand...
Click to collapse
to boot into system you need hybrid bootstacks, and definitiverly need thermal twrp 2.8.7.3
you could either do both. download twrp and bootstaclks the hybrid ones.
first update twrp if you want. but i recomend as it has thermal to control heat during installations
once you in twrp. wipe all. then reboot into recovery from recovery.
flash hybrid bootstacks then again reboot into recovery from recovery, and when you in twrp flash rom it should boot.
just remeber to reboot into recovery each time you flash twrp ot hybrids to take effect.
I officially upgraded to 3.0.2, unlocked and rooted my phone.
It was fine for the first few times I flashed multiple ROMs. But ever since I flashed Exodus, I keep having issues switching to different ROM.
A week ago, I flashed "Switch to OOS3_H2OSMMv7" zip and was able to flash Resurrection Remix, but today when I tried switching to CM13 or PA it gets stuck at flashing the ROM zip. I tried flashing the firmware zip again and flash the ROM, but to no avail. It won't flash any ROMs now, just stuck at recovery while flashing the zip.
I have a working fastboot and recovery mode though, so I'm trying to avoid flashing the entire factory image but that seems to be only option left. Does anyone have any clue as to why this is happening and how I can fix it?
Edit: Resurrection Remix gets installed fine, CM13 and PA still giving me issues.
Edit: I downloaded the latest version of CM13 and it works. Earlier I was using June 30 build which seems to have issues with the new firmware. I'll try out the new PA build to see if it fixes that too.
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
piyushmodi01 said:
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
Click to expand...
Click to collapse
It does not show any error as it just looping while installing the zip. I have to force shut down the phone to exit it.
Yes, I have backed up all my data
Yes, I am able to access my phone in both ADB and in fastboot modes.
After flashing Custom ROM, Wipe data, cache, d-cache and then reboot.
If still doesnt work try flashing another custom ROM. You can use adb-sideload to flash another zip in recovery mod.
Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.
First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.
alopez_666 said:
Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.
Click to expand...
Click to collapse
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread
F4nno said:
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread
Click to expand...
Click to collapse
I already tried, it did not work, I have installed last gapps 8.1, last twrp, last everything and it never works, it keeps stucking again and again.
same ****ty problem with my 3s 2gb .. doesnt matter which oreo 8.1 rom i flash.. tried almost 4 oreo 8.1 roms.. all couldnt boot.. and if by chance it boots then cant add google account..
yet to try that 'Mount' thing solution suggested by Williams
You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!
I face the same issue with a Redmi 3 S (global version) with 3 GB RAM. Nougat ROM's are fine but all Oreo ROM's which I tried (most recent builds of PixelExperience, crDroid, Atomic-OS) show these boot loops. This is all with the latest TWRP installed (also tried custom builds), cleaned properly my device and was using the linked Oreo GAPPS. I usually flash in one instance 1) ROM, 2) GAPPS and 3) Magisk.
The only time I had a working Oreo ROM was after several tries with PixelExperience where on my last try I booted into safe mode and it somehow worked after that.
AidANiem said:
You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!
Click to expand...
Click to collapse
go **** your mother, she likes it
william.johhn7! said:
First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.
Click to expand...
Click to collapse
Thanks, it worked for me:
1 - full wipe and format
2 - install rom
3 - install gapps
4 - mount system
5 - reboot system