Develop Bugs

[REF] SGS2 PIT File

SGS2 has changed a lot from SGS1 with filesystems, since there is no RFS anymore. The PIT file looks pretty different now too.
Code:
GANG : emmc.img
BOOT : boot.bin
EFS : efs.img
SBL1 : Sbl.bin
SBL2 : bl.bin (?)
PARAM : param.lfs
KERNEL : zImage
RECOVERY : (blank, unlike SGS1 which was a copy of zImage)
CACHE : cache.img
MODEM : modem.bin
FACTORYFS : factoryfs.img
DATAFS : data.img
HIDDEN : hidden.img
Preliminary notes:
Recovery is blank instead of zImage. Not sure what this could mean - it's possible that this is now unflashable? It's also possible that this is no longer used, and the kernel is used directly.
Something called GANG is at the top of the file. No idea what this is. Stuff at the top is usually lower level. It does have the image file name emmc though, http://en.wikipedia.org/wiki/MultiMediaCard#eMMC
eMMC describes an architecture consisting of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array (BGA) package.[4]
Embedded MultiMediaCard (e-MMC) e-MMC/Card Product Standard, High Capacity, including Reliable Write, Boot, Sleep Modes, Dual Data Rate, Multiple Partitions Supports and Security Enhancement
Click to expand...
Click to collapse
Sounds interesting, anyway.
FactoryFS and Data are now seperate, when in the SGS1 they were the same thing. (SGS1 copied over /data from inside factoryfs when it was not found - this means that factory reset might work differently here.)
hidden.img is part of the CSC, not sure what this could be, or even why it's here. Will have to look inside the img file to find out, I guess. CSC is usually just extra files placed in /system
SBL2 is bl.bin instead of Sbl.bin - typo by Samsung?
Since this is all EXT4 now, we might actually be able to re-size things properly now, as in the SGS1 with it's RFS stuff the /system partition couldn't actually be resized.
EDIT: Adding some reference stuff from the device.
All partitions appear to be directly off mmcblk0 - there are 12 of them. Output follows:
Code:
brw------- root root 179, 12 2011-05-08 10:35 mmcblk0p12
brw------- root root 179, 11 2011-05-08 10:35 mmcblk0p11
brw------- root root 179, 10 2011-05-08 10:35 mmcblk0p10
brw------- root root 179, 9 2011-05-08 10:35 mmcblk0p9
brw------- root root 179, 8 2011-05-08 10:35 mmcblk0p8
brw------- root root 179, 7 2011-05-08 10:35 mmcblk0p7
brw------- root root 179, 6 2011-05-08 10:35 mmcblk0p6
brw------- root root 179, 5 2011-05-08 10:35 mmcblk0p5
brw------- root root 179, 4 2011-05-08 10:35 mmcblk0p4
brw------- root root 179, 3 2011-05-08 10:35 mmcblk0p3
brw------- root root 179, 2 2011-05-08 10:35 mmcblk0p2
brw------- root root 179, 1 2011-05-08 10:35 mmcblk0p1
Partitions map as follows:
Code:
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
Not sure what the unmapped partitions are for yet.

Nice, i had a look at the partitions table to, and can verify your find. Lets see if we can make some useful of this.

Doc! I hope you got your SGS2 as SGS2 definitely need you
RyanZA! I hope you also got your SGS2, as Dev forums cannot live without you
DocRambone said:
Nice, i had a look at the partitions table to, and can verify your find. Lets see if we can make some useful of this.
Click to expand...
Click to collapse

nasgilani said:
Doc! I hope you got your SGS2 as SGS2 definitely need you
RyanZA! I hope you also got your SGS2, as Dev forums cannot live without you
Click to expand...
Click to collapse
Hahah, I've got one. To be honest though, I'm having a hard time finding anything I actually want to mod. Samsung has actually done a very good job this time around.

i can think of a few..
1. sound is not as good as my sgs with voodoo sound.
2. 2e recovery right on the phone would be nice
3. lower minimim brightness level
4. transparent status bar...
5. correctly working vpn and wpa_supplicant with adhoc mode working.
6. extra batteris i can charge with a wall charger so i can always have a spare in my pocket (they appear to be not out yet.. the idiots on ebay are selling the wrong battery and chargers for the phone)
7. working sip stack built into gingerbread like it should be.

