Database Info

[Q] [P3100] wrong device flash /efs /modem /recovery corrupted

Hi every one!
I made a huge mistake yesterday evening: i flashed Zip's through CWM that don't belong to my p3100 but to i705.
According to MrHyde03, the files i destroyed were those partitions:
(p3100) /modem emmc /dev/block/mmcblk0p8 (TZ on i705)
(p3100) /efs ext4 /dev/block/mmcblk0p1 (MODEM on i705)
(p3100) /recovery emmc /dev/block/mmcblk0p6 (RPM on i705)
I Flashed those 3 files (!! DON'T DO IT !!):
MrHyde03 said:
a. TZ - Trust Zone VRBLL2_tz.zip
b. NON-HLOS - Modem VRBLL2_modem.zip
c. RPM - Resource Power Management -OPTIONAL-Some say it helps battery. I can't tell a difference. VRBLL2_rpm.zip
Click to expand...
Click to collapse
in the b-c-a order.
Now my phone boot lock: i can access download mode, recovery, can flash and run CWM.
I tried to flash stock odin rom, with pit and repartition for 16gb p3100.
Same results whatever the rom: it runs up to the animated logo, then show the logo forever. (no boot loop).
I guess /recovery is fine because i can enter and flash recoverys.
I guess /modem is fine because i flashed a p3100 JB modem and CWM said "DONE".
I guess is still have a partition problem with /efs
Fortunately: i made a adb copy of my whole /efs folder when i had my p3100...
My problem may be what CWM 6.3.0.0 (philz touch version) says:
W: failed to mount /dev/block/mmcblk0p1 /efs ext4 (invalid argument)
Error mounting /efs!
This is why i can't push anything into /efs: it is volatile and cleaned after each reboot.
Should i start odin and hit the infamous and dangerous "clear phone efs" button ?
Thanks a lot for your help.

You can try, but you should have a EFS backup, without a backup of your EFS don't doing this I have googled you Failure, think you must go to the repair center.

Dexxmor said:
You can try, but you should have a EFS backup, without a backup of your EFS you should not doing this I have googled you Failure, think you must go to the repair center.
Click to expand...
Click to collapse
I have a full /efs copy from month ago. Thank to my dropbox account they are safe.
I figured out that busybox and mke2fs are available through adb shell...
I used adb shell:
mke2fs -t ext4 /dev/block/mmcblk0p1
My phone BOOTS UP ! Yeah !
Next step: restore my /efs folder files content:
Tried to adb push my whole directory into /efs => files copied OK but /efs still empty after reboot.
/efs mount correctly, and mmcblk0p1 pass e2fsck OK.
Now trying to restore my files through efs professional

According to this thread i need to flash an empty EFS partition image in order for my files to STAY in /efs after each reboot.
EFS pro did the job of providing a well formatted /efs folder (every files,owner,group and rights were set) through its "clean efs" feature. (DON'T USE IT IF YOU HAVEN'T your OWN EFS BACKUP)
Now, i have to hand pick every files of my backup, and put them back in place in /efs...

FYI, the correct structure of /efs directory:
PHP:
drwxrwxr-x root root 2013-03-29 12:35 .files
-rwx------ radio radio 1048576 2013-03-29 12:35 .nv_core.bak
-rwx------ radio radio 32 2013-03-29 12:35 .nv_core.bak.md5
-rwx------ radio radio 2097152 2013-03-29 12:35 .nv_data.bak
-rwx------ radio radio 32 2013-03-29 12:35 .nv_data.bak.md5
drwxr-xr-x system system 2013-03-29 12:35 FactoryApp
drwxrwxr-x radio system 2013-03-29 12:35 bluetooth
drwxrwxr-x radio system 2013-03-29 12:35 imei
-rw------- radio radio 276 2013-03-29 12:35 nv.log
-rwx------ radio radio 2097152 2013-03-29 14:52 nv_data.bin
-rwx------ radio radio 32 2013-03-29 14:52 nv_data.bin.md5
drwxrwxr-x radio system 2013-03-29 12:35 wifi

I have restored all .nv_core and .nv_data files. They resist a phone reboot.
However, files nv_data.* are reseted to new content every phone reboot.
I wonder if i should plug my simcard back or if i should wait to know more: i already had issue with my phone operator's "network security team" and do not want to explain again what i messed up in my phone...
... 5 minutes later ...
nv_data.bin and nv_data.bin.md5 do not seems to be central to geting my imei back. Like this is writen everywhere: .nv_data.bak was !
So: i deleted nv_data*. Rebooted. i checked my rom imei (through phone command *#06#) against my real imei (micro-writen on back of device)... THEY MATCH !
i plugged my simcard back in, rebooted... and my rom doesn't ask for sim-card pin. What's the problem now ?
I think i need to check my modem...

Was just reading a post yesterday about someone flashing the wrong thing to their device. It's a different device but may steer you in the right direction.
http://forum.xda-developers.com/showthread.php?t=1448765
Hope this helps, good luck

I've already done what's he said. repartition, reflash, formatted my corrupted /efs folder.
Only then i was able to boot a stock rom.
Then i fixed my efs folder and my imei.
Now i'm wondering why my phone doesn't ask for my simcard pin.
So i tried cm10.1 installation procedure:
Flashed philz touch recovery
wiped data and system through recovery
installed JB SBL
installed CM10.1
installed gapps
... YEAH !!!!
CM10.1 28/03 booted, asked me my sim pin code.
Hspda+ icon appear, my phone is safely back to normal operation.
Thank you MrHyde03 for your support,
Thank you all for your time reading my adventure and trying to help.

Maybe the story will different if you have a backup of /efs in raw format. Try in recovery:
Code:
mke2fs -t ext4 -b 4096 -L EFS /dev/block/mmcblk0p1
mount -t ext4 /dev/block/mmcblk0p1 /tmp
Open a new terminal window to push your /efs backup to /tmp.
Please confirm your command output:
Code:
ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
lrwxrwxrwx root root 2013-03-29 21:37 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-29 21:37 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-29 21:37 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-29 21:37 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-29 21:37 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-29 21:37 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-29 21:37 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-29 21:37 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-29 21:37 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-03-29 21:37 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-29 21:37 SBL2 -> /dev/block/mmcblk0p3

Don't panic!
just download Odin and flash stock rom (google it)
Everything will be normal. You should get your device like how your get in factory reset/hard reset. :good:

how can I get efs.img
I have the same problem where my efs folder got error, but I don't backup the efs, where I can got the efs.
Thank you

doloop said:
I have a full /efs copy from month ago. Thank to my dropbox account they are safe.
I figured out that busybox and mke2fs are available through adb shell...
I used adb shell:
mke2fs -t ext4 /dev/block/mmcblk0p1
My phone BOOTS UP ! Yeah !
Next step: restore my /efs folder files content:
Tried to adb push my whole directory into /efs => files copied OK but /efs still empty after reboot.
/efs mount correctly, and mmcblk0p1 pass e2fsck OK.
Now trying to restore my files through efs professional
Click to expand...
Click to collapse
Do i need to change something for my p3110 ?

doloop said:
I have a full /efs copy from month ago. Thank to my dropbox account they are safe.
I figured out that busybox and mke2fs are available through adb shell...
I used adb shell:
mke2fs -t ext4 /dev/block/mmcblk0p1
My phone BOOTS UP ! Yeah !
Next step: restore my /efs folder files content:
Tried to adb push my whole directory into /efs => files copied OK but /efs still empty after reboot.
/efs mount correctly, and mmcblk0p1 pass e2fsck OK.
Now trying to restore my files through efs professional
Click to expand...
Click to collapse
plz can you upload ur full /efs copy , i need it dude.
coz i get IMEI null and i didn`t make backup of EFS partition

Safy4u said:
plz can you upload ur full /efs copy , i need it dude.
coz i get IMEI null and i didn`t make backup of EFS partition
Click to expand...
Click to collapse
Sorry you can't.
/efs is my personnal imei, so i'm afraid your phone is dead, and your samsung device is now wifi only.

How to back up imei/efs?

Does anyone know how to back them up? I came from a Samsung device and do not see the efs folder, I'm assuming it is stored elsewhere?
Sent from my XT1034 using xda app-developers app

That's only a Samsung thing.
Sent from my Moto X cellular telephone...

Yea but for us its somewhere in a PDS folder I went to it but don't know which file to back up
Sent from my XT1034 using xda app-developers app

Backing it up was a safeguard for Samsung devices. Its not practiced on other phones...if it exists...which I don't think it does. And if it does....it is meaningless on non Samsung phones. Backing it up that is.
Google it.
Sent from my Moto X cellular telephone...

A number of people appear to have already managed to loose their IMEI, so it might be worth finding a way to back it up.
If serophia is correct, and imei is stored in the 'pds' partition - it could be backed up using adb:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.img​
To restore:
dd if=pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds​
The pds.img could also be turned into a cwm flashable zip:
ui_print("Restoring IMEI ...");
package_extract_file("pds.img", "/dev/block/mmcblk0p26");
ui_print("Finished!"); ui_print();​
Maybe someone could make a tool to simply the process further?
Further information:
In addition to the EFS partition, there are several partitions on our n9005 devices that do not exist in official odin roms.
This means that they must be unique to your phone, and they might be as important to back up as the EFS folder to prevent IMEI loss or other problems (like those bootloops many people get when flashing kernels, which appear to be tied to corrupted modemst1 partitions).
These partitions are: modemst1, modemst2, fsg, fsc, backup, dbi, ddr, pad
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2617276​
Full list of partitions on Moto G:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p31
cache -> /dev/block/mmcblk0p33
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p28
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p27
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p29
recovery -> /dev/block/mmcblk0p32
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sdiBackup -> /dev/block/mmcblk0p14
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p34
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p13
userdata -> /dev/block/mmcblk0p36
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15

@serophia, @lost101
I understand Nexus 5 stores IMEI in modemst1 and/or modemst2.
Isn´t this our case too?
Where did you get the info about pds from?

drfr said:
@serophia, @lost101
I understand Nexus 5 stores IMEI in modemst1 and/or modemst2.
Isn´t this our case too?
Where did you get the info about pds from?
Click to expand...
Click to collapse
Both modemst1 and modemst2 can be safely wiped without losing IMEI. When restoring Stock Firmware the following commands are included:
fastboot erase modemst1
fastboot erase modemst2​
That is not to say IMEI is not stored there temporarily; but it must exist another more permanent location. AFAIK, 'pds' is not touched by any normal fastboot firmware flashing process making it a good candidate.
EDIT: Searching XDA for "pds partition imei" turns up mainly Motorola devices. It appears to be the permanent location of a few unique device indendifiers:
Well it's kinda obvious, you need to flash a retail /pds partition. The thing is, you wont get it, cuz it has sensitive data like IMEI, MAC address, serial number, etc.​[source]

And how could I edit the pds.img to find/restore my imei?
Because if I'm in fastboot and type getvar imei it's there, but in dialer it says "0".
Any help/solutions?
Maybe with a HEX editor?

RestlessScreams said:
And how could I edit the pds.img to find/restore my imei?
Because if I'm in fastboot and type getvar imei it's there, but in dialer it says "0".
Any help/solutions?
Maybe with a HEX editor?
Click to expand...
Click to collapse
You can´t edit it, I tried to look with hex editor. That´s why it is good idea to back it up before something bad happens, sorry.
---------- Post added at 04:38 PM ---------- Previous post was at 04:32 PM ----------
lost101 said:
fastboot erase modemst1
fastboot erase modemst2​
Click to expand...
Click to collapse
Yeah, that´s what I realized too.
Even if it´s there just temporarily, it´s there and it won´t do any harm to back them up besides the pds partition.
Edit: btw just noticed that the pds size is exactly a sum of modemst1 + 2 sizes. I know that that doesn´t prove anything but...
Another thing - I´ve read somewhere from a user who compared hashes of his multiple modemst backups and they differed. Apparently there are some other non-constant infos stored there besides IMEI, that´s why it is erased during fastboot flash.

drfr said:
You can´t edit it, I tried to look with hex editor. That´s why it is good idea to back it up before something bad happens, sorry.
---------- Post added at 04:38 PM ---------- Previous post was at 04:32 PM ----------
Yeah, that´s what I realized too.
Even if it´s there just temporarily, it´s there and it won´t do any harm to back them up besides the pds partition.
Edit: btw just noticed that the pds size is exactly a sum of modemst1 + 2 sizes. I know that that doesn´t prove anything but...
Another thing - I´ve read somewhere from a user who compared hashes of his multiple modemst backups and they differed. Apparently there are some other non-constant infos stored there besides IMEI, that´s why it is erased during fastboot flash.
Click to expand...
Click to collapse
So I'm prett fuc*d ?:cyclops:

Yes for now

Here is a detailed guide for entering a new IMEI number on Droid Razor, access via BP Tools Mode:
[HOW TO][FIX] Recover your IMEI
http://forum.xda-developers.com/showthread.php?t=1960918​EDIT: In that thread someone suggests flashing the Stock Firmware Image without a SIM inserted, boot phone and skip all, proceed to home screen, shutdown, insert SIM and boot.

this way man
http://forum.xda-developers.com/showthread.php?p=50960462
follow the link above to backup and restore ur imei for moto g

sheraz1015 said:
http://forum.xda-developers.com/showthread.php?p=50960462
follow the link above to backup and restore ur imei for moto g
Click to expand...
Click to collapse
Cool thanks will try it when I get the chance
Sent from my XT1034 using xda app-developers app

[Q] Recovery can't properly access /data - WTF?

Hi all,
I don't remember when it started, but recently my Photon's recovery has been acting strange when accessing /data partition. I'm now using official TWRP 2.7.0.1, and the recovery "hot reboots" itself when wiping /data, effectively making it unable to restore backups (because to restore the /data partition it has to be wiped first). I tried an older version of CWM (6.0.1.2), and it "wipes" /data in a blink of an eye, which only means it didn't wipe successfully at all.
For reference sake, I can still use my phone normally. I can install apps, restore app backups, or even directly create/delete files in /data partition once I'm booted into Android, so the problem is only limited to recovery. I even tried RSD-ing back to stock and then start all over, but still no dice.
Any ideas would be welcome. If I need to grab any logs, please tell me which and how.

AndyYan said:
Hi all,
I don't remember when it started, but recently my Photon's recovery has been acting strange when accessing /data partition. I'm now using official TWRP 2.7.0.1, and the recovery "hot reboots" itself when wiping /data, effectively making it unable to restore backups (because to restore the /data partition it has to be wiped first). I tried an older version of CWM (6.0.1.2), and it "wipes" /data in a blink of an eye, which only means it didn't wipe successfully at all.
For reference sake, I can still use my phone normally. I can install apps, restore app backups, or even directly create/delete files in /data partition once I'm booted into Android, so the problem is only limited to recovery. I even tried RSD-ing back to stock and then start all over, but still no dice.
Any ideas would be welcome. If I need to grab any logs, please tell me which and how.
Click to expand...
Click to collapse
Recovery logs are stored in /cache/recovery .

kabaldan said:
Recovery logs are stored in /cache/recovery .
Click to expand...
Click to collapse
For TWRP, I thought it was just /tmp/recovery.log...
But either way, can you post a log from recovery after attempting to wipe?

I had something similiar when I wanted to restore a nandroid from my sdcard with TWRP (earlier, about a year ago).
At the end I chose to backup and restore on the internal sd (/data/media) instead of the external sd.
I am not sure if it was the sdcard but this solved my backup problems with TWRP.
Since then I always first backup to internal sd and then copy it to the external one.
I could not read if the problem comes by just wiping /data or while restoring a backup (which should first wipe a backup).

kabaldan said:
Recovery logs are stored in /cache/recovery .
Click to expand...
Click to collapse
Here is the last_log from TWRP 2.7.0.1: http://d-h.st/TKb . These 2 parts grabbed my attention:
Code:
I:Mount: Unable to find partition for path '/data'
and
Code:
I:wipe list '/data;'
I:wipe_path '/data'
Wiping data without wiping /data/media ...
[STRIKE]I:Unable to unlink '/data/bugreports'[/STRIKE]
I:Fixing /data/media/0 contexts
...What's that "/data/bugreports" all about?
And here's the last_log from CWM 6.0.4.8 (I built it via ClockworkMod Builder myself): http://d-h.st/zvK . These:
Code:
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Something even more strange is, although TWRP "hot reboots" / CWM "fast skips" when wiping /data, /data gets wiped anyways.
Loader009 said:
I could not read if the problem comes by just wiping /data or while restoring a backup (which should first wipe a backup).
Click to expand...
Click to collapse
Hmm, my problem can be triggered simply by attempting to wipe /data, so I'm pretty sure this is not relevant to my SD. For verification, I ejected my SD before booting into recovery, and attempted another /data wipe, which still "hot rebooted" my recovery.

AndyYan said:
Hmm, my problem can be triggered simply by attempting to wipe /data, so I'm pretty sure this is not relevant to my SD. For verification, I ejected my SD before booting into recovery, and attempted another /data wipe, which still "hot rebooted" my recovery.
Click to expand...
Click to collapse
Probably I'm talking about another problem.
Sorry, I was not sure and noticed my problem to be on the safe side.

Loader009 said:
Probably I'm talking about another problem.
Sorry, I was not sure and noticed my problem to be on the safe side.
Click to expand...
Click to collapse
I'm not sure if you're familiar with linux at all. But there's a simple fix to this solution. I had the same problem when I was using CM7 with my second OG Droid. But basically you use the following commands. If it's a problem with wiping the /Data clean out, and then rebuilding from a previous backup where the /Data directory is in tact, this is what you do. (WARNING! IF YOU ARE NOT COMFORTABLE ISSUING THESE COMMANDS, THEN DON'T.)
open up cmd prompt
Click to expand...
Click to collapse
navigate to your adb folder where the actual adb.exe file is located. Then make sure your phone is booted into recovery.
adb shell
Click to expand...
Click to collapse
that will put you in a linux environment while your phone is in recovery
ls
Click to expand...
Click to collapse
that will list all directories and files in the root of your phone make sure there is a directory called data. as long as there is, do the following.
rmdir data
Click to expand...
Click to collapse
that will delete the entire current /data structure on your phone. If you don't feel safe doing this, then don't. From there just do the recovery again.
ENJOY!

dslinfreak said:
I'm not sure if you're familiar with linux at all. But there's a simple fix to this solution. I had the same problem when I was using CM7 with my second OG Droid. But basically you use the following commands. If it's a problem with wiping the /Data clean out, and then rebuilding from a previous backup where the /Data directory is in tact, this is what you do. (WARNING! IF YOU ARE NOT COMFORTABLE ISSUING THESE COMMANDS, THEN DON'T.)
navigate to your adb folder where the actual adb.exe file is located. Then make sure your phone is booted into recovery.
that will put you in a linux environment while your phone is in recovery
that will list all directories and files in the root of your phone make sure there is a directory called data. as long as there is, do the following.
that will delete the entire current /data structure on your phone. If you don't feel safe doing this, then don't. From there just do the recovery again.
ENJOY!
Click to expand...
Click to collapse
You really sure this could deal with my issue, since you're replying to HIM instead of ME in MY question post?
EDIT: I actually risked my phone and attempted this - I think I already know ADB commands pretty well - and although /data is totally deleted, after a reboot to recovery, wiping /data still causes "hot reboot".
AND the actions also totally wiped my internal storage (because internal storage is /data/media and deleting /data also deleted it)! Thank god I don't have anything important in there...
Sent from Google Nexus 4 @ CM11

Yes, that's what I was thinking after reading his post.
It is also a little bit different problem than the one discussed here.
In your case AndyYan I simply would flash a stock ROM with RSDLite and then redo the flash recovery and ROM steps.
Because your data is already lost, this might be the fastest way.
But this way we wouldn't figure out what the current problem is. It's your choice since I don't know how fast you need the phone. I don't know if you are able to get a shell (with OpenRecovery you surely are) but what do you get if you enter "mount"? (Search for a line with /data)
With "mount" you'll get plenty of lines so it might be better to do it on the PC with "adb shell mount".
edit: With mount you get only the mounted partitions. I forgot that nothing of that is mounted. Theoretically we should be able to mount the data partition manually and format it with the right filesystem...
But I really don't know what might break, what happens to the media folder and other soft-/hardlinks.

Loader009 said:
flash a stock ROM with RSDLite and then redo the flash recovery and ROM steps.
Because your data is already lost, this might be the fastest way.
But this way we wouldn't figure out what the current problem is. It's your choice since I don't know how fast you need the phone. I don't know if you are able to get a shell (with OpenRecovery you surely are) but what do you get if you enter "mount"? (Search for a line with /data)
With "mount" you'll get plenty of lines so it might be better to do it on the PC with "adb shell mount".
edit: With mount you get only the mounted partitions. I forgot that nothing of that is mounted. Theoretically we should be able to mount the data partition manually and format it with the right filesystem...
But I really don't know what might break, what happens to the media folder and other soft-/hardlinks.
Click to expand...
Click to collapse
As said in the OP, RSD'd already but problem remains. As for mounting problems, I assume I can attempt to manually mount it, but I don't know the right command (Linux n00b).
I don't have any important data on the phone (it's not my primary device, as my signature says), everything's on the SD card, so feel free to throw suggestions/commands at me, as long as it doesn't have the risk of hard-bricking!
Sent from Google Nexus 4 @ CM11

AndyYan said:
You really sure this could deal with my issue, since you're replying to HIM instead of ME in MY question post?
EDIT: I actually risked my phone and attempted this - I think I already know ADB commands pretty well - and although /data is totally deleted, after a reboot to recovery, wiping /data still causes "hot reboot".
AND the actions also totally wiped my internal storage (because internal storage is /data/media and deleting /data also deleted it)! Thank god I don't have anything important in there...
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
I appoligize that you did this. i really was just talking to him. as for the fix, was there a stock rom already on the phone? or had you put cm10 or 11 on there? i know for a fact that their internal storage for files, pictures, music, and dowloads are stored in /sdcard on the photon q. i did enough digging on adb for the past week to memorize that file structure.
Edit: Now that /data is gone, do an advanced recovery, don't wipe data, just flash it on. this might avoid the 'hot reboot' issue. i'm about to attempt to replicate this problem on my emulator.

dslinfreak said:
I appoligize that you did this. i really was just talking to him. as for the fix, was there a stock rom already on the phone? or had you put cm10 or 11 on there? i know for a fact that their internal storage for files, pictures, music, and dowloads are stored in /sdcard on the photon q. i did enough digging on adb for the past week to memorize that file structure.
Click to expand...
Click to collapse
/sdcard is just a symlink to /data/media...

I read the thread from the beginning to be sure what has already been tried.
It looks like the /data partition is corrupted, probably even more, the partition table (which we cannot rewrite afaik).
But I give my best suggestions I have to help.
As you might imagine, I won't be able to solve your problem but I can try to search where the actual problem is.
Please correct me if I am saying something wrong!
The following commands should be entered inside "adb shell" and the output should be posted here:
mount
ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/mmcblk0p39
The first command tells us what has been mounted within the recovery. /data should be there somewhere.
The second command tells us what partitions are available. userdata is the /data partition and should be listed.
The third command is actually a confirmation. If userdata is not in the output of the second command, then this command tells us if the actual partition exists.
In the last case (userdata is not shown in the second command but the partition exists), there might be a naming issue. Theoretically a format of this partition and give it the name "userdata" should solve it.
How? Actually I know on linux the command "mkfs.ext4 /path/to/partition" with which it is possible to format a partition into the ext4 filesystem.
But how do we give it a name? I don't know. Actually this is done in the partition table and not in the partition itself.

arrrghhh said:
/sdcard is just a symlink to /data/media...
Click to expand...
Click to collapse
well, color me purple now. Not a great thing for me and now I look like an absolute retard. I think I'm gonna go back to hs now and retake linux OS.

dslinfreak said:
I appoligize that you did this. i really was just talking to him. as for the fix, was there a stock rom already on the phone? or had you put cm10 or 11 on there? i know for a fact that their internal storage for files, pictures, music, and dowloads are stored in /sdcard on the photon q. i did enough digging on adb for the past week to memorize that file structure.
Edit: Now that /data is gone, do an advanced recovery, don't wipe data, just flash it on. this might avoid the 'hot reboot' issue. i'm about to attempt to replicate this problem on my emulator.
Click to expand...
Click to collapse
It's okay, if there were any important data there I would have backed it up before you say it. And yes, /sdcard simply symlinks to /data/media.
As I described, I can flash ROMs all I want, yet I can't backup or wipe my /data, which is needed for backup ops.
Loader009 said:
I read the thread from the beginning to be sure what has already been tried.
It looks like the /data partition is corrupted, probably even more, the partition table (which we cannot rewrite afaik).
But I give my best suggestions I have to help.
As you might imagine, I won't be able to solve your problem but I can try to search where the actual problem is.
Please correct me if I am saying something wrong!
The following commands should be entered inside "adb shell" and the output should be posted here:
mount
ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/mmcblk0p39
The first command tells us what has been mounted within the recovery. /data should be there somewhere.
The second command tells us what partitions are available. userdata is the /data partition and should be listed.
The third command is actually a confirmation. If userdata is not in the output of the second command, then this command tells us if the actual partition exists.
In the last case (userdata is not shown in the second command but the partition exists), there might be a naming issue. Theoretically a format of this partition and give it the name "userdata" should solve it.
How? Actually I know on linux the command "mkfs.ext4 /path/to/partition" with which it is possible to format a partition into the ext4 filesystem.
But how do we give it a name? I don't know. Actually this is done in the partition table and not in the partition itself.
Click to expand...
Click to collapse
Here's the full output:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
[B]/dev/block/mmcblk0p39 on /data type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)[/B]
/dev/block/mmcblk0p39 on /sdcard type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
~ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2014-05-18 00:52 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-05-18 00:52 abootBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-05-18 00:52 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-05-18 00:52 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2014-05-18 00:52 carriercust -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2014-05-18 00:52 cdrom -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2014-05-18 00:52 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-05-18 00:52 devtree -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-05-18 00:52 dhob -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-05-18 00:52 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-05-18 00:52 hob -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-05-18 00:52 kpan -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-05-18 00:52 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-05-18 00:52 mbl -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-05-18 00:52 misc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-05-18 00:52 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-05-18 00:52 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-05-18 00:52 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-05-18 00:52 padA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-05-18 00:52 padB -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-05-18 00:52 pds -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-05-18 00:52 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-05-18 00:52 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-05-18 00:52 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-05-18 00:52 rpmBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-05-18 00:52 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-05-18 00:52 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-05-18 00:52 sbl2Backup -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-05-18 00:52 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-05-18 00:52 sbl3Backup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-05-18 00:52 sp -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-05-18 00:52 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-05-18 00:52 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2014-05-18 00:52 tombstones -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2014-05-18 00:52 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-05-18 00:52 tzBackup -> /dev/block/mmcblk0p14
[B]lrwxrwxrwx root root 2014-05-18 00:52 userdata -> /dev/block/mmcblk0p39[/B]
lrwxrwxrwx root root 2014-05-18 00:52 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-05-18 00:52 utagsBackup -> /dev/block/mmcblk0p15
~ # ls -al /dev/block/mmcblk0p39
ls -al /dev/block/mmcblk0p39
brw------- root root 259, 7 2014-05-18 00:52 mmcblk0p39
As you can see, /data and userdata both exists.
Furthermore, using TWRP, I can even use its file manager to delete files, modify permissions, etc. in /data, just can't wipe it or back it up (backing up /data usually takes 20+ seconds, but now it's completed in a flash).

For me everything looks ok.
The partition is mounted and the recovery can access the partition.
It should work but it doesn't.
I am kind of clueless.
If I remember correctly, there was in TWRP an option to wipe data/internal storage (or something like that).
Could you try this one? (And post the last_log again.)
I think that it wipes in a blink of an eye because there is nothing to delete.
With the wipe data/internal storage I think it formats the partition instead of doing a "rm -R" (wipe data) on several folders. (I think it is rm -R, I don't actually know it.)
I have problems if I backup data from (external) sdcard. I have to move my backup to the internal storage (not in a recovery!) to successfully restore my backup.
It is annoying, but I haven't found a solution to be 100% sure that the recovery reads the backup correctly from the (external) sdcard.

What about a recovery.log after the failed attempt?

He already has:
AndyYan said:
Here is the last_log from TWRP 2.7.0.1: http://d-h.st/TKb.
[...]
And here's the last_log from CWM 6.0.4.8 (I built it via ClockworkMod Builder myself): http://d-h.st/zvK.
[...]
Something even more strange is, although TWRP "hot reboots" / CWM "fast skips" when wiping /data, /data gets wiped anyways.
Click to expand...
Click to collapse

Loader009 said:
If I remember correctly, there was in TWRP an option to wipe data/internal storage (or something like that).
Could you try this one? (And post the last_log again.)
I think that it wipes in a blink of an eye because there is nothing to delete.
With the wipe data/internal storage I think it formats the partition instead of doing a "rm -R" (wipe data) on several folders. (I think it is rm -R, I don't actually know it.)
I have problems if I backup data from (external) sdcard. I have to move my backup to the internal storage (not in a recovery!) to successfully restore my backup.
It is annoying, but I haven't found a solution to be 100% sure that the recovery reads the backup correctly from the (external) sdcard.
Click to expand...
Click to collapse
I tried the "format data" option like you said, and it seems to go nicely - the log says it recreated filesystem properly - until it "hot reboots" again. Bang it. Log attached: http://d-h.st/chh
I have always been backing up to/restoring from external SD card without any flaws. Now I can't restore my backup, but only because restoring backup involves wiping /data...

Loader009 said:
He already has:
Click to expand...
Click to collapse
I kept looking for recovery.log... haha.
Nothing brilliant is coming to me at the moment, I will ask some people (much) smarter than I...

[Q] VERIZON Samsung Tab 2 10.1 sch-i915 Hardbrick help

I have an incident that I have accrued myself so no need for those comments. The history of the hardbrick i created. If any information regarding anything feel free.
First of all i rooted my device using towelroot. It works for alot of devices and runs as 3rd party apk installer. Created by the infamous Geohotz. Godbless. https://towelroot.com/ for those of you who do not know.
2nd i was looking and trying to swap my extSdCard with my internal /sdcard. I edited the vold.fstab and the vold.conf files thinking hey i can use the external as full internal to have the devive install apps on properly w/o manually moving and use the internal remaining sdcard memory as virtual Ram. I have not completed this process yet. Ill explain.
After mounting the internal as external and vice. I ended up being stuck in a boot loop. NOTE: i did not have custom recovery(was one of the oopsies) so was stuck with basic android recovery. Reset device did not fix. Was going to Odin flash the stock rom and/or CWM Recovery, but there is absolutely NO STOCK or LEAKED rom anywhere for the verizon model. I also pulled those 2 files off of my other tab 2 10.1 NON VERIZON *vold.fstab and vold.conf and places it into zip file and signed it using signapk.
which now i feel like an idiot finding this link "http://forum.xda-developers.com/galaxy-nexus/themes-apps/tutorial-making-flashable-zips-edify-t1611615"
NOTE: I used a different post somewhere that didnt explain to have the right binary so it gave me a signature mismatch error when trying to flash. Use above post to make sure you use propery binary.
Luckily i did some research and knowledge of what i actually did to fix it and plus my addiction to play around and learn things. I manually duplicated the vold.fstab/vold.conf files from my one device to the bricked one
Boot up device in Android recovery.
installed and loaded up ADB.exe from command line.
Code:
adb shell
su
echo *yourlinehere*> /system/etc/vold.fstab
echo *yourlinehere*>> /sytem/etc/vold.fstab
the first > rewrites the file from start black document and inputs the first line
the 2nd >> note the double >> appends to the next line.
i rebooted and VOILA FIXED!!! but wait....theres more ><
So knowing the troubles i had to fix my lil play around mistake. I wanted to get custom recovery partition installed. Used Rom Manager to install CWM Recovery. I picked the wrong rom for my device and flashed it. The one i used was for the international Tab 2 10.1 the gt-5100. It said it successfully flashed so i figured wth it couldnt hurt right? WRONG i clicked reboot to recovery to check it. and here is where I lie. HARD BRICK. No boot up at all. Plug in charger to outlet or PC i dont even get the charging device battery image. So now here we go more research fun!!!
I looked up some information on how to fix a hard bricked device. some posts say using a jig to bypass it and get into download mode. Ok this is a 30 pin connector not a 4 pin like most the android devices. I could do some research on this and probably rig a jig to convert and match the pin layouts but meh my problem still lies within not having stock firmware for this model. I also learn of Jtag methods. Oh all well and handy but buying the Riff Box and all this gets your device bootable, but hey guess what? it would allow me to boot into that download mode or android recovery. Which still bottom line fails as i dont have a stock rom to flash. OH the dilemna.
What ive come up with. I plugged in my device into my pc. Well what do you know i can actually get recognition. but this is where i am stuck at.
I figured out that the device is recognized and i needed drivers. I found this handy site
https://developer.qualcomm.com/forum/qdevnet-forums/general-discussion/9428 Which also explains that i messed up my boot partition.
I download and installed the QPST program and installed the drivers on win7. I had to reboot and use advanced options to disable the unsigned drivers check. OK sweet connection is up!
I tried using ADB shell but device isnt connected that way.
In the QPST program it shows my device on com10 in download mode. I tried to retrieve some data or partition information from the device but it says i cannot when device is in download mode. So no pulling files and fixing and reflashing them. Back to the same problem before NO STOCK ROM.
So here are the questions I have regarding my situation. The android device im playing with has the base partitions. As an example of this http://www.all-things-android.com/content/review-android-partition-layout
I do not have my partition layout for my device as its bricked. I dont even know if it needs to be repaired yet. If any of you with a verizon tab 2 10.1 sch-i915 has a rooted device and can get me this table or a pit file for this device it would be appreciated
2nd firmware vs firmware. As previously stated I do not have firmware for this verizon tab. HOWEVER i did find firmware for the Sprint version of this exact tablet. My question is, could these stock firmwares be exact duplicates with the exclusion of the boot up screen bs and the /misc partition containing the imei phone stats and carrier information?
3rd Flashing just certain partitions of this firmware. Is it possible if the above is feasible considering i know my /boot partition is messed up and my /recovery partition is messed up to only flash those 2 partitions with the one from sprint. The stock kernal should be the same in both devices for the /boot and the /recovery partition should hold the same android recovery should it not?
4th. If anyone has a rooted sch-i915 device would you be willing to make dump of the partitions using this guide http://forum.xda-developers.com/showthread.php?t=2450045. That would be appreciated.

Let Me Work On That
You Are Possibly In Luck. I Know Somone That Has That Tablet. Problem Is It Is My Mom's And Well She Rather Beat Me With It Then Let Me Touch It. I'll See What I Can Do And Will Post Back.. Wish Me Luck i Will Need It :fingers-crossed:

][NT3L][G3NC][ said:
You Are Possibly In Luck. I Know Somone That Has That Tablet. Problem Is It Is My Mom's And Well She Rather Beat Me With It Then Let Me Touch It. I'll See What I Can Do And Will Post Back.. Wish Me Luck i Will Need It :fingers-crossed:
Click to expand...
Click to collapse
Appreciated good luck.
If not possible and i get it fixed ill post how i did it and such. and also post up a JB 4.12 stock/updated leaked rom of this device which apparently seems to be missing in the world for some damn reason.

I Got A Question
Sorry I Been Busy, & Google Has Not Been Kind 2 Me. I Did Find The California Lottery Vulnerability Report Generated By Nessus. But If Someone Could Please Point Me In The Right Direction Or Just Break It Down For Me As Quickly And Light As You Could, Short, Straight Forward, The LIghtest Kliff Notes Ever Would Be Appreciated.
Verizion SCH-I915 [ 4.1.2 ]
I Only Had A Few Minutes With The Tablet But I Already Rooted It, Installed BusyBox, I Barely Started To Get Into The FIle System.... I'm Using Kali LInux
1. What Partitions/Blocks Do I Need To Obtain To Create An Odin Flashable Recovery Image
2. Is There A Droid Binary, Or Script I Can Use To Dump The Rom While Creating The Above For Odin?
Just Found Something I Downloaded At Some Point Called: ROMGEN Any Idea On That Binary??? And phantomphr33k Any Request.
Forgive Me I Work Nights, Two Kids, So I'm Up Days + On Call During The Day.
lrwxrwxrwx root root 1970-10-27 01:41 aboot -> /dev/block/mmcblk0p5 ???
lrwxrwxrwx root root 1970-10-27 01:41 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-10-27 01:41 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-10-27 01:41 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-10-27 01:41 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-10-27 01:41 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-10-27 01:41 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-10-27 01:41 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-10-27 01:41 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-10-27 01:41 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-10-27 01:41 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-10-27 01:41 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-10-27 01:41 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-10-27 01:41 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-10-27 01:41 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-10-27 01:41 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-10-27 01:41 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-10-27 01:41 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-10-27 01:41 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-10-27 01:41 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-10-27 01:41 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-10-27 01:41 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-10-27 01:41 userdata -> /dev/block/mmcblk0p15

Should Post The Rest Tomorrow
I Have Attached Some Text Files With The Output Of A Couple Commands To Get The block/partition layout.
I Have Dumped The system.img which is 1.6gb In SIze
Tomorrow I Should Have : Modem "firmware" , Boot , Recovery
QUESTIONS:
What Is aboot?
Which Is The Kernel?
What Is Modemst*?
And More Important, Which Ones Do I Need To Pull For A Complete ROM Dump?
lrwxrwxrwx 1 0 0 20 Nov 2 1970 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 0 0 21 Nov 2 1970 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 0 0 20 Nov 2 1970 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 0 0 21 Nov 2 1970 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 0 0 21 Nov 2 1970 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 0 0 21 Nov 2 1970 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 0 0 21 Nov 2 1970 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 0 0 21 Nov 2 1970 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 0 0 20 Nov 2 1970 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 0 0 21 Nov 2 1970 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 0 0 21 Nov 2 1970 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 0 0 20 Nov 2 1970 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 0 0 21 Nov 2 1970 param -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 0 0 21 Nov 2 1970 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 0 0 21 Nov 2 1970 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 0 0 20 Nov 2 1970 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 0 0 20 Nov 2 1970 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 0 0 20 Nov 2 1970 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 0 0 20 Nov 2 1970 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 0 0 21 Nov 2 1970 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 0 0 21 Nov 2 1970 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 0 0 20 Nov 2 1970 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 0 0 21 Nov 2 1970 userdata -> /dev/block/mmcblk0p15

Sorry its the Holidays so its understandable. Cant really twist your arm to rush it Im by far not an expert on this i do research myself. Ill do my best and if anyone else can shed light please do.
][NT3L][G3NC][ said:
QUESTIONS:
[*]What Is aboot?
[*]Which Is The Kernel?
[*]What Is Modemst*?
[*]And More Important, Which Ones Do I Need To Pull For A Complete ROM Dump?
Click to expand...
Click to collapse
1) Aboot partition is basically your "Odin Downloader" protocol. while booting pressing power + Vol Dwn will put your device in this mode.
2) The kernel/ramdisk is stored in the /boot partition
Note Primary Bootloader and SB* are secondary bootloaders 1,2,3 those are loaded up as well to set certain params + setup/initialize hardware as far as im understanding. and loads up the kernel/ramdisk.
3)Ill quote from another thread: http://forum.xda-developers.com/showthread.php?t=2582811
][NT3L][G3NC][ said:
- backup and restore important device partitions - EFS (Samsung), TA (Sony), MODEM (Exynos devices), MODEMST1 & MODEMST2 (Qualcomm devices),
- root is required
- easy to use
- many localizations
- see paths to important partitions of your device using Menu -> Device Partitions
Click to expand...
Click to collapse
As far as im understanding these partitions hold carrier information/imei and all other sorts of GRPS information in regards to connecting your devices radio to Service. Sorta like your network card drivers and Mac Address
I looked at another persons rom dump and I seen only these partitions in the archive. Sadly I dont remember where i found this but is from a guy who JTAGS devices. So im pretty sure its legit. Its from the Sprints version of this device.
/system.img.ext4(going to be the biggest dump)
/recovery.img
/cache.img.ext4
/boot.img
[QUOTE=']
1. What Partitions/Blocks Do I Need To Obtain To Create An Odin Flashable Recovery Image
2. Is There A Droid Binary, Or Script I Can Use To Dump The Rom While Creating The Above For Odin?
Just Found Something I Downloaded At Some Point Called: ROMGEN Any Idea On That Binary??? And phantomphr33k Any Request.
[/QUOTE]
So basicallly special request if you could is mainly dump those partitions above
This Romgen seemingly looks to dump what is needed for the rom. It also makes and update-script flashable Odin file. Never tried it myself. ive used cygwin/kitchen personally.
If you would do that would be sufficient as a stock rom. Granted if the rom is updated its not stock.....BUT at least it will be an updated stock vwz sch-i915 out there in public finally.
AND...extra special request is a pit file. Reason being is i need to attempt to flash by other means not via odin.(more personal use than general public) and i need the block information to flash partitions to the chip at the certain points. Im extracting the *.img/bin files and compiling *.mbn files and going to attempt to flash directly to the chip. As far as ive seen its worked on a few other devices and i might as well try considering this is a Qualcomm device and it is recognized in QPST. Maybe the security on the bootloader may not allow it but what could it hurt? its already hard bricked right? lol
http://forum.xda-developers.com/showthread.php?t=1916936
program here for windows. I never checked for any linux based tools cuz i use cygwin if i absolutely need linux.
Much appreciated ][NT3L][G3NC][ your making my day :laugh:

happy new years intelligence since it seems ur the only one to view this thread.

so did you ever get a good romdump? I have been trying all night to do it to mine but can not get it to work.

K1 Not booting after flashing stock image

Yesterday I flashed BitO-KU kernel with dtb and blob file provided in this thread https://forum.xda-developers.com/sh.../tweaked-kernel-nvidia-shield-tablet-t3069776 on my Shield Tablet K1. Since then the problem started and my tab didn't boot.
How problem started?
Flashed BitO-KU kernel https://forum.xda-developers.com/sh.../tweaked-kernel-nvidia-shield-tablet-t3069776
Reboot (working fine)
Flashed dtb file "tegra124-tn8-p1761-1270-a04-e-battery.dtb" (provided in same thread)
Reboot (stuck on bootloader)
Flashed blob file (provided in same thread)
Reboot (stuck on bootloader)
After that I flashed factory images provided on Nvidia official site for K1 Tablet but still not booting. Although many times I have successfully flashed firmware images before, but only this time it's not booting. I think that the dtb and blob files I flashed previously with BitO-KU kernel were for Original Shield Tablet not for K1, that's why my tablet bricked.
What's working and what's not:
Bootloader is working and able to flash files using fastboot. But it's niether showing any error nor booting after flashing firmware images.
Recovery Not Working. Flashed various versions of TWRP from official website, none of them is working. Even tried directly booting to twrp recovery instead of flashing, still not working.
Any help is appreciated.
Sorry for my bad English!

Did you flash the stock system file and the stock blob? I think the instructions (recovery image) say to flash a few other things (recovery, userdata) but I was able to just flash the system and blob (flashing stock recovery might not hurt either).
Also, please don't apologize for your bad English. Your post is very well written, and I never would have guessed you are not a native English speaker.

redpoint73 said:
Did you flash the stock system file and the stock blob? I think the instructions (recovery image) say to flash a few other things (recovery, userdata) but I was able to just flash the system and blob (flashing stock recovery might not hurt either).
Also, please don't apologize for your bad English. Your post is very well written, and I never would have guessed you are not a native English speaker.
Click to expand...
Click to collapse
Hi @redpoint73, thanks for your response. Yes I did flash the stock system file, stock blob file and stock boot file. Still it wasn't booting.
And thanks for your compliment about my English.

Hello,
I was in a similar situation but finally managed to fix this boot issue on my K1.
What I have, Nvidia Shield Tablet K1
What I did wrong, flashed via fastboot a stock ROM image from Nvidia GameWorks - SHIELD Open Source Resources and Drivers
But not the correct one for Shield K1
I had the following steps for this recovery ROM (not for K1 tablet...):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
fastboot reboot
Flashing them failed on userdata (not enough space) and results in K1 to be stuck on boot and the Nvidia logo for ages.
(For a K1 tablet, you don't have a userdata and dtb flash image steps). I think what messed up my K1 is the dtb flashing step because formating, erasing and flashing recovery, boot, system and userdata partitions didn't have any effects on being stuck at boot.
What I did to get out of this mess and what you need:
Stock ROM K1: nv-recovery-image-shield-tablet-k1-factory0_0_0
fastboot + adb
twrp for K1 for revovery partitions
And know your K1 partitions
Via adb shell:
cd /etc
cat recovery.fstab
shieldtablet:/etc # cd /etc
shieldtablet:/etc # cat recovery.fstab
Result:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc wait,formatable
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=writeback,noauto_da_alloc wait,check,formatable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/RP3 /usercalib ext4 noatime,data=writeback wait,formatable
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host* auto vfat defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/tegra-ehci.0/usb* auto vfat defaults voldmanaged=usb:auto
/dev/block/platform/sdhci-tegra.2/by-num/p1 /sdcard vfat defaults recoveryonly
Via adb shell:
cd dev/block/platform/sdhci-tegra.3/by-name/
ls -al
Resust:
shieldtablet:/dev/block/platform/sdhci-tegra.3/by-name # ls -al
total 0
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxr-xr-x 2 root root 520 2019-11-19 08:27 .
drwxr-xr-x 4 root root 600 2019-11-19 08:27 ..
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 APP -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 CAC -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 CHG -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 DTB -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 EKS -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 FB -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FBP -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FCG -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FCT -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 GPT -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 LBP -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 LNX -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 MDA -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 MSC -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 NCT -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP2 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP3 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP4 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 SOS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 TOS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 UDA -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 USP -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 WB0 -> /dev/block/mmcblk0p5
MAP boot, system, blob (staging) partitions with corresponding memory block
Ex: boot -> LNX -> /dev/block/mmcblk0p12
Via adb shell and using the images from K1 ROM nv-recovery-image-shield-tablet-k1-factory0_0_0 (check if your tablet k1 has the same partitions)
dd if=boot.img of=/dev/block/mmcblk0p12
dd if=system.img of=/dev/block/mmcblk0p13
dd if=blob of=/dev/block/mmcblk0p16
By getting from another ROM: tegra124-tn8-p1761-1270-a04-e-battery.dtb (renamed tegra124.dtb)
dd if=tegra124.dtb of=/dev/block/mmcblk0p11
Still failing... and stuck at boot so I decided to restore nv-recovery-image-shield-tablet-k1-factory0_0_0 via fastboot a last time but cleaned everything first:
twrp wipe all system cache data
then
fastboot flash system
fastboot erase boot
fastboot flash boot
fastboot erase staging
fastboot flash staging blob
fastboot reboot
And my Shield Tablet K1 was working again!! And very happy to have my Nvidia Shield K1 back (with latest LineageOS 15.1 ROM and working like a charm)!
I did a lot of stock ROM erase / format / restore on these partitions before and they all failed before. But I thing here the main difference is around the DTB partition.
May be the dd if=tegra124.dtb of=/dev/block/mmcblk0p11 step did properly restore the dtb info and partition or actually "corrupt" it in a way that cause the K1 to properly boot back. I don't know.
Hope that can help someone in the same situation!