Develop Bugs

Roommate wants to brick his phone

Yesterday my roommate decided that he wanted to join the party and root his Evo after seeing the pure unfiltered awesomeness of mine, but he ran into a problem. While trying to flash a custom recovery he kept getting the an error message about a "bad block 000x0000010000" or something similar. So, unless I'm way off, I told him he must have bad handset hardware.
Well, he decided to take the phone back to the Sprint store and see if he could talk them into swapping one out due to the defect. They said no, because after running whatever tests it is that they do that there wasn't a reproducible problem. The sales person did say though, that if his phone were to "unexpectedly crash" then he would easily just replace it.
So... my question at this point, is there a way to get around this "bad block" error, or is there a way to brick the phone without it being obvious that anything voiding the warranty was done? I searched the forums about this error, but everything if found said they eventually got it to work by trying different recoveries, or they swapped out the phone. We have a tried a few different recoveries, but none are working and we have tried more times than I can count.

Its fraud. Nobody on this forum is likely to help you since its BS claims like that which caused the deductible to raide to $100.

I understand how one could see it that way, but the way my roommate sees it is that he was sold a bad device. I don't know, I'm not here to argue semantics nor ethics, I'm just wondering if anyone has some advice for the guy. We would prefer to just keep the phone if we can manage to get the device working the way we would like.

Intensentropy said:
Yesterday my roommate decided that he wanted to join the party and root his Evo after seeing the pure unfiltered awesomeness of mine, but he ran into a problem. While trying to flash a custom recovery he kept getting the an error message about a "bad block 000x0000010000" or something similar. So, unless I'm way off, I told him he must have bad handset hardware.
Well, he decided to take the phone back to the Sprint store and see if he could talk them into swapping one out due to the defect. They said no, because after running whatever tests it is that they do that there wasn't a reproducible problem. The sales person did say though, that if his phone were to "unexpectedly crash" then he would easily just replace it.
So... my question at this point, is there a way to get around this "bad block" error, or is there a way to brick the phone without it being obvious that anything voiding the warranty was done? I searched the forums about this error, but everything if found said they eventually got it to work by trying different recoveries, or they swapped out the phone. We have a tried a few different recoveries, but none are working and we have tried more times than I can count.
Click to expand...
Click to collapse
Have you tried flashing eng build and flashing recovery from bootloader?

we flashed the engineering build through the bootloader but not the recovery. The method we used to flash recovery was though adb. we'll take a look and see if we have any better luck. my roommate said that he read something about using fastboot, but I'm not sure about that. We'll give it a try.

Just be careful not to run out of power "accidentally" while flashing a new radio... that could have devastating effects on phone usage... "Hint... Hint..."
though i highly doubt that your friends problem lies with the phone itself... should try to redo all the steps... and if you can repeat the error post more details on here...

wrx4memp said:
Just be careful not to run out of power "accidentally" while flashing a new radio... that could have devastating effects on phone usage... "Hint... Hint..."
though i highly doubt that your friends problem lies with the phone itself... should try to redo all the steps... and if you can repeat the error post more details on here...
Click to expand...
Click to collapse
lol, we are running though the whole process again right now. Thanks for the suggestion, though we are trying to avoid such a devastating event.

Well... Thanks for all your suggestions! We got everything to finally work though. I don't know why I didn't think of it earlier but we tried the simple root method and let the automated process handle all the labor. We got the exact same error with this method, but the program recognized the issue and moved the recovery to a section with no bad blocks. Doing it manually didn't allow for us to chose a different section to write to. Donation can be expected from my roommate! Thanks for the great application!

[Q] HOX reboots when app starts

Hello,
I've done an update while my HOX was charging, it took around 2 hours but at the end phone turned on. BUT since then when I try to launch almost every app, phone restarts. Even when I try to change my ringtone phone does the same. I did a "Factory Reset" several times, it didn't help, I uninstalled all the apps, which I downloaded, made a factory reset, didn't help. I entered safe mode, but still have the same problem. So now I can't enjoy the phone, that is very pity. Software info: Android 4.0.3, HTC Sense 4.0, Software number 1.28.401.9.
I'm a rookie in whole android issue, so I'd be very thankful for your help.
I contacted an HTC service but they couldn't help me, they suggested to send it to a lab. Is there any other solution?
Thank you in advance

