Develop Bugs

[Q] CM11 snapshot/nightly stuck at boot... now can not even rollback to 10.2

Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )

nabeelmoeen said:
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
Click to expand...
Click to collapse
Your HBOOT is to low you must to upgrade ti 1.39 or 1.72 but 1.31 is tooo low and for this the CM11 don't boot

Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version

nabeelmoeen said:
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
Click to expand...
Click to collapse
try restore stock and chek for update restore nandroid and see I am not sure J15 is only 1.31

Will give it a shot tonight and report back. ...what's grinding my gears is none of the other roms including jb ones I tried are working either

i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!

nabeelmoeen said:
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
Click to expand...
Click to collapse
is HBOOT still the same version or did you upgrade it?

I am curious about the order in which you did things. After formatting boot, system and cache partitions, did you flash the boot image again or did you do that prior to the formatting.
Thanks

help ...Random reboots on every lollipop rom as soon as the screen turns off

everything was ok till 22 december build...it started from 27 december build
earlier every lollipop rom worked fine on my n7100.
i dirty flashed 27 december build on 22 december build..it started rebooting randomly.
i wiped everything and flashed again it also showed same error and the rom was rebooting as soon as the screen turns off
after that i have tried every lollipop rom out there even every build of cyanogenmod 12 but it is showing same problem and rom in unusable. I was also using agni kernel on that rom and titanium backup. The phone reboots as soon as the screen turns off and the cyanogenmod logo appears. I have also tried wiping internal storage 3 times but no success.
I seriously want to use 5.0.2. Came from dn4 which worked awesome. using TWRP 2.8.4.0 Earlier i also used multirom twrp when everything was working fine.
Thanks in Advance

ritikbanga said:
everything was ok till 22 december build...it started from 27 december build
earlier every lollipop rom worked fine on my n7100.
i dirty flashed 27 december build on 22 december build..it started rebooting randomly.
i wiped everything and flashed again it also showed same error and the rom was rebooting as soon as the screen turns off
after that i have tried every lollipop rom out there even every build of cyanogenmod 12 but it is showing same problem and rom in unusable. I was also using agni kernel on that rom and titanium backup. The phone reboots as soon as the screen turns off and the cyanogenmod logo appears. I have also tried wiping internal storage 3 times but no success.
I seriously want to use 5.0.2. Came from dn4 which worked awesome. using TWRP 2.8.4.0 Earlier i also used multirom twrp when everything was working fine.
Thanks in Advance
Click to expand...
Click to collapse
This is not true for me.I have tried almost all the Lollipop ROMs since their first release.Now I am with the Resurrection Remix 5.3.2 dated 27.01.2015.I have not experienced any random reboots till this date.Most of the time while flashing new ROMs I was doing full wipe and Factory Reset.Once I installed Agni Kernel.After that when I shifted to another ROM I lost my IEMI. Flashing stock ROM couldn't restore it.Hence I went to Samsung Service Centre.They said that the Mother Board has to be replaced which which will cost Rs.7000.00 (apprxly 75..00 USD).So I went to a private technician and he restored the IMIE at a cost of merely Rs.250.00(apprxly 4.50 USD).Thereafter also I shifted to many Lollipop ROMs without any issues.But I never installed Agni since then.I am sticking with the kernels came with those ROMs.

pnsdhrn said:
This is not true for me.I have tried almost all the Lollipop ROMs since their first release.Now I am with the Resurrection Remix 5.3.2 dated 27.01.2015.I have not experienced any random reboots till this date.Most of the time while flashing new ROMs I was doing full wipe and Factory Reset.Once I installed Agni Kernel.After that when I shifted to another ROM I lost my IEMI. Flashing stock ROM couldn't restore it.Hence I went to Samsung Service Centre.They said that the Mother Board has to be replaced which which will cost Rs.7000.00 (apprxly 75..00 USD).So I went to a private technician and he restored the IMIE at a cost of merely Rs.250.00(apprxly 4.50 USD).Thereafter also I shifted to many Lollipop ROMs without any issues.But I never installed Agni since then.I am sticking with the kernels came with those ROMs.
Click to expand...
Click to collapse
but i am getting these issues

Installed CM 12.1 everything went fine, went to flash gapps, getting UID error

Coming from stock rooted / unlocked Touchwiz KitKat
Cm12.1 installed just fine but when I rebooted and went to flash gapps I get a non-stop error saying "there's an internal problem with your device, and it may be unstable until you factory data reset."
So I factory reset the device and even installed CM 12.1 without gapps and it still gives me this error.
Factory reset again, try my recovery and I get an error mentoning UID's being messed up (I did this and it did not help http://forum.xda-developers.com/and...on-finally-t3151579/post61729442#post61729442 ) . So I factory reset again and flashed CM 12.1 without gapps and everything is fine.
Boot into recovery and flash gapps and boom the error again. Seems like the only way to get rid of the error (After many trials and errors) is to Restore recovery -> factory reset -> flash rom. The only problem is when I also flash gapps the error comes back.
Now here is the part where I can use YOUR help, in TWRP I keep saying red text that says
"E:error opening '/data/data/com/google.android.gms/files/images/games/de7f5650'
E:error: Not a directory"
on everything I do, from formating the system to flashing a rom. I think this is where my problem lies.
Other notes: No sd card,
when CM is working, I am getting no reception (Looks like a full but has ! next to it)
When CM is working, the messaging app does not even open and just instantly closes

OK I'll break into parts I see 1: gapps 2 signal 3:msg app.
1: GAPPS
cm 12.1 is android 5.1.* so you need to verify you have correct gapps. Use gapps for 5.1 hopefully that will fix problem. Factory reset, flash cm 12.1, flash gapps 5.1, wipe dev/cache, and reboot. Should be working fine after.
2: Signal is due to rom bugs but usually due to bad/wrong apn settings or bad efs/modem pretty much all the time from my experience. So I'll break that down from easiest to the latter and hopefully we'll fix it.
a: check you apn settings and see the attachments. I'm on lte tmo so if you aren't the Google apn setting for your carrier.
b: flash back up of moden/efs
3: msg app might be fixed since gapps was installed but if not only thing I can think of is clear data/cache for msg app.
Hope I could help

these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me

BsB5068 said:
N900TUVUCNB4
Click to expand...
Click to collapse
Rolatnor said:
these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me
Click to expand...
Click to collapse
lineageos 16.0 is what I've been running on it, i needed a newer os cuz stock 5.0 was the last official version, and pokemon go was dropping support for the note 3 with stock roms, now switching to LineageOS 17.1 on my note 3 i'll update whether gapps works so you know
LineageOS Downloads
download.lineageos.org
LineageOS 17.1 is android 10

btw I have sd cards in all my spare phones 8gb normally, so I am recommending a small sd card 4gb-16gb because it makes it easier to flash roms with twrp

google play works, gmail works, yt works, sound works, flashlight works, and camera works on LineageOS 17.1
note 3 sm-n900t
i used the nano gapps from opengapps
the newest file version of lineageos 17.1 on their site

Mobile data does not work anymore on my C2005

I had no problem with mobile data on official ROM but from the day I installed CM 13, I can not using mobile data anymore.
First of all, I installed CM 13 beta, then CM 13 stable and some nightly builds. Nothing changed!
I installed AOPS Nougat 7.0 Beta2 few weeks ago on my C2005.
I had "CM13-UNOFFICIAL-20160104-NIGHTLY" and data did not work, I updated it to "stable-20160527-NIGHTLY" (via cmupdater) and nothing changed. After few months, I installed AOPS Nougat 7.0 Beta2 but I can not use the data yet. I installed Nougat Beta2 via TWRP boot manager and wiped everything (all the data, cache, etc.) .
There is few weeks I've installed CM 14.1 on my C2005 and updated it to some nightly builds but the problem still exists after several months and several Android versions.
I installed CM 13 "stable-20160527-NIGHTLY" on my wife's C2005 and the data works a charm! Even I tried to flash mine to that version but problem still exists to my phone even with that version.
The only different between my phone and my wife's C2005 is that I didn't install TWRP on her phone and just installed CM13 with it's own recovery.
I tried instructions described in this link and the problem has not not solved yet.
The last thing is when I enable mobile data (SIM 1 or SIM 2) the cross mark but it does not change to H+ or other marks that shows I'm using data (attached screenshot).
Is hardware problem possible for this issue?
How can I provide CM logs for this problem to find out what's wrong with my phone?
Does someone else have such a problem?

Any idea about debugging and providing some logs?
Any idea about debugging and providing some logs?

Read the bug section of Cynogenmod
http://forum.xda-developers.com/showpost.php?p=69518095&postcount=12
Device-related bugs
– Dual: no internet on 2nd SIM
Click to expand...
Click to collapse
Also, try flashing your device with official rom 4.3 again and try using internet on it. If it works you are doing something wrong in flashing other os, if not, it's device related.

Thanks for reply. Actually I can not use data on SIM1. It's OK for me and it shouldn't be necessarily on specific SIM.
I'm looking for another way of checking data rather than reflashing to official ROM and install CM again. Something like reading /var/log/something.log in Linux distros. Is anything like that possible on AOSP or CM?

No. You can try however reflashing and clean installing aosp 7 or cm14 again, alongwith with THIS patch for dual sim users. But before you install anything make sure you are on 4.3 firmware, or you are likely going to face the same problem again.

Data works on 2nd SIM.
Thank you all for your help.
Believe it or not, the data on 2nd SIM is usable, but 1st SIM.
It could be Edge or HSPA.
As the known bugs says, data is now work on 2nd SIM, I always tried to enable data on the 1st SIM, but few nights ago I had enough free time to check all the options and finally it worked!

undetected sim, Unknown baseband, Rogers, d2can, cm14.1

I recently installed cm14.1 on a Rogers d2can phone and I got unknown baseband and sim card stopped working. I tried flashing different modems which made the situation worse as now even old cm11 roms show unknown baseband.
Can someone please tell me where I can download modem zip file that works for Rogers and for cm14.1?

I recommend flashing the latest KK stock ROM from sammobile.com which will restore your phone back to stock and ensure the bootloader and modem/baseband are matched. After flashing stock and confirming that the imei is correct, then flash twrp, cm14.1, and gapps.

I was downloading from sammobile.com very slow and the download was interrupted in the middle. I will try again later.
Is there a better site to download firmware from?

So I downloaded it and flashed using odin. Flashing took a while but it passed. The phone got stuck on bootloop though.
So I booted to stock recovery and performed a factory reset. Booted again. Now it works!
I'm going to stay on Touchwiz 4.4.2 for a while.

Glad you got it working.

I would not call "staying on Touchwiz 4.4.2", "working" more like opening yourself to a long list of known exploits.
Others are having the same issue (cyanogenmod is dead so I removed the link, hope LineageOS fixes the issue some day.)
Using the last good CM-13 build is probably the best for now.

sim not provision ed MM#2...... easiest fix ....please n thanks;;;;

We'll need more information in order to help solve the sim problem like model #, ROM, etc.