Hi Guys
Can someone point me in the right direction with a problem with my new phone.
Basically I recently bought a ulefone Vienna (1 month and my 1st Android phone). It was working fine and on the stock rom and no changes to the system. Yesterday I did a OTA update and now my phone is stuck in a bootloop.
The phone just restarts and after after the company logo I get the Android man with an exclamation mark.
I have downloaded all the stuff to flash the phone from ulefone but as the phone keeps restarting and rebooting I can not get the PC to install the drivers.
The PC recognises the phone when the company logo is on the phone and starts to install the drivers but when I get the Android man the PC says the phone is unplugged.
I am IT literate and don't mind getting my hands dirty but I am a recent convert to Android. I want to fix the issue myself because that's the way to learn but I am a little out of my depth.
I have read that ADB can stop the boot sequence so any pointers to what I need to read and understand to fix this issue would be greatly appreciated.
Thanks.
The_Bionic_Man said:
Hi Guys
Can someone point me in the right direction with a problem with my new phone.
Basically I recently bought a ulefone Vienna (1 month and my 1st Android phone). It was working fine and on the stock rom and no changes to the system. Yesterday I did a OTA update and now my phone is stuck in a bootloop.
The phone just restarts and after after the company logo I get the Android man with an exclamation mark.
I have downloaded all the stuff to flash the phone from ulefone but as the phone keeps restarting and rebooting I can not get the PC to install the drivers.
The PC recognises the phone when the company logo is on the phone and starts to install the drivers but when I get the Android man the PC says the phone is unplugged.
I am IT literate and don't mind getting my hands dirty but I am a recent convert to Android. I want to fix the issue myself because that's the way to learn but I am a little out of my depth.
I have read that ADB can stop the boot sequence so any pointers to what I need to read and understand to fix this issue would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Hi,
I couldn't find much information about your device here except these two threads:
Ulefone Vienna - Development & Support
Ulefone Vienna - Information & Reviews
Try posting your query in the support thread. Experts there may be able to assist you.
Good luck
Art Vanderlay
XDA Assist
Related
hey guys.
so this is my problem....
my friend just bought this phone which it need to be open lined.
then he went to a technician to open his new phone..
after that his starting screen went green with a red square and a blue square.
everything went okay..but days has passed his phone freezes at that screen but i can still access the recovery mode that the technician made.
so i researched one of your forums and i got some suggestions.
done the wipe data and other methods to fix the boot loop/soft brick.
but nothing happens.
i tried to download the official firmware and installed it to flash it back to stock.
but this happens.
it reaches 1/4 of the bar in the downloading process.
how to fix it?
and can you please answer me step by step?
thanks
I do think its sounding like hardware issue.
Please post in Android Q&A, Help & Troubleshooting
so that the right experts may be of help.
Please be patient,& Gentle with me, I'm new here,,, (TY) Hi, I have a Pantech P9060 (old I know ) Android 2.3.4 , Gingerbread( Stock Rom). It's rooted. It will turn on, load in the boot screen- and stop there, and if I touch the power/menu keys, it will start the loop acting boot process, without re-starting the phone , just continuous boot screen. I have changed the boot screen probably 3/4 times from the original AT&T screen using Jimmy Rummel apps, Rom Installer . I've tried returning back from backup, Titanium Pro, I backed up to google drive as well, but regardless I can't seem to reset to factory( which I've done before), or even update, Nothing.. It's so frustrating. I've searched these forums inside out for a solution as to not bother you guys with my old phone issues, but I have to admit, I need help with this. I don't think it's hard bricked, I'm thinking I may have flashed the wrong Rom( im not sure though) trying to upgrade from 2.3.4 .. Not positive though. I sure hope there's someone to help me here, It wont connect to the PC syncing, Pantech PC Suite, yet my pc shows the phone in Device Manager and Computer. So I'm hoping I've done something simple, :/ stupid,,but simple. Anyone help me out ? Thanks in advance.......
Hi,
I can't find a relevant thread on XDA for your issue, so you'll need to ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
Thank you. Thread closed.
Hey, guys good afternoon. I have a Cubot Note S which I manage quite stupidly, to brick. The phone was rooted with KingRoot and I accidentally press to update to the latest software version from the Update Center of the phone and before it managed to complete, it showed an "ERROR" message. After that, I stuck into a boot loop. I've been searching the internet for a stock firmware of the phone in a .zip file because the Cubot has something like a stock Recovery mode, which I can boot to, to factory reset my phone, to boot into bootloader or apply an update through an sdcard etc. So far I only found a rom on needrom and it is in .rar and has many other irrelevant files in it. It has instructions below how to perform a clean flash of the ROM, but something goes wrong at the process. Either the SP-DMT (Flash Tool) doesn't work properly or my computer doesn't recognize my phone and I can't find the proper drivers for it. Has anyone ever been in this situation before with a chinese phone? Please help out with this because the cell phone belongs to a dear friend of mine and I can't afford to buy a new one these days. Thank you in advance.
Hello and thank you for using XDA Assist,
please create a thread here:
Android Q&A, Help & Troubleshooting
Kind regards
Trafalgar Square
XDA Assist
Good morning to all of the bosses here and to everybody...I am also new in adventuring in custom rom flashing. Oh God, I just afford a zenfone 6 and quickly I decided to mod it with custom roms. I tempted to update it manually to lollipop and it was successful. Then I decided to downgrade to kitkat in order to unlock the bootloader. I was served on internet with 2 ota files(6.2.2.2 and 6.3.3.3). I flashed the file 1 with success but as for the file 2, my phone didn't finished the process and switched off itself. I turned it on and it directly went on recovery trying to finish the downgrade. When the phone tried to reboot it stucked on asus logo. I went on recovery and made a hard reset, but it kept stuck on the asus logo at boot. Now came the bad luck; I found tutorial on internet on how to unbrick zenfones. I precise that almost all the tutorials spoke about the case zenfone 5 and 6 are stuck on usb logo, but mine manifested itself in a cycle of 5 to 7 reboots before showing the usb logo and then turns off itself definitively about one minute after that usb logo, and I have to turn it on again for a new cycle again. So that bad luck is that I saw that tutorial to unbrick zenfone with a method using usb intelsoc and other tools I forgot the names. I installed these stuffs with success and my device could be detected ready for flashing. The files that had to be flashed are fastboot.bin, ifwi.bin, dnx.bin, osr dnx.bin...I flashed them successfully, but unlesse I get my phone on its usual asus droidboot screen, it ended up by a frozen intel inside logo. I tried to put it into droidboot or recovrey, but to no vail. The reboot cycle was still there. Then I saw a tutorial on zenfone 5 stuck at intel inside logo where it was said to add a file called ...fuse.bin. I tried to find one for zenfone 6, but I didn't find it...so...so...so I used that fuse.bin intended for zenfone 5 and flashed my zenfone with it. The flash wax successful but when the phone rebooted...BLACK SCREEN!!! With some vertical white stripes appeared. No image, but cycle of reboot continue without the usb logo this time. The phone is still detectable and I even tried to reflash the previous file without that bad fuse.bin, successful but screen is still black...oh God help me, oh my new phone, everybody here help me recover my phone please!!! The version of my phone is TW version...thanks in advance!
Hello and thank you for using XDA Assist,
your device don't have a device specific forum here on XDA. Please create a thread here:
Android Q&A, Help & Troubleshooting
The experts there should be able to help you. Good luck!
Kind regards
Trafalgar Square
XDA Assist
Hi everyone,
I own a Motorola Moto G2 (XT1068, dual sim) that came used with Android 6.0 on it.
I installed TWRP (twrp-3.0.2-3-titan.img) on it but failed to root Android 6.0 as well as 5.0 for whatever not yet understood reason. I don't do Android development for a living but I'm an IT professional, so handling adb and fastboot as well as reading and understanding instructions isn't a problem.
I flashed stock Android 4.4.4 (RETDEALL_XT1068_4.4.4_KXB21.85-14) which I successfully rooted by installing SuperSU via TWRP.
Next I updated SuperSU, verified that root access is indeed working and installed FlashFire, which I hoped to use to install OS upgrades, possibly without losing root. FlashFire is new to me (as of yesterday), everything else mentioned up to here is not.
I used the "Flash ZIP or OTA" action from within FlashFire and the previously downloaded update file in the /cache directory. I can't reproduce the file name since the phone is currently unusable and I didn't write the file name down prior to using FlashFire.
The state of the phone after this unsuccessful attempt was that of a broken USB device, i.e. unable to even register as whatever type of USB device. I learned that this can be fixed by holding the power button down for more than one minute, after which I managed to
get the phone to be shown as working "RELINK HS-USB QDLoader 9008" USB serial device in Windows 7 device manager.
I used the information in these two threads:
http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Since I started with Android 4.4.4 trying to upgrade to 5.0, I had hoped that the blank flash package for one of these Android versions would help fix my problem, but as of now, this doesn't seem to be the case. At the end of the blank flashing process, I get the message
FAILED <blank-flash:sdl-transfer-image:sdl-hello: error sending packet>
After that, the phone still has a black screen and cannot boot into anything. Repeating blank flash works after resetting whatever part of it is still working by holding the power button down for about 30+ seconds.
Is there anything obvious (or maybe even not so obvious) that I missed?
Thanks for reading and any help and/or pointers in the right direction.
Hello and thank you for using XDA Assist,
please create an account and post your question in our Android Q&A section:
G 2014 Q&A, HELP & TROUBLESHOOTING
The experts there should be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist