After flashing dirtysanta successfully I wanted to move over to the magisk installation. Following the steps and attempting t use magisk I must have mucked something up very well.
after flashing the initial boot image and twrp from fastboot I hoped that it would fix these issues. Instead it seems to have corrupted fastboot. I did a kdz restore with reset hoping this would help but the touch screen still doesn't work and now I cannot setup the phone to allow adb. Booting from the system menu into usb-debugging mode just boots the phone normally
Currently I can boot into only into android but because I am stuck at the setup screen I can't connect through adb. I am not sure where to go from here.
The only thing that I can think of is getting a usb-otg adapter and connecting a mouse and attempting to allow adb by setting up the phone that way but I still cant flash anything from adb so I wouldn't know what to do from there. Does anybody have any suggestions?
Is there a way to install a boot image without fastboot?
I was very excited to start using this phone and this sucks. Any help would be appreciated
Do u have twrp at all? Some guys used a mouse and got threw the setup with it.
Sent from my LG-H918 using Tapatalk
I can't access twrp at all attempting all methods leads to a normal boot routine. It doesn't even go to the stock page where it asks to wipe data. Just LG logo, black screen (assuming it crashes and restarts), then regular boot
I have successfully restored touch functionality by reflashing multiple different kdz files over and over again.
This has not fixed my inability to enter fastboot. I can enter the default android recovery from the no command screen after using adb reboot recovery but any other command just restarts the phone. Rebooting into bootloader from the default recovery just restarts the phone. I am not sure where to go from here, really upset because any fix requires fastboot
tgtrottier said:
I can't access twrp at all attempting all methods leads to a normal boot routine. It doesn't even go to the stock page where it asks to wipe data. Just LG logo, black screen (assuming it crashes and restarts), then regular boot
Click to expand...
Click to collapse
I guess U didn't wait more than 30sec during the step 3, this is crucial.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
tgtrottier said:
I have successfully restored touch functionality by reflashing multiple different kdz files over and over again.
This has not fixed my inability to enter fastboot. I can enter the default android recovery from the no command screen after using adb reboot recovery but any other command just restarts the phone. Rebooting into bootloader from the default recovery just restarts the phone. I am not sure where to go from here, really upset because any fix requires fastboot
Click to expand...
Click to collapse
Get into download mode and Use LG bridge to upgrade
hoi_lai said:
I guess U didn't wait more than 30sec during the step 3, this is crucial.
Is this afternoon running step 3 and waiting for boot? Because when I did it I waited around 30 min on the Verizon boot screen before pulling the battery to reboot.
In reference to LG bridge. Is this different than LGUP?
Click to expand...
Click to collapse
tgtrottier said:
hoi_lai said:
I guess U didn't wait more than 30sec during the step 3, this is crucial.
Is this afternoon running step 3 and waiting for boot? Because when I did it I waited around 30 min on the Verizon boot screen before pulling the battery to reboot.
In reference to LG bridge. Is this different than LGUP?
Click to expand...
Click to collapse
I mean you have to wait at least 30 sec for the step "fastboot flash recovery twrp-3.0.2-1-xxx.img", & also have to do it multiple times in order to load the TWRP successfully.
Click to expand...
Click to collapse
The strange thing is that I could access twrp for a while but then after restoring with LGUP I can't access even stock recovery. And flashing the notsostock kernel messed up the ramdisk it seems, because it said it couldn't write over it. The thing that concerns me is restoring with LGUP doesn't make any difference to these two thiñgs
I am suffering with a similar issue, VS995s model. The touchscreen stopped working after the TWRP flash, using OTG I was able to access TWRP. I restored both the dec16 kdz and the feb18 kdz with no affect on the screen. I was able to use OTG mouse and bluetooth mouse to reflash TWRP with dirtysanta and used OTG mouse to flash lineage OS v14.1 this did not solve the issue either. I re-flashed stock and am at a loss on the next possible step.
tgtrottier, you mentioned that it worked again after flashing a bunch of different KDZ files, do you know the specific one? I am looking for a useable touchscreen at this point and can deal with no root.
@frownyface
Did you discover the solution to the touchscreen not working? After flashing TWRP I have the same issue.
Nope i used an otg mouse and reverted to stock and returned the item.
I felt super bad about it, but i didnt have the time to invest in disassembling it to find the cause which i suspect was a loose connection due to the extended vibration during the root process.
Thumbs down sorry i could not be any help,
Related
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
matteosaeed said:
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
Click to expand...
Click to collapse
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Also check this out, it might help
matteosaeed said:
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Also check this out, it might help
Click to expand...
Click to collapse
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Why don't you just go to Heisenberg's guide in the general section and flash the latest stock images from Google via Fastboot and start from there? This way you'll at least have a working phone to boot into. From there you can reflash custom recovery and even systemless root. This is what I have always done when the phone wouldn't boot, or I had a backup handy and flashed that. When in trouble just flash latest images.
Asmodic said:
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
Click to expand...
Click to collapse
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sounds like you need to update you drivers if your computer is not recognizing it
Asmodic said:
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Click to expand...
Click to collapse
Any Luck?
it's because you don't have the NEWEST version of TWRP.
Even the simplest of searches would've come up with this answer.
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
pankajste said:
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
Click to expand...
Click to collapse
No it won't, not in this situation.
Heisenberg said:
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Asmodic said:
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Click to expand...
Click to collapse
So this should be marked "Solved?"
It should be marked as "when in trouble revert to Heisenberg's guide."
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
StarShoot97 said:
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
theesotericone said:
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
Click to expand...
Click to collapse
I said it looks like this, I did not say the button is the reason
When I access fastboot it stays there until I manually select an option
ultyrunner said:
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
StarShoot97 said:
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
Click to expand...
Click to collapse
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
When stock recovery is installed, I am from time to time able to access it (most of the times it just ends in a bootloop)
If I flash TWRP I can't access it, no matter how often I try
I have factory reset my phone, the stuff on the internal is still there and I want to reach this, as I have my chats, SMS, university stuff and so on backed up on the internal storage
I am trying everything - all the regular adb methods, toolkits, every driver, nothing is working
Sorry if you don't understand my situation, but I am in a pinch right now
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery and cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Edit2: wrong, see my latest reply
RoyJ said:
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery. Perform a factory reset again like you already mentioned you did as well as a cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Click to expand...
Click to collapse
I did this already exactly like you wrote, did it again now, and I am still stuck in the reboot loop (boots up to Google Logo, then shuts itself down; repeat)
Can't reach recovery mode either
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Fastboot twrp 3.0.0-0 then try to access it
RoyJ said:
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Click to expand...
Click to collapse
Yes, I think so too. I flashed the phone with the full Stock image, the bootloop is still there.
Looks like my precious is dead
At least I have my most important data like phonenumbers, pictures and SMS saved to the cloud
Gonna RMA it tomorrow
Goodybe my precious, I hope you'll be fine :crying:
Got my device back today, the mainboard was damaged, so I had no chance to get my data from the phone
Hey, at least my warranty has been renewed 'till 2018
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
Try flashing TWRP 3.0.2-3 or boot into twrp through fastboot. Using
fastboot boot recovery <twrp filename>.img
I think booting to twrp using this command will work.
And here's the link to Twrp 3.0.2-3 , as its not available on Official Twrp page.
https://idlekernel.com/twrp/nexus/twrp-3.0.2-3-angler.img
I had the same problem with my 5X, nothing worked I tried every possible solution described above and more. Nothing. I figured out that there was nothing to loose and followed directions from YouTube videos (links below) and it worked. Used heat gun at max temp for about 2 mins from each side. It's been about 12 hours since then, phone works flawlessly. Here are the links:
https://www.youtube.com/watch?v=SD25mdrgAys
https://www.youtube.com/watch?v=Cqh2x-TGnCY
Be careful handling the motherboard after you heat the first side, let it cool first before you start working on the second side. The same with the second side do not pick it up until it's cool.
5X, Pure Nexus Rom 7.1.2 June 5th security update, Elemental X Kernel,
has anyone found solution to this?????
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 .
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.
I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!
zhangla said:
I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!
Click to expand...
Click to collapse
Obviously you did not do enough reading on the ds root process because then you'd know static on boot is normal and you would have read about the button combo to get into twrp. I suggest you do some more reading
Sent from my LG-H910 using XDA Labs
I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?
zhangla said:
I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?
Click to expand...
Click to collapse
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.
Mysticblaze347 said:
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.
Click to expand...
Click to collapse
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?
zhangla said:
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?
Click to expand...
Click to collapse
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.
Mysticblaze347 said:
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.
Click to expand...
Click to collapse
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...
zhangla said:
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...
Click to expand...
Click to collapse
Might just have to redo Dirty Santa again...I really dont know what else other than researching ADB commands.
Im assuming that you already tried manual boot in twrp as Cnjax stated. Look into those as well. Different models sometimes have different button combos.
@zhangla
You best slow down and do more reading
You made another mistake
I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom
Click to expand...
Click to collapse
The Oreo stock rom is Stock and flashes Stock recovery and removed TWRP.
Their are two v20 rooted Oreo h910 roms
you needed to use those.
You now need to start over by flashing the h915 nougat kdz and following the root guide
https://r.tapatalk.com/shareLink?ur...share_tid=3664500&share_fid=3793&share_type=t
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
Sent from my PH-1 using Tapatalk