[Q] Android starting apps [ALL ROMS] - Nexus 4 Q&A, Help & Troubleshooting

Hello,
I got a big big problem.
When i try to flash ANY rom on it it won't boot.
I tryd:
- All Nexus 4 stock rom's.
- ParanoidAndroid
- Cdroid AOSP
- SimpleAOSP
- PAC all in one.µ
- Dirty unicorn rom.
With all these rom's i dit:
1. TOTAL CLEAN (Wipe System / dalvik / cache / data / internal memory / OTG) -> REBOOT(AND ALSO ONE TRY FOR EACH ROM WITHOUT REBOOT SOMETIMES I GET THE /DATA/ MOUNT ERROR WITHOUT REBOOT)
2. ADB PUSH -> Rom's to Internal memory.
3. Install Stock/Custom Rom & Gapps.
4. reboot or install other packages's (or other way around install pkg's -> reboot)
5. Wait 15min - 2hr's every rom.
6. Reboot / wipe dalvik cache.
7. wait 15min - 2hr's every rom AGAIN.
And still i aint have any boot screen or anything.
I get the Optimizing apps screen 1 - xx(depends how much app's install in the rom)
still no screen only i get stucked ALWAYS on STARTING APPS.
PLEASE HELP ME WHAT IM DOING WRONG?
I TRYED EVERYTHING IM ALREADY DOING THIS FOR 2 WEEKS !
If you wan't footage just put in the topic and i will post a video of me flashing the rom.

Related

[Q] Help - Defy is stuck in bootloop

Hello
I've tried to upgrade my Defy (525, green lens) to CM10(jelly bean), but im stuck in a boot loop!
My phone had originally Android 2.1 installed, one year ago i successfully rooted it and Android 2.2 successfully.
What i've tried:
- load into 2nd init, wipe cache/wipe data
- install kernel-froyo-222-179-4-signed
- install CM10-20120924-NIGHTLY-mb525
- wipe dalvik cache(this does not promp for confirm, and prints nothing to the console, is this normal?), wipe data
- reboot. Now its stuck in an endless boot loop.
I can enter bootmenu/bootloader/2nd init/stable recovery. I can share here the SD card, so i can copy stuff to my phone
But as i turn on the phone, the red moto logo appears, the top LED is blue, then green, then reboot.
Did i miss something? (I've read somewhere about flashing SBF, do i need to do it?)
EDIT: I've tried to install cm-7-20120930-NIGHTLY-jordan.zip, but this gets stuck at the moto logo forever...Can i someohw see the bootlogs to fund out the problem?
Thanks
EDIT2: Solved it!
1. installed back Nordic froyo with RSD lite, rooted again
2. instaaled CM7 with this tut: http://forum.xda-developers.com/showthread.php?t=1054447
3. installed CM10 with the instructions from here: http://forum.xda-developers.com/showthread.php?t=1795647
dunno what went wrong for the 1st time, maybe upgrading from 2.2->4.1 does not work...
What went wrong
You have answered yourself. In the link to install Cm10, you will see the instruction requires you to flash froyo kernel.
For MB525 builds:
1) Go to Stable Recovery.
2) Wipe data/factory reset, wipe Cache and go to Advanced ► Wipe dalvik.
3) Go to install zip from sdcard ► Choose zip from sd card.
4) Flash froyo kernel
5) Flash CM10-2012xxxx-NIGHTLY-mb525.zip.
6) Flash Gapps.
7) Wipe Cache and Dalvik again (recommended).
8) Restart.

[HELP] Can't get Slim GAAPS to work Nexus 7 2012 HELP ME :(

Hey guys, so i'm trying to install the following items:
-SlimLp F2FS (Android L)
-M-Kernel_a73.zip
and
-Slim_full_gapps.BETA.5.0.x.build.0.x-20150213-482
I use NRT to get into TWRP and from there I follow the following steps (my system is already in F2FS mode which i reformatted from the existing Ex?? one)
Clean Flash:
Wipe syste, data, cache, dalvik cache
Flash the rom
Flash Slim gapps or L Gapps (IDK WHAT THE DIFFERENCE BETWEEN GAAPS AND L GAAPS IS and they take me ultimately to the same link so wtf)
Reboot
The main issue is, after the tablet reboots and opens up I don't see the play store, i don't see ANY google items and I can't install anything. It seems to me that the GAAPS zip isn't being installed properly. I've already installed the main ROM, then GAAPS, then the M kernel and nothing seems to work. I don't see any playstore icons even in the app drawer. Can someone please explain to me what i'm doing wrong? Thanks!
Can someone please help?
bump for a response

