Develop Bugs

[HELP] Need Clean Modem.bin & amss.bin (instructions inside)

One of the AT&T users flashed my ROM on the T-Mobile side. Initial ROMs we were building were not having radio and we assumed it was because we needed to flash modem.bin and amss.bin so we included that as part of our ROM zip and updater-script. When he flashed my ROM, he overwrote his AT&T modem.bin/amss.bin with our T-Mobile modem.bin/amss.bin (who know they were different?)
I feel bad and want get him a quick fix.
If someone could run the commands to pull these files for me and send them via DropBox or whatever so I can make a flashable zip to fix his radio signal, I'd greatly appreciate it.
In terminal emulator (or adb shell in cmd window)
su
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.bin bs=4096
Pulls modem.bin
Code:
dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin bs=4096
Pulls amss.bin (if that doesn't work its 0p12 but I'm pretty sure it's 13)
They'll be dumped to your sdcard.
Thank you for any help.

Link's not live yet but when it's done it'll be there. I can upload the other one too.
EDIT: Uploading a zipped one instead - https://dl.dropbox.com/u/40864263/modem.zip

snotyak said:
Uploading the modem.bin here now - https://dl.dropbox.com/u/40864263/modem.bin
Link's not live yet but when it's done it'll be there. I can upload the other one too.
Click to expand...
Click to collapse
Thanks bro

NP. It's live now and the compressed amss.zip should be live in a little bit - https://dl.dropbox.com/u/40864263/amss.zip

snotyak said:
Link's not live yet but when it's done it'll be there. I can upload the other one too.
EDIT: Uploading a zipped one instead - https://dl.dropbox.com/u/40864263/modem.zip
Click to expand...
Click to collapse
Is it flashable by chance?
I don't have a ton of experience making flashable zips. I have the command lines for it, but I'm not sure how to get the update-binaries? (are they need for flashing something like this?) or the rest of the command lines for the updater-script.
I have:
Code:
ui_print("Flashing modem ...");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing modem...");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p1", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
ui_print("Flashing amss.bin");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("amss.bin", "/tmp/amss.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p12", "/tmp/amss.bin"),
delete("/tmp/flash_image"));
ui_print("amss.bin Flash complete!");
ui_print("Clearing temp files...");
assert(delete("/tmp/amss.bin"));
delete("/tmp/flash_image");
unmount("/system");
ui_print(" ");

uoY_redruM said:
Is it flashable by chance?
I don't have a ton of experience making flashable zips. I have the command lines for it, but I'm not sure how to get the update-binaries? (are they need for flashing something like this?) or the rest of the command lines for the updater-script.
Click to expand...
Click to collapse
It's just a compressed .BIN because it was like 60MB and my internet is slow, haha. I didn't do anything to make it flashable.
Also, see my post above for the amss.bin (also a compressed zip)

uoY_redruM said:
Is it flashable by chance?
I don't have a ton of experience making flashable zips. I have the command lines for it, but I'm not sure how to get the update-binaries? (are they need for flashing something like this?) or the rest of the command lines for the updater-script.
I have:
Code:
ui_print("Flashing modem ...");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing modem...");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p1", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
ui_print("Flashing amss.bin");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("amss.bin", "/tmp/amss.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p12", "/tmp/amss.bin"),
delete("/tmp/flash_image"));
ui_print("amss.bin Flash complete!");
ui_print("Clearing temp files...");
assert(delete("/tmp/amss.bin"));
delete("/tmp/flash_image");
unmount("/system");
ui_print(" ");
Click to expand...
Click to collapse
Could i just insert these into the current att rom in running? Like goto system and put this in the build?

is its 60 mb thats not a modem.bin.... what the hell did u people doo....... ****tt

doh.... :facepalm:

howtomen said:
is its 60 mb thats not a modem.bin.... what the hell did u people doo....... ****tt
Click to expand...
Click to collapse
Like a dumb a$$ i flashed a tmo rom to see if it would wrk. i didnt know that the modem.bin would be in the rom, and now i have no radio. Im trying to get a bin i can use to get my radio back. I looked in the skyrocket forum and saw that people made flashable zips of the radios for this reason, so now thats what im trying to get done. do you know how? Cuz im starting o get worried now.

