So I tried to update twrp via some app recommended by a friend and now cannot get into recovery at all. I've tried every way possible and nothing. I tried to push the recovery img via adb and my laptop won't recognize my phone when I connect it.
I'm stumped and am hoping for some help.
mpetruzz said:
So I tried to update twrp via some app recommended by a friend and now cannot get into recovery at all. I've tried every way possible and nothing. I tried to push the recovery img via adb and my laptop won't recognize my phone when I connect it.
I'm stumped and am hoping for some help.
Click to expand...
Click to collapse
If you're rooted and on KitKat, try using Autorec to flash it. It does the other changes required to re-open the exploit so a recovery can be flashed.
Related
I did root, installed custom recovery, factory reset, update ota to 10e, phone stuck in recovery mode any help
i am in the same boat and would love some help as well
Hi codemans I bought the OTG cable try to connect phone to a USB stick as it will let you know
i have been in getting help from an xda user named charlieb620. he gave me this link http://forum.xda-developers.com/showthread.php?t=2451696 to fix it i just need to get adb working because every time i press the terminal command in twrp it brings up the file manager.
edit also i seem to be having trouble getting the right drivers.
You fixed phone?
X1053, rooted and unlocked bootloader on T Mob US
Tried to install a new kernel but it failed. Wiped cached (factory reset in twrp) and now it won't boot past the animation logo.
As its not booted into the OS, windows won't recognize it as a device so i can't install a new rom to try again. Windows 8 'bings' when I connect it but it won't load as a drive.
I CAN get into AP Fashboot Flash Mode If I then go to Recovery, it still takes me to twrp. But there are not zip files to install that work and I can't work out how to copy them over without windows recognizing the device?
Thanks in advance
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
kj2112 said:
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
Click to expand...
Click to collapse
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
emailrob said:
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
Click to expand...
Click to collapse
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Cyphir said:
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Click to expand...
Click to collapse
OK panic nearly over! I managed to get it flashed using RDS lite. 4.4 is back on now, although I lost my root Not sure I want to go down the whole downgrade to 4.2.2 etc but I'll see. Thanks again
Just adding a reply in case anyone has a similar issue.
RSDLite managed to get the firmware back on. It lost root, but what actually happened is the recovery got deleted / corrupted.
So i went back through the rooting guide which started by adding twrp and then flashing. Rebooted, and SuperSU tells me all is OK and root is there.
:laugh:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
nhizzat said:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
Click to expand...
Click to collapse
Its all working OK now thanks. I just flashed 4.4 again and re-installed TWRP.
I need some help...I updated my firmware and I must of updated with the wrong firmware...did they one with stock recovery or something. Now my phone doesn't have a custom recovery and I do not have root. I tried to download the trwp tool and flash but it says I do not have root. Also when I try to adb connect to my phone it doesn't recognise that the device is there. I am running Insert Coin 4.4.4 version 5.03. Any help is much appreciated! Also I should mention the firmware was from Captain Throwbacks thread with the latest. I am also Soff.
Very strange @Captain_Throwback's firmware should not have stock recovery included.
You can fastboot flash twrp.
ADB = OS/Recovery
Fastboot = Bootloader
My computer won't even recognize my phone now so I can't flash anything through fastboot. The command prompt says waiting for device
kpahl1973 said:
My computer won't even recognize my phone now so I can't flash anything through fastboot. The command prompt says waiting for device
Click to expand...
Click to collapse
Are you in fastbootusb ?
Yes fastbootUSB and its in red letters
kpahl1973 said:
Yes fastbootUSB and its in red letters
Click to expand...
Click to collapse
Unplug phone
Uninstall everything HTC and reboot PC
Install these drivers
Plug phone in (drivers should install)
If not try this:
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Thanks that worked...flashed the recovery successful but wont let me go into it. I think its because I am not rooted. Do I just use the all in one tool to get root back?
kpahl1973 said:
Thanks that worked...flashed the recovery successful but wont let me go into it. I think its because I am not rooted. Do I just use the all in one tool to get root back?
Click to expand...
Click to collapse
If it flashed successfully you should be able to get into recovery.
Are you sure you flashed the correct version? There are several for the M8.
I ended up flashing another version and I got into recovery. Root Checker still says I dont have root so I am going to wipe and reflash my rom. Hopefully that will do it. Not sure what happened but I really appreciate the help with getting the drivers corrected so I could communicate with my device again. With out adb I didnt know what I was going to do.
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..
Good morning i just got my lg g4 yesterday i was able to root it and flash custom recovery twrp via adb yesturday i even flashed some roms but today no matter what i do i cant get adb to work i keep on getting unathorized. On adb im stuck i cant get to boot to twrp either every time i try to whit the buttons vol down power at factory resets im stuck on exorsism rom but because i factory reset it dont got super su i tried diffrent computers and i get same error i uninstall android sdk and install whit no luck i tried lg flash tool to flash KDZ file gives me error can't connect to network try again in a few minutes can some help is their away to boot to twrp whit out adb ? Or how can. I fix the unauthorized on adb i think the problem is in my phone i tried diffrent computers windows 7 and 10 any help will greatly appreciates thanks
Sent from my LG-H811 using XDA-Developers mobile app
Did you try USB 2.0, if you a have a USB3.0 port it causes problems,
does your G4 serial starts with serial 505 to 510 and harware 1.0 ? those seems affected by the hardware flaw that makes boot loops
I read somewhere in here that serials 601and upper have the bootloop flaw fixed
Anyway, if you have an SD card installed, with the phone off remove it
and try again without the SD card
sometimes that helps
looks like G4 is a unstable beast
I did the same thing, I still haven't gotten adb working again but you can boot into recovery via kernel auditor. Or do a factory reset via the hardware keys and it will take you to twrp.
Sent from my LG-H811 using Tapatalk
I'm stuck at pretty much the same juncture. Kernel Auditor requires root to function (which we both seem to have lost) and the hardware buttons/factory reset just do that then boot me back into the rom. I also assume it's something with the phone since it reads "unauthorized" on 3 separate machines. Any other thoughts guys?
Also it has become apparent that although I fastbooted into TWRP initially, it did not stick. Leaving me with stock recovery, and clueless how to flash a recovery without ADB access.
@oogsaggie this what i did to get it fixed just download LGUP, put it in download mode, download the 20i KDZ file, and go back to stock 20i. and then root again make sure you permanently flash twrp move the twrp. image to your phone and flash iy from twrp
Sent from my LG-H811 using XDA-Developers mobile app
COCODRILO45 said:
@oogsaggie this what i did to get it fixed just download LGUP, put it in download mode, download the 20i KDZ file, and go back to stock 20i. and then root again make sure you permanently flash twrp move the twrp. image to your phone and flash iy from twrp
Sent from my LG-H811 using XDA-Developers mobile app
Click to expand...
Click to collapse
@COCODRILO45 Ended up doing exactly that. Wish I had seen your post earlier, but regardless great minds and all that stuff. For future reference I think COCODRILO45's solution is the most painless way to go. Cheers!