I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.
Flash fastboot images search and follow naman's unbrick guide, skip the data partition to keep your files
Sent from my ONE A2005 using Tapatalk
1439soccerdude said:
I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.
Click to expand...
Click to collapse
This thread will help you, https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
if you use twrp recovery and is not working on the Vol+ "-", try this way : RENAME your recovery file into twrp.img and flash it again.
If is not working,
following this thread first:
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
Then repeat my rename recovery method.
SOFT brick
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%
Seimus said:
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%
Click to expand...
Click to collapse
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours
Spannaa said:
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours
Click to expand...
Click to collapse
Indeed but i prefer to go back to the previous build as per I know its stable. I like to do rollback and then the update. So I can better isolate any new caused issue
Related
Michael Hall writes about how you can win an OPPO Find 5 by porting Ubuntu Touch to it!
http://mhall119.com/2013/08/win-an-oppo-find-5/
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
RaspberryJam said:
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
Click to expand...
Click to collapse
-True, but during XDA: DevCon we had 3 people without a phone produce images for it, and it's not a one-chance thing, you can resubmit as often as you like.
-How about this, if you already have a Find 5, give me the same of somebody who you think should get this one instead. Could be a friend, or somebody who's work in the XDA community you think should be rewarded.
Despite having three separate developers build images and flash them onto the phone, none were able to boot into Ubuntu Touch.
Click to expand...
Click to collapse
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
paperWastage said:
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
Click to expand...
Click to collapse
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Testers needed
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
mhall119 said:
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Click to expand...
Click to collapse
Throw your files and what youve done so far over here. Im willing to continue work on it.
Androguide.fr said:
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf_2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
Click to expand...
Click to collapse
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
SystemErrorOne said:
Throw your files and what youve done so far over here. Im willing to continue work on it.
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
Click to expand...
Click to collapse
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Androguide.fr said:
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Click to expand...
Click to collapse
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Androguide.fr said:
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Click to expand...
Click to collapse
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
SystemErrorOne said:
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
Click to expand...
Click to collapse
From your error message, you simply didn't add the .img extension to the twrp image
Also, you can't fastboot a zip, don't try.
But, did you try to simply do the following?
Code:
adb reboot recovery
There's absolutely no reason why it would have overwritten your recovery, my guess is you can't reboot to recovery using the button combination.
Anyway, if the above doesn't work, follow these steps to reflash your recovery:
Open a terminal on your pc
Make sure you cd to the directory where your twrp image is
issue the following command:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-find5[COLOR="DarkRed"].img[/COLOR]
Reboot to recovery using:
Code:
adb reboot recovery
Are you on windows or linux?
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
+Franco Colomba I had no such issues with drivers. The only thing was ADB needed an extra USB VID added.
Click to expand...
Click to collapse
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
SystemErrorOne said:
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
Click to expand...
Click to collapse
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Androguide.fr said:
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Click to expand...
Click to collapse
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
SystemErrorOne said:
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
Click to expand...
Click to collapse
Try this:
Download a CM build
Open it with winrar and extract the boot.img from it
hold shift and do a right-click in the folder where you extracted the boot.img, and select "open a terminal here" (or whatever the header is)
Issue this command
Code:
fastboot flash boot boot.img
Now try again to reboot to recovery using the buttons combination
hurray so i managed to get the phone working by using a script found in that one thread you linked me too.. never the less i managed to get into TWRP and from there i had already made a backup (THANK GOD) and i restored and the phone is up and running perfectly. Now what Im going to do is what you instructed to do first.
1. the build first
2. then the ubuntu base afterwards
with
factory reset, wipe dalvik-cache
i will post back my results wish me luck
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
mhall119 said:
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
Click to expand...
Click to collapse
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
SystemErrorOne said:
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
Click to expand...
Click to collapse
Yeah, Michael Hall reported to me that the build doesn't boot either.
I'm working on a new build using a different toolchain, as with the stock Google TC I had to hack my around -Werror flags and this might be the problem.
I'll post the progress here.
Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet
ishmeet said:
Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet
Click to expand...
Click to collapse
FOLLOW THESE INSTRUCTIONS ONLY IF ANYTHING BETTER DOESNT COME UP BECAUSE I DON'T WANT TO FEEL GUILTY IF YOU "FUBAR" YOUR PHONE. I am not an expert in this stuff.. I can only follow instructions and the two videos helped me get out of crappy situation in the past couple weeks.
Follow the two videos below on how to re-install your drivers properly and flash and root Nougat 7.0
First go delete your driver from your PC via Device Manager. Anything that you can associate with N6P or Google.
Then watch this video on how to install new drivers.
This video on how to install Nougat
If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.
Pain-N-Panic said:
If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.
Click to expand...
Click to collapse
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.
ranjha94 said:
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.
Click to expand...
Click to collapse
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
I think I figured out mine problem. I am not sure what you mean by locked bootloader but in my case I was able to reboot to bootloader by pressing all three buttons (Volume up, Volume down and power button) at the same time.
Once you are there and if your bootloader is already unlocked you can flash your own android. Probably this process is called unbrick your phone. I am surprissed and sad as I am not allowed to post link which can help you. Ask admin.
Any related problem while following process. I can try as I am not very expert.
RIP my English.
Thanks
---------- Post added at 05:20 AM ---------- Previous post was at 05:16 AM ----------
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
https://devs-lab.com/how-to-unbrick-hard-soft-bricked-google-huawei-nexus-6p.html
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
And that's why it's a good idea if you do ANY tinkering to your phone that you have an unlocked bootloader. I have screwed my phone up a hundred times over but nothing that a fastboot flash of the stock Google images couldn't overcome.
I'm not sure what situation you're in but I would try to get that bootloader unlocked asap. Just know that when you unlock it, every partition on the phone will be completely wiped to include internal storage (sd card).
I wasn't tinkering that's the thing. I was on the Android beta but I have installed those OTA. I would love to be able to unlock the bootloader but none of the commands will work to unlock it because usb debugging was not enabled or the developer options and I can't boot it to change that.
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
jay0514 said:
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
Click to expand...
Click to collapse
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
ohhh i see
yeh I dones't let me get to the recovery mode in the options from bootloader
and what are the commands to format cache and data in fastboot??
5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
5.1 said:
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
Click to expand...
Click to collapse
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
jay0514 said:
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
Click to expand...
Click to collapse
Sorry... Known issue with the N6P... Have you checked the tread I linked you in my first answer?
Good luck...
jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
Fastboot flash-all.sh is for Mac computers so presumably you have a Mac. Flash-all.bat is for windows. You need to unzip the Google image and move everything into the same folder where you have the fastboot program. Just open a command prompt window inside that folder and type the command. That's how I do it in Windows. Presumably the process is similar with a Mac. You will still have a zipped archive after you unzip the Google image but you want to leave that one as is. So far flashing flash-all.bat has gotten me out of every boot loop I've gotten into on my 6P but my phone never spontaneously bootlooped. I was always doing something (updating a rom, trying to restore a nandroid backup) that resulted in a bootloop. The fact that your phone boot looped without warning is probably a bad sign. If you still have warranty I would try to flash stock and see if you can RMA phone. If that isn't possible you might want to try staying on stock or using a different rom and seeing if the random reboots still occur. Good luck.
Well that really sucks. Sorry for your loss but it is a long running phone failure problem. I'm on my second 6P because this. Even worse to me is the fact your were running almost the exact same setup I am now. I refrained from running 7.x.x to try and minimize my chances of another BLOD so now w4on knows what to do. Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
BackCheck said:
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
Click to expand...
Click to collapse
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
EpicLPer said:
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
Click to expand...
Click to collapse
Flash Tool is a mighty powerful tool, alright. I couldn't find a good scatter file so in a caffeine deprived state I tried to cobble one together. I may have damaged the preloader. It does show up in device manager but it is different that the VCOM preloader device that was showing. Now it totally crashes Flash Tool too. I'm still working on it but since I have a second watch now, I might just RMA this one and start over.
Again, if anyone has a good scatter file please post it. I found one after the fact but I get errors and it's for another MT2601 device, not the Ticwatch.
The good news is I found if you power down the watch and hold the power button on boot you'll get a long vibrate. If you release the button and hit it 3 or 4 times during the vibrate you'll be in the bootloader.
Anyone have stock or even custom working system.img and boot.img?
great
thank you very much man, i was blocked in twrp recovery after a factory reset, and now i should have installed stock recovery, thanks to your post .