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?
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Thanks for the reply.
Are you sure what happened to is exactly what happened to you? Because I tried the ToolKit and it is not working. I tried both the versions of the TWRP and Stock recovery.
If you know anything else about this issue that would help me. I'd love to hear it.
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Also. Does encryption affect this in anyway, because I did it. I don't want to factory reset my phone because this is my primary phone and I don't have another phone. And I don't want to risk it, at least for a few days.
malachiseelam said:
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Click to expand...
Click to collapse
Modified TWRP version should do it
Same, when I flashed cm 14.1 I also got blank TWRP.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Then, what did you do?
LS.xD said:
Modified TWRP version should do it
Click to expand...
Click to collapse
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
malachiseelam said:
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
Click to expand...
Click to collapse
Thanks it worked!
Please try the modified TWRP, 3.0.2-22
I was running 3.2.8 as of this morning but decided to go back to stock, so I:
flashed stocked recovery
installed 3.2.8
setup my phone, etc
connected to my vpn
downloaded and installed the update
phone boots to 6.0.1/OOS 3.2.8
I don't get it. Originally I had an issue with the update, it wouldn't install. SO I rebooted to (stock) recovery and wiped cache, rebooted and was able to perform the update. But when the phone rebooted it booted to OOS 3.2.8. WTF?!
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
dcdevito said:
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
Click to expand...
Click to collapse
Why don't you try installing the update manually?
Formhault said:
Why don't you try installing the update manually?
Click to expand...
Click to collapse
I tried side loading but I get "can't read [filename].Zip"
dcdevito said:
I tried side loading but I get "can't read [filename].Zip"
Click to expand...
Click to collapse
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Formhault said:
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Click to expand...
Click to collapse
I reinstalled adb drivers and I can at least get the stock recovery to attempt to sideload it, but the install fails like it does from the system updater.
Could be the stock Nougat recovery that I am not using - perhaps I am using an older version - where can I verify the download for that?
For reference this is where I got the stock recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
dcdevito said:
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
Click to expand...
Click to collapse
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
dcdevito said:
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Click to expand...
Click to collapse
I see
dcdevito said:
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
Click to expand...
Click to collapse
Well, you missed this
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
Formhault said:
I see
Well, you missed this
Click to expand...
Click to collapse
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
dcdevito said:
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
Click to expand...
Click to collapse
I stand correctd - looks like it TWRP and SU were indeed updated
Okay, so a few days ago I had a completely stock LG G3 D855 v30n Marshmallow. Then I decided I wanted to root it and flash fulmics. So I flashed the v30b kdz with lg flash tool and rooted the phone with rootking. Everything worked perfectly until I flashed the ROM. I made a nandroid backup with TWRP and I downloaded the fulmics 6.6 zip of the xda forum and put it onto my external sd card. I tried to flaash it onto my phone but it wouldn't work (it kept reloading into recovery mode every time I tried to flash it). I thought the problem was I was using an old version of TWRP. So I flashed my backup and soft bricked my device. I have access to download mode. Could someone please help me in unbricking my phone and is it even possible to flash a rom in my situation? Thank you very much in advance.
BluPixel said:
Okay, so a few days ago I had a completely stock LG G3 D855 v30n Marshmallow. Then I decided I wanted to root it and flash fulmics. So I flashed the v30b kdz with lg flash tool and rooted the phone with rootking. Everything worked perfectly until I flashed the ROM. I made a nandroid backup with TWRP and I downloaded the fulmics 6.6 zip of the xda forum and put it onto my external sd card. I tried to flaash it onto my phone but it wouldn't work (it kept reloading into recovery mode every time I tried to flash it). I thought the problem was I was using an old version of TWRP. So I flashed my backup and soft bricked my device. I have access to download mode. Could someone please help me in unbricking my phone and is it even possible to flash a rom in my situation? Thank you very much in advance.
Click to expand...
Click to collapse
Hello again.
Can you access TWRP recovery?
Sotiris02 said:
Hello again.
Can you access TWRP recovery?
Click to expand...
Click to collapse
@Sotiris02
Hi, yes I can but it's the 2.8.7.0 version. thanks for responding
BluPixel said:
Hi, yes I can but it's the 2.8.7.0 version. thanks for responding
Click to expand...
Click to collapse
Ok so,
Connect your phone to your PC.
Go here TWRP and select the "official".Download the latest one,move it to your phone's SD Card.Flash it with TWRP.
And after that,Full wipe and reflash Fulmics.
Sotiris02 said:
Ok so,
Connect your phone to your PC.
Go here TWRP and select the "official".Download the latest one,move it to your phone's SD Card.Flash it with TWRP.
And after that,Full wipe and reflash Fulmics.
Click to expand...
Click to collapse
@Sotiris02 I can't access the phone in recovery using my PC but I think I can do it using ADB
BluPixel said:
@Sotiris02 I can't access the phone in recovery using my PC but I think I can do it using ADB
Click to expand...
Click to collapse
Hm give that a try then.
Sotiris02 said:
Hm give that a try then.
Click to expand...
Click to collapse
@Sotiris02 I managed to get the .img of twrp onto the phone and flash it but I rebooted and now I can't access recovery
BluPixel said:
@Sotiris02 I managed to get the .img of twrp onto the phone and flash it but I rebooted and now I can't access recovery
Click to expand...
Click to collapse
I can access download mode so I will try and flash the stock kdz and dll using lg flash tool
BluPixel said:
I can access download mode so I will try and flash the stock kdz and dll using lg flash tool
Click to expand...
Click to collapse
Ok that's great!
Sotiris02 said:
Ok that's great!
Click to expand...
Click to collapse
Oh, forgot to mention I fixed it! Reset and was back in stock 4.0. I rooted again and flashed the fulmics rom (properly) and everything is working great! Thanks so much for the help - would be screwed without it!
Hi,
I understand this is probably a common problem with a simple fix, but this is my first attempt to root. My phone is unlocked and s-off, running 3.37.605.7. I used TWRP to install SuperSU and then after rebooting, it was stuck in a bootloop. After doing some research I think maybe I installed the wrong version of SuperSU, but I can't figure out how to fix it. I did a backup with adb beforehand, but when I tried restoring it said to unlock my phone and confirm, and I can't unlock my phone. I tried doing the restore command with TWRP open and it seemed to do something at first, but then nothing. I'm really stuck and would appreciate some help.
Thanks!
Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?
RoyalDrew said:
Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?
Click to expand...
Click to collapse
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.
jrzee45 said:
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.
Click to expand...
Click to collapse
After you get TWRP back, flash View attachment BETA-SuperSU-v2.65.zip to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.
RoyalDrew said:
After you get TWRP back, flash View attachment 4082602 to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.
Click to expand...
Click to collapse
Just flashed 2.65 and it worked! Thanks so much.
Unable to boot
Anyone having issues with this ROM. I flashed using TWRP 2.8.7.0, S-OFF and Unlocked, after flashing, phone reboots into aboot and i select reboot, and it rebots to aboot again without booting to the rom.