i cant figure this out at all for the life of me
i have done this since cm7 i can install every build up to cm-10.1.3-RC2-galaxysmtd and gapps-jb-20130812-signed
soon as i try to do any of the cm-10.2 builds i get stuck in the boot animation loop
then i restore with odin, install cwm and reinstall 10.1.3-RC2 and im back working fine again
someone please point me in the right direction
do i have to partition it myself larger or does the rom do this as i have read and done the double run to install and supposedly setup the 600mb partition from the 400 used before 10.2
my cwm is 6.0.3.6 i believe think i read somewhere this may need an update to 6.0.4.0 to work for 10.2 how would i do this with odin or thru the rom my vol+ is broken so i cant access the recovery with that method
thanks guys
downloaded CF-Root-XX_OXA_JW4-v4.4-CWM3RFS and flashed it in odin and booted cwm 6.0.4.4 wiped everything as usual installed 10.2 and gapps and voila its working on 10.2 now hopefully this helps anyone else with the same issues
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.
I tried an upgrade to C-ROM with its TWRP backup. I want to go back to CM11 and I have two CWM backups.
C-ROM grabs a reboot to Recovery and shows a screen with options, none of which is useful to me.
ROM manager won't install as incompatible.
Please tell me what to do?
Richard
Flash CM11 nightly and after reboot into the OS, reboot recovery and restore your backup. Optionally, you can just flash the CM11 stock kernel and reboot into its CWM recovery and restore your backup then.
Recovery on i9000 is part of the kernel, so you can totally forget ROM Manager app for flashing the recovery.
tetakpatalked from Nexus 7 flo
Thanks, I hope
tetakpatak said:
Flash CM11 nightly and after reboot into the OS, reboot recovery and restore your backup. Optionally, you can just flash the CM11 stock kernel and reboot into its CWM recovery and restore your backup then.
Recovery on i9000 is part of the kernel, so you can totally forget ROM Manager app for flashing the recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks, that sounds easy. I considered doing something like that but lacked confidence to do it.
Richard
Questions about Recovery
Richard Hallett said:
Thanks, that sounds easy. I considered doing something like that but lacked confidence to do it.
Richard
Click to expand...
Click to collapse
Hi tetapetak
I get trapped in the TWRP menu screen whenever I try to boot into Recovery. I tried Install and went to the CM zip file and was able to get to the com folder but didn't know where to go next. Should I go deeper.
While browsing I found an app called Flashify. Would that help"
I also found a youtube video Change Custom Recovery from TWRP to ClockworkMod on HTC One that sounded good but Galaxy and HTC are different.
I would have to chose between TWRP for Samsung Galaxy S2 Exhilarate SGH-i577 or TWRP for Samsung Galaxy S3 (Canada) if I wanted to follow the directions.
Richard
Richard Hallett said:
Hi tetapetak
I get trapped in the TWRP menu screen whenever I try to boot into Recovery. I tried Install and went to the CM zip file and was able to get to the com folder but didn't know where to go next. Should I go deeper.
While browsing I found an app called Flashify. Would that help"
I also found a youtube video Change Custom Recovery from TWRP to ClockworkMod on HTC One that sounded good but Galaxy and HTC are different.
I would have to chose between TWRP for Samsung Galaxy S2 Exhilarate SGH-i577 or TWRP for Samsung Galaxy S3 (Canada) if I wanted to follow the directions.
Richard
Click to expand...
Click to collapse
Don't worry mate, you will get your phone working. You can not follow the threads for other phones. HTC has separately flashable recovery, unlike the i9000 which uses the same partition for recovery and kernel. That is the reason why i9000 gets easier light-bricked, because as soon as the kernel doesn't boot also the recovery mode often won't work anymore.
The most reliable way to unbrick, tough bit longer one, is to flash a stock firmware with Odin. For downgrading to 2.3.x from 4.3+ roms using the PIT file with repartition is obligatory. So as you use KitKat (and other system partition sizes than stock) it would be easier and faster to flash just a kernel that will boot.
So, how is the situation exactly now: do you get just TWRP recovery splash screen but can not enter it? If so, please flash in download mode with Odin v.1.82 or v.1.83 the Semaphore kernel v3.4.3 with unchecked auto-reboot and unchecked re-partition (use tar file under PDA in Odin). Then turn off and reboot into the recovery with 3-buttons combo.
You will possibly can restore whole CM11 backup with Semaphore recovery if you have used CM11 stock kernel to create backup. I am not sure for that, but what would ceirtanly work would be to wipe data, cache, dalvik cache and system, to flash CM11 nightly and then reboot once into the OS and reboot recovery to restore nandroid backup.
tetakpatalked from Nexus 7 flo
Progress report
tetakpatak said:
Don't worry mate, you will get your phone working. You can not follow the threads for other phones. HTC has separately flashable recovery, unlike the i9000 which uses the same partition for recovery and kernel. That is the reason why i9000 gets easier light-bricked, because as soon as the kernel doesn't boot also the recovery mode often won't work anymore.
The most reliable way to unbrick, tough bit longer one, is to flash a stock firmware with Odin. For downgrading to 2.3.x from 4.3+ roms using the PIT file with repartition is obligatory. So as you use KitKat (and other system partition sizes than stock) it would be easier and faster to flash just a kernel that will boot.
I would be happy to get to a stock firmware. But Odin is not working well with the phone, more below.
So, how is the situation exactly now: do you get just TWRP recovery splash screen but can not enter it? If so, please flash in download mode with Odin v.1.82 or v.1.83 the Semaphore kernel v3.4.3 with unchecked auto-reboot and unchecked re-partition (use tar file under PDA in Odin). Then turn off and reboot into the recovery with 3-buttons combo.
I don't get any recovery screen now. All I get is the Samsung page.
You will possibly can restore whole CM11 backup with Semaphore recovery if you have used CM11 stock kernel to create backup. I am not sure for that, but what would ceirtanly work would be to wipe data, cache, dalvik cache and system, to flash CM11 nightly and then reboot once into the OS and reboot recovery to restore nandroid backup.
Currently I cannot do all that stuff.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
tetakpatak said:
Don't worry mate, you will get your phone working. You can not follow the threads for other phones. HTC has separately flashable recovery, unlike the i9000 which uses the same partition for recovery and kernel. That is the reason why i9000 gets easier light-bricked, because as soon as the kernel doesn't boot also the recovery mode often won't work anymore.
The most reliable way to unbrick, tough bit longer one, is to flash a stock firmware with Odin. For downgrading to 2.3.x from 4.3+ roms using the PIT file with repartition is obligatory. So as you use KitKat (and other system partition sizes than stock) it would be easier and faster to flash just a kernel that will boot.
So, how is the situation exactly now: do you get just TWRP recovery splash screen but can not enter it? If so, please flash in download mode with Odin v.1.82 or v.1.83 the Semaphore kernel v3.4.3 with unchecked auto-reboot and unchecked re-partition (use tar file under PDA in Odin). Then turn off and reboot into the recovery with 3-buttons combo.
I did this and when Odin said it was a success, the phone said it was still working. I gave up after 15 min. and tried the booting. A recovery boot or normal boot just gives me the Samsung page. The download boot gives me the still working screen. So phone still thinks it is downloading. I should mention that I was unable to get in to developer mode using tap 7 times. I read that developer mode is important with Odin
You will possibly can restore whole CM11 backup with Semaphore recovery if you have used CM11 stock kernel to create backup. I am not sure for that, but what would ceirtanly work would be to wipe data, cache, dalvik cache and system, to flash CM11 nightly and then reboot once into the OS and reboot recovery to restore nandroid backup.
I'd like to do that.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks for your help. I need more.
Richard
Good progress, almost there.
Richard Hallett said:
Thanks for your help. I need more.
Richard
Click to expand...
Click to collapse
Things are going well, not perfect but well. That sticking is download position was not a problem. You just have to download something else that will complete. To use Odin (Kies didn't work) I needed a tar of a system. I tried a Samsung JB that I found on SamMobile, using Odin. It loaded are booted when complete. Got the Samsung screen and those wavy lines with music but nothing more. Tried the Recover button trick and it worked. So the phone is fixed except for picking up a tar to start and then I can recover a CM11 backup of mine.
I think I need a KK tar to get the CM11 backups to work. I did try restoring one and got an error saying that "this package is for "galaxys2.i9100 .." devices; this one is a "", There was nothing between the quotes. The tar system I used was a JB so that may be the problem.
So all I need to know of a KK tar or I could try changing the tar to a zip to please Odin.
Thanks again for your help tetapetak
Richard
Are you trying to flash a i9100 rom onto i9000? That won't have a happy end.
Richard Hallett said:
. I tried a Samsung JB that I found on SamMobile, using Odin.
Click to expand...
Click to collapse
No stock JB exists for the i9000, the last firmware was GB 2.3.6
tetakpatalked from N7100
Typo not i9000
tetakpatak said:
Are you trying to flash a i9100 rom onto i9000? That won't have a happy end.
No stock JB exists for the i9000, the last firmware was GB 2.3.6
tetakpatalked from N7100
Click to expand...
Click to collapse
That was a typo. I meant i9100 international M
More than a typo I just noticed I in the wrong group. Sorry, but I have found it to be very useful.
Hey, I just tried rooting my Galaxy Note 5 from Bell, model SM-N920W8, and was unable to boot into recovery when using arter's Philz recovery (though odin reported the flash successful). I tried TWRP afterwards which works as a recovery, however afterrwards my OS stopped booting, resulting in a bootloop before the boot animation. even when trying to flash a new ROM (VIPER 1.4) it bootloops and trying to flash Philz through a zip file also breaks recovery. Is there anything I am doing wrong?
Im going to try another rom, but any suggestions or knowledge as to why i can't get CWM or my System to boot.
Edit: Tried the SpaceX kernel and it seems to be working. Guess arter's kernel and recovery just wont play nice.
Hello, just bought an used i8190. Since last friday i have been trying to flash a custom recovery on this phone via Odin, but after i flash it returns to the default recovery on next boot.
Yes, i have unchecked the "Auto-reboot" option on Odin. I turn off the phone and then manually enter recovery but with no results. I rooted the phone pretty easily and installed both TWRP and CWM apps to flash from android, but they don't work either (twrp crashes always and CWM just gives me an error.
Mi baseband model is XXAll2
kernel is 3.0.31 [email protected] (root name seems weird)
I searched the forum and found similar cases with the baseband, but even so i haven't found a concrete solution.
I even flashed a new pre-rooted rom from this thread: https://forum.xda-developers.com/showthread.php?t=2030282
Mi compilation number has changed to XXAMG1 but the baseband remains the same. I can't flash a recovery whatever i try.
I hope someone can give me an answer, cause i really want to use this phone feautures to it's fullest
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Glass_Arcana said:
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Click to expand...
Click to collapse
Flash the stock rom as it will fix bootloops and bricked devices. Make sure to have the right ROM and flash it with Odin. The os may take longer on first boot and make sure to factory reset it as data may cause bootloops, then try flashing the recovery.
I flashed twrp 3.1.1 through Odin