i downgrade my phone from 4.4.4 to 4.2 using flashtool. after completing flash succesfully i turn on my phone but the phone shows the welcome screen and shutdown it and automatically my phone turned on and again do the previous work. It worked continuously. I can't use my phone. Now what can i do?? plz give me solution as soon as possible.......
Thank you.
Abbas Ibne Malek said:
i downgrade my phone from 4.4.4 to 4.2 using flashtool. after completing flash succesfully i turn on my phone but the phone shows the welcome screen and shutdown it and automatically my phone turned on and again do the previous work. It worked continuously. I can't use my phone. Now what can i do?? plz give me solution as soon as possible.......
Thank you.
Click to expand...
Click to collapse
Hi,
It would be best to ask your question in your device specific forum, there you will find many helpful people who will know a solution, be as specific as you can about what happened for the best results
Good luck!
Thread closed and thanks!
Related
hello!
i have a asus fonepad 7 with android 4.4.2. Recently i got an android 5.0 update notification and i downloaded it and pressed install. As soon as installing began after reboot, it showed error and after that rebooted again and showed installing again. Now the phone only shows installing, then shows error, reboots again and same process continues. So i went into the recovery and tried to repair by ADB but ended up in deleting the recovery. Now i have a tablet which is bricked, continuously restarts to installing and shows error and has no recovery option at all. I want help in the issue, I wanna know if there is a possibility that i can repair it myself because it is out of warranty.
Thanks!!
Hi, thank you for using XDA Assist. Well, the good news is it is not bricked if it turns on. You need to flash the stock firmware. The bad news is there is very little information on XDA about your device. See if anyone here knows where to find a flag the stock firmware. http://forum.xda-developers.com/android/help or here http://forum.xda-developers.com/android/help/asus-fonepad-7-fe170cg-firmware-please-t2835097
jd1639 said:
Hi, thank you for using XDA Assist. Well, the good news is it is not bricked if it turns on. You need to flash the stock firmware. The bad news is there is very little information on XDA about your device. See if anyone here knows where to find a flag the stock firmware. http://forum.xda-developers.com/android/help or here http://forum.xda-developers.com/android/help/asus-fonepad-7-fe170cg-firmware-please-t2835097
Click to expand...
Click to collapse
but there is no recovery mode or download mode through which i can flash a stock rom. Can u plz tell me how to flash rom in it if there is no recovery option or download option????
BigBadWolf90 said:
Hi, i got the same problem as you.
Try this method. http://forum.xda-developers.com/showpost.php?p=58949547&postcount=9
You will get your recovery back.
Click to expand...
Click to collapse
i wiped the recovery by mistake, there is no fastboot menu no matter what key pattern i hold...
Please see the thread provided by XDA Assist. Please follow up in that section with information as far as firmware and device specific flashing tools.
Thread closed.
Yesterday i finally got my JIayu s3
This one, on pandawill: jiayu-s3-smartphone-4g-lte-mtk6572-octa-core-3gb-16gb-55-inch-ogs-fhd-screen-black-p97209
I wanted to got to lollipop, so tried to flash a new rom with flashtool.
An unofficial lollipop rom
After flashing it would not boot up.
The screen wont even turn on, and when i connect it to my pc, it keeps connecting en disconnecting every 3 seconds or so...
Now when i try to flash an another rom, i keep getting the Brom error 4032.
What do i need to do to get my phone back?
Please help
XDA Visitor said:
Yesterday i finally got my JIayu s3
This one, on pandawill: jiayu-s3-smartphone-4g-lte-mtk6572-octa-core-3gb-16gb-55-inch-ogs-fhd-screen-black-p97209
I wanted to got to lollipop, so tried to flash a new rom with flashtool.
An unofficial lollipop rom
After flashing it would not boot up.
The screen wont even turn on, and when i connect it to my pc, it keeps connecting en disconnecting every 3 seconds or so...
Now when i try to flash an another rom, i keep getting the Brom error 4032.
What do i need to do to get my phone back?
Please help
Click to expand...
Click to collapse
Welcome to XDA Developers.
First, please register as a user, here > http://forum.xda-developers.com/register.php
I'm sorry, but there is not a specific forum for your device yet.
After you have registered, if you go to the following forum and post your question, hopefully one of our experts can help you > http://forum.xda-developers.com/showthread.php?t=2259645
Good luck.
I tried installing replicant on my Nexus S device. It worked fine for some days.However, when i rebooted the device it fails to power on. It seems there was some problem in flashing the image on the device. Is there a way to unbrick the device?. It fails to power on so i cant get to the bootloader mode even.
Thanks for your Help.
joyce7 said:
I tried installing replicant on my Nexus S device. It worked fine for some days.However, when i rebooted the device it fails to power on. It seems there was some problem in flashing the image on the device. Is there a way to unbrick the device?. It fails to power on so i cant get to the bootloader mode even.
Thanks for your Help.
Click to expand...
Click to collapse
Hello,
You could visit here
Also I would advise you to browse the Nexus S Q & A Forum. There are quiet a lot of different solutions.
-Vatsal
Hello guys,
A few months ago, I rooted my phone using kingroot. After a few weeks, i tried to install TWRP custom recover to unlock bootloader. I accidently downloaded a wrong version of it and flashed it using flashify app, after which i booted into recovery to check the new recover mode. But, something awkward happened. THE BOOT MODE DIDN'T OPEN AND THE SCREEN GOT STUCK AT "Booting into recovery". I read on the internet and realised that my device has got soft-bricked. Also, phone wasn't rebooting. So, i found a solution atleast start my phone. I took out my battery, pressed the buttons for download mode and then placed the battery back in and pressed the buttons for download mode and somewhow rebooted my phone (i read about this technique in xda forums). Now, although my phone works but i cannot access the recovery mode as it has got soft-bricked. Thus, i cannot perform a hard reset as it gets caught in that "recovery booting stuck cycle". So, can anyone tell me how to fix this? PLS QUICKLY. aLSO, i don't know much about ADB, so pls explain that too as my friend suggested me to use ADB to fix softbrick but im not sure!!
androcrazy24 said:
Hello guys,
A few months ago, I rooted my phone using kingroot. After a few weeks, i tried to install TWRP custom recover to unlock bootloader. I accidently downloaded a wrong version of it and flashed it using flashify app, after which i booted into recovery to check the new recover mode. But, something awkward happened. THE BOOT MODE DIDN'T OPEN AND THE SCREEN GOT STUCK AT "Booting into recovery". I read on the internet and realised that my device has got soft-bricked. Also, phone wasn't rebooting. So, i found a solution atleast start my phone. I took out my battery, pressed the buttons for download mode and then placed the battery back in and pressed the buttons for download mode and somewhow rebooted my phone (i read about this technique in xda forums). Now, although my phone works but i cannot access the recovery mode as it has got soft-bricked. Thus, i cannot perform a hard reset as it gets caught in that "recovery booting stuck cycle". So, can anyone tell me how to fix this? PLS QUICKLY. aLSO, i don't know much about ADB, so pls explain that too as my friend suggested me to use ADB to fix softbrick but im not sure!!
Click to expand...
Click to collapse
Hi androcrazy24
Thanks for using XDA Assist.
Could you please state the Manufacturer & Model of your device so we would better approach your issue guiding you to the appropriate experts? Your last post from November 2015 is referring to the S III. It is still that?
I will be waiting for your reply within the next 2 days.
Nice regards.
.
my phone is samsung galaxy s4 mini DUOS GT-I9192, OBVIOUSLY BY SAMSUNG..........
Kdio said:
Hi androcrazy24
Thanks for using XDA Assist.
Could you please state the Manufacturer & Model of your device so we would better approach your issue guiding you to the appropriate experts? Your last post from November 2015 is referring to the S III. It is still that?
I will be waiting for your reply within the next 2 days.
Nice regards.
.
Click to expand...
Click to collapse
"mY phone is samsung galaxy s4 mini duos GT-19192 RUNNING ANDROID 4.4.2
androcrazy24 said:
"mY phone is samsung galaxy s4 mini duos GT-19192 RUNNING ANDROID 4.4.2
Click to expand...
Click to collapse
Hi androcrazy24
Thank you for your answer
Our experts at the below forum should be able to help you. Please be welcome to ask in there.
Galaxy S 4 Mini Q&A, Help & Troubleshooting
Nice regards and good luck.
.
tried many things
unable to flash firmware
everytime phn boots gets stuck on sony boot screen,
tried hard reset nothing happens,after resetting gets stuck again on the bootscreen.
flashtool detects fastboot but not detecting flashmode.
What can i do now?
need help plz.
Ritesh07 said:
tried many things
unable to flash firmware
everytime phn boots gets stuck on sony boot screen,
tried hard reset nothing happens,after resetting gets stuck again on the bootscreen.
flashtool detects fastboot but not detecting flashmode.
What can i do now?
need help plz.
Click to expand...
Click to collapse
Hi Ritesh07
Thank you for using XDA Assist
We were able to determine that you have already posted your issue here. It would be convenient that you give some time for our experts to analyse and answer you. Therefore, I will be closing this request here.
If you feel that it's taking too much, you may *bump up* you original thread by reposting some additional information regarding it and so.
Thankful for your understanding.
Nice regards and good luck.
THREAD CLOSED
.