Develop Bugs

GNex stuck in boot loop since 4.3 flash

Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?

Flash the official Google image: http://forum.xda-developers.com/showthread.php?t=2376687

check dreams rom thread and see my post there
Sent from my Galaxy Nexus using Tapatalk 4 Beta

Fix it by flashing factory images! do a full wipe, you can get imprtant stuff from your Nexus by using adb pull commands!
Users was blaming me when they screwed their Nexus with the root files!
I can successfully even flash old root files and no bootloops but ofc. root wont work if using those old root files.

OP, did you factory reset between ROM flashes?

beekay201 said:
OP, did you factory reset between ROM flashes?
Click to expand...
Click to collapse
pulling files then flashing 4.2.2 stock image to start fresh

NyPlaya513 said:
Ok, I am paranoid and want to be sure about this. I am in the same boat as the OP. I have a 32gb toro on twrp 2.5. I am under the impression that flashing the stock images will flash my sdcard partition and I want to pull some files if that is the case. Is there anyway to pull the files or am I stuck and need to start fresh.
Click to expand...
Click to collapse
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.

NeoMagus said:
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
Click to expand...
Click to collapse
nvm pulling files

If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it

NeoMagus said:
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
Click to expand...
Click to collapse
nvm got the toolkit to pull files via adb for me on my parallels

agent47er said:
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Click to expand...
Click to collapse
"just wipe data" in recovery after flashing, solve bootloop issue

dexviajiboy said:
"just wipe data" in recovery after flashing, solve bootloop issue
Click to expand...
Click to collapse
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.

agent47er said:
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
Click to expand...
Click to collapse
i dont think there's any kernel for now, give it some time and you'll get one

Cyanogen OS system upgrade

Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks

Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.

Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.

is a ZIP file available for flashing via TWRP?

Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver

mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI

Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464

mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated

Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!

seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).

Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.

seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.

mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?

seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.

Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?

seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success

Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.

seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.

Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.

Best way to currently install marshmallow after failed attempts

Hi, after trying to use philz recovery to flash a ROM on to my device I got what I think was called a soft brick where I had to download and flash the stock ROM.
My device (GT-N7100) is now not rooted again and back to square one. Any problems I come across occur from using old tutorials with dead links so if someone could recommend a tutorial to install a custom rom like 5.1 I would be very grateful. Thanks
EDIT. I found this guide on youtube http://mytechtube.in/samsung-galaxy-note2-rooting.html + http://mytechtube.in/samsung-galaxy-note2-6-0-1.html . Does it look like it will work?

Flash twrp using Odin, then flash a custom rom via twrp.

Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk

Root is not required to flash TWRP. TWRP can be flashed directly to the phone using Odin.

1life2love4 said:
Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
audit13 said:
Flash twrp using Odin, then flash a custom rom via twrp.
Click to expand...
Click to collapse
Should I just use the latest version of TWRP direct from their website https://twrp.me/devices/samsunggalaxynote2n7100.html ?
I think my phone code name is t03g how can i confirm?
Thanks
EDIT. Just installed TWRP :good: now on to picking a good ROM. will have a look at the ressurection one too.
To install apps that require root should O root it now or do some ROMS root it for me?
Sorry for the amount of questions

The easiest way to install twrp would be to flash the tar version using Odin.

audit13 said:
The easiest way to install twrp would be to flash the tar version using Odin.
Click to expand...
Click to collapse
Just did as you suggested thanks. To install apps that require root should I root it now or do some ROMS root it for me?

Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.

audit13 said:
Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.
Click to expand...
Click to collapse
Thanks for the info. I've watched some videos of cm13 and I so far thats what im going with. Will look for a youtube video to help with installing it.

To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.

audit13 said:
To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.
Click to expand...
Click to collapse
I didnt realise that before. Could I for example install any of the GAPPS from this link https://devs-lab.com/android-gapps-download.html " full google apps" or pico google apps ?
From whatI gather GAPPS are installed straight after rom install before root though is this the same in cm13?

Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/

