flashed
fastboot flashing unlock
then
fastboot flashing unlock_critical
now the phone wont boot just staying on google boot screen
flashed ota img still no joy any ideas thanks
jaythenut said:
flashed
fastboot flashing unlock
then
fastboot flashing unlock_critical
now the phone wont boot just staying on google boot screen
flashed ota img still no joy any ideas thanks
Click to expand...
Click to collapse
You'd be better off flashing the factory image vs the ota. Did you side load it, or try fastboot??
Badger50 said:
You'd be better off flashing the factory image vs the ota. Did you side load it, or try fastboot??
Click to expand...
Click to collapse
i fastbooted it fastboot -w update image-taimen-opd1.170816.025.zip when it reboots i get google splash its like theres no software on the phone just tried flashing 8.0 still no joy
geting this as well telling me the device is corrupted
jaythenut said:
i fastbooted it fastboot -w update image-taimen-opd1.170816.025.zip when it reboots i get google splash its like theres no software on the phone just tried flashing 8.0 still no joy
Click to expand...
Click to collapse
So you tried fastbooting the ota??? That's not gonna work. You need to download the factory image, then unzip/extract it and put all the contents in your SDK platform-tools file. Then edit and save the flash-all.bat script with the -w removed, then you should be fine :good:
Badger50 said:
So you tried fastbooting the ota??? That's not gonna work. You need to download the factory image, then unzip/extract it and put all the contents in your SDK platform-tools file. Then edit and save the flash-all.bat script with the -w removed, then you should be fine :good:
Click to expand...
Click to collapse
yeah that what ive been doing ive installed twrp and there is no img on the phone just flashed system .img on its own still nothing
jaythenut said:
yeah that what ive been doing ive installed twrp and there is no img on the phone just flashed system .img on its own still nothing
Click to expand...
Click to collapse
The factory image# you posted earlier, ending in .025, is the November build. Is that what your wanting to do??? What build were you on before you started this??
Badger50 said:
The factory image# you posted earlier, ending in .025, is the November build. Is that what your wanting to do??? What build were you on before you started this??
Click to expand...
Click to collapse
was on 8.1 dec went to flash 8.1 jan couldnt flash as i didnt unlock critical so unlocked it and thats when this all started read on here some guy flashed back to 8.0 and it fixed it but not me lol
jaythenut said:
was on 8.1 dec went to flash 8.1 jan couldnt flash as i didnt unlock critical so unlocked it and thats when this all started read on here some guy flashed back to 8.0 and it fixed it but not me lol
Click to expand...
Click to collapse
Ah, now I see. In order to downgrade, you have to let your phone get wiped. So put the -w back in the flash-all script.
However, since your phone has already been wiped with unlocking_critical, might as well just flash the January update and don't edit the flash-all script. Then let your phone boot up, do a minimal setup, then go back to fastboot mode and boot twrp, then root if you want to with magisk 15.2 :good:
Badger50 said:
Ah, now I see. In order to downgrade, you have to let your phone get wiped. So put the -w back in the flash-all script.
However, since your phone has already been wiped with unlocking_critical, might as well just flash the January update and don't edit the flash-all script. Then let your phone boot up, do a minimal setup, then go back to fastboot mode and boot twrp, then root if you want to with magisk 15.2 :good:
Click to expand...
Click to collapse
cant find valid operating system the device will not start
wtf ive flashed 10 times today haha
jaythenut said:
cant find valid operating system the device will not start
wtf ive flashed 10 times today haha
Click to expand...
Click to collapse
Is your SDK up to date, as are you device drivers?? Also, what transfer cable are you using?? Your using up all my options bro!
Badger50 said:
Is your SDK up to date, as are you device drivers?? Also, what transfer cable are you using?? Your using up all my options bro!
Click to expand...
Click to collapse
yeah im out of ideas as well but thanks for trying to help :good:
just sideloaded ota looks like that worked
jaythenut said:
yeah im out of ideas as well but thanks for trying to help :good:
just sideloaded ota looks like that worked
Click to expand...
Click to collapse
I hate being defeated!!!! If everything is up to date, then the only other thing I could suggest is to go into stock recovery, do a factory reset, then start over. There is also a rescue script put there if that doesn't work. I'll find the link if you need it.
Badger50 said:
I hate being defeated!!!! If everything is up to date, then the only other thing I could suggest is to go into stock recovery, do a factory reset, then start over. There is also a rescue script put there if that doesn't work. I'll find the link if you need it.
Click to expand...
Click to collapse
all fixed with ota :fingers-crossed:
jaythenut said:
all fixed with ota :fingers-crossed:
Click to expand...
Click to collapse
You gotta be sh****ng me! Well good for you dude. Did you side load it?
Badger50 said:
You gotta be sh****ng me! Well good for you dude. Did you side load it?
Click to expand...
Click to collapse
Yeah sideloaded it strange that that worked but like you out of ideas so thought I'd try and boom
jaythenut said:
Yeah sideloaded it strange that that worked but like you out of ideas so thought I'd try and boom
Click to expand...
Click to collapse
Well, I'll be damned! Oh well, I learned something new at least. Glad you got it working though :good:
Related
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
MColbath said:
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
Click to expand...
Click to collapse
Do you still have root? What was the error?
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
MColbath said:
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you outline the exact steps you are doing to flash?
mdamaged said:
Can you outline the exact steps you are doing to flash?
Click to expand...
Click to collapse
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
MColbath said:
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
Click to expand...
Click to collapse
In the process of resetting back to factory, did it relock your bootloader? I ask only because some tools do this automatically. I had to ask.
mdamaged said:
In the process of resetting back to factory, did it relock you bootloader? I ask only because some tools do this automatically. I had to ask.
Click to expand...
Click to collapse
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
MColbath said:
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
Click to expand...
Click to collapse
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it (a suggestion to use goo was here, but forget that).
If you can boot into twrp using the above suggestion, you can at least root and get some stuff done while waiting for a fix or update or someone more knowledgeable than I to solve your issue.
The only thing I can think of is that the bootloader changed and we are back to where you started, waiting for them to update it for your bootloader.
mdamaged said:
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it and try using...goo manager (never used this myself heard some good, some bad things, about it YMMV etc etc).
Click to expand...
Click to collapse
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
MColbath said:
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
Click to expand...
Click to collapse
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Okay seems good.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
MColbath said:
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
Click to expand...
Click to collapse
No problem, thanks for the update.
mdamaged said:
No problem, thanks for the update.
Click to expand...
Click to collapse
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
MColbath said:
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
Click to expand...
Click to collapse
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or location or added a new one (with a diff name) or did something with the permissions so it could not be renamed, and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
mdamaged said:
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or added a new one (with a diff name), and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
Click to expand...
Click to collapse
Yeah there are new backup files all over the place in System partition.
MColbath said:
Yeah there are new backup files all over the place in System partition.
Click to expand...
Click to collapse
Stupid providers.
mdamaged said:
Stupid providers.
Click to expand...
Click to collapse
I'm checking the developer block section of recovery right now.
I'll upload the log for the recovery too. Hold on.
Here it is.
MColbath said:
Here it is.
Click to expand...
Click to collapse
Is there a file in /system named recovery-from-boot.p?
Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !
So do I really have to remove my password Everytime I flash something via twrp?..
egren58 said:
So do I really have to remove my password Everytime I flash something via twrp?..
Click to expand...
Click to collapse
Yes
Sent from my Pixel 2 XL using Tapatalk
browniegirl said:
Yes
Click to expand...
Click to collapse
Damm all I want is center clock that's it lol
egren58 said:
Damm all I want is center clock that's it lol
Click to expand...
Click to collapse
It sucks I know
Sent from my Pixel 2 XL using Tapatalk
Not anymore. TWRP just got updated.
rickysidhu_ said:
Not anymore. TWRP just got updated.
Click to expand...
Click to collapse
Where can I update?..
rickysidhu_ said:
Not anymore. TWRP just got updated.
Click to expand...
Click to collapse
Be cared if your wanting to flash roms or switch slots. There are reports that the new version is not working in that regard!!?
egren58 said:
Where can I update?..
Click to expand...
Click to collapse
Right about here ?
https://dl.twrp.me/taimen/
Badger50 said:
Be cared if your wanting to flash roms or switch slots. There are reports that the new version is not working in that regard!!?
Click to expand...
Click to collapse
I'm still on stock and stick to one slot so this new update is very welcome, now that it can finally decrypt! Appreciate the heads up regardless though =) :highfive:
rickysidhu_ said:
I'm still on stock and stick to one slot so this new update is very welcome, now that it can finally decrypt! Appreciate the heads up regardless though =) :highfive:
Click to expand...
Click to collapse
I'm stock room. And I have kernal installed am I safe flashing this I have no idea what slot I am though
egren58 said:
I'm stock room. And I have kernal installed am I safe flashing this I have no idea what slot I am though
Click to expand...
Click to collapse
You should be okay to flash that mod (I don't know which one it is exactly so don't hold me responsible); but I'm pretty sure you should be okay without worrying about slots, for this at least
rickysidhu_ said:
You should be okay to flash that mod (I don't know which one it is exactly so don't hold me responsible); but I'm pretty sure you should be okay without worrying about slots, for this at least
Click to expand...
Click to collapse
Sorry I meant I should be okay updating to the latest twrp. I've heard people locking up their phone in the thread.. lol
egren58 said:
Sorry I meant I should be okay updating to the latest twrp. I've heard people locking up their phone in the thread.. lol
Click to expand...
Click to collapse
Yes, if your still on 8.1, there's no trouble with it at all. Fastboot the new twrp.img, enter twrp, flash the twrp.zip, then kernel.zip, then magisk.zip. I would, for this new update, still remove your screen lock security just to be safe. Then add it back in, and you'll be fine :good:
Badger50 said:
Yes, if your still on 8.1, there's no trouble with it at all. Fastboot the new twrp.img, enter twrp, flash the twrp.zip, then kernel.zip, then magisk.zip. I would, for this new update, still remove your screen lock security just to be safe. Then add it back in, and you'll be fine :good:
Click to expand...
Click to collapse
+1
rickysidhu_ said:
+1
Click to expand...
Click to collapse
I already have twrp install couldn't it just be as flashing the updated TWRP?.
egren58 said:
I already have twrp install couldn't it just be as flashing the updated TWRP?.
Click to expand...
Click to collapse
Go ahead if you'd like. I Was merely pointing out the safe and tested method that I, and many others use to upgrade. The P2XL is a little bit of a finicky beast. I've read too many stories over the last 3 months with bootloops and soft bricks by others doing simple flashing procedures that worked fine on other nexus devices, but crap a brick on this thing. Therefore, I don't take chances
Badger50 said:
Go ahead if you'd like. I Was merely pointing out the safe and tested method that I, and many others use to upgrade. The P2XL is a little bit of a finicky beast. I've read too many stories over the last 3 months with bootloops and soft bricks by others doing simple flashing procedures that worked fine on other nexus devices, but crap a brick on this thing. Therefore, I don't take chances
Click to expand...
Click to collapse
So I have to boot into temporary recovery with adb and than flash the updated trwp img
egren58 said:
So I have to boot into temporary recovery with adb and than flash the updated trwp img
Click to expand...
Click to collapse
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Badger50 said:
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Click to expand...
Click to collapse
So I have to reflash the boot I'm and magisk too
egren58 said:
So I have to reflash the boot I'm and magisk too
Click to expand...
Click to collapse
Yes. There have been reported issues with bootloops if you don't flash your custom kernel and magisk at the end.
Badger50 said:
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Click to expand...
Click to collapse
So I have to reflash the boot I'm and magisk too?
i was on aquari os july build i flashed DU august build succesfully then i restored my backup of Aquari os and when i rebooted it went to bootloop
so i did factory reset in twrp and flashed stock images without wiping internal
but it still goes to bootloop
i really want my internal storage and dont want to wipe it as twrp cannot decrypt if i temp boot it
please help
Prattham said:
i was on aquari os july build i flashed DU august build succesfully then i restored my backup of Aquari os and when i rebooted it went to bootloop
so i did factory reset in twrp and flashed stock images without wiping internal
but it still goes to bootloop
i really want my internal storage and dont want to wipe it as twrp cannot decrypt if i temp boot it
please help
Click to expand...
Click to collapse
Oh my brother, what have you done now? :laugh:
When you restored your AquariOS, did you only restore data I hope?
Then you fastbooted the factory image correct? If so, did you fastboot it to both slots?
Badger50 said:
Oh my brother, what have you done now? :laugh:
When you restored your AquariOS, did you only restore data I hope?
Then you fastbooted the factory image correct? If so, did you fastboot it to both slots?
Click to expand...
Click to collapse
I restored boot data efs system
in deuces script when it asks me to unlock bootloader do i have to say No or yes as iam already unlocked?
i just did a flash-all command while flashing the stock
Prattham said:
I restored boot data efs system
in deuces script when it asks me to unlock bootloader do i have to say No or yes as iam already unlocked?
Click to expand...
Click to collapse
Only restore data when you do that from now on. If your fully bootloader unlocked, say no.
Badger50 said:
Only restore data when you do that from now on. If your fully bootloader unlocked, say no.
Click to expand...
Click to collapse
it isnt working
after all the flashing it asked format userdata i said no then it said batch file not found
i have the platform tools folder files the images an deuces script togther
i am freaking out i dont want to lose my internal data
please help
Prattham said:
it isnt working
after all the flashing it asked format userdata i said no then it said batch file not found
i have the platform tools folder files the images an deuces script togther
i am freaking out i dont want to lose my internal data
please help
Click to expand...
Click to collapse
Did you take all the image files out of the large secondary zip file you find within the factory image file and put them individually in the platform-tools folder. Don't freak my friend, that won't help at all.
Badger50 said:
Did you take all the image files out of the large secondary zip file you find within the factory image file and put them individually in the platform-tools folder. Don't freak my friend, that won't help at all.
Click to expand...
Click to collapse
yes as i said all the platform tools files the 21 images and the deuce script in one folder
Badger50 said:
Did you take all the image files out of the large secondary zip file you find within the factory image file and put them individually in the platform-tools folder. Don't freak my friend, that won't help at all.
Click to expand...
Click to collapse
here is the folder
https://drive.google.com/file/d/1-_I5dtp9v1KrunpxCa-sYcV232H4hXl1/view?usp=sharing
Prattham said:
yes as i said all the platform tools files the 21 images and the deuce script in one folder
Click to expand...
Click to collapse
And the 3 flash-all.bat files as well, and bootloader and radio?
Prattham said:
here is the folder
https://drive.google.com/file/d/1-_I5dtp9v1KrunpxCa-sYcV232H4hXl1/view?usp=sharing
Click to expand...
Click to collapse
the rest of the files are also there just forgot to scale it for the pic lol
Badger50 said:
And the 3 flash-all.bat files as well, and bootloader and radio?
Click to expand...
Click to collapse
yes everything
Prattham said:
here is the folder
https://drive.google.com/file/d/1-_I5dtp9v1KrunpxCa-sYcV232H4hXl1/view?usp=sharing
Click to expand...
Click to collapse
Gotchya. Ok, everything looks right. Try running it again. I've read people have had to run the script a few times to get it to work. If not, try another cable or port.
Badger50 said:
Gotchya. Ok, everything looks right. Try running it again. I've read people have had to run the script a few times to get it to work. If not, try another cable or port.
Click to expand...
Click to collapse
okay i noticed my platform tools wasnt updated
so updatd it and will try again
Prattham said:
okay i noticed my platform tools wasnt updated
so updatd it and will try again
Click to expand...
Click to collapse
That was my next suggestion. I always take that one for granted with many folks.
Badger50 said:
That was my next suggestion. I always take that one for granted with many folks.
Click to expand...
Click to collapse
SO it flashed and asked me to format i said no and my device is still in bootloader so should i restart right? not weird it didnt auto reboot?
i restarted it and still stuck at G logo with loading bar
Prattham said:
SO it flashed and asked me to format i said no and my device is still in bootloader so should i restart right? not weird it didnt auto reboot?
Click to expand...
Click to collapse
Prattham said:
i restarted it and still stuck at G logo with loading bar
Click to expand...
Click to collapse
That's not weird. Sometimes it does, sometimes not. What a hard restart with the power button a few times?
Badger50 said:
That's not weird. Sometimes it does, sometimes not. What a hard restart with the power button a few times?
Click to expand...
Click to collapse
already tried hard reset .... so freaking out
Badger50 said:
That's not weird. Sometimes it does, sometimes not. What a hard restart with the power button a few times?
Click to expand...
Click to collapse
is there a way i can make a backup of my internal now?
i flashed again with script but still stuck at G logo with bar
Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse