Database Users

[Q] Bootloop whenever I flash ANY ROM

I restored my phone and flashed CM10.1.2 with 4.2.2 Gapps, cleared caches and rebooted. I keep getting stuck in a boot loop with the CyanogenMod circle spinning. I also tried with PA3 with its Gapps and same deal, I got stuck in the boot loop with the shark changing colours.
What do I do?!??! This makes no sense. I am rooted, installed BusyBox and have TWRP flashed.
Help....
This has been going on for like 3 days now.

Format data too. I know it sucks but its what you have to do.
Sent from my Nexus 4 using Tapatalk 4 Beta

maulich said:
Format data too. I know it sucks but its what you have to do.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Omg thank you. Maybe now I can start getting everything I lost when I wiped.
and

Is your bootloader unlocked?
Sent from my Nexus 4 using Tapatalk 4 Beta
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
Glad I could help
Sent from my Nexus 4 using Tapatalk 4 Beta

maulich said:
Is your bootloader unlocked?
Sent from my Nexus 4 using Tapatalk 4 Beta
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
Glad I could help
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I believe so. How come the WiFi bars are not blue?

That means Google has not synced yet, but you still have network.
Sent from my Nexus 4 using Tapatalk 4 Beta

maulich said:
That means Google has not synced yet, but you still have network.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I added my Google account and synced it. But the WiFi icon is still grey.

Google pushing a bugfix for Android 4.4 KitKit [KRT16S]

Hopefully it fixes some things which is keeping me from wanting to update.
http://www.androidcentral.com/googl...exus-devices?utm_source=ac&utm_medium=twitter

I've updated, but no new build number.
Sent from my 2014 Nexus 7 using Tapatalk 4.4

habylab said:
I've updated, but no new build number.
Sent from my 2014 Nexus 7 using Tapatalk 4.4
Click to expand...
Click to collapse
Yes there is a new build number
Sent from my Nexus 7 using xda app-developers app

Just got the update too here in UK.
I am rooted with twrp recovery. Can I just install this then re-root ? Or will twrp fail to install it. I have no access to my pc to go back to stock first.
Cheers.

Dr0iD9 said:
Just got the update too here in UK.
I am rooted with twrp recovery. Can I just install this then re-root ? Or will twrp fail to install it. I have no access to my pc to go back to stock first.
Cheers.
Click to expand...
Click to collapse
It flashed stock recovery AND broke root on me. Be warned.
Sent from my SGH-T699 using XDA Premium 4 mobile app

ruggie0 said:
It flashed stock recovery AND broke root on me. Be warned.
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks I will be waiting to install this then.

Matrix_19 said:
Yes there is a new build number
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not here. All it does is correct the name of the bootloader.
Sent from my 2014 Nexus 7 using Tapatalk 4.4

Dr0iD9 said:
Thanks I will be waiting to install this then.
Click to expand...
Click to collapse
It did not affect my recovery, only lost root.

I'm running the Flashed official 4.4 update with the stock kernel and the 4.4 boot loader with TWRP recovery... Would it be safe for me to perform the OTA?
Sent from my Nexus 7 using XDA Premium 4 mobile app

Abel669 said:
I'm running the Flashed official 4.4 update with the stock kernel and the 4.4 boot loader with TWRP recovery... Would it be safe for me to perform the OTA?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For me is just lost root, but can gain back easily by flash the su.zip. However, had read some encounter recovery revert back to stock.

lenrek said:
It did not affect my recovery, only lost root.
Click to expand...
Click to collapse
Build number KRT16S
Killed TWRP
Re-flashed TWRP and su

Abel669 said:
I'm running the Flashed official 4.4 update with the stock kernel and the 4.4 boot loader with TWRP recovery... Would it be safe for me to perform the OTA?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I lost root and TWRP. WugFresh Toolkit brought it all back. Though, could be just a random event, but when it was suppose to boot to the bootloader the second time, it didn't. Had to start the process over. Worked fine after that.
Sent from my Nexus 7 using Tapatalk 4

LoopDoGG79 said:
I lost root and TWRP. WugFresh Toolkit brought it all back. Though, could be just a random event, but when it was suppose to boot to the bootloader the second time, it didn't. Had to start the process over. Worked fine after that.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'm now going to make fun of you for using a toolkit to flash recovery and instal su on a nexus device.

xdhall said:
I'm now going to make fun of you for using a toolkit to flash recovery and instal su on a nexus device.
Click to expand...
Click to collapse
Don't care, got root.
Sent from my Nexus 7 using Tapatalk 4