Screen keeps flickering

This is my first post on XDA developers and let me start by saying thanks to all developers for all those great ROMS out there. Have been a user of your modifications since day one. Recently though, I have been having problems with my Samsung Galaxy S5 (SM-900F). With the latest CM13 nightlies/Open GApps installed my screen keeps flickering when I push the Home button or On/Off button. I have TWRP installed as custom recovery and have done several clean installs with the same end results (the screen keeps flickering). I suspect this is related to the CM13 nightlies because it doesn't happen when I install a different ROM (say MIUI). It's driven me crazy because , although I can use the phone when I'm quick enough to press on an app while it's flickering, it takes forever to get out. Any help is appreciated!
cm-13.0-20160622-NIGHTLY
open_gapps-arm-6.0-mini-20160623
TWRP v2.8.7.0
Clean install:
1. Wipe Dalvik Cache/System/Data/Internal Storage/Cache
2. Install CM13
3. Wipe Cache/Dalvik
4. Install Open GApps
5. Wipe Cache/Dalvik
6. Reboot

WLAN don't work

i used custom rom paranoid 4.6beta (OS KK). before i instal custom kernel WLAN is worked properly, but after i flashing custom kernel WLAN can't be turn on. please help me! how to fix this bug. ( i was try to instal the kernel in another rom based KK and it's wored) i'm sorry i bad in english.
1. Take a backup(Select Boot, Recrovery, System)
2. Install other ROM
3. Backup(Modern, EFS)
4. Recrovery your ROM
5. Recrovery Modern, EFS
6. Clear backups
7. Wipe Cache
8. Reboot
9. Open Wifi
10. Connect to a Wifi
11. Done.

Bootlooped after install of Lineage, twice!

Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!
try this
BeansBeanson said:
Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!
Click to expand...
Click to collapse
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
whatever the rom requires(10.3.0) however the Q beta 4 works just fine, havent found any real bugs / newer security patches etc.
(CUSTOM ROM)
Latest rom that will work with BASE and TWRP decryption
(latest TWRP )
twrp 3.3.1-31 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - Q
(Latest)
custom compatible kernel
(Latest)
NanoDroid - with con/fig read alter installation notes
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp
I'm a little slow..
I got the phone back to factory with the msmtool, so I'm ready to do this! I get the general idea, but for a few of these, can you ELI5. Thanks so much for taking the time to help me out.
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer. Do I just find the zip in the file structure in twrp and install? I'm at this step in twrp and I don't see how to install it. Previously I had `adb push twrp.img /storage/` so that I had a file I could find and install. If it's already there just from `fastboot boot twrp.img`, I can't seem to find it.
--solved this by pushing the twrp-intaller.zip to /storage, and then installing. It did the expected installation to both a/b
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
I went to `mount` and checked all the boxes. Then went back to `wipe advanced` and checked all those boxes. Now I'm stuck at the fastboot screen and can't boot or start. :crying:
I can't do a `fastboot boot twrp.img either. Any suggestions before I blow it away with the msmtool again??????
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!) How was I doing it wrong? Or do you mean that these steps just now are the only mounting that should be done?
install OOS(BETA4).zip / TWRP installer What command should I use to move it from my pc to the phone? `adb push .zip storage` ?
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer Do it twice, exactly the same? Is this so it's on both slots?
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage. What command should I use for copying? Like above `adb push <files> storage`?
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
[/COLOR]just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp
Not sure what you mean by this part here. I wasn't planning on installing gapps. I'm confused about the reseting both slots. Is the idea that I did the install twice above, so that it's on both a/b slots and I'd have to reset both if there's a problem?
Click to expand...
Click to collapse

Categories

Resources