Database Info

Null

Null

Null

Null

You can also do this in your old recovery, just make sure to download this file and then push it to /bin or wherever that it is accessable.
Download the above flash_image file also if it is not included in your rom.
It doesn't work on htc dream.. just tried it out

Thanks haha, I was going to upload the binary but it was already 2AM
When I get home, I'll try to add Dream support if you'd like to test it
Sent from my HTC PH39100 using Tapatalk

YAY!!!! <(^_^<) <(^_^)> (>^_^)> why do I do this....cause im bored xD

xillius200 said:
YAY!!!! <(^_^<) <(^_^)> (>^_^)> why do I do this....cause im bored xD
Click to expand...
Click to collapse
Hahaha
Sent from my HTC PH39100 using Tapatalk

You can't just flash from fastboot?
Anyways I'll try this out soon as I find the time.
Sounds awesome

frankdrey said:
You can't just flash from fastboot?
Anyways I'll try this out soon as I find the time.
Sounds awesome
Click to expand...
Click to collapse
If you have an Engineering HBOOT then yes, you can. Unfortunately 1.33.0013d doesn't allow it.

Infinimint said:
If you have an Engineering HBOOT then yes, you can. Unfortunately 1.33.0013d doesn't allow it.
Click to expand...
Click to collapse
Ah well I thought so
But you should include that in the instructions
So that people still with an engineering spl won't waste time

i did flashed it but it failed to boot into the new recovery i flashed it via adb had to re flash amon ra recovery

mahroze said:
i did flashed it but it failed to boot into the new recovery i flashed it via adb had to re flash amon ra recovery
Click to expand...
Click to collapse
I have the same problem

Only works for 32B Sapphire for some strange reason. I'm sure xillius and Infinimint are working on it and will post it soon

e334 said:
Only works for 32B Sapphire for some strange reason. I'm sure xillius and Infinimint are working on it and will post it soon
Click to expand...
Click to collapse
Prob you just swap in my ezgb ebi0 kernel kernel for full dream/sapphire 32b support and not whatever was pulled by the cyanogen build tree.
Either by updating the build or just unpacking/repacking recovery.
(yes you want recovery with ebi0 even if your rom is 2708+, we will live without the extra ram in recovery.. and its safer ie. prevents bricks that would otherwise happen on some operations.)
That or use an older cm kernel.
Regardless recovery.img has a kernel included.. best to link to the source code per gpl.. may also want to link to busy box source. (The one in cm's tree is used for cwm)
Biggest question is there any issue with the yes no script of mine used in some install scripts with the new cwm.. since there have been complaints on other devices of not being able to get it to work.
Sent from my Galaxy Nexus using Tapatalk

ezterry said:
Prob you just swap in my ezgb ebi0 kernel kernel for full dream/sapphire 32b support and not whatever was pulled by the cyanogen build tree.
Either by updating the build or just unpacking/repacking recovery.
(yes you want recovery with ebi0 even if your rom is 2708+, we will live without the extra ram in recovery.. and its safer ie. prevents bricks that would otherwise happen on some operations.)
That or use an older cm kernel.
Regardless recovery.img has a kernel included.. best to link to the source code per gpl.. may also want to link to busy box source. (The one in cm's tree is used for cwm)
Biggest question is there any issue with the yes no script of mine used in some install scripts with the new cwm.. since there have been complaints on other devices of not being able to get it to work.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
When I get home, I'll compile it using your kernel
As for yesno, I'll take a look as well.
Sent from my HTC Flyer P512 using Tapatalk

Thanks. Ported to 32A.
Using Amon-RA Sapphire 1.7.0G kernel
Thanks
Radio-3.22.26.17 tested okay

xaueious said:
Thanks. Ported to 32A.
Using Amon-RA Sapphire 1.7.0G kernel
Thanks
Radio-3.22.26.17 tested okay
Click to expand...
Click to collapse
Nice , I'm going to try to support all the D/S phones. Until then, do you mind if I add it to the OP?
Sent from my HTC PH39100 using Tapatalk

something confuse me now.i once tried to flash this recovery with my dream,obviously it failed at last.but the strange thing was after that i cannot flash any recovery any more.it showed:
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/170.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
why,sorry for that.....

WongHokZau said:
something confuse me now.i once tried to flash this recovery with my dream,obviously it failed at last.but the strange thing was after that i cannot flash any recovery any more.it showed:
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/170.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
why,sorry for that.....
Click to expand...
Click to collapse
I had that strange error too. Did you have custom MTD when you flash the file?

e334 said:
I had that strange error too. Did you have custom MTD when you flash the file?
Click to expand...
Click to collapse
I don't see what custom MTD has to do with it
it says out of memory
could it be that the ram is full?
do you have adb?
try this
adb shell
Code:
free
stop zygote
free
flash_image recovery /sdcard/170.img
start zygote

[a700]WARNING!DON'T use factory rest in the system settings!

after using factory rest in the system settings menu,I found my device not starting.then I went into the cwm,i found that i could not mount /data or do anything else to the data folder.it looks like the /data folder has gone...
then i went to the fastboot menu,and did the following commands:
E:\A701\CWM-recovery_A70x>fastboot flash data recovery.img
sending 'data' (6144 KB)...
OKAY [ 2.169s]
writing 'data'...
FAILED (remote: (00030003))
finished. total time: 3.261s
E:\A701\CWM-recovery_A70x>fastboot flash userdata recovery.img
sending 'userdata' (6144 KB)...
OKAY [ 2.036s]
writing 'userdata'...
OKAY [ 1.712s]
finished. total time: 4.356s
E:\A701\CWM-recovery_A70x>fastboot flash system recovery.img
sending system' (6144 KB)...
OKAY [ 2.535s]
writing 'system'...
OKAY [ 1.902s]
finished. total time: 4.437s
then i went to the cwm menu,the /system folder could not be mounting,either.
I wonder if there are raw image,just like system.img or data img could do solve the problem.I reflashed the bootloader but it's still not mailfunctioning.do i have to flash the pit partition file or sth else?
and i see this in the nexus 7 forum:
recovery.fstab
/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
fstab.grouper
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/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
at here:http://forum.xda-developers.com/showthread.php?t=1742416
and I don't now how and where to flash this....
at least,we know one thing....do not use factory rest...

goddamn cwm
lsnc said:
after using factory rest in the system settings menu,I found my device not starting.then I went into the cwm,i found that i could not mount /data or do anything else to the data folder.it looks like the /data folder has gone...
then i went to the fastboot menu,and did the following commands:
E:\A701\CWM-recovery_A70x>fastboot flash data recovery.img
sending 'data' (6144 KB)...
OKAY [ 2.169s]
writing 'data'...
FAILED (remote: (00030003))
finished. total time: 3.261s
E:\A701\CWM-recovery_A70x>fastboot flash userdata recovery.img
sending 'userdata' (6144 KB)...
OKAY [ 2.036s]
writing 'userdata'...
OKAY [ 1.712s]
finished. total time: 4.356s
E:\A701\CWM-recovery_A70x>fastboot flash system recovery.img
sending system' (6144 KB)...
OKAY [ 2.535s]
writing 'system'...
OKAY [ 1.902s]
finished. total time: 4.437s
then i went to the cwm menu,the /system folder could not be mounting,either.
I wonder if there are raw image,just like system.img or data img could do solve the problem.I reflashed the bootloader but it's still not mailfunctioning.do i have to flash the pit partition file or sth else?
and i see this in the nexus 7 forum:
recovery.fstab
/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
fstab.grouper
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/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
at here:http://forum.xda-developers.com/showthread.php?t=1742416
and I don't now how and where to flash this....
at least,we know one thing....do not use factory rest...
Click to expand...
Click to collapse
Now I know,it's because of the goddamn CWM in the development ,that's a dangerous thing and not perfect at all,could do harm to our devices.

lsnc said:
Now I know,it's because of the *^*%*(% CWM in the development ,that's a dangerous thing and not perfect at all,could do harm to our devices.
Click to expand...
Click to collapse
Yes, this is the price we pay when we mess with things. Although, if the Dev "doesn't" own the specific device, it would be better to at least have "1" laboratory rat to test the recovery before putting it public.
Would have avoided a lot of bricked tabs.
Oh well, Acer Service Center.....
Hopefully, I can get with one of the recovery devs from the 500 forums, and maybe (if and when I get my tab back) we can work on a functioning recovery. Would also be nice to have a better bootloader with full fastboot from the start.
MD

been a laboratory rat...
Moscow Desire said:
Yes, this is the price we pay when we mess with things. Although, if the Dev "doesn't" own the specific device, it would be better to at least have "1" laboratory rat to test the recovery before putting it public.
Would have avoided a lot of bricked tabs.
Oh well, Acer Service Center.....
Hopefully, I can get with one of the recovery devs from the 500 forums, and maybe (if and when I get my tab back) we can work on a functioning recovery. Would also be nice to have a better bootloader with full fastboot from the start.
MD
Click to expand...
Click to collapse
but there is a proble that i'm in china,the device is not for sale publicly...seems,i can only wait for the nvflash or wait for the openning sales in china...

Moscow Desire said:
Yes, this is the price we pay when we mess with things. Although, if the Dev "doesn't" own the specific device, it would be better to at least have "1" laboratory rat to test the recovery before putting it public.
Would have avoided a lot of bricked tabs.
Oh well, Acer Service Center.....
Hopefully, I can get with one of the recovery devs from the 500 forums, and maybe (if and when I get my tab back) we can work on a functioning recovery. Would also be nice to have a better bootloader with full fastboot from the start.
MD
Click to expand...
Click to collapse
If you find a stock recovery for the A700, let me know! I flashed the CWMR on my A700, but I haven't used CWMR on it (thankfully), and I want to get the stock recovery back to make sure no issues pop up. Thanks in advance!

1
californiarailroader said:
If you find a stock recovery for the A700, let me know! I flashed the CWMR on my A700, but I haven't used CWMR on it (thankfully), and I want to get the stock recovery back to make sure no issues pop up. Thanks in advance!
Click to expand...
Click to collapse
edit this file in the update package updater-script
delete the first and the third comand.then bring it back to replace the orginal file of the update package.
then reflash.
and everything goes back.u need to reroot.

Can those with A700 units, especially ones that partially bricked, run the following from a command line?
Code:
cat /sys/class/block/mmcblk0/device/name
And then
Code:
cat /sys/class/block/mmcblk0/device/cid
Or run Chainfire's "Got Brickbug" app from the Galaxy Note forums?
http://forum.xda-developers.com/showthread.php?t=1693704
These symptoms sound a lot like "Samsung Superbrick". While this isn't a Samsung device, Samsung ships their flash chips to many companies other than Samsung. For example, about half of Kindle Fires manufactured have defective M8G2FA chips.

Hi
Here are the results
Code:
[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
MBG8FA
[email protected]:/ $ cat /sys/class/block/mmcblk0/device/cid
1501004d424738464121bd1b68e9ae00
Gotbrickbug says the chip is unknonwn.
Sent from my A700 using xda premium

laloutre said:
Hi
Here are the results
Code:
[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
MBG8FA
[email protected]:/ $ cat /sys/class/block/mmcblk0/device/cid
1501004d424738464121bd1b68e9ae00
Gotbrickbug says the chip is unknonwn.
Sent from my A700 using xda premium
Click to expand...
Click to collapse
That is an unknown chip, HOWEVER it is a Samsung chip. Is your device a 32GB by any chance?
M8G2FA = 8GB
MAG4FA = 16GB
MBG8FA = ???
fwrev is 0x21, which is also unknown - but most likely all A700 units have the same fwrev. Not all may have Samsung chips.
Bad news: Anyone who suffered damage is hosed. This damage is unrepairable.
Good news: It is possible to protect against damage. If recovery is built with BOARD_SUPPRESS_EMMC_WIPE it will be safe, although you need to be careful about update-zips in firmware releases that can still do damage even with a safe recovery.
It is also possible to render a kernel safe if you have kernel source code by removing MMC_CAP_ERASE from the relevant driver in drivers/mmc/host/ - For example on Samsung Exynos based phones it is mshci.c, on Qualcomm-based ones it is msm_sdcc.c - not sure about these Acers.

Yep it is a 32G
I forgot to mention i am not affected as I didn't wipe or flash anything after installing CWM.
I guess i'm gonna stick on this stock rom for a while.
By the way thanks for looking at this issues I've been reading the great work you did for the Galaxy Note !
Sent from my A700 using xda premium

Thanks for this important info. I also have 32G in my tab. It is running on stock 1.055 (EMEA_DE), has CWM 6.0.1.0 from pawitp and is not rooted yet. I also didn't mess around so my tab is not bricked. I followed (and read ) your link to Chainfire's Brickbug (didn't install it) and also followed his link about the backround and used the cat-command from there (without su). Got this result
Code:
[email protected]:/sys/class/block/mmcblk0/device $ cat name hwrev fwrev manfid oemi
d date type serial cid
MBG8FA
0x0
0x0
0x000015
0x0100
10/2011
MMC
0x180690d8
1501004d424738464121180690d8ae00
As you can see, same chip but different cid and fwrev. My A700 was manufactured in June 2012 (may be of interest).

lsnc used the older ZeroNull CWM for erasing which is why he had the issues with factory resets, the new CWM 6.0.1.0 doesn't have these problems !

The next builds of CM and recovery will no longer send the problematic erase command to the mmc and should be more safe.

pawitp said:
The next builds of CM and recovery will no longer send the problematic erase command to the mmc and should be more safe.
Click to expand...
Click to collapse
hi, can u plz help build the new CWM for A510, there're also many bricked A510 need to rescue:crying:

jokerzlh said:
hi, can u plz help build the new CWM for A510, there're also many bricked A510 need to rescue:crying:
Click to expand...
Click to collapse
Unfortunately, it's intended to prevent new devices from being bricked, not rescue old devices. And I want to focus on the devices that I do have, some 510 developer can take the kernel/device source I've posted and compile a version for A510.

pawitp said:
Unfortunately, it's intended to prevent new devices from being bricked, not rescue old devices. And I want to focus on the devices that I do have, some 510 developer can take the kernel/device source I've posted and compile a version for A510.
Click to expand...
Click to collapse
I have no way, so i install the new A700 CWM 6.01.1, luckily that i can enter it, but the screen become very abnormal.
I chose to install update.zip, then i saw a abnormal picture and no progress bar. I wait for 10 minutes but it only hang there.
Then i chose to factory reset, 'cos i can't c any progress text, so i didn't know what happened, but it back to munue after a while.
If the factory reset success, my bricked A510 maybe work! ( the 5.8.5 CWM kill my tab when i use the factory reset )
so i reboot my device but it also hang in 'iconia tab' Logo :crying:
thx anyway!

I'd like to note that the first time I did a factory reset from CWM update 1, my Wi-Fi went all wonky. It would scan fine, then would act as if there was little to no signal upon trying to connect. I ended up flashing to EMEA_CUS1 to get everything going again.
Just wanted to let people know.
Sent from my A700 using XDA Premium HD app

jokerzlh said:
I have no way, so i install the new A700 CWM 6.01.1, luckily that i can enter it, but the screen become very abnormal.
I chose to install update.zip, then i saw a abnormal picture and no progress bar. I wait for 10 minutes but it only hang there.
Then i chose to factory reset, 'cos i can't c any progress text, so i didn't know what happened, but it back to munue after a while.
If the factory reset success, my bricked A510 maybe work! ( the 5.8.5 CWM kill my tab when i use the factory reset )
so i reboot my device but it also hang in 'iconia tab' Logo :crying:
thx anyway!
Click to expand...
Click to collapse
never a good idea to flash a recovery from a different device...

md5 missing

trying to install http://forum.xda-developers.com/showthread.php?t=2181399 and it says my md5 is missing so there for i cant install the rom... cant figure it out and need to have my phone back.. also backup is failing as well

phatryan69 said:
trying to install http://forum.xda-developers.com/showthread.php?t=2181399 and it says my md5 is missing so there for i cant install the rom... cant figure it out and need to have my phone back.. also backup is failing as well
Click to expand...
Click to collapse
leave both those options unchecked when flashing. You check the MD5 on your PC using an md5 checking application or you can do it with an md5 check app on your phone, but not during flash.

exad said:
leave both those options unchecked when flashing. You check the MD5 on your PC using an md5 checking application or you can do it with an md5 check app on your phone, but not during flash.
Click to expand...
Click to collapse
but if my md5 is missing even b4 i flash what must i do then? cause i thought md5's were added in the file itself.

Read what Exad said and try again.
Turn off md5 checking in recovery and do it manually yourself before flashing.
Sent from my Evita

had no idea htc phones were such a PITA to install and such. long time samsung guy... i thought i did everything right but said failed when i tried to install...

Not really a pain in the ass, I've never had an issue.
So you turned off md5 checking and it still failed?
Did it give an error code?
Which recovery are you using?
Sent from my Evita
---------- Post added at 03:46 AM ---------- Previous post was at 03:22 AM ----------
PS. an md5 is not "added to a file", nor is it "a part of a file". An md5 is merely a hexadecimal readout of the contents of that file.
Here's how it works: A file is created, in our case it is a zip file. The creator or publisher of that file uses an md5 generator to generate the md5sum, which as I said before, is just a numerical readout (like a fingerprint) of the contents of that file. Now the end user has a tool to make sure that the file hasn't been compromised during a download or transfer. Using an md5 checker is a simple way to verify that the file is uncompromised. Input the md5 given by the publisher into an md5 checking app, then the app calculates the md5 of the file you've downloaded, if they match you know the file integrity is good.
Sent from my Evita

I don't find it to be a PITA either...
I mean, if you're rooting.. a lot of this stuff should be familiar or already make sense.

Idk just seems like I'm either missing a step or not doing something right.. I've followed everything I can as far as loading ROMs extracting boot.IMG and flashing in fast boot then booting into recov then flashing like u normally would and everything then pops up and says failed missing md5.. I can get root and everything fine but the minute I get to flashing a ROM I have a problem.. Maybe I needs step back and relook over what I'm doin
Using twrp btw
Sent from my SGH-I927 using xda app-developers app

So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using?
Sent from my Evita

what ver. of twrp?

timmaaa said:
So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using
i have everything unchecked that could be unchecked yes... and 2.5.0.0
Click to expand...
Click to collapse

phatryan69 said:
timmaaa said:
So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using
i have everything unchecked that could be unchecked yes... and 2.5.0.0
Click to expand...
Click to collapse
I would recommend upgrading TWRP to 2.6.0.0. 2.5 had some issues with this phone (mostly with Sense ROMs in my experience). In TWRP > Settings make sure "Zip file signature verification" is unchecked. I think that sets the overall default. Otherwise I think you have to uncheck it each time on the screen where you "Swipe to Confirm Flash".
Click to expand...
Click to collapse

phatryan69 said:
timmaaa said:
So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using
i have everything unchecked that could be unchecked yes... and 2.5.0.0
Click to expand...
Click to collapse
2.5 has issues.
flash 2.6
then fastboot erase cache
then do a factory reset in twrp
Then try again.
Click to expand...
Click to collapse

having alot of problems with my computer nor recognizing my phone as well it seems... just uninstalled and reinstalled all drivers as well but only in bootloader when it says that trying to send commands to the phone.
installing 2.6

idk what i did but i got my phone on that rom and running...is there a list of fastboot commands somewhere?>

Not that I know of. Some that should work don't work also so... Maybe ill write one up later.
Sent from my HTC One X using xda app-developers app

phatryan69 said:
idk what i did but i got my phone on that rom and running...is there a list of fastboot commands somewhere?>
Click to expand...
Click to collapse
exad said:
Not that I know of. Some that should work don't work also so... Maybe ill write one up later.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just running "fastboot" will give you a list of sorts, but I don't know that most of those should ever be run by most of us. A list of the useful ones and what they do would be awesome, exad!
Code:
C:\Users\username>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable

Since moving to cwm i haven't had an issue. I had tons of issues with twrp after 2.3.x.x i moved when cwm got official and haven't changed back. We also latest cwm builds from mdmower i believe the alias is, ill post a link when i get home.

DvineLord said:
Since moving to cwm i haven't had an issue. I had tons of issues with twrp after 2.3.x.x i moved when cwm got official and haven't changed back. We also latest cwm builds from mdmower i believe the alias is, ill post a link when i get home.
Click to expand...
Click to collapse
I've always had cwm might have to try that for a while
Sent from my HTC One X using xda app-developers app

Since TWRP 2.6 was released, I would have a hard time switching. They even made Wiping quicker and easier. I'd take a look at it if I was you. I've seen an issue with someone going from CM to TWRP and no longer being able to mount/access there SD card in TWRP. Dunno who's fault that is but they had to flash over an older non touch CWM and then fastboot erase cache and then flash TWRP. What a pain.

Internal memory corrupted ? unable to mount /data /cache

Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done​
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"​
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8​
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.​
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate

you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes

So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)

ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.

hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!

So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..

ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done​
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"​
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8​
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.​
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.

When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?

little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB

ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.

Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo

ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?

Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue

ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.

Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:

ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.

ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?

Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch

ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.

little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !

Restore fried partitions - Fastboot flash stock ROM via MiFlash takes forever

Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
EDIT: Finally, I managed to restore my phone. To save you from reading the whole thread, which is full with creative ideas to unbrick the phone you can jump to the last post. There I described my final solution and ruled out, what probably my mistake with the MiFlash Tool was.

Muenzi said:
Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
Click to expand...
Click to collapse
Did you do anything before you noticed your partitions are fried?

jjgvv said:
Did you do anything before you noticed your partitions are fried?
Click to expand...
Click to collapse
Yes I installed OrangeFox as a recovery. From there on, everything get messed up.
If nescessary to know, the BL is unlocked of course. I backuped all data from the phone. So I do not need a safe way to get them back. I am happy when the phone can operate a reliable OS again.

https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.

jjgvv said:
https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.
Click to expand...
Click to collapse
Thank you for your help. Can you tell me please to which partition this has to be flashed? And what will be the outout I can send you (probably a log file?).
So lets say commands instructions like
fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
would be really cool to avoid confussion and mistakes.
Anyway, it is 3 am here and I have to get up in around 4 hours. So I will leave and take a nap. Maybe I can ask you to wait for my reply? And again, thank you so much for your help.
Best regards
Stephan

yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img

Muenzi said:
And what will be the outout I can send you (probably a log file?).
Click to expand...
Click to collapse
I need What happens in the cmd window like:
Code:
Desktop-XCRXAJB > C:\platform tools >
fastboot flash system system-roar-arm64-aonly-vanilla.img
Reported max download size = 2580192068 bytes （ 2.7 GB）
sending 'system' （2070713691 bytes）
OKAY （1576 secs）
writing 'system' （2070713691 bytes）
FAILED （remote : failed to mount 'system' : system partition layout is 'null'）

jjgvv said:
yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
Thats the outout:
Code:
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/3 (786328 KB)...
OKAY [ 21.029s]
writing 'system' 1/3...
FAILED (remote: Partition not found)
finished. total time: 21.031s
So, I have to go now. See you in a couple of hours.

adb shell
parted /dev/block/mmcblk0
print

see you soon

jjgvv said:
adb shell
parted /dev/block/mmcblk0
print
Click to expand...
Click to collapse
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.

Muenzi said:
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.
Click to expand...
Click to collapse
recovery

jjgvv said:
recovery
Click to expand...
Click to collapse
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.

Muenzi said:
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.
Click to expand...
Click to collapse
oh so probably Orangefox fried your other partitions

jjgvv said:
oh so probably Orangefox fried your other partitions
Click to expand...
Click to collapse
What happens when flash TWRP

jjgvv said:
What happens when flash TWRP
Click to expand...
Click to collapse
I already did. The problem persists. To clarify, all the last steps were already performed with TWRP as recovery. But the problem occurred first under TWRP.
Is there any chance to recreate the partition table?

maybe but complicated

Hi you may try boot from sd card
[HOW TO] BOOT FROM SD CARD [SUCCESSFULLY] on QMobile Z8 with BRICKED/DEAD eMMC
I'm a mechanical engineer, not an IT guy. I can fix machines, perhaps, but not bricked phones. So try anything at your own extreme risk. This is NOT a step by step guide. DEVICE: QMobile Z8, same as Wikio Ridge 4G, (MSM8916). Running Android...
forum.xda-developers.com

jjgvv said:
maybe but complicated
Click to expand...
Click to collapse
Okay if you have any idea, let me know.

or this https://forum.xda-developers.com/t/...dor-partition-for-pt-gsi-rom-mi3-mi4.3878995/
this is create vendor but should be possible to create all