Related
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
bboybtek said:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
Click to expand...
Click to collapse
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
alray said:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
Click to expand...
Click to collapse
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.
Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell?
Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems . Thanks a lot for helping out man!
I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?Even my the the bootloader unlock warning reboots several times before getting to the never ending bootanimation
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files
There's a number of guides in this subforum that goes through flashing the stock firmware for your phone. The reason you're getting bootloops is because there's currently no stable way to get root access on Lollipop for this phone, but it is being worked on.
ADB can be a bit finicky, so it'd probably be easier to have your ROM on the phone itself, whether in the data/media/ folder in Internal Storage, or on an SD card, since neither are wiped whenever you factory reset or clean your phone. TWRP 2.8.2.0 and above allows you to enable MTP mode so you can move your files straight onto or off your phone.
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
sleekykenny said:
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
Click to expand...
Click to collapse
Did you try manually selecting the driver is device manager?
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Traediras said:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Click to expand...
Click to collapse
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
sleekykenny said:
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
Click to expand...
Click to collapse
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Traediras said:
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Click to expand...
Click to collapse
Thanks Dude, After your last message I rechecked the mfastboot-v2 folder on the thread and realised the only new file in there was the mfastboot.exe file so i quickly googled it and saw another thread in which i found the file.I downloaded it and then executed all the commands. Goshh I finally saw my phone boot up in a long time which brought a huge smile to my face.
I would like Thank all of you guys who took the time out to visit this thread and give me suggestions. THANK YOU BROS
I really appreaciate it. Happy new year
Glad to hear everything worked out for you. Happy New Year to you too.
Duplicate thread created by OP
Original is here
Please do not create multiple threads again.
Thread closed
Dear people of XDA Developers,
After installing some different ROMs and rooting my XT1068 Moto G 2014 it crashed. I can no longer use Android because somehow my Android is corrupt. I have been trying to fix this problem for a couple of weeks but after tons and tons of forum threads that didn’t quite match my problem I’m here explaining my problem. (btw my bootloader is still unlocked)
First of all, when I do a normal bootup on my Moto G, most of the times it will show the Motorola loading animation but when the animation would go away and show my lockscreen, it shows a black screen. In some rare cases it shows the animation, it says “preparing Android” and my Android would boot up but after a few seconds everything starts crashing and it gives messages like:
Unfortunately, process.android.acore has stopped.
Unfortunately, Google Play Services has stopped.
If I close these messages, they will all reappear.
My phone is able to boot into TWRP Custom Recovery from fastboot. I am running TWRP version v2.8.6 and I also have MultiROM v32 with trampoline v23, although I only have 1 ROM currently installed.
I have downloaded this Easy installer from the XDA Developers Forum:
(5.0.2 XT1068 Retaildsdsall Feb 25th LXB22.99-16 version 22.41.16)
I have put my phone into fastboot, I have put all the downloaded files into a folder on my Desktop and I have opened the Auto Restore Script.bat file. (see pictures 1 to 5)
After the process, the exact same things happen as I described earlier when booting up Android.
So then I downloaded a stock Lollipop 5.0.2 ROM from this forum thread:
(I downloaded the Pure Edition which was called “Stock_XT1068_22.21.28-ROM_PURE-EDITION.zip”
I downloaded the zip onto my microSD card which I then put into my phone. I booted up into fastboot and opened my recovery. For some reason it already said “E: Unable to open ‘/cache/recovery/.version’.”
Then I tapped on “wipe”, then “advanced wipe” and I selected everything except for MicroSD. It was done in about 1 second and it said “Wipe Complete” but “Failed” in red letters was written under it.
I still tried to continue, so then I went back and tapped on install. I navigated to the folder which the zip was located in, selected the zip and installed it. At the end it gave me the error: “E:Error executing updater binary in zip ‘/sdcard1/Stock_XT1068_22.21.28-ROM_PURE-EDITION.zip’”.
I really don’t know what to do from now on, so I would really appreciate your help!
Also, I put the file log (recovery.log) from trying to install the zip as an attachment on this post, and picture 6 is the response I get from typing “fastboot getvar all” in cmd.
Greetings,
Thomas
(By the way, i'm Dutch so please ignore some grammar/vocab errors )
TheSupermazter said:
Dear people of XDA Developers,
After installing some different ROMs and rooting my XT1068 Moto G 2014 it crashed. I can no longer use Android because somehow my Android is corrupt. I have been trying to fix this problem for a couple of weeks but after tons and tons of forum threads that didn’t quite match my problem I’m here explaining my problem. (btw my bootloader is still unlocked)
First of all, when I do a normal bootup on my Moto G, most of the times it will show the Motorola loading animation but when the animation would go away and show my lockscreen, it shows a black screen. In some rare cases it shows the animation, it says “preparing Android” and my Android would boot up but after a few seconds everything starts crashing and it gives messages like:
Unfortunately, process.android.acore has stopped.
Unfortunately, Google Play Services has stopped.
If I close these messages, they will all reappear.
My phone is able to boot into TWRP Custom Recovery from fastboot. I am running TWRP version v2.8.6 and I also have MultiROM v32 with trampoline v23, although I only have 1 ROM currently installed.
I have downloaded this Easy installer from the XDA Developers Forum:
(5.0.2 XT1068 Retaildsdsall Feb 25th LXB22.99-16 version 22.41.16)
I have put my phone into fastboot, I have put all the downloaded files into a folder on my Desktop and I have opened the Auto Restore Script.bat file. (see pictures 1 to 5)
After the process, the exact same things happen as I described earlier when booting up Android.
So then I downloaded a stock Lollipop 5.0.2 ROM from this forum thread:
(I downloaded the Pure Edition which was called “Stock_XT1068_22.21.28-ROM_PURE-EDITION.zip”
I downloaded the zip onto my microSD card which I then put into my phone. I booted up into fastboot and opened my recovery. For some reason it already said “E: Unable to open ‘/cache/recovery/.version’.”
Then I tapped on “wipe”, then “advanced wipe” and I selected everything except for MicroSD. It was done in about 1 second and it said “Wipe Complete” but “Failed” in red letters was written under it.
I still tried to continue, so then I went back and tapped on install. I navigated to the folder which the zip was located in, selected the zip and installed it. At the end it gave me the error: “E:Error executing updater binary in zip ‘/sdcard1/Stock_XT1068_22.21.28-ROM_PURE-EDITION.zip’”.
I really don’t know what to do from now on, so I would really appreciate your help!
Also, I put the file log (recovery.log) from trying to install the zip as an attachment on this post, and picture 6 is the response I get from typing “fastboot getvar all” in cmd.
Greetings,
Thomas
(By the way, i'm Dutch so please ignore some grammar/vocab errors )
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 without the "mfastboot.exe oem lock begin" part
KuranKaname said:
Try this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 without the "mfastboot.exe oem lock begin" part
Click to expand...
Click to collapse
Nope, i can boot up, but when the bootup animation stops, i get all these error messages again:
Unfortunately, process.android.acore has stopped.
Unfortunately, Google Play Services has stopped.
etc.
Thanks for your time btw,
Thomas
TheSupermazter said:
Nope, i can boot up, but when the bootup animation stops, i get all these error messages again:
Unfortunately, process.android.acore has stopped.
Unfortunately, Google Play Services has stopped.
etc.
Thanks for your time btw,
Thomas
Click to expand...
Click to collapse
Did you try to install a custom rom?
Try restoring to stock with fastboot
ethanchow said:
Try restoring to stock with fastboot
Click to expand...
Click to collapse
That's what i did, only all commands were automatically typed in thanks to the autostorescript.bat file from the Easy Installer
KuranKaname said:
Did you try to install a custom rom?
Click to expand...
Click to collapse
I did, i tried several ROMs but all of them give the same error which is:
E:Error executing binary in zip "sdcard1/NameOfROMRightHere.zip"
I googled this error but all i found was for CyanogenMod which i haven't got installed on my device and is not the ROM i want to get on it.
I have also tried some Android 4.4 ROMs but no luck with those either.
~Thomas
TheSupermazter said:
I did, i tried several ROMs but all of them give the same error which is:
E:Error executing binary in zip "sdcard1/NameOfROMRightHere.zip"
I googled this error but all i found was for CyanogenMod which i haven't got installed on my device and is not the ROM i want to get on it.
I have also tried some Android 4.4 ROMs but no luck with those either.
~Thomas
Click to expand...
Click to collapse
What recovery are you using?
KuranKaname said:
What recovery are you using?
Click to expand...
Click to collapse
As i said in the original post, i am using TWRP Recovery version v2.8.6.
TheSupermazter said:
As i said in the original post, i am using TWRP Recovery version v2.8.6.
Click to expand...
Click to collapse
Try using Philz recovery: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-philz-touch-recovery-t3006838
Sounds like your eMMC is bad.
If that is the case, it's non- recoverable and you'll need to get a new device.
Sent from my XT1031™
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Bricked is right !
quyvinh said:
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
My recovery is still untouched, so does bootloader. That is why I said mine os softbrick. It means if I have the stock ROM, then I am ready to go back alive again. I cannot imagine how could you erase the stock recovery? Unless you failed the custom recovery, then it probadly hard bricked. If I can find how to fix it then I will post here. I am currently working around with MTK Droid tool and SP Flash tool, but they are working partially only. Cannot write out the scatter file. Man, this phone is tough.
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
min1968 said:
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
Click to expand...
Click to collapse
Did you do this?
emowing said:
13. select wipe, format data, type in yes (this fixes the boot looping issue -- credit @acotto)
Click to expand...
Click to collapse
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
This is because first these phones are MTK67xx phone, and 2nd they are running on new android 5.1. So the way they are rooted different with the old ways.
grampyog said:
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
Click to expand...
Click to collapse
eksasol said:
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
Click to expand...
Click to collapse
Here you go. this is a twrp backup.
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
how do i restore the rom im kinda a newb i rooted my phone than restored and now im stuck a startup and it wont go it. just gets stuck on "checking connection" i have the vivo XL and i am in need of help so how do i get this rom back to original because i dont know what to do:fingers-crossed:
Bam-Great
Followed all of the instructions and many tries later I have a phone that boots and works just fine. What I'm not finding is an image of the original rom anywhere. Pretty sure I've looked closely but if anyone has a link take me to your leader. My thanks to the awesome person that put this tutorial together. If anyone has bricked their phone trying to root follow these instructions.
Note: The stock MS drivers did not work make sure to load the VCOM drivers.
Many thanks again,
Ken
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
Any ideas if this restore method with Bypass the Factory reset protection?
Just as a quick update. Simply formatting with the flash tool. And installing the gionee firmware was enough to bypass the Google factory reset prevention. Hope this helps anyone else that forget there Gmail address they used.
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
cas8180 said:
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
Click to expand...
Click to collapse
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
xdadev_user11 said:
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
Click to expand...
Click to collapse
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
cas8180 said:
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
Click to expand...
Click to collapse
That's strange. grampyog had the same problem. But the backup rom worked for me and eksasol. Very strange.
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
xdadev_user11 said:
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
Click to expand...
Click to collapse
That did it my good man! I have a complete bundle now with boot logo and the nvram secro files you included I feel compelled to mirror so let me work on that. Thanks a bunch thanks to you I am back in business!
Here is the link for the complete TWRP backup that should be able to restore any device back to stock. https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip?dl=0
Crossposting from the Lineage 15 thread, as it may be a more general problem...
I installed lineage 15 a couple days ago.
I followed the OP, flashed the partition firmware first, then the ROM, TWRP, GAPPS, rebooted, flashed Magisk. Everything was working fine.
I took the 0210 nightly OTA. Google Play Services and all Google apps stopped working.
I figured I'd start fresh through fastboot, but now any command that would actually help (flash, boot, etc) returns "failed: unknown command". Can't boot into TWRP.
"fastboot devices" returns the device ID fine, fastboot reboot works.
Tried a factory reset based off another post I found, still in the same boat.
Any ideas?
Horror Business said:
Crossposting from the Lineage 15 thread, as it may be a more general problem...
I installed lineage 15 a couple days ago.
I followed the OP, flashed the partition firmware first, then the ROM, TWRP, GAPPS, rebooted, flashed Magisk. Everything was working fine.
I took the 0210 nightly OTA. Google Play Services and all Google apps stopped working.
I figured I'd start fresh through fastboot, but now any command that would actually help (flash, boot, etc) returns "failed: unknown command". Can't boot into TWRP.
"fastboot devices" returns the device ID fine, fastboot reboot works.
Tried a factory reset based off another post I found, still in the same boat.
Any ideas?
Click to expand...
Click to collapse
What happened is that you messed up the installation order.
https://forum.xda-developers.com/showpost.php?p=78037053&postcount=685
You only use the zip and rom before the restart and then Gapps and Magisk after.
If nothing else works, then I'd suggest flash stock and start from step one.
The factory reset only, normally, only clears the data partition.
Your bootloader and system partitions are bad as TWRP is written to the bootloader and Gapps installs to the system.
Don't quote me on the bad bootloader though; worst case, you'll want a blankflash and flash stock before starting over again.
[EDIT]
I may have alleviated worst case scenario, read the bottom: https://forum.xda-developers.com/showpost.php?p=78046198&postcount=692
dougo007 said:
What happened is that you messed up the installation order.
https://forum.xda-developers.com/showpost.php?p=78037053&postcount=685
You only use the zip and rom before the restart and then Gapps and Magisk after.
If nothing else works, then I'd suggest flash stock and start from step one.
The factory reset only, normally, only clears the data partition.
Your bootloader and system partitions are bad as TWRP is written to the bootloader and Gapps installs to the system.
Don't quote me on the bad bootloader though; worst case, you'll want a blankflash and flash stock before starting over again.
[EDIT]
I may have alleviated worst case scenario, read the bottom: https://forum.xda-developers.com/showpost.php?p=78046198&postcount=692
Click to expand...
Click to collapse
I definitely got the installation order correct for the fresh install. I used the built-in updater in lineage to update the OS, so it's entirely possible that there's a slot issue related to that...
The firmware link at the bottom of your post was the very first thing I did.
A blankflash file I found that I think should be recent enough for my device just shows <waiting for device>. I ran ADB and it shows the device as connected, so I don't think it's a driver issue. I know nada about blankflash, though.
Researching now. Thanks for the help.
Horror Business said:
I definitely got the installation order correct for the fresh install. I used the built-in updater in lineage to update the OS, so it's entirely possible that there's a slot issue related to that...
The firmware link at the bottom of your post was the very first thing I did.
A blankflash file I found that I think should be recent enough for my device just shows <waiting for device>. I ran ADB and it shows the device as connected, so I don't think it's a driver issue. I know nada about blankflash, though.
Researching now. Thanks for the help.
Click to expand...
Click to collapse
I have a whole package I created with links to different XDA threads on this device, but I don't have it with me at the moment.
You will definitely need to know what variant you're using.
I found one for XT1900-1 and one for XT1900-7.
There is a phone button combo you'll need to use and good timing.
dougo007 said:
I have a whole package I created with links to different XDA threads on this device, but I don't have it with me at the moment.
You will definitely need to know what variant you're using.
I found one for XT1900-1 and one for XT1900-7.
There is a phone button combo you'll need to use and good timing.
Click to expand...
Click to collapse
I have XT1900-1.
Thanks!
Here is my 'data dump' from my text file on what to do in the worst case scenario; I grabbed and linked what I could together below.
Don't take the words as direct advice from me as I never did this myself before.
--------------------------------------------------------------------------------------------------------
Enter download Mode: Power & Volume - (down) for ten seconds [ or volume +]
blank flash (two different files, not sure which to use)
Generic Instructions:
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Device Instructions:
https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472
https://forum.xda-developers.com/showpost.php?p=77847019&postcount=606
https://forum.xda-developers.com/showpost.php?p=77847374&postcount=44
https://www.aryk.tech/2017/09/moto-x4-unbrick-solutions.html
use qualcomm driver first with blank flash
MAY NEED TO ENTER PC INTO TEST MODE:
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
(Restart computer)
***When you no longer need it.***
###To deactivate it we will use the following command.###
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
Once the two commands have been executed, we must restart our computer so that the changes take effect and this mode is deactivated correctly.
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile.
use manual and brick help to load system partition
ROMS: https://androidfilehost.com/?a=show&w=files&flid=229118
Data upload
There is one more file too big or here mentioned in the PDF.
I don't know which ROM is the best to use but you should use a PAYTON_FI for the XT1900-1
dougo007 said:
Data upload
There is one more file too big or here mentioned in the PDF.
Click to expand...
Click to collapse
Massive, massive thanks, man!
Got me rolling back to being able to flash a stock rom, which is good enough for me on this device!
I'm still guessing that slots jacked something up, but I'm not going to try to replicate the problem at this point, LOL!
One last note.
I noticed that flashing stock doesn't make the device genuine.
It appears that a trick I used to use on my old device works here; rooting with Magisk will mark the phone as certified.
To make sure this is the case, install the manager and if there is one RED and one GREEN; you're good to go on the install.
[EDIT]
Also, you can remove the unlocked bootloader warning with a patched image; I don't know if these two things will conflict though.
[EDIT 2]
I also don't know if either will conflict with OTA updates, assuming they work after you fixed your phone.
You can let me know below if you can provide any useful data.
If you have any other questions, make another post/thread. @Horror_Business