Hello everyone,
Ok so I bought a brand new g2 on craigslist. Everything was working perfectly fine...until I decided to root it. I downloaded the necessary files and it all worked perfectly fine. Now I know some of you may bash me for this but thats not the reason im asking for help. I know I messed up by not reading more into depth ahead of time. I opened up visionary did the temproot, then proceeded to do the permroot. Phone rebooted but stayed stuck in the HTC logo screen. I seriously need help guys and I would greatly appreciate it if I could just make it work again. I went into the bootloader restored back to factory settings but same thing happens. I managed to get a copy of the original 2.2 stock rom for the g2 put it in the sd card then it seems like it updates fine..restarts a couple of times but stays in the htc logo again after like the second restart. I have the S-on...(prolly screwed). Anyway, im asking here because I searched a lot and I know there are other posts about people who ask this but then there are no concrete answers. I am wondering if there really is a way to fix it. Whether it be installing a custom rom or any other thing. If its not fixable as much as it hurts, Im going to have to put it up for sale and get at least something out of it (for parts or whatever). Any help is greatly appreciated. Thanks Guys
I will give gou 10 dollars! But hey do a search for visionary bootloop fix. There was a great guide on how to fix that. It will require you to learn about adb. Adb will be your friend for fixing things.
Sent from my HTC Vision using XDA App
lol
lol about the 10$...hey I greatly appreciate your help though...
Man, I just noticed there are lots of people stuck in this HTC logo screen. Having a hard time installing the damn adb......ahhhh this crap really sucks and its all my fault....hopefully there is someone out there who had the exact same problem and got it working.
ADB is quite easy to install actually, all you need to do is download the Android SDK, get the usb drivers, modifiy the inf files in the usb_drivers folder, and you're good to go.
As for rooting, I would suggest using the more updated gfree method.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
I dunno why you have to modify anything. I plugged my phone in and everything just worked.
Sent from my HTC Vision using XDA App
Only $10!
Man i would've given you @ least $11.
If anyone is having trouble with adb (and I know that it can be a struggle), I'm writing a guide to try and help - http://forum.xda-developers.com/showthread.php?t=865685
It's not finished yet, but there's enough information in there already to perhaps help a few people out.
Hello
Not very competent on the phone, thats my son... anyway he gave me this phone changed to freedom pop with their free 200mins service.
Yesterday morning there was a message stating need to install upgrade to software, since then it has not worked, see photo. I tried installing from cache but it doesnt. My son is out of town and I dont know how to fix this.
I was thinking I should just install software from scratch, but dont know which one, I believe it was rooted. So please help me restore my phone.
Thanks
I am having the same problem, could someone please show us what to do.
Found the fix, flash the tar http://forum.xda-developers.com/showthread.php?t=3007847
yes this worked for me.
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
Yep...you're seeing me again...with another phone...in a public thread (moderator please make a device page for this phone...)
oh wait..ANOTHER BOOTLOOPED PHONE(wasn't me, my friend's)
Oh hello!
Sooooo yeaaa cause I am a helpful person and I am the only one who understands how this Android tweakeroonie works, I am trying to help my friend's Lenovo S850 (SKU unknown cuz owner didn't remember lel...)
So the story begins...
This phone is rooted, and survived for some time and one day, the owner would like to try to flash Lollipop in his. Now I don't know WHICH Lollipop he was trying to flash (he himself is unclear, I maybe could re-trace the link of guide), but it's not CyanogenMod, because this device supports CyanogenMod 12.1. I am wondering to myself, "if you really need Lollipop, why don't you go Cyanogen?"
After clicks, he told me that he bootlooped his phone while trying to flash the ROM. But he has successfully installed TWRP (he said...not by my inspection). He said that he would able to boot once in the recovery and then...
BOOP
"The hell is going on? It's taking too long to start! NU UH I'M PANIC!":crying:
Me came in the way and try to save the day.....(not really)
So technical part..
As I am trying to resurrect the phone, I have the stock firmware + scatter, I have SPFlashTool, the phone in factory mode and a heavy duty data cable connected. While the loading of the scatter is a success, a popup saying "PMT has been changed, it must be downloaded". And I'm like " umm wat?". Techies, please if anybody can explain in detail what is that popup means, why is that happen. Googled "PMT error spflashtool" and found that I need to MAKE (yep make...I dunno code droid) a new scatter file specifically for that unit of phone. Well MTKDroidTools we go.....
And this is the point that I got stuck, while the SPFlashTool detects the phone, the MTKDroidTools doesn't.
"HOW ARE YOU NOT CONNECTED?!? I AM CONNECTED GADDAMIT! DONT YE HEARD THE 'DUN DUDUDUN DOON' SOUND?"
Help... I am out of wit to continue researching. It's midnight. I am sleepy so...
Please anybody is skilled enough to understand and try to tell me how to fix this annoying prob.
Problems after installing XPOSED
I believe it is because of XPOSED, because it was after its installation.
It plays me playstore, it must have been temporary error or go to know why
Basically, I can't start with root. Nor, pressing volume up and power.
Yes, I try to start with root, the samsung letters are always fixed and the phone does nothing (I waited until 15 min.)
I put tp you, the messaget that i was put in Magisk post, another night¡
Hello, good to everyone
I'm Sergio from Zaragoza, happy to talk with you!
Although, rather, it is asking for some help or a tutorial to see if I can avoid having to wait and restart the entire root process, although I don't think I can help it
My current situation is as follows; my computer died 2 weeks ago and until Friday the new one does not arrive because it was much better to wait for black friday, so now I only have my Android device, which is a Samsung A50 - FN
During these weeks, I survived thanks to him but now I have one more problem! Haha!
I am not a programmer, at the moment and pulling high I am an amateur, so my lack of knowledge is high. However, at the end of October and thanks to a forum partner who explained how the S A50-FN could be rooted, I got the root, sorry but I put the referral of the partner in question as I navigate in this wonderful forum without the app and with the mobile browser is very difficult, since I use an instant translator to understand you well and the truth is very frustrating to navigate (very, very slow) to that you add that due to the problem I write to you (I think that's why, more than anything to find an explanation) I can not install applications, but that is what I think least should matter right now!
Forgive the long text, I just want to explain my best in my current curious circumstances xD¡¡
Basically, before installing two modules of Xposed with all my joy and completely ignorant! Or rather, I could not imagine, that I could leave the phone on the screen of the letters of Samsung! Suddenly my cell phone was not going! I had no means of contacting human haha or anything at all.
So, try with very little hope (I did not remember exactly how it was done) enter the recovery mode and from there, try to find a solution!
Fortunately, on the second attempt I managed to restart the phone and it started! Since if I turned it off, it automatically restarted and stopped working, again the letters of SAMNSUNG, but when I restarted it started and I could use the phone!
Of course, at the cost of right now I have no root and I can not for example install Apps or God knows how many more things will fail on the device!
I could read something and I think if I had TWRP I could uninstall Magisk by flashing the Magisk uninstaller or God knows, if only the two modules at best!
But I don't have TWRP or any custom recovery since I did it with Magisk and ODIN and I didn't need it .....
So, do you think I can do something to fix it or will I be forced to have a computer and do a hard reset and have to do the process again?
Thank you very much for all your unstoppable work! Hopefully you can help me!