Flashed Custom Rom over stock q700. Phone not detected. - Xolo Q700, Q700i

Hello ,
I was wondering if anyone could help me with a problem I am facing. I was on Q700 stock rom. I flashed cwm via mobile Uncle. Then I mistakenly flashed Xperia Z2 rom on top of that after doing a factory reset via cwm. I forgot to flash Q700i rom prior to installing the Xperia z2 rom. The problem is that now the phone wont boot up past the boot screen. There is no bootloop. The recovery is working. But, the main problem that I am facing is that my phone is not detected by the computer. It is not detected when I plug it in while powered off even though I have proper VCOM driver. It is not detected when I plug it in when the phone is in CWM. I want to go back to stock. Is there any way anyone can help me ?

Related

Yureka Soft brick.. Help me....!

I am Using Custom Roms From Last 5 Months. I ve installed cwm recovery in My yu yureka. Recently changed my Custom ROM To CR droid. It was Going smooth and neat. I Got bored of CR droid. Tried To change my ROM to miui Through cwm Got bootloop
Then I have restored my old CR droid ROM through cwm. And then I flashed Twrp 3.0 . and again I tried to flash miui ROM again got bootloop. And then again restored to CR droid which I have backed first. And then downloaded the Resuccurtion remix ROM and flashed through Twrp it booted up. And again I tried flashing miui Through Twrp. Phone started restarting again and again continuously and then went to my recovery tried restoring my old ROM phone booted up and I was using the same ROM. Next morning when I wake up phone rebooting again and again. Went to recovery , tried cleared system / factory reset Phone still rebooting. Made clean wipe flashed new ROM phone still rebooting
Don't know what to do. Then I flashed stock ROM using fastboot mode , flashed successfully phone booted up after completing setup wizard the phone started rebooting Help me to get rid out of this thanx :good:
Sorry for long explanation
I have same problem here after miui 8
waiting for solution
hope someone will solve
I have a similar case my device is in bootloop untill charger is connected.
I had similar(all most same) trouble you mentioned before and my bad luck i still dont have a solution :crying:

zuk z1 bootloop when flashing any rom

i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....

OnePlus 2 never boots up into system, but boots into recovery and fastboot mode.

I Installed the unofficial cynogenmod 14 with gapps , and i was enjoying the new rom. After using the rom for 8-10 hours , the mobile froze , so i had to restart the phone . After the phone started , it started to lag , and while it was lagging it restarted on its own, and was stuck on boot logo.
I waited for a long time for it to boot up , but it was stuck there , so i tried flashing the unofficial cm14 again as it was in the internal storage , but the result was same no matter how many times i try , and in between numerous OS flash attempts , i accidentally wiped the INTERNAL STORAGE
Getting the PC to recognize the phone , and also for the ADB and FASTBOOT to work properly was way too much of a pain , but i was able to get everything correct so ADB and FASTBOOT were working .
AND THAT'S HOW MY JOURNEY BEGAN.
I HAVE FLASHED ALL THE OTA ROMS , flashed the official cynogenmods , flashed the unofficial cm14 and cm 14.1 , tried flashing thru MSM8994DownloadTool , all of the Roms i FLASHED were successful even the MSM8994DownloadTool was SUCCESFULLY FLASHED
BUT MY PHONE STILL DOESN'T BOOTS UP IN SYSTEM , IT'S STILL STUCK AT THE ONEPLUS BOOT LOGO
I LIVE IN BANGLADESH (ASIA) , after i failed so many times and given up all hope , i went to the mobile shops for repairing the HALF DEAD SOUL , and its really sad that even they were not able to make it LIVE AGAIN
ANY HELP TOWARDS MY SITUATION WILL BE REALLY REALLY APPRECIATED
It maybe cause of old modem. try restoring to stock(i.e oos 3.x) or flash latest modem then latest recovery and Rom.
ThePresence said:
It maybe cause of old modem. try restoring to stock(i.e oos 3.x) or flash latest modem then latest recovery and Rom.
Click to expand...
Click to collapse
Tried the op2 mm modem , the phone automatically restarted to recovery with a new recovery , but its still stuck
talhaisdead said:
Tried the op2 mm modem , the phone automatically restarted to recovery with a new recovery , but its still stuck
Click to expand...
Click to collapse
Are you following the right steps to flash rom? if you don't rom won't boot. also try resetting your phone to stock, it might help you.
ThePresence said:
Are you following the right steps to flash rom? if you don't rom won't boot. also try resetting your phone to stock, it might help you.
Click to expand...
Click to collapse
Yes , but it still doesn't work . No errors are given while flashing

problem in flashing custom rom

i was using viper os for a few months, today i decided to flash aosp extended. bt befr flash i wipe all things eg, delvik, system, internal storage, data,asdf etc in the twrp menu. aftr flash the zip file i stucked into boot loop.
luckily i hv a twrp backup of my zenui. aftr flashing tht file my phone is ok. bt if i flash any other custom rom it stuck into boot loop. i tried with 2 different rom. bt same result.
mac address of my phone is changed aftr this and my phone is running with zenui twrp backup only.
i cant figure out this problem. need some help and accidentally i dnt hv any laptop right now. so, i want to avoid pc command things. bt will try to manage if tht is the only way to solve this prblem.
thank you.

Can´t flash stock ROM + lost touchscreen

Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
eldeecko said:
Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
Click to expand...
Click to collapse
I was lucky one with August firmware. Problem solved, can be closed.

Categories

Resources