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!

[Q] sghT999 stuck-bootloop after a bad root,clockworkmod; Success with SuperSU.

I have a T-mobile sgh-t999 that is stuck in boot-loop. I can get into recovery and download modes. The problem started with an unsucccessful root attempt using clockwork mod. After several attempts at fixing, i finally rooted with Chains DD. I enjoyed one day of control and was instructed by "MacTweaker" app to reboot so service could take effect and have not been able to start phone since. There also seems to be a remote-user who is inhibiting my attemps at repair. i dont want to return the phone back to the carrier because of the penalties and charges that may apply. Remote user is a dev with much more knowlegde than myself, and has even infected my home computer through usb from the phone. I was lucky enough to to discover him/her through running trouble-shoot on phone and intercepted a log that had his her "fixes" for my phone that dated Feb. 5, Feb 7, 8, and 9th. These "fixes" included turning up voltage to my kernal, fixing the kernal from "whining about an outdated hack, and states that device will not be able to boot until it receives a reboot signal from a driver a1f2d6. This log also had many referances to clockwork mod with entries like: "Merge clock cm12345 with LED display cm 54321. Run cm 45678 with left handed display...", and many other instances. I believe this dev works for either cwm and is angry i changed to Chains DD, or is employed by Samsung. I tried to save entire log on home computer for further review to have a chance of deciphering and ultimately repairing, but it was "mysteriously" erased from my desktop, AND the FIVE other places I attempted to hide it in: (Folders within folders within folders. Shortcuts to the file within other files, etc.). I am sending this from an internet cafe to try to avoid detection. I've tried to update the drivers but am either not allowed to do so, or the price is more than the the fix. Driver websites also tell me there is an "unknown device" installed on the phone, also. Is there a link that i can download just to reboot the phone? I can download apps to fight once if I could do that. I believe I can fight Big-Brother if i can just get the phone on. PLEASE HELP...

Flash Stock Firmware using Kies.

Huge problem need help urgently
---------- Post added at 12:00 PM ---------- Previous post was at 11:55 AM ----------
[/COLOR]Well I have a Samsung t999 which had a USB problem it charge alright but my MTP wasn't working dunno why.. I figure it was a software problem so tried to flash it with cm11 but I 4got to backup and wiped everything in recovery mode and the cm11 didn't work now my Samsung is stuck in bootloop and I can't use Odin coz my USB cn only charge but not MTP mode... I rli need help... Is there any way I can flash my phone without using Odin... I rli love my phone we been thru alot together... Need help please

Blu Advance 4.0 L A010U ROMs

Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance

I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!

Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.

Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.

Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.

I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?

Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!

Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.

I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method

well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.

What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.

Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.

Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..

Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.

links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy

Root + twrp + bootloader unlock + twrp flashable stock rom - marhsmallow

If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.

Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?

Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.

Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.

I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!

slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....

Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.

I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?

Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's

Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?

famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's

Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.

famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.

Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?

famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.

Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".

famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )

Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.

eMMC image for VS986 Needed for Hard Bricked Device

I hard bricked my phone downgrading from 13b to 11a.
I can send it to LG for a repair per their customer support. I might try doing that.
Would anyone be willing to upload their eMMC image?
If you are that lucky person, who is stuck in the NEW “Qualcomm HS-USB QDLoader 9008” mode, to be honest, the steps to be taken are a lot easier. However, you need somebody having the same phone as yours to upload your device’s complete eMMC image for you. To get such image, you could ask your friend to do these steps (root the phone first):
Format your external MicroSD card with “exfat” system file, and the size of this SD card should be morethan 16 GB , which is the size of the whole partition.
Do a full factory reset, meaning wipe your cache, data, and internal storage using either CWM, TWRP, or PhillzTouch.
Insert the SD card to your phone and connect your mobile with ADB, type:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
The size of the “backup.img” is around 16 GB, However, if you compressed it, it would be around 2 GB.
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse

I've been looking for this for months now. Unfortunately, not a lot of people wanted to help.

There are lots of people willing to help. The problem is that VS986 has not been rooted, and as stated in the post quoted above, root is required to dump the eMMC.
sushi-gee, I am having the same issue and was also told by LG support that I could send it in. Did you end up sending yours in to LG? If so, did they fix it?
I also live in Las Vegas (looking at you, greedness)!

biorpg said:
There are lots of people willing to help. The problem is that VS986 has not been rooted, and as stated in the post quoted above, root is required to dump the eMMC.
sushi-gee, I am having the same issue and was also told by LG support that I could send it in. Did you end up sending yours in to LG? If so, did they fix it?
I also live in Las Vegas (looking at you, greedness)!
Click to expand...
Click to collapse
LG took care of me

biorpg said:
There are lots of people willing to help. The problem is that VS986 has not been rooted, and as stated in the post quoted above, root is required to dump the eMMC.
Click to expand...
Click to collapse
What do you mean VS986 hasn't been rooted?
The Verizon LG G4 (vs98611a and 13b) have been rooted for some time now. And if you're on marshmallow you can downgrade to LP and still root.

sushi-gee said:
LG took care of me
Click to expand...
Click to collapse
Thanks for replying! I'll send mine in once I remember how to stick things to folding paper-pockets and sharpie up boxes for snail-mail.
Spookymyo said:
The Verizon LG G4 (vs98611a and 13b) have been rooted for some time now. And if you're on marshmallow you can downgrade to LP and still root.
Click to expand...
Click to collapse
It is not a full root though, is it enough to allow dumping the eMMC? If so, I will reroot mine to 13b and dump the eMMC for others(and probably myself) to use for recovering the phone from this state so that we can have more attempts to fully brick the thing!

It is a full root. But unlocking the bootloader and therefore installing a custom recovery is not available. There are methods for grabbing your own complete system image.

any luck

majinawaz said:
any luck
Click to expand...
Click to collapse
​I'm still using my G4 to keep my fan from blowing my papers off my desk. The warranty had expired, and I did not have insurance through Verizon, so I may ship it to LG and hope for them to fix it for cheap or free, but it's not on my priority list(as if I keep such a list?!).
​I bought a OnePlus 3T, which is a relieving experience after the G4's constant bull****. I've already flashed TWRP, and then flashed cyanogen, got that working, tried to flash nethunter on top of it all, got stuck in a fastboot bootloop, wiped, reformatted, re-flashed TWRP and cyanogen, and its all working again. That all goes very quickly when the phone is not throwing up road blocks at every step and forcing you to conduct potentially fruitless searches for cryptic error messages or stabbing you in the back with a qualcomm security 'feature' that never gets mentioned until you've triggered it.
​The only drawback with the OnePlus 3T on Verizon is so far it is only capable of making/receiving calls or texts while connected to 3G. If I dial *#*#4636#*#* and choose 'LTE only' it will connect to Verizon 4G, but is then unable to call or text. That was all on the stock ROM, im gonna play around with third party stuffs to see if I can get both to work together.
I am also open to the option of opening up the G4 and retrieving the eMMC via JTAG if someone wants to point me to a guide(I found one a while ago, so it's out there somewhere)

biorpg said:
​I'm still using my G4 to keep my fan from blowing my papers off my desk. The warranty had expired, and I did not have insurance through Verizon, so I may ship it to LG and hope for them to fix it for cheap or free, but it's not on my priority list(as if I keep such a list?!).
​I bought a OnePlus 3T, which is a relieving experience after the G4's constant bull****. I've already flashed TWRP, and then flashed cyanogen, got that working, tried to flash nethunter on top of it all, got stuck in a fastboot bootloop, wiped, reformatted, re-flashed TWRP and cyanogen, and its all working again. That all goes very quickly when the phone is not throwing up road blocks at every step and forcing you to conduct potentially fruitless searches for cryptic error messages or stabbing you in the back with a qualcomm security 'feature' that never gets mentioned until you've triggered it.
​The only drawback with the OnePlus 3T on Verizon is so far it is only capable of making/receiving calls or texts while connected to 3G. If I dial *#*#4636#*#* and choose 'LTE only' it will connect to Verizon 4G, but is then unable to call or text. That was all on the stock ROM, im gonna play around with third party stuffs to see if I can get both to work together.
I am also open to the option of opening up the G4 and retrieving the eMMC via JTAG if someone wants to point me to a guide(I found one a while ago, so it's out there somewhere)
Click to expand...
Click to collapse
Every thing needed for the VS986 "9008" HARD BRICK can be found here on XDA. No Boxes, NO Dongles, No SD cards, No exotic or elusive files. Check this "LG G4 VS986 Super-Hard-Brick-Unbrick / On Any FW version / QComm_9008 Fatality Move"

vs986_27C_QFILRecoveryImage
https://drive.google.com/file/d/0B41ACD_ESYnHbkVzbDloY00tNVk/view?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
---------- Post added at 01:40 AM ---------- Previous post was at 01:34 AM ----------
gratefuldeaddougie said:
https://drive.google.com/file/d/0B41ACD_ESYnHbkVzbDloY00tNVk/view?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
Click to expand...
Click to collapse
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder.