No more bootloops on custom recoveries!!! Tested onT110, but should work in T111 too. feedback would be great
Kernel sources: http://github.com/pazos/android_kernel_samsung_goyawifi
Device tree: http://github.com/pazos/android_device_samsung_goyawifi (not uploaded yet )
Credits:
@ketut.kumajaya for the initial kernel base for lt02
@gr8nole for inital goyawifi device tree to build TWRP
all people sharing code here, in xda
Thank you so much for your work!
:cyclops: !!! Of course If something crashes I won't pay you for any damage :cyclops:
Hi paziusss,
I am on the case of recovery bootloop after flashing CWM.
Thanks for this work but how does it work ? How to use the files on the link ?
Many thanks for your answer.
EDIT : Well, I will answer myself telling my solution
1. flash cmw with odin
2. reboot into recovery and flash twrp.zip
3. reboot recovery
4. Flash root zip
5. reboot system ..... no more bootloop
Flashed this with Flashify and it has fixed my bootloop issue.
Sent from my SM-T110 using Tapatalk
Working well, tested on 2 tablets, thanks.
I'm glad it worked for you
I just noticed some non-critical errors:
- it doesn't backup boot.img
- wipe preload partition does not work because of Selinux
- screen timeout (sometimes) puts the system in unresponsive state -> Disable it!
- Missconfigured "screen_brightness"
Everything else should work as expected.
In the next days I'll upload a new version to fix above errors and make an odin installable tar.md5
Next version will be shipped without SELinux, because we don't need that until samsung releases 4.4 for the Tab3 lite (or someone ported CM11 with Selinux support)
Feedback, as always, is _VERY_ welcome !!!
will it work on sm t 111 tab india ?
sushil888 said:
will it work on sm t 111 tab india ?
Click to expand...
Click to collapse
Yes, it should work, but I didn't test
ok
paziusss said:
Yes, it should work, but I didn't test
Click to expand...
Click to collapse
ok
boot loop gone on T110 ?
paziusss said:
In the next days I'll upload a new version to fix above errors and make an odin installable tar.md5
Next version will be shipped without SE Linux, because we don't need that
Click to expand...
Click to collapse
Wow! Does your kernel mean T110 users have a custom recov which does not bootloop anymore?
That would be awesome! Fantastic break thru on T110 ! :good:
no stock ASR install
this recov does not simply install via stock ASR on my T110 (reboot, "missing signature").
I guess one has to flash PhilZ first using ODIN, and only then install this recov from within PhilZ
Uploaded a new version! for both Odin and recovery!
Tested last two weeks and everything works well!!
Have fun
brief install how-to much appreciated
paziusss said:
new version! for both Odin and recovery!
Have fun
Click to expand...
Click to collapse
people would have more fun if you dropped 1 or 2 lines about how to install the NON-ODIN version.
does one have to flash CWM with ODIN prior to using that ?
So that stock users should go for the ODIN version straight away cuz it saves install time?
---------- Post added at 04:09 PM ---------- Previous post was at 04:05 PM ----------
Also:
is this TWRP permanent and does not exhibit the dreaded bootloop? re-edit : YES this TWRP exhibits NO bootl loop acc. to DEV.
i.e. T110-users finally do indeed have a WORKING CUSTOM RECOV ? re-edit: YES ! FINALLY THE BREAK THROUGH IS THERE !!
that would make you the KING DEV of planet-T110 ! :good:
excellent !
:laugh::laugh::laugh:
smashing ! for us T-110 users the day has finally come !
KING of "planet T-110", the dev Sir paziusss
gave us a non-bootlooping custom recovery !
we now can handily
root (straight from within TWRP, works like a charm)
flash customs roms (well there are only 2 for T110: Criskelo and stock debloated)
above all: make nandroid backups & restore them
just flash the recov with ODIN 3.09, see pic attached :
http://forum.xda-developers.com/showpost.php?p=60707541&postcount=2
in TWRP, if u do a "advanced wipe" and wipe "internal storage" too (all is tagged except "MicroSD"), then that will kill the bloody bloatware installer that will otherwise spam ure storage with sh!tty apk's after fresh stock ROM or Criskelo ROM install (as part of most branded versions) .
I guess u get the bloated stuff back when flashing full OS with ODIN.
I found however, that Criskelo deletes TWRP. You would have to reinstall TWRP. Instead I chose to kill Criskelo which was OK but slightly bloated, I felt.
I run this TWRP , no prob so far. excellent T110 feel.
recovery.fstab safestrap
Code:
[FONT=Courier New]/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
#/misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/efs emmc /dev/block/platform/msm_sdcc.1/by-name/efs flags=backup=1;display=EFS
/external_sd vfat
/dev/block/mmcblk1p1
/dev/block/mmcblk1
/usb-otg vfat
/dev/block/sda1
/dev/block/sda flags=removable;storage;display=USB-OTG[/FONT]
https://raw.githubusercontent.com/T...samsung_lt02ltetmo/android-4.4/recovery.fstab
fstab of the lt02ltetmo, the expensive NON-LITE Tab 3 7"
it may apply to our T110 as well.
what about safestrap ?
http://blog.hash-of-codes.com/how-to-safestrap
http://forum.xda-developers.com/tags.php?tag=safestrap
take abow
:angel: ur great
nodobt abt that ur something special dev...
feeling happy for 110 users
njoy
Am I the only one confused as to why this is such a big deal? I've been using the 2.7.0.1 version of TWRP for the T110 from here for over a year and have yet to experience a bootloop or problem of any kind.
funny
Dudash said:
Am I the only one confused as to why this is such a big deal? I've been using the 2.7.0.1 version of TWRP for the T110 from here for over a year and have yet to experience a bootloop or problem of any kind.
Click to expand...
Click to collapse
well did anyone report successful use of that recov earlier ?
clearly PhilZ recov is bootlooping and no one suggested a replacement. :crying:
Dudash said:
Am I the only one confused as to why this is such a big deal? I've been using the 2.7.0.1 version of TWRP for the T110 from here for over a year and have yet to experience a bootloop or problem of any kind.
Click to expand...
Click to collapse
You're right here. Bootloop problem only happens if you tell your device to go to recovery (via adb reboot recovery, or with programs like quickboot). If you boot in recovery with buttons combo you'll never see a bootloop cause the tablet doesn't know it boots recovery. The only real scenario you'll find a bootloop is after a factory reset, because It will trigger a reboot-recovery like command and custom recoveries don't handle this. I didn't try to change this from userspace (I know some phones have a /misc partition with BCD data inside, but Tab3 don't). Instead I built a kernel from stock sources which triggers "recovery-done" at every reboot.
Related
Hey, I bring to you the first Clockworkmod Recovery or commonly known as CWM for your N5100 and N5110. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods. *Now known as Advanced CWM or aCWM. Thankyou to 'xperiacle' and 'GSLEON3' for giving me the stock recoveries and kernels for N5100/10, so I could start off with my work.
Works perfectly now. OP will only be updated with stable releases, everything else will be floating around the thread.
I have provided the stock recovery if you encounter any issues, you can always flash back.
Featues:
Most things you would expect from stock CWM
EFS backup / restore
Removed option to: report error / show log / testkeys
More to come...
Downloads:
Use this if you are having problems with your SDCard. (Mount / Backup / Restore)
N5100 / N5110
Stable Release #1: ODIN | ZIP
Stock Recovery: http://d-h.st/tHx
N5120
Stable Release #1: ODIN
Stock Recovery: http://d-h.st/51H
Changelog:
Code:
[I][U]Stable Release #1[/U][/I]
Added reboot menu (rom, download, recovery)
Advanced CWM = aCWM
Code:
[I][U]Experimental #6[/U][/I]
Working EFS backup / restore under 'advanced' tab
Removed keytest / report error / show log options
Custom recovery, no more to be called 'stock' CWM, more device specific features to be added
N5120 support
Fix permissions now directed to /sdcard/.android_secure
Cleaned up some code for flashing zips
[I][U]Experimental #5[/U][/I]
[COLOR="Red"]REMOVED DUE TO ISSUES[/COLOR]
Touch recovery (reimplemented)
Universal for 5100 / 5110
Fixed up some mount lengths
Fixed up init.rc
[I][U]Experimental #4[/U][/I]
Display issues fixed
[I][U]Experimental #3[/U][/I]
Built again with fresh tree - n5110
(info: skipped for n5100)
[I][U]Experimental #2[/U][/I]
Touch Input excluded (temp)
kernel built from source with dancing cwm patch
[I][U]Experimental #1[/U][/I]
Public release
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your n5100. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'xperiacle' for giving me the stock recovery and boot.img. Flash with Odin
This has not been tested by me and is still experimental. I hold no responsibility for any
problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $$$.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back.
Downloads:
CWM Recovery: http://d-h.st/rDv
Stock Recovery: http://d-h.st/tHx
Changelog:
Code:
[I][U]Release #1[/U][/I]
Public release
Click to expand...
Click to collapse
Thanks now we need one for the N5110.
rfb813 said:
Thanks now we need one for the N5110.
Click to expand...
Click to collapse
Just need to check if this works properly. If yes, then n5110 is up next
emwno said:
Just need to check if this works properly. If yes, then n5110 is up next
Click to expand...
Click to collapse
Thanks!
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Southrice said:
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Nothing to be credited for, until the device boots to CWM
How do you flash this custom recovery with ODIN?, what version?, thanks
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
How did you flash, Odin?
brosenz said:
How did you flash, Odin?
Click to expand...
Click to collapse
I added the zip to the pda area and flash Odin v3.07
I installed the image with ADB.
put the recovery image on the sdcard mount or ext sdcard mount
ADB to the note 8.0
su to root
go to your image directory
dd if=xxx.img of=/dev/block/mmcblk0p6
switch back to the note and reboot directly to recovery (i used goomanager)
it does boot the first time - but it is jittery and in landscape mode.
after the first system boot- the device wipes it and goes back to stock recovery.
I have seen this with other stock android devices- sometimes there
is a script that gets triggered on boot to remove any custom recoveries.
I did clear the recovery check from CWM - but it was hard to see because of the
landscape mode and the screen jumping around.
It looks like the full backup is working- now I wonder what ROM will be close enough
to the 8.0 to try flashing.
Speedy Gonzalez said:
I added the zip to the pda area and flash Odin v3.07
Click to expand...
Click to collapse
Any idea why it didn't flash with Odin?
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
Found this Q&A in the Note 10.1 rooting guide in RootGalaxyNote.com:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
This may have been the problem.
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
rfb813 said:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
Click to expand...
Click to collapse
Those having issues, try that ^^^
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
Yeah, But i'd like to keep, just incase something goes insanely wrong. The stock recovery.img is provided, you can always flash back it something goes wrong. And i am readying up TWRP, may need you to pull some logs if it doesnt boot
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=GT-N5100
http://samsung-updates.com/device/?id=GT-N5110
I will be releasing a full Note 8.0 Toolkit today or tomorrow with support to rename the stock recovery restore files so that custom recovery isnt overwritten after flashing. If anyone wants to help test please email me at [email protected]
Mark.
Attached is a tar of recovery.log pulled with ADB while booted to CWM.
The display goes to landscape on boot - and the fonts seem extra large.
When the vol up/down navigates the screen jumps and you can't see the
highlighted option.
It is usable with trial and error if you know the order of the CWM menus and
use the vol up/down and power to navigate.
emwno said:
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Click to expand...
Click to collapse
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
I tried changing orientation before boot - it always goes to landscape.
I attached 2 images - one is the display after the first CWM boot.
The second is after pressing Vol Up to navigate to the 2nd menu option.
I have seen jumpy CWM presentation like this on some smaller screens like the
Sony Xperia 2011/2012 phones.
emwno said:
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
Click to expand...
Click to collapse
PLEASE!
Before you do anything take a backup of your EFS, use this easy one click tool.
I'm not responsible for your bricked device!
Note:
I recommend the ported PhilZ recovery over this one as it includes EFS backup and many other features.
CivZ Touch Recovery REV1.1 CWM 6.0.4.4. (Latest)
Touch driver fix (also for aroma) thanks to nickdollahz
Features of this plain recovery:
Backup/restore to internal and external SD
Wipe menu's
Format data/media = get rid of every thing = game data, pictures, movies.....
and all the normal stuff of the stock CWM.
GT-N5100 and 5110 : CivZ-Touch-6.0.4.4-Odin-5110_5100-REV1.1.tar ; CivZ-Touch-6.0.4.4-CWM-Package-5110_5100-REV1.1.zip
Odin flashable package = if you are on stock recovery you need this.
cwm flashable package = Only works when you are on a custom recovery
GT-N5120:CivZ-Touch-6.0.4.4-Odin.-5120-REV1.1.tar ; CivZ-Touch-6.0.4.4-CWM-Package-5120-REV1.1.zip
Odin flashable package = if you are on stock recovery you need this.
cwm flashable package = Only works when you are on a custom recovery
Changelog:
21/10/2013
New touch recovery released based on CWM 6.0.4.4
Fixed touch driver thanks to nickdollahz.
Also works in aroma but is not optimal in long lists.
Hardware buttons also work.
22/10/2013: CivZ Touch Recovery REV1.1
Rebuild kernel from samsung update2 and changed touch config to be less sensitive in aroma long list scrolling.
Exfat cards supported - I hope.
Click to expand...
Click to collapse
I leave the older version 6.0.3.2 no touch available.
THANKs
works fine with my N8 GT-N5100
I tested bkup to SDCard ... OK
can i flash this cwm6 package with stock e3 recovery..?
Sent from my GT-N5100 using XDA Premium HD app
desire91 said:
can i flash this cwm6 package with stock e3 recovery..?
Sent from my GT-N5100 using XDA Premium HD app
Click to expand...
Click to collapse
No you can't, you'll need odin to flash any custom recovery first. The stock recovery will just report a signature error.
ok..thanks
Sent from my GT-N5100 using XDA Premium HD app
screen malfunction at startup
I flash this CWM over my N5120,
I am not sure if I get anything wrong in the procedure.
However, everytime I start the machine. It get a screen malfunction.
Cwm and download mode work fine.
Then, I decided to flash back N5120 rom from sammobile thr. odin.
Screen malfunction still exist and I found out that snote will FC no matter which version of rom I flash.
Anyone has any idea on the issue?
How should I fix it?
Thank you very much for help.
May i know how you install this? Newbie here
superng888 said:
May i know how you install this? Newbie here
Click to expand...
Click to collapse
Um, that s a long story.
First, I flashed CWM6.03.2.
And I found a bit strange at boot up. The screen blink at bootup.
Then, I tried Custom CWM 6.x - N5100 / N5110 / N5120 - Ex#6.
I also restored the rom from sammobile at the same time.
Screen malfunction at boot.
But, everything works fine, except 2 things.
1) CWM factory reset didn't work.
2) Snote FC
I try every cwm in the forum. Nothing change until.......
I flashed PhilZ 5.03.0 and try something like "clean up to install rom" or "prepare to install clean rom" inside the recovery.
After reboot, my machine bricked.
DaDaDa, I should be the first one to brick N5120 in xda because I flashed everything without thinking.
Right now, when i press down+power right now, the machine directly jump to download mode without asking.
However, odin wont detect.
It is not the connection issue. It can connect my note2.
I am now waiting usb jig from ebay and hope THE MIGHTY JIG will at least bring me the real download mode.
emwno said I might have soft bricked the bootloader.
I will keep posting on final result about jig, in case some newbie like me flash everything they saw.
N5100, stock N5100XXBMD1_N5100XEZBMC3_N5100XXBMC8, rooted by framaroot, recovery applied and seems working. Backup done by EFSPro, donation sent (TID:*644C). Terminating connection.
EOF
Press, hold, shake, upside down???
Okay...here's an extremely stupid question: How do you boot into CWM recovery manually on the Note 8? I've tried every button combo I can think of and haven't been successful.
EDIT: Nevermind! Got it. My bumper case must have been interfering with the volume up button. Duh!
Added version for the GT-N5120 , tested by AndyGod and reported to be working.
363 downloads and only 7 people find it worth to click the thanks button? Strange?
Works well on my n5100
Thanks Civ
Envoyé depuis mon GT-N5100 avec Tapatalk
sisterchick said:
Okay...here's an extremely stupid question: How do you boot into CWM recovery manually on the Note 8? I've tried every button combo I can think of and haven't been successful.
EDIT: Nevermind! Got it. My bumper case must have been interfering with the volume up button. Duh!
Click to expand...
Click to collapse
LOL!
Great job Civato, work good, and i like full backup
I'm on stock rooted using framaroot. Put my note in download mode, and flashed the tar file through odin. Now, I can reboot into recovery but I can't access anything on my internal storage. Any pointers on what I could be doing wrong? Do I need an external sd card for flashing/nandroid backups etc?
Edit: Looks like its because I have the note encrypted. Will decrypt and then try again.
Is there any way to make it work on portrait mode???
by the way, nice job mate!!!
Can I use mobile odin to install this?
a few folks have, but there is no guarantee that it will work for everyone...
I was able to use it for twrp a few days ago, but didnt try CWN..
wase4711 said:
a few folks have, but there is no guarantee that it will work for everyone...
I was able to use it for twrp a few days ago, but didnt try CWN..
Click to expand...
Click to collapse
Did you use the recovery or pda slot of mobile Odin?
i dont recall Mobile odin asking you for a "slot" choice; using "regular" Odin, PDA slot would be the proper choice..
here is chainfires post explaining it..
http://forum.xda-developers.com/showpost.php?p=41744001&postcount=2
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
Lets first understand,
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
Instructions :
Download compatible ROM
Download FormatPartitions.zip
Download "special" TWRP for All-F2FS: openrecovery-twrp-2.7.0.0-mako-All-F2FS.img
(This is different for that of simply F2FS)
Copy FormatPartitions.zip and ROM on Phone
Flash "special" TWRP with Fastboot
Flash FormatPartitions.zip with new Recovery
Reboot Recovery
Flash ROM with new Recovery
(Flash GApps with new Recovery)
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
Note : If you already on F2FS directly flash the zip and then Supersu from below link
Tested it..
All working fine..
Need to flash Supersu to retain root..
Downlaods
Link : Flashable Zip Folder - All Files
or
Flashable Zip - ROM
Mirror Link :
http://goo.gl/oQL9uD
Supersu : http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
Wifi Fix : Wifi Fix
F2FS 4.4.3 Kernel : d-h.st/t34
Credits :
@is0l4ted - creating the F2FS version
@My Nexus 4 whatsapp group members..
@Rohit02(Me)
@CallMeAldy : Wifi Fix
Changelogs :
2014/06/03 : Initial Release
2014/06/04 : Fixed bootoop for some users. Fix zip included in the new link. (Old link removed)
Rohit02 said:
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
@My Nexus 4 whatsapp group members..
Click to expand...
Click to collapse
There's a Nexus 4 WhatsApp group?
Sent from my Nexus 4 using XDA Free mobile app
Rohit02 said:
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
Tested it..
All working fine..
Need to flash Supersu to retain root
Click to expand...
Click to collapse
I'm on stock with root, recovery and Xposed. Can I just flash the zip and root again without lose anything?
is there a big difference in speed with F2FS? any problems??
thx
Gr8 work @is0l4ted and @Rohit02 and all the Whatsapp Group members !! Really short on time but if possible will try flashing it tomm evening !!
ronakchavan said:
There's a Nexus 4 WhatsApp group?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm yes an amazing group
ttheodorou said:
is there a big difference in speed with F2FS? any problems??
thx
Click to expand...
Click to collapse
Many threads out there about f2fs its advantages and disadvantages !! Its faster in opening apps and boot times and improved io performance especially on dalvik !!
NABENDU1 said:
Many threads out there about f2fs its advantages and disadvantages !! Its faster in opening apps and boot times and improved io performance especially on dalvik !!
Click to expand...
Click to collapse
so in short it is a good upgrade for the phone. i think i will try it at some point
ok I flashed without wipe and now it's in bootloop. Uff I don't want to wipe everything
CWM ?
Is it compatible with TWRP only or can I flash it via CWM ?
Sorry Bro
gajira said:
ok I flashed without wipe and now it's in bootloop. Uff I don't want to wipe everything
Click to expand...
Click to collapse
Sorry Bro for the inconvenience.. here is the fix for your problem hope you didn't wiped again!!!
Hit Me to fix bootloop!! or Me!!
---------- Post added at 02:09 AM ---------- Previous post was at 02:03 AM ----------
spfc_jcp88 said:
Is it compatible with TWRP only or can I flash it via CWM ?
Click to expand...
Click to collapse
Only TWRP F2FS Version. To confirm that the back button on TWRP should be red in color.
is0l4ted said:
Sorry Bro for the inconvenience.. here is the fix for your problem hope you didn't wiped again!!!
Hit Me to fix bootloop!! or Me!!
---------- Post added at 02:09 AM ---------- Previous post was at 02:03 AM ----------
Only TWRP F2FS Version. To confirm that the back button on TWRP should be red in color.
Click to expand...
Click to collapse
thanks, I had a nandroid backup
Maybe that's the problem, I need a F2FS TWRP.
OP updated..
Enjoy
Can't seem to get my wifi working :/ Installer says it should be activated to view networks, but i cant activate it. If i skip the first install screen where you need to log into your google account etc, and then try to activate wifi in the settings menu nothing happens when i flip the switch :/
Did a clean install multiple times, but it just keeps on not working any fixes for this?
mumaster20 said:
Can't seem to get my wifi working :/ Installer says it should be activated to view networks, but i cant activate it. If i skip the first install screen where you need to log into your google account etc, and then try to activate wifi in the settings menu nothing happens when i flip the switch :/
Did a clean install multiple times, but it just keeps on not working any fixes for this?
Click to expand...
Click to collapse
Same here. Cannot activate wi-fi.
Can I have to install the new radio?
sychim said:
Same here. Cannot activate wi-fi.
Click to expand...
Click to collapse
flash new modem and baseband. If you change to the new android version google provides new binaries. If you haven't then maybe you're wifi won't work. Look in general section for modem baseband flashable.zip
or here:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
carepack said:
flash new modem and baseband. If you change to the new android version google provides new binaries. If you haven't then maybe you're wifi won't work. Look in general section for modem baseband flashable.zip
or here:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
Click to expand...
Click to collapse
Already got the new .02 baseband installed :/
To install this "special" recovery, which one of these commands is right?
Code:
fastboot flash boot filename.img
OR
Code:
fastboot flash recovery filename.img
Many thanks before...
omegahanggara said:
To install this "special" recovery, which one of these commands is right?
Code:
fastboot flash boot filename.img
OR
Code:
fastboot flash recovery filename.img
Many thanks before...
Click to expand...
Click to collapse
fastboot flash recovery filename.img
is the right way...
carepack said:
fastboot flash recovery filename.img
is the right way...
Click to expand...
Click to collapse
You're my hero.... :highfive:
omegahanggara said:
You're my hero.... :highfive:
Click to expand...
Click to collapse
no problem man
Hi Guys. short (and maybe dumb) question but i have to be sure before messing up the phone of my friend.
I would like to flash CM11 nightlies with clockworkmod on a Samsung Galaxy Note GT-N7000.
I have read several tutorials for flashing the GT-N7000 and i'm not sure which is the best way to do it.
It is neccesary to update or change the (current stock) kernel? Or is it possible to just copy the recovery and ROM to the SD card, boot into download mode, install from there?
Sorry i only have experience with flashing my HTC One X.
Thanks in advance,
Greetings
I am in the same possition. A friend of mine wants to help him install a custom rom to his n7000.
He has the stock samsung rom and the phone is LAGGY!!
I only have experience with flashing cm11 to my own galaxy s3 with philz touch recovery.
I am reading for 4 hours now and i am lost...
Should i only use TWRP?
but twrp has a version only for cm 10...(i havent found by searching any cm11 twrp version for n7000)
Should i use cm 10 then and all is ok??
Thanks a lot
I am reading things about installing kernel for recovery (philz touch)
After installing that, its just wipe data / cache and install Rom from Zip.
Im still bit confused about the rooting process -> Trough Zip or trough Odin.
I hope some1 can help me.
First you need root. Then you can flash a custom rom.
To root your device tgere a several ways possible. All written here in sticky threads.
Easy way via Philz Kernel. You will get custom recovery and root in in step. What Rom is currentky installed? Last five digits are enough.
User_99 said:
First you need root. Then you can flash a custom rom.
To root your device tgere a several ways possible. All written here in sticky threads.
Easy way via Philz Kernel. You will get custom recovery and root in in step. What Rom is currentky installed? Last five digits are enough.
Click to expand...
Click to collapse
Stock rom is currently installed. I uploaded a picture with the specs within an attachment
Search for XXLTA Kernel in PhilZ thread and flash this one. All written in PhilZ thread. After that take your new Rom an follow the instructions in the thread again. For CM 11 you need also Raw4 kernel first. Only after that flash the custom rom. But that's all written 100000 times here....
User_99 said:
Search for XXLTA Kernel in PhilZ thread and flash this one. All written in PhilZ thread. After that take your new Rom an follow the instructions in the thread again. For CM 11 you need also Raw4 kernel first. Only after that flash the custom rom. But that's all written 100000 times here....
Click to expand...
Click to collapse
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
hosseltietjes1990 said:
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
Click to expand...
Click to collapse
you also need gapps
eveles said:
you also need gapps (and maybe for later use one custom kernel )
Click to expand...
Click to collapse
Yes i know, to install play store and other applications. But for the flashing part, that is enough right? The kernel, ROM and Philz Recovery?
hosseltietjes1990 said:
Yes i know, to install play store and other applications. But for the flashing part, that is enough right? The kernel, ROM and Philz Recovery?
Click to expand...
Click to collapse
yes that is enough but gapps are usually installed right after the ROM so having it together with the other files is a good idea.
- transfer ROM, Kernels to internal or external SD.
- flash Philz JB kernel compatible with your device [ follow the instruction in Philz kernel thread on how to flash with no yellow triangle ] and reboot then verify that root is working (just try and give a file explorer root access or install an app like root checker from playstore)
- Once root is verified reboot to recovery (you should now be in philz touch recovery) I recommend you take a nandroid backup but the choice is yours
- Wait for the backup to complete or if you are skipping backup then
a) wipe data factory reset
b) wipe cache
c) format system by going into mounts and storage
d) wipe dalvik cache
- flash raw kernel and reboot recovery.
- Now in TWRP recovery (you can again choose to do steps a to d which is totally optional) find and flash the ROM you want
- flash gapps
- reboot
That should do it
and now just in case you don't like what you flashed you can always go back to your ROM if you took a nandroid backup as suggested in the installation steps
hope it helps
Restore instructions :
I don't know if CWM recovery takes he same path to backup as Philz recovery but if it does it pretty simple
- just reboot to recovery and do the steps a to d from the above installation steps and restore backup
But in case you are not able to find backup file in CWM then do this
- reboot to recovery
- flash Philz kernel (same one you flashed during installation )
-go to advanced and select "reboot recovery"
- now you should be in Philz recovery again
- do steps from a to d again and restore
Simple
REVENGE SOLVES EVERYTHING
tysonraylee said:
yes that is enough but gapps are usually installed right after the ROM so having it together with the other files is a good idea.
- transfer ROM, Kernels to internal or external SD.
- flash Philz JB kernel compatible with your device [ follow the instruction in Philz kernel thread on how to flash with no yellow triangle ] and reboot then verify that root is working (just try and give a file explorer root access or install an app like root checker from playstore)
- Once root is verified reboot to recovery (you should now be in philz touch recovery) I recommend you take a nandroid backup but the choice is yours
- Wait for the backup to complete or if you are skipping backup then
a) wipe data factory reset
b) wipe cache
c) format system by going into mounts and storage
d) wipe dalvik cache
- flash raw kernel and reboot recovery.
- Now in TWRP recovery (you can again choose to do steps a to d which is totally optional) find and flash the ROM you want
- flash gapps
- reboot
That should do it
and now just in case you don't like what you flashed you can always go back to your ROM if you took a nandroid backup as suggested in the installation steps
hope it helps
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Very clear! Thank you very much. Sorry for being a noob with this but it i think you cant be too sure when you are flashing kernels. Got my Nexus S bricked once while i was flashing a custom kernel.
And i dont have any experience with flashing samsung phone. Only HTC.
Thanks again and have a good day!
hosseltietjes1990 said:
Very clear! Thank you very much. Sorry for being a noob with this but it i think you cant be too sure when you are flashing kernels. Got my Nexus S bricked once while i was flashing a custom kernel.
And i dont have any experience with flashing samsung phone. Only HTC.
Thanks again and have a good day!
Click to expand...
Click to collapse
I was in the same boat 2 years ago so i understand the situation I am glad i could help and if you are coming from nexus I am pretty sure you won't have any issues at all. Just one or two flashes and you will know everything
and who knows I might need your help one day as I am thinking of buying the N6 myself
oh and btw let me tell you that recovery and kernel are in the same partition for N7000 so you can't have "this kernel and that recovery" here as you would in other devices. Thus if you need a certain recovery then you have to flash a certain kernel and if you need a certain kernel then it will install the recovery that comes with it overwriting the previous one. Also even if you flash just recovery somehow, the device will restore the one with the kernel upon reboot
So yeah
REVENGE SOLVES EVERYTHING
tysonraylee said:
I was in the same boat 2 years ago so i understand the situation I am glad i could help and if you are coming from nexus I am pretty sure you won't have any issues at all. Just one or two flashes and you will know everything
and who knows I might need your help one day as I am thinking of buying the N6 myself
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
I just recently flashed my HTC one X And the One X of a friend of mine. No need there to flash the kernel on that phone, only recovery trough adb and flash rom. So i really dont wanna mess with kernels
I you would like to ask something, feel free to ask! Thanks for the support
hosseltietjes1990 said:
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
Click to expand...
Click to collapse
In the guide below
http://forum.xda-developers.com/showthread.php?p=53346482
it clearly says ''-Download Raw Kernel r5 and copy it to either your internal or external memory''
You have downloaded raw_kernel_r4_j43
Why is that?
Am i missing something?
My friend's n7000 runs on 4.1.2 as well and my goal is to install cm11 as well.
Saying that, which is the appropriate raw_kernel???
The kernel code name should match the currently installed TW rom (4.1.2) or should it match the CM11 rom you intend to flash (4.4.4)????
to answer my own question : In XxPixX's quide of course it says r5 so 4.4.4 )
Anyway the kernel that you have downloaded is neither r5 nor r1 (i beleive that r1 is for 4.1)
Thanks, i hope someone with more experiense would clarify that!!
eveles said:
In the guide below
http://forum.xda-developers.com/showthread.php?p=53346482
it clearly says ''-Download Raw Kernel r5 and copy it to either your internal or external memory''
You have downloaded raw_kernel_r4_j43
Why is that?
Am i missing something?
My friend's n7000 runs on 4.1.2 as well and my goal is to install cm11 as well.
Saying that, which is the appropriate raw_kernel???
thanks!!!!!!
Click to expand...
Click to collapse
yes you have to download raw kernel because CM 11 or Android Kitkat requires SE Linux compatible recovery and raw kernel is the one that has this compatibility.
If you skip raw kernel then installation will fail giving you "status 7 installation aborted" error.
Downloading the latest Raw kernel for KitKat should do it just read in the kernel thread and download the latest one for kk.
the kernel code name should match the ROM (4.1.2) the one you currently have. Download the philz JB kernel for your JB ROM(follow the steps given in philz kernel thread)
There is no requirement as such for 4.4.4 ROM
REVENGE SOLVES EVERYTHING
tysonraylee said:
yes you have to download raw kernel because CM 11 or Android Kitkat requires SE Linux compatible recovery and raw kernel is the one that has this compatibility.
If you skip raw kernel then installation will fail giving you "status 7 installation aborted" error.
Downloading the latest Raw kernel for KitKat should do it just read in the kernel thread and download the latest one for kk.
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
hosseltietjes1990 said:
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
Click to expand...
Click to collapse
The download link you have provided links to r6 not r5
r6 says that is only for omniron 4.4
We were talking about cm11.
eveles said:
The download link you have provided links to r6 not r5
Click to expand...
Click to collapse
Oh i'm sorry haha. R6 should work right?
edit: sorry i did not read properly. r5 it is then
hosseltietjes1990 said:
Oh i'm sorry haha. R6 should work right?
Click to expand...
Click to collapse
No.
r5 should work.
Dude you are more confused than i am!!
hosseltietjes1990 said:
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
Click to expand...
Click to collapse
yes that should do it, download the k44 one
I haven't seen any videos about that but it is possible to do so but that's just using the recovery temporarily to flash a certain ROM but in the end that recovery is replaced by the ROMs kernel recovery its the same thing we are doing by using raw kernel here in these installation steps but its true that it gets a little confusing
I have updated my previous reply. Please refresh the page to see the explanation
eveles said:
The download link you have provided links to r6 not r5
Click to expand...
Click to collapse
R6 is the latest version. Please download the R6-k44.zip
REVENGE SOLVES EVERYTHING
I would install KITKAT on my Galaxy S i9000 using the TWRP recovery.
In the list of devices on which you can mount the TWRP not indicated the Galaxy S I9000.
It 'an error or you can not?
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I will choose the ROM later.
Now I have already choosed the procedure to save EFS files.
Now I'm choosing what type of recovery use.
I repeat: I would use TWRP but my smartphone does not appear in the list of supported devices.
On the contrary, in all the guides TWRP is indicated as an alternative to CWR.
Original TWRP is not available for i9000.
BUT: The CodeROM-Team managed to make it running onto i9000. Therefore, you need to extract TWRP from their ROM, convert it to an Imagefile and upload it with ODIN. This works!
Hello, I would like to also do this as stated in the OP. The image in the kernel.tar, that's what I have to flash the i9000 with Odin? Do I have twrp recovery then in the i9000?
Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?
bronxboy1 said:
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?
Click to expand...
Click to collapse
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
---------- Post added at 05:13 PM ---------- Previous post was at 05:08 PM ----------
Fragone said:
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
Click to expand...
Click to collapse
> The phone does not boot in download mode either
Did not see that before. I never had such an issue. Try it again, but do not push the power button more than 10 seconds, else the phone reboots again and again.
Sometimes, Download mode works even thought you cannot see anything on screen. try to connect the device to your PC and launch ODIN, you'll see if it can connect.
Tnx for your reply Fragone. It took me a while, had to wait on a USB jig for me to get the phone in download mode.
Unfortunately I did format to f2fs, how did you get back to ext? As for the other files, I did get my hands on an original rom, but I have to go look for the files you mentioned and try it with those, as the stock rom does not boot either. If you have the links, I'd be much abliged. Right now I go to sleep, just got home from the graveyard shift.
So someone finally returned my i9000 to me after a few years of use and I'm looking to put a current ROM on it so I can use it as a test phone. I keep seeing TWRP as the custom recovery used for the new ROMs. And yet like umberto, I've found there's no official custom TWRP for this phone. I'm pretty familiar with using TWRP on all my other devices.
So back to the original question of this thread - is there a way to get TWRP on the phone? It looks like Fragone's suggestion isn't the right way to go? The only thing I could find in my thread searches was a suggestion to use Mackay's ROM to get 2.8.1.0 and then (theoretically) it's on there so you could move to other ROMs. Any help?
D
@umberto santulli @dnaod
On the i9000, kernel & recovery share the same image, thus the recovery cannot be flashed separately. Therefore there is no i9000 on the TWRP site.
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One
tetakpatak said:
@umberto santulli @dnaod
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One
Click to expand...
Click to collapse
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.
dnaod said:
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.
Click to expand...
Click to collapse
There should be no problem to change the ROM. Just mind that the kernel & recovery share the image. I was using Omni 4.4.4 by kasper_h and Mackay kernel with TWRP
tetakpatalked from Nexus 7 flo