howtomen said:
is its 60 mb thats not a modem.bin.... what the hell did u people doo....... ****tt
Click to expand...
Click to collapse
hmm, it was pulled from the modem partition with the command line to pull modem.bin. The modem.bin we pulled on our end was 60MB.
It caused absolutely no issues on our end....

kydkupa said:
Like a dumb a$$ i flashed a tmo rom to see if it would wrk. i didnt know that the modem.bin would be in the rom, and now i have no radio. Im trying to get a bin i can use to get my radio back. I looked in the skyrocket forum and saw that people made flashable zips of the radios for this reason, so now thats what im trying to get done. do you know how? Cuz im starting o get worried now.
Click to expand...
Click to collapse
we dont even know where the radio partition is and its not mmcblk0p1 so that means u didnt flash a radio who knows what u flashed which is why i am worried because now not only u but a bunch of tmobile folks have some wierd **** going down there phones....
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
uoY_redruM said:
hmm, it was pulled from the modem partition with the command line to pull modem.bin. The modem.bin we pulled on our end was 60MB.
It caused absolutely no issues on our end....
Click to expand...
Click to collapse
thats cuz its ur device but its not a modem... no way in hell its a modem... who said it was mmcblk0p1?

howtomen said:
we dont even know where the radio partition is and its not mmcblk0p1 so that means u didnt flash a radio who knows what u flashed which is why i am worried because now not only u but a bunch of tmobile folks have some wierd **** going down there phones....
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
thats cuz its ur device but its not a modem... no way in hell its a modem... who said it was mmcblk0p1?
Click to expand...
Click to collapse
Who's having issues with their phone on the T-Mobile end? I haven't heard of anybody at all. This is the first issue I've seen with my ROM other then WiFi Calling not working properly....
As for mmcblk0p1, I can't remember the exact adb shell commands we ran off the top of my head but we found each and every partition using the command and made a list of them all.
Code:
mmcblk0p1 61440 MODEM
mmcblk0p2 128 SB12
mmcblk0p3 256 SB12
mmcblk0p4 512 SB13
mmcblk0p5 2048 aboot
mmcblk0p6 512 rpm
mmcblk0p7 10240 boot
mmcblk0p8 512 t2
mmcblk0p9 512 pad
mmcblk0p10 10240 param
mmcblk0p11 13952 efs
mmcblk0p12 3072 modemst1
mmcblk0p13 3072 modemst2
mmcblk0p14 1536000 system
mmcblk0p15 12832768 userdata
mmcblk0p16 8192 persist
mmcblk0p17 860160 cache
mmcblk0p18 10240 recovery
mmcblk0p19 10240 fota
mmcblk0p20 6144 backup
mmcblk0p21 3072 fsg
mmcblk0p22 8 ssd
mmcblk0p23 5120 grow
mmcblk0boot1 2048 disk
mmcblk0boot0 2048 disk

uoY_redruM said:
Who's having issues with their phone on the T-Mobile end? I haven't heard of anybody at all. This is the first issue I've seen with my ROM other then WiFi Calling not working properly....
As for mmcblk0p1, I can't remember the exact adb shell commands we ran off the top of my head but we found each and every partition using the command and made a list of them all.
Code:
mmcblk0p1 61440 MODEM
mmcblk0p2 128 SB12
mmcblk0p3 256 SB12
mmcblk0p4 512 SB13
mmcblk0p5 2048 aboot
mmcblk0p6 512 rpm
mmcblk0p7 10240 boot
mmcblk0p8 512 t2
mmcblk0p9 512 pad
mmcblk0p10 10240 param
mmcblk0p11 13952 efs
mmcblk0p12 3072 modemst1
mmcblk0p13 3072 modemst2
mmcblk0p14 1536000 system
mmcblk0p15 12832768 userdata
mmcblk0p16 8192 persist
mmcblk0p17 860160 cache
mmcblk0p18 10240 recovery
mmcblk0p19 10240 fota
mmcblk0p20 6144 backup
mmcblk0p21 3072 fsg
mmcblk0p22 8 ssd
mmcblk0p23 5120 grow
mmcblk0boot1 2048 disk
mmcblk0boot0 2048 disk
Click to expand...
Click to collapse
thats not true... you guys pulled that straight from i9300 i remember correcting ur mount points in original updater... u cant find out what mount points are from adb.... and as for modem thats wrong... u can look in ur recovery if u decompile it... infact most of those are i9300 values which no one should use for reference because the devices arent identical inside much less kernel recovery or firmware wise....

howtomen said:
thats not true... you guys pulled that straight from i9300 i remember correcting ur mount points in original updater... u cant find out what mount points are from adb.... and as for modem thats wrong... u can look in ur recovery if u decompile it... infact most of those are i9300 values which no one should use for reference because the devices arent identical inside much less kernel recovery or firmware wise....
Click to expand...
Click to collapse
I literally pulled non of those from i9300. If I could find the commands I ran, I'd show you what I mean. It was something | find "system" and I did "system" "boot" and a few others and it listed the block with block number.
When Five gets on tomorrow, he can confirm. We both found these separately, non of them were found using any reference to i9300.

Alright ladies, play nice.
Sent from my SAMSUNG-SGH-I747 using xda premium

uoY_redruM said:
I literally pulled non of those from i9300. If I could find the commands I ran, I'd show you what I mean. It was something | find "system" and I did "system" "boot" and a few others and it listed the block with block number.
When Five gets on tomorrow, he can confirm. We both found these separately, non of them were found using any reference to i9300.
Click to expand...
Click to collapse
That's wierd because why would u get I9300 modem partition and its not ours....
Sent from my HTC Desire HD using xda premium

I'm able to get signal now but it's only edge and 3g. So I guess it's on tmo but all my phone info says att. What should I do to get to lte and hspa+? I have the right apn too.
Sent from my SAMSUNG-SGH-I747 using xda premium

howtomen said:
That's wierd because why would u get I9300 modem partition and its not ours....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
The modem.bin and amss.bin I uploaded for him/them were from your ROM....??
Disregard this if you're talking about something completely different

snotyak said:
The modem.bin and amss.bin I uploaded for him/them were from your ROM....??
Disregard this if you're talking about something completely different
Click to expand...
Click to collapse
No itll work to.fix that dudes stuff but its not what it seems
Sent from my HTC Desire HD using xda premium

[Q] Backup/Restore using DD and ODIN

Any help will be appreciated :good:​
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So all we need the block device list for note 2
/dev/block/mmcblk0 Whole Internal Storage
/dev/block/mmcblk0p1 4194kB BOTA0
/dev/block/mmcblk0p2 4194kB BOTA1
/dev/block/mmcblk0p3 21.0MB EFS
/dev/block/mmcblk0p4 4194kB m9kefs1
/dev/block/mmcblk0p5 4194kB m9kefs2
/dev/block/mmcblk0p6 4194kB m9kefs3
/dev/block/mmcblk0p7 8389kB PARAM
/dev/block/mmcblk0p8 8389kB BOOT (Kernel)
/dev/block/mmcblk0p9 8389kB RECOVERY
/dev/block/mmcblk0p10 92.3MB RADIO (Modem)
/dev/block/mmcblk0p11 4194kB TOMBSTONES
/dev/block/mmcblk0p12 1434MB CACHE
/dev/block/mmcblk0p13 2147MB SYSTEM
/dev/block/mmcblk0p14 587MB HIDDEN
/dev/block/mmcblk0p15 8389kB OTA
/dev/block/mmcblk0p16 11.4GB USERDATA (User Accessible Storage and /DATA folder)

[email protected] said:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So I need all the block device list for note 2
So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
Perhaps you should find out what the mount command does before you start using dd to read and write directly to the partitions. These sort of commands don't take prisoners

I said I'm not a linux expert, it doesn't mean I'm totally noob. I'm using Lubuntu on my netbook.
I'm well aware of risks, I'm using dd on PC time to time.
Mount only shows mounted partitions. I'm asking those partitions. I couldn't find a full partitions list anywhere
There are many partitions and I want to know what they are
Code:
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 90112 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1400832 mmcblk0p12
179 13 2097152 mmcblk0p13
179 14 573440 mmcblk0p14
179 15 8192 mmcblk0p15
259 0 11141120 mmcblk0p16
179 16 62367744 mmcblk1
179 17 62351360 mmcblk1p1
[email protected]:/ # ls -l /dev/block/mmcblk*
ls -l /dev/block/mmcblk*
brw------- root root 179, 0 2013-04-01 00:14 mmcblk0
brw------- root root 179, 1 2013-04-01 00:14 mmcblk0p1
brw-rw---- system radio 179, 10 2013-04-01 00:14 mmcblk0p10
brw-rw---- system radio 179, 11 2013-04-01 00:14 mmcblk0p11
brw------- root root 179, 12 2013-04-01 00:14 mmcblk0p12
brw------- root root 179, 13 2013-04-01 00:14 mmcblk0p13
brw------- root root 179, 14 2013-04-01 00:14 mmcblk0p14
brw------- root root 179, 15 2013-04-01 00:14 mmcblk0p15
brw------- root root 259, 0 2013-04-01 00:14 mmcblk0p16
brw------- root root 179, 2 2013-04-01 00:14 mmcblk0p2
brw------- root root 179, 3 2013-04-01 00:14 mmcblk0p3
brw-rw---- system radio 179, 4 2013-04-01 00:14 mmcblk0p4
brw-rw---- system radio 179, 5 2013-04-01 00:14 mmcblk0p5
brw-rw---- system radio 179, 6 2013-04-01 00:14 mmcblk0p6
brw-rw---- system root 179, 7 2013-04-01 00:14 mmcblk0p7
brw------- root root 179, 8 2013-04-01 00:14 mmcblk0p8
brw------- root root 179, 9 2013-04-01 00:14 mmcblk0p9
brw------- root root 179, 16 2013-04-01 00:14 mmcblk1
brw------- root root 179, 17 2013-04-01 00:14 mmcblk1p1
For some reason listing partitions by-label doesn't work either for android or block devices.
Code:
[email protected]:/ # ls -l /dev/block/by-label
ls -l /dev/block/by-label
/dev/block/by-label: No such file or directory

[email protected] said:
...So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
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 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)

cargobr151 said:
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
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 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
Click to expand...
Click to collapse
Thank you a lot, parted is not working on mine. Probably busybox related?
Edit: Nevermind I found the executable file of parted . Worked fine. Thanks again.

You must have installed a custom recovery. (with parted command included)
Like cwm or twrp v2.4.4.0. I use twrp v2.4.4.0.

@OP updated my thread with this thread info...You can visit here

@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?

dr.ketan said:
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
Click to expand...
Click to collapse
Roger that
here http://forum.xda-developers.com/showthread.php?t=1777579 @das7982 well explained the instructions for Galaxy SIII
According to his post, he's recommending to make an ODIN package from only system.img
To make system.img of note 2
Code:
dd if=/dev/block/mmcblk0p13 of=/storage/extSdCard/system.img bs=4096
Here we need a linux pc or Cygwin for Windows. If we going to use Cygwin, we need to install it along with tar, md5sum commands
Code:
tar -H ustar -c system.img > system.img.tar
Then we need to make Md5 checksum
Code:
md5sum -t system.img.tar >> system.img.tar
rename it
Code:
mv system.img.tar system.img.tar.md5
I haven't tried this yet but I'll try soon

I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium

dr.ketan said:
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You're correct, stock kernel and recovery shouldn't increase the flash counter.
To backup /data we can use
Code:
adb shell
stop
busybox tar -cZvf /storage/extSdCard/data.ext4.tar --exclude media --exclude dalvik-cache /data
reboot
To restore
Code:
adb shell
stop
busybox tar -xvf /storage/extSdCard/data.ext4.tar -C /
reboot

[Q] how to install a boot.img file

Hi guys,
I have a Linux partition on my sdcard and I want to have it mount at boot. I checked out this page( a page that I am not permitted to link to that might or might not contain this text "wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images") on how to do it and I have put together a boot.img file I want to flash. The instructions call for this maneuver:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/mynewimage.img
but the Note 8 doesn't have a MTD device:
[email protected]:/storage/sdcard0 # ls -l /dev/mtd*
/dev/mtd*: No such file or directory
what do I do?

