So. I've finally done it - gone way beyond my comprehension. I'm not exactly new to flashing roms/kernels, but I'm certainly still at the noob level.
Here's what I did: I have Pac Man rom (22.2.0-rc1). I've tried different kernels but have a very poor signal at home and it's very hard to connect to wifi at home even though other devices connect flawlessly. Even the latest Franco (both stable and nightly) have a lot of problems with the wifi. So, I just made a nandroid in TWRP, flashed cwm-radio-m9615a-cefwmazm-2.0.1700.54.zip, then flashed Faux123+Shaky156V0.4.zip, then wiped cache/delvik then rebooted system. (I did all of this by copying the files into the ready-to-flash/root files and simply flashed them via TWRP.
Here's the problem: I'm stuck on PACs boot screen. The little pac man game-type animation runs, then it goes to the PAC is loading screen and stays there. And I can't get back to TWRP. If I hold the power/volume up& down keys, it simply reboots right to the rom and goes back to the bootloop.
I've tried searching XDA for a solution but can't find one. Any advice? Thanks!
david251 said:
So. I've finally done it - gone way beyond my comprehension. I'm not exactly new to flashing roms/kernels, but I'm certainly still at the noob level.
Here's what I did: I have Pac Man rom (22.2.0-rc1). I've tried different kernels but have a very poor signal at home and it's very hard to connect to wifi at home even though other devices connect flawlessly. Even the latest Franco (both stable and nightly) have a lot of problems with the wifi. So, I just made a nandroid in TWRP, flashed cwm-radio-m9615a-cefwmazm-2.0.1700.54.zip, then flashed Faux123+Shaky156V0.4.zip, then wiped cache/delvik then rebooted system. (I did all of this by copying the files into the ready-to-flash/root files and simply flashed them via TWRP.
Here's the problem: I'm stuck on PACs boot screen. The little pac man game-type animation runs, then it goes to the PAC is loading screen and stays there. And I can't get back to TWRP. If I hold the power/volume up& down keys, it simply reboots right to the rom and goes back to the bootloop.
I've tried searching XDA for a solution but can't find one. Any advice? Thanks!
Click to expand...
Click to collapse
Its volume down + power button... not power + vol up/down. Do that then use the volume up/down buttons to go to RECOVERY and then boot into recovery.
I don't see why flashing those two would cause it to bootloop.... maybe bad MD5 hash?
zephiK said:
Its volume down + power button... not power + vol up/down.
Click to expand...
Click to collapse
Thanks - got it. I definitely appreciate your time and help.
david251 said:
Thanks - got it. I definitely appreciate your time and help.
Click to expand...
Click to collapse
Welcome, hit the thanks button .... just reflash the ROM without wiping and then reboot. See if it loads up, it should boot up without having it boot loop.
zephiK said:
Its volume down + power button... not power + vol up/down. Do that then use the volume up/down buttons to go to RECOVERY and then boot into recovery.
I don't see why flashing those two would cause it to bootloop.... maybe bad MD5 hash?
Click to expand...
Click to collapse
By the way, your question of possibly a bad MD5 hash.... lol... I have no idea. I tend to think it's more due to me doing things to my phone that I really have no business doing since I have only the vaguest clue of what I'm doing at any given time.
david251 said:
By the way, your question of possibly a bad MD5 hash.... lol... I have no idea. I tend to think it's more due to me doing things to my phone that I really have no business doing since I have only the vaguest clue of what I'm doing at any given time.
Click to expand...
Click to collapse
Basically, if you're going to be flashing things. Especially when it comes to a flashing a bootloader or radio (baseband) you should verify its MD5 hash.
MD5 hash just verifies that your download was indeed a good download and nothing screwed up. Flashing a bootloader/baseband with the wrong MD5 hash will lead to problems and ultimately possibly to a brick (not to scare you or anything).
Nah what you did was fine, I don't know why would boot loop. But stuff happens, at least you didn't say "omg i bricked my phone??!" like some other people hehe.
For example, http://forum.xda-developers.com/showthread.php?t=2087227 If we look at 0.54 baseband on the website,
MD5 Sum: 0d556693de6c6af086d8d9a74a5dc164
It has that.... you would then use a program such as http://www.softpedia.com/get/System/File-Management/HashTab.shtml
Which when you download the file, right click -> properties -> file hashes -> you can copy paste the md5 hash and it'll have a check (same md5 hash as the one you copy pasted) or X which is NOT the same md5 hash. If its a green check mark... go ahead and flash away, else... redownload it until you get the right md5 hash (use another browser to download if it fails the second time again).
Better safe than sorry, right? especially when flashing bootloader/basebands. Both are very fragile components of the phone. As far as kernels, roms, etc... doesn't mean as much.
In case it helps anyone, I'll say that it has something to do with the kernel I used. Here's why I say that:
After getting back into TWRP, I restored the nandroid I'd made and everything booted very well, back to just the way it was. Since I'm not one to give up so easily, I went back to TWRP and flashed the radio .54, wiped cache/delvik and rebooted the system - the idea here was to try one at a time and see what happened. Phone rebooted normally and everything as before (meaning it showed (in About Phone) the baseband version 54 but still wouldn't connect to wifi without trouble. So - everything was normal. (Just for the record, the only ROM/Kernel I've found that had no problems at all (in terms of my own Nexus 4) was Paranoid Android v.3.56 from 22MAY2013. This one connected pretty well consistently. But then an update to that rom came out and after flashing, it booted fine but I kept getting an error of "Android Process Acore has stopped" and I couldn't do anything at all - which is what led me to the PAC rom.)
Anyway, so after flashing the radio .54 the phone booted and worked normally. Then I went back into TWRP and flashed the Faux123+Shaky kernel, wiped cache/delvik and rebooted system. Now it went back into the same bootloop and stayed there. So... maybe it's just that this kernel isn't compatible with my PAC rom??
So now I've again restored the nandroid. It's a bummer because I love the PAC rom but I have to be able to connect to wifi. And from what I've read, I'm surprised the Franco kernel doesn't help that. It will eventually connect but often takes 30 to 60 minutes to connect and will then often disconnect after the phone sleeps for 10 minutes or so.
From what I have experienced , faux kernel can not be directly flashed over Franco kernel due to something wrong I didn't know with Franco kernel, I did it and went into boot loop then searched and found that you have to flash reset kernel from faux first over Franco then flash faux kernel,
Official notice from faux kernel thread
NOTICE: If you come from Franco Kernel, YOU MUST FLASH RESET KERNEL FIRST otherwise it will result in a boot loop due to NON-STOCK ramdisk used in Franco Kernel!
Hope that helps
Sent from my Nexus 4 using Tapatalk 2
The reset kernel has helped me a couple of times when had bootloops. The 2 I've had wouldn't ever get to the boot animation though, just the Google logo with padlock, then reboot and same again.
This is the reset kernel I've used. I don't know where I got it or who to give credit to, but it works well
back.to.stock_kernel_and_components.zip here http://www.multiupload.nl/BHFJSGU3QD
MD5: f801fc7702e29d85447e9b6fdc880549
SHA-1: a6e60cf80ba29da4eff4c2048934e8627fb682ac
Pretty sure that Franco changed the ramdisk back to the stock ramdisk A LONG time ago and Faux forgot to change the OP post.
Wouldn't hurt to try the 'reset kernel' though but I don't think that is the case.
Source:
r85:
* Add a bunch of patches from CAF to test if the msm_hsic wakelock can get lower.
* Fix the boot.img packing derp that could bootloop the device after flashing another custom kernel on top of franco.Kernel.
* Make the thermal driver poll twice as fast when the device hits the hot threshold as by showp1984 suggestion.
* Disable sched_autogroup because of one Google's engineer answer to my question: https://android-review.googlesource.com/#/c/51323/
* Add a sampling_timer option for the hotplug driver: /sys/module/auto_hotplug/parameters/sampling_timer - it controls how often the hotplug decision is called. The value is in jiffies. For reference 1 second is 100.
* Merge a patch from Linux Kernel that adds a new hashtable (http://en.wikipedia.org/wiki/Hash_table) implementation to be used in the block layer (block layer is the layer that controls the IO on the several block nodes).
Source: http://minooch.com/franciscofranco/Nexus4/4.2.2/appfiles/nightly-changelog
Click to expand...
Click to collapse
(in bold)
zephiK said:
Pretty sure that Franco changed the ramdisk back to the stock ramdisk A LONG time ago and Faux forgot to change the OP post.
Wouldn't hurt to try the 'reset kernel' though but I don't think that is the case.
Source:
(in bold)
Click to expand...
Click to collapse
Wrong Franco still uses a modified ramdisk. What he's talking about is a drep in the packaging of the boot.IMG that caused bootloops
Sent from my Nexus 4
spaceman860 said:
Wrong Franco still uses a modified ramdisk. What he's talking about is a drep in the packaging of the boot.IMG that caused bootloops
Sent from my Nexus 4
Click to expand...
Click to collapse
K no need to be rude about it with saying "wrong" this is XDA a place to learn from each other. Sorry I don't follow every single word that is being said in the Franco thread or any other related kernel thread.
You need to work on your articulation to make yourself not come off as an aggressive person for absolutely no reason.
zephiK said:
K no need to be rude about it with saying "wrong" this is XDA a place to learn from each other. Sorry I don't follow every single word that is being said in the Franco thread or any other related kernel thread.
You need to work on your articulation to make yourself not come off as an aggressive person for absolutely no reason.
Click to expand...
Click to collapse
I wasn't being rude :beer::thumbup:
Sent from my Nexus 4
I appreciate all the input from everyone. As a final update to this thread, what I finally did is flashed the Xenon HD rom and GAPPS with photosphere (as recommended by the developer). Wifi and signal issues are completely resolved and it seems to be an awesome rom for me. I'm stoked and think I'll wait at least a few days before I go in and screw up anything else.
david251 said:
I appreciate all the input from everyone. As a final update to this thread, what I finally did is flashed the Xenon HD rom and GAPPS with photosphere (as recommended by the developer). Wifi and signal issues are completely resolved and it seems to be an awesome rom for me. I'm stoked and think I'll wait at least a few days before I go in and screw up anything else.
Click to expand...
Click to collapse
PSST, if you're scared you might screw up, make a NANDROID when your phone is still fine. If you get into a bootloop, just restore the NANDROID. It does take quite a lot of space though, so keep that in mind.
Related
Hey ya'll. I'm a NOOB who's currently using CM 7.0.3.1-Supersonic. My phone was randomly rebooting and I was told switching the kernel may alleviate that issue. Based on forum recommendations, I downloaded a SavageZen kernel - SavagedZen-2.2.1-CFS-HAVS-signed.zip MD5 thinking it would correct the problem. I must've selected the wrong kernel or something because my phone is stuck at the boot animation screen and I cannot get beyond it. I do have Titanium backing up my stuff nightly. I just really need some help.
Thanks in advance for your insight!
Cristal
MsCristal said:
Hey ya'll. I'm a NOOB who's currently using CM 7.0.3.1-Supersonic. My phone was randomly rebooting and I was told switching the kernel may alleviate that issue. Based on forum recommendations, I downloaded a SavageZen kernel - SavagedZen-2.2.1-CFS-HAVS-signed.zip MD5 thinking it would correct the problem. I must've selected the wrong kernel or something because my phone is stuck at the boot animation screen and I cannot get beyond it. I do have Titanium backing up my stuff nightly. I just really need some help.
Thanks in advance for your insight!
Cristal
Click to expand...
Click to collapse
It just keeps boot looping?
If so, and all of your information is backed up, it would probably just be easiest to formal all (system, data, boot, cache, dalvik cache) and then reflash the rom and kernel.
easy step is to restore NAND, if you don't have that, get into recovery either via ADB or by power button and volume. Once in recovery just flash the ROM overtop itself or if you have the correct kernel flash that
MsCristal said:
Hey ya'll. I'm a NOOB who's currently using CM 7.0.3.1-Supersonic. My phone was randomly rebooting and I was told switching the kernel may alleviate that issue. Based on forum recommendations, I downloaded a SavageZen kernel - SavagedZen-2.2.1-CFS-HAVS-signed.zip MD5 thinking it would correct the problem. I must've selected the wrong kernel or something because my phone is stuck at the boot animation screen and I cannot get beyond it. I do have Titanium backing up my stuff nightly. I just really need some help.
Thanks in advance for your insight!
Cristal
Click to expand...
Click to collapse
I know this may be a dumb question, but how would I do that if it's stuck in an endless loop? I don't think I can get to bootloader.
MsCristal said:
I know this may be a dumb question, but how would I do that if it's stuck in an endless loop? I don't think I can get to bootloader.
Click to expand...
Click to collapse
Hold down the volume down button (with the phone off) and press power while still holding the volume button down until you see the bootloader.
pull the battery, when you put it back on hold power + vol -
then select recovery
MsCristal said:
I know this may be a dumb question, but how would I do that if it's stuck in an endless loop? I don't think I can get to bootloader.
Click to expand...
Click to collapse
Thanks. I did manage to figure that part out. I also downloaded the most recent tiamat kernel and flashed it. Still stuck at the boot screen.
are you sure you have ROOT and full NAND unlock? did you try flashing the ROM overtop itself after you got into recovery?
MsCristal said:
Thanks. I did manage to figure that part out. I also downloaded the most recent tiamat kernel and flashed it. Still stuck at the boot screen.
Click to expand...
Click to collapse
No, I did not try flashing the ROM over itself. I'm sorry for being such a "girl." LOL. Should I try doing that too?
When you flash a kernel you generally have to do a full wipe. I recommend Calkulins format all zip file.
Then flash the ROM, then flash the kernel, then flash GAPPS.
If you get stuck in a boot loop while flashing a kernel make sure you didnt download a wrong kernel(like an incredible kernel). I have done that and didnt realize it said INC instead of EVO and got stuck at the boot screen.
Thanks for your help. I had to re-flash my ROM, but I'm back in business!
I just bricked my device I guess.
First off flashed:
http://forum.xda-developers.com/showthread.php?t=1162302
TouchWiz UX for 10.1
- Cleared all (factory reset)
Which was working nicely, but then I needed some extra kernel modules, so I installed:
http://forum.xda-developers.com/showthread.php?t=1175299
3.1 Galaxy Tab Wifi OC1.6
- Cleared all (factory reset)
It booted at first, but then rebooted and eventually went to black screen. Now powering up won't work.
So yes it really won't come to life out of it's own.
-------------
My first step: Hang it to a PC
Well it recognized the tab, and was asking for the APX driver, which I found over here: http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75
Which installed correctly, and is recognizing my device (for now).
Who can help me further (it is possible to backup and restore using nvflash)
-- Update 0x4 error...
NVFlash seems to be a dead end. You can't use it without sbk, which we don't have. Any more suggestions?
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
sassafras_ said:
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Click to expand...
Click to collapse
Been there, done that... I've flashed all through CWM recovery, always made a backup, but it doesn't go through the bootloader anymore, so I can't access the recovery, nor the download mode (for Odin flashing).
The only thing I can access at the moment is that stupid NVFlash, and since my device is I/O locked, I can't flash anything.
tmbk said:
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I will check on this. It's the only way to fully reset my device. Since it is I/O locked, it can't have harmed my bootloader or CWM recovery.
I made sure before flashing that the MD5 checksum was right (which it was). The only thing it flashed was a kernel. Well I will drain my battery and check if it is possible to boot it up after that. Else I buy a new one
Exact same thing happened to me.. ran poitee kernel over OTA update.. killed everything but nvflash + all black screen.
Cannot get it to flash w/ bootloader.. Have 2 days to RMA and I really don't want my data out there in the event this thing comes back up after the battery dies.
PS- My unit was bootloader unlocked and rooted.
Hello,
I have tried searching but haven't been able to find a similar issue for any android devices (amazing right?). My nexus 7 will not respond to any soft reboot. From power menus to terminal to factory reset (yes including from ROM recovery and the like). It will reboot from the 10second press, but as we know that is pretty ineffective considering the nexus 7 has that bug where you can't access recovery from boot loader. I have tried connecting to a PC to force recovery, Nada.
So now I am out of idea. Also, for the next 2 weeks I don't have a PC, only a gnex and nexus 7...
Any help appreciated.
update your bootloader and recovery, that bug has been fixed. what rom are you running, every single reboot/power off option works here.
I can't update it without being able to reboot. And I know its not a common issue.. hense why I ask for help... I am not reporting a issue, I am asking for ideas... thanks for the tremendous comprehension though
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
MatAuc12 said:
I can't update it without being able to reboot.
Click to expand...
Click to collapse
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
MatAuc12 said:
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
Click to expand...
Click to collapse
let the battery die and power itself off, then charge it. flash another kernel for sure.
simms22 said:
let the battery die and power itself off, then charge it. flash another kernel for sure.
Click to expand...
Click to collapse
I did let it die for cold boot and again, understanding my problem means since I can't initiate a reboot or get into recovery I cannot flash anything
BillGoss said:
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
Click to expand...
Click to collapse
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
MatAuc12 said:
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
Click to expand...
Click to collapse
boot pressing volume down while pressing the power button into the bootloader, flash a different kernel via fastboot. you can flash franco kernel in fastboot, since it is in boot.img form, or extract the stock boot.img from a stock rom and fastboot flash that. ive had similar behaviors with test kernels, faux forgot something in the kernel. then download and flash the newest bootloadee to fix your recovery from bootloader bug.
Try simms22 approach first.But if you can't get into fastboot and you can boot into the ROM- then you could try rewriting the boot.img. Get the boot.img/kernel you want and use the dd command to write it.
Warning: you can do serious damage with the dd command.
If you need some help with this, let me know. But I accept no responsibility if things go terribly wrong.
Sent from my Nexus 7
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
EDIT:
I have TWRP 2.5.0.3 on my phone
sebbo1 said:
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
Click to expand...
Click to collapse
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Colonel Sanders said:
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Click to expand...
Click to collapse
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
sebbo1 said:
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
Click to expand...
Click to collapse
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Colonel Sanders said:
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Click to expand...
Click to collapse
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
sebbo1 said:
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
Click to expand...
Click to collapse
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Colonel Sanders said:
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Click to expand...
Click to collapse
Are you talking about slimroms.net? If you are, which addons do I download?
EDIT: nevermind. I downloaded the AIO (all in one)
sebbo1 said:
Are you talking about slimroms.net? If you are, which addons do I download?
Click to expand...
Click to collapse
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Colonel Sanders said:
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Click to expand...
Click to collapse
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
sebbo1 said:
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
Click to expand...
Click to collapse
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Colonel Sanders said:
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Click to expand...
Click to collapse
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I would say so myself, Odin back to stock, but since you have a mac and I'm not sure if Heimdall support the S4 try this:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Format /data
Format /internal (If CWM-based recovery)
Flash ROM, addons, reboot
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
sebbo1 said:
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
Click to expand...
Click to collapse
That means the battery is low... Charge it up some... Check your PM for my gmail if you need some help, posting back and forth can take a while.
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
sebbo1 said:
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
Click to expand...
Click to collapse
Glad you got it going man, and enjoy Slim, it's hands down the best ROM there is if you prefer minimal with tons of customization options.
Hey guys,
I've known about this whole modding thingy going on for android phones, and i've decided to give it a shot myself.
I took a backup of everything (copied everything.. didn't use any app for that. not too smart of me..)
Anyway,
I looked around and decided to install Hells Core kernel on my phone, along with Cyanogen Mod.
So after installing the SDK on my computer, unlocking the phone, rooting the phone with SuperSU and Clockwork Mod,
I got to installing the kernel.
I put it on my phone, rebooted into recovery mode, reset all data (dalvik cache and all..)
then I installed the kernel from a zip file I put on the phone, and it all went smoothly.
However, when I reboot my phone - it's all messed up!
The screen is all half yellow, and half is just black - not even text.
In the yellow part, you can hardly tell that it's the first welcome screen - because the text is too big to fit the screen.
Anyway, the whole phone is fk3d up.
I just wanna put it back to the original stock kernel and rom...
How do I do that now?
Thanks a lot guys..
This is urgent >_<
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
jd1639 said:
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
Click to expand...
Click to collapse
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
capzul said:
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
Click to expand...
Click to collapse
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
hassi4042 said:
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
Click to expand...
Click to collapse
Well, I flashed the kernel before I put the ROM, so this happened with HC kernel on stock ROM.
:X
you probably flashed the wrong version of the kernel
You did get the CM Version of Hells Core, right?
This happens to me all the time, just reflash the Roms .zip and you'll be fine.
Sorry to say that, but from your comments it's obvious that you messed up with wrong kernel's version and is not a fault of this specific kernel.
Also the zero kb downloads show bad downloads on your side again.
Sent from my ONDA A9 Core4
capzul said:
Hey guys,
I've known about this whole modding thingy going on for android phones,
Click to expand...
Click to collapse
Lol
Sent from my Nexus 4 using Tapatalk