Develop Bugs

Problem with alot of heros and no fix found USB/ADB

i have seen a problem with alot of heros and mine, to do with when it is connected to computer the drop down menu doesn't appear for sync or mount sd card. i have tried everything and nothing works, the only way you can connect to pc is through fastboot i've tried to -
- checked enable debugging
- update my recovery (thought it was a bad flash)
- reflash radio roms (thought it was a bad flash because someone else had this problem)
- updated hboot
- updated roms
- tried a few different usb cables
- drivers up to date and reinstalled ( mojos post) edit
anyone know what i could do to totally wipe my phone and start again? like original radio, rom, hboot, recovery. thanks in advance for help, i know quiet a few people could do with the help.
Solution found!
i dont know how it worked but it did,
- i installed a 2.1 eris rom which got things rolling on the phone
- installed the new htc sync that was taken from the legend in this post! http://forum.xda-developers.com/showthread.php?t=653351
- returned back to madaco 3.2 and works perfectly!

Try re-installing the drivers on your computer.

hmm maybe a stupid and too simple suggestion, but are you using any kind of task killer app ? try ignoring the pc sync process,
worked for me,
regards Wouter

Sparra said:
anyone know what i could do to totally wipe my phone and start again? like original radio, rom, hboot, recovery.
Click to expand...
Click to collapse
Install an RUU.
Regards,
Dave

Sparra, i'm having this problem also. Extended discussions have been happening on Modaco too.
foxmeister: you can't instal an RUU if you can't get the phone connected via USB

thanks people, going to try killing pc sync task dont think it will work though maybe will, yeah cant install ruu because phone doesnt connect to computer if you look at OP.

i had the same problem with my phone, had to send it in for repair as even after flashing the RUU update in fastboot i couldnt get anything

crashd said:
Sparra, i'm having this problem also. Extended discussions have been happening on Modaco too.
foxmeister: you can't instal an RUU if you can't get the phone connected via USB
Click to expand...
Click to collapse
there is a thing call micro sd card reader.
before ur phone crash do u did a nandroid backup? if u do pls try restore to the previous one =)

i would of done this but my original nandroid backup was lost!! , wonder if anyone elese has an original unbranded nandroid backup? would be good to try.

From what I can see, you CAN flash roms (updated recovery/hboot etc). ADB is working?
My guess is that you're using one of the Eclair based roms, in which usb-pc didn't work.
Try downloading mountusb from the market.

Yeah sorry i can flash roms through recovery, but no adb, computer doesn't recognise the phone.
I can connect in fastboot and all works to pc in that, I have modaco 3.1 and have used all versions of his Rom, problems started around version 2.5 or so.
Ive also tried mount usb! Might have to send back to htc!

If you put your phone into fastboot and connect, can you then run an RUU against it?
Regards,
Dave

Try another computer and see if it works

If your doing this at work, a lot of companies stop the USB ports from working.

Tried another computer and doing the ruu in fastboot, its my home pc so all usb ports work, ok pretty sure its the phones software and not a hardware problem! Thanks for suggestions!

Yeah. It's a software issue, as you can use the HEROIMG.ZIP method (search here or modaco) from the microSD when you hold vol.down + power. You also get normal fastboot. So no hardware is broken
But... Nothing I've seen mentioned can fix it. Flashing seems to do nothing. I guess there is some NAND somewhere that needs a wipe/reflash (probably the same NAND that stuff like the IMEI is stored in, but that's just a guess at the architecture). If we could find the NAND, we could compare a dump between a broken and working phone and see...

Yeah sorry i can flash roms through recovery, but no adb, computer doesn't recognise the phone.
Click to expand...
Click to collapse
it doesn't see it or says "no drivers found"
which os are you using
i can charge and usb mount even without drivers ...

It doesn't know what it is so doesn't install correctly. It's Windows 7 I don't have an issue with the druvers it worked fine before.

See http://android.modaco.com/content/h...om/300825/usb-device-not-recognized-solution/ on modaco. It's worth a shot, but bear in mind I think it will wipe /data. Might be hard to do a nandroid before though with no SD (as many people experience with this issue)

Well, I have the same problem with my hero and I have original rom, my hero isn't even rooted...

help! accidently installed broken kernel!

hey guys, i really really need some help here please. i finally decided to root my phone, that went fine, then i decided to look for a kernel so i could overclock my desire z, i downloaded kernel manager, and installed Flippy125's 1.9ghz froyo kernel (which i didnt know was broken because it didnt say so on kernel manager)...after that kernel was installed, i now cant connect to wifi, cant get a mobile network signal, and cant connect to the pc at all (usb disk drive, usb debugging, internet pass through) i cant get any sort of internet what so ever to try going to kernel manager and getting a new one can you help me out at all on how to reset it to a factory kernel or anything that can atleast get my phone working again? thanks guys

Did you create a backup in recovery before you upgraded the kernel? If so wipe and the restore. If not try to find a stock rom and flash back to stock. Youll lose all your apps however.
Sent from my HTC Vision using xda app-developers app

kryptonite666 said:
hey guys, i really really need some help here please. i finally decided to root my phone, that went fine, then i decided to look for a kernel so i could overclock my desire z, i downloaded kernel manager, and installed Flippy125's 1.9ghz froyo kernel (which i didnt know was broken because it didnt say so on kernel manager)...after that kernel was installed, i now cant connect to wifi, cant get a mobile network signal, and cant connect to the pc at all (usb disk drive, usb debugging, internet pass through) i cant get any sort of internet what so ever to try going to kernel manager and getting a new one can you help me out at all on how to reset it to a factory kernel or anything that can atleast get my phone working again? thanks guys
Click to expand...
Click to collapse
Try flashing a different ROM over it.

blackknightavalon said:
Try flashing a different ROM over it.
Click to expand...
Click to collapse
is it possible to do it through the clockwork recovery console? i was trying to get into it for like an hour then my phone randomly restarted into it while i was typing that first post...lol
EDIT: okay guys, i found some MIUI rom on my sd card, installed that, and everything seems to work now, but seems like it'll be a major chore to get used to, is there any way i can use the original HTC UI? or do i have to use different ROM's from now on?

kryptonite666 said:
is it possible to do it through the clockwork recovery console? i was trying to get into it for like an hour then my phone randomly restarted into it while i was typing that first post...lol
EDIT: okay guys, i found some MIUI rom on my sd card, installed that, and everything seems to work now, but seems like it'll be a major chore to get used to, is there any way i can use the original HTC UI? or do i have to use different ROM's from now on?
Click to expand...
Click to collapse
Don't flash that kernel. ROMs have their built-in kernels that are already fast (1500Mz when the phone was originally rated 800Mz is impressive). Try different ROMs out.
Sent from Spaceball One.

Have a look at virtuous roms, those are (mostly) all sense based
-Nipqer

okay guys, im pretty sure i got it all figured out now, that MIUI rom made everything work, and from there i've been looking at different rom's, so far i keep going back to the MIUI one though just because im used to it the most so far xD, AND the fact i hate restoring my stuff every time i try a new rom..so..yeah, but thanks for ur help guys i can see this will be the forum i'll be using for alot of my questions/help requests.

[TUT][CDMA]ROM randomly rebooting? Here are some fixes! (BACK IN BUSINESS!!! :D)

