Related
Alright so today I bricked my g2 (not a huge problem, generally) installing this http://forum.xda-developers.com/showthread.php?t=2502789 on my vs980. I installed it normal then all my phone did was boot into a fastboot screen [700]udc_start() . So I am trying to unbrick through this guide http://www.lg-phones.org/how-to-flash-unbrick-lg-g2-back-to-stock.html and it only gets to 49% then says it does not work. If anybody here has a solution to this I beyond appreciate it.
Additional Note. I was on CWM and then I used Flashify to flash TWRP 2.6.3.2 img and then I tried installing rom and that's where it went down
Ars3nal said:
Alright so today I bricked my g2 (not a huge problem, generally) installing this http://forum.xda-developers.com/showthread.php?t=2502789 on my vs980. I installed it normal then all my phone did was boot into a fastboot screen [700]udc_start() . So I am trying to unbrick through this guide http://www.lg-phones.org/how-to-flash-unbrick-lg-g2-back-to-stock.html and it only gets to 49% then says it does not work. If anybody here has a solution to this I beyond appreciate it.
Additional Note. I was on CWM and then I used Flashify to flash TWRP 2.6.3.2 img and then I tried installing rom and that's where it went down
Click to expand...
Click to collapse
Try this method, I have had success with this method a couple of times already. Who is your carrier, there are more detailed info in your carrier development forums.
http://forum.xda-developers.com/showthread.php?t=2432476
Jimi Mack said:
Try this method, I have had success with this method a couple of times already. Who is your carrier, there are more detailed info in your carrier development forums.
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
It did the same thing and stopped at 49%...can't explain it.
Yeah sorry, I am on Verizon so I have done it with the TOT files not the other method. Check around your your carriers Development forum.
Hi Guys, i think that i have softbricked mi Zenpad :silly:
So, i have used KingRoot in order to have root permission, after i have use super_me or something like this in order to change KingUser app with SuperSu app, but after the reboot it has gone in bootloop
I have tried to reset it using standard recovery (by ASUS) but it doesn't works, it is still in bootloop.
Can you help me ? (again :laugh
Thanks to a Jappanase blog i was able to unbrick my tablet and install CM 13.0 without have a funcrional rom: {Mod edit}
------------------------------------------------------------------------
How to solve:
1_ Download the following zips in a folder
Code:
[URL="https://vasy.ru/TWRP/P024/"]https://vasy.ru/TWRP/P024/[/URL] TWRP
[URL="http://4pda.ru/pages/go/?u=http%3A%2...zip&e=48313529"]http://4pda.ru/pages/go/?u=http%3A%2...zip&e=48313529[/URL] CM 13.0
[URL="http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico"]http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico[/URL] G APPS
[URL="http://d-h.st/8FqR#"]http://d-h.st/8FqR#[/URL] ADB and other utilities . Thanks to @backwardastep
2_ Move CM 13.0 and G APPS in a sd card and insert it into the tablet
3_ Unzip z380klroot_w_xposed
4_ move the TWRP.img in the "z380klroot_w_xposed" folder
5_ open cmd on Windows and move in the z380klroot folder. Type:
Code:
cd C:\Users\XXX\Desktop\z380klroot_w_xposed
6_ Connect the tablet
7_ Then type:
Code:
fastboot boot twrpxx.xx.xx.img
the tablet will start to looking for a device
8_ Press power + "volume +" in order to put the tablet in recovery (you can also put the tablet in recovery mode before the point 7)
9_ Then it should boot a temporany TWRP
10_ From TWRP wipe all data and install first CM 13.0 and GAPPS as usual
Now you have a working CM 13.0
PS. i noted in the Andmen blog's that exist also an Resurrection Remix
Code:
[URL="https://mega.nz/#F!3JtglKKJ!JIL2MZnzTg1vgW8mLLd8kA"]https://mega.nz/#F!3JtglKKJ!JIL2MZnzTg1vgW8mLLd8kA[/URL]
Custom Kernel CM-13.0
For Asus P024 cm13 Z380KL
NEOX_P024-cm13-v1.0-U700-zram
The problem is twrp can't be touch, the display seems locked
bangdes said:
The problem is twrp can't be touch, the display seems locked
Click to expand...
Click to collapse
yeah, i have exaclty the same problem: http://forum.xda-developers.com/and...z380kl-unrootable-t3213933/page3#post69032596
i'm kinda of stuck :silly:
How do you flash back to ASUS's stock ROM? I downloaded 4.8.0_WW off 4PDA but it gives me an error when trying to flash it via TWRP. Any ideas?
xDark_ said:
How do you flash back to ASUS's stock ROM? I downloaded 4.8.0_WW off 4PDA but it gives me an error when trying to flash it via TWRP. Any ideas?
Click to expand...
Click to collapse
You cannot flash the stock rom from twrp.
Stock roms work only with stock recovery
giorgiofolle said:
You cannot flash the stock rom from twrp.
Stock roms work only with stock recovery
Click to expand...
Click to collapse
So I would have to reflash the stock recovery and use that to flash stock? If I use ASUS's FlashTool would that reset everything back to stock?
Sent from my Samsung SM-G930T using XDA Labs
xDark_ said:
So I would have to reflash the stock recovery and use that to flash stock? If I use ASUS's FlashTool would that reset everything back to stock?
Sent from my Samsung SM-G930T using XDA Labs
Click to expand...
Click to collapse
1. yes, you should flash before the stock recovery and then the stock rom
2. I don't know, i have never used asus flash tool, but i think that you should have anyway the stock recovery file
Again, i repeat, if someone know how copy the stock recovery, i can do it. My tablet have still the stock one and i could copy and post here !
I've tried to flash recovery image in adb fastboot and stock rom in asus flash tool but it doesn't work
Sent from my GT-I9300 using XDA-Developers mobile app
giorgiofolle said:
1. yes, you should flash before the stock recovery and then the stock rom
2. I don't know, i have never used asus flash tool, but i think that you should have anyway the stock recovery file
Again, i repeat, if someone know how copy the stock recovery, i can do it. My tablet have still the stock one and i could copy and post here !
Click to expand...
Click to collapse
bangdes said:
I've tried to flash recovery image in adb fastboot and stock rom in asus flash tool but it doesn't work
Sent from my GT-I9300 using XDA-Developers mobile app
Click to expand...
Click to collapse
Gonna try this:
{Mod edit}
(use GTranslate)
Do you have a link to the stock recovery @bangdes?
Edit: I flashed this (https://www.asus.com/zentalk/tw/thread-147621-3-1.html) and now I just get an ASUS logo that eventually goes to the "Powered by Android" screen. Gonna try flashing stock now.
Edit 2: Gave me an error 7. Gonna try charging it up and flashing it again while I research what's up.
Edit 3: tried booting TWRP over stock recovery and adb sideloading it. finished saying total xfer: 1.09x and booted me to a black screen once I tried rebooting (TWRP gave me a No OS warning) saying it couldn't find drivers for Qualcomm HD-9008. ****, I think I just hard bricked my tablet yet again. Rebooted into driver signature disabled mode and it says "unknown device". Can't even turn off the damn thing.
xDark_ said:
Gonna try this:
{Mod edit}
(use GTranslate)
Do you have a link to the stock recovery @bangdes?
Edit: I flashed this (https://www.asus.com/zentalk/tw/thread-147621-3-1.html) and now I just get an ASUS logo that eventually goes to the "Powered by Android" screen. Gonna try flashing stock now.
Edit 2: Gave me an error 7. Gonna try charging it up and flashing it again while I research what's up.
Edit 3: tried booting TWRP over stock recovery and adb sideloading it, booted me to a black screen once I tried rebooting saying it couldn't find drivers for Qualcomm HD-9008. ****, I think I just hard bricked my tablet yet again. Rebooted into driver signature disabled mode and it says "unknown device". Can't even turn off the damn thing.
Click to expand...
Click to collapse
my z380kl is latest (2016) version and cannot enter to recovery stock, or maybe the stock recovery doesn't exist.. it's weird
bangdes said:
my z380kl is latest (2016) version and cannot enter to recovery stock, or maybe the stock recovery doesn't exist.. it's weird
Click to expand...
Click to collapse
The stock recovery is just an Asus logo I think. That's what it is for me with the flashed recovery using the link above.
Sent from my Samsung SM-G930T using XDA Labs
I've tried thousand time and no luck, I found the stock recovery from 4pda. But I forgot the link
Ok, lil update. Found out a potential unbricking method:
{Mod edit}
Also this thread is just dedicated to this brick: {Mod edit}}
And here's a few others who have the same issue: {Mod edit}
According to a guy who natively speaks Russian, this is a hardbrick that can't be repaired without sending it in to the OEM.
Kinda wish I had a little birdie that could fly into the ASUS office (I've been there, actually pretty nice. Lounge chairs with tablets and phones on display to play with while you wait, and a TV that was playing Finding Nemo in Chinese. Plus staff was nice enough, I just played dumb about what happened lol) and just tell me what exactly I can do to fix this. Even worse, the one year warranty is almost up so I'm gonna have to fork over cash if I send it in to be repaired AGAIN. This makes me want to send this tablet off to repair and sell it off for a NVIDIA Shield or something, Jesus. I got burned by Asus with the ZF2 and yet I still fell into this trap. Same with Samsung, I guess I'm just a masochist or something. Anyways, currently juggling fixing/rooting my S7 along with school work, so it'll be a few days or so until I can start experimenting with this. On a sidenote, damn the OPO is good. Still flies after three years of daily usage
Back to factory firmware
I found pretty good guide here to help restore the z380KL back to factory firmware.
{Mod edit}
squall77 said:
I found pretty good guide here to help restore the z380KL back to factory firmware.
{Mod edit}
Click to expand...
Click to collapse
If you're going to spam, at least make an unbricking tutorial.
xDark_ said:
If you're going to spam, at least make an unbricking tutorial.
Click to expand...
Click to collapse
I apologize if it looks like a spam, I am just suggesting that you should at least try to restore the stock system partition before trying to flash stock rom using TWRP as it does not work with the custom ROM system partition. As far as I have tried I couldn't boot into stock recovery, maybe it doesn't have one on my model. I can only boot into fastboot.
Best bet is to try to boot into custom recovery and restore the stock system partition from a backup file and then flash the stock rom and see whether it works.
squall77 said:
I apologize if it looks like a spam, I am just suggesting that you should at least try to restore the stock system partition before trying to flash stock rom using TWRP as it does not work with the custom ROM system partition. As far as I have tried I couldn't boot into stock recovery, maybe it doesn't have one on my model. I can only boot into fastboot.
Best bet is to try to boot into custom recovery and restore the stock system partition from a backup file and then flash the stock rom and see whether it works.
Click to expand...
Click to collapse
No, I'm asking you that if you're going to spam your own site then at least make a tutorial that's useful, not just a tutorial everyone who wants to flash CM13 already knows how to do.
hi, pls help.
never got to step 9.
after type fastboot boot twrpxx.xx.xx.img, stuck at waiting devices
hafizhans said:
hi, pls help.
never got to step 9.
after type fastboot boot twrpxx.xx.xx.img, stuck at waiting devices
Click to expand...
Click to collapse
Can you boot into ADB normally? Like type in adb devices before you type in any commands
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 !!!!
Hi,
I have the issue that my g4 plus won't boot at from boot loader. I have flashed the 8.1.0 stock ROM, but am unable to boot into the system. It just boots to the dead android no command screen. I have tried the other methods in other threads to no avail. I also tried ADB side loading but it didn't work either as it did not recognize the .zip. Does anyone have any solutions?
Derpsherpa said:
Hi,
I have the issue that my g4 plus won't boot at from boot loader. I have flashed the 8.1.0 stock ROM, but am unable to boot into the system. It just boots to the dead android no command screen. I have tried the other methods in other threads to no avail. I also tried ADB side loading but it didn't work either as it did not recognize the .zip. Does anyone have any solutions?
Click to expand...
Click to collapse
If you try to flash the 8.1.0 stock rom it needs to be extract from the zip. You cannot flash the zip like a custom rom. But that's explained in the instructions in the first post.
Please make this sure.
strongst said:
If you try to flash the 8.1.0 stock rom it needs to be extract from the zip. You cannot flash the zip like a custom rom. But that's explained in the instructions in the first post.
Please make this sure.
Click to expand...
Click to collapse
Oh I fixed it nvm. I just forgot to boot my bad. I guess the thread is useless now.
I have a 8704V, that's stuck in bootloop now while trying to install LineageOS. I found a QFIL flashable rom but that also didn't work. My tab4 now just boot-loops on the lenovo screen.
I have twrp and fastboot working.
Is anyone with a 8704V and TWRP, willing to make a backup of his boot, recovery and system/system-image partition; and share it with me.? Thanks in advance.
suhridkhan said:
I have a 8704V, that's stuck in bootloop now while trying to install LineageOS. I found a QFIL flashable rom but that also didn't work. My tab4 now just boot-loops on the lenovo screen.
I have twrp and fastboot working.
Is anyone with a 8704V and TWRP, willing to make a backup of his boot, recovery and system/system-image partition; and share it with me.? Thanks in advance.
Click to expand...
Click to collapse
Responding to my own post, as it could help other in the future.
I spent days trying to work with QFIL and TWRP.
But the simplest solution is to use the 'Lenovo Smart Moto Assistant'. It's such a powerful tool. The firmware can be downloaded and flashed with a few clicks. The tab was back to life in a few minutes. The way it worked, seems like it also used the edl mode. I don't see any reason to use QFIL on a Lenovo device again, which was such a pain.
Do you mind sharing what version of twrp worked for your TB-8704V?
suhridkhan said:
Responding to my own post, as it could help other in the future.
I spent days trying to work with QFIL and TWRP.
But the simplest solution is to use the 'Lenovo Smart Moto Assistant'. It's such a powerful tool. The firmware can be downloaded and flashed with a few clicks. The tab was back to life in a few minutes. The way it worked, seems like it also used the edl mode. I don't see any reason to use QFIL on a Lenovo device again, which was such a pain.
Click to expand...
Click to collapse
samxda said:
Do you mind sharing what version of twrp worked for your TB-8704V?
Click to expand...
Click to collapse
The one form here
https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
https://androidfilehost.com/?fid=1322778262903982743
Great, tyvm!
Btw, have you seen this? Any of these were boot-looping your device?
https://forum.xda-developers.com/th...om-lineageos-14-1-lenovo-tab4-8-plus-t3948223
suhridkhan said:
The one form here
https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
https://androidfilehost.com/?fid=1322778262903982743
Click to expand...
Click to collapse
samxda said:
Great, tyvm!
Btw, have you seen this? Any of these were boot-looping your device?
https://forum.xda-developers.com/th...om-lineageos-14-1-lenovo-tab4-8-plus-t3948223
Click to expand...
Click to collapse
Already tried both. Noting but bootloops. So I decided to stay with stock rooted with magisk.