This is my first post on XDA, since new members cant post in the developer forum, i had no other choice than to post the question here, instead of the original post, please be kind to me
So as the title says I have installed the newest release of the foxhound custom ROM for the samsung s4 i9505. I have read the thread, and the solutions posted there is to flash a custom kernel (I have tried multiple of those).
Device: S4 i9505
Custom recovery: CWM
So this is what I have tried:
Reinstalled the rom, Factory reset + wipe of cache and delwik.
Flashed different kernels, Factory reset + wipe of cache and delwik.
Reinstalled rom (Factory reset + wipe of cache and delwik) and flashed kernel at the same time.
WiFi was working on the Foxhound 0.1 rom before I tried to install the latest (12.6) rom from CM 10.1 (Wich all versions of keeps giving me a error 7, even after I remove the check from the script.)
The other method I found, was to reinstall the Original Samsung ROM (4-11 times) until it worked, then root, flash new Foxhound 0.4 ROM and then the new Kernel (Adam). But I wanted to post here before trying this.
The WiFi toggle is greyed out, making me suspect that the device simply does not register that there is a WiFi chip at all, and that is a kernel problem, no?
Got it working after a long struggle.
Here is what I did:
Factory reset
Wiped chache
Formated system, chache and data
Installed Fochound ROM 0.4
Factory reset + wipe chache / dalwik
Flashed Wanam's Kernel, adam did not work. (http://forum.xda-developers.com/showthread.php?t=2281738)
Shut off phone, not restart.
Turned phone on.
Tried so many combinations, and in the end it worked. Can't believe that it didn't work when I used CWM to reboot, but rather when I shut it off and turned it on manually, maybe a coincidence?
Tipe in dialer next time *#0011# left click,wifi,off and you will haw.
Sent from my GT-I9505 using xda premium
Syversen said:
This is my first post on XDA, since new members cant post in the developer forum, i had no other choice than to post the question here, instead of the original post, please be kind to me
So as the title says I have installed the newest release of the foxhound custom ROM for the samsung s4 i9505. I have read the thread, and the solutions posted there is to flash a custom kernel (I have tried multiple of those).
Device: S4 i9505
Custom recovery: CWM
So this is what I have tried:
Reinstalled the rom, Factory reset + wipe of cache and delwik.
Flashed different kernels, Factory reset + wipe of cache and delwik.
Reinstalled rom (Factory reset + wipe of cache and delwik) and flashed kernel at the same time.
WiFi was working on the Foxhound 0.1 rom before I tried to install the latest (12.6) rom from CM 10.1 (Wich all versions of keeps giving me a error 7, even after I remove the check from the script.)
The other method I found, was to reinstall the Original Samsung ROM (4-11 times) until it worked, then root, flash new Foxhound 0.4 ROM and then the new Kernel (Adam). But I wanted to post here before trying this.
The WiFi toggle is greyed out, making me suspect that the device simply does not register that there is a WiFi chip at all, and that is a kernel problem, no?
Click to expand...
Click to collapse
I same to you
but after flashed this kernel. wifi is working! :laugh:
http://forum.xda-developers.com/showthread.php?t=2297379
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
leandronb said:
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Click to expand...
Click to collapse
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
andyabc said:
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Nigeldg said:
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Click to expand...
Click to collapse
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
12ian34 said:
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
Click to expand...
Click to collapse
I had exactly the same issue you had at first boot, it remained at Google logo forever when i first flashed PA 3.92. This issue came because i was flashing PA 3.02 with Franco nightly 165, franco nightly 165 is for 4.2.2m and if you were in 4.2.2 then you will never know new releases as that one was the last 4.2.2 kernel. I suggest you flash PA 3.92 + gapps from 0802, without Franco, it will boot fine. Also, as explained in big letters in PA download, first step is to download radio and bootloader for the update, i did not have to wipe my memory for the upgrade.
I don't recommend downloading Franco 175 for 4.3, as it has conflicting issues with PA, so use PA with the stock kernel and you should be good meanwhile this gets solved.
12ian34 said:
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Click to expand...
Click to collapse
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Click to expand...
Click to collapse
But how do I go about backing it up before I wipe it give that I can only access fastboot and recovery (CWM) ?!?!
OK, I've found a way to do it using
./adb-mac pull /sdcard/0/ sdcardbackup
do I need to backup anything else?
Also, I've downloaded the link you sent me, just to be clear, first, I wipe data, factory reset, then I send the radio and baseband to my phone using adb, then flash them in recovery and then flash PA 3.69, GApps, Franco Kernel r165 then wipe cache, dalvik cache, then reboot, then go about restoring all my data. Is this correct?
Mee too
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
jsmonu said:
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
Click to expand...
Click to collapse
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
molesarecoming said:
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
Click to expand...
Click to collapse
Moles! Help me! I refer you to my first post in this thread, I want to stay on 4.2.2 and PA 3.69 for the moment, and preferably not wipe everything. I accidentally updated to PA 3.92 and then stuck at the PA logo on boot forever. Now I've tried to go back to 3.69 many times and still get stuck at PA logo. currently using adb pull to get all my important stuff off phone.
Is there a shortcut for me, which doesn't involve wiping??
EDIT:
... OK, I just downloaded the 4.3 radio and bootloader, pa 3.94, gapps and sent them to my phone, flashed each one in turn and then wiped caches, reboot. I skipped the wipe, and now my phone is working for the first time in three days - [optimising apps]. Let's see if this works....
Yep, phone works absolutely fine, didn't have to wipe and now have 4.3 and PA 3.94, which wasnt my original intention, but it had to happen sometime! Thanks for all the help people, I think we can consider this one solved
12ian34 said:
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Click to expand...
Click to collapse
Download the nexus 4 toolkit and flash stock rom from it
I've been trying to upgrade from CM 7.2 to CM 10.{0,1,2}, but my phone keeps getting stuck with the red LED after the Motorola. My understanding is that this means that there is not a viable OS installed. When I flash the appropriate zip the recovery is updated (e.g., TWRP 2.5.0 is installed with CM 10.1). I've tried wiping cache, data, Dalvik cache before and after install, but it doesn't help.
Can anyone suggest what might be happening?
Here's the full story:
I've been running CM 7.2 for a long time and it's been great and stable. But, I saw that CM 10.2 was available a while ago and wanted to give it a try. I originally tried flashing straight to CM 10.2 from CM 7.2 but the installation aborted (status(0)). I posted on the CM 10.2 thread and _mak_V_ suggested that I needed to install TWRP or go through 10.1 first.
I installed Defy TWRP version 2.1.1 from the TeamWin webpage, but was still unable to install CM 10.2. Same problem, and I'm guessing that the recovery is still too old.
So, I decided to go through CM 10.1. I flashed this using TWRP 2.1.1 along with gapps-jb-20130812-signed.zip and the installation seemed to go smoothly. However, I was stuck at the red LED.
I reverted my TWRP backup to CM7.2 and then tried CM 10 with gapps-jb-20121011-signed.zip -- same thing.
To make sure I wasn't completely losing it I installed CM 9 which I tried before. This worked perfectly, but I still can't upgrade to CM10 or above.
Apologies if this question has been answered already. I'm sure that I'm missing something simple, but I've combed the Bravo and Defy threads and can't find anything to help. Can anyone suggest anything?
Thanks for your help!
still no answer?
sjbonner said:
I've been trying to upgrade from CM 7.2 to CM 10.{0,1,2}, but my phone keeps getting stuck with the red LED after the Motorola. My understanding is that this means that there is not a viable OS installed. When I flash the appropriate zip the recovery is updated (e.g., TWRP 2.5.0 is installed with CM 10.1). I've tried wiping cache, data, Dalvik cache before and after install, but it doesn't help.
Can anyone suggest what might be happening?
Here's the full story:
I've been running CM 7.2 for a long time and it's been great and stable. But, I saw that CM 10.2 was available a while ago and wanted to give it a try. I originally tried flashing straight to CM 10.2 from CM 7.2 but the installation aborted (status(0)). I posted on the CM 10.2 thread and _mak_V_ suggested that I needed to install TWRP or go through 10.1 first.
I installed Defy TWRP version 2.1.1 from the TeamWin webpage, but was still unable to install CM 10.2. Same problem, and I'm guessing that the recovery is still too old.
So, I decided to go through CM 10.1. I flashed this using TWRP 2.1.1 along with gapps-jb-20130812-signed.zip and the installation seemed to go smoothly. However, I was stuck at the red LED.
I reverted my TWRP backup to CM7.2 and then tried CM 10 with gapps-jb-20121011-signed.zip -- same thing.
To make sure I wasn't completely losing it I installed CM 9 which I tried before. This worked perfectly, but I still can't upgrade to CM10 or above.
Apologies if this question has been answered already. I'm sure that I'm missing something simple, but I've combed the Bravo and Defy threads and can't find anything to help. Can anyone suggest anything?
Thanks for your help!
Click to expand...
Click to collapse
Oc someone's going to tell you to use search or Google it but I'm not that person shortly I'm going to install cm10 on mine so I'll go through the steps and let you know what to do or might have happened I'll keep you posted.
just made the same mistake
Try updating the recovery and when you wipe you have to do it in ext3 if you want to revert to gingerbread and ext4 for jb as far as I know
Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!
django e said:
Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!
Click to expand...
Click to collapse
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.
kenny1991 said:
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.
Click to expand...
Click to collapse
Thanks! I managed to restore the imei flashing stock lollipop. I initially downgraded because it seemed to me that all instructions were based on kitkat and not much information was available on lollipop. Just wanted to make sure I followed the instructions to the letter. Stupid me...
I tried to restore efs the way you describe it, but it didn't work out for me. Thankfully, things are back to normal now and I will flash cm12.1 directly from stock lollipop now.
Thanks for taking the time to help!