Nothing to mod? Sounds like a boring phone.

RyanZA why did you leave the SGS scene? I miss you

jaju123 said:
RyanZA why did you leave the SGS scene? I miss you
Click to expand...
Click to collapse
With all the mods/devs for the SGSI, everything on that device already works perfectly (imo anyway). There was nothing left that I wanted to change, and all the cool projects are well in hand by people who don't want help/don't need help.
And the main problem: I got an SII, which makes it hard to look at the SI these days.

sorry for question maybe answer is allready at the forum. But can i RESIZE system ?? Now i want put there somethink (3mb) by xplore but i cant. Its says that temp file cant be writen.... when i delete somthink (3mb) from system its ok. So system is full... can i resize it?

Alcatel 960C/ One Touch Authority

Has anyone created a clockworkmod for this? This phone can be rooted, thru two apps, poot, and ministro(Qt). It still has gingerbread 2.3.6, and I need clockworkmod, or the source code, to use clockworkmod's builder. It is the cdma variant of the alcatel 995(which is gsm). can anyone point me in the right direction?

Source Code
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.

reggjoo said:
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.
Click to expand...
Click to collapse
how did you get it rooted?

rooting alcatel authority (960c)
squidbutt said:
how did you get it rooted?
Click to expand...
Click to collapse
First make sure you have USB Debugging checked and your allowing instalation of unknown sources
DL these from the play store:
Minstro2
Superuser
DL poot.apk: View attachment poot.zip
Run poot, click yes to download the extra librarys, click "click here to poot" you will need to restart the phone when it prompts. You should be rooted now :good:
You can DL ES File Explorer(from play store) and in the settings check: Root Explorer, Up to Root and Mount File System. Now you can manage all the files on your phone but be careful of what you delete, some of the stock apk's are very hard to recover if you delete them.
Hope this helps

Download superuser first
Download superuser first, you won't be able to run it until the phone's rooted. after it's rooted, it will work. This way, seems to stop a problem, when you go thru the steps to root. Some people had a error. If you plan to open the /data, /system, or dalvik cache, on your computer, install chainfire's adb insecure. These folders don't open without this, on a computer.

I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.

Haven't seen this
aldude999 said:
I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.
Click to expand...
Click to collapse
Hello, I haven't looked into this thread for a while. I see that you have some info for these blocks. that I couldn't get. I tried using root explorer, to look into some files, and they couldn't load, and tried to use too much memory, just to attempt to open, which, my phone said it was low on memory. Hate gingerbread, and kwansi choi( maker of this rom), This phone could easily handle a later os.
The usb ID's, are "Device 007: ID 1bbb:9018" .

USB ID's
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.

reggjoo said:
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.
Click to expand...
Click to collapse
I noticed that:
mmcblk0p15
mmcblk0p12
mmcblk0p8
all have the same number of blocks.
The FOTA code shows
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
Click to expand...
Click to collapse
applypatch useage is as follows:
applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Click to expand...
Click to collapse
Apply patch from blk8 to blk15.
So maybe I was mistaken with what I thought was the partition. Blk8 seems to be where fota grabs it's updated partition from?
This shows that blk15 may actually be the recovery partition. Still useless unless the bootloader can be worked on.

Battery terminals
As we know, if the battery is out, the phone will do nothing( unlike my old huawei, it didn't matter). I wondered if that was the reason why, it's so hard to unlock it. I think the bootloader has been set up to not respond to attempts. The bootloader condition treats the phone as if there's no power to it(?) . I found out that the middle terminals, of the battery contacts, will power the phone, if they're connected, but only for a few seconds.
Maybe there's some code that's unknown, or procedure. The phone doesn't respond to fastboot commands, and I can't enable it(function), on it. In the default.prop file, I see that ro.secure, is 1. Whenever I try to change it to 0( in rewritable mode), it never takes. So this is a little info.

reggjoo said:
The bootloader condition treats the phone as if there's no power to it(?)
Click to expand...
Click to collapse
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.

aldude999 said:
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.
Click to expand...
Click to collapse
Yes, I think alcatel's a little shady. I use a dual boot pc, and I found out, using the lsusb command, that the usb id's were different, than what the id's were for the supposedly official usb drivers. Sent them a msg, and they said I was wrong( can't be wrong if everything works!). They take no responsibility for their hardware, and I let people know, every chance I get, whenever I see a review of a phone from them. I found out the id's were wrong, when, before I even rooted it, I installed their onetouchmanager, and it couldn't find my phone( what! out the box!). That's not the way you do things.

Bringing 960C Back To Life!!!
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...

thealexday said:
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...
Click to expand...
Click to collapse
I still am using my 960c. I wouldn't mind finding the original stock rom or finding out how to upgrade to a newer android version. Currently running version 2.3.6
Too bad I don't know much about modding save for rooting and flashing. I gather there are still some of us here who really like our 960c phones otherwise.

Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)

This thread is dedicated to booting Qualcomm Snapdragon-based Samsung Galaxy S3 models from an SD card.
As I understand it, this only works because the Snapdragon boot ROM (NOT the bootloader, which resides on the eMMC - this is part of the CPU) has a fallback mode which reads the bootloader from an SD card if the eMMC fails. To date, the only devices I am aware of that have this fallback mode are the Snapdragon Galaxy S3 models designed for use in the US. As such, this will not work on international/Exynos based phones.
The process of preparing an SD card for this is fairly simple. All that is needed is a working, rooted phone and an empty SD card.
The dumps at the end of this post were obtained by various people using a variant of the following command:
Code:
busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70
Depending on the device, you may need more than 70MB, but on the Sprint Galaxy S3, the first 70MB of the eMMC contains everything needed for download mode without including identifying information in the dump, like the EFS partition for example.
If you are absolutely certain your SD card is empty, you can change the dd command to "of=/dev/block/mmblk1" to write the eMMC backup image directly to the SD card instead of to a file. Be very careful working with dd! mmcblk0 is the eMMC and mmcblk1 is the external SD card.
This should be obvious, but cross-device dumps will not work! This is the main reason so many people are finding themselves in need of this guide!
Use common sense - do your research and don't cross-flash, especially between US and international ROMs!
If your model is not listed there, search the forums or ask someone to make a dump for you.
Please note: if your phone model is not listed here, that doesn't mean this method won't work - however, I would appreciate it if everyone would do their research instead of bombarding me with private messages.
I hope this helps! Flash wisely!
For posterity, this is the content of the OP that led me to discover the SD boot mode by accident:
I am trying to fix a 16GB Sprint Samsung Galaxy S3 that went through a rooting process and failed, leaving download mode and most other recovery options inaccessible.
I don't have a USB download mode jig or JTAG equipment, but I noticed it's recognized as "05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" when connected to a Linux computer.
From what I've read, not many people have gotten it out of this mode, however, I've found guides that imply the NAND/eMMC is writable in this mode with qdload.pl. None of the files I've seen want to be flashed with this tool - the generic, unsigned 8960_msimage.mbn/MPRG8960.hex files to get it into EMMC USB storage mode don't execute/stay intact after flashing, so I'm guessing they failed the signature check.
Is anyone willing to dump the partition table/bootloader from their working 16GB Sprint SGS3 for me?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1048576 count=70
I unfortunately don't know what stages of the bootloader were corrupted, and I'm not sure what address to flash aboot to, if that's even possible with qdload.
Downloads:
Sprint SPH-L710: http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz (Thanks @CNexus!)
AT&T SGH-i747: http://d-h.st/iEy (Thanks @Android_Geeek!)
T-Mobile SGH-T999: http://www.mediafire.com/download/grgyera66w0rt25/debrick_SGH-T999.img (Thanks @Techlyfe!)

Sure, gimme a sec.
EDIT: You know you can find these in the firmware zips freezes has in his thread, right?

CNexus said:
Sure, gimme a sec.
EDIT: You know you can find these in the firmware zips freezes has in his thread, right?
Click to expand...
Click to collapse
I've been looking around for stock firmware packages and couldn't find them. I'll look a little harder...
EDIT: This? sbl1.mbn? Downloading it, but I'll be pretty disappointed if it doesn't work after using ~700MB...

Top of this thread you will find all the latest MD4 stuff
http://forum.xda-developers.com/showthread.php?p=32176586
Sent from the future via Tapatalk 4

No, the firmware zips, not the ROMs
And yes. The bootloaders are there, they're smaller, like 20~ MB
Grab the one that says "MD4 firmware/modem/baseband"
EDIT: This thread may be useful, it's a different device but the board is the same (MSM8960).

CNexus said:
No, the firmware zips, not the ROMs
And yes. The bootloaders are there, they're smaller, like 20~ MB
Grab the one that says "MD4 firmware/modem/baseband"
Click to expand...
Click to collapse
Found it, thanks. Unfortunately, flashing the SBL didn't fix it.
What address does aboot get flashed to? Can someone post the partition table so I can figure out the offset?

Here are two more links that give more technical information on the MSM8960 bootloaders.
Here
http://forum.xda-developers.com/showthread.php?t=1856327
And here
http://forum.xda-developers.com/showthread.php?t=1769411
You should be able to find most everything you need there.

CNexus said:
Here are two more links that give more technical information on the MSM8960 bootloaders.
Here
http://forum.xda-developers.com/showthread.php?t=1856327
And here
http://forum.xda-developers.com/showthread.php?t=1769411
You should be able to find most everything you need there.
Click to expand...
Click to collapse
I've been over those threads multiple times and I still don't know what address to plug into qdload to flash aboot (mmcblk0p5).
parted /dev/block/mmcblk0 might help.

Ok, I was just trying to help.
Code:
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm

CNexus said:
Ok, I was just trying to help.
Code:
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
Click to expand...
Click to collapse
Thanks! Sorry I'm being so demanding - you have no obligation to help me, after all.
Could I trouble you for the size in bytes? Again, thanks for the help!
Edit: This is probably asking too much, but it would be immensely helpful:
"dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"

gTan64 said:
"dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"
Click to expand...
Click to collapse
Anyone with a rooted SGS3 willing to do this? I don't know what got messed up or how - the guy who gave this phone to me just said it wouldn't reboot after one of the steps in the rooting process - but flashing that backup with qdload could be a good method of fixing bricked phones without JTAG!
In the spirit of sharing, if I manage to fix it, I'll be doing an Ubuntu "port" (building a bootloader/kernel for desktop Linux distros, not Ubuntu Touch), hopefully with Freedreno drivers too.

Sorry, couldn't get the size in bytes or else I would have posted that instead of the MB
Here's the output of dd
http://db.tt/nvwsj4e5

CNexus said:
Sorry, couldn't get the size in bytes or else I would have posted that instead of the MB
Here's the output of dd
http://db.tt/nvwsj4e5
Click to expand...
Click to collapse
It's supposed to be the first 70MB of the eMMC chip, containing the partition table, the 64MB firmware partition, the three bootloader stages, and aboot. Unless I gave the wrong command or you changed it, 70 bytes isn't going to be much help

gTan64 said:
It's supposed to be the first 70MB of the eMMC chip, containing the partition table, the 64MB firmware partition, the three bootloader stages, and aboot. Unless I gave the wrong command or you changed it, 70 bytes isn't going to be much help
Click to expand...
Click to collapse
I know, but that is the output, I was surprised as well

CNexus said:
I know, but that is the output, I was surprised as well
Click to expand...
Click to collapse
I'm guessing the version of dd on your phone is a stripped down version that doesn't recognize suffixes.
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=71680

gTan64 said:
It's supposed to be the first 70MB of the eMMC chip, containing the partition table, the 64MB firmware partition, the three bootloader stages, and aboot. Unless I gave the wrong command or you changed it, 70 bytes isn't going to be much help
Click to expand...
Click to collapse
I know, but that is the output, I was surprised as well
EDIT: dd would not accept "MB" for some reason, so I just wrote out the number of bytes. Here's the file
http://d-h.st/G3l
Md5sum: 12ca987274d905865a337d687f9e2a73

CNexus said:
I know, but that is the output, I was surprised as well
EDIT: dd would not accept "MB" for some reason, so I just wrote out the number of bytes. Here's the file
http://d-h.st/G3l
Md5sum: 12ca987274d905865a337d687f9e2a73
Click to expand...
Click to collapse
I miscalculated - it should have been 70.6MB - but I was able to find the aboot offset, so it's okay!
Huge thanks! Flashing now!

