My device has been booting for 10 mins for far since updating to 5.0 is this an issue?
I was previously running Purity ROM with Khaons Kernel System/Data/Cache were all on F2FS format.
I used Wugs Nexus Tool Kit and flashed 5.0 image Stock unroot.
Many Thanks.
Hi,
did you do a full wipe in stock recovery? I came from the same rom und without a wipe it will not boot.
Andi
Related
I had stock Android 4.3 and wanted to get USB OTG to have more space using powered USB.
I first downloaded and installed Nexus root toolkit 1.6.6 and Unlocked the boot loader and then rooted the phone (pre -requisites for loading ziddey-otg-r165-07291101. zip)
All went well.
I am at Android 4.3 and rooted and then I went to recovery (TWRP) and then selected Install and selected the .zip that I downloaded from XDA.
Boom!
I tried to reboot the phone and ever since stuck in the start up screen just displaying the google icon for nearly 15 minutes. Did i just manage to brick my phone? Please help!
Also I am currently using the same toolkit to re-install factory stock Nexus 4 Android 4.3
Will the ziddey-otg-r165-07291101.zip not work at android 4.3? Please help any suggestions are welcome.
Thanks,
Sandy
This zip is not supported with Android 4.3.
Tell me if you need help in restoring your device to stock.
Sent from my Nexus 4 using Tapatalk 4
3 solutions
You can ether re flash stock 4.3 kernel
Or 2 you can flash any rom or stock android version and u can install the ROM from side loader in recovery
3 you can try to wipe data factory reset from recovery and cache partition vs dalvik cache
Just keep flashing Roms don't stop trying
Solved
Thanks guys. I was able to re-load stoc 4.3 and all looks good now. Still awaiting the OTg for the 4.3 and following ziddey's thread for the hack.
OTG not workin
I am running on CM10.2 with my Nexus 4. I have bought an OTG Y cable and flash kernel from Ziddey and... constant bootloop
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!
Trying to install CM11 on Note 3 international Qualcomm. Rooted with CF-Autoroot, flashed TWRP with Recovery Tools and then booted into recovery and wiped everything and installed CM11 nightly from SDCARD. It came up as 'FAILED'.
I did a backup but internal storage is not showing up and I wiped it afterwards. I have backed up original recovery.
I also tried flashing a previously nightly with no luck. Also tried flashing this: [OnLine][07.02.2014] X-NOTE build 9.0 N9005 NA7 4.4.2 - flashes successfully but does not boot from samsung splash screen.
I was on stock 4.3 prior to doing any rooting etc..
How do I get back to stock 4.3 or successfully install 4.3?
Thanks in advance.
Can't get back to 4.3 once you've upgraded your boot loader - which it appears you have done with x note 9. look at the TWRP thread and get the version for KK and it should work.
If by some reason your BL hasn't upgraded, then just flash a 4.3 rom.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hi
Recently i decided to install Autodroid rom on my nexus 2012,no luck.Then i tried 2 of slimkat roms,Nothing worked.
It always keeps on booting the custom roms for infinite time(waited 20 minutes) and then reverted back to stock lollipop.
Here is what i did
I unlocked bootloader
rooted device
did factory reset from TWRP,
flashed rom zip
cleared dalvik cache.
reboot
Am i missing anything.Please help me .I am new to nexus 7 custom roms.
Hey guys,
Im trying to get my G2 to run the latest MIUI release - however i've run into some problems.
Background:
- D802
- Running Cloudy 3.2 (L)
- TWRP 2.8.6.1 installed and working
- MIUI ROM - Author: gtbluesky Version: 5.6.20 (MIUI6) Size: 886.29M
So I boot into Recovery, Flash the ROM, Wipe caches, wipe data, wipe system, flash the ROM again for good measure, reboot.
At this point, the device sits on the MIUI boot screen forever - it does not boot.
What am I doing wrong here? I think, the issue could be that the ROM above is based on KK and not L, where as I am running L. Does this mean I need to flash the KK Bootloader before I flash the MIUI ROM?
Im going to attempt to sideload and reflash Cloudy in the mean time, but I assume that using autorec to flash a KK BL and THEN booting into recovery to flash MIUI would fix the issue?
Any help appreciated..
EDIT:
_ can access the device via logcat, and can use fastboot/adb etc. I'm now back up and running on Cloudy thanks to adb sideload.