[Question] Can't flash, can't get into bootloader...

[luuksa]

Hello, I'm a little bit new to all this, so any help and detailed instructions are very very helpfull.

So I have Gigabyte GSmart Aku A1 device (MediaTek 6589), I don't know if it's bricked or what but apparently is not working quite well.

When I turn on my phone, it just loads and loads and loads and nothing happens (waited for about 4-5 hours), that was starting to happen after I somehow installed CWM on my device with some tutorial, CWM worked for the first time and after next reboot, it disappeared and stock recovery came back (and the problem with infinite loading screen - only showing logo).

I have ADB drivers installed, SDK aswell, tried to put stock firmware (got it from official site) and in like 1/4 of installation it says:

Code:

symlink: some symlinks failed

After that, I tried to install few versions that I downloaded from that official site, but same error again and again. (I tried to install with SD card and with ADB too. ADB is only working when I go to "apply update from ADB" in recovery. I have also used 2 different types of SD cards.)

That didn't worked either, so I got to some russian forum, and using google translator I downloaded 5-6 types of custom ROM's / Firmwares. That didn't worked either, one time when installing one of those ROM's - it said something about signature..
After that I was trying to install those ROM's with ADB and with SD Cards aswell, but turns out that every single time I get error saying: "Installation aborted.".

I have ofcourse tried to wipe data/factory and to wipe cache too, but nothing helps..

Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.

I really don't know what to do anymore, so any help would be very very appreciated. Thank you for your help in advance, if you need any videos, pictures or something, just tell me.

Also, When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".

[mirandam]

First of all you should have a complete backup... oh well, I guess you don't have it
Second, you should get the correct stock rom for your phone, or the one nearest to it
Third, give up on adb sideload and other flashing stuff, use sp flash tools, nothing else.
Forth, to use that, install the correct drivers
Fifth, read on this forum all you can find about sp flash tools even before trying, if not you will be asking questions which are likely to have been put forward by others, so search and read, and read
Sixth, flash your stock rom and see if the phone boots
Seventh, if it does, leave it alone and read again all you can find about how to make a proper backup
Eight, make that backup before anything else.
Ninth, write on this forum about your experience
Tenth, give a party! Now you can go ahead doing things like flashing other recoveries, since you have that great backup, no worries!
and last of all, let us know how your party went!

As you can see , these are the ten commandments to any android device. If that don't work, read the bible again and pray...

[luuksa]

Hey mirandam, thank you for replying .

1st, Yeah I know, that was my fault.. Didn't backed up at all :/
2nd, Got it and can't install it, every single time I get this symlink error, googled it and found nothing about it..
3rd, The problem is that I can only use adb sideload, can't use other tools.
4th, I have original drivers installed, I got them from Gigabyte support page.
5th, I had my phone connected to SP flash tools, before it was bricked, now SP flash tools can't find my phone at all. (I had already tried reinstalling drivers, downloading other versions of SP flash tools.)
6th, The problem is that installation gets to like 25 percent, and then ends with and symlink error.
7th, I would do that if my phone would sucessfully boot.

So yeah, I already tried all of that and nothing of that is working. I'm 100% sure that I have correct drivers and that they are installed, the only thing is that I don't get ADB connection when I connect my device with USB. I can get ADB connection only when I'm trying to install ROM from adb (when I select that option in recovery).

So, umm.. What could I do? Is there any way that someone send me backup of Aku A1 and that I restore it?

Anyway, thanks for replying and for your time

[WuddaWaste]

[aus9]

at the risk of offending mirandam

Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.

this does not look right at all.

If you have a PC and adb is running correctly, for Windows users that means in admin mode.....you can not issue any adb command until you see a positive result for

Code:

adb devices

if you phone appears then and only then can you run

Code:

adb reboot bootloader

this will reboot phone into either a menu bootloader or fastboot

2) if you are in fastboot.....all adb commands MUST fail
instead you need fastboot installed on your PC and you now issue

Code:

fastboot devices

Do you see a trend here? and you must see a device

AFAIK your options to flash during fastboot are limited to
boot,recovery and system....choose one or more or all

Pretending your recovery is crap you would restore your original with

Code:

fastboot flash recovery recovery.img

where recovery.img is in the same folder as a windows user is running fastboot.

Linux users have better options but would require even more reading that your time does not seem to permit.

3) custom recovery offers sideload

to get to it....you boot into recovery
choose install zip
choose from sideload

on PC your command is

Code:

adb sideload filename

where filename is in same folder as a Windows users running adb.

another way of putting that is
---while in adb mode you are never in fastboot mode
---while in fastboot mode you are never in adb mode

good luck

[mirandam]

at the risk of offending mirandam
...

No offense at all, we all try to help the best way we can.

...

Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.

this does not look right at all.

If you have a PC and adb is running correctly, for Windows users that means in admin mode.....you can not issue any adb command until you see a positive result for

Code:

adb devices

if you phone appears then and only then can you run

Code:

adb reboot bootloader

this will reboot phone into either a menu bootloader or fastboot
...

True, but if the phone isn't booting at all it probably won't respond to adb. Some phone don't respond to adb in recovery.

Also, When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".

Which to me seems like something is wrong with one of img files.
Could be your scatter file or even images itself.
If an image is too large to fit in the partition on your phone, it will overwrite part of the next partation usually leading to not booting.
As you can get into recovery, seems like preloader, lk.bin and recovery are ok, so it's likely to be one of the other images.
Bit tedious, but you'd do wise to check all images sizes against the info in the scatter file to make sure they fit.
And I stick with WuddaWaste's remark about flashtools, I think you should spend time and effort on getting this to work, otherwise things get too complicated.

[aus9]

Also, When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".

Which to me seems like something is wrong with one of img files.

don't be shy.....he is in recovery mode when attempting this....say so. It has nothing to do with any other image file other than recovery. Not that I am an expert but I do have experience in this area.

It is highly likely its a bad recovery..../etc/recovery.fstab

OP is not in custom recovery any more AFAIK....he is in stock

2) Now that I have opened my big gob....I downloaded a CZ version of CWM for that device and can state the following

a) scatterfile appears to be as attachment

b) source is
[Only registered and activated users can see links Click here to register]

3) I took the liberty of unpacking the cwm recovery and just like siewerner's post with me and me rebuilding his CWM......the problem is CWM does NOT build correctly the init.usb.rc

b) wrong usb rc attached....renamed from init.usb.rc to usb.txt for forum rule compliance.....you will notice that the set command got it wrong IMHO
setprop sys.usb.vid 0BB4
and for adb to work the next line IMHO is also wrong
write /sys/class/android_usb/android0/idProduct 0C03

I suggest that it was a port of either a HTC device or iocean
as they share the same usb ids.


4) that zip file contains allegedly an original recovery so I post in quote box the recovery.fstab.....maybe the OP can confirm if it looks ok?

# mount point fstype device [device2]

/boot emmc boot
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p5
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p3

b) and the cwm recovery in quote box

# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p7
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p9
/sdcard vfat /dev/block/mmcblk1p1
/sd-ext auto /dev/block/mmcblk1p2

###############

OP can you get into boot loader menu?

#############

Assuming OP was indeed in stock recovery the reason for the data mount error is
stock recovery is trying to mount /dev/block/mmcblk0p5
while CWM believes its /dev/block/mmcblk0p8


I may have more to say later.