gTan64 said:
I miscalculated - it should have been 70.6MB - but I was able to find the aboot offset, so it's okay!
Huge thanks! Flashing now!
Click to expand...
Click to collapse
After the process failed for the umpteenth time, I concluded qdload only loads code into RAM and executes it - of course, in this case, it wasn't executing the backup. It seems I need an alternative method of accessing the eMMC.
The aboot/appsbl address I used was incorrect, so I still need to figure out where it's supposed to be loaded in RAM.
This doesn't appear to be common knowledge, unfortunately. Looks like I may have to JTAG it after all...

gTan64 said:
Looks like I may have to JTAG it after all...
Click to expand...
Click to collapse
I am happy to eat those words! I was able to get CNexus's backup onto an SD card (fixing the rpm, tz, and boot.img partitions that weren't part of the backup) and it booted that with no trouble! I'm currently in download mode flashing a stock ROM! Yay!!!
Thanks CNexus for the eMMC dump! I'll be posting a fixed dd image for an SD card soon for anyone who wants it. No more JTAG!

gTan64 said:
I am happy to eat those words! I was able to get CNexus's backup onto an SD card (fixing the rpm, tz, and boot.img partitions that weren't part of the backup) and it booted that with no trouble! I'm currently in download mode flashing a stock ROM! Yay!!!
Thanks CNexus for the eMMC dump! I'll be posting a fixed dd image for an SD card soon for anyone who wants it. No more JTAG!
Click to expand...
Click to collapse
HOLY GEEZ. AWESOME SAUCE. Please post a thread in development outlining your process so we can get it stickied !!
Also, PM me a Dropbox link to it or something and I'll mirror everywhere lol :thumbup::beer::beer:
This is actually great. Do you happen to know how the phone was initially bricked?
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

Need assistance....I did a bad, bad thing....