Here is the Kitkat minor 3.4MB patch.
Razor:
http://android.clients.google.com/p....signed-razor-KRT16S-from-KRT16O.67b84ced.zip
Nakasi:
http://android.clients.google.com/p...signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
Manta:
http://android.clients.google.com/p...gned-mantaray-KRT16S-from-KRT16O.95106d22.zip
Source: http://ausdroid.net/2013/11/20/goog...android-4-4-kitkat-build-krt16s-minor-bug-fix
I found the article by looking at my logcat and matching up the filename.

wilsonlam97 said:
Here is the Kitkat minor 3.4MB patch.
Razor:
http://android.clients.google.com/p....signed-razor-KRT16S-from-KRT16O.67b84ced.zip
Nakasi:
http://android.clients.google.com/p...signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
Manta:
http://android.clients.google.com/p...gned-mantaray-KRT16S-from-KRT16O.95106d22.zip
Source: http://ausdroid.net/2013/11/20/goog...android-4-4-kitkat-build-krt16s-minor-bug-fix
I found the article by looking at my logcat and matching up the filename.
Click to expand...
Click to collapse
Anybody have any idea what bug fixes this patch formally addresses? (Release notes)

wilsonlam97 said:
Here is the Kitkat minor 3.4MB patch.
Razor:
http://android.clients.google.com/p....signed-razor-KRT16S-from-KRT16O.67b84ced.zip
Nakasi:
http://android.clients.google.com/p...signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
Manta:
http://android.clients.google.com/p...gned-mantaray-KRT16S-from-KRT16O.95106d22.zip
Source: http://ausdroid.net/2013/11/20/goog...android-4-4-kitkat-build-krt16s-minor-bug-fix
I found the article by looking at my logcat and matching up the filename.
Click to expand...
Click to collapse
Can I flash this over stock rooted 4.4 using cwm > install zip from sdcard?

codahq said:
Anybody have any idea what bug fixes this patch formally addresses? (Release notes)
Click to expand...
Click to collapse
I have no idea. Maybe the touchscreen was fixed because it feels pretty good to me. Before it was a little iffy.
MWFD said:
Can I flash this over stock rooted 4.4 using cwm > install zip from sdcard?
Click to expand...
Click to collapse
Yes.

MWFD said:
Can I flash this over stock rooted 4.4 using cwm > install zip from sdcard?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6 using Tapatalk 4
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
wilsonlam97 said:
Yes.
Click to expand...
Click to collapse
Bah. You beat me to it.
Sent from my Nexus 6 using Tapatalk 4

xdhall said:
Yes.
Sent from my Nexus 6 using Tapatalk 4
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
Bah. You beat me to it.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
i tried to flash this over stock rooted 4.4 using twrp and install zip from sdcard and failed????

Got the prompt for 4.4.3 on ATT, do I do it?

I'm on 4.4.2 rooted.
Sent from my LG-D800 using xda app-developers app

Dkrizzle said:
I'm on 4.4.2 rooted.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Im pretty sure its not 4.4.3. What you received is a patch to 4.4.2 to fix Google+ and such.

Dkrizzle said:
I'm on 4.4.2 rooted.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Why not? If you have the bluetooth wakelock bug, then 4.4.3 update is rumoured to fix this, and other system bugs. You could also download then share the update with devs so they could make their ROM's more stable. Just a thought.
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
daraj said:
Im pretty sure its not 4.4.3. What you received is a patch to 4.4.2 to fix Google+ and such.
Click to expand...
Click to collapse
Sprint has begun seeding 4.4.3 to N5 users via OTA, so it is possible (however unlikely) that AT&T are seeding to G2 users...

I've always been told you shouldn't do OTA updates when rooted?
Sent from my LG-D800 using xda app-developers app

Kiwi_Dude said:
Why not? If you have the bluetooth wakelock bug, then 4.4.3 update is rumoured to fix this, and other system bugs. You could also download then share the update with devs so they could make their ROM's more stable. Just a thought.
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
Sprint has begun seeding 4.4.3 to N5 users via OTA, so it is possible (however unlikely) that AT&T are seeding to G2 users...
Click to expand...
Click to collapse
The newer phones like G Pro 2 or Flex doesn't even have 4.4.3. In fact, only Nexus now is getting it. So yes maybe next year AT&T will seed it.

Dkrizzle said:
I've always been told you shouldn't do OTA updates when rooted?
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I was rooted (stock) on 4.4.2 and took the OTA and kept root. Just used the AutoRec tool and I now have TWRP and am running CloudyPro II. :good:

Lollipop Upgrade - OTA or Factory Image?

I'm rooted with 4.4.4 and TWRP recovery. When updates come out, I flash the ota zip using TWRP and have never had any issues. With the Lollipop update right around the corner, I'd like to know if one is better than the other as far as flashing the OTA vs the factory image. Is one better, cleaner, more efficient than the other? Like does flashing the factory image leave less junk files behind? Or are they pretty much the same thing?

shobuddy said:
I'm rooted with 4.4.4 and TWRP recovery. When updates come out, I flash the ota zip using TWRP and have never had any issues. With the Lollipop update right around the corner, I'd like to know if one is better than the other as far as flashing the OTA vs the factory image. Is one better, cleaner, more efficient than the other? Like does flashing the factory image leave less junk files behind? Or are they pretty much the same thing?
Click to expand...
Click to collapse
Flashing the image will wipe your device. So if you're looking to start fresh that is the way to go.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Flashing the image will wipe your device. So if you're looking to start fresh that is the way to go.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks
That aside, is there a difference as far as the phone and the system files are concerned?

shobuddy said:
Thanks
That aside, is there a difference as far as the phone and the system files are concerned?
Click to expand...
Click to collapse
And if you flash the AOSP build, could it recieve OTA updates from Google later?

jd1639 said:
Flashing the image will wipe your device. So if you're looking to start fresh that is the way to go.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
unless you hold off flashing the userdata.img part of the factory.img, then you get to keep your data.
---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------
shobuddy said:
Thanks
That aside, is there a difference as far as the phone and the system files are concerned?
Click to expand...
Click to collapse
no difference at all. the only difference is how you flash.
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
davidpoiu said:
And if you flash the AOSP build, could it recieve OTA updates from Google later?
Click to expand...
Click to collapse
no. aosp is not stock. they differ very slightly.

When's the update coming??
Sent from my Nexus 4 using XDA Free mobile app

arkangel72 said:
When's the update coming??
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
next year

arkangel72 said:
When's the update coming??
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
november 12th from what i hear, thats wednesday.

I'm waiting for the OTA.. Patiently
Sent from my Nexus 4 using XDA Free mobile app

Factory image...always factory image OTA is just too much hassle for me, especially with the new security. You can't have made a single change in the system partition at all....even SU, build.prop, etc. If you have, it will fail. This is just way too much to worry about every time I need to reinstall for one reason or another....and I do it often. So it's got to be a factory image for me, since I can run TiBu, wipe with recovery, then $ fastboot flash system system.img less headaches = profit!

I prefer factory image
Inviato dal mio Nexus 4 utilizzando Tapatalk

OTA then hard reset
Recenty I started to go by way of OTA and then perform a hard reset. Not sure if there is a difference.

Will safetrap gonna e available now that we have root ?

im just curious about it

randy-247 said:
im just curious about it
Click to expand...
Click to collapse
I dont think so so happy I got back root today..Maybe multisysyem which is tricky Im looking into it

I've tried the KK safestrap on Jasmine 6.1 (5.0 LP) and as far as I can tell it doesn't work for me. The developer has stopped the support of it so our only hope is a tool to make it compatible or perhaps someone else to pick up the development of satestrap at some point if possible?

After 5.0 they had fireflash or flashfire I think. Can't remember the name and worked for me on with 5.0 before. which is like the safestrap
Sent from my VS985 4G using Tapatalk

thunderblaster88 said:
After 5.0 they had fireflash or flashfire I think. Can't remember the name and worked for me on with 5.0 before. which is like the safestrap
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Flashfire
Sent from my SM-N900V using Tapatalk

Flash fire Is not a recovery..don't think. If something goes wrong flash fire does not come to rescue. It's an app
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
So was safestrap but it hijacked boot
Sent from my SM-N900V using XDA Premium 4 mobile app

davekaz said:
Flash fire Is not a recovery..don't think. If something goes wrong flash fire does not come to rescue. It's an app
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
So was safestrap but it hijacked boot
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And since SS is loaded before the OS booted, then if there was a problem booting such as a bootloop, SS would allow you to recover a backup. Flashfire only works if the OS is able to load. Most important to me is the ability to access the OS files via the file manager and rename files. Many times when trying a MOD you may rename the original files and the new files will cause a bootloop. In this case SS will allow you to restore the backup files. Flashfire is useless for this.

Fireflash is sketchy at best. Lol.
But SS doesn't and for the note 3 prolly will never work on LP
Sent from my SM-N900V using Tapatalk