formatted /persist and /firmware - G 2014 Q&A, Help & Troubleshooting

Hello everyone, last night i was trying the PhilZ Touch CWM recovery and in the wipe section it has an option to format /persist and /firmware, so being very stupid i formatted those partitions and when i tried to install a new rom i couldn't connect to wifi, i fixed that with this http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308 and everything seems to work perfectly in stock rom, i must admit i was very afraid, but now i'm curious because i search a little and others phones have drm files or more folders (i only have a lost+found folder and to 2 more .bin archives) and i was wondering if any of you ever had done the same as me or know more about it and could help me if i'll have problems in the future for my stupid behavior. Thanks

kievam said:
Hello everyone, last night i was trying the PhilZ Touch CWM recovery and in the wipe section it has an option to format /persist and /firmware, so being very stupid i formatted those partitions and when i tried to install a new rom i couldn't connect to wifi, i fixed that with this http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308 and everything seems to work perfectly in stock rom, i must admit i was very afraid, but now i'm curious because i search a little and others phones have drm files or more folders (i only have a lost+found folder and to 2 more .bin archives) and i was wondering if any of you ever had done the same as me or know more about it and could help me if i'll have problems in the future for my stupid behavior. Thanks
Click to expand...
Click to collapse
/firmware = modem = flash NON-HLOS.bin from stock package.
And this is how /persist should look like:
Code:
[email protected]:/persist # find
.
./lost+found
./WCNSS_qcom_wlan_factory_nv.bin
./WCNSS_qcom_wlan_nv.bin
./sensors
./sensors/sensors_settings
./.bt_nv.bin
./prov
./prov/randomString1_
./prov/randomString1_/randomString2_
./prov/randomString1_/randomString3_
./prov/randomString1_/randomString4_
./prov/randomString1_/randomString5_
./data
./data/app_g
./data/app_g/randomString1_
./data/app_g/randomString1_/randomString6_
./data/app_g/randomString1_/randomString7_
./data/app_g/randomString1_/randomString8_

LuK1337 said:
/firmware = modem = flash NON-HLOS.bin from stock package.
And this is how /persist should look like:
Code:
[email protected]:/persist # find
.
./lost+found
./WCNSS_qcom_wlan_factory_nv.bin
./WCNSS_qcom_wlan_nv.bin
./sensors
./sensors/sensors_settings
./.bt_nv.bin
./prov
./prov/randomString1_
./prov/randomString1_/randomString2_
./prov/randomString1_/randomString3_
./prov/randomString1_/randomString4_
./prov/randomString1_/randomString5_
./data
./data/app_g
./data/app_g/randomString1_
./data/app_g/randomString1_/randomString6_
./data/app_g/randomString1_/randomString7_
./data/app_g/randomString1_/randomString8_
Click to expand...
Click to collapse
Thank you so much for the answer!, i only have ./lost+found ./WCNSS_qcom_wlan_factory_nv.bin y ./.bt_nv.bin, any idea what are the others for?

kievam said:
Thank you so much for the answer!, i only have ./lost+found ./WCNSS_qcom_wlan_factory_nv.bin y ./.bt_nv.bin, any idea what are the others for?
Click to expand...
Click to collapse
No, I dunno.

Related

[DUMP] Motorola Atrix 4G U4_1.5.2

Hi!
This is a dump of [FLASH_SBF] Motorola Atrix 4G U4_1.5.2
Kernel config, initramfs + recovery Code Group 56 / Partition 10 / Recovery --- Code Group 55 / Partition 11 / Kernel
Modem (new ver: oly17706 stock: oly17705) (Code Group 5)
/system - mirror (Code Group 57)
/osh (Code Group 58)
I'll post the other partitions shortly.
Stock ----------------
ro.build.id=OLYFR_U4_1.2.6
ro.build.display.id=OLYFR_U4_1.2.6
ro.build.version.incremental=1296900353
ro.build.date=Sat Feb 5 03:11:10 CST 2011
ro.build.date.utc=1296897070
ro.build.user=w19091
ro.build.host=il93lnxdroid46
ro.build.description=olympus-user 2.2.1 OLYFR_U4_1.2.6 1296900353 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/olyatt/olympus/olympus:2.2.1/OLYFR_U4_1.2.6/1296900353:user/ota-rel-keys,release-keys
ro.build.version.full=Blur_Version.4.1.26.MB860.ATT.en.US
Update ----------------
ro.build.id=OLYFR_U4_1.5.2
ro.build.display.id=OLYFR_U4_1.5.2
ro.build.version.incremental=1298398352
ro.build.date=Tue Feb 22 09:28:35 PST 2011
ro.build.date.utc=1298395715
ro.build.user=fpgh48
ro.build.host=ca25rhe85
ro.build.description=olympus-user 2.2.1 OLYFR_U4_1.5.2 1298398352 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/olyatt/olympus/olympus:2.2.1/OLYFR_U4_1.5.2/1298398352:user/ota-rel-keys,release-keys
ro.build.version.full=Blur_Version.4.1.52.MB860.ATT.en.US
Da_G said:
Hi!
This is a dump of [FLASH_SBF] Motorola Atrix 4G U4_1.5.2
System - [font size=-2]mirror[/font]
I'll post the other partitions shortly.
Click to expand...
Click to collapse
If I may ask, how did you pull the Dump?
hes da_g, thats how he did it.
There are a couple sbf tools available that will separate out the CGs (Code Groups) from the .sbf (which is a container for the CGs and a few other things)
I used RSD Lite which splits them out, each is an image of the partition (like one made with dd) so you can do:
Code:
mount -o loop ~/olyfr_u4_1.5.2_signed_olpsattspe_p012_hwolympus_1g_1ffCG57.smg /mnt/atrix
which mounts the filesystem to /mnt/atrix letting you read everything out
Ok so pretty much the currently available version of RSD (4.9) can read the SBF just not flash it to the Atrix. Thanks!
Da_G said:
There are a couple sbf tools available that will separate out the CGs (Code Groups) from the .sbf (which is a container for the CGs and a few other things)
I used RSD Lite which splits them out, each is an image of the partition (like one made with dd) so you can do:
Code:
mount -o loop ~/olyfr_u4_1.5.2_signed_olpsattspe_p012_hwolympus_1g_1ffCG57.smg /mnt/atrix
which mounts the filesystem to /mnt/atrix letting you read everything out
Click to expand...
Click to collapse
Si Senor. Yes Sir!
Sorry I am trying to learn all the limbo.. what the significance of a dump? is that a copy of the sbf?
It's a file archive (specifically .tar.gz, which is comparable to a .zip or a .rar) with all the files in the filesystem. So it's not a copy of the .sbf, but another way of presenting the same data. And with root you can shuffle these files in by remounting /system rw and copying them in, to try out new stuffs
edit: updated first post with /osh dump
Da_G said:
It's a file archive (specifically .tar.gz, which is comparable to a .zip or a .rar) with all the files in the filesystem. So it's not a copy of the .sbf, but another way of presenting the same data. And with root you can shuffle these files in by remounting /system rw and copying them in, to try out new stuffs
edit: updated first post with /osh dump
Click to expand...
Click to collapse
Hey G, exactly whats new in this? How do I remount the new stuff? You make everything sound so simple!
Well, for example, if you wanted to pull out an app you could grab the .apk from the dump, deodex it, and introduce it into your current rom..
I think it's likely possible to directly flash the .smgs to NAND too, bypassing the bootloader. I did some testing with Fenrir on IRC that resulted in a brick (all hail!) but before the brick happened we were successful in flashing a (signed) part of the NAND without issue.
(uploaded kernel config, initramfs, modem)
Da_G said:
Well, for example, if you wanted to pull out an app you could grab the .apk from the dump, deodex it, and introduce it into your current rom..
I think it's likely possible to directly flash the .smgs to NAND too, bypassing the bootloader. I did some testing with Fenrir on IRC that resulted in a brick (all hail!) but before the brick happened we were successful in flashing a (signed) part of the NAND without issue.
(uploaded kernel config, initramfs, modem)
Click to expand...
Click to collapse
Any exciting things inside? That are worth checking? Is the modem different?
Da_G said:
Well, for example, if you wanted to pull out an app you could grab the .apk from the dump, deodex it, and introduce it into your current rom..
I think it's likely possible to directly flash the .smgs to NAND too, bypassing the bootloader. I did some testing with Fenrir on IRC that resulted in a brick (all hail!) but before the brick happened we were successful in flashing a (signed) part of the NAND without issue.
(uploaded kernel config, initramfs, modem)
Click to expand...
Click to collapse
can you write to /sys folder with mounting ? if so i will stop what im doing as i have something to try
dumb question, but is there any rsd lite version that will flash this onto the atrix? not that i plan to do it, just want to learn.
t0dbld said:
im confused are you guys all not running this version already? I have 2 atrix in my hands this is same build i have ran sense day 1 are some of you running different versions? also what are than your build dates ?
Click to expand...
Click to collapse
I'm on Build # U4.1.2.6 so....
franciscojavierleon said:
dumb question, but is there any rsd lite version that will flash this onto the atrix? not that i plan to do it, just want to learn.
Click to expand...
Click to collapse
Not right now. Tomorrow maybe.
@Fixter:
The modem is 1 version higher (info in first post) changes are negligable.
@t0dbld:
Yes, you are free to read/write the whole /system partition. (with root) (edit: after talking on irc i realize you meant /sys which is a kernel interface rather than a partition, you can't write to it like a partition, but you can change some config settings there)
And should any (very) brave souls want to try flashing through a completely manual, arcane, scary, possibly deadly to your device method, I might have a way to bypass the bootloader for writing the sensitive areas of NAND that would normally be signature checked. With some testing were able to write a few 1KB chunks without issue, when tried a whole image it bricked, failing security check on next boot. Have some ideas how to get around that though, maybe better to try when a working RSD/SBF combo is available for easy recovery
Da_G said:
@Fixter:
The modem is 1 version higher (info in first post) changes are negligable.
@t0dbld:
Yes, you are free to read/write the whole /system partition. (with root)
And should any (very) brave souls want to try flashing through a completely manual, arcane, scary, possibly deadly to your device method, I might have a way to bypass the bootloader for writing the sensitive areas of NAND that would normally be signature checked. With some testing were able to write a few 1KB chunks without issue, when tried a whole image it bricked, failing security check on next boot. Have some ideas how to get around that though, maybe better to try when a working RSD/SBF combo is available for easy recovery
Click to expand...
Click to collapse
Hi, will this resolve my Atrix 4G's problem of unable to detece network carriers after using *#*#4636#*#* code to check the radio band?
My 4G now can only dial emergency calls. Can I share with u the attached docment and hopefully you can give me some advice if I can resolve my problem.
Thanks so much...
Da_G said:
There are a couple sbf tools available that will separate out the CGs (Code Groups) from the .sbf (which is a container for the CGs and a few other things)
I used RSD Lite which splits them out, each is an image of the partition (like one made with dd) so you can do:
Code:
mount -o loop ~/olyfr_u4_1.5.2_signed_olpsattspe_p012_hwolympus_1g_1ffCG57.smg /mnt/atrix
which mounts the filesystem to /mnt/atrix letting you read everything out
Click to expand...
Click to collapse
nice, just like the rfs files from the captivate
Da_G said:
@Fixter:
The modem is 1 version higher (info in first post) changes are negligable.
@t0dbld:
Yes, you are free to read/write the whole /system partition. (with root) (edit: after talking on irc i realize you meant /sys which is a kernel interface rather than a partition, you can't write to it like a partition, but you can change some config settings there)
And should any (very) brave souls want to try flashing through a completely manual, arcane, scary, possibly deadly to your device method, I might have a way to bypass the bootloader for writing the sensitive areas of NAND that would normally be signature checked. With some testing were able to write a few 1KB chunks without issue, when tried a whole image it bricked, failing security check on next boot. Have some ideas how to get around that though, maybe better to try when a working RSD/SBF combo is available for easy recovery
Click to expand...
Click to collapse
RSD 5 is in the release thread now, seems to be working here so far
t0dbld said:
can you write to /sys folder with mounting ? if so i will stop what im doing as i have something to try
Click to expand...
Click to collapse
Are you trying to write to /sys or /system? Also, what are you trying to do?
ok serious question that might sound dumb.
how far are from unlocked bootloader ?
i mean i see everyone is so excited. but i dont know what does that mean .
can someone explain to me in simple way so i can thank him ? lol

[L3] [MOD] CWM recovery for e400 [CM/MIUI/SDMERGE]

Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
I also included the recovery for the SDMerge and also a linux script. Sorry, but the archive is too big to post it here on xda so i had to upload it on 4shared.
Requirements:
1) Rooted phone (obviously!!)
Instuctions Windows:
1) Download the package from 4shared
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
Instructions Ubuntu/Debian/Mint:
1) Download the package from 4shared
2) Extract it
3) Make sure you have the sdk properly installed with adb (if not check here: http://forum.xda-developers.com/showthread.php?t=2100673 )
4) Run the script by typing
Code:
./CWM-Installer.sh
5) Enjoy the new recovery
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /data/local/recovery.img
or if you want the recovery for the SDMerge just replace:
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
with this:
Code:
Files\adb push Files\SDmergerecovery.img /data/local/recovery.img
And then run the script again.
Feel free to post comments!!
Download here:
http://www.4shared.com/archive/8HmnogYQ/CWM-Installer-E400tar.html
wow, long time no see...
keep it up buddy
yayakuya said:
wow, long time no see...
keep it up buddy
Click to expand...
Click to collapse
Thanks yaya, I was busy with work and home and I haven't internet at home so I can't download the huge GBs of a repo.
Works like said great job keep it up buddy!
Cobmaster said:
Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
Requirements:
1) Rooted phone (obviously!!)
Instuctions:
1) Download the attachment
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
IT DOESN'T WORK WITH SDMerge MOD!!!
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /mnt/extra-sd/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /mnt/extra-sd/recovery.img
And then run the script again.
Feel free to post comments!!
Click to expand...
Click to collapse
i created a flashable zip for the recovery her it is please thank me.:good:
jeffreyvh said:
i created a flashable zip for the recovery her it is please thank me.:good:
Click to expand...
Click to collapse
I used the script written a long time ago for who has only the device rooted but hasn't the recovery installed... Btw good job!
@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)
andwie said:
@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)
Click to expand...
Click to collapse
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).
Cobmaster said:
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).
Click to expand...
Click to collapse
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort
andwie said:
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort
Click to expand...
Click to collapse
Here it is, to flash it use my script replacing the recovery.img with the one attached and report if it works or not.
Btw, are you sure that the "/data" partition is ext4? Because if it's wrong the recovery doesn't mount it.
Very sorry for the very late reply, I just had the time to test your new recovery (I had to create flashable zip for it since the script didn't work) and it work perfectly.
Now we have alternative to increase data partition without having to edit apps like gellmar's StockMergE400, means it will be compatible with all stock-based rom :victory:
Thanks again @Cobmaster :good:
Don't worry about it. It's very pleasing to see that it works.
hi!
 @Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good
dricoarmani said:
hi!
@Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good
Click to expand...
Click to collapse
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Cobmaster said:
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Click to expand...
Click to collapse
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off
Axims said:
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off
Click to expand...
Click to collapse
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium
Cobmaster said:
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium
Click to expand...
Click to collapse
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?
lomax84 said:
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?
Click to expand...
Click to collapse
only use gellmar recovery, because it is fixed for sdmerge
kien_vip said:
only use gellmar recovery, because it is fixed for sdmerge
Click to expand...
Click to collapse
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2
lomax84 said:
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2
Click to expand...
Click to collapse
it contain in step 2 or you can see it on some sdmerge rom

Device Essential Material *** Firmware, Source Code, Root etc.***

This thread will list and link to all core device essential stuff.
PM me if there is new stuff or something doesn't work please​
STOCK ASUS FIRMWARE
WW_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
US_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
kernel_11_4_1_17.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
CWM Recovery V6.0.4.8. for 4.3*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery recovery.img [where recovery.img is the name of the file image you downloaded]
CUSTOM ROM'S
By Sbdags based on stock with quite some enhancements: HERE
CyanogenMod 11 Preview Proxy thread: HERE
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/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,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION​
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!​
Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/show....php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/show....php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/show....php?t=2621028
Delete
Root and firmware.
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.
tf701mega said:
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.
Click to expand...
Click to collapse
If you want to root then use my guide as it is for 10.26.1.18. Downgrading to .47 and back up again is really painful.
download problem
Hi OP,
Download links are down...
please fix theme?
henengel said:
Hi OP,
Download links are down...
please fix theme?
Click to expand...
Click to collapse
anyone know where I can get the files? links are broken
kuthedude said:
anyone know where I can get the files? links are broken
Click to expand...
Click to collapse
Which files are you looking for?
Most of the files are available from ASUS's website and the ROM and recovery links are old and newer ones are available in the Development section of this form.
Sorry for the inconvenience.
Asked in the OP to PM me if there is new stuff or if somethings doesn't work but received nothing.
Files will be back end of the day with latest firmware and kernel source.
Hi, I am getting my tablet soon, and I am assuming the tablet will be on 4.3 or earlier by the time I get it.
What firmware/kernal/boot loader is the best setup to get me onto the latest 4.3 OS. I only am wanting this because I want to avoid the 4.4.2 battery drain issues (since I am most likely going to flash an AOSP ROM after I get this tablet).
Also, how would I be able to properly update the tablet with the firmware/kernal/boot loader? Thanks for the help!
Sent from my SCH-I545 using Tapatalk 2
Hi, I tried pushing my firmware file to root, but it wouldn't work. I would use root explorer and it would just freeze and restart. anyone know why this would happen? Im trying to update to 4.3 without getting into 4.4.2. please help if you can
You have to unpack the file, inside this is another zip file. Put it then in sd root this should work as far as i know
Gesendet von meinem LG-D855 mit Tapatalk
Hi
There is a new firmware version 11.4.1.27.
Is it posible to add this version to the post?

[RECOVERY][Experimental][OS2SD/Internal][f2fs]TWRP2.8.0.0-multi

TWRP 2.7.1.0 multi-mode recovery. 2.7.1.0 v3 was the first release for p500, (thanks to @HardLight for advising, testing, and posting it. And for making a p500 OS2SD ROM to justify it.)
v1 and up are for thunderc (Optimus V/S), there's a separate thread over there in the appropriate forum.
Now with f2fs! Thanks @HardLight
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
This has a special partitioner to set up your card for OS2SD. In OS2SD mode, go to Advanced then Partition. Set your sizes, it isn't aware yet of the whole card size (yet) so it'll just tell you if you go over and refuse to format it.
Whatever is left after your system/swap/data is your /sdcard size.
If it's in Internal mode the partitioner does sd-ext and swap instead. same deal, the leftover space is your /sdcard size.
Under the Wipe -> advanced menu, you can now select either system or data and press the 'repair or change filesystem' bar at the bottom, select change filesystem, select f2fs.
TLS enabled, system/data MTD swap on internal mode to match post-7/12/2014 androidarmv6 builds. Won't flash older ROMS or ones without the MTD swap correctly.
I am working on making it compatible with older builds too... but not yet. You may have to use a new update-binary to flash older zips. Or grab the older one from this zip file.
download, shared folder here:
Experimental, may be glitchy! Enjoy!
source on github
reserved
reserved against whatever need
reserved
I suspect I'll need more than one extra post to cover important stuff that won't fit in the OP.
On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).
bigsupersquid said:
TWRP 2.7.1.0 multi-mode recovery. v4. ...
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
Experimental, may be glitchy! Enjoy!
source on github
Click to expand...
Click to collapse
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...
Dovidhalevi said:
On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).
Click to expand...
Click to collapse
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
xdema said:
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...
Click to expand...
Click to collapse
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
//edit: proper syntax:
run_program("/sbin/busybox","mount","/system");
instead of trying to call out the filesystem type.
bigsupersquid said:
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
instead of trying to call out the filesystem type.
Click to expand...
Click to collapse
i'll check the updater script, thanks for the pureperformance thinks, i discover a another method to speed up the p500 :fingers-crossed:
bump
f2fs enabled for OS2SD.
uses updater script like so:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p4", "/data");
to use f2fs /data go into Wipe menu, advanced, select data checkbox, press 'repair or change filesystem' bar, change filesystem, f2fs. accept.
you only have to do that once to change from the default ext4 partition type.
it handles /system f2fs as well.
mount("f2fs", "EMMC", "/dev/block/mmcblk0p2", "/system");
change the filesystem the same way as data.
new 3.0.101 kernel but I noticed no differences in recovery except the working f2fs. Thanks @HardLight.
for now, attached .img for you who really have to experiment. I haven't tested this one very much on thunderg, just thunderc. basics tested on thunderg.
flashable zip added to shared folder linked in OP.
there's a little something extra in the shared folder...
I'm also uploading ROMs for the adventurous.
f2fs-system and f2fs-data os2sd builds if you're brave enough to try them. change both system and data to f2fs in recovery before flashing the rom unless you've already done that with an earlier version.
I don't have cell service to test but it's basically an androidarmv6 build plus 3.0.101 kernel and f2fs os2sd. everything else looks like it works to me.
I added Email, Apollo, Speech Recorder (which tunes up voice search I think), emojii in messaging and aosp keyboard, and extra wallpapers. Including Grass live wallpaper (which does actually work on armv6, it just looks for some network function and errors out ... I patched it,) and it reverts to building libcamera. Plus hackers keyboard because I like arrow and tab in terminal. No voice search in hackers keyboard though.
...
bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.
bigsupersquid said:
bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.
Click to expand...
Click to collapse
i'm testing your's 0509
in this you made the on boot fix?
##fix "add_tid_to_cgroup failed to write" errors
chmod 0660 /dev/cpuctl
# allow reading kernel command line
chmod 0644 /proc/cmdline
Click to expand...
Click to collapse
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal
xdema said:
i'm testing your's 0509
in this you made the on boot fix?
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal
Click to expand...
Click to collapse
looks normal to me, ext4 uses "only" about 16MB after format but f2fs uses a lot more.
minitool will only work right if your kernel supports f2fs and I doubt m$ware does right now.
and the fix din't get migrated from the overrides in thunderc to p500 yet, sorry, was a 'for fun' build to share after a recent repo sync.
this one probably has a built libcamera instead of the froyo as well. (reversion)
reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.
bigsupersquid said:
reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.
Click to expand...
Click to collapse
My 01 does have fastboot e.e
andrea210701 said:
My 01 does have fastboot e.e
Click to expand...
Click to collapse
I meant that I can use. HardLight pointed me to the method to enable it... if I hadn't completely fried my firmware. no backlight even, much less lg logo or emergency mode.
eventually I'll find another p500 for development (I can't use gsm phone on my service) but the going rate on ebay is $50 and I can't justify that for a hobby.
unfortunately it's too tweaky and time consuming for me to remotely develop by having someone else debug, so any more p500 stuff will be untested and slightly sketchy because of that.
Project [F2FS] [OS2SD]
[F2FS] [OS2SD] it can work with any other rom? Thanks.
cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...
Any PlayStore said:
cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...
Click to expand...
Click to collapse
clockwork mod v 6.0.5.3 for pre-tls roms (before androidarmv6 swapped the system and data Mount points in the kernel) used for kitkat roms around July 2014 or earlier or other 4.4 roms without the MTD partition swap

Question Looks like I screwed up more that I think I screwed up......

So, I recently unlocked the boot loader of my phone, Redmi Note 11 (spes). The thing is due to water damage I had to change my Screen and certain components. Obviously to stay cheap, I installed a Third party Screen and Didn't care much. So today when I tried installing PixelExperience and other Cutom ROMs, Things weren't working like they should. It turns out, the custom rom kernel didn't have support to third party replacement screens. So I tried to root my MIUI Install and Backup certain files, like Kernel and other Stuff, so that when I install Custom ROMs, I can replace the new kernel with my backup kernel. While doing that I accidentally flashed a wrong image to the persist partition. I tried decompiling the official ROM, but didn't find any persist.img file, like literally it screwed up the whole Partition Table so bad, I can't even revert to orignal State. Here are the log files, which I think might help.
Custom ROMs use stock kernel (found in MIUI) due to lack of source code. I don't think the problems were kernel related, correct me if I'm wrong though
hadrbass89 said:
AFAIK Custom ROMs use stock kernel (found in MIUI) due to lack of source code. I don't think the problems were kernel related, correct me if I'm wrong though
Click to expand...
Click to collapse
well, the problem was kernel related indeed, because after i locked my phone and pressed the power to wake it, but touch input was acting like mouse hover. Also, I don't really care about this issue anymore, I just want my phone restored first. I want is, Someome upload their TWRP Backup here, so that I restore it to the Original Condition.
Can you use a fastboot rom ( MIUI )?
Also, if there is a way to run this command on a rooted terminal, like after booting a custom recovery:
Code:
ls -l /dev/block/by-name | grep persist
It should show you which block device has the persist partition. On mine it's sda2, I think.
Vagelis1608 said:
Can you use a fastboot rom ( MIUI )?
Also, if there is a way to run this command on a rooted terminal, like after booting a custom recovery:
Code:
ls -l /dev/block/by-name | grep persist
It should show you which block device has the persist partition. On mine it's sda2, I think.
Click to expand...
Click to collapse
I managed to find the persist.img, But still have other errors to deal with, like:
Failed to mount '/system_ext' (Block device required)
and other Messages as well like this for product vendor and system_root!
You know these fall under the super partition. And I am totally unable to fix these errors, even though I have the corresponding images from the miui payload.bin. But I will surely try your method to try to fix it. Thanks
arnv2004 said:
I managed to find the persist.img, But still have other errors to deal with, like:
Failed to mount '/system_ext' (Block device required)
and other Messages as well like this for product vendor and system_root!
You know these fall under the super partition. And I am totally unable to fix these errors, even though I have the corresponding images from the miui payload.bin. But I will surely try your method to try to fix it. Thanks
Click to expand...
Click to collapse
That command is to find the partition, not fix it.
You should try to flash a fastboot rom.
Better unlock the bootloader if you locked it.
Okay, So now I have system system_ext vendor product images with with. Now since, these fall under the super partition, how can I flash them separately?
arnv2004 said:
Okay, So now I have system system_ext vendor product images with with. Now since, these fall under the super partition, how can I flash them separately?
Click to expand...
Click to collapse
Find and flash the appropriate fastboot rom
Done! Flashed MIUI Back using the help of Telegram Community
Now its back to normal!

Categories

Resources