bagrooove said:
Hello,
I've done an update while my HOX was charging, it took around 2 hours but at the end phone turned on. BUT since then when I try to launch almost every app, phone restarts. Even when I try to change my ringtone phone does the same. I did a "Factory Reset" several times, it didn't help, I uninstalled all the apps, which I downloaded, made a factory reset, didn't help. I entered safe mode, but still have the same problem. So now I can't enjoy the phone, that is very pity. Software info: Android 4.0.3, HTC Sense 4.0, Software number 1.28.401.9.
I'm a rookie in whole android issue, so I'd be very thankful for your help.
I contacted an HTC service but they couldn't help me, they suggested to send it to a lab. Is there any other solution?
Thank you in advance
Click to expand...
Click to collapse
Send it in to the lab.

The problem is that, I live in Israel and HTC doesn't have lab here. They suggested me to send it to Greece, I'm not too happy with this option. Maybe I can downgrade the current software? Or any other possibility.
Thanks,

bagrooove said:
The problem is that, I live in Israel and HTC doesn't have lab here. They suggested me to send it to Greece, I'm not too happy with this option. Maybe I can downgrade the current software? Or any other possibility.
Thanks,
Click to expand...
Click to collapse
No, the only way you're going to Downgrade your software or Just install a different ROM, is by rooting it.
This Voids your warranty, so do your research first.
If you're not comfortable with that you might aswell just send it to HTC.

Can you, please, give me some references about how am I doing the rooting?
Thanks,

You could download the RUU for your current software version and try running that to reinstall it; the phone is not meant to be charging while you install an OTA update so it's possible something hasn't copied correctly because of that.

hopscotchjunkie said:
You could download the RUU for your current software version and try running that to reinstall it; the phone is not meant to be charging while you install an OTA update so it's possible something hasn't copied correctly because of that.
Click to expand...
Click to collapse
Where can I find it? And also some installation's steps could help...
Thanks

bagrooove said:
Where can I find it? And also some installation's steps could help...
Thanks
Click to expand...
Click to collapse
You can find all released RUUs here (the links in the first post are pretty slow, but there are faster mirrors scattered throughout the thread). Make sure you download the one that matches your version.
Installation steps? Plug your phone into your computer via USB and run the .exe file. It'll take you through everything else.

Thank you very much. I hope it'll help...

[Q] Nitro HD external speaker stopped working after failed root.

Got my phone right after the last update and I went to root it with superoneclick and it hasn't had sound now for about 3 months. Wondering if anyone knows what I can do. I've tried just about everything I could think of but for some reason my phone just doesn't seem like it interacts with the pc right.
halp.
Thanks in advance.

you said a failed root, so if it's still stock you might be able to bring it in.
depending on who your with they will take your phone, send it in, upgrade the firmware (or re-flash it if it is the newest) and send it back to you for free.
i had mine rooted and with a custom firmware on it, and bell still took it and flashed V11a for me.
if you plug headphones in do they work?
hope you get everything sorted out

Thanks, I'll see what I can do, although as I have service with AT&T I can only expect a long harrowing process with nil results. :/
Yes, when I plug in headphones/auxiliary cords it's fine.

lol yea...it only took 7 days to get my phone back...
it's interesting that your headphones work, and it wouldn't be physical damage, because you said it happened after trying to root it.
i would re-try to root it, or downgrade/upgrade your firmware to see if that works before sending it in (if you do that)
sorry i can't be of much help, good luck though

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

Phone stuck in "Download mode" after official Pie OTA update!

Hey good people.
Yesterday i was excited to see the notification for Pie update come up, so i quickly installed it on the phone. It finished, then asked me to reboot, so i did. But for some reason, the phone couldn't reboot properly, and ended up getting stuck in download mode.
Tried to get out of it using every combination, nothing worked. Then i decided, well, lets reinstall the firmware on it. If i could find any! Majority of links are misleading, don't work, yandex disk links didnt let me download anything. Tried like 3 different versions of OST, none of them worked, not even the patched one, not to mention the lack of firmware in the first place.
The only step forward i could make is getting the phone to show up in device manager, because it hasnt even showed up before.
i've never even fiddled with the device's software or anything, everything was 100% stock and untouched.
i'm seriously disappointed in nokia, already contacted the reseller who yet has to reply (i don't have much hope for that either).
Any kinda help would be highly appreciated.

