(sorry for my English )
the thing is that my Samsung S wont starts ,when i click the power button its starts in CWM RECOVERY and when i press "reboot system now" it enters a boot loop (the logo keeps running over and over and the phone)
before this happened i originally had the stock ROM of my cellular carrier (2.3.3
then i decided to install another rom and kernel (cyanogenmod 10) so i installed first a clean stock rom (2.3.6) via odin
and then the cyanogenmod rom and kernel (up to now its all fine)
after that i wanted to change and install other rom so i installed again the clean stock rom 2.3.6 via odin...and from then it started to boot loop.
i thought that if i will install the kernel again it will be OK ,but it wont..
and now im in the situation that i have described above..
help SOMEONE please=]
LCPD said:
(sorry for my English )
the thing is that my Samsung S wont starts ,when i click the power button its starts in CWM RECOVERY and when i press "reboot system now" it enters a boot loop (the logo keeps running over and over and the phone)
before this happened i originally had the stock ROM of my cellular carrier (2.3.3
then i decided to install another rom and kernel (cyanogenmod 10) so i installed first a clean stock rom (2.3.6) via odin
and then the cyanogenmod rom and kernel (up to now its all fine)
after that i wanted to change and install other rom so i installed again the clean stock rom 2.3.6 via odin...and from then it started to boot loop.
i thought that if i will install the kernel again it will be OK ,but it wont..
and now im in the situation that i have described above..
help SOMEONE please=]
Click to expand...
Click to collapse
it is because the latest CM10 is based on a different partitioning layout than the stock one.. after flashing CM10 once when you go in a boot loop.. go to CWM recovery by using the three button combo and flash CM10 again.. . this time your rom will boot:good:
replay
ishangoyal said:
it is because the latest CM10 is based on a different partitioning layout than the stock one.. after flashing CM10 once when you go in a boot loop.. go to CWM recovery by using the three button combo and flash CM10 again.. . this time your rom will boot:good:
Click to expand...
Click to collapse
I installed the kernel and then the stock rom again but now its just bootlooping without getting load up to CWM recovery
so how can i get into CWM recovery????
(i tried VolumeUP+HOME+POWER but it just get into regular recovery...)
pull out your battery for a couple of minutes then replace battery
;hold three button forever or until it goes into recovery if that doesnt work
reflash through odin and do it again or check out darkyrom 10. re this gets flashed through odin
LCPD said:
I installed the kernel and then the stock rom again but now its just bootlooping without getting load up to CWM recovery
so how can i get into CWM recovery????
(i tried VolumeUP+HOME+POWER but it just get into regular recovery...)
Click to expand...
Click to collapse
flash darkyrom 10.2 Resurrection edition using odin.. this will give you a GB rom with root
flash CM10 through CWM recovery
reboot.. (you may not be able to boot as of now)
go to CWM recovery again using 3 button combo
flash CM10 again
reboot
this should do the trick
THANK YOU TWO
the Darkys rom 10.2 re was great --- it starts now hahah
i Will try now another rom (not cyagonmod but PilotX)
thank you very muchhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
I had installed LiquidSmooth ROM on my Samsung Galaxy Note GTN7000 a while ago. I run Philz Touch recovery version 6.0.0.1 .
When I tried flashing CM11 , I got an error something like set_metadata_recursive .. .
I googled it up, and found that I need to update my recovery. SO, i downloaded the latest version of CWM from their website and tried flashing it through the recovery. And it is resulting in a sudden shut down and then in a bootloop when switching on .
What wrong am I doing? How can I rectify this?
Flash Raw Kernek r5:
http://forum.xda-developers.com/showthread.php?t=2397000
On our device the recovery is incorporated into the kernel, never flash a recovery or kernel that isn't meant for our device.
Once you have flashed that, reboot to recovery and perform a full wipe. Then proceed with the installation of CM.
[Q&A] [RECOVERY] TWRP v2.8.0.0 by NovaFusion 20140911 ( ͡° ͜ʖ ͡°
Q&A for [RECOVERY] TWRP v2.8.0.0 by NovaFusion 20140911 ( ͡° ͜ʖ ͡°)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP v2.8.0.0 by NovaFusion 20140911 ( ͡° ͜ʖ ͡°). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
TWRP 2.8.0.0 won't start
Hello all,
I've tried to flash TWRP 2.8.0.0 from novafusion on my GT-I8190, never touched (without root or custom rom) via Odin.
It flashes ok, restarts, but when I try to enter Recovery mode, the Android stock system recovery starts.
I've did it twice: once with Odin 3.07 at PDA line, once with Odin 3.10 at AP line.
In download mode, I can see that system status is now modified from Samsung to Custom, and binary download is at 2 counts now.
Any ideas why TWRP won't start?
Thanks
EviluSH said:
Hello all,
I've tried to flash TWRP 2.8.0.0 from novafusion on my GT-I8190, never touched (without root or custom rom) via Odin.
It flashes ok, restarts, but when I try to enter Recovery mode, the Android stock system recovery starts.
I've did it twice: once with Odin 3.07 at PDA line, once with Odin 3.10 at AP line.
In download mode, I can see that system status is now modified from Samsung to Custom, and binary download is at 2 counts now.
Any ideas why TWRP won't start?
Thanks
Click to expand...
Click to collapse
I am having a very similar problem but on my cm 11 if I attempt to reboot into recovery it reboots to system and I am unable to access my TWRP installed recovery
Sent from my GT-I8190 using XDA Free mobile app
support i8190T ????
godinw183 said:
support i8190T ????
Click to expand...
Click to collapse
Yes
Sent from my GT-I8190 using XDA Free mobile app
I8200N
Hi New Macław, would it be much of an effort to make the next TWR version workable for the Galaxy s3 mini I8200N ?=?
I understand that there is a different chip set used.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access http://forum.xda-developers.com/gal...wrp-v2-8-0-0-novafusion-20140911-t2964838here -->.
Done.
Reocvery won't work
When I tried to flash the TWRP recovery on to my Samsung Galaxy S3 MINI (GT-I8200L). it wouldn't work. I used Odin. When into download mode clicked PDA put the TWRP recovery it said it was working and when my phone rebooted it said "PASS" when I got to my lock screen. But when I Went into recovery Mode I still had the same stock recovery before please help. Btw my phone is rooted with Kinguser.
Best regards,
Twisterboy
Twisterboy669 said:
When I tried to flash the TWRP recovery on to my Samsung Galaxy S3 MINI (GT-I8200L). it wouldn't work. I used Odin. When into download mode clicked PDA put the TWRP recovery it said it was working and when my phone rebooted it said "PASS" when I got to my lock screen. But when I Went into recovery Mode I still had the same stock recovery before please help. Btw my phone is rooted with Kinguser.
Best regards,
Twisterboy
Click to expand...
Click to collapse
after it shows PASS, (phone reboots) take QUICKLY out battery (prevent system from booting) now wait 10 secs, reinsert battery & reboot directly to recovery using the button combo. in some cases the recovery gets allways overwritten if u get directly into system after a flash...
Hi! I messed up a bit with the TWRP installation, I flashed the wrong file. Afterward, I managed to flash the appropriate file and the phone works perfectly, but the Samsung Galaxy logo before the boot animation is now replaced with a
"grainy" image, and it bugs me. Any ideas how to fix this?
I've a Galaxy S3 mini GT-I8190 with CM11 (latest from novafusion). It had CWM recovery and I flashed TWRP 2.8.0.0 with Odin. Starting the phone after flashing enters TWRP immediately. I also can reboot to TWRP.
But if I booted to cm11 once there is no way to get back into TWRP. I only see the Samsung logo and then a black screen. Now trying to boot the system will also lead to logo and black screen.
So the only possibility to start the system is to flash TWRP again enter it and reboot from there.
Booting and rebooting cm11 are working fine if I not tried to enter recovery before.
Do you have any suggestions to fix this behavior?
I haven't been able to flash any recovery. Is root needed? There is a CSC changer that runs when recover is started; I wouldn't mind loosing that. I am thinking boot, odin and recovery are locked. Was a good thing at one point when I flashed the wrong rom and it wouldn't boot to anything but odin and recovery. I've successfully flashed 2 different roms (except for the odin and recovery parts). The rom that failed had a recovery img in it. I've tried flashing a stock recovery followed right away with pulling the battery and then did the same with twrp several times. No change.
I just want to flash one of the 4.4.x roms. Can I still do this? I might be fine since I will always have odin(download mode) and recovery. I want a newer version of android because sound is screwed up recording videos in Instagram and Everysing. This is my daughters phone. I also want to remove some of the crapware. Clean Sweep is part of the stock rom??
How to unlock recovery?
Well I did manage to flash a rooted Rom. So I have confirmed root and did a few things that required root. It hasn't helped me flash any recovery. It and/or boot still seem locked. Is there something I can do about it now that I have root? I did try an app that claimed to be able to flash recovery, but no change.
I used a terminal app and wrote TWRP to the recovery rom location. Something like mmcblk0p21. Works. Today I will be going back to stock and hopefully recovering my efs partition so I can actually use this as a phone. I had wiped everything a few times. I still just want a rom where Instagram doesn't distort the audio or go green on video uploads.
thanksss!!
hello first off all ive rooted and installed custom roms on s3 gti9300 and s4 gt i9500 but this n7000 is a bit confusing so i rooted via odin and installed philz 5 custom recovery but when i install rom i get error 7 and have to flash back to stock 4.1.2 and also do i need to use external sd card for custom roms with n7000 as didnt with s3/4 ... any help would be great as really great as stock rom is slow as hell
02hudsond said:
hello first off all ive rooted and installed custom roms on s3 gti9300 and s4 gt i9500 but this n7000 is a bit confusing so i rooted via odin and installed philz 5 custom recovery but when i install rom i get error 7 and have to flash back to stock 4.1.2 and also do i need to use external sd card for custom roms with n7000 as didnt with s3/4 ... any help would be great as really great as stock rom is slow as hell
Click to expand...
Click to collapse
error 7 happens when your kernel/recovery does not support your rom. Use philz to enter recovery and install a raw kernel from here. Choose the appropriate kernel and flash it, reboot into recovery and you're ready to flash the rom.
AutumQueen92 said:
error 7 happens when your kernel/recovery does not support your rom. Use philz to enter recovery and install a raw kernel from here. Choose the appropriate kernel and flash it, reboot into recovery and you're ready to flash the rom.
Click to expand...
Click to collapse
witch do i download :L.. my phone wont boot it just restarts in to team win recovery project now so cant get in to philz recovery //// have i got to flash back to stock an re do all this again
AutumQueen92 said:
error 7 happens when your kernel/recovery does not support your rom. Use philz to enter recovery and install a raw kernel from here. Choose the appropriate kernel and flash it, reboot into recovery and you're ready to flash the rom.
Click to expand...
Click to collapse
just an update i may have done it its installed rom and its optimizing apps
my GT-n7000 is stuck at Boot screen after flashing the 16/3 lollipop kernel , I was at the previous kernel and ROM
I flashed the 16/3 kernel and rebooted to flash the new ROM but it doesn't boot neither open recovery
Can someone help me ? please I need the device fast
thanks