audit13 said:
Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/
Click to expand...
Click to collapse
Perfect Im going to try that in the next hour. I like the look of aroma. For platform would I select ARM and android 6.0?
EDIT. Found the answer it was ARM.

Arm as I believe your phone has a Qualcomm processor.

audit13 said:
Arm as I believe your phone has a Qualcomm processor.
Click to expand...
Click to collapse
Yeah was ARM as I just installed CM13. Thank you seriously headig your way.

Hopefully, everything works.
Now that you have twrp on your phone, you can use it to create a backup of everything in your phone, including time efs folder. Save the efs folder in a safe place in case you need to restore it to the phone at a later date.
After making a backup, you can flash other Roms and you can return to cm13 by restoring your backup.

Just getting familiar with it. Thanks for the help.
Do you know if there's settings to turn screen on during during calls because it works with the front sensor and that sensor is broke on my phone?
Sent from my GT-N7100 using Tapatalk

You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.

Got it sorted using an app from the play store.
Sent from my GT-N7100 using Tapatalk

audit13 said:
You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.
Click to expand...
Click to collapse
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the rom and reinstalling the custom rom like I did the first time.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop.
Any suggestions on how i could get it running again? Thanks!

Trouble Flashing Custom ROM

So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.

Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later

Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)

slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew

Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.

peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew

Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew

Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!

First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs

Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]

TWRP Not installing ANY roms on my LG G3.

Sup guys,
TWRP Is having its mood swings and will not let me install any Roms at all the roms i've tried are.
1. Pacman Rom
2. Zephyr rom
3. Liquid Dark Rom
These 3 are compatible with my phone but when I go to install the rom it will install then suddenly it will give the message.
'E: ERROR EXECUTING UPDATER BINARY IN ZIP '/EXTERNAL_SD/ZEPHYR-OS-V5.0-SENTINEL-20160901-D855-UBERTC.ZIP'
I've wiped the system, data, Dalivik cache rebooted the recovery.
Plus I found out that It says I have the wrong baseband. Its weird though every rom that i've used it never asked me to change the baseband.
Thats all i've done please help me out guys.
I forgot to say the rom that I was currently on was Fulmics rom and since i installed that no other roms will install.

HunterTubeHD said:
Sup guys,
TWRP Is having its mood swings and will not let me install any Roms at all the roms i've tried are.
1. Pacman Rom
2. Zephyr rom
3. Liquid Dark Rom
These 3 are compatible with my phone but when I go to install the rom it will install then suddenly it will give the message.
'E: ERROR EXECUTING UPDATER BINARY IN ZIP '/EXTERNAL_SD/ZEPHYR-OS-V5.0-SENTINEL-20160901-D855-UBERTC.ZIP'
I've wiped the system, data, Dalivik cache rebooted the recovery.
Plus I found out that It says I have the wrong baseband. Its weird though every rom that i've used it never asked me to change the baseband.
Thats all i've done please help me out guys.
I forgot to say the rom that I was currently on was Fulmics rom and since i installed that no other roms will install.
Click to expand...
Click to collapse
You need v21c modem. Modem
Install it and then install AOSP based ROMs.
Greetings.

Sotiris02 said:
You need v21c modem. Modem
Install it and then install AOSP based ROMs.
Greetings.
Click to expand...
Click to collapse
I wanna give you a hug so bad. Thank you for fixing this problem for me!

Sotiris02 said:
You need v21c modem.
Install it and then install AOSP based ROMs.
Greetings.
Click to expand...
Click to collapse
HunterTubeHD said:
I wanna give you a hug so bad. Thank you for fixing this problem for me!
Click to expand...
Click to collapse
I'm having trouble going from Fulmics to crDroid/CM14 on my G3 D855. I keep getting ERROR 7.
I've tried removing the assert lines of code from the binary file in the ROMS zips, but that doesn't work (says the whole file is missing when installing). Do we think that what worked for you, may work for me? Does that sound likely?
EDIT: Went ahead and did it - it worked! Thanks guys! Been looking for a solution for the past 24 hours!