Related
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
Are you on a Canadian carrier?
Sent from my SGH-I747 using xda app-developers app
Nope, southern california ATT.
I edited using vim and did it cleanly, no chance of a carriage return or something stupid contributing to this.
Are you on the proper bootloader?
mrhaley30705 said:
Are you on the proper bootloader?
Click to expand...
Click to collapse
I have tried running the zip manually from recovery mode in CWM, tried installing it from Rom Manager where it reboots and automatically selects it and I have tried directly from the CM10 update button within the About Phone settings menu.
Is that what you are referring to?
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
mrhaley30705 said:
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
Click to expand...
Click to collapse
I do not follow, what is the jelly bean bootloader? I understood it to be an alternative to CWM? Why have I been able to flash every update for CM10 until this?
Link to this jelly bean bootloader update?
Bootloaders are not a type of recovery. Perhaps you should read through this:
http://forum.xda-developers.com/showthread.php?t=1903437
Then this:
http://forum.xda-developers.com/showthread.php?t=2292957
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
I have the same problem. Guess I'll never get 10.1, because it looks like you have to put a new bootloader on it, not sure why, and it risks a hard brick. It doesn't make any sense to require a new bootloader, seeing as I already have cyanogenmod 10, but the devs chose that for their reasons. I really want the camera in 4.2.
Well, if you've flashed any of the stock ROMS here, rooted or not rooted, you've flashed bootloaders.
well I guess I am confused. I am currently running cm-10.1-20130411-EXPERIMENTAL-d2att-M3.zip with the same bootloader I flashed with Odin back when I got the phone in september 2012. My roomate got the same phone except on sprint and we flashed his with the appropriate CM10.1 experimental release for the sprint phone. Since then we both have been updating via the built in CM updater and he has been able to go to the new stable CM 10.1.0 release today and has not flashed any new boot loader or anything, just updated CWM like I did.
So my question to you mrhaley30705, which no amount of searching or reading links has helped me thus far, is this something specific to the ATT version of the Galaxy S3? I do not understand what changed and why he can do it and I cannot.
More importantly, will flashing the newer boot loader you suggested require a wipe of everything? The only post actually referencing this for my phone is http://forum.xda-developers.com/showpost.php?p=41503727 and it is vague to say the least.
Your answers are much appreciated.
Here is the screen shot of what was posted on g+ by cm. I would say he is on the new bootloader. If you check the second link I posted above, there's a way to tell which bootloader you and your buddy have.
It doesn't wipe anything. You'll probably never notice the difference, with the exception of being able to run aosp based ROMS
thank you, that is informative, but still leaves me confused since I am running 4.2.2 (although the build is before that May release) and I am currently running I747UCLH9.
Checking my roomate's phone he is running XXXXXXLJ7 so either he started with a newer one or something. I guess that clears it up. Also, this thread was very helpful incase anybody searches and stumbles on my posts: http://forum.cyanogenmod.com/topic/73407-how-to-update-bootloader-and-do-i-need-to-do-this/
Hi, I was running the latest AOKP and I decided to install franco kernel. After doing that, on the reboot I had this error repeteadly and I can't get into the system. How do I enter TWRP? Usually I used to longpress power and select reboot -> recovery, but now I can't use that option.
If I turn on the phone by using volume down + power, I get into the recovery stock, but I can't select anything.
How do I resolve? I managed to get into the recovery once, I wiped data, but the error comes out again. Now I'm stucked on the initial wizard with this popup message :crying::crying:
Just keep pressing ok to it and get to settings/apps/all and clear data in contacts and contact storage. Then let it all re sync from Google
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Just keep pressing ok to it and get to settings/apps/all and clear data in contacts and contact storage. Then let it all re sync from Google
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I reinstalled the rom and it seems to work, but then I tried reinstalling franco kernel and the popup is here again. Why? Is the kernel the problem?
Tommolo said:
I reinstalled the rom and it seems to work, but then I tried reinstalling franco kernel and the popup is here again. Why? Is the kernel the problem?
Click to expand...
Click to collapse
I assume the latest AOKP is based off Android 4.3, and you're trying to install Franco r392? Have you tried the modified Franco r392 by @osm0sis?
Sent from Samsung Captivate Glide @ CM10.2
I am experiencing the same behavior on the 2013-11-14 AOKP build. I have tried r392-fixed by osm0sis and was surprised to see the same issue. I've used that kernel on an earlier build of AOKP without issue. I would really like to reinstall Franco kernel. Is there anything else that I can try?
Thank you
lanruid said:
I am experiencing the same behavior on the 2013-11-14 AOKP build. I have tried r392-fixed by osm0sis and was surprised to see the same issue. I've used that kernel on an earlier build of AOKP without issue. I would really like to reinstall Franco kernel. Is there anything else that I can try?
Thank you
Click to expand...
Click to collapse
Did you try my above post? I used to test the official PAC rom for the Xperia S so it happens a lot with test builds. It always sorted the issue
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Did you try my above post? I used to test the official PAC rom for the Xperia S so it happens a lot with test builds. It always sorted the issue
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried the r392-fixed by osm0sis. I used the same .zip file that I have successfully installed on previous AOKP builds. While there is no way to clear Contacts and Contact data once in this "com.android.phone has stopped" loop, I have tried clearing the Contacts & Data, then immediately rebooting into recovery and flashing r392-fixed. Upon reboot I am presented with the same message. Thinking that this may have been something caused by restoring data from Titanium, I did a factory reset and clean install of AOKP 2013-11-14 along with franco r392-fixed and I still see the issue. I have cleared both cache and dalvik on every flash. Could there be some other cache stored on the sdcard somewhere causing issues?
At this point I was planning to wait for the next AOKP release and hope the issue goes away unless someone has other suggestions.
Thank you.
i had the same problem with franco kernel.
go into bootloader mode , and use the wugfresh root toolkit to boot your phone into custom recovery , and flash another kernel.
handofdark said:
i had the same problem with franco kernel.
go into bootloader mode , and use the wugfresh root toolkit to boot your phone into custom recovery , and flash another kernel.
Click to expand...
Click to collapse
I was able to get into recovery and simply restore the ROM, which replaces the kernel. I was posting to see if anyone could help me actually get the franco kernel installed on the 2013-11-14 AOKP build. I would like to have posted this in the kernel dev thread, but my post count isn't high enough.
i think the problem is with the r392 franco kernel , cause i had the problem with the latest cm 10.2 nightly version
For future readers who may find themselves in this situation, I found the following procedure to allow you to get out of the error loop and boot into recovery without pulling the battery provided your power off menu has an option to reboot into recovery [AOKP provides this option].
When the phone first boots you will be stuck in an infinite "Process com.android.phone has stopped" popup loop. Dismissing the dialog simply brings it right back.
1. Turn the display off by pressing the power button.
2. Turn the display back on using the power button.
3. Dismiss the dialog. It did not come back at this point for me, leaving me at a normal looking slide to unlock screen.
4. Long press the power button to bring up the Power Off / Reboot menu.
5. Reboot into recovery.
At this point you can re-flash your ROM which should restore the stock kernel provided with your ROM.
---------- Post added at 01:26 PM ---------- Previous post was at 01:16 PM ----------
handofdark said:
i think the problem is with the r392 franco kernel , cause i had the problem with the latest cm 10.2 nightly version
Click to expand...
Click to collapse
Please try the r392 FIXED version provided by osm0sis. I believe there is a link provided earlier in the thread. While this did not work for me with the 11-14 AOKP build, I have had it work with earlier builds and many have had luck with it using CM based ROMs.
My problem is that even the fixed version left me with the com.android.phone error and I'm not sure why.
im good with leankernel at the moment thanks
I'm having the exact same problem. I'm using AOKP 2013-11-14. I also tried the previous version of the Franco kernel, r391, but it did the same thing.
Is there another kernel that you guys can recommend that's as well supported and has similar features?
Also, I wanted to say that I've seen posts from lots of people using AOKP+Franco, saying that it works perfectly. Why is it suddenly not working for us? Could it be our particular AOKP nightly version?
TheNexian said:
I'm having the exact same problem. I'm using AOKP 2013-11-14. I also tried the previous version of the Franco kernel, r391, but it did the same thing.
Is there another kernel that you guys can recommend that's as well supported and has similar features?
Also, I wanted to say that I've seen posts from lots of people using AOKP+Franco, saying that it works perfectly. Why is it suddenly not working for us? Could it be our particular AOKP nightly version?
Click to expand...
Click to collapse
Did you try the fixed version by osm0sis? If not, you can find a link earlier in this thread and in the Franco kernel thread. If it works for you, please let me know because it didn't for me with this build.
lanruid said:
Did you try the fixed version by osm0sis? If not, you can find a link earlier in this thread and in the Franco kernel thread. If it works for you, please let me know because it didn't for me with this build.
Click to expand...
Click to collapse
I'm sorry, I can't find the link in either of the locations. I did a search for the word "osm0sis" in the franco kernel thread and it doesn't show up.
I'm very much a newbie at rooting and roms at the moment, so please excuse the question, but is there any reason that two identical phones running the same rom, kernel, and recovery should behave differently? My phone's the I9250, and I'm using clockworkmod recovery.
Thanks
try franco r394
I was having the same problem while using CM 10.2 and several Kernels.
I have now flashed franco.Kernel r394. All modification done by osm0sis are included and it's working fine on my Nexus.
Sczep said:
I was having the same problem while using CM 10.2 and several Kernels.
I have now flashed franco.Kernel r394. All modification done by osm0sis are included and it's working fine on my Nexus.
Click to expand...
Click to collapse
Same here. r394 is working fine with AOKP nightly 2013-11-14 on my GNex as well.
I got this error when I try to place or pick a call in PAC or Carbon or crDroid rom. But no such error in slim rom. Can anyone tell me why. I really want to try pac rom.
sent from a phone running on SLIM ROM
I recently rooted my AT&T Samsung Galaxy S3 running Android 4.3 using odin. I loved the features, I flashed the ROM CyanogenMod and had that working just fine. Until just recently I made the mistake of installing a new ROM. I used ROM manager and decided to go with stratatak7 . Now after doing this, my phone has been downgraded from 4.3 to 4.1.1 and is not running properly and crashes. So I went back into ROM manager and tried to get CyanogenMod back, but am unable too, every time I try to install I get an error. I am looking for ANY way to fix this. I mainly want to get my phone back to COMPLETE factory settings and Android 4.3. Im currently running Build Number Intergalactic 2.5.
PLEASE HELP!!!
EraOfDiscovery said:
I recently rooted my AT&T Samsung Galaxy S3 running Android 4.3 using odin. I loved the features, I flashed the ROM CyanogenMod and had that working just fine. Until just recently I made the mistake of installing a new ROM. I used ROM manager and decided to go with stratatak7 . Now after doing this, my phone has been downgraded from 4.3 to 4.1.1 and is not running properly and crashes. So I went back into ROM manager and tried to get CyanogenMod back, but am unable too, every time I try to install I get an error. I am looking for ANY way to fix this. I mainly want to get my phone back to COMPLETE factory settings and Android 4.3. Im currently running Build Number Intergalactic 2.5.
PLEASE HELP!!!
Click to expand...
Click to collapse
Step #1 - Dont use ROM manger to install roms.
Step #2 - Flash back to stock and start over. If you need help with this there are stickies all over the general and q&a sub forums.
dntesinfrno said:
Step #1 - Dont use ROM manger to install roms.
Step #2 - Flash back to stock and start over. If you need help with this there are stickies all over the general and q&a sub forums.
Click to expand...
Click to collapse
Thanks for the reply, but now a new problem has happened, now when I boot up it gets stuck at the Samsung Galaxy SIII boot logo... any suggestions?
EraOfDiscovery said:
Thanks for the reply, but now a new problem has happened, now when I boot up it gets stuck at the Samsung Galaxy SIII boot logo... any suggestions?
Click to expand...
Click to collapse
All by itself? Or did you manage to flash back to stock? If so the fix is to boot into recovery and factory reset. Also note it will take a little longer to boot after a stock flash (or wiping the cache) as the cache needs to be rebuilt.
I have a T989, not a T989D, running TWRP 2.7.1.0 and UVMC6 radio, coming from a JB 4.1.2 Slimrom.
Also I have taken out the board and inspected the power button, and everything seems okay there. I don't think it's being caused by a faulty button or some other hardware problem because I can flash my old Slimrom, and that boots up just fine.
I wanted to give Paranoid Android a whirl with the latest Wild kernel, and though I've tried 8 different PA builds, a PACman, a Slimkat, and an Alpine rom, ALL KitKat roms so far are bootlooping. [EDIT: Even PA 3.99 JB 4.3 is doing it. So it's more than just KitKat even.]
I'm doing the following:
Wipe system, data, cache, dalvik, and perhaps android secure and preload as well
Flash ROM & Gapps
Wipe cache & dalvik
Reboot
I reach the splash, and maybe it even finishes booting. But invariably, it takes about 60-90s from initialization before the screen dims, everything freezes for 2-5s, and it reboots.
I'm out of ideas.
Why won't my phone work with KitKat?
Thanks in advance
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
meekrawb said:
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
Click to expand...
Click to collapse
I read something to that effect. Haven't seen a .tar file for it, only .zip.
jaybird16 said:
I read something to that effect. Haven't seen a .tar file for it, only .zip.
Click to expand...
Click to collapse
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
meekrawb said:
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
Click to expand...
Click to collapse
Okay, I did that. Flashed the latest Paranoid Android 4.45. No dice. Same story.
jaybird16 said:
Okay, I did that. Flashed the latest Paranoid Android 4.5. No dice. Same story.
Click to expand...
Click to collapse
That was the only thing I could think of. Maybe someone else has some ideas.
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
meekrawb said:
That was the only thing I could think of. Maybe someone else has some ideas.
Click to expand...
Click to collapse
Much appreciated. My phone shipped at the tail end of Gingerbread. So now I have whatever drivers from 4.1.2, and that's one more potential problem eliminated.
The stock rom ran just fine, btw, once I factory reset (the documentation was nil, but at 750mb, I knew it was more than just UVMC6 radio firmware...)
So 4.1.x seems to be okay, but not 4.3.x or 4.4.x. Next I'll have to try a flavor of 4.2.x and see how it feels about that.
Lokke9191 said:
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
Click to expand...
Click to collapse
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.5. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
Never. Ever. Rule out leprechauns!
Lokke9191 said:
Never. Ever. Rule out leprechauns!
Click to expand...
Click to collapse
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
jaybird16 said:
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
Click to expand...
Click to collapse
Nice. Lemme know how it works out. Oh. The new PA is awesome.
My bad. I saw the number "8" at the bottom of the page which had not been there earlier and assumed it was next after after "7". No, that's an ancient recovery from 2012.
TWRP 2.8.1 for the Hercules has NOT just dropped!
Okay, so, my first test with a newly downloaded, MD5 checked, and flashed TWRP 2.7.1 recovery, and an MD5 checked PA 4.45 has not produced any different result.
However, you've made me realize that I can't hope to troubleshoot this without being fastidious about MD5 from here on out, so, thx 4 that.
...same goes for a 2nd test with an MD5 checked PA 4.5 Alpha3...
...same goes for a 3rd test with an MD5 checked PA v3.69 (4.2)...
...But Slim-Star v4.12 (4.2) loads no problem...go figure...
Fix permissions?
I tried to install the PA 4.5 Beta, and same problem. It bootloops.
Could it have anything to do with permissions?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
when i had an issue like this i re-installed the factory original rom and started from the very beginning. if you've tried that and it doesn't work, well i'm pretty much unhelpful here. :crying:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
ayr0 said:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
Click to expand...
Click to collapse
There were problems reported of even the latest version of Wild! not working with Paranoid.
jrc2
Sent from my T-Mobile S2 using Tapatalk.
I'm having the same issues, but no one knows what's up. I've tried so many ROM's and only the older ones work.
http://forum.xda-developers.com/showpost.php?p=55050951&postcount=9
This is my post with the logs I got from the constant crash on cm11. I tried pa and had the same result.
Issue solved
After sharing some logs with Sultanxda, he pointed out this bootloop issue due to the CM kernel and helped me get it fixed.
My problem was that my phone would not boot on MOST JellyBean ROM's or ANY KitKat ROM. It would crash/kernel panic on or before the set up screen.
I do not know if the latest KitKat ROM's have the issue patched, but I asked if he could upload the patch for the kernel to source for other ROM's to use.
This thread should be solved I guess.
I am trying to flash the CM12.1 official nightly, and when I flash it on to my device (SM-T320), all it does is get stuck at the [Samsung Tab Pro 8.4] screen, after a while it just shuts itself off.
I have also tried other ROMs, which work fine. Anyone know what the issue is with CM12.1?
Try a version older of the CM12.1 official nightly, if this still doesnt not work, DM me right away and i'll help you asap!
komugi said:
I am trying to flash the CM12.1 official nightly, and when I flash it on to my device (SM-T320), all it does is get stuck at the [Samsung Tab Pro 8.4] screen, after a while it just shuts itself off.
I have also tried other ROMs, which work fine. Anyone know what the issue is with CM12.1?
Click to expand...
Click to collapse
No problem for me, what recovery and I hate to say it but are you wiping cache, data and system?
komugi said:
I am trying to flash the CM12.1 official nightly, and when I flash it on to my device (SM-T320), all it does is get stuck at the [Samsung Tab Pro 8.4] screen, after a while it just shuts itself off.
I have also tried other ROMs, which work fine. Anyone know what the issue is with CM12.1?
Click to expand...
Click to collapse
Try clean install it. Make sure you install the right gapps
Make sure to wipe
Any updates?
I am having the same problem, same device.... Did you get it to work?
I have tried nightly builds between 20150720 - 20150728 to no avail. I am using TWRP 2.8.7.0 and GApps 20150222. I am wiping Data, Cache, and Dalvik. Only the 27th and 24th builds actually get passed 'Patching system image unconditionally...'
Any help would be greatly appreciated!
---------------------------------------------------------------------------------------------------------------------------------
I managed to find a working combo, I used CM12.1 20150728 with GApps-L-4-21-15 and booted just fine!