Develop Bugs

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

No OS will install properly, odin won't work, need help with TWRP on N5110

This is my first post, so please forgive any mistakes I make with a post.
My wife's Galaxy Note 8.0 tablet was being stupid, it would refuse to properly use the internet from our Asus router, would connect but apps would insist there was no connection. Was getting tired of that crap so I decided to install a custom ROM, since samsung can be kind of jackasses abandoning most their devices after one major update, was only running Kitkat for crying out loud. I had done so before, but issues arouse. For one, I had great difficulty finding a proper TWRP for some stupid reason, NO ONE seamed to know where to get a well working version. I found one, but it messed everything up, it seems to work just fine but any ROM I install has massive issues with the Google apps, they crash eternally and continuously so I can do literally nothing, can't even get past first setup. I came across talk that it was old TWRP to blame, that it has issues with newer OS's like the lollipop I was trying to install, and FINALLY managed to find a newer version of TWRP, but freaking Odin keeps hanging on it's install, gets to "Nand write start" then stops doing anything. I have tried different cables as well as different computers, does jack crap so far to help. My backup I made in TWRP doesn't even work, when I restore the result is nothing but a boot loop. I am trying to find a stock os to restore it to (mostly) original condition, but it is absurdly difficult for some stupid reason to find, found one all in one exe that didn't work for a damn. I was hoping there might even be a way to install the newer TWRP from with TWRP itself. Can anyone help me with any part of this?

First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.

kge420 said:
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
Click to expand...
Click to collapse
Sorry, but you are going to have to be a little more specific. I installed Switch, but connecting an off device obviously does nothing, should I install and let it boot into a broken ROM again, where gapps crashes, and connect it then?

If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!

Thanks, pretty much.
kge420 said:
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Click to expand...
Click to collapse
None of what you said really made sense, I could not get to ANYTHING AT ALL that was not Odin or TWRP. But that link you had gave me the name for the stock os, I searched that and flashed it and now everything is great. So thanks, sort of. You even mentioned that method not working for you I think in that thread, but it did for me, so yeah.

All good then.

Need Help Modding ROM

Hello,
I am new to modding/creating ROM's but have ok experience with android and linux themselves. I recently bought a Pumpkin android 4.4.4 head unit that has a RK3188-T SOM with 32GB nand and 2GB RAM at 1024x600. I thought it would work with malaysk's rom because it's a RK3188, but it gets stuck in a bootloop with the google stock android boot animation (the silver ANDROID with a shimmer going across). I've been trying to self teach/google how to mod the rom to make it work with my device but haven't been able to yet. I have the update.img's for both malaysk and pumpkin unpacked as well as their recovery and boot img's. I've also been trying to learn what it takes to pre-root the stock rom so I can at least get xposed up and running, but there's not really any good tutorials on that either. If anyone could help me out learning how to pre-root or how to/what to mod to get malaysk's rom working I'd be extremely grateful!!!!
Oh, also, with the unit at the boot animation, is that still the boot.img, or has boot.img passed control off to system.img at that point? Trying to narrow down where the problem is.
Thank you in advanced,
-Kyle

Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development

themissionimpossible said:
Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development
Click to expand...
Click to collapse
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle

kjcsg said:
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle
Click to expand...
Click to collapse
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon

Goose247 said:
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon
Click to expand...
Click to collapse
Unfortunately, my factory settings password entry only allows for numbers. I can't get the on screen kb to come up or the usb kb to type letters in the box.

Update: I got malaysk's rom up and running...However the touch screen is messed up (it receives input about an inch above where I tap). Then when I tried to reinstall the rom from settings with wiping it went back to the display off the left side of the screen. How I did it:
1) Install malaysk's rom from stock recovery (with "Check parameter..., E:Check failed at 0x4, Update Parameter..., Check parameter after update..." the first install part, and "E:1 parse errors" and "handle script error! ignore..." the second part)
2) Boot loop - USB kb hit ALT PRTSCR I until I get the recovery sliver on the left hand side of the screeen
3) This time I tried using the second option instead of third installing the pumpkin stock update.img and it boot looped the pumpkin boot animation
4) Reinstalled malaysk's rom using the pumpkin recovery again
5) Malaysk's rom booted up! Touch screen messed up but it booted up!
Now I'm redoing that and going to try to install the kld mcu.img's to get the touch screen working right along with the buttons and volume knob. Still no usb recognition on my pc tho sadly.

