[jake01]

albertetsbd, on 29 January 2013 - 09:38 AM, said:

I with the same problem ....

I can load USB recovery.to 100% then when finish es recognized like nexus7 in yellow un device.mánager.
I download SDK android from windows

i can't execute adb commands becuase its not connected ..... ( the problem is because is recognized like Nexus 7)

When put adb firts command of recovery.sh

Always device not connected

You need a driver for adb. I´ve installed PdaNet (http://pdanet.co/bin/PdaNetA4013.exe) and the nexus7 in the device manager turns into a android phone and adb shows the devices.

Good luck!

[albertetsbd]

jake01, on 29 January 2013 - 09:45 AM, said:

You need a driver for adb. I´ve installed PdaNet (http://pdanet.co/bin/PdaNetA4013.exe) and the nexus7 in the device manager turns into a android phone and adb shows the devices.

Good luck!

Thanks !! i flash usb.zip 100% without problems .... Now i can enter in ADB but fail ....

recognized like android adb interface and 2 mass storage


Following instructions of fdl :


1. adb push fdisk.cmd /tmp OK
2. adb push fdisk.sh /tmp OK
3. adb shell chmod 775 /tmp/fdisk.sh OK
4. adb shell /tmp/fdisk.sh--------------------------------- > fidk : cant open /dev/block/avnftli


here i enter in adb shell and cd /dev/block and ls listed only loop0,loop1 ...... loop7
i try to modify fdisk.sh


from
/sbin/busybox fdisk /dev/block/avnftli < /tmp/fdisk.cmd/sbin/busybox sync
to
/sbin/busybox fdisk /dev/block/loop0 < /tmp/fdisk.cmd/sbin/busybox sync

and then again point 1,2,3

but then in point 4 error cant read from /dev/block/loop0 ( i try too to modify perms 775 or 777 )

STOP HERE

5. adb shell parted -s /dev/block/avnftli mkfs 1 fat32

EDIT : i try follow withou point 4 and 5 ( because fail )



6. adb push update.zip /tmp OK
7. adb push update-binary /tmp OK
8. adb shell chmod 775 /tmp/update-binary OK
9. adb shell /tmp/update-binary 3 stdout /tmp/update.zip --->>>

....
...
...

about to run program [/tmp/install-optional.sh] wi
Installing face detection support
unmount of /system failed; no such volume
write_raw_image: no mtd partition named "bootloade
write_raw_image: no mtd partition named "boot"
write_raw_image: no mtd partition named "aml_logo"
write_raw_image: no mtd partition named "logo"
write_raw_image: no mtd partition named "recovery"
script result was []

I supose because i can made the point 4 and 5 .....

stop here now




10. copy uImage_recovery for twrp(batch3) to sd card, also included in usb_recovery.zip
11. remove usb cable from device, boot the device, insert usb cable
12. adb push update.zip /tmp
13. adb push update-binary /tmp
14. adb shell chmod 775 /tmp/update-binary
15. adb shell /tmp/update-binary 3 stdout /tmp/update.zip
16. adb push aml_autoscript /sdcard
17. remove usb cable and reboot the device, wait for another reboot, charger screen or shutdown
18. remove sd card, boot the device, you should see your tablet booting



I want to mourn are entering, I feel very silly

ANY IDEA OR HELP ????


is not posible to put avnftli in /dev/block/ is someone download this file and i put with push with adb ( sorry if I say stupid things but it is the first time I deal with these issues)


IN ADB SHELL :

/dev/block # ←[6nls -la
ls -la
drwxr-xr-x 2 root root 200 Jan 13 06:50 .
drwxr-xr-x 10 root root 13200 Jan 13 06:50 ..
brwxrwxrwx 1 root root 7, 0 Jan 13 06:50 loop0
brw------- 1 root root 7, 1 Jan 13 06:50 loop1
brw------- 1 root root 7, 2 Jan 13 06:50 loop2
brw------- 1 root root 7, 3 Jan 13 06:50 loop3
brw------- 1 root root 7, 4 Jan 13 06:50 loop4
brw------- 1 root root 7, 5 Jan 13 06:50 loop5
brw------- 1 root root 7, 6 Jan 13 06:50 loop6
brw------- 1 root root 7, 7 Jan 13 06:50 loop7
/dev/block # ←[6n

This post has been edited by albertetsbd: 29 January 2013 - 04:04 PM

[fuser-invent]

So I purposefully hard bricked my device a couple of times today to test this out. I made sure to bring it down to the M6 Chip level so I'd be able to test it from a "hard" brick. The instructions are mostly pretty clear and everything worked without a problem up until the last step.

I pushed the aml_autoscript to the sd card, unplugged the tablet and rebooted the device. I went through the process from start to finish and rebooted both with just the power button and then again with the power and vol- because it wasn't specified which one to use in the windows instructions but seemed that way in the linux ones. The tablet lights up black screened but just stays lit up and never shuts down. At this point the only two things on the SD card should be the aml_autoscript and uImage_recovery, correct?

Also on step 11 I rebooted into recovery and ran through the adb commands again. I would suggest specifying that in the instructions if I was correct and specifying in step 17 and 18 whether or not we should be rebooting into recovery or booting with just the power button.

Also what is recovery2.sh and all associated files for?

This post has been edited by fuser-invent: 29 January 2013 - 05:52 PM

[scoopex]

fuser-invent, on 29 January 2013 - 04:26 PM, said:

So I purposefully hard bricked my device a couple of times today to test this out. I made sure to bring it down to the M6 Chip level so I'd be able to test it from a "hard" brick. The instructions are mostly pretty clear and everything worked without a problem up until the last step.

I pushed the aml_autoscript to the sd card, unplugged the tablet and rebooted the device. I went through the process from start to finish and rebooted both with just the power button and then again with the power and vol- because it wasn't specified which one to use. The tablet lights up black screened but just stays lit up and never shuts down. At this point the only two things on the SD card should be the aml_autoscript and uImage_recovery, correct?

Also on step 11 I rebooted into recovery and ran through the adb commands again. I would suggest specifying that in the instructions if I was correct and specifying in step 17 and 18 whether or not we should be rebooting into recovery or booting with just the power button.

i have powered off my device by my self when i need to go into twrp. there was the only thing, that´s adb do not see the crystal. starting and stoping adb sideload does that i could do it with adb again. after this, power down the crystal an i have only the aml_autoscript on the SD-Card. it tooks a minuet or so and the crystal boots. but at this time it was not 100% clear what i have to do, it worked ;-)
but you have to do the restart by youself after using adb.

[scoopex]

@ albertetsbd

do you have any sd-cards in the device? i don´t know why you will get two mass storage devices.
i brick my device with ab wrong comp (batch 1), so that i can do this again and it works. you can try to erase the nand (AML), it can be one thing.

[fuser-invent]

Still having problems, it looks like there might be problem with:

adb shell parted -s /dev/block/avnftli mkfs 1 fat32

Once it gets to installing the update.zip there are tons of errors and it quickly says there is no more room to install parts of the package.

[scoopex]

fuser-invent, on 29 January 2013 - 06:16 PM, said:

Still having problems, it looks like there might be problem with:

adb shell parted -s /dev/block/avnftli mkfs 1 fat32

Once it gets to installing the update.zip there are tons of errors and it quickly says there is no more room to install parts of the package.

at this point i haven´t a problem, only 3 or 4 by installing the update.zip at the beginning with bad things (sorry can't remember the correct output).
now it works the second time by me. fldc says nothing with NAND erase, i have done this. after that i flashed it without powering down.
can it be, that is anything left on you device, that you have to erase?

[fldc]

fuser-invent, on 29 January 2013 - 04:26 PM, said:

So I purposefully hard bricked my device a couple of times today to test this out. I made sure to bring it down to the M6 Chip level so I'd be able to test it from a "hard" brick. The instructions are mostly pretty clear and everything worked without a problem up until the last step.

I pushed the aml_autoscript to the sd card, unplugged the tablet and rebooted the device. I went through the process from start to finish and rebooted both with just the power button and then again with the power and vol- because it wasn't specified which one to use in the windows instructions but seemed that way in the linux ones. The tablet lights up black screened but just stays lit up and never shuts down. At this point the only two things on the SD card should be the aml_autoscript and uImage_recovery, correct?

Also on step 11 I rebooted into recovery and ran through the adb commands again. I would suggest specifying that in the instructions if I was correct and specifying in step 17 and 18 whether or not we should be rebooting into recovery or booting with just the power button.

Also what is recovery2.sh and all associated files for?

ok,here we go ..
yes, aml_autoscript should execute when no buttons are pressed, but did it execute in your case? In that case, maybe this should be mentioned.

I didn't mention this because because you're supposed to do a normal boot, but yes,could be more clear.

recovery2.sh is removed in the most recent file i uploaded, I was initially trying to change u-boot environment variables from linux by using fw_envset from u-boot, but it never actually wrote changes to nand for some reason, so I abandoned this, it could read without issues though.

EDIT:
Also, I have no problems with you adding this/something based on or improved to your thread, the important thing for me is only to help people getting their tablets to a usable state.

This post has been edited by fldc: 29 January 2013 - 08:03 PM

[fuser-invent]

@ scoopex - I'm pretty sure I completely wiped everything. I got it into M6 chip mode and then did a nand erase before starting.

Yes I'm mostly sure aml_autoscript executed with no buttons pressed, I just rebooted the tablet normally but I also tried adb reboot when that worked. The screen goes off, comes back on for a few seconds, goes off again for a second and then comes on and stays on. I must have the old files, so I'll download the new ones and give it another shot, were there any changes that might make it so this work for me?

[fldc]

scoopex, on 29 January 2013 - 05:18 PM, said:

i have powered off my device by my self when i need to go into twrp. there was the only thing, that´s adb do not see the crystal. starting and stoping adb sideload does that i could do it with adb again. after this, power down the crystal an i have only the aml_autoscript on the SD-Card. it tooks a minuet or so and the crystal boots. but at this time it was not 100% clear what i have to do, it worked ;-)
but you have to do the restart by youself after using adb.

I usually just remove and insert the cable to get adb working when it fails to get it working, but this could be a good workaround to mention.
Didn't think of this, maybe I should mention how to reboot/shutdown

[fldc]

fuser-invent, on 29 January 2013 - 06:16 PM, said:

Still having problems, it looks like there might be problem with:

adb shell parted -s /dev/block/avnftli mkfs 1 fat32

Once it gets to installing the update.zip there are tons of errors and it quickly says there is no more room to install parts of the package.

update.zip will not touch this partition, it's only the internal storage, did you erase nand? Is it a batch3? Could be a size difference in the different nand used on the second batch3 variant.
I would need an actual error to know what goes wrong.

[fldc]

scoopex, on 29 January 2013 - 07:13 PM, said:

at this point i haven´t a problem, only 3 or 4 by installing the update.zip at the beginning with bad things (sorry can't remember the correct output).
now it works the second time by me. fldc says nothing with NAND erase, i have done this. after that i flashed it without powering down.
can it be, that is anything left on you device, that you have to erase?

You're right, erasing nand is always a good thing, so I should probably mention this to.

[fldc]

fuser-invent, on 29 January 2013 - 07:49 PM, said:

@ scoopex - I'm pretty sure I completely wiped everything. I got it into M6 chip mode and then did a nand erase before starting.

Yes I'm mostly sure aml_autoscript executed with no buttons pressed, I just rebooted the tablet normally but I also tried adb reboot when that worked. The screen goes off, comes back on for a few seconds, goes off again for a second and then comes on and stays on. I must have the old files, so I'll download the new ones and give it another shot, were there any changes that might make it so this work for me?

Sounds like it yes Much was removed from aml_autoscript if you're using the first one I uploaded, it now contains what's important to the recovery, i was setting all env variables before, caused som issues sometimes. I've noticed you never really know what's going to happen when reset is issued in the script.

[fuser-invent]

Well I'm going to run through the process again right now. What about the question I had about adding it to the pinned unbricking thread, crediting you and whether or not you wanted me to host your files?

EDIT: I just took a look at the new package and your scripts. They are much cleaner now. So far no errors in the adb commands where I was getting them before. How long should the aml_autoscript take and does it actually shut down when it's done?

EDIT 2: Still the same result on my end but with only two of what I think are errors from the update-binary:

mtd: not erasing bad block at 0x80000000
mtd: not erasing bad block at 0x82000000

They were the first two lines in the command prompt and everything else worked fine this time. I'm assuming this means that it's not writing the kernel. The end result is still a backlit screen but the ROM doesn't boot. Could this be because I used my method to unbrick this Batch 2 and overwrote the kernel with the grady.wang or do you have any other ideas?

This post has been edited by fuser-invent: 29 January 2013 - 08:44 PM

[scoopex]

fuser-invent, on 29 January 2013 - 08:05 PM, said:

EDIT 2: Still the same result on my end but with only two of what I think are errors from the update-binary:

mtd: not erasing bad block at 0x80000000
mtd: not erasing bad block at 0x82000000

They were the first two lines in the command prompt and everything else worked fine this time. I'm assuming this means that it's not writing the kernel. The end result is still a backlit screen but the ROM doesn't boot. Could this be because I used my method to unbrick this Batch 2 and overwrote the kernel with the grady.wang or do you have any other ideas?

when i was unbricking, i've got the same errors. both times when running the update. do you think its the kernel? and yes i have the 3.0.8-gcda87f3-dirty-chengnan.tan@droid07-sz kernel.
when you see the display flashing and go black. try to remove the sd-card an power on.

[3ndymion]

scoopex, on 29 January 2013 - 03:42 AM, said:

camera works an g-sensor too. i will test this in games.

i have used "androsensors" to test it. al all three axis works.

That's great news. Thanks for mentioning that androsensors. That's a really great thing to have. I usually use Elixir for all that, but this one's just as good too.

[albertetsbd]

scoopex, on 29 January 2013 - 05:23 PM, said:

@ albertetsbd

do you have any sd-cards in the device? i don´t know why you will get two mass storage devices.
i brick my device with ab wrong comp (batch 1), so that i can do this again and it works. you can try to erase the nand (AML), it can be one thing.

NOt sd card imsert ....

I try with erase nand,usbzip 100 %

My problem inicial for brick crystal : Insert sdcard for error with a firmware of hero (autoflash) .... this I supose delete system files of crystal


and same problem in ADB

adb shell /tmp/fdisk.sh--------------------------------- > fidk : cant open /dev/block/avnftli

I think that is corrupt (missing avnftli and i think too missing files dev/block/m mcblk0p1, mmcblk0p1 or something else ) necesarys for partition i think


SOMEONE know what files will have in /dev/block ???

because if ignored this and then continue in this point error :



9. adb shell /tmp/update-binary 3 stdout /tmp/update.zip --->>>

supose for missing files in dev/block
....
...
...

about to run program [/tmp/install-optional.sh] wi
Installing face detection support
unmount of /system failed; no such volume
write_raw_image: no mtd partition named "bootloade
write_raw_image: no mtd partition named "boot"
write_raw_image: no mtd partition named "aml_logo"
write_raw_image: no mtd partition named "logo"
write_raw_image: no mtd partition named "recovery"
script result was []


Any solution ????? I have another Crystal untouched working fine

HELP ME PLEASE !!!!

id dont know if troy or someone know this ....

Thanks and regars

This post has been edited by albertetsbd: 30 January 2013 - 05:02 AM

[fuser-invent]

Someone sent me a Batch 3 Crystal to unbrick for them and this method worked for that tablet. No problems at all like with my personal Batch 3. I also got 100% in the AML Software without an error and only had to run through the adb commands once instead of twice.

This post has been edited by fuser-invent: 31 January 2013 - 06:23 PM

[droidbaby]

Flickering Screen of Death


So update on my problem... the first few flickering screen of death I plugged my tablet into the PC, PC recognized it as it is.
I tried it again after more flickering screen of death, I got error so I did the Power button and -vol button, gave me a the 2M drives.
I uplugged it and tried it on a different PC, I got an Unidentified Device XNo Driver Found error.
Can somebody tell me if I'm bricked?

The only thing that I know I did was fix the Google play. BUT the flickering screen of death was there already long before I did the fix (change the build.prop to nexus 7)

[fuser-invent]

If it's showing up on your computer as a M3 or M6 Chip then yes, you have a "deep" bricked device.