Develop Bugs

[Q] A1CS Fusion5 Economy - bricked

Hi all
I have one of these cheap ICS tablets.It won't let me post the link because I'm new but if you search amazon for A1CS Fusion5 Economy you can see the specs.
It's a bit slow and unresponsive (what do you expect for the price), so I thought flashing it with CM might help.
I got a CWM working on it and following a thread on these forums about allwinner tablets in general I flashed it with (in this order).
cm10_a10_20120913.zip
gapps-jb-20120726-signed.zip
protab2xxlv2_compatibility_1.2.0.zip
Clearly these were not the correct roms (in hindsight I can see that I have used an allwinner A10 rom when my tablet is an Allwinner A13).
After I shut down from CWM the tablet will not switch back on. It also won't boot into either recovery or download mode. Nothing happens when I plug it into its wall charger, nor will the laptop recognise it when plugged into the usb.
I think I have no way to fix this since it is unresponsive to everything that I might do to get it into a state to fixit, but I am very new to this so posting to see if anyone can help?

Did you ever unbrick your tablet and find a solution?
The same happened to me and I could find no way to recover the tablet and yes mine turned out to be an A13 as well
spoondoom said:
Hi all
I have one of these cheap ICS tablets.It won't let me post the link because I'm new but if you search amazon for A1CS Fusion5 Economy you can see the specs.
It's a bit slow and unresponsive (what do you expect for the price), so I thought flashing it with CM might help.
I got a CWM working on it and following a thread on these forums about allwinner tablets in general I flashed it with (in this order).
cm10_a10_20120913.zip
gapps-jb-20120726-signed.zip
protab2xxlv2_compatibility_1.2.0.zip
Clearly these were not the correct roms (in hindsight I can see that I have used an allwinner A10 rom when my tablet is an Allwinner A13).
After I shut down from CWM the tablet will not switch back on. It also won't boot into either recovery or download mode. Nothing happens when I plug it into its wall charger, nor will the laptop recognise it when plugged into the usb.
I think I have no way to fix this since it is unresponsive to everything that I might do to get it into a state to fixit, but I am very new to this so posting to see if anyone can help?
Click to expand...
Click to collapse

I'm afraid I've joined the club....
Does anyone know how to fix this?!!!!

Update!
I have since discovered that the bricking is almost certainly due to loading an incorrect ROM.
I am trying to find a ROM which will work and to upload it using livesuit (google and download it!). I will update further if I have any success, in the meantime I hope this helps someone!
Oh and if the tablet is not recognised by your PC, press and hold the power button for a little while (until your PC beeps like you connected a usb device)
Good luck and update me if you have any luck !

Update 2
Search for:
A7S_A13_86VEB_M707EBC_130511_V1.2
This rom will, once flashed using livesuite, at least allow you to boot to recovery again.
When that screen fired up again I had a big geeky smile on my face!
---------- Post added at 10:20 PM ---------- Previous post was at 10:07 PM ----------
And this cyanogen rom
cm_a13_20130628
will bring you almost back to where we want to be.....
http://www.slatedroid.com/topic/80689-rom-cyanogenmod-10-for-allwinner-a13/
No touchscreen yet......:silly::silly::silly:

