Flashed Hyperion and stuck at splash image now I can't enter into the recovery it reboots if I do so
Sent from my HTC One X using xda app-developers app
Try
flashing Stock ROM in Download mode.
to fix recovery on your device.
Look for sticky thread in development section by doky73
Flash stock via odin
Sent from my Galaxy Y - A phone with Small Screen and Big Buttons
Related
I tried installing CM7 but accidentally downloaded and tried to flash an update. I can get into recovery and download mode but my phone can't get past the "Galaxy S" screen. Any help would be greatly appreciated.
Thanks!
Start from the start and reflash.
Go to the download mode n repeat the same procedure but make sure u flash the correct file
Sent from my GT-I9000 using XDA Premium App
flash stock 2.2.1 with odin and start over.
Anyone can help me ><?
First, sorry for my Englsh ><
My phone is using cm10.
I can't open anything. Then I reboot my phone, it shows the bootanimation continuously.
And I can't go into the recovery mode by 3-Button Combo.
But I can go into the download mode, I don't know what is it because I always ask my brother helps me to upgrade my phone ><
Then, what can i do now ><?Thanks><
Flash semaphore .tar for jelly bean through odin using download mode to get recovery recovery back and flash rom again.
Sent from my GT-P7500 using xda premium
Alright I have searched all day and can not seem to find a resolution to my problem. It is my fault I shouldn't fix something that isn't broke but it has resulted in issues and I would appreciate it if someone could help me.
I had twrp 2.5.0.2 installed running GE 4.2.2 ROM with MF3 radios installed and GE kernel v11. I saw twrp had a update to 2.6.0.0 and I decided to install it via goo manager it booted up in recovery with the "the software is unauthorized by att" screen and I can do volume down + power after that to reboot phone and not have issues as far as getting my phone booted and working on all the above. But the problem I am having now I have lost custom recovery. I have tried goo manger again as well as some on click root/recovery methods from these forums and all result in the same back to the unauthorized screen mentioned above its like it won't boot into a custom recovery. Any advice is greatly appreciated.
Sent from my Nexus 7 using xda app-developers app
Maybe try ROM manager and install cwm .it will pop up in ROM manager as the T-Mobile s4 but that's what I used to install the first recovery image,then I used that recovery to flash the auto Loki recovery.I have used the same plain auto Loki recovery since then.
Sent from my SAMSUNG-SGH-I337 using xda premium
Just tried that as well. Still not working. When I takes me to that unauthorized page top left it says "secure fail: kernel". But when I reboot the phone normal it comes up just fine....so that tells me its getting past with Loki to boot up my ROM and kernel but for some reason it will not take a custom recovery anymore when I have had one installed previously.
Sent from my SGH-I337 using xda app-developers app
If memory serves me right the Google Edition ROM will make TWRP / GooMananger think you have a 9505(G) and thus it will install that version. So you installed a non-loki'd recovery.
Use Odin, go back to AMDL firmware. (Take SIM out before doing so so it wont download the AMF3 update). Redo Root + Recovery. BEFORE you flash another rom, install GooManager and then update from there. You will be running stock firmware so it will identify the model correctly. Then flash your custom ROM.
Forgive me for being noob when it comes to Odin. But does this OTA the software or will I need to get Odin on my desktop?
Sent from my SGH-I337 using xda app-developers app
I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz
nomad836 said:
I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz
Click to expand...
Click to collapse
What firmware are you on? Please if you know how to flash ROMs you should know where to find it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Sent from my SGH-M919 using xda app-developers app
If you can boot into OS, download Goo Manager from Market and install TWRP 2.5.0.2 recovery
If you get it working--do a lot of reading--many variants and our bootloader is locked. Get to know loki-doki too, if you don't--
I installed twrp and it still gives me the att lock when I go into recovery. Should I try to install Loki with Odin?
Sent from my SGH-M919 using xda app-developers app
loki doesn't install thru odin--it installs thru recovery as a zip
if you still can't get into revovery you may need to odin back to stock--i never used odin, haven't needed too and on an iMac
there are some threads on using it and someone may help with that
loki bypasses samsung's signature verification on recovery and kernels and lets you flash a kernel that hasn't already been loki'd by dev--
Are you getting a lock on the Samsung screen? Or are you getting the warning saying that software is detected that is not authorized by AT&T.
If you are getting the first. Let it boot.
If you are getting the second, loki-doki patch. Google it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Or u can in fact use ROM manager just to flash a recovery "CWM".after flashing cwm get rid of ROM manager and use cwm to flash any of the recoveries. I use philz touch recovery .Google is badass though
Sent from my SAMSUNG-SGH-I337 using xda premium
ODIN emergency restore fixes it.
Sent from my Nexus 7
here ya go
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom
vedantgp said:
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom
Click to expand...
Click to collapse
This is the correct procedure...
Please any one help me...morning i edit the build.prop file on my sgy like this model_name s5360 to nexus s5 and restart....its stuck on boot loop the samsung logo in again again blinking...and restart itself...
Please help what i do i am not have pc...sorry 4 my bad english...
1- restore your nandroid backup you made before making any changes to your phone (but I bet you didn't make one)
2- take the build.prop from the rom you are using put in flashable zip & flash with system mounted
3- try my build.prop - flash attachment in cwm with system mounted (stock based rom only not cm7)
Thanks..checking
Thanks bro let me try.....
Also there is no such thing as a Nexus S5
HnnnnnnnnmnHmmmmmmmmGpuuuuuuuuuuuuu
Enter download mode and flash a stock rom via odin
Sent from my GT-S5360 using xda app-developers app
Dude download odin and flash d stock rom ..... U will find many videos on using "Odin" in YouTube
Sent from my GT-S5360 using xda app-developers app