Develop Bugs

[Q] How do I get past "initiating swagger" boot loop

Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!

http://forum.xda-developers.com/showthread.php?t=1996665

cybervibin said:
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Thanks for responding. So if the kernal is a .zip file, I should rename the entire file "boot.img" correct? I don't extact the boot.img file from the zip...

it will be in .img format by default if not try opening it and see!

cybervibin said:
it will be in .img format by default if not try opening it and see!
Click to expand...
Click to collapse
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?

ninjastic said:
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?
Click to expand...
Click to collapse
I was able to figure out that I needed to flash a older RUU to be able to flash a custom rom. :laugh:

ninjastic said:
Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!
Click to expand...
Click to collapse
Did you happen to install an ota update when you still had your stock rom on your phone?
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
ok.... never mind

Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!

It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting

donhashem.dh said:
It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting
Click to expand...
Click to collapse
Thanks for the reply. You are saying to restore my phone using the back up I created using the recovery then reflash?
Or are you saying to download a factory restore and flash that? From what the op states he needed to flash an older build.
---------- Post added at 09:36 PM ---------- Previous post was at 09:03 PM ----------
so I erased my rom, reflashed with the same image and it now boots into the rom. I am seeing a lot of issues though. The android keyboard has FC numerous times. The home button only seems to function one time, it asks which launcher to use, I select on then it will not work as a home button again. Also the button that shows all open application is opening context menus (the ... you see on some apps) instead of showing recent apps I tried reflashing again with the same results. Thoughts/comments?

are u cdma?

EDIT: Issue I has was unrelated to this thread I believe. If anyone else experiences what I described read this post, I outline everything I did and how to fix it (different gapps file )

mrdally204 said:
Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!
Click to expand...
Click to collapse
For anyone else reading this (and thx to donhashem below for elaborating) the stock RUU can be found here. Kudos to all who put these links together :good:

[Q] "Status 7" While Updating to 4.2.1, Unable to Boot

