Related
I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?Even my the the bootloader unlock warning reboots several times before getting to the never ending bootanimation
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files
There's a number of guides in this subforum that goes through flashing the stock firmware for your phone. The reason you're getting bootloops is because there's currently no stable way to get root access on Lollipop for this phone, but it is being worked on.
ADB can be a bit finicky, so it'd probably be easier to have your ROM on the phone itself, whether in the data/media/ folder in Internal Storage, or on an SD card, since neither are wiped whenever you factory reset or clean your phone. TWRP 2.8.2.0 and above allows you to enable MTP mode so you can move your files straight onto or off your phone.
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
sleekykenny said:
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
Click to expand...
Click to collapse
Did you try manually selecting the driver is device manager?
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Traediras said:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Click to expand...
Click to collapse
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
sleekykenny said:
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
Click to expand...
Click to collapse
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Traediras said:
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Click to expand...
Click to collapse
Thanks Dude, After your last message I rechecked the mfastboot-v2 folder on the thread and realised the only new file in there was the mfastboot.exe file so i quickly googled it and saw another thread in which i found the file.I downloaded it and then executed all the commands. Goshh I finally saw my phone boot up in a long time which brought a huge smile to my face.
I would like Thank all of you guys who took the time out to visit this thread and give me suggestions. THANK YOU BROS
I really appreaciate it. Happy new year
Glad to hear everything worked out for you. Happy New Year to you too.
Duplicate thread created by OP
Original is here
Please do not create multiple threads again.
Thread closed
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
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!
When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?
did you ever unlock the phone....?
Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.
Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed
You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.
I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.
I reasked the question in Q and A. Please help some one.
You start over. LG bridge.
Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks
* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h
the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
I tried everything in this thread:
http://forum.xda-developers.com/p8lite/general/hand-fixing-bootloop-t3464740
to no avail. One thing I noticed is that the link given in the Fastboot menu links to a Chinese (?) website - http://zh.ui.vmall.com/emotiondownload.php?mod=restore - I'm not sure if this is indicative of me having a device for the East Asian markets and if there are any software differences?
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
GfIsGonnaKillMe said:
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
Click to expand...
Click to collapse
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
XePeleato said:
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
Click to expand...
Click to collapse
Just the very static image, it doesn't even go into the animation.
Edit: this is a newly bought P8 Lite, the Box says Android 5.0, don't know if relevant?
by now I've wiped stuff with TWRP more times than I can count, and tried manually flashing the boot, recovery, cust and system of b132, b170, b190, and b564 to no avail
GfIsGonnaKillMe said:
Just the very static image, it doesn't even go into the animation.
Click to expand...
Click to collapse
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
XePeleato said:
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
Click to expand...
Click to collapse
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
GfIsGonnaKillMe said:
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
Click to expand...
Click to collapse
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
XePeleato said:
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
Click to expand...
Click to collapse
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
GfIsGonnaKillMe said:
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
Click to expand...
Click to collapse
[ 8.389146s][pid:1,cpu1,init]BUG: failure at /cloud/jenkinswh/ci/workspace/Alice_Channel_ANDROID/android_code/kernel/drivers/video/hisi/hi6220/balong_compose.c:613/vpu_on_notice_ade()!
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
XePeleato said:
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
Click to expand...
Click to collapse
It is very nice of you to look into this! Worst case scenario, the device was broken from the start and has now lost its warranty (though I booted it up once without problems right in the beginning).
For the main problem - which is my gf - I simply factory reset my own P8 Lite and put the stickers from the new one on it. Now I don't have a phone, but at least I get to keep my relationship
ninja edit: checking my terminal history, I remember trying to fix the not-installing SuperSU by trying fastboot -w and fastboot format cache as recommended elsewhere, but both failed
Playing around with it again, it seems the only fastboot commands working are fastboot flash and fastboot reboot, everything else is giving a "FAILED (remote: Command not allowed)" error, even for things like getvar
flashing b564 allows me to get into stock recovery, will try dload update now!!
EDIT: IT WORKS!!!
Things I learned from this:
- it is important to flash right update version
- use dload if you can boot into stock recovery
- recovery will only be loaded if not connected via USB, otherwise EMUI crap will launch
- vendors do not always have correct information on device package!!
GfIsGonnaKillMe said:
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
Click to expand...
Click to collapse
delete
For unbrick, its easy if your bootloader is unlocked.
Just need time and flash few files by adb (downgrade)and update your device's to the android version you want.
If you want I have all the necessary files.
After your device's is like at his first boot.
Sent from my SM-N9005 powered by QS-N9005-LP