Hi everyone,
So i'm having an issue with my Galaxy S4 GT-i9505. It seems that any custom ROM I try to flash it with just gets stuck at Boot. I can always restore to stock so its not that big of a deal but still I'd like to be able to use a custom ROM on it one of these days !
Here's what I did so far:
1) The phone was rooted with CF Autoroot, then flashed TWRP recovery with Odin 3.x
2)Tried to install Omega Rom v9. With Data, Cache, Delpik wipe. Stuck at Samsung logo after reboot
3) Restored back to stock
4) Repeated 2)
5)Tried to install PAC Rom, again Data, Cache wipe, Flashed Gapps before Reboot
6)Stuck at "PAC loading" logo
7)Tried 5) again without flashing Gapps. Still stuck
8)Back to stock
I'm thinking of trying to flash a Pre-Rooted Rom like some of DJeMBeY. Anyway, can someone point me in the right direction ?
Slash5469 said:
Hi everyone,
So i'm having an issue with my Galaxy S4 GT-i9505. It seems that any custom ROM I try to flash it with just gets stuck at Boot. I can always restore to stock so its not that big of a deal but still I'd like to be able to use a custom ROM on it one of these days !
Here's what I did so far:
1) The phone was rooted with CF Autoroot, then flashed TWRP recovery with Odin 3.x
2)Tried to install Omega Rom v9. With Data, Cache, Delpik wipe. Stuck at Samsung logo after reboot
3) Restored back to stock
4) Repeated 2)
5)Tried to install PAC Rom, again Data, Cache wipe, Flashed Gapps before Reboot
6)Stuck at "PAC loading" logo
7)Tried 5) again without flashing Gapps. Still stuck
8)Back to stock
I'm thinking of trying to flash a Pre-Rooted Rom like some of DJeMBeY. Anyway, can someone point me in the right direction ?
Click to expand...
Click to collapse
Flash philz recovery and then flash any rom u want after flashing rom wipe cache / dalvik and reboot
Well that did it... God damn TWRP been battling with it for a week ! Thanks
Related
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
ifonuser78 said:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
This happens with many including me some time with many diffrnt files chainging and overwriting causes the same
Best option as u said above flash stock firmware
Then u can try what I feel will work better in ur case
Root the phone with CF root method
Flash Philz Recovery
wipe cache / dalvik / ix perm and reboot and go ahead with ur Rom flashing
Ok, flashed the stock ROM which was not rooted, then rooted using CF's method and flashed PhilZ. I couldn't find the option to fix permissions in PhilZ recovery, and went ahead with the installation of Omega 9 after wiping. I couldn't even get Omega to boot, previously it worked on the first boot and then no longer after a restart.
I don't know whats going on here.
I'm flashing the pre-rooted MGA now.
ifonuser78 said:
I'm flashing the pre-rooted MGA now.
Click to expand...
Click to collapse
Pre-rooted MGA works fine, but no other custom ROM.
I ran TriangleAway to reset the counter, but that didn't help either. No third party custom ROMs for me. :crying:
Flash latest Philz recovery.
Go to mounts and storage.
MAKE SURE YOU HAVE A ROM ON SD CARD.
Format system, cache, data and preload.
then just to be sure everything is gone I go to wipe /data factory reset and choose the wipe to install a new rom.
Then go to install zip and flash rom.
Once it's flashed you should be good to reboot.
If you're still in a bootloop then go to wipe/data factory reset but choose first option not the one to install rom.
Now reboot again, good to go!
Just a thought, if you're still having trouble flash a AOSP kernel in Philz as you might be trying to boot an AOSP rom with a TW kernel installed
Sent from my GT-I9505 using XDA Premium HD app
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Nepoznati said:
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Click to expand...
Click to collapse
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
antique_sonic said:
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
Click to expand...
Click to collapse
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Nepoznati said:
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Click to expand...
Click to collapse
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
SOLVED
antique_sonic said:
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
Click to expand...
Click to collapse
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Nepoznati said:
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Click to expand...
Click to collapse
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
antique_sonic said:
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
Click to expand...
Click to collapse
It could probably be a problem with TWRP as you mentioned earlier. After using CWM everything went smooth after updating my kernel. Last night I couldnt hold me back to try one more time, and I flashed X-NOTE with TWRP and I got the same problem as described in #1 post. Then I installed CWM and flashed X-NOTE again and everything got messed up. Then I restored everything, force installed the kernel and bootlaoder. After that installed CWM and then I was able to run X-NOTE without any problem.
I am not a professional developer but I may think that the problem is TWRP when it tries to flash the kernel under the process with may results in some problems. When using CWM from the beginning I do not get any problems but when using TWRP I need to restore everything back.
hello guys,
i have a problem with my galaxy s5 live demo unit and i can install G900F roms without problems... but then i tried to change the splash screen but it didn't work... then i installed a new rom with kitkat because i wanted to change back to kitkat and the rom installed without any errors but it won't boot up because it's stuck at the splash screen so i restored from a backup i made with TWRP and it booted up fine... then i installed alexandr rom with android 6.0.1 and after that 5.0 but it doesn't seem to install any rom anymore because it's stuck on the splash screen
please help me i really want another rom that is kitkat or marshmallow
AlphaGam3r said:
hello guys,
i have a problem with my galaxy s5 live demo unit and i can install G900F roms without problems... but then i tried to change the splash screen but it didn't work... then i installed a new rom with kitkat because i wanted to change back to kitkat and the rom installed without any errors but it won't boot up because it's stuck at the splash screen so i restored from a backup i made with TWRP and it booted up fine... then i installed alexandr rom with android 6.0.1 and after that 5.0 but it doesn't seem to install any rom anymore because it's stuck on the splash screen
please help me i really want another rom that is kitkat or marshmallow
Click to expand...
Click to collapse
Yes you can
I'm using G900X running
Resurrection Remix 6.0.1_r61 for (G900F)
Pico Gapps
Boeffla Kernel
Xposed
What I did is to clean first...
Wipe Data, Cache, System, Dalvik Cache & do a Factory Reset,reboot.
Boot to Download Mode then flash Chainfire Superuser.zip using PC Odin to root.
Reboot & installed Busybox open it & install to systen/xbin done.
Turn on USB Debugging on Settings> Developer Options.
Flash Philz recovery....
Boot to recovery (Philz_recovery) then select Wipe > Wipe to install rom, after that wipe Dalvik, then flash Resurrection Remix 6.0.1_r61 v5.7.3, wipe Dalvik
Now flash Pico Gapps the wipe Dalvik...done!
Wait for it to boot it may take 5-10min
Hello,
I did have CM13 installed on sm-a500fu and wanted to go back to stock rom. Downloaded right version (TWO-A500FUXXU1BOJ6-20151119145810 - 5.02. )) and flash process was without problem (ODIN) .Then i wanted twrp back and i cant do this no matter which version of twrp i use(twrp2.8.7.0-a5ultexx-19082015.tar,twrp-2.8.7.0-a5ultexx-20082015.tar). Recovery flash goes ok but cannot enter recovery.
Phone is always on Samsung logo
My suggestion is to flash again stock ROM, boot in stock recovery and wipe data/factory reset. Reboot to stock ROM normaly and after that you have to follow the steps to root and install twrp as mentioned in the other thread dedicated to it (I assumed you did that once when you flashed CM13).
In fact that's what I did on my phone...
Flash full stock and once done do a factory reset in stock recovery, do this 3 times, then flash twrp.
From the giver of stock roms
After seeing DarkLord's ROM for turning my Note 3 into a Note 7, I decided to give it a go.
I rooted my Note 3 [SM-N9005] with TWRP and went ahead with the install.
Unfortunately, a few seonds after it looks like it's installing, the phone restarts only to display the default Samsung Galaxy Note 3 wording in white with the black ground. It does nothing more.
I have tried other ROMs which result in the same and stock ROMS that display "Could not find 'META-INF/com/google/android/update-binary' in the zip file" instead.
My phone seems to be now totally screwed where I've got no idea what to do next so any help would be very much appreciated.
There is no need to root the phone before installing twrp as twrp can be flashed using Odin.
To flash the rom, did you wipe system, data, and cache before installing?
To start over, flash a stock rom using Odin, then reinstall twrp, perform and full wipe, and flash the custom rom.
audit13 said:
There is no need to root the phone before installing twrp as twrp can be flashed using Odin.
To flash the rom, did you wipe system, data, and cache before installing?
To start over, flash a stock rom using Odin, then reinstall twrp, perform and full wipe, and flash the custom rom.
Click to expand...
Click to collapse
I did wipe the above each time I try to install a ROM but it won't install any whatsoever, as described in my previous post.
Also Odin doesn't seem to see the phone anymore, although I'm not sure if I have to change a setting in TWRP for that to happen.
Maybe if I could install a new recovery manager then I might have a chance but can't get Odin to see my phone.
I'm really worried now, just can't understand what's going on.
Thanks again.
Odin can only recognize the phone if the phone is in download mode, not TWRP/recovery.