NOTICE: I no longer have a copy of the recovery image since goo.im went down. If anyone still has it, feel free to post a link. I'll leave the instructions here. Also, I won't be updating this since I no longer have a TF201 and ROM development seems to have shifted to a modified bootloader, which requires a different recovery image anyway.
Original post:
Warning: You must be on the 4.1.1 Bootloader to use this. Androwook and other stock based ROMs supply their own recovery.
With 4.4 based ROMs starting to come to our tablet, and official TWRP not flashing them, I thought I'd take a crack at updating it. As some of you may know, attempting to flash a KitKat ROM using the current version of TWRP fails, resulting in a "set_metadata_recursive" error. This updated version, based on the OmniROM fork of TWRP, fixes that.
Latest Version: 2.7.0.0-Voyager2k_v1.2
Instructions:
1.(Highly Recommended) Enable NVFlash if you haven't already. Check here for details.
2. Make sure you are on the 4.1.1 Jellybean Bootloader. If you are already running ParanoidAndroid or CyanogenMod, you're fine.
3. Download the recovery image here. The latest file is recovery1.2.img. EDIT: Links are broken. See above
4. You can use the same instructions that are on the TWRP page, but for convenience, I'll add them here. You have two options:
A. Fastboot. Boot the tablet into fastboot and use "fastboot -i 0x0b05 flash recovery recoveryX.X.img" (no quotes, replace X.X with whatever numbers are in the filename) from your computer to flash the recovery.B. Flash from terminal within the tablet. Open a terminal emulator within android and type "su" (no quotes) to get root access. Then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4" (no quotes, replace X.X with whatever numbers are in the filename) to flash the recovery and reboot normally. This is critical, as the recovery won't flash until the system has rebooted normally.
If successful, the version number should read: "2.7.0.0-Voyager2k-vX.X" (X.X being my revision number)
Known Issues:
1. /system/media doesn't get backed up for some reason. Restoring backups works, but you won't have sounds or a boot animation. (I think this is fixed in the newest version, but I'm waiting on other reports before I remove this item)
Ususal disclaimer: I am not responsible if this messes up your tablet in any way.
Credits:
TWRP for making the recovery
Built from the OmniROM fork. Source is here.
Changelog:
Version 1.1 - 2/19/2014
Added support for the dock keyboard
Fixed /system/media not backing up properly
Synced with latest OmniROM recovery sources
Version 1.2 - 3/25/2014
Updated to TWRP version 2.7.0.0
A little cleanup behind the scenes
one more.
Works Great! Flashed without problems via fastboot :victory:
Thank You!
Now I just need an awesome 4.4. ROM to flash :fingers-crossed:
works also with the second instruction over the tablet
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
thanks, it works through terminal. jut make sure to be root (su) and adjust the path of the recovery image
Sent from my EPAD using Tapatalk
thanks! This rec works and I have flashed cm11. Terminal works. U should insert "su" first
Sent from my GT-N7102 using Tapatalk
To use the second method you need to run su command first before using dd
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4
Terminal
Just would like to ditto.
The process worked in the terminal on the device.
Thank you for this!
Bug report!
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Dasdranamin said:
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Click to expand...
Click to collapse
Thanks for the report. I'll look in to it.
Cyrozo said:
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
Click to expand...
Click to collapse
Are you sure you placed the new "recovery.img" in the root directory of the sdcard? Won't work if the file is anywhere else.
Note 3 4.4.2
Does it work on note 3 with 4.4.2??
SAMERKAD said:
Does it work on note 3 with 4.4.2??
Click to expand...
Click to collapse
Nope, check your devices fora for compatible recoveries.
Bastaerd said:
Nope, check your devices fora for compatible recoveries.
Click to expand...
Click to collapse
can i bring back backed up data with other recovery?
SAMERKAD said:
can i bring back backed up data with other recovery?
Click to expand...
Click to collapse
You should be able to do so. Anyways, this isn't the recovery for your device.
Bastaerd said:
You should be able to do so. Anyways, this isn't the recovery for your device.
Click to expand...
Click to collapse
yeah i know, but i had it on 4.3 and backed up data via TWRP
now im on 4.4.2 with CWM Recovery...
want to restore my System data
Thankss
What bootloader is this compatible with? Does it work with the TF300T Bootloader? I am guessing not but someone from the Androwook thread might try it and that will not be good.
Seeing this is for kk support/ROMs, why would a wookie fastboot this?
Thank you Voyager for the ongoing support for the prime!
Sent from my VS980 4G using Tapatalk
Related
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Recovery flashable version here
Credits: Dees_Troy
dr87 said:
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Mount and unmount issues *may* be fixed (I haven't been able to reproduce them)
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Credits: Dees_Troy
Click to expand...
Click to collapse
Awesome job bro! Running like a champ!!
Sent from my One using XDA Premium 4 mobile app
Thanks a lot!
Now I can run Mahdi without problems!
thanks for this- but it's still not working- will i need to reflash madhi? i just fastbooted the recovery across and it boots into the recovery no worries and recognises all partitions but rom won't boot...
***edit*** it just booted up, about 5th attempt.. no boot animation though...ignore me...
Flashed recovery.img, bootet into recovery, no partitions..
Klarooo said:
Flashed recovery.img, bootet into recovery, no partitions..
Click to expand...
Click to collapse
Which rom were you running when you rebooted into recovery?
Stock, so CM11s.
mine still is not good. i treid to reboot to get it to hold the no hardware buttons. didn't reboot. tried about 10 times. eventually booted intot this new recovery and reflashed rom and booted it up. it's a bloody weird looking boot- no boot animation- made me think it was screwed again.
did you have to do anything to get it working again? Wipe entire device or just data partition?
Working good here, but I had no issues with the official build. I have an international version, 64GB OPO.
It's nice to see some additional features added, though.
Just helping out, packaged in a flashable zip for those with current CWM or TWRP recoveries, tested and working, enjoy everyone.
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Chris123NT said:
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Click to expand...
Click to collapse
Guys i wonder when you press efs restore is it
fastboot format modemst1 & st2
or
fastboot erase modemst1 & st2
or may be both? in that case in what order?
I flashed the one in OP, but the system does not see any partition ?
Can I flash 15th without bricking the phone
[EDIT] I tried a second time, and now it´s ok, partitions are there and backup is currently running
Any chance at adding F2FS support direct for this recovery for the ONE Plus?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Looks like the official .img version has been incremented to 2.7.1.1
More here: http://techerrata.com/browse/twrp2/bacon
A flashable zip for v2.7.1.1 would be nice.
Changelog? Hopefully they fixed those Partitions issues
2.7.1.1-Bacon Recovery Flashable zip
Mikey said:
2.7.1.1-Bacon Recovery Flashable zip
Click to expand...
Click to collapse
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
playya said:
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
Click to expand...
Click to collapse
Correct, easy huh
Delete the twrp.img......drag and drop the new img into the zip......dont uncompress the zip and compress it again.
NOTICE
As i no longer own this tab, i will no longer be providing support for it.
As devhost is slowly and surely deleting my files, i have moved them
to androidfilehost https://www.androidfilehost.com/?w=files&flid=23547
As androidfilehost does not delete files, these recoveries will remain hosted indefinitely.
m
Update 1 Uploaded - Choose v2
i am doing a new build as i may have missed setting support for extended attributes.
will update shortly.
v2 is up - link updated
changed default security module to selinux and modified source /bootable/recovery-cm/updater/install.c
as follows:
<cm11 source dir>/bootable/recovery-cm/updater/install.c
in line 586 (under the function ParsePermArgs(int argc, char** args):
654:- parsed.has_capabilities = true;
654:+ parsed.has_capabilities = false;
mainly for testing. still functional as before.
on v2
okay,
i have been using v2 quite a lot since i posted it and it works pretty solidly.
A major note- to flash supersu update zip you must use most recent version from chainfire's site.
The adb experience is good provided you remember to mount data and system.
I will be getting to Philz Advanced after a little more practice with building.
Right now my attempt in th recovery arena will be to get aromafm built and working.
Both versions of my cwm build will remain posted.
m
edit- uploaded v2 Alien - i know, it's goofy but it looks pretty cool. =)
Philz Adv CWM 6.55.0 - CWM 6.0.5.0
sorted.
screen shots
Philz Adv CWM - Update August 2, 2014
Before all other things, @Hazou , Dude you rock !!
Unending thanks to @Phil3759 for making your source available.
okay so this is Philz Advanced Touch for GT-P5210 [fixed, no lag].
If anyone needs CWM rebuilt let me know.
This time i have released it in a flashable zip [CWM]. I wil be pulling the clunky one [Philz]
And with that, I think I am done with recovery building for now. Enjoy
the name of the file is PhilzAdvCWM-6_55_0-gtp-5210.zip. See OP for link.
m
AROMAFM
yup, aromafm :victory:
okay so,
issues are lag, resolution and possibly a ram related crash, in which event, force reboot [will return you to recovery] and then reboot normally.
i'm working on it. NOTE- enabling automount seems to reduce occurence of crash/hang.
in terminal ~#whoami
returns ~#uid0 :good:
busybox :good:
see OP for link. this is an initial offering and requires work.
thanks a million times to @amarullz for making his source available
thanks to @Hazou as ever :good:
please pm me to report bugs and issues. enjoy !
m
TWRP v2.7.1.0 for GT-P5210
Reserved for TWRP
Will be attemtping to improve/fix/sort terminal.
Didn't want to be unfair to TWRP users.
Will update.
m
Thanks @Siberian Tiger :good:
Okay so, TWRP is up. See OP for link.
I am still looking for what i need to know to make the terminal in twrp a less-suck experience.
No lag and, I am actually starting to like TWRP alot. I have tested on my tab, backup/recovery are good. aromafm installs and runs well. adb seems to be in order. I did trim the fstab leaving system, data/internal storage, cache, recovery, boot and external storage.
If other variants need different setup please let me know.
As always please do not post thank-you's. Bugs and issues only.
thank you for reading
m
Notes
I did not generate any new or additional code.
All sources are already available - CWM, PHILZ, TWRP, AROMAFM
However the patches applied to cm11 build environment are
@Hazou , infinitely thankable :good:
https://github.com/HazouPH/android_system_core/commit/54cf228097d58713d71a13a6c79794bfa373eab0
https://github.com/HazouPH/android_device_motorola_smi/blob/jellybean/patch/cwm_0001.patch
m
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
damian312 said:
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
Click to expand...
Click to collapse
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Awsome. With the instruction spelled out to me, even I might be able to have a go att it.
BIG thanx for your patients with us end-users (that have no talent for coding )
/H
hmm...
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
FurFur_ said:
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
Click to expand...
Click to collapse
Read the OP completely.
moonbutt74 said:
Read the OP completely.
Click to expand...
Click to collapse
Of Course! thaaanks~~
moonbutt74 said:
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38524#files TO RECOVERIES
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38598#files TO AROMAFM - W.I.P.
NOTE- This is not a flashable/odin-able file. You must dd write to /dev/block/mmcblk0p11 [or appropriate recovery block]
Click to expand...
Click to collapse
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
kgyirhj said:
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
Click to expand...
Click to collapse
You need to execute the command as the root user, or what we call the superuser. Execute: su root. And then you are good to go.
Thanks @Divine_Madcat
m
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Okay i would like to flash this but because i currently have twrp installed and am not a fan cause it won't let me install 4.4. However i have know idea what this means. Can i flash this cwm using twrp?
Made TWRP Friendly
@jyerly
Okay so, this is Philz Recovery with the assert removed to be Old TWRP Friendly
TESTED, WORKING. I don't do it any other way.
devhost link - http://d-h.st/SSY
m :good:
HI Moonbutt74,
sorry for my maby silly question, but always just flashed via ODIN, CW; TWRP on my SGSII.....the Tab3 is differnet here and seems I have no clue .
I have rooted my Tab via the Root.zip and use the CWM from DutchDanny, still on stock firmware (see my sig).
I'd like to update to one of your new recoveries and go with Restl3ss Pimpdroid....but have no clue from terminal command.
Is there any hint how I execute the command you posted in OP?
Thanks for your kind help,
GeScha
http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks
This work in miui v6
Thanks a lot for this quick update :thumbup:
Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing
Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?
@pilger i'm here, what to do next?
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!
pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Thanks Train, I would been lost. I replied to you gplus posting. Really appreciative for your work on this post. Thanks dude.
Ash
Bump
Sent from my Nexus 6P using Tapatalk
Double Bump
Sent from my SGP621 using XDA-Developers mobile app
This needs to be pinned!
Sent from my Nexus 6 using XDA Labs
I just used this and was able to get my Nexus 6P back up with your nandroid. I should not be able to use fastboot flash correct to get a full google stock?
pctechdroid said:
I just used this and was able to get my Nexus 6P back up with your nandroid. I should not be able to use fastboot flash correct to get a full google stock?
Click to expand...
Click to collapse
Yes you should be able to... Or just unroot so that the OTA will work.
Sent from my Nexus 6P using Tapatalk
Train88 said:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Click to expand...
Click to collapse
Dude. I don't know what to say. I really thought I lost my nexus 6p. But your tutorial worked like a charm. Thank you so much for sharing your nandroid and writing up an amazing tutorial!!! This seriously needs to get pinned!!????✌?
Sent from my ONE A2003 using Tapatalk
---------- Post added at 05:22 PM ---------- Previous post was at 05:17 PM ----------
BTW, I also was on MTC20F. Your nandroid booted the device. But I had to clean install MTC20F again so that the WiFi and sim started to work. Might come handy for some people... ??
Sent from my ONE A2003 using Tapatalk
im_Zak said:
Dude. I don't know what to say. I really thought I lost my nexus 6p. But your tutorial worked like a charm. Thank you so much for sharing your nandroid and writing up an amazing tutorial!!! This seriously needs to get pinned!!????✌?
Sent from my ONE A2003 using Tapatalk
---------- Post added at 05:22 PM ---------- Previous post was at 05:17 PM ----------
BTW, I also was on MTC20F. Your nandroid booted the device. But I had to clean install MTC20F again so that the WiFi and sim started to work. Might come handy for some people... ??
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I'm glad I could help! Thanks for the extra info! ?
Sent from my Nexus 6P using Tapatalk
I have a similar issue, any advice on this... Updated to PureNexus Nougat fine, but even before that I had realized that my phone was not being detected through USB, no fastboot, recovery, nothing. So I flashed through TWRP to the current PureNexus Nougat build. All went good, except I now realized that the version of TWRP I have must be one with bugs on Nougat. Booting into recovery it just sits at the TWRP loading screen forever.
I can't get ADB through USB, can't get into Recovery, and Fastboot wont connect on USB. I can boot into the ROM just fine (not rooted) and can do ADB w/ wifi when booted up in Android.
Any ideas on how to fix my recovery and/or flash anything at all at this point? I am almost feeling like there must be something wrong with the actual usb-c port, but charging works fine, just no data connection at all (tried any different cables, Windows, Mac, different usb ports).
Is debugging on in your developer options.
Sent from my ONE A2003 using Tapatalk
Lacrosse200760 said:
I have a similar issue, any advice on this... Updated to PureNexus Nougat fine, but even before that I had realized that my phone was not being detected through USB, no fastboot, recovery, nothing. So I flashed through TWRP to the current PureNexus Nougat build. All went good, except I now realized that the version of TWRP I have must be one with bugs on Nougat. Booting into recovery it just sits at the TWRP loading screen forever.
I can't get ADB through USB, can't get into Recovery, and Fastboot wont connect on USB. I can boot into the ROM just fine (not rooted) and can do ADB w/ wifi when booted up in Android.
Any ideas on how to fix my recovery and/or flash anything at all at this point? I am almost feeling like there must be something wrong with the actual usb-c port, but charging works fine, just no data connection at all (tried any different cables, Windows, Mac, different usb ports).
Click to expand...
Click to collapse
What Zak said - you are not even in the same boat as the people that need this guide. You can get it to boot. I could not do anything besides go to fastboot(download mode) when I made this
Sent from my Nexus 6P using Tapatalk
Lacrosse200760 said:
I have a similar issue, any advice on this... Updated to PureNexus Nougat fine, but even before that I had realized that my phone was not being detected through USB, no fastboot, recovery, nothing. So I flashed through TWRP to the current PureNexus Nougat build. All went good, except I now realized that the version of TWRP I have must be one with bugs on Nougat. Booting into recovery it just sits at the TWRP loading screen forever.
I can't get ADB through USB, can't get into Recovery, and Fastboot wont connect on USB. I can boot into the ROM just fine (not rooted) and can do ADB w/ wifi when booted up in Android.
Any ideas on how to fix my recovery and/or flash anything at all at this point? I am almost feeling like there must be something wrong with the actual usb-c port, but charging works fine, just no data connection at all (tried any different cables, Windows, Mac, different usb ports).
Click to expand...
Click to collapse
You can flash recovery from phone terminal, Google the commands. You need root though, install super su from playstore. Otherwise you'll need to fix that adb issue.
djdarkknight96 said:
You can flash recovery from phone terminal, Google the commands. You need root though, install super su from playstore. Otherwise you'll need to fix that adb issue.
Click to expand...
Click to collapse
Installing SuperSU from playstore wont actually give me Root though. I like the idea though, maybe there is something that can be done around this.
Lacrosse200760 said:
Installing SuperSU from playstore wont actually give me Root though. I like the idea though, maybe there is something that can be done around this.
Click to expand...
Click to collapse
Flash recovery through adb or android terminal, download the superSU zip, flash the zip in recovery. If you're having trouble getting recovery to stick, you need to flash the superSU zip immediately after you flash recovery. If you boot before doing that, android will try overwrite the custom recovery on boot
Sent from my Nexus 6P using Tapatalk
Train88 said:
Flash recovery through adb or android terminal, download the superSU zip, flash the zip in recovery. If you're having trouble getting recovery to stick, you need to flash the superSU zip immediately after you flash recovery. If you boot before doing that, android will try overwrite the custom recovery on boot
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Doesn't flashing recovery through adb require root? (only have adb wifi access when phone is booted into ROM)
Lacrosse200760 said:
Doesn't flashing recovery through adb require root? (only have adb wifi access when phone is booted into ROM)
Click to expand...
Click to collapse
No you don't need root to flash in adb. Just an unlocked bootloader
Sent from my Nexus 6P using Tapatalk
Lacrosse200760 said:
Doesn't flashing recovery through adb require root? (only have adb wifi access when phone is booted into ROM)
Click to expand...
Click to collapse
Train88 said:
No you don't need root to flash in adb. Just an unlocked bootloader
Click to expand...
Click to collapse
I have been very lucky to not have to remember but Train is correct. You should be able to push recovery via adb Wi-Fi. I forget root isn't needed to replace it, like Train said. "Kinda talking to myself as a reminder lol"
Train88 said:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Click to expand...
Click to collapse
Followed Your guide
at first, I couldn't repair the data partition. Then I formatted the whole device again and was able to repair data partition. But when I go to restore your backup, boot flashes fine but when it says flashing data, TWRP hangs and it reboots into the google splash logo screen.
TJ_bab said:
Followed Your guide
at first, I couldn't repair the data partition. Then I formatted the whole device again and was able to repair data partition. But when I go to restore your backup, boot flashes fine but when it says flashing data, TWRP hangs and it reboots into the google splash logo screen.
Click to expand...
Click to collapse
It could be due to the storage option my 6P has (128 GB)... Try restoring everything but data. But essentially, it's the efs backup that you need if your issue was created by a bad backup from TWRP 3.0.2-1.
Sent from my Nexus 6P using Tapatalk
How to use magisk to twrp from 2.3.5 gingerbread without a computer?
@Didgeridoohan
Do you think its possible to flash twrp from a terminal emulator? Or what are my options?
If you really can't get a hold of a computer you might be lucky with an app like Franco Kernel Manager, Flashify, etc. Problem is that most apps likely won't support or be compatible with that ancient version of Android or whatever root you currently have installed. And, you're also risking bricking your device if you don't have access to a computer...
I really think your best bet is to somehow get access to a computer. Friend/school/work/something...
If you can't install stuff on that borrowed computer you could create a bootable USB with a Linux distro and run everything from there. Linux Mint is quite user friendly, they've got good documentation on how to get things running with a Live Boot USB, and it's not too hard to get adb & fastboot up and running.
Ill try and get a hold of a computer because nothing seems to work on 2.3.5
@Didgeridoohan
I had rooted using framaroot but after a factory reset it wont install supersu or superuser to my app drawer, can you give me a suggestion? Btw im using my xbox one to type this.
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
jwoegerbauer said:
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
Click to expand...
Click to collapse
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
chris1892006 said:
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
Click to expand...
Click to collapse
Is it so hard to read posts carefully?
I found this https://www.youtube.com/watch?v=-YAKGRblIuw
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9
What part of the command do i change for a yp-g70 venturi? Also can i extract my twrp 2.8.0.0.zip and get the .img out of it or can i flash the .zip?
This what i used to flash cwm/ entropys daily driver kernel
https://forum.xda-developers.com/showthread.php?t=1445840
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p11
Well i got cwm installed! Now i just need to flash twrp and then a rom
chris1892006 said:
... Now i just need to flash twrp and then a rom
Click to expand...
Click to collapse
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
jwoegerbauer said:
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
Click to expand...
Click to collapse
Thanks i had 4.4.4 up and running but tried flashing 5.1.1 lollipop on cwm and it corrupted the bootloader. Now i cant get into recovery because twrp wouldnt flash over cwm, i tried to flash twrp 2.8.0.0 & it succeeded yet didnt work after a reboot, why? I read the op but i still cant figure out why it didnt work after a reboot? Still remained cwm.
https://forum.xda-developers.com/galaxy-player/development/recovery-twrp-v2-8-0-0-t2867742
http://www.meticulus.co.vu/p/yp-g70.html
@Didgeridoohan
How do i flash twrp over cwm?
Hey... Look at that, you had some progress. Nice.
I've never used CWM, so I wouldn't know.... Sorry.
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
jwoegerbauer said:
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
Click to expand...
Click to collapse
thanks only problem is they only make a .zip for twrp for my device... I don't know how to flash it.
That's a really old android version, I'm not sure if it's possible. If you don't have access to a PC, try to ask a friend if they could do it for you, just to be safe. Trying to modify stuff within android, especially on such an old version, with probably unsupported software could result in a bricked device.
Thanks but I finally got TWRP and Lollipop 5.1.1 installed it took an ADB Sideload from a PC to sideload the twrp.zip file for my device and now I'm up and running and very happy to say the very least. Sure I bricked it 3 times in the process but was always able to recover using ODIN and having the proper files on hand.
Now im having an issue with xda on the device where the xda app wont let me sign in and the browser will sign me in but go right back to the sign in page again, idk how to fix it?
I install a dalvik cache wiper with root required and it corrupted the recovery again. So I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.