I'm trying to install the mcu img from recovery but even with the rom positioned correctly on screen the recovery is still a sliver on the left of my screen. Can someone tell me the options in recovery so I know what I'm selecting please and thank you.
Sent from my VS990 using XDA-Developers mobile app

Nvm, I found a picture online. Next question, does anyone know how to copy the mcu partition or modify mcu data? The pumpkin mcu is in bin format n the converter I have won't convert it to img because it's too big.
Sent from my VS990 using XDA-Developers mobile app

If you get it to work, please let us know here.

Well, from what I can tell, it won't work because the custom roms have different kernels causing the display to be off the screen, at least for the fused roms. I tried a non fused malaysk rom and it wasn't off the screen, but I couldn't get the mcu to work. To get the mcu to work you could try to copy the stock settings mcu update, I tried but it's over my head once I got it decompiled and tried following the code to see what it actually does when you click mcu update in the pumpkin settings. Because of kernels and reverse engineering the pumpkin mcu update are over my head for my current knowledge and understanding, I'm trying to get a refund for this unit and going to buy a joying unit since joying actively works with us, the modding community, giving us stock firmware and root and kernels and help and thus we get a much better unit and rom in the end! Joying understands the meaning of android and how it's supposed to be open source and collaborative for the community to work together to make the best goodies possible. I mean, for crying out loud, Google has gotten many of their features that they've put into their kk, lp, mm releases from us, from modders creating what they want and tuning android to it's best!!! Pumpkin, and as a related note, Verizon sucks!!! Alright, rant complete, any questions, let me know!
-kjcsg

SW3 may need partition repair

My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.

golfnut22 said:
My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.
Click to expand...
Click to collapse

Same issue here
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.

baronimus said:
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.
Click to expand...
Click to collapse
Yes, I still have not been able to update to MM. Mine does connect to my smartphone with no issues. Although, the last time I did have an issue where it kept cycling and trying to connect to the internet via the phone. So, I went thru the steps again to basically get it back to the ROM you noted above and it is working. One thing I have noticed once I get it going with the steps I used, I cannot boot to twrp via fastboot. I have to go to XC and let it try and repair, which it says it does, but doesn't. I get the 4 dots again, and from there when I fastboot, I can fastboot twrp.img and adb push stuff to install. However, I have noticed that I need to use the flash commands and flash the .simg file noted in my thread in order for the above ROM to actually work. I also noticed when that ROM is installing, it does mention working on partitions...so, it must be doing something to some of them.
I would love to be able to get MM working on this, but I think I have run out of ROMs to try. I'm probably not sequencing something right, but have not clue as to what is wrong. I am an newbie at this.
If you get MM to finally update on your watch, it would be much appreciated if you would share your detailed process in achieving that success.

T807A Recovery Help

Hi there,
I recently purchased a Tab S 10.5 off of eBay from a seller that said they'd messed up a custom ROM installation and with a cursory amount of research I saw that it was possible to return it to factory and had no issue putting in the leg work to get it done. However, I'm finding that my own knowledge of rooting and custom ROMs isn't sufficient for this situation now that I've gotten stuck into it. The tablet shows the Tab S logo and then immediately displays a message that says the software isn't official ATT and to return to a store for assistance. When I try to boot into the recovery menu I'm met with a screen that has a large android and says, 'Downloading...' and I can't get any further there either.
I've tried flashing recovery files with Odin but they have all failed and have also tried the Turkish image and it just sits at, '<ID:0/004> SetupConnection.." and doesn't initialize.
I've also gotten a, 'NAND StartWrite FAIL!!' notice as well.
I got the thing for a steal and would love it if it were possible to return it to factory and was just curious what kind of options I had at this point. Are there any program alternatives to Odin or different recovery files to use mayhaps?
I'm wondering if buying a new logic board would fix the issue at this point but, wanted to double check that it wouldn't cause any differing problems than the issue I'm experiencing now.
Edit: Odin finally got passed the, 'SetupConnection' line for the Turkish image and displayed this next: '<ID:0/004> Can't open the serial(COM) port.' - This is the first time it's displayed this message and I'm not sure what to do about this either.

T807a firmware isn't available afaik.

ashyx said:
T807a firmware isn't available afaik.
Click to expand...
Click to collapse
Are there any other versions of the firmware that would work instead?
Regarding the rest of my questions, I'm really just interested at this point if replacing the logic board would fix the issue. If anyone has tried that at least.