Related
This is a full flashable build of 4.0.4 AOSP I compiled myself.
There are absolutely no tweaks of any kind, this is full stock.
Download
You can download it here: https://faramir.eriador.org/r/full-maguro-ota-en.4.0.4.zip
Installation
It can be installed with CWM.
Wipe
You should not need to wipe (except maybe cache). That said if you have weird issues, like accounts not syncing, try wiping.
I installed it over CM9 without wiping, but your mileage may vary.
If you come from pre 4.0.3 ROMs, please wipe.
Google Apps
gapps are not installed, so you will have to flash them too. You can use my mirror at https://faramir.eriador.org/r/gapps-ics-20120317-signed.zip
Please prefer the version of google apps you were already using, otherwise you will more than probably need a wipe.
Root
Note that this is stock, hence there is no superuser, you will have to install superuser and su by hand like on a stock rom.
Here is a mirror for it: https://faramir.eriador.org/r/su_ICS_GN.zip
Kernels
It should be compatible with all 4.0.3 custom kernels although I only tested FuguMod (http://forum.xda-developers.com/showthread.php?t=1438417)
RECOVERY WARNING
This is full stock, which means if you keep the original kernel, it will reflash stock recovery at first boot.
nikademus said:
Hello,
I just compiled 4.0.4 AOSP
You can download it here: https://faramir.eriador.org/r/full-maguro-ota-en.4.0.4.zip
It can be installed with CWM.
You should not need to wipe (except cache).
gapps are not installed, so you will have to flash them too.
Note that this is stock, hence there is no superuser.
It should be compatible with all 4.0.3 custom kernels although I only tested FuguMod.
Click to expand...
Click to collapse
So is it completely stock i.e stock kernel etc? basicly just an ota but not an ota if you get me?
p.s first haha
leelaa said:
So is it completely stock i.e stock kernel etc? basicly just an ota but not an ota if you get me?
Click to expand...
Click to collapse
Yes, it's fully stock, the google way
Real OTA image from google is not available yet, so this is what looks like it the most.
It's mainly for those who want to have real 4.0.4 now without waiting and without losing CWM or making a wipe.
Thanks thats what i want, good job
nikademus said:
Yes, it's fully stock, the google way
Real OTA image from google is not available yet, so this is what looks like it the most.
It's mainly for those who want to have real 4.0.4 now without waiting and without losing CWM or making a wipe.
Click to expand...
Click to collapse
how about losing CWM after making a full wipe
how can i go back to restoring a nandroid backup mate?
thx for help
i only have 3e recovery with the belly-up android...
I just flashed this and lost CWM and have no Gapps.. my Signal bars stay grey and don't turn cyan (blue) even though I know.I'm in an area I get perfect service.
Sorry can't see any changes. Same sh#@% defrent day.
klone96 said:
I just flashed this and lost CWM and have no Gapps.. my Signal bars stay grey and don't turn cyan (blue) even though I know.I'm in an area I get perfect service.
Click to expand...
Click to collapse
As I posted in the OP, you need to flash gapps. It's forbidden to distribute them (at least included in a ROM).
klone96 said:
I just flashed this and lost CWM and have no Gapps.. my Signal bars stay grey and don't turn cyan (blue) even though I know.I'm in an area I get perfect service.
Click to expand...
Click to collapse
How did you flash the ROM?
I also flashed it together with Gapps, su and FuguMod R200.
I didn't loose recovery and also I can connect without any issues on Wifi and mobile data.
zurchpet said:
How did you flash the ROM?
I also flashed it together with Gapps, su and FuguMod R200.
I didn't loose recovery and also I can connect without any issues on Wifi and mobile data.
Click to expand...
Click to collapse
he probably wiped full like me and also forgot to download SU (from the other thread), gapps and optional kernel
zurchpet said:
How did you flash the ROM?
I also flashed it together with Gapps, su and FuguMod R200.
I didn't loose recovery and also I can connect without any issues on Wifi and mobile data.
Click to expand...
Click to collapse
I flashed in cwm and flashed the gapps but I guess it didn't take bcuz I don't see them I'm no where near a laptop so I'm guessing I'm screwed untill I root/flash recovery??
I have put links to gapps and su in the OP
Soo.. is it best to just wait for another stock rom with a kernel that has a recovery... or just flash this?
This rom will not overwrite existing recovery partition.
Sent from my Full AOSP on Maguro using Tapatalk
YoungAceAtlanta said:
Soo.. is it best to just wait for another stock rom with a kernel that has a recovery... or just flash this?
Click to expand...
Click to collapse
You can flash FuguMod before booting, it will not wipe your recovery.
The problem is within the init.rc:
Code:
service flash_recovery /system/etc/install-recovery.sh
class main
oneshot
This is stock behavior.
Hey guys can I flash this over the AOKP Mod I have installed? If so, how?
I do not find meaningful replace the stock ... what's the point? Then, after a day or puts the CM9 o another aopk ..... mistake?
sago62 said:
I do not find meaningful replace the stock ... what's the point? Then, after a day or puts the CM9 o another aopk ..... mistake?
Click to expand...
Click to collapse
I will probably stay on that ROM and not flash any AOKP or so. It has all I need.
Joshaldo said:
Hey guys can I flash this over the AOKP Mod I have installed? If so, how?
Click to expand...
Click to collapse
I have flashed it over CM9 nightly without any wipe needed.
sago62 said:
I do not find meaningful replace the stock ... what's the point? Then, after a day or puts the CM9 o another aopk ..... mistake?
Click to expand...
Click to collapse
please talk english to us! thanks!
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
joshnichols189 said:
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
Click to expand...
Click to collapse
I've tried all the latest kernels. Every kernel I've tried is compatible with the ROM I've tried it on.
isikh said:
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
Click to expand...
Click to collapse
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
TheAxman said:
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
Click to expand...
Click to collapse
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
isikh said:
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
Click to expand...
Click to collapse
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
TheAxman said:
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
Click to expand...
Click to collapse
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Use this kernel it works perfectly on CM10
http://forum.xda-developers.com/showthread.php?t=1845836
EDIT: nvm use this one http://forum.xda-developers.com/showpost.php?p=31025930&postcount=1152
isikh said:
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Click to expand...
Click to collapse
Now I am a tad confused, you have UVALH2 on the phone already, and you want to flash UVALH2? or did you typo? I am no dev, but from what I have been seeing, the radio should not matter at the moment, if I am wrong, someone please set me straight, also, I will be on the web all night and tomorrow, so I will help where ever I can, I will check here for your progress. Good luck my friend.
BTW, I do not like stock roms, so to me CM10 is for sure better. Faster also.
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
joshnichols189 said:
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
Click to expand...
Click to collapse
Yeah, I know all this, but I wanted to ask in case I may have missed something. Even when you're pretty Android savvy when it comes to rooting and whatnot, you do miss things on occasion. In this instant I didn't, but I was hoping I did because a bunch of custom kernels won't work on my phone with CM10! Trinity worked well, so I'm waiting for those. It must be some specific chip related issue because I'm not the only one. Anyways, thanks everyone!
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Shane24 said:
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Click to expand...
Click to collapse
Hey man,
My suggestion is to use Odin to flash the stock image back to stock and see if the problem persists. If it does, I'd take it back to at&t for a new phone (if you've had it less than a year or you have some sort of insurance plan.)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:23 AM ---------- Previous post was at 02:18 AM ----------
If flashing back to stock fixes it, its user error. Make sure you're up to date on everything, I.e boot loader, recovery, everything. If that does nothing for you maybe try flashing the new version of CWM and see if it'll flash right that way.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it just me or is your lean kernel like years old? Isn't the newest version 7.2?
Same with your rom.. 2.9 is out?
Sent from my SGH-I747 using xda premium
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Shane24 said:
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Click to expand...
Click to collapse
Hey man,
If you're going to be flashing custom ROMs you should probably learn what a kernel is. Use the search feature or simply use google. In fact, the xda TV channel just put out a video on kernels this week on YouTube.
Anyways, as I said previously, make sure EVERYTHING is up to date. Including the ROM version. Dont worry about flashing kernels until you have a solid understanding of what they are. I'm almost positive that you are just flashing out of order. Just start from scratch, make sure EVERYTHING is up to date. Good luck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
What the guy above me said about TW roms is correct. Flashing the wrong kernel is not a good idea. Here's what I do on every flash
- wipe system, data, caches, etc.
- flash rom( and gapps if necessary)
- boot up rom and let it settle for 5 min, then boot back into recovery
-flash correct kernel for the rom's version(check kernel number in about device and custom kernels op), then wipe both caches and fix permissions.
-reboot and enjoy:laugh:
DMF1977 said:
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Click to expand...
Click to collapse
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Shane24 said:
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Click to expand...
Click to collapse
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
DMF1977 said:
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
Click to expand...
Click to collapse
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Shane24 said:
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Click to expand...
Click to collapse
What?
What DMF1977 was saying is just flash the ROM you desire to have on your device and just run the kernel that comes with the ROM. After running the ROM you chose for awhile, if you feel the need to flash a new kernel then and only then flash the correct version of Ktoonsez kernel. And its not surprising that if you tried to flash anything AOKP related with TW you got an error.
Just flash an AOKP ROM and Dont worry about flashing an additional kernel.
Goodluck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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.
Hi Everyone
I have just grabbed the Paranoid .zip for Nexus 9 (Flounder) flashed it via twrp but it stuck in bootloop for about 10 mins. I have restarted the device but still no luck. Any suggestions?.
Thanks
vampire_8_7 said:
Hi Everyone
I have just grabbed the Paranoid .zip for Nexus 9 (Flounder) flashed it via twrp but it stuck in bootloop for about 10 mins. I have restarted the device but still no luck. Any suggestions?.
Thanks
Click to expand...
Click to collapse
You figure it out? I had the same issue.
Marky__Mark said:
You figure it out? I had the same issue.
Click to expand...
Click to collapse
I think I did can't really remember mate, I think it was the kernal I had a custom one and caused the bootloop. Flashed the stock boot image and it did work afterwards. Honesty I ditched it after 2 days running dirty unicorns now, in my opinion it's the best custom rom out there for now, I even flashed it to my N6 running perfectly fine check it out and make sure u don't have xposed install you can have some issues, just check it out and read the thread you'll be fine ????????
vampire_8_7 said:
I think I did can't really remember mate, I think it was the kernal I had a custom one and caused the bootloop. Flashed the stock boot image and it did work afterwards. Honesty I ditched it after 2 days running dirty unicorns now, in my opinion it's the best custom rom out there for now, I even flashed it to my N6 running perfectly fine check it out and make sure u don't have xposed install you can have some issues, just check it out and read the thread you'll be fine ????????
Click to expand...
Click to collapse
Im running PA with xposed and elementalx and its smooth as silk. My issue, I think, is my device was unencrypted and its been so long that I havent used a custom kernel that i forgot about it. I flashed the new AOSPA without elementalx to test out the stock kernel and i think it tried to encrypt. When it took too long for the first boot, i manually rebooted the device and that borked the data so i had to do a factory reset and lose all my data. Pain in the ass, but im diggin this rom.