Tried to install CWM from rom manager 6.0.4.6 but i had 6.0.4.7.
This cus i have problem installing CM updates directly by pressing restart and install.
Efter this i was in a boot loop an could not access CWM only the DL mode. So i installed CWM from the original source i did the first time and then the boot was ok all the way but then tried PWR VOL+ HOME but then i gut in to the boot loop again untli i reinstalled the CWM tried once more but same result.
So now i have CWM installed and i can boot up but i cant access CWM to make backup or restore the previus one.
Any ideas of what could be wrong?
Wrong section
Sent from my SM-N900T using Tapatalk
6.0.4.7 is for KK bootloader. If you haven't that's why
go back to 4.6
I have kitkat cm11
maybe thats why it does not work now?
With one should i have? Link to dl pls.
Sorry if posting wrong could someone move it please?
spyvingen said:
I have kitkat cm11
maybe thats why it does not work now?
With one should i have? Link to dl pls.
Sorry if posting wrong could someone move it please?
Click to expand...
Click to collapse
its your bootloader thats still 4.3, cm kitkat works on the old bootloader .... just go and download a older version of cwm
ratcom said:
its your bootloader thats still 4.3, cm kitkat works on the old bootloader .... just go and download a older version of cwm
Click to expand...
Click to collapse
I upgraded to samsung stock kikat before and its non reversible as i got it does that matter?
to be frank, I never try to flash anything from ROM manager.
This tools I've left it very very long time ago.
Have you tried to reflash the KK stock firmware, since you said you are on KK already (to get your stock recovery first), make sure everything is ok. Then reflash the CWM through ODIN. Don't use ROM manager.
antique_sonic said:
to be frank, I never try to flash anything from ROM manager.
This tools I've left it very very long time ago.
Have you tried to reflash the KK stock firmware, since you said you are on KK already (to get your stock recovery first), make sure everything is ok. Then reflash the CWM through ODIN. Don't use ROM manager.
Click to expand...
Click to collapse
Could try that. The problem is i cant make a backup now when i dont have access to CWM
But if it is the only way sure i will try it.
Related
it seems i cant get CWM to be flashed into my GT-I9500 (rooted with adam kernel already)
already tried from http://forum.xda-developers.com/showthread.php?t=2274526&page=8&nocache=1 and cofface one...
but still no luck there.. after i successfully flashed with odin at PDA and i get reboot there was no CWM there and even after i go to recovery mode (power + up + menu) i still cant access CWM, it just give me my ordinary recovery mode...
need some help here..
libra88 said:
it seems i cant get CWM to be flashed into my GT-I9500 (rooted with adam kernel already)
already tried from http://forum.xda-developers.com/showthread.php?t=2274526&page=8&nocache=1 and cofface one...
but still no luck there.. after i successfully flashed with odin at PDA and i get reboot there was no CWM there and even after i go to recovery mode (power + up + menu) i still cant access CWM, it just give me my ordinary recovery mode...
need some help here..
Click to expand...
Click to collapse
I have installed both the recovery and it works fine can u tell me whats the error u getting while flashing with odin so that some one here can help
123hiten said:
I have installed both the recovery and it works fine can u tell me whats the error u getting while flashing with odin so that some one here can help
Click to expand...
Click to collapse
actually there was no problem when flashing with odin... i already used the latest odin.. and im already root my sgs2 nicely and my sgs4 (using adam kernel) with odin..
odin last message was successful and no problem..
my device I9500XXUAMDL and i know it already listed there as working device..
so im still confused why my phone cant get CWM installed right T__T while already rooted by adam kernel too..
+another not really important question... im already in this forum since my sgs2 (almost 2year ago) but now im listed as new member -__- hmm what happened here?
libra88 said:
actually there was no problem when flashing with odin... i already used the latest odin.. and im already root my sgs2 nicely and my sgs4 (using adam kernel) with odin..
odin last message was successful and no problem..
my device I9500XXUAMDL and i know it already listed there as working device..
so im still confused why my phone cant get CWM installed right T__T while already rooted by adam kernel too..
+another not really important question... im already in this forum since my sgs2 (almost 2year ago) but now im listed as new member -__- hmm what happened here?
Click to expand...
Click to collapse
If possible Re flash the stock firmware find urs from below link
http://forum.xda-developers.com/showthread.php?t=2265477&highlight=stock+firmware
after that below link for rooting and recovery and see if works
http://forum.xda-developers.com/showthread.php?t=2276803
May be ur were inactive so it says like that not sure thought just a guess as on 2 posts
libra88 said:
actually there was no problem when flashing with odin... i already used the latest odin.. and im already root my sgs2 nicely and my sgs4 (using adam kernel) with odin..
odin last message was successful and no problem..
my device I9500XXUAMDL and i know it already listed there as working device..
so im still confused why my phone cant get CWM installed right T__T while already rooted by adam kernel too..
+another not really important question... im already in this forum since my sgs2 (almost 2year ago) but now im listed as new member -__- hmm what happened here?
Click to expand...
Click to collapse
According to XDA your join date is May 2013
Disable Auto Reboot in Odin and flash the CWM, then boot manually into the recovery. Its a known security feature which flashes the stock recovery after reboot.
problem solved
jerricson said:
Disable Auto Reboot in Odin and flash the CWM, then boot manually into the recovery. Its a known security feature which flashes the stock recovery after reboot.
Click to expand...
Click to collapse
wowww dude thx a lot it solves my problem
but still that auto recovery... cant be disabled try it but i get error + fail boot => reboot-ed again => lost my CWM again... but at least already get the backup done XD
can anyone tell my how to disabled stock recovery XD CWM cant do that as i try it before..
+yep im joined since 2 years ago but not really active lately especially after sgs2 ics stable version come out .__.
Try this recovery http://forum.xda-developers.com/showthread.php?t=2280457 and don't forget to choose disable recovery flash option when you exit the recovery.
jerricson said:
Try this recovery http://forum.xda-developers.com/showthread.php?t=2280457 and don't forget to choose disable recovery flash option when you exit the recovery.
Click to expand...
Click to collapse
already tried it but when i choose disable recovery flash - i got error message and fail boot... but after hard reboot, everything come back to normal and of course recovery flash initiated too ~_~ lost my cwm again....
libra88 said:
already tried it but when i choose disable recovery flash - i got error message and fail boot... but after hard reboot, everything come back to normal and of course recovery flash initiated too ~_~ lost my cwm again....
Click to expand...
Click to collapse
How about flashing stock ROM and start everything again? May be you'll get lucky.
jerricson said:
How about flashing stock ROM and start everything again? May be you'll get lucky.
Click to expand...
Click to collapse
i prefer not because my hp already rooted good enough with no errors just cant use cwm.. maybe i hope cwm dev can get solution for this matter XD stock recovery things....
I have an ATT i337 S4 (mdl baseband) running on T-mobile. Current setup was wicked 7.0 ROM with ATT kernel.
I was trying to change to cyanogenmod ROM and tried using my TWRP 2.5.0.2 to load the rom but it would flash it and gave me an md5 error. Supposedly this is a known issue with TWRP so most people recommend using clockworkmod recovery and I tried to load that using recovery tools. Recovery tools couldn't find the CWM image file but did find the 2.6.3.0 updated TWRP image file so I tried to update TWRP and when I did, I can't boot to recovery anymore and instead get the yellow triangle saying unauthorized software.
At the same time (ugh) I flashed wicked 8 ROM update and think I loki'd it (I am running wicked 8.0 now) but I forgot to run the att kernel afterward. The current kernel is 3.4.5 ... dirty ptmr3 ... N5110 #1. I think this is the standard t-mobile kernel which will obviously not work on my ATT phone.
The problem is, now I can't reboot into recovery mode. When I try, I get the yellow triangle "system software not authorized by ATT...". I don't know if the problem is with the bad kernel or with the updated 2.6.3 TWRP. The only way I can get around the bootloader problem is the hold down the down vol and home button, then the power button and that gets me into a "Warning a custom OS can cause critical problems ..." page. From there if I continue, I get the yellow triangle. If I hit the volume down button to cancel, it boots normally but not into the bootloader and I have partial functionality of my phone.
Where do I go from here? Odin to stock? Replace the bootloader somehow? Anything else?
I did do a nandroid of my system before all of this but for some reason I can't access my SD card. I can hit mount but nothing shows up on file manager. Will that backup replace the bootloader with the known good one? I could copy the backup to the phone memory and do it from there using titanium backup I think.
Thanks,
odin back to stock and then wipe/clear then retry should fix this problem
lilg754367 said:
odin back to stock and then wipe/clear then retry should fix this problem
Click to expand...
Click to collapse
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
colorchange said:
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
Click to expand...
Click to collapse
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
colorchange said:
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
Click to expand...
Click to collapse
I'm guessing I might be able to modify the open boot script and change to the old version but I don't know how to do this.
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
lilg754367 said:
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
Click to expand...
Click to collapse
Thanks lil, i know the kernel I want and have it downloaded. Right now I am downloading the tar file to get me back to stock. I was hoping to do something easier but crud...
yea no problem just hit the thanks button for me good luck
I can't get Odin to talk to my device. When it is not in download mode, Odin sees it but hangs and can't communicate. When I connect it in debug mode (very hard to get into download mode), Odin can't see it.
Help!
i installed safestrap and tried updating to oudhs recovery through recovery.
it says it installs but when i reboot its still safestrap.
also tried installing twrp thorugh android emulator still have safestrap.
any suggestions?
You can't flash a recovery. You're going to have to return to stock
Edit how can someone with so many posts know so little about their device. If you're on ss you have to use the recovery that comes with it. Read the stickies
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
bstylz911 said:
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
Click to expand...
Click to collapse
So if you are on MDB or MDL (You must have been if you have the AT&T S4 and custom recovery) just Odin back to stock firmware and re-install whichever custom recovery you want (as long as it is for this phone and LOKId). Make sure you get the custom recovery on the phone before it tries to update to a firmware that you can't do anything (other then Safestrap) with. Search and read to find the information you need if you don't understand what I am telling you. And don't do anything to your phone until you do. Good luck.
Hi all,
I rooted my smg900f two days ago and flashed a recovery, everything went fine, I tried a couple of custom rom and at some point I noticed that I didn't have root access anymore (checked with root checker). I launched towelroot again, and now it says that my device is not supported yet. Does anybody encountered the same issue ?
ElChouch said:
Hi all,
I rooted my smg900f two days ago and flashed a recovery, everything went fine, I tried a couple of custom rom and at some point I noticed that I didn't have root access anymore (checked with root checker). I launched towelroot again, and now it says that my device is not supported yet. Does anybody encountered the same issue ?
Click to expand...
Click to collapse
Just flash the latest superSU.zip with a custom recovery, link http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip.
Thanks for the tip but it didn't work
ElChouch said:
Thanks for the tip but it didn't work
Click to expand...
Click to collapse
What recovery do you have and what did you do exactly?
gee2012 said:
What recovery do you have and what did you do exactly?
Click to expand...
Click to collapse
I have clockwork recovery, I had Omega ROM running on my phone (maybe at this moment I already lost root but I only noticed it after), I tried to flash this mod, it didn't work so after a few tries I full wiped my phone and insalled Omega 8.0 again. Then I noticed I lost root access when trying to open some apps.
I also flashed the bootloader for SMG900F featured in the Omega rom thread
That's about it
ElChouch said:
I have clockwork recovery, I had Omega ROM running on my phone (maybe at this moment I already lost root but I only noticed it after), I tried to flash this mod, it didn't work so after a few tries I full wiped my phone and insalled Omega 8.0 again. Then I noticed I lost root access when trying to open some apps.
I also flashed the bootloader for SMG900F featured in the Omega rom thread
That's about it
Click to expand...
Click to collapse
Flash CF Auto Root with Odin, your KNOX flag is tripped anyway. Link http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip.
gee2012 said:
Flash CF Auto Root with Odin, your KNOX flag is tripped anyway. Link http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip.
Click to expand...
Click to collapse
Might be a stupid question but in which slot should I load the tar file ? BL/AP/CP/CSC ?
ElChouch said:
Might be a stupid question but in which slot should I load the tar file ? BL/AP/CP/CSC ?
Click to expand...
Click to collapse
AP is the right one.
gee2012 said:
AP is the right one.
Click to expand...
Click to collapse
This didn't work neither :-/
ElChouch said:
This didn't work neither :-/
Click to expand...
Click to collapse
Then i suggest you flash a stock rom, factory reset and root/flash custom recovery from scratch. Its seems some files are messed up that prevents you to root. Backup important files to the pc/sdcard first. That is what i would do at least
gee2012 said:
Then i suggest you flash a stock rom, factory reset and root/flash custom recovery from scratch. Its seems some files are messed up that prevents you to root. Backup important files to the pc/sdcard first. That is what i would do at least
Click to expand...
Click to collapse
I ll try this asap thanks for the help
ElChouch said:
I ll try this asap thanks for the help
Click to expand...
Click to collapse
Good luck mate. After the flash and factory reset flash a custom recovery and then the superSU.zip and you`re rooted.
gee2012 said:
Good luck mate. After the flash and factory reset flash a custom recovery and then the superSU.zip and you`re rooted.
Click to expand...
Click to collapse
Last question (I hope) I have backup files (from my stock rom) I generated with CWM recovery, but it seems I lost CWM too, can I flash this backup with Odin ?
ElChouch said:
Last question (I hope) I have backup files (from my stock rom) I generated with CWM recovery, but it seems I lost CWM too, can I flash this backup with Odin ?
Click to expand...
Click to collapse
There should be a folder on the sdcard named Clockworkmod with the backup, save it to the sdcard before you factory reset. No a backup can`t be flashed with Odin, only in recovery
gee2012 said:
There should be a folder on the sdcard named Clockworkmod with the backup, save it to the sdcard before you factory reset. No a backup can`t be flashed with Odin, only in recovery
Click to expand...
Click to collapse
Ok so I got this rom Alvin's_G900F_XXU1ANG2_Deodexed I boot in regular recovery, start flashing the rom, but it doesn't work and I'm still stuck on Omega rom with no root nor custom recovery :-/ what did I do wrong ?
ElChouch said:
Ok so I got this rom Alvin's_G900F_XXU1ANG2_Deodexed I boot in regular recovery, start flashing the rom, but it doesn't work and I'm still stuck on Omega rom with no root nor custom recovery :-/ what did I do wrong ?
Click to expand...
Click to collapse
Did you flash a stock rom with Odin or flash a custom rom in 3rd recovery? Just do a data factory reset in recovery, pull the battery and wait 20 seconds and flash a stock rom with Odin.
gee2012 said:
Did you flash a stock rom with Odin or flash a custom rom in 3rd recovery? Just do a data factory reset in recovery, pull the battery and wait 20 seconds and flash a stock rom with Odin.
Click to expand...
Click to collapse
There is definitely something i miss... The Rom I downloaded is a .zip with the regular boot.img and all that stuff into it, I can't flash that with Odin right ? I need a .tar right ?
ElChouch said:
There is definitely something i miss... The Rom I downloaded is a .zip with the regular boot.img and all that stuff into it, I can't flash that with Odin right ? I need a .tar right ?
Click to expand...
Click to collapse
You need a md5/tar file for Odin, look on Sammobile/firmwares for it.
gee2012 said:
You need a md5/tar file for Odin, look on Sammobile/firmwares for it.
Click to expand...
Click to collapse
I did it all as you said, everything went fine, Odin said it passed the rom flashing, but then I'm stuck in a boot loop any idea ?
I'm about to try to flash a stock bootloader
ElChouch said:
I did it all as you said, everything went fine, Odin said it passed the rom flashing, but then I'm stuck in a boot loop any idea ?
I'm about to try to flash a stock bootloader
Click to expand...
Click to collapse
No, pull the battery andere wait 20 seconds. Then boot into recovery and data factory reset and reboot.
So my note 3 n9005 always comes up with an error whenever I try installing custom roms. Even with Cwm or Phil touch recovery my phone gets bricked. Any help
Insayn29 said:
So my note 3 n9005 always comes up with an error whenever I try installing custom roms. Even with Cwm or Phil touch recovery my phone gets bricked. Any help
Click to expand...
Click to collapse
What error what roms ??
Usual story is wrong rom for phome model .
JJEgan said:
What error what roms ??
Usual story is wrong rom for phome model .
Click to expand...
Click to collapse
File package not supported if I remember correctly. I am on stock lollipop rom rooted
Check phone model by booting to download mode first .
Sent from my SM-N930F using XDA-Developers Legacy app
Rom should be zip file and flashed as zip through custom recovery .
JJEgan said:
Check phone model by booting to download mode first .
Rom should be zip file and flashed as zip through custom recovery .
Click to expand...
Click to collapse
Yeah i have the correct model for custom rom and everything foes fine till when it reaches the end of installation it comes up an error. I installed cwm and it bricked my phone so its back to lollipop stock rom rooted. Do i need to unlock or install anything else to make it work
I installed cwm and it bricked my phone
thats not possible unless you flash wrong stuff .
what file are you using ??
Insayn29 said:
Yeah i have the correct model for custom rom and everything foes fine till when it reaches the end of installation it comes up an error. I installed cwm and it bricked my phone so its back to lollipop stock rom rooted. Do i need to unlock or install anything else to make it work
Click to expand...
Click to collapse
Are trying to flash custom roms using the stock recovery ?
zlazaar said:
Are trying to flash custom roms using the stock recovery ?
Click to expand...
Click to collapse
No when I manage to get Cwm on my phone I use that then when rebooting phone it goes back to stock recovery
JJEgan said:
I installed cwm and it bricked my phone
thats not possible unless you flash wrong stuff .
what file are you using ??
Click to expand...
Click to collapse
I use rom manager to flash my Cwm. If flashes fine then when I reboot phone it goes back to stock recovery then into download mode
Insayn29 said:
No when I manage to get Cwm on my phone I use that then when rebooting phone it goes back to stock recovery
Click to expand...
Click to collapse
In certain cases, custom recovery won't stick after reboot. The stock firmware will replace it.
Best procedure is to untick "Auto-reboot" in odin and flash TWRP or Phil'z, then manually reboot directly to recovery.
<I use rom manager to flash my Cwm>
Thats your problem . Dont use rom manager at all .Multiple identical posts on the forum .
TWRP is better than CWM, in my opinion. More custom ROMs seem to be more compatible for some reason with TWRP.
2.8.7 to be on the safe side