Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
Page 1 of 2    1 2
 
Post Reply+
Tip us?
 
lsnc 		Old
6th July 2012, 02:50 AM
(Last edited by lsnc; 6th July 2012 at 04:53 AM.)
#1  
Junior Member - OP
Thanks Meter 2
Posts: 16
Join Date: Aug 2011
Default [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/show....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...
 
REPLY
The Following User Says Thank You to lsnc For This Useful Post: [ Click to Expand ]
 
lsnc 		Old
8th July 2012, 04:09 AM
#2  
Junior Member - OP
Thanks Meter 2
Posts: 16
Join Date: Aug 2011
Default goddamn cwm
Quote:
Originally Posted by lsnc View Post
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/show....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...
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.
 
REPLY
 
Moscow Desire 		Old
8th July 2012, 09:21 AM
#3  
Moscow Desire's Avatar
Forum Moderator
Thanks Meter 2208
Posts: 4,075
Join Date: Mar 2011
Location: Somewhere in a Deep Cave on the Troll Kings Throne

 
DONATE TO ME
Quote:
Originally Posted by lsnc View Post
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.
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
"Though I walk daily surrounded by trolls, I fear them not. For I am the Troll King."

Killin 'dem Trolls since 2011

Acer Iconia A701 * Acer Iconia A501 * HTC Desire S * HTC Desire
 
REPLY
 
lsnc 		Old
8th July 2012, 11:25 AM
#4  
Junior Member - OP
Thanks Meter 2
Posts: 16
Join Date: Aug 2011
Default been a laboratory rat...
Quote:
Originally Posted by Moscow Desire View Post
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
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...
 
REPLY
 
californiarailroader 		Old
8th July 2012, 02:48 PM
#5  
californiarailroader's Avatar
Senior Member
Thanks Meter 278
Posts: 3,206
Join Date: Mar 2006
Location: Redwood Valley, NorCal (97-) /Pocatello, ID (90-97)/ Covina, SoCal (71-90)
Quote:
Originally Posted by Moscow Desire View Post
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
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!

http://www.nwprr.net
http://www.sonomamarintrain.org
http://www.cahighspeedrail.ca.gov
http://www.xpresswest.com
http://www.freightrailworks.org
http://www.amtrakcalifornia.com
http://www.amtrak.com
http://www.bnsf.com
http://www.up.com
http://www.metrolinktrains.com
http://www.pioneertrain.org/
http://www.sbb.ch
http://www.isu.edu
Current Devices-HTC One (AT&T),Nokia Lumia 920 (AT&T)
 
REPLY
 
lsnc 		Old
8th July 2012, 03:34 PM
#6  
Junior Member - OP
Thanks Meter 2
Posts: 16
Join Date: Aug 2011
Default 1
Quote:
Originally Posted by californiarailroader View Post
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!
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.
 
REPLY
 
Entropy512 		Old
4th August 2012, 06:36 PM
#7  
Elite Recognized Developer
Thanks Meter 20770
Posts: 11,472
Join Date: Aug 2007
Location: Owego, NY

 
DONATE TO ME
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/show....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.
*so much sig updating needed*

My Github profile - Some Android stuff, some AVR stuff

An excellent post on "noobs vs. developers"

A few opinions on kernel development "good practices"

Note: I have chosen not to use XDA's "friends" feature - I will reject all incoming "friend" requests.

Code:
<MikeyMike01> Smali is a spawn of hell
<shoman94> ^^^ +!
Code:
<Entropy512> gotta be careful not to step on each other's work.  :)
<Bumble-Bee> thats true
<jerdog> compeete for donations
 
REPLY
The Following User Says Thank You to Entropy512 For This Useful Post: [ Click to Expand ]
 
laloutre 		Old
4th August 2012, 08:33 PM
#8  
Senior Member
Thanks Meter 35
Posts: 163
Join Date: Mar 2012
Hi
Here are the results
Code:
app_123@android:/ $ cat /sys/class/block/mmcblk0/device/name
MBG8FA
app_123@android:/ $ cat /sys/class/block/mmcblk0/device/cid
1501004d424738464121bd1b68e9ae00
Gotbrickbug says the chip is unknonwn.


Sent from my A700 using xda premium
Current Devices : Galaxy Note2 Carbon ROM, Nexus 7 travelling from ROM to ROM
 
REPLY
 
Entropy512 		Old
4th August 2012, 08:56 PM
#9  
Elite Recognized Developer
Thanks Meter 20770
Posts: 11,472
Join Date: Aug 2007
Location: Owego, NY

 
DONATE TO ME
Quote:
Originally Posted by laloutre View Post
Hi
Here are the results
Code:
app_123@android:/ $ cat /sys/class/block/mmcblk0/device/name
MBG8FA
app_123@android:/ $ cat /sys/class/block/mmcblk0/device/cid
1501004d424738464121bd1b68e9ae00
Gotbrickbug says the chip is unknonwn.


Sent from my A700 using xda premium
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.
*so much sig updating needed*

My Github profile - Some Android stuff, some AVR stuff

An excellent post on "noobs vs. developers"

A few opinions on kernel development "good practices"

Note: I have chosen not to use XDA's "friends" feature - I will reject all incoming "friend" requests.

Code:
<MikeyMike01> Smali is a spawn of hell
<shoman94> ^^^ +!
Code:
<Entropy512> gotta be careful not to step on each other's work.  :)
<Bumble-Bee> thats true
<jerdog> compeete for donations
 
REPLY
The Following User Says Thank You to Entropy512 For This Useful Post: [ Click to Expand ]
 
laloutre 		Old
4th August 2012, 11:00 PM
(Last edited by laloutre; 4th August 2012 at 11:06 PM.)
#10  
Senior Member
Thanks Meter 35
Posts: 163
Join Date: Mar 2012
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
Current Devices : Galaxy Note2 Carbon ROM, Nexus 7 travelling from ROM to ROM
 
REPLY

 
Post Reply+
Page 1 of 2    1 2
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...