Hey i'm new to android stuff but i have followed the steps for flashing the custom rom (unlockbootloader, root, custom recovery twrp, wipe system cache dalvik, and install zip and gapps) it's working perfectly on 4.2.2 but in 4.3 it seems stuck on the boot animation, is there any special steps on 4.3 build?
I'm using stock 4.3, sorry for my bad english
Read this thread. Here is explained what went wrong at google.
http://forum.xda-developers.com/showthread.php?t=2382880
Related
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
ifonuser78 said:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
This happens with many including me some time with many diffrnt files chainging and overwriting causes the same
Best option as u said above flash stock firmware
Then u can try what I feel will work better in ur case
Root the phone with CF root method
Flash Philz Recovery
wipe cache / dalvik / ix perm and reboot and go ahead with ur Rom flashing
Ok, flashed the stock ROM which was not rooted, then rooted using CF's method and flashed PhilZ. I couldn't find the option to fix permissions in PhilZ recovery, and went ahead with the installation of Omega 9 after wiping. I couldn't even get Omega to boot, previously it worked on the first boot and then no longer after a restart.
I don't know whats going on here.
I'm flashing the pre-rooted MGA now.
ifonuser78 said:
I'm flashing the pre-rooted MGA now.
Click to expand...
Click to collapse
Pre-rooted MGA works fine, but no other custom ROM.
I ran TriangleAway to reset the counter, but that didn't help either. No third party custom ROMs for me. :crying:
Flash latest Philz recovery.
Go to mounts and storage.
MAKE SURE YOU HAVE A ROM ON SD CARD.
Format system, cache, data and preload.
then just to be sure everything is gone I go to wipe /data factory reset and choose the wipe to install a new rom.
Then go to install zip and flash rom.
Once it's flashed you should be good to reboot.
If you're still in a bootloop then go to wipe/data factory reset but choose first option not the one to install rom.
Now reboot again, good to go!
Just a thought, if you're still having trouble flash a AOSP kernel in Philz as you might be trying to boot an AOSP rom with a TW kernel installed
Sent from my GT-I9505 using XDA Premium HD app
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.
bump
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.
Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)
Hi everyone,
I'm planning on upgrading my Nexus 4 to KitKat.
Currently I'm using PA 3.69 (4.2.2) with Franco Kernel and CWM Recovery.
1. What files do I need to flash for the upgrade, possibly with links? (I'm going for Purity ROM)
2. In what order should I do the flashing process?
3. Should I upgrade CWM before flashing, and if yes, which is the latest version that supports 4.4 and how does upgrading work?
Thanks in advance
If you want to install stock KK, you can download the factory Occam images and install via fastboot.
If you want to install a custom rom, you may need to update your recovery to the latest version and flash a KK rom that includes an updated radio and boot img.
So you think I can:
1. Upgrade CWM to 6.0.4.5 here: http://forum.xda-developers.com/showthread.php?t=2198942
2. Flash this: http://forum.xda-developers.com/showthread.php?t=2545838, since it includes Bootloader and Radio.
3. Flash this: http://forum.xda-developers.com/showthread.php?t=2281607 (Purity ROM)
4. Flash any desired Kernel (e.g. Franco) and use Titanium backup to restore my apps?
U just have to download the Rom. Install it. Set it up. Then boot back into recovery and install the kernel
I don't think u have to update CWM. So just steps 3 and 4
I'm asking cause I am coming from 4.2.2 with old radio and bootloader and I want the most up-to-date ones.
And I am sure that just flashing the rom will cause problems... What do I need to wipe prior to flashing?
BarbaxX said:
I'm asking cause I am coming from 4.2.2 with old radio and bootloader and I want the most up-to-date ones.
And I am sure that just flashing the rom will cause problems... What do I need to wipe prior to flashing?
Click to expand...
Click to collapse
I checked the links. Your method seems to be OK.
As for wiping, you need to wipe data, cache and dalvik cache from the recovery when you flash the Purity Rom
Everything has worked flawlessly. Thanks!
I'm currently running an LS980 with a CM10.2 nightly with TWRP and either ZV8 or ZV7–they both have the same baseband? This was all the latest and greatest as of when I updated in December.
Now I'm trying to just to a decent CM11 or Pacman ROM, but I'm getting confused as I wade through disorganized threads with people with questions not related to my setup. There's a whole mess of downgrades and autorec and ioroot and other tools that I don't know if I need.
So I have CM10 and old TWRP, what do I need to do for a stable CM11?
Thanks a ton!
1. Download your rom and Gapps (usually provided on the rom thread)
2. Copy your rom and Gapps to your internal sd card (on your phone)
3. Boot into recovery
4. Wipe Data/Factory, wipe System, wipe dalvik cache
5. Install your rom first, then Gapps
6. Reboot
7. Profit !
As long as you stick with CM or other aosp-based roms, you're good to go. You don't need to do fancy things to have a working kitkat rom with root and recovery.
If you want a Stock KitKat rom, then you're going to need IOroot 2.5 to root your G2 and then use AutoRec (provided by cloudyfa) to get a working recovery.
That's it !
Edit: think about updating your recovery beforehand, it won't hurt and may save you from going back to square one
Guys..how to flashing kitkat stock rom with twrp 2.8.6.1..im always facing error when flashing this stock rom.im on ed300 cm 11 now.im newbie here.sory for my bad english.
simpang said:
Guys..how to flashing kitkat stock rom with twrp 2.8.6.1..im always facing error when flashing this stock rom.im on ed300 cm 11 now.im newbie here.sory for my bad english.
Click to expand...
Click to collapse
Nobody can help you if you don't provide the exact error. From my experience, I think you need to edit and remove the assert() line from the updater script. Alternatively, you can try this-
1. Make complete backup of you current ROM using TWRP.
2. Wipe Cache, Dalvik, System, Data partition.
3. Now instead of flashing the new stock ROM, go to advanced options and choose reboot to recovery.
4. Now, again your phone will not into recovery; and this time you should be able to flash the ROM.