gabika1941 said:
Hey good people.
Yesterday i was excited to see the notification for Pie update come up, so i quickly installed it on the phone. It finished, then asked me to reboot, so i did. But for some reason, the phone couldn't reboot properly, and ended up getting stuck in download mode.
Tried to get out of it using every combination, nothing worked. Then i decided, well, lets reinstall the firmware on it. If i could find any! Majority of links are misleading, don't work, yandex disk links didnt let me download anything. Tried like 3 different versions of OST, none of them worked, not even the patched one, not to mention the lack of firmware in the first place.
The only step forward i could make is getting the phone to show up in device manager, because it hasnt even showed up before.
i've never even fiddled with the device's software or anything, everything was 100% stock and untouched.
i'm seriously disappointed in nokia, already contacted the reseller who yet has to reply (i don't have much hope for that either).
Any kinda help would be highly appreciated.
Click to expand...
Click to collapse
Which type and do You have a screenshot from the startscreen.

Maybe this helps

Part 2

EricH7001 said:
Which type and do You have a screenshot from the startscreen.
Click to expand...
Click to collapse
i honestly have no idea about the type, but i have screenshot

actually, no matter what i pressed in what order or battery percentage, it just said "download mode", and i also couldnt even turn the phone off either.
tbh i've contacted the reseller since then, and we'll probably just send it back in the next few days

gabika1941 said:
i honestly have no idea about the type, but i have screenshot
Click to expand...
Click to collapse
Don't you have the retail box? The type should be written on it. Also, do you have the ZEISS logo on the camera? If not, then you most likely have the TA-1054 variant, which is for the Chinese market.

intervall said:
Don't you have the retail box? The type should be written on it. Also, do you have the ZEISS logo on the camera? If not, then you most likely have the TA-1054 variant, which is for the Chinese market.
Click to expand...
Click to collapse
it must be the Chinese then, because it doesn't have Zeiss or android one logo on it.
But actually, is that very significant?

gabika1941 said:
it must be the Chinese then, because it doesn't have Zeiss or android one logo on it.
But actually, is that very significant?
Click to expand...
Click to collapse
Well, I cannot be 100% sure. But I would assume that if your phone was running a ported version of the global ROM and not the official Chinese firmware and it somehow got an OTA update then because of the differences in how the phone's memory is partitioned it would make sense that the device ends up being bricked after trying to flash something not ment to be flashed on it. :/ I hope this makes some sense to you. Also, if I am correct then it makes no sense to blame HMD for this because they have not done anything wrong. It is most likely the reseller who reflashed your TA-1054 with a ported version of the global ROM.

intervall said:
Well, I cannot be 100% sure. But I would assume that if your phone was running a ported version of the global ROM and not the official Chinese firmware and it somehow got an OTA update then because of the differences in how the phone's memory is partitioned it would make sense that the device ends up being bricked after trying to flash something not ment to be flashed on it. :/ I hope this makes some sense to you. Also, if I am correct then it makes no sense to blame HMD for this because they have not done anything wrong. It is most likely the reseller who reflashed your TA-1054 with a ported version of the global ROM.
Click to expand...
Click to collapse
i've legit thought about that! the box itself has lots of chinese on it, so it might be the case. Either way, reseller responded and i'll probably just sent it back to them this week because apparently it's their fault.
strangely, my mi a1 didnt even let the OTA install when i had the bootloader unlocked, so it's weird to see a phone getting bricked like this. I actually felt guilty for letting the OTA install, even though i didn't do anything wrong here (exceptionally:laugh
Thanks for the suggestions m8!

I think You bought a crappy Chinese dummy Nokia 6.1 HMD is not in Finland hands anymore.
The hardware is different. And the software is Android one.
I am curious how your reseller solves the problem.

can anyone tell how can help to exit from download mode. i have tried by connecting charger and holding pwr button and vol up and after andriod logo came i released by pwr button and holding the vol up button. its not worked
later i connected to my pc and install adb driver and fastboot and then through cmd prompt i run adb bootloader but its not working then i check adb devices but there is nothing shows in attched devices and also i tried with fastboot reload then mobie restarts and came back to dowload mode. so out of these step can anyone have any suggestions to get back my mobile..thank you

ok so, i kinda neglected the thread but heres what happened:
i tried EDL mode with deep flash cable, didnt work. i tried installing all sorts of drivers on my PC from all sorts of sketchy sites, after a point i decided not to mess my PC or the phone up even more.
i contacted my reseller who "fixed" the phone by installing the pie update on it somehow, and it's functional now. i even told them the phone wasn't the european version but they didn't seem to care, and i didn't feel like playing with them anymore. but it's FAR from stable, buggy as hell, and LTE B20 doesn't work either (that might have a thing or 2 to do with the phone being chinese...)
thanks for all of u for helping, this particular phone was way more than enough reason for me not to buy a nokia again ))))