Hi,
I was running 4.2.0 on a Takju Gnex. Attempted to update to 4.2.1 using the Takju link from the Android Police website using Clockworkmod Recovery. Gave me a "Status 7" error. I tried rebooting, and it hung on the Google logo for over 10 minutes. Restarted into Recovery, no longer have a USB mounting option, so cannot connect it to my laptop anymore. If I plug it into my laptop while it's stuck on the Google logo, my laptop recognizes it as an "Android 1.0" device, but won't do anything with it like it used to.
So I can only access the Recovery on my phone, but cannot get my laptop to recognize the device (this wasn't a problem before trying to update).
Any suggestions?
EDIT: I see I can transfer files to my Gnex using adb. Is my only option to just flash a factory 4.2 image and start over?

Same here
I have the exact same problem...
Help would be much appreciated.

This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!

This might help
mmuzzy said:
- If you get a status 7 error flashing a ROM, try making sure SYSTEM is unmounted in 'mount/unmount partitions' menu in recovery. Thanks to jroid for finding the tip.
Click to expand...
Click to collapse

NeoMagus said:
This might help
Click to expand...
Click to collapse
Could also be that the device is reading that the rom was meant for another model...
OP:
Post three of the guide in my Sig.

I had same issue so I wiped cache ad Dalvik cache and went to fastboot mode and flashed system.img and boot.img also I flashed CWM touch 5.# that is not recommended on 4.2.#
I have made Deodexed rooted ROM of 4.2.1 and it's for takju.. you can find it from GNex Android development section..

aDcOoL said:
This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!
Click to expand...
Click to collapse
I've done the same and has booted now .....just "upgrading applications" as I type

aDcOoL said:
This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!
Click to expand...
Click to collapse
you just have to mention that you have to reflash cwm

Also something that may interest you guys. From koush/CWM on twitter:
Holy crap. I just found and fixed the "Status 7" bug that I've been trying to locate for months.
Click to expand...
Click to collapse

aDcOoL said:
This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!
Click to expand...
Click to collapse
As a semi-noob who has a bigxie 4.2 with CWM and the stock 4.2.1 system.img file...
...do I boot into CWM recovery, and run just "fastboot flash system system.img"? It's my first time dealing with the .img files and I'm not entirely sure how they're handled yet.

Demon-Xanth said:
As a semi-noob who has a bigxie 4.2 with CWM and the stock 4.2.1 system.img file...
...do I boot into CWM recovery, and run just "fastboot flash system system.img"? It's my first time dealing with the .img files and I'm not entirely sure how they're handled yet.
Click to expand...
Click to collapse
learn how to use fastboot here:http://forum.xda-developers.com/showthread.php?t=1529058
basically you will need do it on command prompt on a windows PC while your phone is hooked up

chickentuna said:
learn how to use fastboot here:http://forum.xda-developers.com/showthread.php?t=1529058
basically you will need do it on command prompt on a windows PC while your phone is hooked up
Click to expand...
Click to collapse
I'm aware of that step, I'm just trying to verify that it's only the system.img file that needs updating, and not the four others (boot, recovery, userdata,radio) that were in the package, and that the command I believe to be correct is the only one that needs to be run to update/return to stock without wiping the phone completely back to empty.

As an update, yes, what I was asking about did work and got me to 4.2.1 with only the need to re-root and put a widget back.

Need some help with my new Nexus 7

I just got a new Nexus 7 today and naturally, my first goal is to unlock and root.
I started by booting into the bootloader and doing "Fastboot oem unlock"
I said yes, wipe and it said it worked fine.
After that I installed the latest TWRP for the Nexus 7 2013
It installed just fine and i installed supersu 1.69 through it
for some reason it is stuck at the boot animation now and in TWRP it says 0 internal storage space and fails whenever i factory reset.
what can I do to fix this?

fenguepay said:
After that I installed the latest TWRP for the Nexus 7 2013
It installed just fine and i installed supersu 1.69 through it
for some reason it is stuck at the boot animation now and in TWRP it says 0 internal storage space and fails whenever i factory reset.
what can I do to fix this?
Click to expand...
Click to collapse
Did you try installing TWRP again?

meekrawb said:
Did you try installing TWRP again?
Click to expand...
Click to collapse
yes and i also tried installing cwm recovery too. no luck with either. im currently trying to reboot after re-unlocking.

fenguepay said:
yes and i also tried installing cwm recovery too. no luck with either. im currently trying to reboot after re-unlocking.
Click to expand...
Click to collapse
Wiping data doesn't work?
You MAY have to flash back to stock and start over.
Other people have had this problem, check here:
http://forum.xda-developers.com/showthread.php?t=2380913
Keep in mind that that thread is from before Google released the factory images. Hopefully it can help you out though.

You can also try one of scrosler's pre-rooted stock ROMs. I'd recommend using fastboot to wipe cache, system and userdata to be on the safe side.
http://www.scottsroms.com/downloads.php?do=cat&id=94

http://forum.xda-developers.com/showthread.php?t=2381582 fixed it

[Q] boot loop

Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.

DarkGruf said:
Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
Click to expand...
Click to collapse
No idea anyone ? Could it be hardware related for instance ?

Wipe system, data, cache, dalvik cache and internal. Then flash factory image.

h4xx0rr said:
Wipe system, data, cache, dalvik cache and internal. Then flash factory image.
Click to expand...
Click to collapse
I did, about 5 or 6 times and still in boot loop.
ty

DarkGruf said:
Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
Click to expand...
Click to collapse
What caused this ? Did you flash a ROM or something ?

Bootloader is unlocked (padlock symbol visible) right? If you've previously locked it, then Recovery won't do anything if you haven't unlocked.

FredFS456 said:
Bootloader is unlocked (padlock symbol visible) right? If you've previously locked it, then Recovery won't do anything if you haven't unlocked.
Click to expand...
Click to collapse
Yes it's unlocked, I can even flash a custom recovery.

Atishay Jain said:
What caused this ? Did you flash a ROM or something ?
Click to expand...
Click to collapse
It's my son's device so i don't know really but I'mquite sure he did not flash anything. I do it for him when he needs.So no, I have no idea. One minute before it was working one minut after it reboot itself and stays in boot loop.

DarkGruf said:
It's my son's device so i don't know really but I'mquite sure he did not flash anything. I do it for him when he needs.So no, I have no idea. One minute before it was working one minut after it reboot itself and stays in boot loop.
Click to expand...
Click to collapse
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.

Atishay Jain said:
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Click to expand...
Click to collapse
What is v6 supercharger???

h4xx0rr said:
What is v6 supercharger???
Click to expand...
Click to collapse
Its a script to improve performance. Anyways u seem to be unaware of that so it means you've not done anything like installing a MOD, Try updating the recovery.

Can you give me link for supercharger?

Atishay Jain said:
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Click to expand...
Click to collapse
No, I did not intall any mod, last rom i had on it was a modaco but when I gave thephone to my son I just pushed the last stock root rom i picked from xda 4.2 I think. Still I goona try what u sayed, I did not try to push a custom rom only google images. TY, I will tell what happens. And yes it's an European Samsung Galaxy Nexus as we are in Galaxy nexus section

h4xx0rr said:
Can you give me link for supercharger?
Click to expand...
Click to collapse
Here you go :
http://forum.xda-developers.com/showthread.php?t=2733251
There are also a few other tricks and MODs listed there if u want to improve your phone's performance.
Rate the thread well if it helped you.:good:

Looks allot like my girlfriends phone and this thread http://forum.xda-developers.com/galaxy-nexus/help/normal-boot-loop-problem-t2875961
factory reset does not do/wipe anything, pushed files don't stay on the device after reboot, flashing new rom from PC does not stick
Nexus seems to be in some kind of readonly mode.

TWRP bootloops

I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk

Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu

You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !

Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk

I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks

badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.

followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks

badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.

followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!

That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.

badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..

``

tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices