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?
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
eid_elageeb said:
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
Click to expand...
Click to collapse
You need modified TWRP 3.0.2-28 to get TWRP working with Beta 8. I had the same issue witrh my installation.
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
strumaticjoker2 said:
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
Click to expand...
Click to collapse
even without protection, twrp asking pw, need to erase use data and system.
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
eid_elageeb said:
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
Click to expand...
Click to collapse
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
yiphoming said:
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
Click to expand...
Click to collapse
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
eid_elageeb said:
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
Click to expand...
Click to collapse
No luck, can erase the storage, but it is still in encrypted.
yiphoming said:
No luck, can erase the storage, but it is still in encrypted.
Click to expand...
Click to collapse
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
rarog said:
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
Click to expand...
Click to collapse
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
AcmE85 said:
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
Click to expand...
Click to collapse
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
rarog said:
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
Click to expand...
Click to collapse
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
Do you also get the dm-verity bootscreen?
AcmE85 said:
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
Click to expand...
Click to collapse
Hm... Interesting, do you have a link? And perhaps a link to a thread with all the available versions? I searched, but found only several tutorial threads with just one or another version linked, no thread for specific modified version.
AcmE85 said:
Do you also get the dm-verity bootscreen?
Click to expand...
Click to collapse
As far as I know - no.
When would this error message pop up?
LS.xD said:
As far as I know - no.
When would this error message pop up?
Click to expand...
Click to collapse
Right at boot before or after the screen which shows that the bootloader is unlocked.
AcmE85 said:
Right at boot before or after the screen which shows that the bootloader is unlocked.
Click to expand...
Click to collapse
No such error message for me
LS.xD said:
No such error message for me
Click to expand...
Click to collapse
Did you flash SuperSU?
AcmE85 said:
Did you flash SuperSU?
Click to expand...
Click to collapse
Yes, 2.78 SR5
I have done format userdata in fastboot but my phone still shows up as encrypted. Flashed 3.0.2-1.28 and I still get a password screen when booting to recovery. Not really sure what else I can do.
Where can I find this, exactly? I looked through the 8.1 image, and while I found the boot.img file, there is no recovery file anywhere inside it.
Can anybody help me find this please?
MultiKoopa said:
Where can I find this, exactly? I looked through the 8.1 image, and while I found the boot.img file, there is no recovery file anywhere inside it.
Can anybody help me find this please?
Click to expand...
Click to collapse
Why exactly do you need this? It flashes fine without it
With A-B partitioned devices (inc. Pixel), recovery is part of boot
PresidentMcCain said:
With A-B partitioned devices (inc. Pixel), recovery is part of boot
Click to expand...
Click to collapse
this explains EVERYTHING
thanks
I needed it cause I made a dumbass mistake while switching to 8.1 and trying to root it
did you get it?
MultiKoopa said:
this explains EVERYTHING
thanks
I needed it cause I made a dumbass mistake while switching to 8.1 and trying to root it
Click to expand...
Click to collapse
did you get it?
HeZhiKui said:
did you get it?
Click to expand...
Click to collapse
Yeah I just flashed the boot image to both partitions, and the boot loop was fixed
MultiKoopa said:
Yeah I just flashed the boot image to both partitions, and the boot loop was fixed
Click to expand...
Click to collapse
my pixel xl is now stuck at the initial setting up staus after i unenrolled the 8.1 beta program due to always "Couldn't connect to internet" while the wi-fi is connected . and i post a thread(see the below) link for help, but no body reply me yet. Do you have any idea about my issue? sorry i would like to attched the pictures, but i dont know how to.
thanks.
https://forum.xda-developers.com/pixel-xl/help/setting-due-to-connect-to-internet-wi-t3701963
Hi Friends
pleas help , i wanted install Oreo so i went to lock boat-loader by TOOL_ALL_IN_ONE
and i didnt see the alert message and above message appeared "Your device is corrupt. It can't be trusted and will not boot"
so please advise
If you alter the system in any way you can't lock the bootloader as it will not boot due to possible safety issues by modying the system. In order to use the device with a locked bootloader, you need to flash the original OS.
If you want to use a modified system, keep the bootloader unlocked. Unfortunately, there is no other way.
how can i flash rom please help
MsuatafaKhatab said:
how can i flash rom please help
Click to expand...
Click to collapse
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Macusercom said:
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Click to expand...
Click to collapse
Is it OxygenOS?
yes it is
Did you modify it in any way? Root, Magisk, Xposed, Recovery, flashable ZIPs or anything else?
yes, the problem i used tool "TOOL_ALL_IN_ONE" to lock boat-loader
Use "fastboot flashing unlock" to unlock it again, install TWRP, use adb push to copy OxygenOS to it, flash OxygenOS, use "fastboot flashing lock" and it should work just fine again.
not allow to me to unlock again
https://imgur.com/a/fIYqZ
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Macusercom said:
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Click to expand...
Click to collapse
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
MsuatafaKhatab said:
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
Click to expand...
Click to collapse
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
MsuatafaKhatab said:
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
Click to expand...
Click to collapse
They keep their tools private. So unless you back them up during the session in the background and use a keylogger to get the password, you will never get your hands on the tools. No one does.
But you can contact them again at any time and they will assist you so just don't do this again and you should be fine
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Seven_of_Nine24 said:
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Click to expand...
Click to collapse
How bro
I already fixed by one plus technical support , but to learn
Sent from my ONEPLUS A5010 using Tapatalk
I didn't do anything in my phone n still I got the device is corrupt.
Tejesh.D said:
I didn't do anything in my phone n still I got the device is corrupt.
Click to expand...
Click to collapse
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Sent from my ONEPLUS A5010 using Tapatalk
MsuatafaKhatab said:
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Click to expand...
Click to collapse
It's working now....but still ll open a ticket
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Try this
https://r.tapatalk.com/shareLink?ur...share_tid=3733012&share_fid=3793&share_type=t
Sumanyu Sinha said:
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Sent from my ONEPLUS A5010 using Tapatalk
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