Just got my n5 and decided to unlock and root it, everything went well until I wanted to flash a rom, no matter what rom I flashed I got all kinds of issues from all apps force closing to bootloops, soft keys not working ect. I've tried flashing stock img, factory reseting ect, nothing seems to work. I'm not sure what's going on here, any help?
I am probably already asking you questions you have already done but... Have you reformated the system, data, and cache partitions prior to flashing? Also are you checking the MD5 of the ROMs you are trying?
Yeah tried all of that, md5's are correct, thanks though
what recovery and version are you on?
what wipes exactly are you performing?
you've checked the md5?
Ok. just trying to narrow things down. When you flash the stock image from https://developers.google.com/android/nexus/images#hammerheadkrt16m are you running the flash-all script? And after that before even adding any apps or changing anything does it give you issues?
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Xolith said:
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Click to expand...
Click to collapse
are you flashing a gapps add-on package with your custom roms? the right gapps?
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
simms22 said:
are you flashing a gapps add-on package with your custom roms? the right gapps?
Click to expand...
Click to collapse
Yeah, tried a few including banks, PA 0-day, psx gapps
neomorphix said:
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
Click to expand...
Click to collapse
They appear right after I flash the rom, tried with both the included and with a custom one
Tried a few days later and it worked, weird haha. Thanks though
Related
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
tomalrocks said:
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
Click to expand...
Click to collapse
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
tomalrocks said:
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
Click to expand...
Click to collapse
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
aypeeootrek said:
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Click to expand...
Click to collapse
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
tomalrocks said:
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
Click to expand...
Click to collapse
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
thnx123
yhnk you for
Zalithian said:
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
Click to expand...
Click to collapse
hehehe I already got that scare after flashing new rom and it was taking a long time to boot during first boot.
Thanks anyways
Ive tried to install a few different ROM but they all get aborted. when i googled it they said update your ROM manager. im using clockwork and says my ROM cant do OTA and im using the latest version of clockwork
Ive checked the MD5 got a green light and codes match. but still aborts the flash. tried 6-7 different roms and nothing. Ive wiped the device twice and cleared the cache, nothing. Any ideas? something I'm missing..
First did you wipe system ,cache, and d cache? Second did you mount system? Third what are you coming from and going to? For example when going from cm to a stock based rom you'd have to flash the stock boot.img.
sent from my xt926 RAZR maxx hd
koftheworld said:
First did you wipe system ,cache, and d cache? Second did you mount system? Third what are you coming from and going to? For example when going from cm to a stock based rom you'd have to flash the stock boot.img.
sent from my xt926 RAZR maxx hd
Click to expand...
Click to collapse
Yes using safestrap 1.33 im able to get it installed now. but when i reboot its still the stock ROM. and when i try to install it in ROM slot 1 nothing boots
Im going from stock to CM 10.1 and i tried with system mounted and unmounted. and yes ive wiped all of them numerous times.
\EDIT
Well the one i had matching md5 was a carbon ROM so ive been working with that one mainly. all the CM ones ive seen didnt seem to work with Verizon phones. if you have DL link i would appreciated it. i would prefer CM
So, I've tried fixing the phone from random cutouts by flashing another Rom, Now, when the rom has been flashed and starts, I get a mass of force close errors on boot, (I've tried this with multiple roms, them being a CM10 and CM11 based roms). I've tried full wipe, and cleared the Dalvik cache. Anybody?
twisted64d said:
So, I've tried fixing the phone from random cutouts by flashing another Rom, Now, when the rom has been flashed and starts, I get a mass of force close errors on boot, (I've tried this with multiple roms, them being a CM10 and CM11 based roms). I've tried full wipe, and cleared the Dalvik cache. Anybody?
Click to expand...
Click to collapse
What apps are FC'd? If they're google's, then consider the gapps package you flash.
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
ashkan-khatar said:
What apps are FC'd? If they're google's, then consider the gapps package you flash.
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
Click to expand...
Click to collapse
The question should be what doesn't FC. I've seen DSP manager close, process.android.acore close and a few other apps such as themer and then the phone just crashes.
Have you tried to format all partitions using 4ext recovery?
I had this problem, that I couldn't turn on WIFI. I didn't want to use the internet so flashed lollipop 5.0.1(from 4.4.4). When flashed to 5.0.1 it was rebooting every time the screen locked, so decided to go back to 4.4.4. At first everything was ok, but then the mobile network just stopped to work. I was ok to cope with the disabled wifi, but i really need the phone internet. What should I do? Already tried flashing stock and factory wiping a couple of times, didn't help
The 'tower' of signal strength looks orange, but there's an H on it
sebreens said:
I had this problem, that I couldn't turn on WIFI. I didn't want to use the internet so flashed lollipop 5.0.1(from 4.4.4). When flashed to 5.0.1 it was rebooting every time the screen locked, so decided to go back to 4.4.4. At first everything was ok, but then the mobile network just stopped to work. I was ok to cope with the disabled wifi, but i really need the phone internet. What should I do? Already tried flashing stock and factory wiping a couple of times, didn't help
The 'tower' of signal strength looks orange, but there's an H on it
Click to expand...
Click to collapse
Using the right gapps version?
beekay201 said:
Using the right gapps version?
Click to expand...
Click to collapse
I'm sorry, but where can i check that?
if i download the zip from teamandroid.com, how can i install them?
sebreens said:
I'm sorry, but where can i check that?
if i download the zip from teamandroid.com, how can i install them?
Click to expand...
Click to collapse
make sure you're getting the correct gapps version: L and KK need different gapps.
KK: http://forum.xda-developers.com/showthread.php?t=2397942
L: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
beekay201 said:
make sure you're getting the correct gapps version: L and KK need different gapps.
KK: http://forum.xda-developers.com/showthread.php?t=2397942
L: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Click to expand...
Click to collapse
When i first tried to install it showed
* Incompatible GApss Currently Installed *
PA GApps can ONLY be installed on top of an existing installation of PA GApps. You must wipe (format) your system partition BEFORE installing any PA GApps package.
**** GApps Installation failed ***********
when i look lower i see
E: Error in ... (the specified image address)
(status 1)
Installation aborted.
when i try to install gapps the second time it shows
E: Can't make /tmp/update_binary
Installation aborted
what should i do?
(I didn't have CWM Recovery before, now I have it installed and rooted the phone)
OFC, you already flashed gapps.
Wipe /system, reflash ROM, flash correct gapps.
beekay201 said:
OFC, you already flashed gapps.
Wipe /system, reflash ROM, flash correct gapps.
Click to expand...
Click to collapse
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
sebreens said:
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
Click to expand...
Click to collapse
Well first of all. Flash TWRP. Trust me. Then solving your problems will be much easier than in CWM
sebreens said:
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
Click to expand...
Click to collapse
NOTE: Ofc, the factory image has gapps included. Google owns gapps, in case you don't know.
Due to lack of info, I was mislead to think that you was running custom roms, and not a factory image.
The orange colored network indicators simply mean that you're not connected to Google Play services. This would NOT prevent you from accessing the internet on a browser for example - doesn't matter if on wifi or on mobile data - visiting www.google.com.
If you want to get a clean/fresh start, flash a factory image. I assume you know how to, so if you don't go read the guides on General. It's very simple.
That said, after flashing a factory image, and booting it, EVERYTHING should just work: adding your google account, connection to google play services, everything.
If you want to run custom roms, then you'll need a custom recovery (as suggested, TWRP), a custom rom, and an appropriate gapps version. Simple.
beekay201 said:
NOTE: Ofc, the factory image has gapps included. Google owns gapps, in case you don't know.
Due to lack of info, I was mislead to think that you was running custom roms, and not a factory image.
The orange colored network indicators simply mean that you're not connected to Google Play services. This would NOT prevent you from accessing the internet on a browser for example - doesn't matter if on wifi or on mobile data - visiting www.google.com.
If you want to get a clean/fresh start, flash a factory image. I assume you know how to, so if you don't go read the guides on General. It's very simple.
That said, after flashing a factory image, and booting it, EVERYTHING should just work: adding your google account, connection to google play services, everything.
If you want to run custom roms, then you'll need a custom recovery (as suggested, TWRP), a custom rom, and an appropriate gapps version. Simple.
Click to expand...
Click to collapse
Ok, so I should just contact warranty if I got this after flashing stock? I cannot turn on wifi (the problem persisted before flashing) and now I have no internet connection. (I checked all the providers, and I have the right ones set there)
What should I do before I bring it to the warranty service?
Everytime I try and use Google Maps either flashed with gapps/bean or installed later from play store all reboot my phone. Stock does not have any issue.
Tried:
ASOP-CAF
ASOP-EX
MOTOPURE
Lineage
TESLA
I just wonder why if the stock maps app works on 6.0 why not on 7.0?? The only thing I can think of is the GPS.
Any tips or suggestions?
Thanks!
Tried nano, pico and full for ARM and Android 7
open_gapps-arm-7.1-full-20170523
open_gapps-arm-7.1-nano-20170511
open_gapps-arm-7.1-pico-20170513
also BeansGapps-Full-7.1.x-20170509 BeansGapps-Mini-7.1.x-20170509
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
grantdb said:
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
Click to expand...
Click to collapse
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
acejavelin said:
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
Click to expand...
Click to collapse
Thanks for helping me, do you mean bootloader.img?
Ok done reflash stock, OTA's and checked gps is fine now backing up... going to use the PureNexus rom or ASOP-CAF
ARRRRRGGGGG Same damn issue... Maps crashes the phone.... so frustrating I am going to give up soon and stick with stock.
Going to try an get a logfile maybe someone can take a look at it
Thanks
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
grantdb said:
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
Click to expand...
Click to collapse
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
grantdb said:
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
Click to expand...
Click to collapse
You can use ADB to get real-time logging of the crash on your PC... Use Google to find the command.
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
Sent you logcat via pm thanks again!
Well I started getting random reboots in Pure Nexus ROM and so tried LOS and right away I had the reboot from Maps. I give up, staying with stock.
Thanks
Seems like one of my problems could be ASOP-CAF ROM as the version I was flashing uses a custom Kernel that has known issues with 7.1.2 and causes bootloops and crashes. The UltraDev kernel changes some things in the modem and could be why any roms I tried after flashing ASOP-CAF would not change the modem and were 7.1.2 based.
Anyways...
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
grantdb said:
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
Click to expand...
Click to collapse
Check out this bug report. It might be your APNs... https://jira.lineageos.org/browse/BUGBASH-248
By messing with my APN settings as per above bug report I can use maps and have no more random reboots. Woop woop