Related
I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.
samanbabah said:
I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.
Click to expand...
Click to collapse
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.
samanbabah said:
I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.
Click to expand...
Click to collapse
Try "adb reboot fastboot", and understand what you're doing before you mod your phone. I've seen you with issues lately that you wouldn't have if you read all of the instructions for what you are trying to do and followed then exactly. You are going to end up with a brick of you don't.
jshamlet said:
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.
Click to expand...
Click to collapse
yeah I just don't want to write over the stock recovery so I can get OTA updates in the future. I guess I'll wait for devs to update their recoveries.
samanbabah said:
yeah I just don't want to write over the stock recovery so I can get OTA updates in the future. I guess I'll wait for devs to update their recoveries.
Click to expand...
Click to collapse
Yeah, I failed to realize there was a way to get around that, and blew my stock recovery away.
That said, I think that you could use Sunshine, assuming it's temp-root feature still works, and abort before running the compatibility test. Then, use a local terminal to backup the stock recovery. There is a dd command to pull the recovery block to a file around here somewhere. Unfortunately, I didn't think of that in time to back mine up.
I have posted a request for the new Developer Edition recovery in another thread, though, so hopefully someone can extract it and post it.
jshamlet said:
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.
Click to expand...
Click to collapse
This has to be Dev Ed specific, because I have no problems, and I really haven't heard of many others having problems either.
Plus, "recoveries are having problems booting from fastboot *right now*"? It isn't like an online service where the website is down.
Flash a backup and fix your sh*t.
xunholyx said:
This has to be Dev Ed specific, because I have no problems, and I really haven't heard of many others having problems either.
Plus, "recoveries are having problems booting from fastboot *right now*"? It isn't like an online service where the website is down.
Flash a backup and fix your sh*t.
Click to expand...
Click to collapse
Dude, seriously, there are many brands of decaf on the market that are just as tasty as the real thing.
The issue with recoveries not booting correctly is a noted issue, and started with WWE users. I got a hard lock on TWRP 2.8.0.3, and Philz seemed to running, but with no video. It is interesting that not everyone is having that issue, though. Right now, the only "workaround" is to actually flash. When I say "not working right now", I mean that the developers haven't found/fixed the issue yet, but you knew that, so I'll move on.
Also, it's not like I don't know how to get a stock recovery. It's just I'd rather not have to go through the hassle if I don't have to, especially since it's not exactly time-critical. There probably won't be another OTA for a while, and I have no doubt someone will post a copy of the updated recovery before then.
jshamlet said:
Dude, seriously, there are many brands of decaf on the market that are just as tasty as the real thing.
The issue with recoveries not booting correctly is a noted issue, and started with WWE users. I got a hard lock on TWRP 2.8.0.3, and Philz seemed to running, but with no video. It is interesting that not everyone is having that issue, though. Right now, the only "workaround" is to actually flash. When I say "not working right now", I mean that the developers haven't found/fixed the issue yet, but you knew that, so I'll move on.
Also, it's not like I don't know how to get a stock recovery. It's just I'd rather not have to go through the hassle if I don't have to, especially since it's not exactly time-critical. There probably won't be another OTA for a while, and I have no doubt someone will post a copy of the updated recovery before then.
Click to expand...
Click to collapse
I actually have heard of problems with CWM and Philz (CWM based)on the ViperOne thread. They state in OP and several times in the thread when screw ups happen to only use TWRP. I always thought it was ROM specific, and because of all the USE TWRP! posts, I haven't heard of recovery problems like this.
Maybe a switch to TWRP will fix his problem?
I'm not really seeing the issue here....you just can't boot the custom recovery from a command prompt(temporarily most likely). You can still flash twrp, do what you need to do(i.e. root,etc), then flash the stock recovery back in less than 5 minutes. You could probably just extract the recovery from the OTA or the rom you flashed. It literally took you more time to post your replies here than it would have taken you to do that....just saying.
Here's the stock recovery image that was posted in another thread: http://goo.gl/KsKQvk
I went through the same thing yesterday being unable to temporary boot to trwp. Sunshine didn't work giving me temp root and Weaksauce and Towelroot didn't do it either.
Custom recovery and Supersu flash worked as always.
HTC One M8
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
I recently got a htc one m8 that is stuck on the boot screen.
i can get into the bootloader and fastboot seems to work.
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
if i reboot normally it goes back to the bootscreen with the green htc logo.
if i try to go to hboot adb doesn't recognize the device.
so i'm stuck now. i've read several tutorials and tried various things but have no idea where to go from here.
i can tell you that the bootloader says its unlocked and that its set to s-on and there is no os installed.
help
jodahall said:
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
Click to expand...
Click to collapse
Try fastboot erase cache, and flash TWRP again with fastboot.
What is your hboot number, and what TWRP version are you trying?
Also, was your phone recently updated OTA for the Stagefright patch? If so, its a known issue that this recent update does not work with TWRP for some folks.
jodahall said:
if i try to go to hboot adb doesn't recognize the device.
Click to expand...
Click to collapse
This is as it should be. adb doesn't work in hboot. You need to be booted into OS to use adb, possibly will work in recovery (but you can't boot into recovery, so that doesn't really matter).
my hboot version is 3.19.0.0000
i am trying to flash the latest twrp
I have not gotten the ota, this phone has been sitting in a drawer for about 6 months so nothing new has been applied.
I will try erase the cache and reflash the twrp
jodahall said:
i am trying to flash the latest twrp
Click to expand...
Click to collapse
What number TWRP exactly? And you're sure its the TWRP file for the M8, right?
I ask for the number, since I've seen at least a couple times where the person claims they are trying to use the "latest" or "current" TWRP. But when I ask for more info, it turns out the version is not even close to current.
Best to be specific when talking about version numbers.
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
I also tried your advice and from a command window erased the cache and then reflashed. It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Sent from my A0001 using XDA Free mobile app
oh, it worked. I am one step closer as it booted into the custom recovery.....whoohooo
I ran the command "fastboot format cache" from a dos prompt a couple of times, there were errors the first two times, then the 3rd time it created it without error.
ok onto the next steps that are in Vomers guides....
thanks for all your help
jodahall said:
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
Click to expand...
Click to collapse
You are correct, that is latest version (and correct one for the M8). You might re-download just to eliminate the possibility the file wasn't corrupted.
jodahall said:
It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
Click to expand...
Click to collapse
If you are still intending on doing this, don't try any version older than 2.8.4.0 or so. TWRP versions much older than that, won't work on hboot 3.19. TWRP will install and seem to work fine, but after you flash the ROM, the ROM won't boot.
jodahall said:
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Click to expand...
Click to collapse
In the technical sense, the emmc chip does have a finite number of times it can be flashed.
But in reality, I think the number of times the emmc can be flashed before failing is (supposedly) something in the thousands.
Of course, things sometimes fail before they are supposed to, and every extra flash may put you closer to that point (in theory). But I don't let that stop me from flashing what I want, whenever I want to. And flashing recovery a few extra times is not going to hurt anything much IMO.
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
jodahall said:
thanks for all your help
Click to expand...
Click to collapse
There's a button for that!
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Try to RMA
zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Badger50 said:
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Even if pay for fix, it is acceptable. It is a fact that I do wrong thing, and I am willing to pay for it.
But if can find a easy way except RMA is better.
Overall, please some advice about how to solve this. Thanks.
Does anyone know if qualcomm flash can flash image without oem unlocking?
zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.
v12xke said:
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.
Click to expand...
Click to collapse
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.?
zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.
v12xke said:
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.[/QUOTE
Sounds about right fasboot twrp . That has saved many phones.
If you can't figure out what to do pay a Dev to use TeamViewer to help you out.
I did that 5 years ago until I understood
ADB commands
Click to expand...
Click to collapse
boot, set active, flash, flashing of fastboot all don't work, because bootloader is locked.
Just reread your post. You can save you phone. You need latest platform tools from Google. Then 8.1 ota image from Google. Learn fastboot commands.
When people start to jump ahead and push,click,touch things they shouldn't you end up here.
Fyi all files for easy reference should be in the plat-forms tools folder.
Download them now.
So let's start:
Fastboot --set-active=_a will set to "a" partition, usually not bootable
Fastboot --set-active=_b will set to "b" partition, usually bootable
Try this:
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_a
On phone scroll to recovery factory reset
Then
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_b
On phone scroll to recovery factory reset
If USB debugging wasn't turned on, boot to recovery and and side load 8.1 ota.
Follow instructions in recovery side load menu
I think it's "adb sideload filename.ota.zip"
Factory reset after boot
Or just get platform tools and 8.0/8.1 imagine depends on what you are on and restore. Probably won't work since OEM/debugging not switched on.
If you get it up and running unlock the phone to help you in the future. Yes both OEM and critical.
Good luck
matt1313 said:
Just reread your post...
Click to expand...
Click to collapse
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.
v12xke said:
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.
Click to expand...
Click to collapse
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..
[email protected] said:
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..
Click to expand...
Click to collapse
Why can't you get to recovery? Stock recovery?
If so sideload ota
matt1313 said:
Why can't you get to recovery? Stock recovery?
If so sideload ota
Click to expand...
Click to collapse
Stock.. Because all possible accessing process to recovery ending with " Can't find valid operating system. The device will not restart". Same issue with sideload ota.. "Flashing is not allowed in lock state"... I have not felt so helpless for a long time.. What a chance..
matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
The only thing that matters is that the bootloader is locked (no fastboot is possible) and no recovery mode (no adb is possible). Done. OP is from China where there is no RMA, so he is "extra" S.O.L. I recognize you are wanting to help, but those are the facts.
I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?
Wait until just after Christmas, then contact Google and say you got it as a present and it says no operating system when it turns on. They're RMA it.
matt1313 said:
I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?
Click to expand...
Click to collapse
As I said, phone is booting only one screen that says "Can't find valid operating system. The device will not restart"..
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
stevew84 said:
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
Click to expand...
Click to collapse
Is this when you fastboot into twrp, or do you have twrp already installed? Have you tried disabling screen lock before you enter twrp? And I assume you've run both bootloader unlocking commands as well?
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
stevew84 said:
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
Click to expand...
Click to collapse
Typically you need to have fully unlocked the bootloader with these 2 commands...
fastboot flashing unlock
and.....
fastboot flashing unlock_critical
Especially the critical, or else you won't be able to flash any roms. I don't know if skipsoft will do this. I know the Deuces scrip will. To find out what is/isn't unlocked run.....fastboot getvar all....
Then you'll know. If you have to unlock critical, which I think you will, it'll wipe your phone completely. So backup your files and such before you do :good:
Any manual methods that work? I mean to flash the roms.
stevew84 said:
Any manual methods that work? I mean to flash the roms.
Click to expand...
Click to collapse
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Badger50 said:
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Click to expand...
Click to collapse
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
stevew84 said:
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
Click to expand...
Click to collapse
Well that changes things a little. You at least have unlocked one partition then. And you can update factory images via fastboot? If so, then your fully unlocked. So you've got a twrp decryption error on slot B. You may want to disable screen lock security, and try again. You could also try fastbooting into twrp as well with screen lock also disabled.
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
stevew84 said:
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
Click to expand...
Click to collapse
Again, run the.....fastboot getvar all....and see what you get :good:
Thanks.
Badger50 said:
Again, run the.....fastboot getvar all....and see what you get :good:
Click to expand...
Click to collapse
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
stevew84 said:
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
Click to expand...
Click to collapse
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Badger50 said:
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Click to expand...
Click to collapse
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
stevew84 said:
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
Click to expand...
Click to collapse
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Badger50 said:
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Click to expand...
Click to collapse
Jesus christ. I'm in a cmd window right now, with the latest platform tools installed.
I ran the command just as you typed, (I'm in bootloader, bootloader version tmz20j by the way). Also, my bootloader version has changed a couple of times during all of this. It was tmz20bb, then tmz12g when I flashed the latest June image...now it's this 20j version.
Anyway, this is what I'm typing and this is what I get in return:
fastboot --set-active=b
fastboot: error: Device does not support slots
I'm at a real loss, obviously this damn device supports slots.
EDIT: OK hold on, when I flashed the June image bootloader version, ran the slot command in ADB, I was able to navigate to the right slot.
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
stevew84 said:
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
Click to expand...
Click to collapse
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Badger50 said:
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Click to expand...
Click to collapse
Thanks.