mounting at boot time
Hi guys,
It has been about a week since I posted this question here. The reason I am trying to edit the boot.img file is to add a persistent mount point to a Linux partition on my sdcard. After fussing with several third party kernels and not succeeding in creating my own working ramdisk, I tried adding init.d support and putting the mount command in a startup script. It looks like the sdcard is not mounted by the time the init process is finished. I tried editing the vold.fstab file. I tried adding this line to the end:
dev_mount debian /storage/extSdCard/debian 50 /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
No dice.
what is the format of this file? Where can I find a man page or a doc?
These are my partitions:
1|[email protected]:/sdcard # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 2621440 mmcblk0p9
179 10 573440 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10518528 mmcblk0p12
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 27343750 mmcblk1p1
179 50 2929687 mmcblk1p2
[email protected]:/sdcard #
these have changed since I updated to 4.2.2 about a week ago. Is there some way to have the config persist through device upgrades?

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??

[q] flashing nexus 7 lollipop without access to pc

I don't know if this is the is the correct place to post this, but here goes...
I have noted in various nexus 7 forums that quite a few people can't flash a rooted Lollipop beacause for whatever reason they have no access to a PC.
I've posted how to get around this, but I know how difficult searching forums for specific information can be.
So, if enough people out there need a step by step guide, I will post it here...

Show me how

I would like to know too...
Sent from my SM-N900V using XDA Free mobile app

Flashing the new bootloader is the problem for me....
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Yeah we kinda have to wait for a recovery flashable bootloader 4.04 still

Same here, just need to be able to flash that bootloader and I'm good from there. Thanks for the effort.
Sent from my Nexus 7 using Tapatalk

Would love a flashable zip as well...I have no PC access but have a bl unlocked n7

Same for me. All I need is a flashable zip for the new bootloader.

Same here.
Sent from my Nexus 7 using Tapatalk

in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors
can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or something?

I assume this is where I should be if I'm looking to update my rooted N7, which has no working USB port (I charge on a QI charger).
Is this promising or am I stuck on KitKat?
Thanks!

Well you should be able to flash to Lollipop as soon as we have a recovery flashable bootloader.zip
Some seem to have flashed the latest ROM without the 4.04 bootloader but I am not sure they still have working root and some other issues.
I have tried to extract the files needed to make the flashable bootloader but am having trouble, so it could be the reason we don't see one yet.
Someone smarter than myself in these matters may have more insight. But so far I have not heard anything from anyone else that has attempted to make a flashable bootloader for 4.04
PsychoMcSatan said:
I assume this is where I should be if I'm looking to update my rooted N7, which has no working USB port (I charge on a QI charger).
Is this promising or am I stuck on KitKat?
Thanks!
Click to expand...
Click to collapse

I saw several posts were people did not update to 4.04 and did not seem to have any trouble, so I decided to try myself, I put a copy of the pre-rooted rom in my downloads
I made a backup, did a factory reset, installed the rom, rebooted and, installed the titanium backup on their twitter feed, restored, and everything seems to working just fine.
I am not sure what the bootloader does affect in the end as far as the running OS goes(not sure why it would affect that), I will upgrade it, if I get a flashable one, but for now I seem to be running Lollipop ok.

kernelsandirs said:
in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors
can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or something?
Click to expand...
Click to collapse
I am trying ImgRePackerRK and i am getting 'unknown header formant'
im in cmd.exe. i type: Imgerpackerrk.exe bootloader-flo-flo-04.04.img
I put everything in the same folder to make the typing the syntax faster. Is that the same error you are getting?
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
2014.11.13 22:59:27 imgRePackerRK (v. 1.04 windows)
2014.11.13 22:59:27 (c) RedScorpio, Moscow, 2013-2014
2014.11.13 22:59:27
2014.11.13 22:59:27 Command parameters: "/log" "bootloader-flo-flo-04.04.img"
2014.11.13 22:59:27
2014.11.13 22:59:27 Run parameters:
2014.11.13 22:59:27 log = 1
2014.11.13 22:59:27 debug = 0
2014.11.13 22:59:27 quiet = 0
2014.11.13 22:59:27 mono = 0
2014.11.13 22:59:27 md5 = 0
2014.11.13 22:59:27 rkcrc = 0
2014.11.13 22:59:27 rkaf = 0
2014.11.13 22:59:27 skip = 0
2014.11.13 22:59:27 2nd = 0
2014.11.13 22:59:27 cid = 0
2014.11.13 22:59:27 memsize = 134217728
2014.11.13 22:59:27
2014.11.13 22:59:27 ==========================[ START ]==========================
2014.11.13 22:59:27
2014.11.13 22:59:27 --- Firmware unpacking ---
2014.11.13 22:59:27
2014.11.13 22:59:27 2-nd layer file unpacking
2014.11.13 22:59:27 RockChip bootloader image format detected
2014.11.13 22:59:27 "bootloader-flo-flo-04.04.img" (RockChip bootloader image) unpacking
2014.11.13 22:59:28 Image properties:
2014.11.13 22:59:28 Type RockChip bootloader image (BOOT)
2014.11.13 22:59:28 Version 21.52
2014.11.13 22:59:28 Date 0.00.21
2014.11.13 22:59:28 Time 61:00:115
2014.11.13 22:59:28 ChipID 0x00316c62
2014.11.13 22:59:28 Code(?) 0x02000000
2014.11.13 22:59:28
2014.11.13 22:59:28 .ERROR. Unknown header format
2014.11.13 22:59:28
2014.11.13 22:59:28 ==========================[ STOP ]==========================
Here is the full description

You can extract the factory image tar gunzip with https://play.google.com/store/apps/details?id=com.rarlab.rar&hl=en
it's alot easier then using windows tools.
Flashify allows you to flash boot and recovery images, I don't see why a extra option couldn't be added for flashing the bootloader also.
If you knew which block the bootloader was stored you could flash it with a terminal emulator also.
The only one I know is
dd if=system.img of=/dev/block/mmcblk0p22
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 34335 loop0
179 0 15388672 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 13029359 mmcblk0p30
254 0 34335 dm-0
[email protected]:/ #

So it looks like we have the bootloader here: http://forum.xda-developers.com/showpost.php?p=56737284&postcount=12
But I want to make sure I do things in the right order. I have no USB port on my rooted N7 (2013). So I thought I'd go ahead and flash the ROM via TWRP as people have had success with the old bootloader. After that I can flash the bootloader to be nice and up to date? Will that mean I lose root at that point? If so, how do I reroot over WIFI?
Thanks!

If you flash the rom from http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx21p-t2938161 it is pre rooted i just downloaded it to my device, rebooted to twrp, made a backup, factory reset, install that rom and rebooted. Worked great. Also Eksasol posted the recovery flashable bootloader here
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/ get the bootloader one from the link. thanks @eksasol
PsychoMcSatan said:
So it looks like we have the bootloader here: http://forum.xda-developers.com/showpost.php?p=56737284&postcount=12
But I want to make sure I do things in the right order. I have no USB port on my rooted N7 (2013). So I thought I'd go ahead and flash the ROM via TWRP as people have had success with the old bootloader. After that I can flash the bootloader to be nice and up to date? Will that mean I lose root at that point? If so, how do I reroot over WIFI?
Thanks!
Click to expand...
Click to collapse

dilfatx said:
Show me how
Click to expand...
Click to collapse
I've just discovered where my original post was moved to.
So if anyone still wants to know how to get lollipop without the latest bootloader, let me know.
I assume after a couple of weeks this has been solved, but if not...
Cheers...

SHABBYLEA said:
I've just discovered where my original post was moved to.
So if anyone still wants to know how to get lollipop without the latest bootloader, let me know.
I assume after a couple of weeks this has been solved, but if not...
Cheers...
Click to expand...
Click to collapse
This was a great trouble for me back then,hell I didn't discovered your thread that time and I'd had to beg for a PC,I sold my PC some months ago!
Thanks @Q8-VO8 liked the trick!