Update 3
Still not quite there with the touchscreen but there are a bundle of driver details here:
http://forum.xda-developers.com/showthread.php?t=2189569
Nonetheless, all that is left to do (in theory!) is to identify the correct driver, enable usb debugging (using a usb mouse since the touchscreen doesn't currently work) and then use basic adb commands (if I can do it, you can too!) to push the driver to the device.
I will update in due course. I guess it's too late for you guys but maybe this will help someone one day.

Little help here?!
Well I've narrowed down the drivers to 1 of 3.
I'm trying to work out how to run these - maybe via adb or terminal emulator? to work out which one works.
Then I believe I need to amend the boot file or the script.bin to run the driver automatically?
Any advice gratefully received!

More!
Getting bored of these updates yet?
Sometimes you have to take a step backwards to take two steps forwards...
Installed a new firmware and ROM (FaaastJB V2) flashed with livesuit. Easy.
Still no TS - when you search for FaaastJB though, you will see a bunch of driver files with adb included in the file so you can just hit run and sit back. I had to reflash a couple of times but very quickly the touchscreen was back.
Still working on the camera but I'm pretty much done.
I hope this helps someone!
PS - I should probably give some props / respect / good karma / shout out to Toxicro, the guy who I believe made faaastJB v2. good work fella!

Final post
Quick last one and that's it from me (at last I hear you cry!)
The new faaastJB - v2.5 includes camera drivers. The same TS drivers work.
Rooted, Rom-ed, working, done!
Godneps out!

Can I root my phone on MAC if I purchase Windows 7?

Good evening everyone,
A little something about me, I have no freaking idea how to do all this. I only have one reason for wanting to root my phone. The camera shutter is annoying the **** out of me. It seriously keeps me from taking photos because the annoying shutter. I can't take photos at weddings, selfies, at the bakeshop! lol But seriously, the shutter is killing me. The camera is the main reason I got this phone and it's me keeping me from using it.
Please don't suggest using the video while taking photos because that's just inconvenient and camera apps are not as good the camera on the phone.
I have a MAC OS X version 10.6.8 . I tried to read the instructions here and it makes me want to pull my hair because I don't understand the jargons used. From what I have come up with so far is that I can't root my phone on mac. I have the latest version of android.
I have two questions.
1. Can I root my s3 on MAC?
2. If not, can I root it if I buy Windows 7 for my laptop?
Thanks in advance,
Patsy

For future tinkering and such (flashing, etc), i would recommend just installing Windows on your Mac. Case in point, I have my main PC, a Mac Mini running Windows 7 via VMWare Fusion (even though i also have an HP Media Centre DEC with Windows 7 as well). I've always been a Mac user and always rooted my devices via Windows, it's just more convenient and less of a hassle.

BootCamp it.
It's better than VM when working with devices in "download" mode.
App/Utilities/BootCamp
Get a 32bits version of Windows. WinXP will work Ok.
Use this method to root the phone.
Go to http://forum.xda-developers.com/showthread.php?p=33460982
and READ everything.
After you root your phone go to Play Store search for Goo.Im. After installed open it and press the menu button, select Install OpenRecovery.
Then you are good to install a custom ROM.
It can't take longer than 10 minutes.(don't count the Windows installation)
Sent from my SPH-L710
---------- Post added at 02:17 AM ---------- Previous post was at 01:56 AM ----------
Important!!! Install Samsung mobile drivers for your phone.
Sent from my SPH-L710

csmasn said:
BootCamp it.
It's better than VM when working with devices in "download" mode.
App/Utilities/BootCamp
Get a 32bits version of Windows. WinXP will work Ok.
Use this method to root the phone.
Go to http://forum.xda-developers.com/showthread.php?p=33460982
and READ everything.
After you root your phone go to Play Store search for Goo.Im. After installed open it and press the menu button, select Install OpenRecovery.
Then you are good to install a custom ROM.
It can't take longer than 10 minutes.(don't count the Windows installation)
Sent from my SPH-L710
---------- Post added at 02:17 AM ---------- Previous post was at 01:56 AM ----------
Important!!! Install Samsung mobile drivers for your phone.
Sent from my SPH-L710
Click to expand...
Click to collapse
I back this statement 100%
I use VMwares and it was a PITA to root using it. Bootcamp works Much More efficently and you dont have as many odd issues connecting your phone. However you CAN do it using a virtual machine.
Unfortunately there is no solution to root the sprint GS3 using a mac. you HAVE to use a Windows pc...

Thank you all for the replies. I'm going to do it this weekend. Though I don't understand the terms, I can read so I should not be hopeless.:cyclops:

patsybeach said:
Thank you all for the replies. I'm going to do it this weekend. Though I don't understand the terms, I can read so I should not be hopeless.:cyclops:
Click to expand...
Click to collapse
if you have any issues feel free to msg me or ask here. ill be more then happy to help as i ran into the same issues no more then a couple months ago.

DriveDroid

https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid
http://forum.xda-developers.com/showthread.php?t=2196707
DriveDroid allows you to boot your PC from ISO/IMG files stored on your phone. This is ideal for trying Linux distributions or always having a rescue-system on the go... without the need to burn different CDs or USB pendrives. The paid version of DriveDroid does not include ads and helps the developer.
DriveDroid also includes a convenient download menu where you can download USB-images of a number of operating systems from your phone.
You can also create USB-images which allows you to have a blank USB-drive where you can store files in. Another possibility is to use tools on your PC to make a bootable USB-drive out of the blank image that DriveDroid created.
Click to expand...
Click to collapse
Has anyone got this app to work? I couldnt though the dev said several people with the Nexus 4 have

I second that. Couldn't get it working on my s3
Sent from my Nexus 4 using xda app-developers app

I have a nexus 4 running CM10.1 with Franco Kernel, put DriveDroid on it a few weeks back and have had no issues running SliTaz, Ubuntu, and BSD off it.

I've used it several times with great success. Actually, no problems to speak of. I've loaded up PartedMagic and MintLinux.
FYI - I'm running AOKP (official) + Franco. Once you load up the app, make sure to follow the on-screen instructions that say to set the storage option as USB Mass Storage (selectable from within DriveDroid).

Im using CM 20130306 nightly stock kernel and followed all the instructions

Anybody knows if this works if i wanna try with Windows 7 in my Nexus 4?

hikhokk said:
Anybody knows if this works if i wanna try with Windows 7 in my Nexus 4?
Click to expand...
Click to collapse
Take a look at this: http://softwarebakery.com/windows-install-on-drivedroid
It should allow you to use the Windows 7 installer from your phone. For a live version of Windows from your phone I'd recommend using Hiren's mini-XP, which you can install as follows: http://softwarebakery.com/install-hirensbootcd-on-drivedroid
I'm still in the works of trying to install Windows 8 on DriveDroid as a live OS (so that it runs from the USB stick, instead of just installing)
---------- Post added at 08:22 PM ---------- Previous post was at 08:14 PM ----------
ermacwins said:
Im using CM 20130306 nightly stock kernel and followed all the instructions
Click to expand...
Click to collapse
All USB-related problems are usually depending on the kernel. There are *MANY* floating around and I can't check the code of them all to be sure they'll work.
Therefore, could you also try the Franco Kernel, like sphyyr did? If you can confirm that'll work for you, I have finally some indication of what the problem is. I've recently received more issues with the Nexus 4 then I've noticed before, so it might also be an update that messed things up... totally not sure though.
andybfmv96 said:
I second that. Couldn't get it working on my s3
Click to expand...
Click to collapse
As for the Galaxy S3, there are two devices specifically that I know do not work with their usual kernel: Sprint and AT&T. I'm still working on getting the right patches into a custom kernel, so that I can recommend that kernel to people. This is an error in the Sprint/AT&T kernel that makes the device acts as a CD-rom device (without the necessary fixes to be able to boot from it) without allowing applications to change that mode back to USB-drive.

FrozenCow said:
Take a look at this: http://softwarebakery.com/windows-install-on-drivedroid
It should allow you to use the Windows 7 installer from your phone. For a live version of Windows from your phone I'd recommend using Hiren's mini-XP, which you can install as follows: http://softwarebakery.com/install-hirensbootcd-on-drivedroid
I'm still in the works of trying to install Windows 8 on DriveDroid as a live OS (so that it runs from the USB stick, instead of just installing)
Click to expand...
Click to collapse
great! thanks! :good::good::good:

Looking for lgl15g (LG Sunrise) stock image

I'm looking for the stock image for the LG Sunrise (lgl15g). For some reason I can't find my backup image of stock 4.4.2. I've rooted with Kingroot and somewhere along the way something went horribly wrong. I'm unable to pair w/ bluetooth, can't recieve or make calls, and my home button isn't working correctly. If anyone has the stock image for this phone it would be a big help and much appreciated.

also.. could anyone direct me to an updated tool that can unlock my LG Sunrise without using a computer? Straight Talk has totally burned me on data its rediculas =/

+1
I'm looking for this too....
Thanks

Have you guys found one yet?

