Related
A while earlier I was trying to enable tethering on my at&t N6 by editing the build.prop and after the reboot it's stuck in a boot loop. I don't imagine that this is important but it doesn't get to the dots animation; just white Google and the unlock at the bottom. I am still able to get into fastboot and recovery (stock one). I have a backup of the correct build.prop in the /system file named build.prop.back , so I'm hoping that there's a way to revert to that without needing to wipe my device again, but I'm not sure.
I found this thread, however my computer isn't recognizing the device when it's in recovery mode. I have the fastboot drivers installed (needed to root), so that may be why but, again, I'm not sure. the adb devices command shows that there is no device, I imagine because the driver is not installed.
any help would be appreciated. thanks in advance.
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
jj14 said:
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Unfortunately that didn't fix the problem.
Do you know if the fastboot driver and recovery driver would be different? As far as I can tell from my research, I think they're the same, but I could be wrong. Hopefully that's the problem and you can direct me towards the correct driver.
If I select "show hidden devices" in the device manager, it shows the phone as ADB Interface, and I tried undating the driver for that but it said it was already up to date. not sure what to do from here.
Thanks for your help.
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
jawmail said:
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
Click to expand...
Click to collapse
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
momo5732 said:
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
Click to expand...
Click to collapse
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
jawmail said:
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
Click to expand...
Click to collapse
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
momo5732 said:
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
Click to expand...
Click to collapse
Cool glad it's working. Yes backup=nandroid
It's cool now I've also noticed the computer recognizes phone in TWRP. You can drag and drop files onto the phone while it's in TWRP not just booted in android, couldn't do that before unless I'm wrong which is often. This is really cool as I always forget a file or two or its location on SD card.
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.
sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it
akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.
sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!
sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.
rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!
sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...
Please does anyone have a solution to this? please help me
Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?
Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.
i did that but no response.
Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
have you tried fastboot oem unlock again ?
uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk
claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.
holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.
Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.
Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!
You can lock boot loader, you just have to make sure your phone boots first before locking it
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?
Hello there, this is my first post here so go easy on me
So I got a new P9 yesterday and I immediately set to work trying to put Lineage OS on it. It took me ages to get a bootloader unlock password but I managed to unlock it in the end. Then I went ahead and installed TWRP. TWRP launched fine, and I proceeded to wipe and attempt to install the Lineage zip from the external SD.
That's when things started to go wrong. At first, during install, it threw an error about not being able to mount the system partition. I've seen this before on my Galaxy S4 and solved it easily by reformatting the partition. So I tried that. It still didn't work, and over the next 4 or 5 hours I tried everything Google and I could think of, and now the phone is completely gone.
I can't factory reset (a bunch of cannot mount errors), format data (same), advanced wipe (same) or change file system (same). The system partition can be formatted but it still says it cannot be mounted. The data partition looks like it's totally gone. In fastboot, when I try things like 'fastboot erase system' or 'fastboot erase data', I get 'FAILED (remote: Command not allowed)'. I can, however, still do 'fastboot flash recovery [twrp.img], and it'll flash the recovery. I used to be able to do that to data and system too but now I can't anymore.
Something I want to try is to flash it manually with fastboot back to the manufacturer recovery and rom, but my Google-fu apparently isn't good enough to find one. A big problem I'm having with this is the fact that this phone came all the way from China and therefore is a Chinese model (EVA-DL00) and I'm searching in English. When I search in Chinese I can see the words EVA-DL00 everywhere but my Chinese is nowhere near good enough to navigate all that.
So I guess what I'm asking is:
1. Does anyone know why I can't mount the data partition? I've considered maybe its encryption or something but I really have no idea.
2. Does anyone know how I can completely return my phone to stock? Where can I find images for EVA-DL00?
3. If I take this in for repairs, is it possible that it's bricked so badly that they won't be able to repair it?
I'd greatly appreciate any help I can get
Thanks!
Infraxion said:
Hello there, this is my first post here so go easy on me
So I got a new P9 yesterday and I immediately set to work trying to put Lineage OS on it. It took me ages to get a bootloader unlock password but I managed to unlock it in the end. Then I went ahead and installed TWRP. TWRP launched fine, and I proceeded to wipe and attempt to install the Lineage zip from the external SD.
That's when things started to go wrong. At first, during install, it threw an error about not being able to mount the system partition. I've seen this before on my Galaxy S4 and solved it easily by reformatting the partition. So I tried that. It still didn't work, and over the next 4 or 5 hours I tried everything Google and I could think of, and now the phone is completely gone.
I can't factory reset (a bunch of cannot mount errors), format data (same), advanced wipe (same) or change file system (same). The system partition can be formatted but it still says it cannot be mounted. The data partition looks like it's totally gone. In fastboot, when I try things like 'fastboot erase system' or 'fastboot erase data', I get 'FAILED (remote: Command not allowed)'. I can, however, still do 'fastboot flash recovery [twrp.img], and it'll flash the recovery. I used to be able to do that to data and system too but now I can't anymore.
Something I want to try is to flash it manually with fastboot back to the manufacturer recovery and rom, but my Google-fu apparently isn't good enough to find one. A big problem I'm having with this is the fact that this phone came all the way from China and therefore is a Chinese model (EVA-DL00) and I'm searching in English. When I search in Chinese I can see the words EVA-DL00 everywhere but my Chinese is nowhere near good enough to navigate all that.
So I guess what I'm asking is:
1. Does anyone know why I can't mount the data partition? I've considered maybe its encryption or something but I really have no idea.
2. Does anyone know how I can completely return my phone to stock? Where can I find images for EVA-DL00?
3. If I take this in for repairs, is it possible that it's bricked so badly that they won't be able to repair it?
I'd greatly appreciate any help I can get
Thanks!
Click to expand...
Click to collapse
are you on nougat already?
Regards
OldDroid said:
are you on nougat already?
Regards
Click to expand...
Click to collapse
Not quite sure what you mean :/
The stock OS was nougat before I decimated it, and I was planning on installing the latest Lineage OS build which is based on nougat.
It doesn't have any OS on it right now though.