Develop Bugs

[Q] Touch Diamond :: permanent reboot :: bootloader update back to Stock SPL imposs.

Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers

same problemm
Same problem. Any help?

tekata said:
Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers
Click to expand...
Click to collapse
Any chance to MTTY? Might help, just guessing...
Or try to flash a new radio ROM as the wifi hardware might be stuck in a state that is unknown to the drivers. Flashing a radio is supposed to reset hardware but I may be wrong.
Really guessing here but symptoms shows relation to radio hardware.
Cheers,
Cina.

sspl
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.

Hello, my solution to this was conductive interconnect of metalic parts as you can see here
://i.ytimg.com/vi/UUnH8O-1jII/0.jpg
(of course with http on the beginning, i'm not allowed to post links)
on the left with aluminium tape (sorry for image quality, found it on web).
It also seems that the sim card reader has to be conductively connected with the above em shielding.
Hope it will help

it´s a battery problem ... get a different one and your phone should be fine

Dreamtheater2003 said:
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.
Click to expand...
Click to collapse
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
@edefux
Do you already had such a case? I am not sure, if buying a new battery is economical enough only in order to try, if it works. I admit, it could be the battery. But running the phone with the charger switched on, should show if its the battery or not. I tried with charger on, but obviously this didn't solve the problem. Or do you mean, that in the battery there is some sort of "short circuit", that's confusing the Diamond no matter if the charger is on or not?
@DiamondFlower
Thanks for the suggestion. I'll give it a try, when I tried everything else
This will be the final try before burrying the precious Diamond.
Cheerz

MTTY.
tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
...
Cheerz
Click to expand...
Click to collapse
See this post for MTTY. This is the second post on Diamond ROM thread pinned for easy access anyway. Please search before you post!
If you can enter bootloader mode with VolDown pressed while reboot you're off to go. You can plug in USB cable and you can flash SPL, Radio or any new ROM. I assumed this based on your first post:
tekata said:
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
Click to expand...
Click to collapse
Cheers,
Cina.

it is a battery problem i´m 99,9% sure of it - i had the same case ... it was driving me crazy ... different roms, radios, but the problem persisted - luckily at that time i was working at a cell phone provider and could try different hardware, which finally brought me to the solution to switch the battery.

edefux said:
it is a battery problem i´m 99,9% sure of it...
Click to expand...
Click to collapse
Maybe I'm a bit unlucky, but I've got the 0,1%. Took a new battery, this didn't solve the problem though.

i´m sorry it didn´t work for you ... !

it's ok! it didn't work - actually I could have thought about it wont work: beforehand I sent the item to the mobile operator guarantee team and they returned it back - no warranty of course (due to olinex bootloader which I wasn't able to remove) and stating: Fremdeinwirkung/ Totalschaden (total loss). And because I sent it without battery and they obviously checked it ... suppose with a fresh or "good" battery. And it still didn't work for them, so...
I'll try to open it and see if there is some short circuit around the metal shielding. Maybe I'm lucky then.
Anyway thanks guys about the hints and suggestions!

tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
Click to expand...
Click to collapse
I'm not sure if its called sspl but you can run it from boot loader and it will black out your phone. after that you need flash the new bootloader.
I'm thinking its not a bootloader problem though...

[Q] Another Bricked Desire

Yes, this is another HTC Desire bricked thread.
Also very yes, I've read a plethora of what I considered similar threads, on this forum and others.
THE HARDWARE:
Us Cellular Branded HTC Desire.
THE PROBLEM:
I rooted the phone without problems. I then attempted to flash several (read: a dozen or so) different ROMS following tutorials to the letter. Most were Froyo ROMS with Sense UI. I like HTC Sense.
So, after trying dozens of different ROMs, none of them gets past the white boot screen with green "htc" text. Sometimes the phone would auto reboot a few times and then shatter my hopes by getting stuck again, and again... and again.
WHAT I HAS DONE:
After proving the cake was no lie, I created a gold card. I then followed some nice instructions about using previously mentioned card to flash non-branded ROMs. After I mopped up my tears of rage and frustration from all these ROMS still getting stuck on the same white boot screen, I wrote this post.
Also, I went in to my local us cellular store (I know the tech who works there) hoping he could do me a favor.. but since the phone was rooted (yes i know i'm an idiot for trying) he could do no such thing.
Also, I tried downloading .exe (RUU files?) that set up a wizard on my pc to fix my desire but they couldn't connect to my device... connection error message kept coming up.
I am willing to crawl up a temple on my knees for penitence if need be to get this fixed. But please don't *only* send a few links to "similar" threads...

Sounds like an usb brick. Follow this guide to repair:
http://forum.xda-developers.com/showthread.php?t=691639
If finished, try to unroot your phone by flashing fitting ruu again.
Btw, a question: which hardwarerevision does your desire have? You find this out, when you boot into hboot and read the number behind the word pvt (first line). Another question: which recovery system do you have?
No warranty for any damage!

Sry for the post, Mat was quicker

The hard part is finding a fitting RUU... since the US Cellular brand does not seem to be popular.
I *FINALLY* got a RUU to flash via fast bootusb.... and it looks like i am in the clear... as far as that goes.
We shall see how this works out.
Thank you (I hit thanks button too)

MasterofAll said:
The hard part is finding a fitting RUU... since the US Cellular brand does not seem to be popular.
I *FINALLY* got a RUU to flash via fast bootusb.... and it looks like i am in the clear... as far as that goes.
We shall see how this works out.
Thank you (I hit thanks button too)
Click to expand...
Click to collapse
Good luck!

If flashing of the US cellular rom fixes it then odds are the goldcard did not work. Goldcards can be temperamental to setup and keep setup correctly.
If you repartition you need to set it up again. I have had a lot of annoyances due to this on my phone.

Thanks all
Everything works great... save for my SD card (which was a gold card). I ended up formatting it with my pc, then reinserting and everything seems fine.

MasterofAll said:
Thanks all
Everything works great... save for my SD card (which was a gold card). I ended up formatting it with my pc, then reinserting and everything seems fine.
Click to expand...
Click to collapse
Congratz!

Another victory for the community.
Good job all !

[Q] [x-post from LG G3] D851 unroot / restore to stock

I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.

http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4

BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.

etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.

Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it

BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.

Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.

Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4

BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.

Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4

BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.

Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea

Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.

Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.

Thank you for answering

yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.

Good luck man let us know what tmobile says

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

Soft bricked my HTC One X (India);Help needed as am dead in water after a week

The following is a description of the events that lead to the brick. I am writing here in utter desperation and have tried almost everything available on the forums and around the web. Requesting assistance from any person in India or anywhere who knows the device well and can help me.
1) I had been using HTC One X for around two years. It went dead slow and I went looking out for options. Found cleaners and other software but nothing helped much.
2) I decided to flash a ROM like I have done on my Micromax A116(Indian mobile brand, available on XDA forums as well).
3) After a bit of research I found that I have to unlock the bootloader and install recovery(installing the recovery isnt new to me)
4) I then unlocked the bootloader and tried installing the ROM.. http://forum.xda-developers.com/showthread.php?t=2753450
5) The installation was a failure due to some partition error.
6) I looked around XDA and found a solution.
7) This is where I goofed up.
I was unable to install the ROM and so I wiped everything using philz touch recovery. It even wiped the backup(I forgot I do not have the option of memory card on this Indian model of HTC One X).
Now after the restart, nothing comes up. I tried flashing other recovery like TWRP 2.8 which is flashing fine however, am unable to do anything except go in bootloader(fastboot, Hboot etc) or inside the recovery.
I read about RUUs, and how to make my phone detectable in PC and use ADB to copy ROM and re-flash it but nothing works at the moment. After a week of trying myself, I am here if anyone can help me out. Would deeply appreciate if anyone can find some time and check out on my issue.
I have HTC One X: CID HTC__038
Hboot: 1.73+
S-on

BhatiaPulkit said:
The following is a description of the events that lead to the brick. I am writing here in utter desperation and have tried almost everything available on the forums and around the web. Requesting assistance from any person in India or anywhere who knows the device well and can help me.
1) I had been using HTC One X for around two years. It went dead slow and I went looking out for options. Found cleaners and other software but nothing helped much.
2) I decided to flash a ROM like I have done on my Micromax A116(Indian mobile brand, available on XDA forums as well).
3) After a bit of research I found that I have to unlock the bootloader and install recovery(installing the recovery isnt new to me)
4) I then unlocked the bootloader and tried installing the ROM.. http://forum.xda-developers.com/showthread.php?t=2753450
5) The installation was a failure due to some partition error.
6) I looked around XDA and found a solution.
7) This is where I goofed up.
I was unable to install the ROM and so I wiped everything using philz touch recovery. It even wiped the backup(I forgot I do not have the option of memory card on this Indian model of HTC One X).
Now after the restart, nothing comes up. I tried flashing other recovery like TWRP 2.8 which is flashing fine however, am unable to do anything except go in bootloader(fastboot, Hboot etc) or inside the recovery.
I read about RUUs, and how to make my phone detectable in PC and use ADB to copy ROM and re-flash it but nothing works at the moment. After a week of trying myself, I am here if anyone can help me out. Would deeply appreciate if anyone can find some time and check out on my issue.
I have HTC One X: CID HTC__038
Hboot: 1.73+
S-on
Click to expand...
Click to collapse
Download this read very carefully and follow each and every step in that file ...
after switching to new layout flash the rom you had downloaded ..and ur HOX will come back to life
to get a hang of new layout read here

HTX One X Stuck in Bootloop
onex master said:
Download this read very carefully and follow each and every step in that file ...
after switching to new layout flash the rom you had downloaded ..and ur HOX will come back to life
to get a hang of new layout read here
Click to expand...
Click to collapse
I Tried the steps listed in the PDF but no go..
I am still stuck at the boot screen and the CM 12 logo is all I get. I never get past that. I have tried multiple flashes and installs but no go.
I followed the instructions step by step and word by word as per http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru but still no go.
Any help will be highly appreciated.

Dragon_Knight said:
I Tried the steps listed in the PDF but no go..
I am still stuck at the boot screen and the CM 12 logo is all I get. I never get past that. I have tried multiple flashes and installs but no go.
I followed the instructions step by step and word by word as per http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru but still no go.
Any help will be highly appreciated.
Click to expand...
Click to collapse
after flashing rom have u flashed the boot.img
if not then flash it using fastboot flash boot boot.img

Cannot thank you enough onex master
onex master said:
after flashing rom have u flashed the boot.img
if not then flash it using fastboot flash boot boot.img
Click to expand...
Click to collapse
Dear onex master,
I had given my phone to service center and got the phone today after they failed to bring it back and said nothing can be done now.
And that is when I came back here to find your post and thought of giving it a try before I go ahead and buy a new phone. Your guidance is so perfect and accurate that my issue is finally resolved now. I got my phone back. Many thanks to you. Much much appreciated. May God bless you dear..

BhatiaPulkit said:
Dear onex master,
I had given my phone to service center and got the phone today after they failed to bring it back and said nothing can be done now.
And that is when I came back here to find your post and thought of giving it a try before I go ahead and buy a new phone. Your guidance is so perfect and accurate that my issue is finally resolved now. I got my phone back. Many thanks to you. Much much appreciated. May God bless you dear..
Click to expand...
Click to collapse
Hi man, im also in the same situation so can please you please elaborate the steps to get back working phone.
Thanks.

Please refer to the pdf link by one x master/Tanuj. You will get your phone back..just follow step by step. Use same software and recovery as mentioned by him in pdf..
Sent from my Micromax A116 using XDA Free mobile app