hi I have rooted and installed clockwork mod on my i9505 but when I boot in to clockwork mod and go to install cyanogen 10.1 it looks like it is installing rom then the android man pops up and lies down with red triangle in chest. I then reboot but my fone it gets to the Samsung gti i9505 screen and halts there no matter how long I wait or reboot again I get no further. I just have to go to restore and use my stock rom I9505XXUAMDM again.
DOES ANYONE NO HOW TO SORT THIS....THANKS
fezz64 said:
hi I have rooted my i9505 but when I boot cwm and go to install cyanogen 10.1 it looks like it is installing rom then the android man pops up and lies down with red triangle in chest. I then reboot but my fone it gets to the Samsung gti i9505 screen and halts there no matter how long I wait or reboot again I get no further. I just have to go to restore and use my stock rom I9505XXUAMDM again.
DOES ANYONE NO HOW TO SORT THIS....THANKS
Click to expand...
Click to collapse
You have to flash a custom recovery in order to flash customs roms (or mods) like Philz Touch or TWRP. Look in Android Original thread for either one of these. I use Philz Touch myself and very happy with it, link http://forum.xda-developers.com/showthread.php?t=2281367.
install custom rom
gee2012 said:
You have to flash a custom recovery in order to flash customs roms (or mods) like Philz Touch or TWRP. Look in Android Original thread for either one of these. I use Philz Touch myself and very happy with it, link http://forum.xda-developers.com/showthread.php?t=2281367.
Click to expand...
Click to collapse
hi there I installed clockwork mod and have root
I can back up my fone with cwm but the problem is installing cy 10.1
Maybe the file is corrupt.
Try downloading the file again, and copy to internal SD.
Related
Hi there,
I'm a newbie to android. Just got my i9000 (international version of Galaxy S) for two weeks which I like it very much and flashed it to the official Froyo 2.2 (Build ZSJPD, which to my understanding is based on the European JPO) straight away. But only recently that I find out that it can neither boot into the recovery nor the download mode via the 3 button method, which makes flashing via the Odin impossible for me. I tried to download the Rom Manager to install the Clockwork Recovery Mod but I faced the same problem as the top message of this thread, i.e. it cannot get into the unsigned CWM recovery as it is running the stock 3e recovery.
Nonetheless, thanks to the "Quick Boot App", I was able to go into the stock recovery mode by clicking the dedicated button. So my question is:
Is there any way I could flash the stock kernel back to 2e recovery, given the above condition, so that I could run the CWM recovery?
Is there any apps, which would actual install a different kernel so that I could bypass the stock kernel?
Hope big guys out there could give me some hint and show me the way! Otherwise, I would miss a lot fun and can't even apply the Universal lagfix.
Alex
I am curious too. I am running ZSJPE (Asian Build) but it doesn't seem to have 2e recovery as I am unable to boot into CWM, even with ROM Manager installed.
Any help would be greatly appreciated.
aywchiu said:
Hi there,
I'm a newbie to android. Just got my i9000 (international version of Galaxy S) for two weeks which I like it very much and flashed it to the official Froyo 2.2 (Build ZSJPD, which to my understanding is based on the European JPO) straight away. But only recently that I find out that it can neither boot into the recovery nor the download mode via the 3 button method, which makes flashing via the Odin impossible for me. I tried to download the Rom Manager to install the Clockwork Recovery Mod but I faced the same problem as the top message of this thread, i.e. it cannot get into the unsigned CWM recovery as it is running the stock 3e recovery.
Nonetheless, thanks to the "Quick Boot App", I was able to go into the stock recovery mode by clicking the dedicated button. So my question is:
Is there any way I could flash the stock kernel back to 2e recovery, given the above condition, so that I could run the CWM recovery?
Is there any apps, which would actual install a different kernel so that I could bypass the stock kernel?
Hope big guys out there could give me some hint and show me the way! Otherwise, I would miss a lot fun and can't even apply the Universal lagfix.
Alex
Click to expand...
Click to collapse
It amazes me the amount of people flashing roms without 3br. Why dont you install the 3br fix? then you can do whatever you like to your phone
http://forum.xda-developers.com/showthread.php?t=785201 odin
http://forum.xda-developers.com/showthread.php?t=821698 update.zip
Try either of these before you brick your phone! it doesnt matter how carefully you follow instructions it takes just one bad flash and your history...
tragusman said:
It amazes me the amount of people flashing roms without 3br. Why dont you install the 3br fix? then you can do whatever you like to your phone
http://forum.xda-developers.com/showthread.php?t=785201 odin
http://forum.xda-developers.com/showthread.php?t=821698 update.zip
Try either of these before you brick your phone! it doesnt matter how carefully you follow instructions it takes just one bad flash and your history...
Click to expand...
Click to collapse
I've been directed to one of these links to fix the 3BR bug on my I9000, but after reading some replies I'm a little hesitant as several people have reported their phone being bricked thanks to it...
If by any chance my phone does get bricked because of this, is there any other way to re-flash or something of the sort?
EDIT: Sorry to bump an old post...
I am in need of some help.
I recently installed a 4.3 rom Kangabean and the install went fine. However on first reboot, I got a yellow triangle warning me that the software was not authorized by att has been found on your phone.
Holding down power and volume down then get me the custom icon
So I am able to boot back the phone but cannot get into recovery.
The phone is MDL and the rom is supposed to be loki'd
How do I get rid of this crap and be able to reboot into recovery.
I'd Odin back to stock and start over.
yeah i think thats what I am going to do
man this is so weird.
Returned to stock. Rooted then went to install twrp. At reboot, bam custom icon. I cannot get into twrp at all
what the heck am I doing wrong?????
Suzook1 said:
man this is so weird.
Returned to stock. Rooted then went to install twrp. At reboot, bam custom icon. I cannot get into twrp at all
what the heck am I doing wrong?????
Click to expand...
Click to collapse
I was going to say this earlier, flash the correct kernel, you are flashing the wrong one...
Thanks you
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is the one I am flashing. How is that wrong?????
Suzook1 said:
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is the one I am flashing. How is that wrong?????
Click to expand...
Click to collapse
that is NOT a kernel, you must use a loki kernel...
TheAxman said:
that is NOT a kernel, you must use a loki kernel...
Click to expand...
Click to collapse
He can't get into recovery. The tar looks correct for Odin.
yes correct I cannot get into recovery. I flashed back to stock. Rooted then did goo manager and as soon as I rebooted into recovery I got the custom icon and it loads stock recovery..... WERIDNESS
ok update. After installing recovery like 5 times through goo it FINALLY boots to twrp
my question is this though, why after just reinstalling the stock firmware, rooting and then installing twrp is is showing a custom rom icon at start up????
Suzook1 said:
ok update. After installing recovery like 5 times through goo it FINALLY boots to twrp
my question is this though, why after just reinstalling the stock firmware, rooting and then installing twrp is is showing a custom rom icon at start up????
Click to expand...
Click to collapse
Post #2 should help getting rid of the custom icon. http://forum.xda-developers.com/showthread.php?p=42320414
thank you for the link. I will chalk that one up as mystery !!!!
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.
Hello,
I am facing weird problem, I am not able to install custom recovery, I have tried almost everything.. nothing helped.
I am still getting stock recovery..I have tried to flash it via Odin, via some apps, unfortunatelly nothing worked.
My Samsung Galaxy S4 i9505 is running KK 4.4.2.
Any idea?
Thank you.
I had this problem too. keep flashing cwm recovery through the app (needs root I think). and reboot into recovery, once you get cwm you can flash a custom rom or another recovery like twpr or philz.
s4 i9505 stock KK
I have that problem too. I have stock KK 4.4.2 XXUGNG8 updatet ota. When i try to flash flashable zip file cwm of philz or twpr i get some error like:
E:footer bad
Mds check
Something like that and cant flash it. I tryed with odin but no luck. Does anyone have same problem?
I had this problem to
I fixed it by checking te root options.
If u use a root app, make sure it gives always root acces.
After this, install a custom recovery rom
After that you'll have no problem installing a custom ROM
Good luck.
Xehk said:
I had this problem to
I fixed it by checking te root options.
If u use a root app, make sure it gives always root acces.
After this, install a custom recovery rom
After that you'll have no problem installing a custom ROM
Good luck.
Click to expand...
Click to collapse
But my phone is not rooted, its new, with stock recovery, knox 0x0 still....
Have any idea?
Ok, but what if my phone is not rooted, how am I supposed to root it? When I tried CF-Auto-Root my phone started to reboot randomly during the phone call.
I have found one solution, but I am not sure if it works, it says that if you are flashing custom recovery via odin, you have to take out the battery after the flash is done so you won't allow your phone to restart and rewrite the recovery back to stock. Have anyone heard about it?
No, no idea.
Thats crappy.
Only know how I fixed it
icefun said:
I have found one solution, but I am not sure if it works, it says that if you are flashing custom recovery via odin, you have to take out the battery after the flash is done so you won't allow your phone to restart and rewrite the recovery back to stock. Have anyone heard about it?
Click to expand...
Click to collapse
Just uncheck auto-reboot before you flash the recovery. That will fix your problem.
I have tried it, but it didn't help still looking for solution, is there any way how to RENAME RECOVERY RESTORE FILES so I can finally flash custom recovery? (non-rooted phone)
OK, so the solution that worked was simple and I have already mentioned it, you have to take out you battery on samsung galaxy s4 logo, before it reboots.
My solution
Hi I had the same problem too,
I solved it this way: (My phone was rooted)
Download the .zip file from the recovery you want (I used CWM 6.0.4.7)
Next download 'SGS4 flasher' from the playstore.
SGS4 flasher needs root (I think) andyou can flash your recovery through that app.
Next boot into the recovery and you should probably end up in your custom revovery every time now.
If you don't end up in your custom recovery, download ROM manager and then choose the option boot into recovery.
This worked for me at least :laugh:
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