Related
Hello guys,
i bricked my vs980 and now i need help.
Here is the story.
I was on 4.4.2 ROM. i installed towelroot and rooted phone. Then i downloaded autorec for vs980 to install twrp. After reboot all i can see on phone are colorful lines. Phone wont boot to OS (after few seconds it auto reboots). I have no download mode or fastboot mode. ALL i have is twrp installed, but i cant see anything on screen (anythinkg usefull - only those multi-colored lines). In twrp i can enter sideload mode.
When i enter sideload mode i see i adb my phone and it says im in sideload mode. So using adb i can install something (at least i think so).
Is it possible to unbrick my phone or is it totally lost?
I think i would need to somehow install original partitions on it using adb sideload.
I dont know how. i tried installing some roms, no success. Still phone wont boot to OS. I propably messed something with partitions when i was trying to unbrick it.
I tried installing kernel KK_Kernel_VS980_jdi, it doesnt help.
Any help appreciated. Thanks in advance.
// edit
Restoring download mode would be good. I would flash kdz then. But no idea how to do it having adb sideload only
//edit 2
I managed using sideload to flash 26a bootskatck and xdabbeb 2.3.0 rom. Then i flashed KK_Kernel_VS980_jdi which should repair those white lines. Now in recovery i still have all those lines (cant see anything on screen), but phone boots to OS. In OS, there are some lines but i can see everything on the screen (KK_Kernel_VS980_jdi helped). I guess now i need to restore download mode. But how?
//edit 3
I restored dl mode using zip from xdabbeb 2.3.0 thread and managed to install 24a using kdz method. It partiallly repaired phone - there are some lines, but according to info found on net they will disappear after some time (24h approx).
Rafal.
Hello,
So I have a P7 at B126. I tried rooting it with kingroot and tried to install TWRP. I got to the part where you have to use fastboot to flash the img and it fails so I gave up. Now I am trying to get into recovery and I can't. It just either goes to a black screen or a Boot failed screen.
Thanks in advance
Hi, I'm a little confused right now. Explain what you did so far a bit more detailed, so we could help you.. Which instruction were you are following? What was the exact error? Is your bootloader unlocked? Can you boot normally?
l3Nni said:
Hi, I'm a little confused right now. Explain what you did so far a bit more detailed, so we could help you.. Which instruction were you are following? What was the exact error? Is your bootloader unlocked? Can you boot normally?
Click to expand...
Click to collapse
I can boot normally.
What I did was this.
I followed the guide to root my phone. Rooted it and then tried to install the TWRP custom recovery. It failed at the installing the recovery for some permission error. So I stopped trying to install it. Now I apparently don't have a recovery at all.
I also installed some root apps like SetCPU, Xposed(Which didn't work), SuperSU(Which didn't Work)
If I try to adb reboot recovery it just takes me to the boot failed screen with the android logo on it. If I try using the Power + Down button it just shows me the huawei ascent P7 screen and just go black.
Also when I go to the fastboot/rescure mode it says my bootloader is unlocked.
Thanks for the reply.
Ah okay. So, boot into the fastboot mode, put the recovery.img in the adb folder on your pc, run cmd and type 'cd c://..' (location of adb folder), then 'fastboot flash recovery [name of recovery.img]' (for example 'fastboot flash recovery recovery_twrp.img'). Now you should get a working recovery.
Are you sure you really got root access? Eventually due to this you got the permission error..
l3Nni said:
Ah okay. So, boot into the fastboot mode, put the recovery.img in the adb folder on your pc, run cmd and type 'cd c://..' (location of adb folder), then 'fastboot flash recovery [name of recovery.img]' (for example 'fastboot flash recovery recovery_twrp.img'). Now you should get a working recovery.
Are you sure you really got root access? Eventually due to this you got the permission error..
Click to expand...
Click to collapse
I do because adb has admin permissions but fastboot doesn't. I tried that with trying to flash twrp on my p7 but i get a failed error after like a second I the command. So I tried flashing a stock recovery and it throws the same error in fastboot.
When I type fastboot devices I get this
? fastboot
No id for my phone but adb sees it.
Ok, your pc does obviously not recognize the p7 in fastboot mode. Did you install the Hi Suite? Through this way you should get the correct drivers (maybe even update/reinstall). If this does not help, I think I can't help you, sorry. You may wait for more help or google what do when the device isn't recognized in fastboot.
Just flash the newest SuperSU.zip when you got a recovery.. That should fix problems with root apps/ the su binary.
Offtopic: I'm not sure if you noticed, but, you're running a pretty old firmware.. You may think about updating
l3Nni said:
Ok, your pc does obviously not recognize the p7 in fastboot mode. Did you install the Hi Suite? Through this way you should get the correct drivers (maybe even update/reinstall). If this does not help, I think I can't help you, sorry. You may wait for more help or google what do when the device isn't recognized in fastboot.
Just flash the newest SuperSU.zip when you got a recovery.. That should fix problems with root apps/ the su binary.
Offtopic: I'm not sure if you noticed, but, you're running a pretty old firmware.. You may think about updating
Click to expand...
Click to collapse
Hi Suite installed and correct drivers are loaded(I hope) and yes thats why Im trying to get this fixed because it wont even let me update firmwares
Try on another pc.. You could also try flashify (look in Google play), but in case of a softbrick you have real problem. Do this on your own risk, most times nothing bad will happen, but it could!
I would recommend to flash the stock recovery, update up to B621 and then installing a custom recovery.
can't boot into recovery
stoutrouge said:
Hello
So I have a P7 at B126. I tried rooting it with kingroot and tried to install TWRP. I got to the part where you have to use fastboot to flash the img and it fails so I gave up. Now I am trying to get into recovery and I can't. It just either goes to a black screen or a Boot failed screen.
Thanks in advance
Click to expand...
Click to collapse
Hi mate.
1. Use your pc, Go shuame.com and download "rom flash program".
2. Enter fastboot&rescue mode and connect your phone and PC
3. The program will recognize your phone.
4. Download anyrom and flash by the program.
The process will not complete but you will have Shuame recovery.
But my case it didn't work properly
5. I downloaded CWM from here "pan.baidu.com/s/1dDq0qcT" password :bttc
Start this program with connect your phone and press nomber 1 and ENTER.
I don't exactly remember my phone was on fastboot & rescue mode or recovery mode.
But I could get recovery and did rom flash so it was fixed.
*****from: Godfrey Peligrino ---sorry i dont know how to post BUT, this guide helped me with my p7 L10 B619..just connect it to pc and let it boot over and over and when pc acknowledge you phone..click rom and just wait if not do it again..hope this will help you too..the writings is on chinese so just copy the english thumbnails before you proceed to download...(QUOTE) THANKS TO THE GUY WHO POST THIS....HE IS TOMODACHI5..
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
Ok so I was going about Trying to flash TWRP it wouldnt go. Tried a few times etc, nothing, so i gave up.
Now when i reboot or turn off and power up, i get a N/A in the top corner for a few seconds but then it boots up fine. But i cannot do a backup & reset, and i cant get into recovery now.
I get a start up failed your devices didnt start up successfully use the software repair assiant on your computer,
bottom says ap fastboot flashmode secure
error: failed to load kernel
fastboot reason: fall-through from recovery boot mode
but i can toggle to Start and it boots fine.
Computer now does not see the phone when i plug it in, it dont make a sound and is not in the device manager, also when i reboot to fastboot, it still isnt seen at all. flashing_unlocked so i can flash. but cant use adb since pc wont reconize phone now, and i cant reset.
So i can use the phone like normal atleast, but cant reset or access recovery. its like it just inst there
any ideas???
Thanks
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Jtaxel said:
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Click to expand...
Click to collapse
It would help to know what model your device is for one thing. Also, what command exactly did you use to flash the recovery? It almost sounds like you flashed the recovery to the wrong place or you did the erase command before trying to flash and borked the recovery partition.
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Jtaxel said:
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Click to expand...
Click to collapse
Try this twrp. It should work fine. Change the name to recovery.img and flash it
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-08-21_14-10
Jtaxel said:
The TWRP on this site from git hub was only a zip file not in .img format,
Click to expand...
Click to collapse
You unzip to extract the img file.
ST Dog said:
You unzip to extract the img file.
Click to expand...
Click to collapse
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
That is the source not the image. Click on the link that ends with .img not .tar and you'll get an img
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Jtaxel said:
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Click to expand...
Click to collapse
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Jason M. said:
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Click to expand...
Click to collapse
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Jtaxel said:
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Click to expand...
Click to collapse
First of all that error is normal. Second, the img is right there on the page I posted the link to. I even posted a screenshot of me downloading it from there. I don't see any reason why I could download the img and you can't. I give up.
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Jtaxel said:
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Click to expand...
Click to collapse
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Jason M. said:
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Jtaxel said:
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Click to expand...
Click to collapse
Ok, try:
fastboot erase DDR
That should solve your booting problem. I knew it was one or the other. Ignore the twrp asking for password and click on the mount settings and you'll see a little check box that says "mount system read only". Uncheck that box
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Jtaxel said:
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Click to expand...
Click to collapse
If you flashed the force encrypt noverity zip yes. If you don't want enryption or want it to be optional to encrypt use the one that says opt encrypt. This is all gone over possibly hundreds of times in numerous threads. You should do a little searching and reading.
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
My bad. Often a .img file is zipped because .img gets treated as a picture.
And you can also extract .img files from flashable zip releases.
Didn't think you might have grabbed a source code zip.
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon