Develop Bugs

[Q] Why does everything go wrong when I try to do it?

Okay, this might not be the place to get some divine intervention to start (or stop) happening, but I'm really starting to get a nervous breakdown and I desperately need some help. I'm going to tell you my story, because it's my last resort before throwing this phone in a fire and never buy anything Samsung related ever.
So the phone came out of the box and for some magic reason I got the bootloader unlocked and phone rooted. It all started with installing CWM I think. This stopped my phone from taking OTA updates. Of course I could have known, but for some reason I installed CWM. I don't know why! I regret it, I don't even want a different ROM installed, I thought it was necessary to root the phone. So when I got the OTA, at first I was like YEAH YEAH, but then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. It was 2 in the morning and I had to get up early to go to Dublin for two weeks. This was really not the time...
So after trying a few times of getting the OTA update message again and failing every time I got it, I started searching. Yes, CWM is installed so you can't OTA they all said. Nice, now I hate on the back laying androids AND CWM. Of course the one to hate is me, but I already hate myself so that's no use. Anyway I used the Galaxy Nexus Toolkit 5.6 to put back stock recovery. Now I had to wait a few weeks again before the update turned up again... By this time the phone started to be REALLY slow when scrolling through the home screen(s). It also is empty before the day is done, but I don't know if that's because of the phone being f'ed up or because I'm too demanding.
Anyway, back to the story. Finally the update came about a week ago, and again I was like YEAH YEAH! But then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. To make things more fun it did a reset of my Go Launcher, 7 screens of widgets and autistic arranged shortcuts gone... Of course I wanted to try again, so this morning the OTA came again and had the same result. By now I killed quite a few, so this has to end, but don't worry there is more torment ahead.
I can't figure out what is wrong now, so I thought, f~ this s~, this phone deserves a full undress and back to the womb operation. So installing all Galaxy Nexus Toolkit v6.0 stuff and drivers. Connect phone, start toolkit, choose 3 (GSM 4.0.2. build ICL53F), phone turns up in main menu, try to put back recovery, -waiting for device-...
It stopped... Or it didn't really stop, it just stood there saying, -waiting for device-... So again a few innocent people died. Tried a different choice, (relock bootloader, just to give the phone a good beating) -waiting for device-...
I raged, pulled my hair, again killed a few, silently cried in a corner and finally started typing this eulogy...
Please kind sirs and madams, help me get this phone back to stock 4.0.4, accepting OTA, bootloader unlocked and rooted, I'm really desperate...

Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium

How do you proceed?
First you need the SDK for you system
http://developer.android.com/sdk/index.html
After this you have to start the SDK manager and install "Android SDK Tools" and "Android SDK Plattform-tools" if you are using Windows you have to install USB drivers too. You could find this under the point "Extras".
After that you have to download the factory image to clean your device, once.
(Notice your SD-Card gets wiped)
https://developers.google.com/android/nexus/images
Look for right version, which fits to your device.
Now you have to bring your telefon into the bootloader by pressing all 3 buttons at the same time Volume+/Volume-/Power. After this you have to unlock your bootloader if you don't already done this.
Now plug in your phone into your computer an go into the unpacked folder from your factory image. There would be an file called flash-all. You have to run this file. Now your phone is flashed with stock rom, stock kernel newest baseband and stock recovery. Now you get ota updates from google. After this you should look for an howto root your phone in the developer section. You don't have to install clockworkmod recovery for rooting. But clockworkmod isn't change the ota. You get OTA with cwm.
Hope i understand your problem an you could understand my bad english. But i want to help. If some questions ask here into the thread.
regards

theSlack said:
Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm out of the house a lot, leaving for Brussels in a couple of hours. I don't want the hassle anymore. I just want to be able to leave the house to go to another hotel and update OTA. I don't have time for all this flashing stuff.
Sent from my Galaxy Nexus using XDA

When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.

If you want to head back to stock ROM, then one of the ways to do it would be to install Android SDK & then follow the instructions from Google developers site.
Else you can try using the Galaxy Nexus Toolkit to do this for you. I think the latest version is 5.7.
Android SDK - http://developer.android.com/sdk/installing.html
Android Images - https://developers.google.com/android/nexus/images#yakju
Galaxy Nexus Toolkit - http://windows.podnova.com/software/5996358.htm

