Update: the VZW Ignore 10.1 is now boot loader unlocked and jail broken using the technique and software I outlined in this thread:
http://forum.xda-developers.com/showthread.php?p=41016954
I'm locking this because its done. Use the report button to report this thread to have it unlocked if you need to.
Hey guys,
I just received this device last night, gave it the obligatory teardown, and I'm in the process of collecting resources. From what I can see about the hardware overview, the device is quite similar to the Verizon Galaxy Note 2. However, the process will not be exactly the same as Galaxy Note 2 for several reasons.
1. Exynos Abuse cannot be triggered without a signed kernel of the proper variant. So there will be no Exynos Abuse. However, This http://forum.xda-developers.com/showthread.php?t=2186177 may function similarly.
2. We need an SBoot.bin so @Ralekdev can get started on code-smithing a new bootloader for the device.
3. The partitions may not be mapped the same.
4. A recovery is required which is functional and I have yet to figure out if there is a hardware difference between the i925 and the other variants of this device.
So, my team just needs an Sboot.bin and a Partition Information Table in order to get started. I have high confidence that we can make this a one-click.
Here's some partition info I've gathered so far.
Code:
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 m9kefs3 -> /dev/block/mmcblk0p6
Looks like UART is enabled by default so there should be a pin which can be monitored on the dock connector during startup.
Code:
console=ttySAC2,115200 loglevel=4 androidboot.baseband=mdm
and here's a zip containing the partitions themselves. I removed my own EFS from there though.
Code:
http://d-h.st/SPx
Update. Was able to pull the pit from the device.. http://d-h.st/dRR Its unclean but it will do for now.
Still need the Sboot
Finally, a developer for our variant.
Sent from my SCH-I925 using xda premium
This is outstanding, we are getting some love, thanks adam and the rest of the team. This model has some serious potential over some of the other model numbers that are out there being produced right now. I love this thing, never thought Id like a tablet, but this thing kills it. Thanks adam and Ill be sending a few beers at you.
Thanks Adam u guys kick a$$. Suckitverizon!!
TaPpEd from my TwEaKeD N2
I'm new to this Note 10.1 (just got it from vzw today). So Adam is working to get the VZW version of the Note10.1 unlocked?
Sent from my Galaxy Nexus using xda app-developers app
omfgbfs said:
I'm new to this Note 10.1 (just got it from vzw today). So Adam is working to get the VZW version of the Note10.1 unlocked?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Sure looks that way. Just like the n2. Verizon better get to work to keep up with those guys!!!
TaPpEd from my TwEaKeD N2
I built a recovery and pulled a pit (which it sounds like you did too) for this mid March for a user but obviously no way to boot and test it yet so ymmv and take caution with it. They're obscuring the partitions that contain the sboot and the storage driver is compiled directly into the kernel. I spoke with ralekdev a bit about this device last month but without the sboot there was nothing to do yet. If you guys get the BL working hit me up and I'll fix up any issues in recovery that might exist.
I sourced the sboot.bin from the korean LTE variant of the tab and offered that last month too as perhaps it could be used but never heard back from him. So that file might be of interest if it could be used on the i925, else probably need to wait for an OTA from big red. I'll defer to someone with far more knowledge in ida pro. If it is, should be easy to leverage similar ideas used before on exynos4 devices to get a working BL. If it's not, at least the recovery I made should help someone.
Attached are the files from the work I started:
good luck with it.
I noticed in your tear down of SCH-I925 The N8020 label on more than 2 locations of the mainboad. This suggests to me that we are dealing with a Verizonized GT-N8020? Are the sboot.bin and recovery.img from the published N8020 any benefit your efforts? Forgive my newbeness
Sent from my GT-N8020 using XDA Premium HD app
waston2013 said:
I noticed in your tear down of SCH-I925 The N8020 label on more than 2 locations of the mainboad. This suggests to me that we are dealing with a Verizonized GT-N8020? Are the sboot.bin and recovery.img from the published N8020 any benefit your efforts? Forgive my newbeness
Sent from my GT-N8020 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, im sure they are. The problem here is there is no clear path back to stock. We have the required tools to test an unlock right now. @Ralekdev could whip up a new bootloader for the Exynos that would function on this device fairly easily.
The problem is that the Verizon Modem does not play nicely with other bootloaders. So you'd end up with a device which continuously reboots or works as a wifi-only model. And we can do that. But theres still no way to get it back to stock.
Hell, maybe we should just release it like that, provide a tool which will brick the device, and let the RMAs handle it. But the proper way is to get a stock bootloader.
Ok. With that said, I have a sacrificial SCH-I925 sent to me by Verizon by accident (long stoy). Can we succesfully make it an N8020 without concern of returning to stock? I have tried to flash stock N8020 through odin, ofcourse unsuccessfully.
I have rooted and run Triangle Away on another SCH-I925 leaving me with a Note that said "unauthorized software detected, please return to nearest Verizon store" I did and they replaced with the Note I am using now.
With explicit instructions I can attempt to prove any and all of your THEORIES on this "extra SCH-I925" I have. As I am not a developer please be detailed.
Best regards [email protected]
Sent from my SCH-I925 using XDA Premium HD app
waston2013 said:
Ok. With that said, I have a sacrificial SCH-I925 sent to me by Verizon by accident (long stoy). Can we succesfully make it an N8020 without concern of returning to stock? I have tried to flash stock N8020 through odin, ofcourse unsuccessfully.
I have rooted and run Triangle Away on another SCH-I925 leaving me with a Note that said "unauthorized software detected, please return to nearest Verizon store" I did and they replaced with the Note I am using now.
With explicit instructions I can attempt to prove any and all of your THEORIES on this "extra SCH-I925" I have. As I am not a developer please be detailed.
Best regards [email protected]
Sent from my SCH-I925 using XDA Premium HD app
Click to expand...
Click to collapse
@Ralekdev should have something tonight. I'll package it up and get it ready for distribution. If you'd like to beta, send me an email via my profile. It will be later tonight at earliest.
Its coming
Anyone who would like to pre-test can do so.
You must have java installed on your computer then run this: http://d-h.st/q2R
I'm preparing a post right now. The unlock was similar to the Galaxy Note 2 in most respects.
http://forum.xda-developers.com/showthread.php?p=41016954
AdamOutler said:
Anyone who would like to pre-test can do so.
You must have java installed on your computer then run this: http://d-h.st/q2R
I'm preparing a post right now. The unlock was similar to the Galaxy Note 2 in most respects.
Click to expand...
Click to collapse
This worked for me Adam. Thanks again to you and all how contributed to this
waston2013 said:
This worked for me Adam. Thanks again to you and all how contributed to this
Click to expand...
Click to collapse
Great! Would you be so kind as to post in here? http://forum.xda-developers.com/showthread.php?p=41016954
This thread is done now. I will update the first post.
Related
I got message from tmobile saying I had used over 10GB this month, which seemed not right to me.
Looking at my bandwidth usage on tmobile's site I saw lots of 40 MB downloads. So I ran tcpdump on the phone for a while and it looks like maybe my phone keeps downloading an update several times a day from google?
There is a GET /updates/signed-kila-ota-150275.53dde3 to IP of 74.125.47.101 .
I am using a JF build: 1.5 CRB 21 147201 test-keys.
Anyone know why this is happening if what I think is happening is in fact happening Or how I might stop it?
Also, I didn't delete the oacerts or cacerts files:
# ./bash
bash-4.0# cd /system/etc/security/
bash-4.0# ls -l
-rw-r--r-- 1 0 0 47159 Aug 1 2008 cacerts.bks
-rw-r--r-- 1 0 0 1107 Aug 1 2008 otacerts.zip
You could try 1 of 3 of JF's solutions:
1. delete the otacerts.zip file manually. The file is at /system/etc/security/otacerts.zip But keep in mind if you use this method your phone will continuously re-down the OTA and try to verify it, which is bad on your bandwidth usage and your battery life
2. Replace /system/build.prop on your phone with the one from the ADP1 version of JFv1.51
3. chmod 000 the OTA file in /cache (unconfirmed solution, but is likely to work)
Click to expand...
Click to collapse
EDIT: actually not the first one since thats what you're trying to avoid
::::::::::::::::::::::::::::::::::::::::::EDIT::::::::::::::::::::::::::::::::::::::::::
i was out for my job and was busy guys......but im again initiating this discussion.................
now im using a 8 gb external sdcard with 1 gb ext4 partition and 7 gb storage...with offcourse modified vold.fstab.......everything works what should in cm7.....im happy and can live with it ......but im tempted to use gps and also want to get good battery life now
so i installed cm7 partitioned external sd with 1 gb ext4 7 gb fat32 storage then odined to 2.2 rom and changed the vold.fstab file......i get 7 gb storage partition mounted but the 1 gb data partition is not mounted.....i tried converting to jfs also from eugenes kernel but it still does not mounts......anyone know how can we mount /data from the external sd partition?? any help from dev side would be highly appreciated .....im noob at linux.... please share opinions.....
PS:my primary aim is to load a 2.2 rom and use it WITHOUT internal sdcard.....
also since i have /system partition inside phone memory...is it possible for the nand to be damaged?? i guess /system partition and other /cache partitions all are in the nand.....am i correct?? maybe we only messed mbr!!!
ANY OPINIONS ARE WELCOMED
#####################################################
#####################################################
OLD POST:
For the background....my samsung vibrant bootlooped after installing dow kernel....after that I was unable to mount my internal....the 16 gb space disappeared.....however I can boot to eugenes froyo 2e recovery rom....nothing else boots the phone.
.i am not linux guy but have some programming skills....so after reading some threads was able to mount external sd as internal sdcard...im happy that the phone is 70 % working as I can listen to music and click photos and record my jam with voodoo soundfix.ps I flashed deadhorse succesfully.....
Now the thinktank part comes.....
can anyone help me mount /data at the external card. which files do I need to edit...
Where should I start?
also I have a feeling that the movinand cannot be damaged that fast.any way of resetting the memory manually?
give any thoughts but dont say send it to tmobile.....im at the opposite side of the globe from USA.......I need to fix it as far as possible and use it.
For those in same situation here is the file....
copy it to /etc folder either from adb or root explorer
it will mount ur external as internal
http://db.tt/eprA3cg
cheers
manjish said:
For the background....my samsung vibrant bootlooped after installing dow kernel....after that I was unable to mount my internal....the 16 gb space disappeared.....however I can boot to eugenes froyo 2e recovery rom....nothing else boots the phone.
.i am not linux guy but have some programming skills....so after reading some threads was able to mount external sd as internal sdcard...im happy that the phone is 70 % working as I can listen to music and click photos and record my jam with voodoo soundfix.ps I flashed deadhorse succesfully.....
Now the thinktank part comes.....
can anyone help me mount /data at the external card. which files do I need to edit...
Where should I start?
also I have a feeling that the movinand cannot be damaged that fast.any way of resetting the memory manually?
give any thoughts but dont say send it to tmobile.....im at the opposite side of the globe from USA.......I need to fix it as far as possible and use it.
For those in same situation here is the file....
copy it to /etc folder either from adb or root explorer
it will mount ur external as internal
###Will upload when I get home.....cant do it from vibrant....
cheers
Click to expand...
Click to collapse
tempted to see this. Might be able to add onto it to get External mounting inside the internal for Frost.
Do we have a copy of what the the device mappings *should* look like? Someone commented that what our phones are actually trying to map looks like an I9000 instead of a Vibrant.
My previous android hacking has been with a chinese tablet. I don't know what partition numbers should go where on the Vibrant.
An additional thought for anyone it might help. As I was trying to troubleshoot this mess on my phone I noticed a difference between Eugene's ROM (that will boot) and the other ROMs I tried. May or may not be important but Eugene's ROM is overwriting almost all of the partitions. The other ROMs I've looked at just overwrote two or three. Eugene's doesn't overwrite the Recovery partition.
If this were my tablet I would be looking for a good dd image dump of /dev/block/mmcblk0p4 to also overwrite the Recovery partition. I don't know what that should be on the Vibrant. (I have a dd dump of my system partition from the Vibrant but not the other partitions.)
Anyone got a partition map or chart?
tekowalsky said:
Do we have a copy of what the the device mappings *should* look like? Someone commented that what our phones are actually trying to map looks like an I9000 instead of a Vibrant.
My previous android hacking has been with a chinese tablet. I don't know what partition numbers should go where on the Vibrant.
An additional thought for anyone it might help. As I was trying to troubleshoot this mess on my phone I noticed a difference between Eugene's ROM (that will boot) and the other ROMs I tried. May or may not be important but Eugene's ROM is overwriting almost all of the partitions. The other ROMs I've looked at just overwrote two or three. Eugene's doesn't overwrite the Recovery partition.
If this were my tablet I would be looking for a good dd image dump of /dev/block/mmcblk0p4 to also overwrite the Recovery partition. I don't know what that should be on the Vibrant. (I have a dd dump of my system partition from the Vibrant but not the other partitions.)
Anyone got a partition map or chart?
Click to expand...
Click to collapse
major minor #blocks name
7 0 3150 loop0
7 1 3150 loop1
7 2 13545 loop2
7 3 2111 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 3150 loop6
7 7 5229 loop7
139 0 513024 tfsr0/c
139 1 256 tfsr1
139 2 256 tfsr2
139 3 10240 tfsr3
139 4 1280 tfsr4
139 5 1280 tfsr5
139 6 5120 tfsr6
139 7 7680 tfsr7
139 8 7680 tfsr8
139 9 293376 tfsr9
139 10 137216 tfsr10
139 11 35840 tfsr11
139 12 12800 tfsr12
179 0 15630336 mmcblk0
179 1 13664224 mmcblk0p1
179 2 1966080 mmcblk0p2
137 0 513024 bml0/c
137 1 256 bml1
137 2 256 bml2
137 3 10240 bml3
137 4 1280 bml4
137 5 1280 bml5
137 6 5120 bml6
137 7 7680 bml7
137 8 7680 bml8
137 9 293376 bml9
137 10 137216 bml10
137 11 35840 bml11
137 12 12800 bml12
138 3 6400 stl3
138 6 1280 stl6
138 9 284672 stl9
138 10 131584 stl10
138 11 32000 stl11
179 8 15558144 mmcblk1
179 9 15554041 mmcblk1p1
254 0 3150 dm-0
254 1 3150 dm-1
254 2 13545 dm-2
254 3 2110 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 3150 dm-6
254 7 5229 dm-7
7 8 18743 loop8
254 8 18742 dm-8
7 9 16664 loop9
254 9 16663 dm-9
7 10 2111 loop10
254 10 2110 dm-10
7 11 8348 loop11
254 11 8347 dm-11
7 12 3150 loop12
254 12 3150 dm-12
adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"
adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"
adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
When this happend to me I just went into download mode and flashed a stock kernel with odin. was that just not possible for you?
You got lucky if the same thing happened to you. In most cases the zapped internal SD issue didn't happen when we flashed the DOW. In my case I ran the DOW kernel for a week to ten days. One day my phone was totally unresponsive (black screen, no lights, no response from any buttons including the power button). I pulled the battery and it was fine. It happened again another day. Again, pulled the battery and it was fine.
The third time this crash happened after pulling the battery my phone froze on the bionix robot girl at boot. I tried pulling the battery because nothing else worked. Same thing -- stuck at bionix girl.
I tried to flash a stock kernel. After flashing the stock kernel with Odin (successfully Odin said) my phone would power up to the Vibrant logo then shut off after displaying the vibrant logo for 1 second. If I plugged my phone in the battery logo would loop as though the phone were continually resetting.
I repeated the Odin flash four or five times to stock with the same results. Every time Odin said the flash was successful. I tried a different computer. Same result. I tried a different stock kernel. Same result.
The only ROM I found that will boot my phone is Eugene's. I tried flashing stock after Eugene's Froyo. My phone went right back to the logo/1 second/power off behavior. Flash back to Euguene's Froyo and my phone would boot.
I tried to boot to Recovery. My phone would not boot to Recovery except if I have Eugene's Froyo installed. I tried to ADB to my phone - works under Eugene's Froyo but not under any other ROM I've tried.
With Eugene's Froyo I discovered my phone said it had 0 MB application storage space and was not mounting either internal or external SD card. Each time I reboot my phone it loses my accounts and most settings. Oddly it keeps some settings like the static IP address for my wifi connection -- but not the password for my wifi network.
After further investigation I found my phone recognizes the external SD card but so far I have not found any way to access the internal SD card. My phone does not recognize the internal SD exists.
The trick with changing the vold.fstab to map the external SD to /mnt/sdcard gets the External SD card mounted and tricks the phone some but doesn't get back any application storage.
These symptoms match a whole group of us who installed Team Whiskey's DOW kernel. We've posted on Team Whiskey's forum and last I checked gotten no response. Team Whiskey still had the DOW kernel available for download.
Search XDA for "DOW sd" and you'll find a bunch of related threads.
Hi guys just to let you know......you can flash bionix rom by installing it through cwm recoyery...open the zip file from windows explorer....inside system/etc....replace the vold.fstab with the one above and flash......you will have bionix...tested with 1.2.1 but should work with recent one....running deadhorse kernel with bionix 1.2.1 without /data lol
Also im trying to make a rfs partition in ext sdcard and mount it...but since my work is all hit and trial it who knows........also any guidance on how to mount /data to external sd would be welcomed......i know its logically possible....trying with parted to partition 2 gb sd to 600 mb rfs for /data and rest for /sdcard...any help gentlemen..
manjish said:
For the background....my samsung vibrant bootlooped after installing dow kernel....after that I was unable to mount my internal....the 16 gb space disappeared.....however I can boot to eugenes froyo 2e recovery rom....nothing else boots the phone.
...
give any thoughts but dont say send it to tmobile.....im at the opposite side of the globe from USA.......I need to fix it as far as possible and use it.
Click to expand...
Click to collapse
Use Odin with Re-partition checked. And learn to search.
Telanis said:
Use Odin with Re-partition checked. And learn to search.
Click to expand...
Click to collapse
+100000
seriously ha ha
manjish said:
Hi guys just to let you know......you can flash bionix rom by installing it through cwm recoyery
Click to expand...
Click to collapse
For some reason CWM will not install for my device.
Some people are soo foolish and they seem to act so smart...lol...odin with repartition......lol....ive been doing it from 2 weeks....it does not work.....thats why this thread is here morons........and u just pass by and say odin with repartition....and another fool comes in and says +100000 lol.......god have mercy on these two guys....help them...lol
@binary....install twice...maybe 3 time
My advice is to send the phone back to T-Mobile. DOW burned out the internal memory. I am.
And don't mind the wankers... they haven't learned to read threads before replying and looking stupid.
Sent from my imx51_bbg using Tapatalk
let me go.... HAHAHAHAAHAHAH i had the same problem anyway go ahead call me noob and im full of my self YES YES now ship it back if u cant use odin properly .bhappy. at least you get new phone,take my advice , stay away from flashing .
+1000
but on the other hand yes some internal sd fail i dont think yours did since u can boot inm to bionix i odnt know im such a noob that it doesent make sense to me that your internal memmory failed but u bootin in to bionix .
Seriously ?
OP already said he's on the other side of the globe. And just like myself and many others, this is more of a hard brick.
It's like telling the mother of a disabled child, "just take vitamins and let him exercise. "
He ain't got no legs or arms and his IQ is 11, you MORON.
bartek25 said:
but on the other hand yes some internal sd fail i dont think yours did since u can boot inm to bionix i odnt know im such a noob that it doesent make sense to me that your internal memmory failed but u bootin in to bionix .
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
You too.
Telanis said:
Use Odin with Re-partition checked. And learn to search.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
Let's stay on topic here people and play nice.
Actually, this sounds like a classic case of overheating thus----heat damage
All need to remember that a minor loss of insulation results in brownout in electronic devices. Or better put, 4 or 5 molecules of insulation
Either way return it or buy a new board.
I checked. No brown on my board, yet I have the same exact issues.
oka1 said:
Actually, this sounds like a classic case of overheating thus----heat damage
All need to remember that a minor loss of insulation results in brownout in electronic devices. Or better put, 4 or 5 molecules of insulation
Either way return it or buy a new board.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
it's init.rc i believe, should see something like this:
"mount rfs /dev/block/mmcblk0p2 /data nosuid nodev check=no"
i'd avoid using a FAT formatted partition, since pulling the card in the middle of a write could result in data loss.
These are git repos for the initramfs that I pulled from the Austria Firmware and the Kernel Source downloaded and reuploaded to github. I'm going to fork and start working on a kernel for when I get the 7.7 myself, but if anyone else wants to start working on it and use them, feel free.
Kernel is still uploading, mistakenly reuploaded the initramfs twice. (Facepalm)
https://github.com/bedwa/P6800-Kernel
https://github.com/bedwa/P6800-initramfs
Enjoy guys!
I have a 6800 device imported from Hong Kong and have been trying to figure out how to port CWM recovery to it. I work as a developer but I haven't looked at this before as I haven't needed to
So far I have rooted the device and had a dig around the filesystem. The partitioning looks similar to the 7 plus:-
179 1 20480 mmcblk0p1 /efs
179 2 1280 mmcblk0p2 /boot
179 3 1280 mmcblk0p3 /mnt/.lfs
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6 / recovery
179 7 204800 mmcblk0p7 /cache
179 8 16384 mmcblk0p8 <radio/modem>
179 9 851968 mmcblk0p9 /system
179 10 13791232 mmcblk0p10 /data
179 11 458752 mmcblk0p11 /preload
179 12 8192 mmcblk0p12
I'm trying to figure out what's in 4,5 and 12.
I have the kernel source code downloaded and buildig and I'm now looking at where to go next. If anyone can post any links to resources on the web which might speed up the process then it would be most appreciated. I don't have a lot of time to spend on this.
Could you "if dd" them and send me a link? I'll be able to find out which is the recovery.img. ;-)
P4 - https://rapidshare.com/files/2298175628/mmcblk0p4.img?bin=1
P5 - https://rapidshare.com/files/2298175628/mmcblk0p4.img?bin=1
P6 - (/recovery) https://rapidshare.com/files/1289796625/recovery.img?bin=1
Let me know what you find and if you don't mind how you went about it. Have got to go and be sociable now
looking in /sys/block/mmbclk0/
gives all the partition info - name,size,ofset, corresponds with pit info from heimdall.
also interested in this
Heres the info (not sure if it helps):
mmcblk0/mmcblk0p4
alignment_ofset 0
discard_alignment 4265607168
inflight 0 0
partition 4
partition_name param
size 16384
start 57344
stat 25 118 1144 0 0 0 0 0 25 40
mmcblk0/mmcblk0p5
alignment_ofset 0
discard_alignment 4257218560
inflight 0 0
partition 5
partition_name kernel
size 16384
start 73728
stat 0 0 0 0 0 0 0 0 0 0
mmcblk0/mmcblk0p6
alignment_ofset 0
discard_alignment 4248829952
inflight 0 0
partition 6
partition_name recovery
size 16384
start 90112
stat 0 0 0 0 0 0 0 0 0 0
mmcblk0/mmcblk0p7
alignment_ofset 0
discard_alignment 4240441344
inflight 0 0
partition 7
partition_name cache
size 409600
start 106496
stat 11 128 20 6 2 64 465 0 280 485
mmcblk0/mmcblk0p8
alignment_ofset 0
discard_alignment 4030726144
inflight 0 0
partition 4
partition_name modem
size 32768
start 516096
stat 58 2560 20944 380 0 0 0 0 330 380
mmcblk0/mmcblk0p9
alignment_ofset 0
discard_alignment 4013948928
inflight 0 0
partition 9
partition_name factoryfs
size 1703936
start 548864
stat 8796 407 701658 31365 0 0 0 0 15540 31325
Thanks - that helps confirm what I had found by digging around and completes the list of partitions.
I have now extracted initramfs from both the runtime and recovery kernels.
Now I need to find time to do some reading on how to port CWM recovery.
Anyone know whats in the param partition?
A quick update....
The partitioning for the 7.7 is very similar to the 7plus.
I have been in contact with the garyd9 who ported CWM to the 7plus and he has given us a few pointers including his github username.
See:-
http://forum.xda-developers.com/showthread.php?p=21717604#post21717604
Interestingly he says that it's likely that the samsung's kernel source release will not have the correct defconfig so we are going to need to tweak it.
The recovery binary gets compiled from the Cyanogenmod sources which are easily obtained.
Unfortunately I'm going to be tied up with my day job for most of this week but will try and look at this again on Friday.
Is there anyone that can keep the ball rolling while I'm busy?
Thanks
Ddraig
I'm getting this one and selling my Note. I'm so excited to see you guys working out of something for P6800 here.
Thanks to all devs in advance!
...........
Dark-Master said:
I'm getting this one and selling my Note. I'm so excited to see you guys working out of something for P6800 here.
Thanks to all devs in advance!
Click to expand...
Click to collapse
+1 here
Anybody want to buy my outdated,used Note?
Hehehe.. well, at least I just *seconds ago* ordered my Tab 7.7 from ebay uk.
Let the modding and ROM flashing begin!
@Lucid what's wrong with your Note..?
Sent from another Galaxy...
Nexus
There is nothing wrong with my Note, it is the best phone I've ever had.
So I went ahead and bought the 7.7 to see if that one is even better. Needs to arrive still.
I intend to use it as a daily phone and will keep it to my ear if needed,
no matter the reactions of other people.
Gadgetwise, I live for myself, not the general public.
I might sell on of them, but history shows I keep all my "old" phones.
I use my galaxy nexus for day to day but since finding out about phoneleash i dont really touch my phone anymore.. check out phone leash if you have two SIMs.. although i guess it can work with GV also..
Sent from another Galaxy...
Tab 7.7
I placed my 7.7 next to my Titan, Sensation and the Galaxy Note today to see how it fares, no way is it practical to put to the ear and it is pretty ridiculous to carry. It's a compact device but not THAT compact. My Kindle Fire was more handy. The bezel is too large.
However, the phone functionality is superb and if one can find an unobtrusive way to carry it, we could finally unify our communication requirements in one device.
lucid said:
There is nothing wrong with my Note, it is the best phone I've ever had.
So I went ahead and bought the 7.7 to see if that one is even better. Needs to arrive still.
I intend to use it as a daily phone and will keep it to my ear if needed,
no matter the reactions of other people.
Gadgetwise, I live for myself, not the general public.
I might sell on of them, but history shows I keep all my "old" phones.
Click to expand...
Click to collapse
monakh said:
.However, the phone functionality is superb and if one can find an unobtrusive way to carry it, we could finally unify our communication requirements in one device.
Click to expand...
Click to collapse
Check out the Samsung HM5000 Bluetooth pen thingy.
Y Ddraig Goch said:
A quick update....
The partitioning for the 7.7 is very similar to the 7plus.
I have been in contact with the garyd9 who ported CWM to the 7plus and he has given us a few pointers including his github username.
See:-
http://forum.xda-developers.com/showthread.php?p=21717604#post21717604
Interestingly he says that it's likely that the samsung's kernel source release will not have the correct defconfig so we are going to need to tweak it.
The recovery binary gets compiled from the Cyanogenmod sources which are easily obtained.
Unfortunately I'm going to be tied up with my day job for most of this week but will try and look at this again on Friday.
Is there anyone that can keep the ball rolling while I'm busy?
Thanks
Ddraig
Click to expand...
Click to collapse
Ddraig - I have been trying to get this get up and running.
So far I have managed to compile a zImage (recovery.img) using pretty much with the default config. Flashed through heimdall
I have used garyd9 recovery_initramfs, used his /sbin folder as is. The rest of the files are taken from the stock gt-6800 ramdisk inc modules. Where necessary make changes to partition entrys.
It boots in to clockworkmod recovery fine. It can mount all partitions but not /cache partition properly. I have checked the path and it seems correct ??
(I can mount via adb but cwm says it cant find it)
I will try building recovery binary at some point but will be busy for some days now.
I can you sent you some of my config files / recovery.img if it helps.
ezynow said:
Ddraig - I have been trying to get this get up and running.
So far I have managed to compile a zImage (recovery.img) using pretty much with the default config. Flashed through heimdall
I have used garyd9 recovery_initramfs, used his /sbin folder as is. The rest of the files are taken from the stock gt-6800 ramdisk inc modules. Where necessary make changes to partition entrys.
It boots in to clockworkmod recovery fine. It can mount all partitions but not /cache partition properly. I have checked the path and it seems correct ??
(I can mount via adb but cwm says it cant find it)
I will try building recovery binary at some point but will be busy for some days now.
I can you sent you some of my config files / recovery.img if it helps.
Click to expand...
Click to collapse
Sounds like you have made some progress with custom recovery, you need to be careful if you are using garyd9 recovery_initramfs on your device, note one i think this for a wifi device being p6210 if you device is a p6800 check all the mounting points as there are some slight differences between wifi and 3g devices. how did you compile your source and make compatible odin file. i'm on a mac and so far i can't get heimdall to work with p6810.
kassemja said:
Sounds like you have made some progress with custom recovery, you need to be careful if you are using garyd9 recovery_initramfs on your device, note one i think this for a wifi device being p6210 if you device is a p6800 check all the mounting points as there are some slight differences between wifi and 3g devices. how did you compile your source and make compatible odin file. i'm on a mac and so far i can't get heimdall to work with p6810.
Click to expand...
Click to collapse
After 2 days of kernel building and insmod, I've finally got a P6810 module to insmod successfully into my stock device. This is the config. It comes from the samsung source (GT-P6810_HC_Opensource) download with some DEBUG params turned off, and the local version set for the Australian DTKL5 firmware. I hope it can help someone avoid some trial and error pain. The p6800 guys may be able to turn off similar debugs and get theirs working. This is not fully tested, if you find other params that need changing please advise.
EDIT: I flashed this kernel to my device and it worked.
Here is more information on the environment.
CodeSourcery toolchain arm-2009q3-67-arm-none-linux-gnueabi.bin
Change the supplied Makefile CROSS_COMPILE to point to installed toolchain (eg, /home/davp/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-)
Copy the supplied file to .config in the directory where you unpacked the kernel source, then run make
Links http://forum.xda-developers.com/showpost.php?p=21870378&postcount=23 for how to do a basic initramfs to go with the new kernel (the result of this is running a command like: make -j5 CONFIG_INITRAMFS_SOURCE=initramfs_root, and then tar and flash the zImage).
Copy of the .config file (from the kernel directory):
Can you confirm you have suscessfully compiled and flashed a working kernel?
I want to have a crack at custom recovery for the p6810, i'm pretty confident we can getting going using a blend of sources from https://github.com/garyd9/initramfs_recovery_GT-P6210 and our kernel stuff.
davp said:
After 2 days of kernel building and insmod, I've finally got a P6810 module to insmod successfully into my stock device. This is the config. It comes from the samsung source (GT-P6810_HC_Opensource) download with some DEBUG params turned off, and the local version set for the Australian DTKL5 firmware. I hope it can help someone avoid some trial and error pain. The p6800 guys may be able to turn off similar debugs and get theirs working. This is not fully tested, if you find other params that need changing please advise.
Click to expand...
Click to collapse
Oh great - the 7.7 also has binary-only modules?
Freaking Samsung, I thought they were making progress with the I9100/I777 (100% open-source kernels, no proprietary modules).
Good luck bedwa - feel free to browse my github for Exynos tips (although much of it will not directly patch onto HC kernels), garyd9 knows what he's doing too.
Hi,
Here's a method based on a security hole to gain root on the Galaxy Tab 2 7" without heavy flashing by Odin. I've successfuly tested this method on my GT-P3110 running stock Android 4.0.3 on kernel 3.0.8-379370, version IML74K.P3110XXALD4.
The original post by Miloj :good: can be viewed here :
http://forum.xda-developers.com/showthread.php?t=1704209
I've only "translated" the trick from TF300T to our Galaxy Tab. I guess it should work for other devices too... To make short, the goal here is to create a symbolic link from the famous /data/local/tmp to the block device on which /system is mounted. The mount command runned in an ADB shell can give the required information :
$ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
After identifying the block device, refer to the well-explained Miloj post and consider :
Code:
[COLOR="Red"]FOR SAMSUNG GALAXY TAB 2 7" ONLY:[/COLOR]
Code:
$ ln -s /dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS tmp
$ exit
Hope it will help !
after typing what you said all i get is " link failed Read-only file system"
tried on galaxy tab 2 p3100 (stock)
ze0 said:
after typing what you said all i get is " link failed Read-only file system"
tried on galaxy tab 2 p3100 (stock)
Click to expand...
Click to collapse
Well, you must follow Miloj's tutorial http://forum.xda-developers.com/showthread.php?t=1704209 from the start : push the binaries downloaded from http://db.tt/FBUNeVmo to /data/local, run an ADB shell and change directory to /data/local, move tmp to tmp.back then create the symbolic link to the block device with the ln command given in my post for the Galaxy Tab and type (or copy / paste) all the following commands (reboot, shell, clean-up, dirty work, ...) given by Miloj.
I know it's a little rough, I'll try to find some time to script all the stuff or adapt the one click tool quoted in Miloj's post.
Good luck !
yes it worked .awesome man thank you you rock ,now i have root in stock with binary counter value 0
The automated tool
Sparkym3 provides an automated tool for rooting the Transformer TF300T with Miloj method :
http://forum.xda-developers.com/showthread.php?t=1706588
I've modded the tool for the Samsung Galaxy Tab 2 7" (see attached file). Check the link above for the instructions and run the modded version called RootDebugfs_n95.bat instead of the original RootDebugfs.bat.
The original tool includes the Asus USB drivers... I failed to join the Samsung ones to the attached zip, maybe due to an excessive weight (near 19 Mo).
Happy rooting !
Gee, it's already been impossible with ICS4.0.4
Wish I hadn't upraded...
Thanks Nesquick95, I've updated my topic with your informations.
hayatama said:
Gee, it's already been impossible with ICS4.0.4
Wish I hadn't upraded...
Click to expand...
Click to collapse
If the security hole is patched in the 4.0.4 release, you'll get an "access denied" error while executing the "debugfs -w /data/local/tmp" command.
If it's the case, we must look for another rooting trick
Can you please tell which kind of error you get and if it's not the "access denied" one, post the result of a "mount" of your tablet (adb shell mount) ?
First,great job,thank you for your work,now we don't need to worry about warranity.Second,maybe you can help us again,can you please tell us how do we keep root,when upgrading 4.0.4? I know that Transformer tabs have some kind of app,named Root Keeper ,if you flash OTA update,and want to keep root.Maybe we can try something similar for our tab ,or using Mobile Odin maybe?
Thanks again!
Best Regards!
Nesquick95 said:
If the security hole is patched in the 4.0.4 release, you'll get an "access denied" error while executing the "debugfs -w /data/local/tmp" command.
If it's the case, we must look for another rooting trick
Can you please tell which kind of error you get and if it's not the "access denied" one, post the result of a "mount" of your tablet (adb shell mount) ?
Click to expand...
Click to collapse
thanx. if my memory serves, it was an error you mentioned, but i will check it soon.
btw, i've got another updates...
Sent from my GT-P3113 using xda app-developers app
hayatama said:
Gee, it's already been impossible with ICS4.0.4
Wish I hadn't upraded...
Click to expand...
Click to collapse
would you like to test this one?
I'm tested in my P3100 with 4.0.4 and worked
Fz.hary said:
would you like to test this one?
I'm tested in my P3100 with 4.0.4 and worked
Click to expand...
Click to collapse
Thanx, i know it'd work, but i want to root "without" flashing rom.
Sent from my SC-02C using xda app-developers app
Yep,the whole point of this root method it's not to flash unofficial kernel using Odin,because it triggers the counter ,and it will void your warranity.If you root without Odin,than you can use Mobile Odin to flash roms,and you'll have the counter 0 ,so you'll keep your warranity. intact.
Cheers
Nesquick95 said:
Sparkym3 provides an automated tool for rooting the Transformer TF300T with Miloj method :
http://forum.xda-developers.com/showthread.php?t=1706588
I've modded the tool for the Samsung Galaxy Tab 2 7" (see attached file). Check the link above for the instructions and run the modded version called RootDebugfs_n95.bat instead of the original RootDebugfs.bat.
The original tool includes the Asus USB drivers... I failed to join the Samsung ones to the attached zip, maybe due to an excessive weight (near 19 Mo).
Happy rooting !
Click to expand...
Click to collapse
So if i use this it will root amid leave tab 2 at 0 on odin
Sent from my Tab 2
photon4glover said:
So if i use this it will root amid leave tab 2 at 0 on odin
Sent from my Tab 2
Click to expand...
Click to collapse
Yes, because this root method exploits a security hole of the tab's software integration and thus doesn't need Odin.
But I'd like to say that this kind of rooting method isn't better or worst than recovery flash...
Recovery flash causes warranty to be broken but is nearly granted to work.
Tricky methods keep warranty alive but have short lifetimes, like the one discussed here that seems to work only on 4.0.3, since providers like Samsung can't leave security holes on their systems and apply patches so the work (find a new trick or write an OTA-rootkeeper) must be done each time an update is released.
Man so no method like this forv4.04
Sent from my Tab 2
photon4glover said:
Man so no method like this forv4.04
Sent from my Tab 2
Click to expand...
Click to collapse
Haven't got 4.0.4 myself so it's hard for me to say...
An unsuccessful try on 4.0.4 is reported here and hole patching by Samsung is strongly suspected.
Well, it's always the same never-ending rooting story : flashing & losing warranty or waiting for a rooting exploit that may never be found & keeping warranty alive.
May I ask how 4.0.4 comes to our tabs ? Is it regular OTA or alternative ROM flashing ? I'm on stock 4.0.3, rooted but not unlocked and have no signs of an OTA update coming.
4.0.4 is available from kies only [p3100] No OTA update
Nesquick95 said:
Haven't got 4.0.4 myself so it's hard for me to say...
An unsuccessful try on 4.0.4 is reported here and hole patching by Samsung is strongly suspected.
Well, it's always the same never-ending rooting story : flashing & losing warranty or waiting for a rooting exploit that may never be found & keeping warranty alive.
May I ask how 4.0.4 comes to our tabs ? Is it regular OTA or alternative ROM flashing ? I'm on stock 4.0.3, rooted but not unlocked and have no signs of an OTA update coming.
Click to expand...
Click to collapse
Since your alrdy rooted u can flash a recovery via mobile Odin or desktop Odin of your not worried about flash counter. If u guys have a link for your 4.0.4 update ill root and de odex for ya. Or let me know what region the 4.0.4 update is for ill try and find it on samsung firm
Sent from my ADR6425LVW using xda premium
Nesquick95 said:
Haven't got 4.0.4 myself so it's hard for me to say...
An unsuccessful try on 4.0.4 is reported here and hole patching by Samsung is strongly suspected.
Well, it's always the same never-ending rooting story : flashing & losing warranty or waiting for a rooting exploit that may never be found & keeping warranty alive.
May I ask how 4.0.4 comes to our tabs ? Is it regular OTA or alternative ROM flashing ? I'm on stock 4.0.3, rooted but not unlocked and have no signs of an OTA update coming.
Click to expand...
Click to collapse
Mine came OTA, and additional OTA was available (P3113)
Sent from my SC-02C using xda app-developers app
I see that the question has been asked, but no one has answered it. I need to sideload an app to the watch, but all the guides I find are written for the 4 and 5, not the 3 since it still uses Tizen no WearOS. If someone could point me in the right direction for a guide, I would appreciate it!
jnelsoninjax said:
I see that the question has been asked, but no one has answered it. I need to sideload an app to the watch, but all the guides I find are written for the 4 and 5, not the 3 since it still uses Tizen no WearOS. If someone could point me in the right direction for a guide, I would appreciate it!
Click to expand...
Click to collapse
How to sideload apps into gw3
Hi. So i've been searching for hours and nothing is working. I'm trying to sideload modded aps onto my gw3. So far I've gone through: https://forum.xda-developers.com/t/app-mod-spotify-lite-scaled-for-standalone-use-on-wear-os.3815680/...
forum.xda-developers.com
You use "adb sideload" to move contents into the watch. If you don't know on how to use it, research for the answer. You can mess up the device.
First time writing here, just wan't to clear things up, because i have been doing some research now for a while...
First off all adb is for "normal" android devices (like most phones), you should use sdb because its specifically designed for use with Tizen Os devices (just as they are saying at the thread Maxninja linked, ehm ehm), including Galaxy Wearables, like documented here: sdb - tizen reference
(working with it is very similiar as with adb though)
To sideload apps there is already a very good tutorial in this forum here:
howto-sign-and-sideload-tizen-applications-to-the-gear-fit2-from-windows
-->Important: stick with java version 15, i had 17 installed and got IllegalAccessExceptions due to some linkage Error caused by newer Java versions. Just install an "Amazon corretti" msi (google it), and it should work.
I think the more important question also is where to get .tpk files...
Simplest way is to temporarily link your galaxy watch 3 with a samsung phone, download all the wanted apps, and then do the following
- enable developer mode,
- with
Code:
sdb pull
download the WHOLE folder, where your app is stored (something like /opt/usr/apps/URI_NAME_OF_APP or opt/usr/globalapps/URI_NAME_OF_APP) to your disk.
--> a tpk file has a structure like this, within the galaxy watch: (example)
com.samsung.d-calculator-wc1 : FOLDER
Code:
lrwxrwxrwx 1 app_fw app_fw 69 May 18 16:15 author-signature.xml -> /opt/usr/globalapps/com.samsung.d-calculator-wc1/author-signature.xml
lrwxrwxrwx 1 app_fw app_fw 52 May 18 16:15 bin -> /opt/usr/globalapps/com.samsung.d-calculator-wc1/bin
d????????? ? ? ? ? ? cache
d????????? ? ? ? ? ? data
lrwxrwxrwx 1 app_fw app_fw 52 May 18 16:15 lib -> /opt/usr/globalapps/com.samsung.d-calculator-wc1/lib
lrwxrwxrwx 1 app_fw app_fw 52 May 18 16:15 res -> /opt/usr/globalapps/com.samsung.d-calculator-wc1/res
drwxr-xr-x 3 owner users 4096 May 18 16:15 shared
lrwxrwxrwx 1 app_fw app_fw 67 May 18 16:15 tizen-manifest.xml -> /opt/usr/globalapps/com.samsung.d-calculator-wc1/tizen-manifest.xml
- if it didn't work, try to pull them independently without cache and data folders (or with the calculator example from "globalapps" instead of "apps"
- setup your galaxy watch to your actual phone (therefore factory resetting it)
- follow the signing procedure linked at the top of my post, for each app
- install them via
Code:
sdb install
Hope this helps!