I have two Verizon HTC Ones (silver and blue) I recently was looking around and saw all the "convert your HTC one to developer/gpe edition" talk and thought, "why not." I figured everything was okay and didn't do as much reading as I normally do. I changed the MID (had SuperMID from java card s-off) to developer edition and, flashed GPE firmware then tried flashing RUUs and when that wouldn't work tried a ROM (Android Revolution HD 5.1). Well, obviously none of this is compatible with a Verizon HTC One and there are now.......issues. As, i said, both of the phones were s-off via java card. Now the silver is S-on, there is no hboot. I can flash recovery, flash roms, etc (they won't boot). But cant figure out how to flash firmware/hboot with s-on. I am using the Blue variant now with Insertcoin ROM and it is great. but the Blue suffers from a severe case of the "pink camera." whereas the silver does not. Is there anyway to fix this or is it bricked. Attached a few pics of the devastation.

RUU should fix it as long as you can get to bootloader.

RUU
yourunlikegus said:
I have two Verizon HTC Ones (silver and blue) I recently was looking around and saw all the "convert your HTC one to developer/gpe edition" talk and thought, "why not." I figured everything was okay and didn't do as much reading as I normally do. I changed the MID (had SuperMID from java card s-off) to developer edition and, flashed GPE firmware then tried flashing RUUs and when that wouldn't work tried a ROM (Android Revolution HD 5.1). Well, obviously none of this is compatible with a Verizon HTC One and there are now.......issues. As, i said, both of the phones were s-off via java card. Now the silver is S-on, there is no hboot. I can flash recovery, flash roms, etc (they won't boot). But cant figure out how to flash firmware/hboot with s-on. I am using the Blue variant now with Insertcoin ROM and it is great. but the Blue suffers from a severe case of the "pink camera." whereas the silver does not. Is there anyway to fix this or is it bricked. Attached a few pics of the devastation.
Click to expand...
Click to collapse
Have you tried to boot into RUU just to see what happens??

lj50036 said:
Have you tried to boot into RUU just to see what happens??
Click to expand...
Click to collapse
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic

Feedback
yourunlikegus said:
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic
Click to expand...
Click to collapse
Have you tried flashing the firmware in post 2 ??

yourunlikegus said:
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic
Click to expand...
Click to collapse
Are you unzipping the signed zips? There may be a .exe inside
If you are using the cmd window to flash you should be able to flash the decrypted RUU
Edit check the Sprint RUU thread see if your RUU is setup like ours

lj50036 said:
Have you tried flashing the firmware in post 2 ??
Click to expand...
Click to collapse
From the thread I posted? yes...hangs at parsing index. The .zip i can open is a bunch of .img files. the rest i cant open, says they are invalid

Hang Tight
yourunlikegus said:
From the thread I posted? yes...hangs at parsing index. The .zip i can open is a bunch of .img files. the rest i cant open, says they are invalid
Click to expand...
Click to collapse
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------
List all the .img files here so I can see what is there.....

lj50036 said:
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
Click to expand...
Click to collapse
Yeah, I've tried both and it either hangs or errors out. Attached is shot of flashing firmware...just sits there at that point.

BD619 said:
Are you unzipping the signed zips? There may be a .exe inside
If you are using the cmd window to flash you should be able to flash the decrypted RUU
Edit check the Sprint RUU thread see if your RUU is setup like ours
Click to expand...
Click to collapse
Will download and attempt it but I'm pretty sure the sprint stuff will be incompatible too. When I tried to run the developer edition ruu.exe it said connection error, plug usb cable in, etc. (not sure of exact error code)
And after succesfully botting into RUU, after the failed attempts and hangs, I cannot fastboot reboot-bootloader, that just hangs too. I have to hold the power button down.

yourunlikegus said:
Yeah, I've tried both and it either hangs or errors out. Attached is shot of flashing firmware...just sits there at that point.
Click to expand...
Click to collapse
Give me a list of all the .img files that you see from the firmware zip
I think I have a solution maybe.. With the bootloader unlocked we can still us fastboot not RUU... We will just have to flash them from fastboot one at a time... give me a list I will work on it....

lj50036 said:
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------
List all the .img files here so I can see what is there.....
Click to expand...
Click to collapse
Well, I can't open the signed zips that are for the vzw (says windows cant, invalid) but I can open 1 of the developer edition ruus that i have...not sure if that really helps

yourunlikegus said:
Well, I can't open the signed zips that are for the vzw (says windows cant, invalid) but I can open 1 of the developer edition ruus that i have...not sure if that really helps
Click to expand...
Click to collapse
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues

yourunlikegus said:
Will download and attempt it but I'm pretty sure the sprint stuff will be incompatible too. When I tried to run the developer edition ruu.exe it said connection error, plug usb cable in, etc. (not sure of exact error code)
And after succesfully botting into RUU, after the failed attempts and hangs, I cannot fastboot reboot-bootloader, that just hangs too. I have to hold the power button down.
Click to expand...
Click to collapse
What I mean is check your RUU and see if it's setup the same as Sprint not flash it
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
yourunlikegus said:
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues
Click to expand...
Click to collapse
You can't flash older firmware or RUUs if you are s-on

BD619 said:
What I mean is check your RUU and see if it's setup the same as Sprint not flash it
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
You can't flash older firmware or RUUs if you are s-on
Click to expand...
Click to collapse
ok. I'll have to figure out which one is hboot 1.54

yourunlikegus said:
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues
Click to expand...
Click to collapse
On that forum did you try to get one of those RUU and upack it?? A newer one like 2.10.605.1 decypted???
2.10.605.1 is hboot 1.54 for sure try to flash that one from RUU just so we know

lj50036 said:
On that forum did you try to get one of those RUU and upack it?? A newer one like 2.10.605.1 decypted???
2.10.605.1 is hboot 1.54 for sure try to flash that one from RUU just so we know
Click to expand...
Click to collapse
Downloading both ruu and firmware for 2.10.605.1. Will flash soon and see what happens. i think i have tried this one already but i can't remember lol

Pic of files in 2.10.605.1 firmware.zip

Partition Table
yourunlikegus said:
Downloading both ruu and firmware for 2.10.605.1. Will flash soon and see what happens. i think i have tried this one already but i can't remember lol
Click to expand...
Click to collapse
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Here is a list of the partitions... If you were to match up the img with the partition, Im sure you would be able to flash from fastboot
An example of a command work be like this
Code:
fastboot erase boot
Code:
fastboot flash boot boot.img
This is just an example.... I would have no idea in which order you would want to flash them...

lj50036 said:
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Here is a list of the partitions... If you were to match up the img with the partition, Im sure you would be able to flash from fastboot
An example of a command work be like this
Code:
fastboot erase boot
Code:
fastboot flash boot boot.img
This is just an example.... I would have no idea in which order you would want to flash them...
Click to expand...
Click to collapse
wont let me erase...remote not allowed. I was able to flash boot, but so far everything else i try is failed remote not allowed also for rcdata and adsp get signature verify fail

Recovery Boot loop on t211 [4.4.2]

Hello everyone
i was trying to deodex the stock rom 4.4.2 italy (T211)
after flashing the deodex zip i created
the tab went in to recovery boot loop
this happened with me when i flashed a mod for t211 which worked totally fine on 4.1.2
what is wrong?
is it because of the zip file or the kitkat stock rom..?

Sammy has left a signature in our Tab....now we can no longer root and mod even though you come back to JB
Sent from my SM-T211 using XDA Premium 4 mobile app

loopiness for everybody ....yay
e.r.,
please describe your process from flashing to recovery loop as clearly and descriptively as possible.
one thought is some sort of mutual check going on between boot and recovery
another is tampering with fusedlocation.apk is a guaranteed loop.
i dl'd the boot.img and will let you know if i find anything.
sorry to impose further but i might need recovery.img as well.
m
i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param

andynroid said:
Sammy has left a signature in our Tab....now we can no longer root and mod even though you come back to JB
Sent from my SM-T211 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow, thats weird
but i think that devs here would surely come up with something
moonbutt74 said:
e.r.,
please describe your process from flashing to recovery loop as clearly and descriptively as possible.
one thought is some sort of mutual check going on between boot and recovery
another is tampering with fusedlocation.apk is a guaranteed loop.
i dl'd the boot.img and will let you know if i find anything.
sorry to impose further but i might need recovery.img as well.
m
Click to expand...
Click to collapse
sure
i flashed the stock kitkat
then booted (welcome screen and stuff)
booted to download mode and flashed a custom recovery (philz cwm)
download that root zip (chainfire 1.94 update) and flashed it
while leaving the recovery, it asked for
prevent system from erasing root something
i choose
fix root
then it booted
downloaded supersu and blah
then was deodexing the rom
got the kitkat deodexer
created a zip file
then went to recovery and flashed it
then reboot to system
again the same fix root issue
selected fix and recovery boot loop
no worries bro
here you go
love to help
https://drive.google.com/file/d/0B21rpre8LhJ6c0RGYmhqbjVWZEE/edit?usp=sharing

i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param

moonbutt74 said:
i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param
Click to expand...
Click to collapse
You mean the content in the folder ?
EDIT:
you want me to upload those files ?

ah
e.r.,
run cat /proc/partitions > /sdcard/cat-part.txt
or similar to get list of your devices mmcblk's by name
or if you have parted on your device run
parted /dev/block/mmcblk0
then wait for
(parted)
and type print all
copy and paste into text and post.
m

moonbutt74 said:
e.r.,
run cat /proc/partitions > /sdcard/cat-part.txt
or similar to get list of your devices mmcblk's by name
or if you have parted on your device run
parted /dev/block/mmcblk0
then wait for
(parted)
and type print all
copy and paste into text and post.
m
Click to expand...
Click to collapse
run where?
terminal emulator..?

ethical ricado said:
run where?
terminal emulator..?
Click to expand...
Click to collapse
yes, if you can without root.
so just to clarify, you booting into recovery repeatedly OR when you boot to recovery you tab hangs?
if i understand it correctly the failure of a critical process/service will trigger panic/reboot
m

moonbutt74 said:
yes, if you can without root.
so just to clarify, you booting into recovery repeatedly OR when you boot to recovery you tab hangs?
if i understand it correctly the failure of a critical process/service will trigger panic/reboot
m
Click to expand...
Click to collapse
give me a min
everything works smooth
nothing hangs
EDIT:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 4096 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 12288 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 12288 mmcblk0p9
179 10 12288 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 1472512 mmcblk0p14
179 15 204800 mmcblk0p15
179 16 204800 mmcblk0p16
179 17 5640192 mmcblk0p17
253 0 358400 zram0
179 48 4096 mmcblk0boot1
179 24 4096 mmcblk0boot0
179 72 7761920 mmcblk1
179 73 7760896 mmcblk1p1

?
e.r.,
i don't understand, your response did not answer my question.
are you saying that you do not have an issue?
m
on a side note; i didn't find anything jn boot.img even suggesting a script/execution of a script.
it's my hope that you have retained the firware in question because i would like you
to crack it open and see if there is a new BOOTLOADER img included, not boot.img/kernel.img

moonbutt74 said:
e.r.,
i don't understand, your response did not answer my question.
are you saying that you do not have an issue?
m
on a side note; i didn't find anything jn boot.img even suggesting a script/execution of a script.
it's my hope that you have retained the firware in question because i would like you
to crack it open and see if there is a new BOOTLOADER img included, not boot.img/kernel.img
Click to expand...
Click to collapse
yeah, no issues
this are the contents
https://drive.google.com/file/d/0B21rpre8LhJ6VzU1T2RZOUo4Q0E/edit?usp=sharing

??
e.r.,
umm so if there is no issue then there is nothing that needs to be done.
as for the image showing the list if you reflash you ORIGINAL stock firware and then pickout the boot,system,images and flash them alone you might break the root-break samsung tried to pull, BUT if there is no issue then there is nothing to do.
based on your responses do you see where i'm confused?
m
on a side note here is a modified boot.img, ro.secure=0 adb.secure=0 and system should be mounted system rw [maybe]
http://d-h.st/search?search_by=1&search_for=t211-modboot
not recovery flashable, you need to dd write it

moonbutt74 said:
e.r.,
umm so if there is no issue then there is nothing that needs to be done.
as for the image showing the list if you reflash you ORIGINAL stock firware and then pickout the boot,system,images and flash them alone you might break the root-break samsung tried to pull, BUT if there is no issue then there is nothing to do.
based on your responses do you see where i'm confused?
m
on a side note here is a modified boot.img, ro.secure=0 adb.secure=0 and system should be mounted system rw [maybe]
http://d-h.st/search?search_by=1&search_for=t211-modboot
not recovery flashable, you need to dd write it
Click to expand...
Click to collapse
The only issue i faced so far was the recpvery boot loop
And i guess that might be because of the wrong zip file
But will try your method tomorrow and see what happens

Noooooooooo
ethical ricado said:
The only issue i faced so far was the recpvery boot loop
And i guess that might be because of the wrong zip file
But will try your method tomorrow and see what happens
Click to expand...
Click to collapse
e.r.,
okay DON'T do that skyelm just told me there's a lot more in this firmware than the original stock, meaning your bootloader
is already overwritten and original stock will not correct that. we need someone still running original firware to
pull/dump their first and secondstage bootloaders if i'm starting to understand the actual ****edupedness of this mess.
what would be good is to shoot me another pic of what's in the original firmware.
m

moonbutt74 said:
e.r.,
okay DON'T do that skyelm just told me there's a lot more in this firmware than the original stock, meaning your bootloader
is already overwritten and original stock will not correct that. we need someone still running original firware to
pull/dump their first and secondstage bootloaders if i'm starting to understand the actual ****edupedness of this mess.
what would be good is to shoot me another pic of what's in the original firmware.
m
Click to expand...
Click to collapse
Gotcha
Give me a min
Will do the honours
EDIT
https://drive.google.com/file/d/0B21rpre8LhJ6UXZMQzZHSjNySTQ/edit?usp=sharing
original FW 4.1.2

okay
ethical ricado said:
Gotcha
Give me a min
Will do the honours
EDIT
https://drive.google.com/file/d/0B21rpre8LhJ6UXZMQzZHSjNySTQ/edit?usp=sharing
original FW 4.1.2
Click to expand...
Click to collapse
e.r.,
okay so it's what skyelm said you see the differences?
so now we need a t211 owner with ORIGINAL FIRMWARE to dump their boot loaders and post them.
for now your stuck with what you have.
m

moonbutt74 said:
e.r.,
okay so it's what skyelm said you see the differences?
so now we need a t211 owner with ORIGINAL FIRMWARE to dump their boot loaders and post them.
for now your stuck with what you have.
m
Click to expand...
Click to collapse
yea bro
will try that workaround now
lets see what happens
EDIT:
The workaround is working
flashed the zip again just to repeat that boot loop stuff and it happened
then booted to download mode and flashed stock recovery via odin
the tab booted to system and everything was fine
then did the workaround to flash the deodexed zip i created
and it worked pretty well

Anyone tried flashing the mod ,I mean this:
http://forum.xda-developers.com/gal...7/rom-stock-nf5-lite-rooted-deodexed-t2808633
Over the stock ROM of 4.4,Any boot loops again with the custom recoveries??