smsmad said:
When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.
Click to expand...
Click to collapse
Ah yes, I now see where I went wrong with the toolkit, I didn't put the phone in fastboot. Stupid...
How is the stock recovery supposed to look like? After putting back stock recovery with the GN Toolkit, I press 'vol+/vol-/power' and choose recovery. It then displays the belly up android with exclamation mark. Is that the way it should be? Am I doin' it wrong?

yes it is the stock recovery. But you dont need it. Flashing everything into fastboot mode(bootloader)

So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?

If you flashed the latest Factory-Image there is no OTA out there. It is the newest version of ICS for your Device.
Maybe i don't understand what you mean with failing OTA. Could you explain it a little bit more?

As I said in the long story, I'm currently 4.0.2. and every time when my phone says, "You have update 4.0.4. standing by, please reboot" it fails.

i would prefer to flash the factory image and root your phone again
then you have a cleaned phone and OTA should work but you don't need them because you are at latest version.
https://developers.google.com/android/nexus/images
i wrote how you could flash it page before, remeber you wipe your data from sdcard

Lex_Michdeandroid said:
So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?
Click to expand...
Click to collapse
I don't know if I can answer why the OTA isn't working (I'll leave that to smarter men than I), but having an unlocked bootloader and root access won't stop the OTA. I had my phone in that state when the 4.0.4 update came out and all was fine, just had to run the command to get root of my phone again as OTA removes root.

Ah great! S~ has just hit the fan, it's bootlooping after trying option 8 (flash stock rom from google). Oh I really am going to kill myself sooner or later...
Edit: not killing myself yet, just had to pull the battery... Let's see what I f~ up next...

Very strange you problems i don't know the Toolkit and don't know how it flash the stock rom. But i could imagin that it only flash rom and not the other things like recovery and so on.
Try out the hard way without toolkit and use sdk and included batch file into the factory image. it is the clean way and you see whats done.

Ok, I now rebooted the phone after option 8 in the toolkit and it seems I'm running 4.0.4. I have to go to Brussels now for two weeks, but I'll try to post some screenshots later. I'll also be back to thank all of you for holding my hand, I just don't have the time right now. Of course this won't be my last problem (I still have a TF101 that needs some RMA action), but I hope I won't be needing too much time consuming support anymore.

Just got in the hotel, and unable to use my phone in Belgium. No available network... Wifi works, 2G/3G works in The Netherlands, 2G/3G unavailable in Belgium...
Screenshot of my device: http://oi46.tinypic.com/34xp89y.jpg
Sent from my Galaxy Nexus using XDA

Just tried my SIM in a different phone, problems are with my network. Phone works with different SIM, so false alarm.
Sent from my Galaxy Nexus using XDA

If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium

msedek said:
If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I rather eat my own shhhhh... shorts than buy something with an apple on it. With the help of you guys it always works out fine, it just takes a life or two.
Sent from my Transformer TF101 using XDA

Did Google not fix the bluetooth issue with 4.2.1?

Whenever I listen to music or podcasts via bluetooth and anything begins to download my bluetooth audio stream begins to stutter badly to the point where I can't comprehend what is coming through.

legato89 said:
Whenever I listen to music or podcasts via bluetooth and anything begins to download my bluetooth audio stream begins to stutter badly to the point where I can't comprehend what is coming through.
Click to expand...
Click to collapse
I see the same issue with nexus 7 but not with gnex.
Sent from my Galaxy Nexus using xda app-developers app

anil76 said:
I see the same issue with nexus 7 but not with gnex.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
After the update today, the bluetooth problem persists. I still can turn it on at all.

gamboaecr said:
After the update today, the bluetooth problem persists. I still can turn it on at all.
Click to expand...
Click to collapse
Same here. It worked for me on 4.2 but 4.2.1 doesn't allow me to turn on BT

I had broken Bluetooth when I upgraded from 4.1 to 4.2. To fix it I had do a clean install of the stock ROM via fast boot (NOTE: it wipes everything).
Instructions to do that are floating around in here but if you can't find them let me know.
Adam.
Sent from my Galaxy Nexus using xda app-developers app

I just did a clean install of 4.2 via fastboot using the image from Googles site, then upgraded OTA to 4.2.1

If you are in 4.2.1 and your Bluetooth does not work here is what worked for me: IT WORKS ONLY IF YOU HAVE UNLOCKED BOOTLOADER AND FASTBOOT SET ON YOUR PC. Download the 4.2.1 factory image from Google yakju or takju depends what you have. Then with 7zip extract ALL the compressed files until you have the file named system.img . Put the system.img file in your fastboot folder and boot your Gnex in bootloader. Then open a terminal in fastboot folder and flash the system image with the command : fastboot flash system system.img. After finishing, reboot and the Bluetooth should be fine. At least that worked for me. WARNING! YOU WILL LOSE ROOT AND OTA ROOTKEEPER BACKUP IF YOU DO THIS SO YOU HAVE TO REROOT. You will not lose data and all your settings doing this. For further explanations and guides about flashing refer to efrant's guides and threads.
Sent from my Galaxy Nexus using xda app-developers app

This fixed it for me (with HOWTO)
gialakias said:
If you are in 4.2.1 and your Bluetooth does not work here is what worked for me: IT WORKS ONLY IF YOU HAVE UNLOCKED BOOTLOADER AND FASTBOOT SET ON YOUR PC. Download the 4.2.1 factory image from Google yakju or takju depends what you have. Then with 7zip extract ALL the compressed files until you have the file named system.img . Put the system.img file in your fastboot folder and boot your Gnex in bootloader. Then open a terminal in fastboot folder and flash the system image with the command : fastboot flash system system.img. After finishing, reboot and the Bluetooth should be fine. At least that worked for me. WARNING! YOU WILL LOSE ROOT AND OTA ROOTKEEPER BACKUP IF YOU DO THIS SO YOU HAVE TO REROOT. You will not lose data and all your settings doing this. For further explanations and guides about flashing refer to efrant's guides and threads.
Click to expand...
Click to collapse
Awesome, this fixed it for me! Although your instructions were a bit to vague for a novice user like me, I managed to get the fix working on Windows with the Samsung Galaxy Nexus Toolkit V10.4.0 (www skipsoft net):
Download the Factory Image (https //developers google com/android/nexus/images)
Extract the tgz-file (with WinRAR or 7-zip.org)
In the extracted files, find a zip file (in my case image-yakju-jop40d.zip) and extract it.
Copy the system.img to the "put_img_files_to_flash_here" directory in the Samsung Galaxy Nexus Toolkit directory (in my case C:\Galaxy Nexus ToolKit\put_img_files_to_flash_here)
Now start the toolkit and select your device model (in my case "7. Android 4.2.1 (Build JOP40D)"
Choose option "11. Boot or Flash .img Files to Device [Fastboot Mode]"
Make sure "system.img" is displayed as available image file
Type "system.img" (or s* for short) to select it
Now follow the instructions. I can't redo them to document... They are clear. But give it some time, it will reboot once or twice and return to the Fastboot menu.
After flashing system.img, the device is unrooted, so you have to root again. You can do it your way, or use the toolkit option:
"4. Root or UnRoot your Device [Fastboot Mode]"
Then choose your favorite option. I chose option 1, because I already had it rooted before.
After these steps, you have your root back and a working bluetooth!
Thanks gialakias!

Confirmed
I also had bluetooth issues after reluctantly accepting the 4.2.1 ota. I lived without bluetooth for a while, but then finally had enough of the seeming joke google played. After considering aokp, for now the solution was reflashing the system.img from the google developers site. Works like a charm now, and i do not know why i had the issue in the first place. Again, a confirmation that a reflash of the system image via fastboot will fix your bluetooth.

Guys, this only applies to factory rom, right? Só I guess I can't do this using a custom rom...
I'm tempted to install Google factory image to see if it fixes the annoying issue...
Sent from my Galaxy Nexus using Tapatalk 2

I'd think a factory image on a custom rom would only cause problems. Perhaps you could unzip the custom rom zip, and find the system image to reflash. Either that, or its likely a known bug on that rom. What rom are you using, and is it a nightly?

Confirmed II
@ Gnoise: Thx: for your good How-To!
This solution works for me, too! :victory:

Hi All,
i have similar problem, but BT was working more or less fine. Only hang up few times. But main problem is that i could not use BT in my car any more. Phone connecting to car with no problem, and i could receive calls from anybody, but as only i try to call from phone, not from car HF system, i get problems. While phone dialing, it happens in background mode, car audio system working, but as only recipient answer the call, Gnex turning his internal speaker, but not the car's HF system, like it was on 4.0.4 - 4.1.2. I flashed custom rom - the same problem, then i download and flash stock rom again, and nothing happens. Does it helps if i now reflesh system.img
p.s.
I asking because i gave Gnex to the warranty service (with all above mentioned explanation) and they gave me back Gnex with 4.0.4 and claim them for that. now i don't want to flash 4.2.1 until they response.
thank you

xoxoJI said:
Hi All,
i have similar problem, but BT was working more or less fine. Only hang up few times. But main problem is that i could not use BT in my car any more. Phone connecting to car with no problem, and i could receive calls from anybody, but as only i try to call from phone, not from car HF system, i get problems. While phone dialing, it happens in background mode, car audio system working, but as only recipient answer the call, Gnex turning his internal speaker, but not the car's HF system, like it was on 4.0.4 - 4.1.2. I flashed custom rom - the same problem, then i download and flash stock rom again, and nothing happens. Does it helps if i now reflesh system.img
thank you
Click to expand...
Click to collapse
I have the exact same issue with my car kit since 4.2.1 and am about to reflash my system.img... I'll let you know what the results are.

I actually re-imaged the system.img and it seems a bit better now... It still loses it's connection after a while and it could be after 2 minutes or after 60 minutes. Once the connection is flaky or broken, I cannot connect to my carkit anymore and the weird things is, no other phone can connect until i completely reset my carkit. It seems like it's messing up with either communication or whatever as it affects the way my carkit behaves afterwards.

fix
BtM909 said:
I actually re-imaged the system.img and it seems a bit better now... It still loses it's connection after a while and it could be after 2 minutes or after 60 minutes. Once the connection is flaky or broken, I cannot connect to my carkit anymore and the weird things is, no other phone can connect until i completely reset my carkit. It seems like it's messing up with either communication or whatever as it affects the way my carkit behaves afterwards.
Click to expand...
Click to collapse
Try the following. It worked to fix my crappy 4.2 Bluetooth sound quality. I did the manual install. Don't forget to change permissions.
http:// http://forum.xda-developers.com/showthread.php?p=38973705
---------- Post added at 03:55 AM ---------- Previous post was at 03:47 AM ----------
Try this. I had the same issue and this worked. Sound quality is great now.
http://forum.xda-developers.com/showthread.php?p=38973705

[Q] PDAnet Broke with 4.2.2

I have been using PDAnet for a couple of years now and never had a problem with the USB tether until I got an update a week or so ago and now it just gets stuck on "connecting to your phone....". I have been emailing the website for PDAnet and they seem to think the update screwed up a driver or something so I reinstalled everything on the phone and PC including the phone drivers. I preferr stock since I am too lazy and too old to keep up with the speed at which changes come so has anyone else had this problem? If so is there a fix? If theres no fix how hard is it to roll back this last update?
Tethering is important to me so all options are on the table even if I have to get back into rooting (though I preferr not to since you guys would get sick of my dumb questions).

Now this has me bothered. Ive never posted a question in here that didn't get some kind of assistance. That would ordinarily make me think my problem was unique except for I have found others with the same issue posting in the PDAnet and PDAnet plus feedback on the Play store.
I'll take any attempt at something I haven't tried from one of you smarter folks. I did a factory reset and it did nothing to help the problem.

Then complain to PDAnet as they probably need to update their app to work with 4.2.2

I have and they are being quite useless. I've just always had good luck here on XDA. Oh well maybe it isnt meant to be.
On another note does anyone have any suggestions on another app to try for tethering without root?

It's not hard to roll back, except that you'll have to unlock the device's bootloader, which wipes its data. Also, you'll have to find a factory image of 4.2.1 for your device, unless you roll back to 4.1.2, then get an update to 4.2.1 and figure out how to disable it for the 4.2.2 update. http://forum.xda-developers.com/showthread.php?t=1626895

When new versions of Android are released its normal for apps to require an update to work properly.
Koush has that no root usb tethering app. Can't remember the name, search the play store fore more apps from the Rom Manager dev and you will see it. Never used it but that's the one I know of.
Just about any custom firmware will have any tethering block or tracker disabled so you can just tether natively with a ROM.

Solved with jTether (root needed).

[Q] NOOB question about install old WiFi binaries to 4.3

Hi guys,
I got real damn headache since my GNex updated to 4.2, the Wifi tethering wipe out.
My PS Vita Couldn't connect it again over a year and no one could help me.
Now I wanna update to 4.3, but I need face this problem to let my Nexus work with correct WiFi.
I got 4.1.1 WiFi binaries from official, but what is the next step to overwrite it to 4.3 WiFi component?
I have try Google it, but I'm NOOB so much and no idea how to deal it...
Anyone could help me?
Thanks

There used to be a couple flashable zips floating around here (in kernel threads I believe...maybe tiny kernel) that will do what you seek.
Or just find those files in the system and overwrite them(take note of their permissions first so you can set them after overwriting the files)

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