Have y'all heard anything about a special cable with a resistor between two terminals forcing low-end LG devices into bootloader/download mode? The only soldering iron I have access to is for leading stained glass, so I'm afraid its tip would be too broad; I'll have to buy a cable somewhere to test this theory.

ToHellWithGA said:
Have y'all heard anything about a special cable with a resistor between two terminals forcing low-end LG devices into bootloader/download mode? The only soldering iron I have access to is for leading stained glass, so I'm afraid its tip would be too broad; I'll have to buy a cable somewhere to test this theory.
Click to expand...
Click to collapse
It happened to me by accident with a LGV410 tablet and some conductive trash inside the cable end. However the LGL15G may be like the LGL34C, being as they're both Tracfone devices, with a locked/near-nonexistant bootloader. Tracfone cheapies are a pain to work with, and with no(?) KDZ files publicly available, impossible to toy with if USB debugging was never enabled.

No luck on the bootloader yet but...
1) Kingroot 4.8 can root it
2) Supersu-Me can remove Kingroot and install SuperSU
3) From there a bloatware removal tool can strip out the office suite and McAfee security software to reclaim internal storage.
I'm hoping to prune enough to make space to switch from Dalvik to ART.

Lgl15g issues ( no calls recieved. Etc)
dm63755 said:
I'm looking for the stock image for the LG Sunrise (lgl15g). For some reason I can't find my backup image of stock 4.4.2. I've rooted with Kingroot and somewhere along the way something went horribly wrong. I'm unable to pair w/ bluetooth, can't recieve or make calls, and my home button isn't working correctly. If anyone has the stock image for this phone it would be a big help and much appreciated.
Click to expand...
Click to collapse
I made a few changes to the build prop. And the system apps. But i wasnt aware of any major changes that i made. But the same thing has happened to me for the most part.
If anyone has a copy of a stock or working build prop. And or a copy of the stock image once someone comes out with a working recovery. Plrase post it.
Code:

LGL15G + Kingroot < LGL15G
I am experiencing the same. Although I do not have the stock image (I think), I did save a couple of backups prior to mine going rogue. If a copy of that would help, let me know.
My main problem now is that I cannot get it to connect to my PC to retreive back up or tranfer files to do a factory reset
~ Cheryl
---------- Post added at 11:53 PM ---------- Previous post was at 11:43 PM ----------
Oh.. I just remembered that I do have the stock kitkat file (about 2g) on my PC but since I cannot get my LGL15G to connect, I cannot use pda.net to gain internet access from PC. If anyone has a solution to this, I can probably post the stock kitkat file.
~ Cheryl

If Kitkat is Kitkat...
I have kitkat 4.4.2 on my G2 (down with a broken touch screen) and apparently the Sunrise is running the same.. or so it says in "About Phone."
This is the link I used to originally download the stock kot file. Hope it helps... if not, I do have the file on my PC which I continually struggle to get internet on.. but if you have any idea on how I can share given the circumstances... let me know
~ Cheryl
---------- Post added at 12:26 AM ---------- Previous post was at 12:24 AM ----------
http://forum.xda-developers.com/showthread.php?t=2665391
here is the link.. sorry.. a blonde moment

I do not have a stock image but have made images of each partition on the device (except userdata - not gonna give you all the keys to my various accounts). The images were made using dd in a terminal emulator on a rooted L15G and can be "flashed" using dd in a terminal emulator on a rooted L15G. Please reply if you want me to post them.

​
ToHellWithGA said:
I do not have a stock image but have made images of each partition on the device (except userdata - not gonna give you all the keys to my various accounts). The images were made using dd in a terminal emulator on a rooted L15G and can be "flashed" using dd in a terminal emulator on a rooted L15G. Please reply if you want me to post them.
Click to expand...
Click to collapse
Pls post system img,thank you

Lgl15g custom recovery and rom
Is it possible to find out how to do it

Invalid official RemixOS 2.0 image for Cube i10-R

