I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.
shaggy9585 said:
I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.
Click to expand...
Click to collapse
we need a story, for starters what did you do/happened before you got into fastboot?
XxZombiePikachu said:
we need a story, for starters what did you do/happened before you got into fastboot?
Click to expand...
Click to collapse
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?
shaggy9585 said:
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?
Click to expand...
Click to collapse
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock
XxZombiePikachu said:
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock
Click to expand...
Click to collapse
is there a way to flash a rom using adb while in twrp or fastboot?
shaggy9585 said:
is there a way to flash a rom using adb while in twrp or fastboot?
Click to expand...
Click to collapse
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)
XxZombiePikachu said:
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)
Click to expand...
Click to collapse
now i just need to figure out whats going on with the touch sensor. idk if its the phone or just twrp
Related
I've rooted my phone...not a problem.When I try to boot into recovery mode using and app like TWRP or ROM Manager premium, I get past the LG G2 splash screen, then I get the belly-up android guy with a red asterisk...how can i get around this to flash my ROM? What am I doing wrong?
HeatM1ser said:
I've rooted my phone...not a problem.When I try to boot into recovery mode using and app like TWRP or ROM Manager premium, I get past the LG G2 splash screen, then I get the belly-up android guy with a red asterisk...how can i get around this to flash my ROM? What am I doing wrong?
Click to expand...
Click to collapse
if I remember correctly that means your recovery did not flash correctly so I recommend using either flashify or freegee from playstore and retrying
It is actually the stock recovery. Try again flashing TWRP or CWM
Sent from my LG-VS980 using Tapatalk
XxZombiePikachu said:
if I remember correctly that means your recovery did not flash correctly so I recommend using either flashify or freegee from playstore and retrying
Click to expand...
Click to collapse
I installed Flashify, rebooted the phone...now its stuck in fastboot mode....what can I do?
HeatM1ser said:
I installed Flashify, rebooted the phone...now its stuck in fastboot mode....what can I do?
Click to expand...
Click to collapse
ok there is a guide here somewhere which explains that if you were trying to install recovery and then go stcuck in fastboot mode you have to get the stock recovery back let mee if I can find the guide and i'll report back
re-edit: try this thread http://forum.xda-developers.com/showthread.php?t=2477595 also you can find needed files here http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware make sure you download correct files for your firmware
25536955 22
XxZombiePikachu said:
ok there is a guide here somewhere which explains that if you were trying to install recovery and then go stcuck in fastboot mode you have to get the stock recovery back let mee if I can find the guide and i'll report back
re-edit: try this thread http://forum.xda-developers.com/showthread.php?t=2477595 also you can find needed files here http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware make sure you download correct files for your firmware
Click to expand...
Click to collapse
Thanks a lot! I followed that guide, and afterwards I was no longer even able to get into recovery/download mode....so I though I was even worse trouble....since one the the instructions was to erase the LAF file and flash it again with a downloaded LAF image, I decided to go to the link with all the files you provided and flash each of them....rebooted, and the phone was able to get into recovery mode again...Then I pushed the file for my phone ( http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware) using Uptest (R&D Tool), rebooted and the phone worked.
Hey guys, Hopefully somebody can help me here.
Basically i flashed & rooted my D802 to 4.4.2 using this method > http://forum.xda-developers.com/showthread.php?t=2680789
All was running fine however somewhere along the line something has messed up! I tried to boot into recovery and now im hit with "Secure Booting Error! Cause : boot certification verify" instead of TWRP!
Ive tried to use this method > http://forum.xda-developers.com/showthread.php?t=2625044 to flash back to stock and unroot BUT when i get to step 5. of method 1. instead of asking to to Select Country & Language it starts the LGMobile Support Tool and the tool tells me i have the latest available software for my device.
The phone is running fine and i can get into download mode.
Thanks in advance for any help.
Anybody got any ideas?
OK ive managed to boot into recovery(TWRP v2.6.3.3)I was gonna try to push a new ROM to my device via ADB sideload, When i select the ADB sideload feature TWRP just gets stuck on "Starting ADB sideload feature..." and sideload wont start!
Anybody got any ideas?
Thanks.
ATOJAR said:
Hey guys, Hopefully somebody can help me here.
Basically i flashed & rooted my D802 to 4.4.2 using this method > http://forum.xda-developers.com/showthread.php?t=2680789
All was running fine however somewhere along the line something has messed up! I tried to boot into recovery and now im hit with "Secure Booting Error! Cause : boot certification verify" instead of TWRP!
Ive tried to use this method > http://forum.xda-developers.com/showthread.php?t=2625044 to flash back to stock and unroot BUT when i get to step 5. of method 1. instead of asking to to Select Country & Language it starts the LGMobile Support Tool and the tool tells me i have the latest available software for my device.
The phone is running fine and i can get into download mode.
Thanks in advance for any help.
Click to expand...
Click to collapse
The ROM you flashed is from my thread. I'm not sure why you think custom recovery remains available? Unless I've missed something else you did. It is overwritten by the stock ROM when flashed. Hence I clearly stated that custom recovery will no longer be available.
I don't know what "messed up" with the ROM?
I suggest you revisit the page you used and try the alternative method if you really fell the need to downgrade...
Well after 5 house of messing around i managed to ADB push CM11 too my device, Boot the phone then connect to my PC then re-flash 4.4.2 & root using this method > http://forum.xda-developers.com/showthread.php?t=2680789
Think ill just stick to 4.4.2 lol.
ATOJAR said:
Well after 5 house of messing around i managed to ADB push CM11 too my device, Boot the phone then connect to my PC then re-flash 4.4.2 & root using this method > http://forum.xda-developers.com/showthread.php?t=2680789
Think ill just stick to 4.4.2 lol.
Click to expand...
Click to collapse
Yes, that's my ROM...
Sent from my LG-D802 using XDA Premium 4 mobile app
Hi all,
I have an LG D802, was running standard ROM just rooted and with PhilZ recovery. Well I was silly and tried an OTA update, and got stuck at recovery...unfortunately I panicked, cleared everything and tried to flash another ROM but I'm still stuck at recovery.
I tried the instructions in the thread about being stuck after an OTA update but as I;ve formatted the sd partition it didn't work.
I want to go back to stock, I just have no idea how....I have ADB access though if that helps! I'm not really experienced in this kind of thing so please dumb it down for me!
Any help much appreciated!
Callum
calistheman said:
Hi all,
I have an LG D802, was running standard ROM just rooted and with PhilZ recovery. Well I was silly and tried an OTA update, and got stuck at recovery...unfortunately I panicked, cleared everything and tried to flash another ROM but I'm still stuck at recovery.
I tried the instructions in the thread about being stuck after an OTA update but as I;ve formatted the sd partition it didn't work.
I want to go back to stock, I just have no idea how....I have ADB access though if that helps! I'm not really experienced in this kind of thing so please dumb it down for me!
Any help much appreciated!
Callum
Click to expand...
Click to collapse
can you get into download mode either try the adb reboot download mode or turn phone entirely off and hold volume up(only volume up) and plug it into the pc usb, if you can use the back to stock guide to get your phone working again
XxZombiePikachu said:
can you get into download mode either try the adb reboot download mode or turn phone entirely off and hold volume up(only volume up) and plug it into the pc usb, if you can use the back to stock guide to get your phone working again
Click to expand...
Click to collapse
hi no I cannot get in to download mode by any means.
calistheman said:
hi no I cannot get in to download mode by any means.
Click to expand...
Click to collapse
have you tried adb pushing/sideloading a rom and flashing to see if it helps?
XxZombiePikachu said:
have you tried adb pushing/sideloading a rom and flashing to see if it helps?
Click to expand...
Click to collapse
Yes trued flashing a custom ROM, however in my haste to try and stop the OTA forcing me to recovery I may have formatted some partitions I shouldnt have.
Can I restore everything by downloading the kdz with all the correct IMG files in, converting to a flash able zip (saw a guide on here) and trying that?
calistheman said:
Yes trued flashing a custom ROM, however in my haste to try and stop the OTA forcing me to recovery I may have formatted some partitions I shouldnt have.
Can I restore everything by downloading the kdz with all the correct IMG files in, converting to a flash able zip (saw a guide on here) and trying that?
Click to expand...
Click to collapse
Yes that is possible to do I should know because we have something like that for d800
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Edit: I fixed it. had to manually extract and reflash some files from a very useful restore to stock tool.
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
Thank you for all of the help so quickly.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
thanks
[email protected] said:
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
Click to expand...
Click to collapse
fixed it thank you!
thanks
benjmiester said:
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
Click to expand...
Click to collapse
fixed it thank you!
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Great news! You're very welcome. I was in that exact same situation with my old Xperia Z2. It's pretty scary.
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
DonKilluminati23 said:
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
kagarii said:
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
Click to expand...
Click to collapse
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
It's possible, through tools like this. I don't know too much of the topic.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Sherrillface said:
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Click to expand...
Click to collapse
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
jDally987 said:
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
Click to expand...
Click to collapse
Nothing it just vibrates as soon as i hit factory reset then bootloops now it wont even go into recovery just fastboot screen but cant get fastboot to work at all and have all drivers android studio etc. Nothing will work need a new solution
It was hash kernel it corrupted all 64 gigs of storage and music etc. Had to return to stock via auto flash firmware.
Mine is XT1572 device. Since the mentioned tool was not available for this model, I took the chance with XT1575 tool. It did all the steps but the issue has become worse. Now, my device is automatically getting On and OFF in seconds and does not boot beyond the bootloader 'unlocked' warning screen. Please please please help !!!!