Develop Bugs

Digital2 Platinum Pad 8 - D2-861G-BK

So I created this topic because there is hardly anything on the internet regarding this tablet. I just recently purchased it from Best Buy and it took me quite some time to find something that would help me root it. Finally, I tried vroot ( a rooting application) and I succeeded in rooting my tablet. I don't have the exact link I used to get vroot but a simple Google search should suffice. Anyway, I figured I'd start this topic for anyone and everyone who uses this tablet or knows of this tablet to discuss any other developments. For now, if anyone needs help rooting their tablet and getting superuser running, I'm here to help.~
For now, I hope you all can figure out how to use vroot (yes, I know it's in Chinese. I can not read Chinese but it was pretty simple to get through the process of rooting.) Anyway, I don't remember the specifics but if anyone else gets through it, I ask that you please post some details on how you did it for everyone else to get through it as well. Hopefully, with time, we can get some good stuff going with this tablet. Could anyone figure out how to get CWM Recovery running on it? I'm a bit new to this and I don't want to screw anything up.

Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!

arpitp said:
Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work. If you want to try the software, however, I've connected it to my computer numerous times without the need for any special drivers. Only thing I can suggest is the generic google drivers. By the way, I reverse searched the tablet's hardware and kernel and came across a duplicate device from China. It is exactly identical right down to the appearance, hardware and software to our tablet. It is called the Chuwi VX8 and the only difference is that it comes in white rather than black.
After making this discovery I came across a nice little development topic for the clone device (http://www.freaktab.com/showthread.php?16025-Chuwi-VX8-RileyROM-1-1) and it seems they've founded good amount of research into the tablet. They've come up with a rom (I've yet to test), CWM Recovery (Unable to flash. If anyone else can try, that'd be dandy.), root methods (with links), among other things. It seems that anything that would work with the Chuwi tablet SHOULD work with the Digital2 Platinum Pad 8. The same rooting method was required and everything about the two tablets is perfectly identical so I'm led to believe they're going to be able to use identical roms or recoveries. I'll look more into flashing CWM Recovery tonight and get back to you on my results.

Josh8550 said:
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work.
Click to expand...
Click to collapse
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.

arpitp said:
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.
Click to expand...
Click to collapse
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.

Josh8550 said:
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.
Click to expand...
Click to collapse
As you mentioned, the link was for the (Windows) software. It requires ADB connection to a computer (usually requires special drivers).
When you said you used the application instead of the software, I assumed you used an APK. However, there is no apk of (the official) Vroot (it was designed to work through Windows). That makes me think the root app you used was something else. So I have to ask... what did you use to root this device?

vRoot is now iRoot
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
UPDATE: (IMPORTANT, please read): The APK does not work. or at least, I couldn't get it to work on my device. It tells you that you've got root, but doesn't really give it to you. Download the computer based exe from the link that Josh8550 posted earlier.
You will need developer permissions (Settings -> About Tablet -> tap Build Number until it tells you you're a developer).
Install ADB and Drivers on windows PC (http://forum.xda-developers.com/showthread.php?t=2588979)
Connect tablet to PC with USB cable.
Run vRoot (iRoot) on PC. Program will connect to tablet and check for root.
Click the "Get Root" button.
Wait...
Tablet will reboot.
Wait...
Program will connect to tablet and check for root.
Program should verify that you have root.
Download and Install SuperSU from the Play Store.
Open SuperSU and Update SU Binary. You will have to give SuperSU root permissions from the chinese interface (choose the box on the right, don't mark the check box).
Reboot.
Congratulations! You now have root access. Enjoy!
More info to come later...

nahrwoldinternet said:
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
Click to expand...
Click to collapse
Thanks man. I couldn't find the link to the apk again so that's a huge help for everyone here. I'll try to get CWM recovery working soon then I'll see about getting Cyanogenmod 11 ported over.

Rooting Digital 2 tablets
Hey everyone.
I successfully rooted with Kingo ROOT using my PC, however now Im stuck. Cant seem to find ROMs or Mods compatible with this tablet.
Any info out there would be great. Im running a 4.1.1 Jelly Bean.

Rooted now what?
Did you ever try the cwmr or cyanogen ROM you had mentioned above?

[email protected] said:
Did you ever try the cwmr or cyanogen ROM you had mentioned above?
Click to expand...
Click to collapse
I did, and ended up hard bricking it for months until I finally got it back out, fixed it and gave up.

I also have the D2-861G and ended up bricking it but have been unable to fix it, would you mind telling me how you got it back up and running.

[Q] Unsure if my LG G3 is fixable, please say it is

Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.

xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.

epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.

I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.

Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.

Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone

Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!

Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.

xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?

epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.

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

Need Rom for Alcatel 4037a

Good day my friends. This is my first post but i read these forums very often. I own a Digicel Dl750 (alcatel 4037a) which i would really appreciate some help with. I tried to flash my phone some time ago using a tutorial i found online since i couldn't find anything useful here (my go to source for these things). However, after trying to flash the rom and failing, i am stuck with a phone that won't respond to any input. COnnecting it with a usb simply gives me a white light on the phone, and device manager reads a "MTK usb port" device. it won't boot or anything else. Been trying to install some kind of recovery but i've had no luck so far. Is anyone here able to provide me with a backup of a working phone so i can fix mine please.
Edit Note1: After a bit more testing, I have pretty much confirmed that it is a problem with the preloader as the phone seems to completely skip the preloader when you connect it to the pc, and after a few seconds goes to the bootrom(?) instead. I am making this call based on the hardware ids show in device manager.

#BUMP I also need a stock firmware for the DL750 4037A

kingofkrunck said:
#BUMP I also need a stock firmware for the DL750 4037A
Click to expand...
Click to collapse
Well i was able to get an OSP dump which solved my problem. Not sure it would be of use to you though

Where can I get this dump at Denis?

Help with a unsupported build

I've been trying to figure this out for a while, and I have made some headway but I think I need to make custom build. If anyone could point me in a direction, it would be super helpful. I have a few ELO ESY15i1 android computers. They are EOL now, and only supported up to kitkat. ELO does not release their kernel source, but I do have their peripherals.
This is how far I have got with this thing, and what I was able to do/determine.
After a bunch of digging, I'm pretty sure that this thing is just a modified S4 i9505. Hardware specs seem to match, outside of the CPU only being 1.7 instead of 1.9ghz. I'm *assuming* that they have down clocked it maybe? The first unit I was working with, apparently had a bricked recovery (had bough it 2nd hand). I was able to boot it into TWRP using the jfltexx image, but I would get no picture. I know it was booted because I could access TWRP via cmd, and it was giving me responses back.
I was able to root it in a very round about way. Since I do not have any volume buttons, I'm limited to adb etc. I was able to root it with iRoot, convert that to supersu, and eventually get flashfire to install. I could finally access almost everything I needed. At some point, I got it stuck in a mode where "QHUSB_DLOAD" was shown to me, with a folder called "image" which I took a copy of. Any google results with that, was just people who had bricked their device, I was able to boot in and out of this, so I'm not sure what was going on or broken.
Here is what the device props listed out: hXXps://pastebin.XXX/FtgQ0DUE
This is the mobilodin report: hXXps://pastebin.XXX/BZrDAFg4
Finally, the "image" I copied: hXXps://anonfiles.XXX/lcQ7RfJ8o0/ESY15i1-image_rar
(sorry can't post links)
The first unit I was working on, I gave to a buddy to mess around with. The 2nd one I have, I have now bricked and it is officially stuck in the "QHUSB_DLOAD" mode. I made a poor choice, and modified the i9505 "updater-script" in lineage-17.1-20200723-nightly-jfltexx-signed to include my "msm8960" device. I flashed it via FlashFire which did go through, just bricked me in the process.
I had a samsung download jig, but I can't find it anywhere, so I have a new one on order. I'm too lazy to cut up a micro usb plug and make one. I have yet to get odin to recognize it at all, or get it into download mode. When I try over adb, it will reboot, try to go in some mode, then reboot again back to the rom.
Any input / help would be greatly appreciated. These machines are super cheap on ebay, the only problem is being stuck on kitkat. I can think of loads of things to use these for, doesn't look like anyone has tried to do anything with them. From all my searching I just found one guy who was trying to root one, and that was about it.

Hi,
I have one 22 inch unit, which I'd like to use with monitoring system and some else, but I need android version with multi windows support, so I'd like to ask you if you succeed with installing new ROM ?
Thanks in advance for reply
Maciek

Well, I've been dinking around with it again, I think I have the HW figured out. I'm pretty sure it's an LG Optimus G, LGE970 is what I'm trying.
I was able to take the stock "ATT-Stock-E97020j" non KDZ zip, pull the boot.img off of it, and flash that.
Now when I connect to my computer, I'm getting LGE Androidnet for Diagnostics, and LGE Androidnet USB serial, as 2 devices.
Just keeps hanging right away when I try and flash the KDZ.