mods please close thread - Galaxy Note GT-N7000 Android Development
closed
How to compile TWRP recovery?
I followed the guide here http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
To summarize...
1. Install Linux
2. Set up CM10 build environment - this is sssssooooo easy and there are loads of guides available with just a simple google search.
3. Repo sync
4. Build standard cm10 from source
5. Delete the contents of the ~/android/system/bootable/recovery and replace with https://github.com/TeamWin/Team-Win-Recovery-Project/ - i just clicked on the download zip button on the top left and unzipped into the folder but am sure there is a proper way of doing this... zip clone???
6. gedit ~/android/system/device/samsung/galaxys2-common/recovery.rc and add: export LD_LIBRARY_PATH .:/sbin
7. gedit ~/android/system/device/samsung/n7000/BoardConfig.mk and add the following to the bottom of the file
#twrp
DEVICE_RESOLUTION := 800x1280
8. cd ~/android/system
9. make -j3 bootimage (if you have a quad core processor make -j5 bootimage)
10. you can find your boot.img at ~/android/system/out/target/product/n7000
11. Copy to SDCARD and flash with mobile odin
12. Done!!!!!
good work. appreciate the effort you have put in.
looking into it now.
Finally here, good work. Will try it as i'm already using TWRP in my N7.
Enviat des d'es meu Nexus 7 amb so Tapatalk2
im using TWRP to flash rom for N8013 and work great.Thanks
nice to see u
subscribed.
You Should pm entropy
Sent from my GT-N7000 using Tapatalk 2
I have sent him a PM
Sent from my GT-N7000 using XDA Premium HD app
timstanley1985 said:
Team Win Recovery Project 2.3 for Galaxy Note (CM10 only)
If you do not know what TWRP is, click here first...... now you know what TWRP is (and how very cool it is!!!) we can continue.
Foreword:
I have looked at those with devices with TWRP with envy for the entire time i have owned a Galaxy Note and have been waiting patiently for an experienced Dev to compile a version for the N7000. After a year of ownership this has not happened so i have decided to go ahead and do it myself!!
Why have you called this a proof on concept?
For a few reasons:
1. I am not an experienced Dev... i have built CM6, 7 and 10 from source and done all the usual tweaks to my android devices but that is where my experience ends. This in itself is no big deal in its self but leads me to point 2...
2. This recovery may have MMC_CAP_ERASE / Brick Bug! I do not know how to check if it is present or not! Until an experienced Dev confirms MMC_CAP_ERASE has been fully suppressed you should assume this recovery is dangerous. As soon as an experienced Dev confirms the recovery is safe i will update this post. If it is confirmed it is not safe i will remove all links
3. I unfortunately to do not have time to maintain this recovery. As Samsung recoveries are included in the boot.img (kernel) it will mean the recovery will need recompiling every time a change is merged to the kernel in CM10. As development is still very active on the N7000 kernel i cannot make the commitment to recompile this that often
4. I am not a kernel Dev therefore i can only compile stock kernel with TWRP recovery. We all love (me included) a custom kernel with all the normal tweaks, OC etc. etc. I will never be able to achieve this so want to use this as the seed for somebody else to take and use to build there own custom kernel with TWRP recovery
5. It needs more extensive testing.... I have been playing with it for an hour this morning and everything seems to work fine but needs more testing.
I have included how to compile TWRP in post two... did i hear someone say enough talking, i want to try this out!!!
How to install
I have attached the boot.img at the bottom of this post.
1. Download
2. Copy to SDCARD
3. Flash with Mobile Odin
4. Enjoy!!
Please remember: This recovery may contain MMC_CAP_ERASE / Brick Bug! I do not known how to check! It is built from CM10 sources and there are TWRP ports for other devices so should be safe but i cannopt be positive! Use at your own risk!
Experienced Dev's: Any feedback on whether this recovery is safe would be VERY gratefully received!
As soon as any confirmation of this recovery being unsafe i will remove link immediately!
Click to expand...
Click to collapse
Based on item #4 (this is using a stock kernel repacked with a new recovery) - it will not be safe for flashing things.
For wipes and backups, it depends on exactly how you built it. Run strings on the binary...
Code:
strings recovery |grep MMC
If you see
Code:
warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware
The recovery binary is safe to do wipes/backups with, but as said above, if you used a stock kernel, it will be dangerous to flash ZIPs.
Also, of course, as this is a galaxys2-family device, the moment you flash anything containing a new kernel, TWRP will be gone.
Sorry, I should have been clearer. When I say stock kernel I mean stock CM10 kernel. This recovery is built by deleting the /bootable/recovery/ folder and replacing it with TWRP recovery. The rest of the build is standard CM10.
Sent from my GT-N7000 using XDA Premium HD app
Some usage feedback: I found it quite hard navigating through a folder filled with many sub-folders and files to select what I want to flash...quite jerky UI and a lot different from the experience I get on my TWRP-recoveried tablet.
But great initial release dev - really, well done!
And is this Heimdall flashable or do you strictly recommend Odin only? I have never used Odin since it is blackbox and everyone I knew has been recommending Heimdall. I know the former is designed to best-case mimic the latter, but just want to cover all my bases.
Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app
timstanley1985 said:
Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Alright will give it a go. Thanks for the quick reply.
alharaka said:
Alright will give it a go. Thanks for the quick reply.
Click to expand...
Click to collapse
Yeah, so maybe I did not understand entirely but when I flashed I got a success with Heimdall 1.3.1 CLI on OS X (10.6.8).
Code:
my-bacbook-pro:~ root# heimdall flash --recovery /Users/myusername/Downloads/boot.img --verbose
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading RECOVERY
0%File Part #0... Response: 0 0 0 0 0 0 0 0
2%
File Part #1... Response: 0 0 0 0 1 0 0 0
5%
File Part #2... Response: 0 0 0 0 2 0 0 0
7%
File Part #3... Response: 0 0 0 0 3 0 0 0
10%
File Part #4... Response: 0 0 0 0 4 0 0 0
12%
File Part #5... Response: 0 0 0 0 5 0 0 0
15%
File Part #6... Response: 0 0 0 0 6 0 0 0
18%
File Part #7... Response: 0 0 0 0 7 0 0 0
20%
File Part #8... Response: 0 0 0 0 8 0 0 0
23%
File Part #9... Response: 0 0 0 0 9 0 0 0
25%
File Part #10... Response: 0 0 0 0 A 0 0 0
28%
File Part #11... Response: 0 0 0 0 B 0 0 0
31%
File Part #12... Response: 0 0 0 0 C 0 0 0
33%
File Part #13... Response: 0 0 0 0 D 0 0 0
36%
File Part #14... Response: 0 0 0 0 E 0 0 0
38%
File Part #15... Response: 0 0 0 0 F 0 0 0
41%
File Part #16... Response: 0 0 0 0 10 0 0 0
44%
File Part #17... Response: 0 0 0 0 11 0 0 0
46%
File Part #18... Response: 0 0 0 0 12 0 0 0
49%
File Part #19... Response: 0 0 0 0 13 0 0 0
51%
File Part #20... Response: 0 0 0 0 14 0 0 0
54%
File Part #21... Response: 0 0 0 0 15 0 0 0
57%
File Part #22... Response: 0 0 0 0 16 0 0 0
59%
File Part #23... Response: 0 0 0 0 17 0 0 0
62%
File Part #24... Response: 0 0 0 0 18 0 0 0
64%
File Part #25... Response: 0 0 0 0 19 0 0 0
67%
File Part #26... Response: 0 0 0 0 1A 0 0 0
70%
File Part #27... Response: 0 0 0 0 1B 0 0 0
72%
File Part #28... Response: 0 0 0 0 1C 0 0 0
75%
File Part #29... Response: 0 0 0 0 1D 0 0 0
77%
File Part #30... Response: 0 0 0 0 1E 0 0 0
80%
File Part #31... Response: 0 0 0 0 1F 0 0 0
83%
File Part #32... Response: 0 0 0 0 20 0 0 0
85%
File Part #33... Response: 0 0 0 0 21 0 0 0
88%
File Part #34... Response: 0 0 0 0 22 0 0 0
90%
File Part #35... Response: 0 0 0 0 23 0 0 0
93%
File Part #36... Response: 0 0 0 0 24 0 0 0
96%
File Part #37... Response: 0 0 0 0 25 0 0 0
98%
File Part #38... Response: 0 0 0 0 26 0 0 0
100%
RECOVERY upload successful
Ending session...
Rebooting device...
But I rebooted and was back in ClockwordModRecovery 6.1.2. Did I misunderstand the directions? Sorry, my first time using Heimdall to write to my device; last few times I just detect'n'dump-ed to avoid destroying my phone because it was unnecessary.
If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app
timstanley1985 said:
If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
I'll give that a try. Who knows what the deal is then.
alharaka said:
I'll give that a try. Who knows what the deal is then.
Click to expand...
Click to collapse
Ok, so I configured Mobile ODIN Lite (thanks for the pointer, by the way, amazing app I thought I had to pay for when I saw it a few weeks ago; had no idea I could test a lite version on XDA, sweet). So, installed it and got the N7000 add-on. What partition do I work with: Hidden?
Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app
timstanley1985 said:
Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Sorry for all the silly questions, and thanks again. I just wanna be sure since the recovery, well, makes mistakes less serious and I rely on it heavily. Once that is broken fixing my phone will get much more technical than I have time for.
Related
Compcache Problems On xROM 1.5r4
Why do i get this output when testing? What the heck am i doing wrong. I want some compcache with backing swap love too!!!!!!!!! === CompCache status === CompCache version 0.6+ Compcache enabled CompCache: MemLimit 16384(system) 8192(user) CompCache: BackingSwap /dev/block/mmcblk0p3(system) /dev/block/mmcblk0p3(user) !!! Unable to set compcache cc_swappiness to user specific "60" Current system value is "28" === CompCache status output === BackingSwap: /dev/block/mmcblk0p3 DiskSize: 100564 kB MemLimit: 16384 kB NumReads: 1 NumWrites: 0 FailedReads: 0 FailedWrites: 0 InvalidIO: 0 NotifyFree: 0 PagesDiscard: 0 ZeroPages: 0 GoodCompress: 0 % NoCompress: 0 % PagesStored: 0 PagesUsed: 0 OrigDataSize: 0 kB ComprDataSize: 0 kB MemUsedTotal: 0 kB BDevNumReads: 0 BDevNumWrites: 0 find: /system/app/*.odex: No such file or directory find: /data/app/*.odex: No such file or directory #
anybody????????????
I think xROM is ignoring my userinit.sh and user.conf, because when I type "free" in to the terminal it shows the size of my swap partition under swap, rather than my compcache size :-S What command are you using to retrieve those values?
[Q] [modem.bin]upgrade to leak rom by heimdall
I am trying to upgrade from GC100ZSALJ6 rom but failed when flashing the modem.bin. I have tried odin and heimdallv1.3.1. The output of the heimdall is, Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: Initialising connection... Detecting device... Manufacturer: "SAMSUNG" Product: "Gadget Serial" length: 18 device class: 2 S/N: 0 VIDID: 04E8:685D bcdDevice: 021B iMan:iProd:iSer: 1:2:0 nb confs: 1 interface[0].altsetting[0]: num endpoints = 1 Class.SubClass.Protocol: 02.02.01 endpoint[0].address: 83 max packet size: 0010 polling interval: 09 interface[1].altsetting[0]: num endpoints = 2 Class.SubClass.Protocol: 0A.00.00 endpoint[0].address: 81 max packet size: 0200 polling interval: 00 endpoint[1].address: 02 max packet size: 0200 polling interval: 00 Claiming interface... Setting up interface... Checking if protocol is initialised... Protocol is not initialised. Initialising protocol... Handshaking with Loke... Beginning session... Session begun with device of type: 131072 Downloading device's PIT file... PIT file download sucessful Uploading RADIO 0%File Part #0... Response: 0 0 0 0 0 0 0 0 1% File Part #1... Response: 0 0 0 0 1 0 0 0 2% File Part #2... Response: 0 0 0 0 2 0 0 0 3% File Part #3... Response: 0 0 0 0 3 0 0 0 4% File Part #4... Response: 0 0 0 0 4 0 0 0 5% File Part #5... Response: 0 0 0 0 5 0 0 0 6% File Part #6... Response: 0 0 0 0 6 0 0 0 7% File Part #7... Response: 0 0 0 0 7 0 0 0 8% File Part #8... Response: 0 0 0 0 8 0 0 0 9% File Part #9... Response: 0 0 0 0 9 0 0 0 10% File Part #10... Response: 0 0 0 0 A 0 0 0 11% File Part #11... Response: 0 0 0 0 B 0 0 0 12% File Part #12... Response: 0 0 0 0 C 0 0 0 13% File Part #13... Response: 0 0 0 0 D 0 0 0 14% File Part #14... Response: 0 0 0 0 E 0 0 0 15% File Part #15... Response: 0 0 0 0 F 0 0 0 16% File Part #16... Response: 0 0 0 0 10 0 0 0 17% File Part #17... Response: 0 0 0 0 11 0 0 0 18% File Part #18... Response: 0 0 0 0 12 0 0 0 19% File Part #19... Response: 0 0 0 0 13 0 0 0 20% File Part #20... Response: 0 0 0 0 14 0 0 0 21% File Part #21... Response: 0 0 0 0 15 0 0 0 22% File Part #22... Response: 0 0 0 0 16 0 0 0 23% File Part #23... Response: 0 0 0 0 17 0 0 0 24% File Part #24... Response: 0 0 0 0 18 0 0 0 26% File Part #25... Response: 0 0 0 0 19 0 0 0 27% File Part #26... Response: 0 0 0 0 1A 0 0 0 28% File Part #27... Response: 0 0 0 0 1B 0 0 0 29% File Part #28... Response: 0 0 0 0 1C 0 0 0 30% File Part #29... Response: 0 0 0 0 1D 0 0 0 31% File Part #30... Response: 0 0 0 0 1E 0 0 0 32% File Part #31... Response: 0 0 0 0 1F 0 0 0 33% File Part #32... Response: 0 0 0 0 20 0 0 0 34% File Part #33... Response: 0 0 0 0 21 0 0 0 35% File Part #34... Response: 0 0 0 0 22 0 0 0 36% File Part #35... Response: 0 0 0 0 23 0 0 0 37% File Part #36... Response: 0 0 0 0 24 0 0 0 38% File Part #37... Response: 0 0 0 0 25 0 0 0 39% File Part #38... Response: 0 0 0 0 26 0 0 0 40% File Part #39... Response: 0 0 0 0 27 0 0 0 41% File Part #40... Response: 0 0 0 0 28 0 0 0 42% File Part #41... Response: 0 0 0 0 29 0 0 0 43% File Part #42... Response: 0 0 0 0 2A 0 0 0 44% File Part #43... Response: 0 0 0 0 2B 0 0 0 45% File Part #44... Response: 0 0 0 0 2C 0 0 0 46% File Part #45... Response: 0 0 0 0 2D 0 0 0 47% File Part #46... Response: 0 0 0 0 2E 0 0 0 48% File Part #47... Response: 0 0 0 0 2F 0 0 0 49% File Part #48... Response: 0 0 0 0 30 0 0 0 51% File Part #49... Response: 0 0 0 0 31 0 0 0 52% File Part #50... Response: 0 0 0 0 32 0 0 0 53% File Part #51... Response: 0 0 0 0 33 0 0 0 54% File Part #52... Response: 0 0 0 0 34 0 0 0 55% File Part #53... Response: 0 0 0 0 35 0 0 0 56% File Part #54... Response: 0 0 0 0 36 0 0 0 57% File Part #55... Response: 0 0 0 0 37 0 0 0 58% File Part #56... Response: 0 0 0 0 38 0 0 0 59% File Part #57... Response: 0 0 0 0 39 0 0 0 60% File Part #58... Response: 0 0 0 0 3A 0 0 0 61% File Part #59... Response: 0 0 0 0 3B 0 0 0 62% File Part #60... Response: 0 0 0 0 3C 0 0 0 63% File Part #61... Response: 0 0 0 0 3D 0 0 0 64% File Part #62... Response: 0 0 0 0 3E 0 0 0 65% File Part #63... Response: 0 0 0 0 3F 0 0 0 66% File Part #64... Response: 0 0 0 0 40 0 0 0 67% File Part #65... Response: 0 0 0 0 41 0 0 0 68% File Part #66... Response: 0 0 0 0 42 0 0 0 69% File Part #67... Response: 0 0 0 0 43 0 0 0 70% File Part #68... Response: 0 0 0 0 44 0 0 0 71% File Part #69... Response: 0 0 0 0 45 0 0 0 72% File Part #70... Response: 0 0 0 0 46 0 0 0 73% File Part #71... Response: 0 0 0 0 47 0 0 0 74% File Part #72... Response: 0 0 0 0 48 0 0 0 76% File Part #73... Response: 0 0 0 0 49 0 0 0 77% File Part #74... Response: 0 0 0 0 4A 0 0 0 78% File Part #75... Response: 0 0 0 0 4B 0 0 0 79% File Part #76... Response: 0 0 0 0 4C 0 0 0 80% File Part #77... Response: 0 0 0 0 4D 0 0 0 81% File Part #78... Response: 0 0 0 0 4E 0 0 0 82% File Part #79... Response: 0 0 0 0 4F 0 0 0 83% File Part #80... Response: 0 0 0 0 50 0 0 0 84% File Part #81... Response: 0 0 0 0 51 0 0 0 85% File Part #82... Response: 0 0 0 0 52 0 0 0 86% File Part #83... Response: 0 0 0 0 53 0 0 0 87% File Part #84... Response: 0 0 0 0 54 0 0 0 88% File Part #85... Response: 0 0 0 0 55 0 0 0 89% File Part #86... Response: 0 0 0 0 56 0 0 0 90% File Part #87... Response: 0 0 0 0 57 0 0 0 91% File Part #88... Response: 0 0 0 0 58 0 0 0 92% File Part #89... Response: 0 0 0 0 59 0 0 0 93% File Part #90... Response: 0 0 0 0 5A 0 0 0 94% File Part #91... Response: 0 0 0 0 5B 0 0 0 95% File Part #92... Response: 0 0 0 0 5C 0 0 0 96% File Part #93... Response: 0 0 0 0 5D 0 0 0 97% File Part #94... Response: 0 0 0 0 5E 0 0 0 98% File Part #95... Response: 0 0 0 0 5F 0 0 0 99% File Part #96... Response: 0 0 0 0 60 0 0 0 100% RADIO upload failed! Ending session... ERROR: Failed to confirm end of file transfer sequence! ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. ERROR: Failed to send end session packet! Are there anyone has done this type of work successfully? Is it related to the flash tools hasn't support this device yet?
not sure if it makes a diff.. but have you rooted your device ?
pileiba said: not sure if it makes a diff.. but have you rooted your device ? Click to expand... Click to collapse Thanks for your reply. Yes I have rooted the device. But as this procedure is in the download mode, is it related to rooted/non-rooted? I just want to try another rom. I have tried another way without modem.bin included and seems all the file could be uploaded to the device now. But I still not sure about why the modem.bin couldn't been flashed
some other solutions I came across where here.. https://github.com/Benjamin-Dobell/Heimdall/issues/43 i.e. to try different versions of heimdell, try a 32bit operating system as opposed to 64 bit, and reinstall the samsung drivers. There is apparently a Heimdell 1.4 . http://www.glassechidna.com.au/2012/devblogs/heimdall-1-4-release-candidate-1/ . Lastly you could try a different usb cable and a different usb port. I think powered hubs sometimes work better.
[Q] P1000 wont boot after overcome
hi there, I've got a problem on my GT-P1000, its bricked.. so i've tried to flash it with odeon.. but on windows it gave me an error.. The tab is well recognized but in every atempt i've made, the error maintains.. heres 2 pics of the procedure. The files ive used were : GB_Stock_Safe_v5 . img546.imageshack.us/img546/2497/image2qy.jpg /img22.imageshack.us/img22/5357/imagegbf.jpg img708.imageshack.us/img708/5387/image15tx.jpg .. after this, when i reboot it loops on samsung logo, or just go black screen with ligths on. Then i've moved out to MAC OS, and tried with heimdall.. and this is the tricky part. using the GB_Stock_Safe_v5 or GB_Stock_Safe_v1 the result is the same... so i dunno if I'm missing some step or what.. 1rst , put it on download mode and connect it . img546.imageshack.us/img546/2497/image2qy.jpg 2nd, on console I manage to install the firmware. img515.imageshack.us/img515/7303/image3ch.jpg No erros, clean install so far. img688.imageshack.us/img688/4596/image4hx.jpg 3rd, I've enter again in download mode, and installed the clockworkmod kernel.. but only service mode appears.. img21.imageshack.us/img21/8845/image6oa.jpg img201.imageshack.us/img201/2470/image7wq.jpg So.. I've putted it again on download mode and installed the slim kernel that i've seen on another thread. And so far so good.. with this I can install via zip the clockworkmod and the Overcome . img845.imageshack.us/img845/8234/image9ly.jpg img839.imageshack.us/img839/2677/image10wc.jpg img832.imageshack.us/img832/9839/image12kf.jpg img27.imageshack.us/img27/1439/image14oy.jpg But then.. no Boot just keeps on this ... If I flash with heimdall only the firmware it keeps looping on Android, or samsung logo.. Can someone help me ?
So on your "2nd" steps, at the end of it you managed to boot into a clean GB JQ1 ROM? (which is what GB stock safe v5) If so, next question, which clockworkmode kernel you flash in step "3rd" better be the zImage that is unpacked from Overcome Kernel 4.0.tar Because you can't just stick any kernel. I just did my own flashing of kernel in linux and it doesn't have those messages you capture $ heimdall flash --kernel ./zImage Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/ Initialising connection... Detecting device... Claiming interface... Attempt failed. Detaching driver... Claiming interface again... Setting up interface... Checking if protocol is initialised... Protocol is not initialised. Initialising protocol... Handshaking with Loke... Beginning session... Session begun with device of type: 0 Downloading device's PIT file... PIT file download sucessful Uploading KERNEL 100% KERNEL upload successful Ending session... Rebooting device... Re-attaching kernel driver...
priyana, nope ! I can't anything.. It will get stuck every time. After flashing in heimdall the GB Stock Safe V5. heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage Click to expand... Click to collapse When i finish this.. this wont boot. Here's the log of heimdall. heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage Claiming interface... Success Setting up interface... Success Beginning session... Handshaking with Loke... Success Uploading PIT PIT upload successful Uploading IBL+PBL 100% IBL+PBL upload successful Uploading SBL 100% SBL upload successful Uploading KERNEL 100% KERNEL upload successful Uploading PARAM 100% PARAM upload successful Uploading FACTORYFS 100% FACTORYFS upload successful Uploading DBDATAFS 100% DBDATAFS upload successful Uploading CACHE 100% CACHE upload successful Ending session... Rebooting device... Click to expand... Click to collapse Note : When it reboot's a voice says: "not enough space on partition, bla bla bla, restore operation, your ... is now activated" and it enter on Android system recovery. Now after this I flashed with Overcome_Kernel_v4.0.0.tar. Here's the heimdall log : heimdall flash --kernel zImage --verbose Manufacturer: "SAMSUNG" Product: "Gadget Serial" length: 18 device class: 2 S/N: 0 VIDID: 04E8:6601 bcdDevice: 021B iMan:iProd:iSer: 1:2:0 nb confs: 1 interface[0].altsetting[0]: num endpoints = 1 Class.SubClass.Protocol: 02.02.01 endpoint[0].address: 83 max packet size: 0010 polling interval: 09 interface[1].altsetting[0]: num endpoints = 2 Class.SubClass.Protocol: 0A.00.00 endpoint[0].address: 81 max packet size: 0200 polling interval: 00 endpoint[1].address: 02 max packet size: 0200 polling interval: 00 Claiming interface... Success Setting up interface... Success Beginning session... Handshaking with Loke... Success Downloading device's PIT file... PIT file download sucessful Uploading KERNEL 0%File Part #0... Response: 0 0 0 0 0 0 0 0 File Part #1... Response: 0 0 0 0 1 0 0 0 File Part #2... Response: 0 0 0 0 2 0 0 0 File Part #3... Response: 0 0 0 0 3 0 0 0 File Part #4... Response: 0 0 0 0 4 0 0 0 File Part #5... Response: 0 0 0 0 5 0 0 0 File Part #6... Response: 0 0 0 0 6 0 0 0 File Part #7... Response: 0 0 0 0 7 0 0 0 File Part #8... Response: 0 0 0 0 8 0 0 0 File Part #9... Response: 0 0 0 0 9 0 0 0 File Part #10... Response: 0 0 0 0 A 0 0 0 File Part #11... Response: 0 0 0 0 B 0 0 0 File Part #12... Response: 0 0 0 0 C 0 0 0 File Part #13... Response: 0 0 0 0 D 0 0 0 File Part #14... Response: 0 0 0 0 E 0 0 0 File Part #15... Response: 0 0 0 0 F 0 0 0 File Part #16... Response: 0 0 0 0 10 0 0 0 File Part #17... Response: 0 0 0 0 11 0 0 0 File Part #18... Response: 0 0 0 0 12 0 0 0 File Part #19... Response: 0 0 0 0 13 0 0 0 File Part #20... Response: 0 0 0 0 14 0 0 0 File Part #21... Response: 0 0 0 0 15 0 0 0 File Part #22... Response: 0 0 0 0 16 0 0 0 File Part #23... Response: 0 0 0 0 17 0 0 0 File Part #24... Response: 0 0 0 0 18 0 0 0 File Part #25... Response: 0 0 0 0 19 0 0 0 File Part #26... Response: 0 0 0 0 1A 0 0 0 File Part #27... Response: 0 0 0 0 1B 0 0 0 File Part #28... Response: 0 0 0 0 1C 0 0 0 File Part #29... Response: 0 0 0 0 1D 0 0 0 File Part #30... Response: 0 0 0 0 1E 0 0 0 File Part #31... Response: 0 0 0 0 1F 0 0 0 File Part #32... Response: 0 0 0 0 20 0 0 0 File Part #33... Response: 0 0 0 0 21 0 0 0 File Part #34... Response: 0 0 0 0 22 0 0 0 File Part #35... Response: 0 0 0 0 23 0 0 0 File Part #36... Response: 0 0 0 0 24 0 0 0 KERNEL upload successful Ending session... Rebooting device... Click to expand... Click to collapse At this point, its reboots again to System Recovery .. I restart the tab, Galaxy TAB Logo appears with Samsung under... the voice comes again " not enough space on partition bla bla " ... Samsung spinning logo apears and stuckk... ! Looks like a loop on logo, and doesnt do anything.
Search again for my last post on "heimdall flash", about less than a week ago. You might have followed one of my bad earlier example command line ( although I don't think it matters for flashing overcome kernel). Notice you stick hidden.rfs into dbdata like I once did. Should have one for --hidden and one for --dbdata Sent from my GT-I9300 using xda app-developers app
Notice you stick hidden.rfs into dbdata like I once did. Should have one for --hidden and one for --dbdata Click to expand... Click to collapse Thank you for the reply.. but should I assign hidden.rfs twice for different parameters ?
There is a dbdata.rfs Sent from my GT-I9300 using xda app-developers app
priyana said: There is a dbdata.rfs Sent from my GT-I9300 using xda app-developers app Click to expand... Click to collapse Still the same.. it's getting stuck on samsung logo.
Grab a windows machine and try Odin. Drivers and Odin are included in gb-stock-safe-v5 Or, just try out CM/AOKP. By now, you should have overcome kernel installed, that means you can boot to CWM recovery. boot to it and flash cm10/aokp or any custom ROM, then flash the rom zip file (you may need to do it 3 times, depending on the steps within the updater script), then flash gapps and reboot into a new ROM. For me, doing the GB-stock-safe-v5 + overcome for all intent and purposes are just to "restock" the partition and to install CWM. Sent from my GT-P1000 using xda app-developers app
[WANTED] File Recovery after Deletion
Good morning, lovely HTC ONE owners! Yesterday, I manually deleted a folder from my HTC ONE containing an important file. I have tried finding a software or app to restore that folder, but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE. Is there any chance to get back my data? In the future, I will use the app 'Dumpster', which only throws files into a special trash bin where files can be restored if necessary...
SecUpwN said: but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE. Click to expand... Click to collapse which filesystem?
We need to know which file you deleted
tryin said: which filesystem? Click to expand... Click to collapse Thanks for helping, guys. The HTC ONE doesn't have an SD card, thus only offering 32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong.
matt95 said: We need to know which file you deleted Click to expand... Click to collapse A file inside a folder with the extension *.bck - it was a settings file created by another app. It is important to me because it contains phone numbers I have not written down. What to do?
I don't think you'll get it back man....
matt95 said: I don't think you'll get it back man.... Click to expand... Click to collapse Darn. Maybe it's gods will. For other peeps reading this: Install DUMPSTER to avoid deletion without being able to recover files. This recycle bin will keep your deleted files for a set amount of time and delete them for good afterwards. If I had only known this app before, this wouldn't have happened.
SecUpwN said: ...32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong. Click to expand... Click to collapse No filesystem..!? Mmm it sound a bit strange... . There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files...
tryin said: No filesystem..!? Mmm it sound a bit strange... . There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files... Click to expand... Click to collapse I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery?
SecUpwN said: I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery? Click to expand... Click to collapse :/ $ mount rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 none /dev/timer_group cgroup rw,relatime,timer_slack 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,seclabel,relatime 0 0 selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0 /sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0 none /acct cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0 tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0 /dev/block/dm-0 /mnt/asec/com.nuance.swype.dtc-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0 /dev/block/dm-1 /mnt/asec/stericson.busybox.donate-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0 /dev/block/dm-2 /mnt/asec/com.gameloft.android.ANMP.GloftA8HM-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0 /dev/block/dm-3 /mnt/asec/com.eclipsim.gpstoolbox.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0 /dev/block/dm-4 /mnt/asec/com.koushikdutta.backup.license-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0 /dev/block/dm-5 /mnt/asec/com.eightyeightgames.tenmillion-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0 tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0 /dev/block/mmcblk0p35 /system ext4 ro,seclabel,noatime,nobarrier 0 0 /dev/block/mmcblk0p37 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc 0 0 tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0 tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0 tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0 DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0 /dev/block/mmcblk0p36 /cache ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier 0 0 /dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,errors=continue,data=ordered 0 0 /dev/block/mmcblk0p31 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0 /dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0 /dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0 /dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 /dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 /dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 /dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
@BenPope, what's that supposed to be?
SecUpwN said: @BenPope, what's that supposed to be? Click to expand... Click to collapse That would be the list of filesystems, their mount points and parameters on my phone. As you can see, it's not as simple as "a filesystem".
It is possible, try this guide: htc phone photo file recovery hope this helps.
jackthomas251 said: From phone it's much more complicated. Click to expand... Click to collapse But not impossible?
Re: File Recovery after Deletion I have also done this kind of mistake previously then my friend told me about Remo Android Recovery software and seriously it worked for me as a miracle. I got back all my accidentally deleted photos. You can give a try to this to recover your deleted folder. Hope you will get success.
This topic is like more than a month old, I guess there's nothing to rescue anymore. But thanks for the hints, everyone should install DUMPSTER beforehand.
Even worse.... I deleted storage/emulated/0 folder on my htc one Ok. So check this ish..... I was tryna free up room on my htc one, so i went into file manager, was lookin for unnecessary stuff to delete, and thats when i notice.. Inside the emulated folder are 2 folders, one named "0" and one named "legacy" so after going back and forth one to the other... I realized that the same exact files and folders as the other, so my retarded asss deleted one thinking it was a whole duplicated folder. Ok, yeah, i messed that one up bad. How could i be so stupid? So i looked up some claims of some solutions, downloaded the pc software they swore would recover everything. Nada... Zip. Zero... What can i do? The htc one is no removable sd card or battery and my phone is not rooted.... Please get back at me on this... Im beginning to think,an htc csr or one of the smartest phone dudes on this forum will know how or what to do... :crying::crying::angel:
Oh yeah i forgot.... I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something
datbitch said: I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something Click to expand... Click to collapse Sorry pal, no chance to recover anything. If you continued to use your phone after erasing all of that, it has been overwritten multiple times already. To make sure such thing does not happen again, install ES File Explorer and enable the RECYCLE BIN in the options - thus, you can recover deleted files easily. And for cleaning your device, always use SD Maid.
TWRP for Samsung Galaxy Z Fold2 5G (F916B)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Welcome to TWRP for the Samsung Galaxy Z Fold2 5G. Samsung were kind enough to release the kernel source code ahead of the device itself, which enabled me to have TWRP ready and waiting when the courier rang my doorbell with my new phone. It's not often that a device sees a day 0 TWRP release.
The image of TWRP available here will work on all F916B, F916N and F9160 devices.
Installation
Only proceed if you are comfortable with low-level device management and are capable of recovering an unbootable device, should an unforeseen mishap occur.
Unlock your device's bootloader and then install the recovery image below. If you use Odin to flash it, remember to rename the image recovery.img and tar it before flashing. You will also need to flash a neutralised vbmeta.img image if you have not already disarmed verified boot.
Post-installation
The Z Fold2 5G utilises proprietary file-based encryption (FBE) in its factory state for the user data partition. TWRP cannot decrypt this, however, so it must be removed. Otherwise, you will not be able to perform back-ups and restores.
To remove encryption from your device, please use TWRP to flash the Samsung multi-disabler and then format /data again. You must use at least v2.5 of the multi-disabler.
Latest releases
These builds are stable and known to perform well on many users' devices.
Android 11 (CTLL firmware)
twrp-f2q-3.5.0_10-A11_3_ianmacd.img
Android 10 (BTJ1 firmware)
twrp-f2q-3.5.0_10-2_ianmacd.img
Known issues
TWRP is displayed only on the device's main (inner) screen.
Haptic feedback does not work.
Source
TWRP device tree for the Galaxy Z Fold2 5G (F916B)
Kernel source code for the Galaxy Z Fold2 5G (F916B)
TWRP source code
Support
For support or just to talk about the device amongst friends, please join our small Telegram group dedicated to the full range of Galaxy foldable devices.
Support may also be found in the more general Samsung TWRP/root group.
XDA:DevDB Information
TWRP for the Samsung Galaxy Z Fold2 5G, Tool/Utility for the Samsung Galaxy Z Fold2
Contributors
ianmacd
Version Information
Status: Production
Current Production Version: 3.5.0-1_ianmacd
Production Release Date: 2020-12-29
Created 2020-09-16
Last Updated 2021-01-25
Changelog 2021-01-25 3.5.0_A11-3 Fix spurious attempt to perform digest authentication when flashing .apk file. 2021-01-25 3.5.0_A11-2 TWRP will now include files named Magisk.apk, app-release.apk or app-debug.apk in the list of flashable .zip files. This is to accommodate the new packaging of Magisk as a payload within the manager app. 2021-01-19 3.5.0_A11-1 First release for Android 11. With kernel built for CTLL firmware. 2021-01-19 3.5.0-2 Merge post-3.5.0 release bug fixes. 2020-12-29 3.5.0-1 Update to TWRP 3.5.0. 2020-12-23 3.4.0-3 Fixed bug that causes unmounting of System when Advanced menu is entered. 2020-12-20 3.4.0-1 First production release. Working MTP implementation. 2020-11-06 3.4.0-1a20 Fixed image back-up of Optics partition. logcat is now enabled in recovery. With kernel built for BTJ1 firmware. 2020-10-07 3.4.0-1a17 With kernel built for BTIA firmware. 2020-09-29 3.4.0-1a15 Ignore touch sensor input from front screen. Align camera recess within status bar. 2020-09-15 3.4.0-1a12 Day 0 TWRP release.
@ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model?
Apo11on said: @ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model? Click to expand... Click to collapse The U models have their bootloaders locked. The B version is an international (korean?) version which can have it's bootloader unlocked. Correct me if I am wrong
Apo11on said: @ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model? Click to expand... Click to collapse similar topic discussed in TG group, FYI ME（Vincent Li）：Hi Ian! @ianmacd I have a silly question wanna ask: is it compatible to flash your twrp image into my F9160(Chinese variant) model after rooting? Click to expand... Click to collapse 鱿鱼：[In reply to Vincent Li] I think you’ll need to check the partition structure before flashing if I remember correctly Click to expand... Click to collapse ME：[In reply to 鱿鱼] I'm not sure whether I understand correctly or not that the partition structure would be the same across different variants (aka F916B/916U/F9160 etc.) as long as they share the same model name like Z Fold2 5G, although those variants might have different firmwares or kernels with which may affect this twrp image working properly? Click to expand... Click to collapse Ian Macdonald：[In reply to Vincent Li] I don't know how the F9160 differs from the F916B. The firmware would certainly be different, but the recovery environments need not be. You don't have much to lose by trying it. If it doesn't work, just flash the stock recovery back. You could also request kernel source code for your model from Samsung; then we can compare them. As of now, only the F916B has source code available, because I requested it before release. Click to expand... Click to collapse
Apo11on said: @ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model? Click to expand... Click to collapse @ianmacd Houston, do you readme? Can you please confirm the list of devices, supported by your build? Over. Here is a full list of mounted partitions on my F916U1 - hope it helps. Code: $ cat /proc/mounts /dev/block/dm-4 / ext4 ro,seclabel,relatime,i_version 0 0 tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=5378544k,nr_inodes=1344636,mode=755 0 0 devpts /dev/pts devpts rw,seclabel,relatime,mode=600,ptmxmode=000 0 0 none /dev/memcg cgroup rw,relatime,memory 0 0 none /dev/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 none /dev/cg2_bpf cgroup2 rw,nosuid,nodev,noexec,relatime 0 0 none /dev/cpuctl cgroup rw,nosuid,nodev,noexec,relatime,cpu 0 0 none /dev/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0 none /dev/stune cgroup rw,nosuid,nodev,noexec,relatime,schedtune 0 0 none /dev/freezer cgroup rw,relatime,freezer 0 0 adb /dev/usb-ffs/adb functionfs rw,relatime 0 0 proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0 sysfs /sys sysfs rw,seclabel,relatime 0 0 selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0 debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0 tracefs /sys/kernel/debug/tracing tracefs rw,seclabel,relatime 0 0 bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime 0 0 pstore /sys/fs/pstore pstore rw,seclabel,nosuid,nodev,noexec,relatime 0 0 tmpfs /mnt tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755,gid=1000 0 0 tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=5378544k,nr_inodes=1344636,mode=700 0 0 tmpfs /mnt/sde tmpfs rw,seclabel,relatime,size=5378544k,nr_inodes=1344636,mode=700 0 0 /dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/efs /mnt/vendor/efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /data/knox/secure_fs/enc_media /mnt/shell/enc_emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1000,fsgid=1000,gid=9997,multiuser,derive_gid,default_normal,reserved=20MB 0 0 /data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0 /data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0 /data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0 /data/media /mnt/runtime/full/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0 tmpfs /apex tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755 0 0 /dev/block/loop2 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop2 /apex/com.android.conscrypt ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop3 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop3 /apex/com.android.apex.cts.shim ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop4 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop4 /apex/com.android.runtime ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop5 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop5 /apex/com.android.media ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop6 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop6 /apex/com.android.media.swcodec ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop7 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop7 /apex/com.android.resolv ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop8 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/loop8 /apex/com.android.tzdata ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0 /dev/block/platform/soc/1d84000.ufshc/by-name/metadata /metadata ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/dm-5 /product ext4 ro,seclabel,relatime,i_version 0 0 /dev/block/dm-6 /vendor ext4 ro,seclabel,relatime,i_version 0 0 /dev/block/bootdevice/by-name/apnhlos /vendor/firmware_mnt vfat ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0 /dev/block/bootdevice/by-name/modem /vendor/firmware-modem vfat ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0 /dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,seclabel,nosuid,nodev,relatime,i_version 0 0 /dev/block/dm-7 /odm ext4 ro,seclabel,relatime,i_version 0 0 /dev/block/dm-8 /prism ext4 ro,seclabel,relatime,i_version 0 0 /dev/block/dm-9 /optics ext4 ro,seclabel,relatime,i_version 0 0 none /acct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct 0 0 none /config configfs rw,nosuid,nodev,noexec,relatime 0 0 /dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/sec_efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/dqmdbg /dqmdbg ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/spu /spu ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/keydata /keydata ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/keyrefuge /keyrefuge ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/omr /omr ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0 /dev/block/bootdevice/by-name/userdata /data f2fs rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,reserve_root=32768,reserve_core=1280,resuid=0,resgid=5678,usrquota,grpquota,alloc_mode=default,fsync_mode=nobarrier 0 0 tmpfs /storage tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755,gid=1000 0 0 /data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0 tmpfs /storage/self tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755,gid=1000 0 0 $
Apo11on said: @ianmacd Houston, do you readme? Can you please confirm the list of devices, supported by your build? Over. Click to expand... Click to collapse It will work on the F916B. It may also work on the F9160 and the F916N. As far as US versions are concerned, the U and U1 models have locked bootloaders that can only be unlocked using a paid service. Once that has been done, this version of TWRP may work on them. I can't say with any more certainty than that, because my own device is the international model, the F916B. Even if this version doesn't work on the 9160, the N, the U and the U1, it wouldn't be a huge amount of work to make those work, too; probably just a question of replacing the kernel with one specific to those devices.
ianmacd said: It will work on the F916B. It may also work on the F9160 and the F916N. As far as US versions are concerned, the U and U1 models have locked bootloaders that can only be unlocked using a paid service. Once that has been done, this version of TWRP may work on them. Click to expand... Click to collapse Do you happen to know of this paid service or where it's available? Depending on the price, I would be willing to consider paying to have the phone unlocked if that's what needs to be done.
WyldOne91 said: Do you happen to know of this paid service or where it's available? Depending on the price, I would be willing to consider paying to have the phone unlocked if that's what needs to be done. Click to expand... Click to collapse +1 was going to ask the exact same question
WyldOne91 said: Do you happen to know of this paid service or where it's available? Depending on the price, I would be willing to consider paying to have the phone unlocked if that's what needs to be done. Click to expand... Click to collapse I have never used this service and cannot vouch for its effectiveness or safety. https://labs.xda-developers.com/store/app/tk.zwander.galaxyunlock
ianmacd said: I have never used this service and cannot vouch for its effectiveness or safety. https://labs.xda-developers.com/store/app/tk.zwander.galaxyunlock Click to expand... Click to collapse Thanks for the warning, at the very least I'll check it out.
Hi @ianmacd how would we go about flashing gsi roms with the new twrp since system slot is now gone ---------- Post added at 06:04 PM ---------- Previous post was at 06:03 PM ---------- Hi @ianmacd how would we go about flashing gsi roms with the new twrp since system slot is now gone
TheUndertaker21 said: Hi @ianmacd how would we go about flashing gsi roms with the new twrp since system slot is now gone Click to expand... Click to collapse You have to flash the super partition now. The System partition is a logical partition inside the super partition, along with Vendor, Product and Odm.
ianmacd said: You have to flash the super partition now. The System partition is a logical partition inside the super partition, along with Vendor, Product and Odm. Click to expand... Click to collapse Oh word Is there a tool that can turn these system img into super partition? Thanks again
ianmacd said: It will work on the F916B. It may also work on the F9160 and the F916N. As far as US versions are concerned, the U and U1 models have locked bootloaders that can only be unlocked using a paid service. Once that has been done, this version of TWRP may work on them. I can't say with any more certainty than that, because my own device is the international model, the F916B. Even if this version doesn't work on the 9160, the N, the U and the U1, it wouldn't be a huge amount of work to make those work, too; probably just a question of replacing the kernel with one specific to those devices. Click to expand... Click to collapse Can confirm for the F916U that it does not work. At least in Odin it gets stuck on "File Analysis" and nothing happens. EDIT: Nevermind it works fine on F916U
Chickenbone20 said: Can confirm for the F916U that it does not work. At least in Odin it gets stuck on "File Analysis" and nothing happens. Click to expand... Click to collapse Did you rename the image recovery.img and tar it? You don't stand a chance of it working if you didn't do that.
3.4.0-1a15 released. I have just released a new alpha build of TWRP. This one fixes the issue of touch sensor input from the front screen not being ignored. If you experienced any ghost touch input issues when using TWRP while holding the device in your hand, this is the reason.
I can't access to files on storage or sdcard so i can't flash anything... how can i resolve this?
Just curious what the chances are that this work will develop into granting us mortals the ability to root and install custom roms?
@Chickenbone20 wondering if you unlocked the bootloader or without it? i am in the process of buying us model or international model. Thanks