Hello, I own a Cube i10-R. The tablet comes with RemixOS 1.0 installed by factory. Recently Jide released an official RemixOS 2.0 image on their site, but I'm not able to flash it. Tried several times, but the procedure always stuck on "droidboot boot". Usb drivers are working, since I'm able to reflash the 1.0 image without issue. I also tried to swap both droidboot.img files (from 1.0 to 2.0 images), but clearly after flashing procedure, the tablet doesn't start. Both the droidboot images are different in sizes, so that swap was an hopeless try basically.
I'm not an android developver, but it seems that the main problem is the droidboot.img file in the last Jide release. Can anyone give a look at it? It would be nice to have a working 2.0 remixos on this good tablet

@Bad-Pixel - Sorry to hear of your experience. When it's our office hours tomorrow, I'll ask the person in charge of this ROM. She'll probably ask me for some specific info from you and then we'll go from there. So, wait until I PM you. Thanks!

RemixOS_Jason said:
Sorry to hear of your experience. When it's our office hours tomorrow, I'll ask the person in charge of this ROM. She'll probably ask me for some specific info from you and then we'll go from there. So, wait until I PM you. Thanks!
Click to expand...
Click to collapse
Thanks for your quick reply! In order to try to speed up both works, the flashing procedure stuck on the follow fastboot command (from flash5.1_user.xml file):
Code:
<command>
<string>fastboot boot $droidboot_file</string>
<timeout>120000</timeout>
<retry>2</retry>
<description>Uploading fastboot image.</description>
<mandatory>1</mandatory>
</command>
When receiving the "fastboot boot droidboot.img" command, the tablet SHOULD switch from DnX mode to Bootloader mode (also called Droidboot if I'm not wrong). After booted in droidboot, the procedure will continue with other commands (this is what happens when I flash back the original RemixOS 1.0 image).
The problem is that the tablet NEVER switch to bootloader mode, but it remains in DnX mode (despites of what the Intel Manufacturing Flashing Tool shows). After 180 seconds, the procedure fails due to ADB Enum Timeout.
I searched on net for some solution, but nothing was found.
Programs used: Intel MFT (ver 6.0.43) with latest Intel Android driver setup (vers 1.10.0). Also i've tried the Intel Phone Flash Tool (both ver 5.3.2.0 and 5.5.2.0)with DnX usb driver.
I can provide to you some screenshots if you need them, just ask whatever you need for!
Anyway, now I just wait for any your comunication. Thanks for your patiente and sorry for multiple messages

You might as well send me screenshots, because in my experience, they'll be helpful.
Thanks!
Bad-Pixel said:
Thanks for your quick reply! In order to try to speed up both works, the flashing procedure stuck on the follow fastboot command (from flash5.1_user.xml file):
Code:
<command>
<string>fastboot boot $droidboot_file</string>
<timeout>120000</timeout>
<retry>2</retry>
<description>Uploading fastboot image.</description>
<mandatory>1</mandatory>
</command>
When receiving the "fastboot boot droidboot.img" command, the tablet SHOULD switch from DnX mode to Bootloader mode (also called Droidboot if I'm not wrong). After booted in droidboot, the procedure will continue with other commands (this is what happens when I flash back the original RemixOS 1.0 image).
The problem is that the tablet NEVER switch to bootloader mode, but it remains in DnX mode (despites of what the Intel Manufacturing Flashing Tool shows). After 180 seconds, the procedure fails due to ADB Enum Timeout.
I searched on net for some solution, but nothing was found.
Programs used: Intel MFT (ver 6.0.43) with latest Intel Android driver setup (vers 1.10.0). Also i've tried the Intel Phone Flash Tool (both ver 5.3.2.0 and 5.5.2.0)with DnX usb driver.
I can provide to you some screenshots if you need them, just ask whatever you need for!
Anyway, now I just wait for any your comunication. Thanks for your patiente and sorry for multiple messages
Click to expand...
Click to collapse

@RemixOS_Jason
here screenshot and log attached!
ps: Also tried to flash it using win7 x64, same error

Hey @bad pixel - I just received an answer from our migration team that I'd like to share with you:
"The reason is that Intel uses different BIOS for Android 4.4 and Android 5.1. The droidboot for Android 5.1 cannot be run on the old 4.4 BIOS. So the flash tool reports an error.
To solve this problem, the user must flash the BIOS first. We do not have CUBE I10's 5.1 bios,
so the user must ask Cube for the new BIOS."
I hope this reply helps. Thanks again!

@RemixOS_Jason Ok i will try to contact them (but I guess it's a waste of time) and explain the situation. I have to ask you one last thing, so please check your pvt.
Many Thanks for your support, I really appreciated your efforts and patiente for this thread

RemixOS_Jason said:
Hey @bad pixel - I just received an answer from our migration team that I'd like to share with you:
"The reason is that Intel uses different BIOS for Android 4.4 and Android 5.1. The droidboot for Android 5.1 cannot be run on the old 4.4 BIOS. So the flash tool reports an error.
To solve this problem, the user must flash the BIOS first. We do not have CUBE I10's 5.1 bios,
so the user must ask Cube for the new BIOS."
I hope this reply helps. Thanks again!
Click to expand...
Click to collapse
Hi, I already provided bad pixel with the droidboot to boot Android 5.1 and the updated bios and its booting with remix 2.0. Could you please send us a link to the latest bios.

Hey tekcomm,
Have I read your comment incorrectly as you seem to state that you're already booting with Remix OS 2.0. The latest bios needs to be supplied by Cube as we do not have them. Please let me know where I've misunderstood and I'll assist you as possible.
Thanks,
Jason
tekcomm said:
Hi, I already provided bad pixel with the droidboot to boot Android 5.1 and the updated bios and its booting with remix 2.0. Could you please send us a link to the latest bios.
Click to expand...
Click to collapse

RemixOS_Jason said:
Hey tekcomm,
Have I read your comment incorrectly as you seem to state that you're already booting with Remix OS 2.0. The latest bios needs to be supplied by Cube as we do not have them. Please let me know where I've misunderstood and I'll assist you as possible.
Thanks,
Jason
Click to expand...
Click to collapse
I already obtained through other means the bios and droidboot that is required. I was wondering if there was a newer version. How can you boot and test remix 2.x without the correct bios?
---------- Post added at 07:20 AM ---------- Previous post was at 07:15 AM ----------
tekcomm said:
I already obtained through other means the bios and droidboot that is required. I was wondering if there was a newer version. How can you boot and test remix 2.x without the correct bios?
Click to expand...
Click to collapse
It does not matter I was just wondering if there was a newer version. Right now I am busy rebuilding the chinese version of the win 10 reference image for the 10-wb and adding remix os 2.0 to it. So it will work on the 10-wb 10-w and 10-r models. Could you do me a favor and double check with one of your devs there is not a bios on mercury.corp.jide.com

We don't actually have any of the BIOS because they're all proprietary to Cube. Please let me know if there's anything else I can assist with. Thanks!
tekcomm said:
I already obtained through other means the bios and droidboot that is required. I was wondering if there was a newer version. How can you boot and test remix 2.x without the correct bios?
---------- Post added at 07:20 AM ---------- Previous post was at 07:15 AM ----------
It does not matter I was just wondering if there was a newer version. Right now I am busy rebuilding the chinese version of the win 10 reference image for the 10-wb and adding remix os 2.0 to it. So it will work on the 10-wb 10-w and 10-r models. Could you do me a favor and double check with one of your devs there is not a bios on mercury.corp.jide.com
Click to expand...
Click to collapse

tekcomm said:
Hi, I already provided bad pixel with the droidboot to boot Android 5.1 and the updated bios and its booting with remix 2.0. Could you please send us a link to the latest bios.
Click to expand...
Click to collapse
Hi, tekcomm. Did you get remixOS 2.0 works on cube i10?

No, I have android 6 installed it came out on the 14 the stable version. To install it install windows 10 first then shrink the partition and install it in the free space. The selection menu even works on boot wwwDOTandroid-x86DOTorg/releases/releasenote-6-0-r2 . The only thing that is not working which is the audio. That is being fixed in the next mainline kernel release. I don't care because I blew up my speakers and use bluetooth anyways.

Btw thats my other account for mediatek devices. If you need any help message my and ill send you my skype.