NOTE: This one's a big one if you can't tell! Everyone give a round of applause to simonsimons34 for tracking down the issue. What does this mean? Well, there may not be a need to ever downgrade using the RUU. If you go here (you really can't miss that big, bolded "here"), you will see that he determined the issue is caused by:
a bad battery driver function in the kernel
Click to expand...
Click to collapse
He also took the liberty of building a kernel compatible with 4.2 and putting in a commit for fixing the kernel to work with the newer radio at GitHub. Any ROM builders who see this, please do check it out. As far as everything goes, I haven't personally tested it but I do always encourage people to try it out. Simon has been a great supporter and kernel builder for our device so I have faith that he hath found the Holy Grail. 'Course my thread will have no more existential purpose, BUT it is a great resource so as it is, I will leave it up for the general perusal of the community. Have a great week everybody and I look forward to a new flood of development.
Exciting news y'all! This thread has been stickied! [Hopefully] this will allow continued support and growth of the thread. My personal philosophy is that anything I post shouldn't be locked down to what I know or believe in, so I encourage any reader to put forth their input. What does that mean? It means that if you have a suggestion, by all means inbox me your thoughts. I'm open to continual development of this tutorial through community teamwork. Have a good day everyone!
-------------------------------------------------------------------------------------------------------
Here are some common reasons why your phone will randomly reboot (bootloop). You should only use an RUU (the methods below the "=" signs) if NOTHING ELSE WORKS (because the RUU does a factory wipe of the phone).
Common Problems:
I switched from another ROM and now my phone keeps rebooting...
There are several factors in play here. The commonly accepted fix is backing up your data and doing a full wipe (cache, dalvik cache, system, data) followed by reflashing your ROM.
I upgraded my ROM from blah blah version to blah blah version (ex. 4.0.x to 4.1.x)...
This is because your old Ice Cream Sandwich system stuff may not be compatible with JellyBean (in the case of the example). Wipe system and the caches (dalvik & cache) followed by reflashing your ROM.
I upgraded my ROM (within the same version) and it keeps rebooting...
Every time I upgrade my ROM, I wipe cache. If something funky happens, just wipe system and reflash your ROM.
I flashed a ROM and it won't boot at all...
Either you flashed a ROM for a different device, you flashed a kernel for another device, OR you didn't flash a kernel at all. Make sure everything is for your phone (the HTC One V on Virgin Mobile is the CDMA version known as "PrimoC" whereas the GSM version is the "PrimoU").
=============================
NOTE: This guide is for the One V!
I know the feeling! You're all excited because you just unlocked your One V's bootloader, flashed a recovery, and flashed a steamin' hot new ROM. You boot up for the first time and get ecstatic, the tension building as you put in your Gmail info. You finish the start up but OH NO!!! Your phone reboots! You blame yourself... you blame your cat... you blame your wife... you blame the war in the Middle East. You think, I must've done something wrong! Stupid, stupid, stupid! Don't fret! Take my experience with this quite seriously (despite the jokes). For 2 weeks, I retraced my steps and tried EVERYTHING! I thought it was just the ROM's problem, so I flashed one after another to the same end. Finally, I decided to post a new thread asking for help. Nothing became of the first thread, so I posted a second one. To my great relief, along trotted Curiousn00b. After shoving me in the correct direction, I figured out the rest. A big thanks by the way, Curiousn00b! The following is the method that I used to get my phone to finally run a ROM. Also, a thanks to CafeKampuchia for the quoted directions below.
A few things to make sure you have:
Windows (with Administrator's priveleges)
Fastboot installed and working
Your phone (duh!)
A USB cable
Time and patience
The following quote is from CafeKampuchia's thread over here.
NOTE ABOUT THE FOLLOWING PARAGRAPH: jmztaylor's site is now legally able to host the RUUs again so the download link is right here*
In support of jmztaylor and all of his work for this device, I have decided to also include his website in this thread... *here is the download directory for the HTC One (Primo) device RUUs. I'm not sure if this bug effects other Primo devices, so this especially pertains to the PrimoC (HTC One V CDMA). Thanks jmz for the tip!
Solution #1
CafeKampuchia said:
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thus far you should have the stock recovery back and be bootlocked again. Now, back in fastboot mode, you should already be connected to your computer via USB (if you disconnected, just reconnect it and wait for "FASTBOOT" to change to "FASTBOOT USB")
Run this command:
Code:
fastboot oem rebootRUU
Next, start up the RUU program again and let it run through without interruption. After this process is done, the phone should boot up to the stock ROM. Let it do its thing, but this time don't do the OTA update. From here, just unlock the bootloader again, install your recovery of choice, and install your ROM of choice or reroot the stock ROM (I know some want to keep it stock).
As also pointed out by RoyalYeo, you can let HBOOT take care of the problem:
Solution #2
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse
My personal solution (Solution #1) is the more technical side of things and also exposes you to the nitty-gritty. Having said this, #1 is quite touchy because if you do something wrong, there is a good chance that you could... well uh, brick your phone to be quite honest. On the other hand, #1 requires no SD card (given the event that your SD card won't mount, your SD reader is broken, or you just plain don't have an SD card). Ultimately, the choice is up to you.

y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665

cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Won't work if the ota is already applied from the factory.

cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
You need to downgrade your radios or your guide will be useless no matter what, i followed this post i found on android forums and it worked
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse

robaho said:
Won't work if the ota is already applied from the factory.
Click to expand...
Click to collapse
Or if you applied the OTA via the popup window saying, "Blah, blah, blah, new update available."

Thank you so much for this. I will try it when I get home. Ever since I applied that OTA battery update, I haven't been able to successfully run any other ROM that I have tried. Hopefully this will be the solution that I have been looking for.
Just out of curiosity though, I have a Nandroid backup of before I applied the OTA Rom. If I restore that backup, would that do the same thing as you provide here, or would I definitely have to go through this process?

Won't work. The radio partition cannot be backed up/restored unless you have an s-off device.

Why not point to htcruu.com no premium acct necessary or wait times
Sent from my One X using xda premium

Moved to General section.

I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.

mastertr said:
I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.
Click to expand...
Click to collapse
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...

mastertr said:
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...
Click to expand...
Click to collapse
Did you relock the bootloader before or after flashing PK76IMG.zip? This does make a difference. My suggestion is just to go back through and try again following everything to a tee. Doesn't always work the first time.

I went with your first solution this time and followed the directions step-by-step and it was a success. I am now running AOKP 10 without any boot loop. Thanks!

Bump

It worked thank you
thanks man followed your guide and boom everything went just fine.
1st i had 1 minute problem. now i dont have any.
i confirm that anybody having 1 minute problem can solve it with this tutorial:laugh::laugh::laugh::laugh::laugh:
thanks

Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA

BobbaLouie said:
Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA
Click to expand...
Click to collapse
check ur version
settigs->about >software version

Is the Sprint RUU the one that works on Virgin Mobile?

Euler MD said:
Is the Sprint RUU the one that works on Virgin Mobile?
Click to expand...
Click to collapse
Yes
Sent from my One V using xda app-developers app

Thankyou for this guide. Even though I followed the steps, it didn't work. Maybe it was just my luck but I'll try again soon.

[Q] Need advice with installing stock ROM

Hey Guys,
I know there are a lot of threads like these, but unfortunately most of them are not exactly up to date, and when you are frustrated with failure that isn't helping either.
So here's the thing, I've tried installing custom recovery and ROM. I used HOX toolkit i've found here, the author suggested using TWRP. It installed okay but i wasn't able to use it because the touchscreen didn't work at all. So I've tried different tutorial on onexroot.com this time with cwm. Again everything installed correctly. I went on to install custom rom (cyanogenmod 10.2) installed it, everything was ok, rebooted my device, the cyanogenmod spinning logo pops up saying something about apps and stuff, then it was stuck for more than 5-7 minutes which pretty much means it doesn't work. So I've tried wiping stuff as said in the tutorial which didn't seem to change anything... Now I'm stuck and have no idea what to do since I haven't backed up old rom (is something like that even possible)
Anyway how should i proceed now?
Is there a way to get back to stock everything or did i just destroyed my hox?
I do realize that this is most probably my fault and i feel really ashamed.
So any working links/tutorials/anything are most welcome
Thanks

Subalee said:
Hey Guys,
I know there are a lot of threads like these, but unfortunately most of them are not exactly up to date, and when you are frustrated with failure that isn't helping either.
So here's the thing, I've tried installing custom recovery and ROM. I used HOX toolkit i've found here, the author suggested using TWRP. It installed okay but i wasn't able to use it because the touchscreen didn't work at all. So I've tried different tutorial on onexroot.com this time with cwm. Again everything installed correctly. I went on to install custom rom (cyanogenmod 10.2) installed it, everything was ok, rebooted my device, the cyanogenmod spinning logo pops up saying something about apps and stuff, then it was stuck for more than 5-7 minutes which pretty much means it doesn't work. So I've tried wiping stuff as said in the tutorial which didn't seem to change anything... Now I'm stuck and have no idea what to do since I haven't backed up old rom (is something like that even possible)
Anyway how should i proceed now?
Is there a way to get back to stock everything or did i just destroyed my hox?
I do realize that this is most probably my fault and i feel really ashamed.
So any working links/tutorials/anything are most welcome
Thanks
Click to expand...
Click to collapse
OK... First of all PLEASE tell me that you have made a nandroid backup before messing around !?!
If you did than it's all fine...
if not... well, we'll come to that...
So, first of you need to get into the bootloader, and flash the boot.img... Get the file by extracting the cyanogen.zip to your PC...
Now move it to the data folder in the all-in-one toolkit, shft+right click there on empty space and click open with command propmt...
now run:
fastboot flash boot boot.img
fastboot reboot
Now you should be able to boot into cyanogenmod...
Now if you want to go to stock, you can just restore your nandroid and flash the stock boot.img using mentions commands, but if not you'll have to ether find an ruu or find an nandroid backup that someone uploaded with your base...
Now, just believe me this...
The BEST recovery is CWM Touch 5.8.4.0 as of today...
So use it...

1 : he already said he hasn't got a backup
2: cwm 5.8 is not the BEST recovery because it's outdated ! Twrp (repacked or not) or philz touch recovery are way more advanced.....
Just saying

And can I just add that the guides are NOT outdated. They work if you follow instructions exactly
Put the kettle on

gonna try desmonds way.
I didn't back up anything
I didn't mean quides on unlocking your device are outdated, by all means they are great for community created guides. What I meant by that that trying the reverse process is a little bit of a struggle

Subalee said:
gonna try desmonds way.
I didn't back up anything
I didn't mean quides on unlocking your device are outdated, by all means they are great for community created guides. What I meant by that that trying the reverse process is a little bit of a struggle
Click to expand...
Click to collapse
Ok, but when you execute the command "fastboot flash boot boot.img" you should type "fastboot erase cache" before and after that command
Put the kettle on

Thank you so much! All of you! It works! Faith in humanity, people on the internet, myself RESTORED!
here's what i did

Okay, not everything really works.... I'm missing playstore, how should i proceed now? :/
nevermind, just found out why
Okay another problem :/ I wanted to installed google apps, however usb driver doesn't work anymore, why is this? i can see HTC in device manager but i do not have appropriate drivers

Because in cynogenmod UBS debugging and adb are disabled by default... Tap the build number a couple of times to unlock developer options and enable them

oorpher 3166
desmond1303 said:
Because in cynogenmod UBS debugging and adb are disabled by default... Tap the build number a couple of times to unlock developer options and enable them
Click to expand...
Click to collapse
Okay that explains it, but i have no idea what the build number is. Where is it located?

Subalee said:
Okay that explains it, but i have no idea what the build number is. Where is it located?
Click to expand...
Click to collapse
Well you go into settings > about > there you will find stuff like android version... if you tap on that a few times you get the jelly beans to play around with, and so if you tap a few times on ether build number or baseband version you will get a toast notification that you are now a developer... now go back to settings and you'll see a new entry at the bottom, called developer options... go in there and turn them on... then fins adb and usb debugging and turn them both on.

desmond1303 said:
Well you go into settings > about > there you will find stuff like android version... if you tap on that a few times you get the jelly beans to play around with, and so if you tap a few times on ether build number or baseband version you will get a toast notification that you are now a developer... now go back to settings and you'll see a new entry at the bottom, called developer options... go in there and turn them on... then fins adb and usb debugging and turn them both on.
Click to expand...
Click to collapse
Enabled it, but still unable to open phones storage in computer.... Including picture of my device manager
I turn on usb storage on my phone but that doesn't change anything

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