I don't have a VZW N4 but do have the USC variant. I've been compiling CM12 for it the past few weeks since slayher released his source.. If you have the developer edition phone I have a build that needs tested. I don't plan to make a post in the developer section. This would be better served by a person with the phone. If someone wants to run with it I have the device chain. Before worrying about that we need to know if it even works.
The normal warnings apply, this can break your phone blah, blah, blah. I assume if you have a developer phone you aren't new to this and understand the risks.
https://www.androidfilehost.com/?fid=95864024717071574
MD5: 5f4d89d70256d86e7ddb76e03cfa4ad1
I will try it. What baseband do i need to be on? i might wait until i get another nexus 6 tonight and set it up so i have it as a backup ready to roll lol
I will try it as well.
Couldnt get it to boot. Stuck at samsung logo. Did full wipe and it said something about kernal not being enforcing, but didnt boot.
How long did you wait. First boot may take 5 minutes. The message you are referring to is because it is a custom kernel.
Sent from my SM-N910R4 using Tapatalk 2
@csstamatin
We're you on NJ5 or previous build?
On mj5, and i waited maybe 2-3 mins, but no boot ani. All the cm builds ive tried before take a long time at boot ani, amd not samy logo. Will try again.
Ok yeah it should at least go to CM boot animation. I'll take a further look when I get home. Thanks for trying. Which recovery arts you using TWRP? The developer model is SM-N910V isn't it. I want be sure I have the assert right.
Sent from my SM-N910R4 using Tapatalk 2
We all have twrp. So yeah he is probably using twrp. And yes model is correct.
Yeah tried again, no luck. Also any specific gapps? Using pa 5.0.1 micro. Will try your next build.
I have been using PA myself. I'll compile another build, will take a few hours.
Sent from my SM-N910R4 using Tapatalk 2
Hey, thanks for your work!
New Build
http://upload.teamuscellular.com/3nd
MD5: 1fe04383b0f7fdc018a80a01a6eb345c
Mod57 said:
New Build
http://upload.teamuscellular.com/3nd
MD5: 1fe04383b0f7fdc018a80a01a6eb345c
Click to expand...
Click to collapse
New build is stuck on the Samsung Logo also.
If you don't mind could you flash again, this time before you boot flash this kernel then boot.
http://d-h.st/pllL
This will let me know if it's kernel related or something else.
Mod57 said:
If you don't mind could you flash again, this time before you boot flash this kernel then boot.
http://d-h.st/pllL
This will let me know if it's kernel related or something else.
Click to expand...
Click to collapse
I've made it to the CM logo, we'll see what happens. I'll report back.
Edit: It gets past the CM logo but once it gets to "android is upgrading" it loops back to the CM logo.
airmaxx23 said:
I've made it to the CM logo, we'll see what happens. I'll report back.
Edit: It gets past the CM logo but once it gets to "android is upgrading" it loops back to the CM logo.
Click to expand...
Click to collapse
oooooohh so close!! getting excited!!
airmaxx23 said:
I've made it to the CM logo, we'll see what happens. I'll report back.
Edit: It gets past the CM logo but once it gets to "android is upgrading" it loops back to the CM logo.
Click to expand...
Click to collapse
Dont know if it needed to be said but incase it shows more interest in this rom rather than only one person trying the rom, this is also what i've experienced when attempting to install the rom.
I'm ready to test it out at anytime.
Blackiisky said:
Dont know if it needed to be said but incase it shows more interest in this rom rather than only one person trying the rom, this is also what i've experienced when attempting to install the rom.
Click to expand...
Click to collapse
I also tried it with and without a Gapps package.
Related
Hey guys, I am having trouble flashing a new rom onto my phone. I used to flash my Galaxy S3 almost every day, and for some reason, I am having trouble with the S4. I have rooted it, and installed Team Win Recovery Project v2.5.0.2 and sometimes the Rom will flash and work, like PA worked first time, so did MIUI Rom, but trying Most of the others they either say failed, or... they go through the whole installation process through the Recovery for Android Revolution HD, and then it boot loops, take battery out, put back in and wipe everything and it just stays on the first Samsung Logo and that's it.
Is there something I am missing?
I am wiping eveyrthing as well before I do it.
Any help will be really appretiated
Thanks
skrapi said:
Hey guys, I am having trouble flashing a new rom onto my phone. I used to flash my Galaxy S3 almost every day, and for some reason, I am having trouble with the S4. I have rooted it, and installed Team Win Recovery Project v2.5.0.2 and sometimes the Rom will flash and work, like PA worked first time, so did MIUI Rom, but trying Most of the others they either say failed, or... they go through the whole installation process through the Recovery for Android Revolution HD, and then it boot loops, take battery out, put back in and wipe everything and it just stays on the first Samsung Logo and that's it.
Is there something I am missing?
I am wiping eveyrthing as well before I do it.
Any help will be really appretiated
Thanks
Click to expand...
Click to collapse
Can you please elaborate this situation without any hassle.? Didn't get your properly. Come again.?:cyclops:
Disturbed™ said:
Can you please elaborate this situation without any hassle.? Didn't get your properly. Come again.?:cyclops:
Click to expand...
Click to collapse
My bad lol, in work and was typing fast.
Basically, when I flashed ParanoidAndroid on my phone, and it worked great, then I changed it to MIUI which worked great,
then I decided to Flash Omega Rom, which was fine, but the WIFI doesn't work for me.
So I tried to Flash Android Revolution and it goes through the Installation Process with no problems and goes into Boot Loop, even though I have done a full wipe of the device.
I am in the middle of Flashing Android Revolution now, for the 3rd time, and it has been on 10% installation for 10 minutes. This is all it says at the moment...
===========================
Android Revolution HD by mike1986
===========================
>>>Formatting partitions
(system is unmounted already)
(preload is unmounted already)
-- that's it --
Sorted, thanks anyway.
Just incase someone else is in the same situation,
All I did was take the battery out for 30 minutes or around that time, and just flash the rom, I didn't wipe or anything else, just flashed and done.
For people having Wifi issues, flash a different Kernel like Adam Kernel, that seems to work for me.
skrapi said:
Sorted, thanks anyway.
Just incase someone else is in the same situation,
All I did was take the battery out for 30 minutes or around that time, and just flash the rom, I didn't wipe or anything else, just flashed and done.
For people having Wifi issues, flash a different Kernel like Adam Kernel, that seems to work for me.
Click to expand...
Click to collapse
Good to see that. BTW Can u prefix solved in ur subject?
Sent from my Disturbed™ Galaxy S4
Disturbed™ said:
Good to see that. BTW Can u prefix solved in ur subject?
Sent from my Disturbed™ Galaxy S4
Click to expand...
Click to collapse
Yea sure no problem. How do you do it though? I have had a look but have no idea lol.
skrapi said:
Yea sure no problem. How do you do it though? I have had a look but have no idea lol.
Click to expand...
Click to collapse
Just edit ur first post and select advance edit. Then u can change it.
Or just double click over subject line for this thread in subforum.
Sent from my Disturbed™ Galaxy S4
Disturbed™ said:
Just edit ur first post and select advance edit. Then u can change it.
Or just double click over subject line for this thread in subforum.
Sent from my Disturbed™ Galaxy S4
Click to expand...
Click to collapse
Sweet, cheers mate = )
Is anyone else having the problem where if you turn off your phone and turn it back on it'll sometimes freeze at the Samsung logo. If you do a battery pull and turn the phone back on again, it'll boot like normal.
Firmware: MDL
ROM: Cyanogenmod 10.1 RC2
Recovery: TWRP
What twrp version?
xBeerdroiDx said:
What twrp version?
Click to expand...
Click to collapse
TWRP 2.5.0.2
I used your HOW-TO guide to complete everything
Loki+TWRP+Motochopper CASUAL
Wiping Device
Flashing ROM
How long has it been doing this/at what point did it start?
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
emckai said:
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
Click to expand...
Click to collapse
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
jd1639 said:
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
Click to expand...
Click to collapse
RC2 is a 4.2.2 build.
Last night I decided to just try and let it hang and see if it'll get past it but 2 minutes later it never did. So I just held the power button (10 seconds) to shut it down and restart.
Sorry, didn't read your whole post and missed the rc2.
jd1639 said:
Sorry, didn't read your whole post and missed the rc2.
Click to expand...
Click to collapse
No problem. Just wondering what is causing this issue, seems like some people in the Cyanogenmod thread is also having this issue.
It's happening on the cm10.2 roms too and seems to be related to the recovery used. See if twrp 2.6.3.0 works for you.
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
I switched custom recovery. TWRP to CWM and everything is booting just fine. (knock on wood) I'll turn off and on my phone a couple more times and see if it's actually the custom recovery.
cwm has had far fewer problems on the S4 than twrp. i've always rolled with cwm touch across my devices just out of preference. glad i havent had to deal with any of these twrp issues. glad you're sorted. cheers
Just rebooted my phone a couple of times (about 10 times) and it didn't hang at samsung logo anymore.
Thanks everyone!
emckai said:
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
Click to expand...
Click to collapse
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
CZ Eddie said:
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
Click to expand...
Click to collapse
x2 to all of the above. Known issue for S4s on 4.3 and 4.4 and although a couple of ROMs have claimed that they're "solving" it as of yesterday's nightlies it ain't fixed....
Just hold down power till the Samsung screen disappears then immediately let go. It'll try again. Repeat, repeat, repeat as necessary and eventually it will work.
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
CZ Eddie said:
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
Click to expand...
Click to collapse
I've been using the same kernel since yesterday afternoon and haven't hung once either. I've tried it with CWM and TWRP because my hangs used to occur when I rebooted system from recovery and both have worked just fine.
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
Same.
Same.
:crying:
Same.
Edit. I tried flashing the ROM by itself then booting the device. Then reboot into recovery and flash the gapps. It worked for me and I have seen others say it is hit or miss. It is worth a try though.
ernieb4768 said:
Same.
Edit. I tried flashing the ROM by itself then booting the device. Then reboot into recovery and flash the gapps. It worked for me and I have seen others say it is hit or miss. It is worth a try though.
Click to expand...
Click to collapse
This doesn't work for me... anyone got a solution? That's annoying..
Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
Did you try a clean install?
-wipe data/factory reset
-flash ROM
-flash gapps
-restart
no "restore"
If you say you had an "Older" version, does this mean you were on PAC23 (with android version 4.2.2)?
If you are on a pre-android 4.3 version of PAC, you need to do a full wipe. If you are already on a 4.3 version of PAC and you have "blame tyler" issues, try factory reset, if the problem persists, try a different nightly
Just a little curious...is the Blame Tyler error a specific error or set of errors, or does Tyler get blamed for everything?
Also, can we get Tyler's xda username, so he can get the blame he deserves :laugh:
Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
try redownloading the rom zip! and check its md5 code before flashing!!
also do a clean flash! all wipes!
if it doesnt work then even try fix permissions option !
Sent from my C6603 using Tapatalk 4
'Blame Tyler' error is just a generic message displayed when some component crashes/throws an unhandled exception, etc. It's not related to a bad ROM d/l or MD5 code. Telling people to do a full wipe b/c of an undiagnosed error condition doesn't help much. There are far too many little brokens with this ROM that need to be addressed and given more developer support, if this ROM is get more adoption.
Since RC1, nightlies have been dropping for 2 months now - no log of what's fixed or added, unless you are a dev who can wade thru the build change logs and understand what that means. It's ridiculous that we've gone this long since RC1 with a new stable release and documented fixes. Maybe this info is buried somewhere, but it's not in the Spring GS4 forum and the Pac-Man website forum is dead.
These errors are not specific to any one nightly and have been going on for months.
the tyler message is just a replacement of the force close messages. It is meant as a joke as he is one of our devs and we all take turns being blamed for breaking stuff.
If your coming from the old stable and flashing the newest nightile...comming from 4.2.2. to 4.3.1 then a full wipe is required due to the different databases and newer code that isnt compatable with the old version. This should fix your issues.
Also please dont post tylers username as its not nice to go and troll him...
I flashed the rom successfully after a full wipe this weekend. Amazeballs. I blame Tyler for making all my friends jealous of my phone.
I want to keep up with nightlies. The only thing not working for me is the wifi tether. If I have the US snapdragon quad-core variant do I want the pac-jfltetmo.zip?
Sent from my SGH-M919 using xda app-developers app
experienced the same problem and would be greatful for help
vedhed21 said:
I flashed the rom successfully after a full wipe this weekend. Amazeballs. I blame Tyler for making all my friends jealous of my phone.
I want to keep up with nightlies. The only thing not working for me is the wifi tether. If I have the US snapdragon quad-core variant do I want the pac-jfltetmo.zip?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yes, if you have the T-Mobile variant of the S4.
keyboard not working.....
Papa Smurf151 said:
the tyler message is just a replacement of the force close messages. It is meant as a joke as he is one of our devs and we all take turns being blamed for breaking stuff.
If your coming from the old stable and flashing the newest nightile...comming from 4.2.2. to 4.3.1 then a full wipe is required due to the different databases and newer code that isnt compatable with the old version. This should fix your issues.
Also please dont post tylers username as its not nice to go and troll him...
Click to expand...
Click to collapse
i have flashed your pac man rom to my galaxy sl everything went right but its keyborad was not working then i manually flashed another JB keyboard in recovery mode... then it worked ... and i flashed blackgapps(JB 4.2.2) from ENHDROIX developers and it is working quite well...
the only problem i had was keyboard stuff..
so devs should fix that issue...
GUYS THIS IS VERY STRANGE.. The nav bar at the bottom overlaps half of the dock of next launcher which makes the dock completely unusable and ugly.. the same problem persist in 50% of the other apps notably go sms, quick pic, go launchers and many others.. I have tried the milestone releases and a few latest nightlies but its still not fixed..
Its hard to believe there are many discussions of issues about pac rom going on but I didn't find this preety obvious and significant one anywhere..
I have waited like 3 months since I started with pac, updated about 5 nightlies along the way hoping it will be fixed but no luck everytime..
This one is serious.. It has forced me not to use some of my fav apps and use pie navigation at times..
No problem with all the minor bugs but this one is frustrating..
ANY IDEA GUYS??
PS. pac ver 4.3.1 on sg tab p3100 and sg3
Sent from my GT-P3100 using XDA Premium 4 mobile app
Do you know how to enable navigation bar? I saw all the settings in PAC settings>navigation bar but found no option to enable it.
Sent from my GT-P3100 using XDA Premium 4 mobile app
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers ?
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
AICP isn't available for Taimen just yet.
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
Thanks for the info, can't wait.........:good:
ROM is up guys!
Great to see here! Kudos
Anybody been able to get past the boot logo? I've tried 4 times. Always hangs on the boot logo indefinitely. Not frozen, the boot animation is cycling, it just never fully boots.
Namolas said:
Anybody been able to get past the boot logo? I've tried 4 times. Always hangs on the boot logo indefinitely. Not frozen, the boot animation is cycling, it just never fully boots.
Click to expand...
Click to collapse
Nope , same here! Can't get it to boot past boot animation and I started with a clean factory image. Dang
tmoore3496 said:
Nope , same here! Can't get it to boot past boot animation and I started with a clean factory image. Dang
Click to expand...
Click to collapse
Same, I started from a flash-all factory image in both slots. Most interesting part ( to me ) is after the 4th try I flashed only the AICP zip, and not TWRP zip this time. Still wouldn't boot and when I booted back to recovery, expecting the stock recovery, but instead now I have Lineage recovery...
Seems I still have a thing or 2 to learn about this device.
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers ?
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
id say its at its peak when we also have pixie dust or w.e and pure nexus roms
Anyone installed this one?....any exclusive features?
amandeepparmar said:
Anyone installed this one?....any exclusive features?
Click to expand...
Click to collapse
To my knowledge nobody has successfully booted it. Won't boot past the boot animation, been trying all night. We are waiting for further instruction from the maintainer.
elliwigy said:
id say its at its peak when we also have pixie dust or w.e and pure nexus roms
Click to expand...
Click to collapse
+1 for Pure Nexus
I got it to boot. I tried mostly what you guys tried. What I did to get it to boot was dirty flash over my previous rom. I had rr before. Make sure you do a backup. I also took off finger prints out any security locks. Also remove any substratum themes otherwise system ui will crash. If you try it, at your own risk.
I forgot to add. I switched slots before flashing.
Sent from my Pixel 2 XL using Tapatalk
Namolas said:
To my knowledge nobody has successfully booted it. Won't boot past the boot animation, been trying all night. We are waiting for further instruction from the maintainer.
Click to expand...
Click to collapse
*fart*
Nochis said:
I got it to boot. I tried mostly what you guys tried. What I did to get it to boot was dirty flash over my previous rom. I had rr before. Make sure you do a backup. I also took off finger prints out any security locks. Also remove any substratum themes otherwise system ui will crash. If you try it, at your own risk.
I forgot to add. I switched slots before flashing.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So what do you think? You stick with it? Worth trying?
Namolas said:
So what do you think? You stick with it? Worth trying?
Click to expand...
Click to collapse
Don't know yet if I stay on it. I don't know if worth a try. Most roms have same stuff. I normally try for battery life and volte and wifi calling.
Sent from my Pixel 2 XL using Tapatalk
Can confirm that dirty flash over RR ROM does indeed allow it to boot!
Dirty flash worked like a charm..
Do you need to delete data to dirty boot? Were you still rooted with magisk installed? Thinking by about trying to over stock but wanna be prepared for the worst so have some fresh backing be up to do first. Lol
I dirty flashed, without wiping data on previous rom. I was going to try on stock but didn't want to turn on computer.
Sent from my Pixel 2 XL using Tapatalk
I had stock rom sm-t510 not sure if the exact build but I decided to try the AOSP 10.0 rom along with the same devs leniage rom, both times I’ve tried flashing in ODIN and TWRP, also flashed another custom “stock” rom, tried a different kernel as well and nothing, all times I get stuck on the boot logo (doesn’t boot loop, just sticks at logo). Also unlocked boot loader prior to flashing anything. I have lots of experience flashing with different phones back in the day and I’ve followed all the instructions like doing a factory wipe to remove encryption after flashing.
I guess my question is what would cause it to get stuck at the boot screen.
having a different base build before flashing the custom ROM
Sent from my SM-G970F using Tapatalk
robertozombie said:
having a different base build before flashing the custom ROM
Sent from my SM-G970F using Tapatalk
Click to expand...
Click to collapse
Makes sense , I’m not even sure of the build I was on prior to flashing, shame on me! So anyone know how I fix this?
Will try
So if this is the case then I should be able to install stock firmware that the rom is built on (found here https://samfrew.com/model/SM-T510/) and once that is installed then installing rom should work, in theory right? Am I missing anything?
yes, check first post:
https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
you'll need build number: (T510XXU3BTFN)
Sent from my SM-G970F using Tapatalk
K1mbo said:
Am I missing anything?
Click to expand...
Click to collapse
There's a real possibility that you may be dealing with the RMM lock, something I've become all too familiar with on my last three Samsung devices...
You can learn about it and how to get around it here:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com