I tiried to flash the new oxygen pie beta. For whatever reason something went wrong and now here I am.
First time i flashed the beat I got the "Your device is corrupt" error. It's not the typical unlocked boot loader error. The explanation point is red, there is no mention of unlocked bootloader and I need to press power button in order to proceed. I tried flashing again at this point and I wiped everything in TWRP, but that didn't help.
Afterwards I have decided to go back to oreo and just upgrade to pie by local upgrade, but after flashing oreo I still get the red "your device is corrupt". However, I can still boot to the oxygen os and it seem to be working fine.
think its the encryption so reformat the data partition and start from scratch
RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
Formatted data and wiped everything. Flashed the pie beta. I can boot to the os, but I still get the error..
RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
mikex8593 said:
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
Click to expand...
Click to collapse
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Can you post the link to the file?
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Guess it is actually form Oneplus site:
https://forums.oneplus.com/threads/...ficial-oxygen-os-roms-and-ota-updates.835607/
In rollback builds under Signed flashable zips (Android P Developer Preview)
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nameless said:
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/one...ional-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
View attachment 4587785
Click to expand...
Click to collapse
The URL you shared is giving 404 error
Please share correct URL
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
:good:
soldier1 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
Click to expand...
Click to collapse
So you are now back to P beta 1 without the error? Hmm. I got my phone back to 8.1 without the area. But once I flashed it again, the same thing came back.
Thanks
Ended up using qualcomm tool, then flashed P beta 1, then unlocked bootloader, installed twrp, installed magisk7. Everything is good now.
Flashing stock didn't help me, I still had the error. I used the qualcom tool and now I'm on pie without the error.
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Also had the same and flashing back the roll back package fixed it, definitely keeping this zip!
Spoke too soon got the corrupt message after going back to 5.1.11 then to oos beta 1 so had to use the unbrick tool instead.
my guess is that the bootloader can not tell if phone is bootloader locked or unlocked. Has any1 tried flashing the bootloader files to see if that could fix it without debrick tool?
mati11233 said:
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Click to expand...
Click to collapse
No its not, safetynet will not pass, says so even in changelog
Yeah i got the same error, only solution for me was to use unbrick tool
Flash OOS Beta over H2OS beta, no need to wipe data between the two. But it works wonders.
Related
If you guys have encountered the issue " Custom Binary Blocked by FAP LOCK", you managed to do this in a few ways, an example is like what my dumbass did, root the phone and decide to turn OEM unlock back on protecting the phone from being modified, so if you cant boot up the phone here's a fix.
Firstly, ya'll gonna want Odin
Secondly Head Here and Download the Firmware which matches your country ( its roughly 1.9 GB so it might take a while)
NOW that you got everything you need, power off device and kick into download mode by pressing VOLUME DOWN + HOME + POWER
Now open Odin and Extract your files somewhere into a folder which can easily be found
You should have something similar to this
Now this is pretty self explanatory , place the AP files within the AP box,
The BL file within the BL box and so on, I didn't the " HOME_CSC_XSA_G930FXSA1APAW_CL7108765_QB8404011_REV00_user_low_ship.tar" into anything and the phone booted up fine, now press UP VOLUME to allow the phone to go into download mode and press "start" on odin and it will format your phone into factory which may take a few minutes and wall-ah , everything should now be working.
*note this is only for S7, for S7 Edge , instructions may be slightly altered as I dont own one so I wouldnt entirely know*
If instructions weren't clear and you somehow managed to get your **** stuck in a toaster PM me and i'll see what you did.
is there a method of doing this without wiping everything on the phone?
O did the same answer flash only AP file with odin. Previously download the right firmware with samfirm.
Nothing was wipe and everything boot fine after.
Wont work
Hey, looking for quick help.. I got the SM-G930W8 and im trying to do this. I load the BL, AP, CP, and CSC into odin, fire up my phone into download mode and click start once odin says my phone was added. which then it just fails immediately... Need help asap please!
Did you use firmware for SM-G930F or fit SM-G930W8?
maik005 said:
Did you use firmware for SM-G930F or fit SM-G930W8?
Click to expand...
Click to collapse
I haven't been able to find the 930W8 one. and i read that the 930F and W8 are pretty well the same so i figured i'd try that one.
Which provider/region?
maik005 said:
Which provider/region?
Click to expand...
Click to collapse
Bell in Alberta.
Found a link for the exact one but it says session expired whenever I tried to download it
-EDIT-
Just tried again, and the download started. its pretty slow. says 2 hours.
Got it from here http://www.sammobile.com/firmwares/d...8OYA1APD3_BMC/ should be the correct one
try the app samfirm instead...
maik005 said:
try the app samfirm instead...
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This program? Put in my model and region, set it on auto and tried to checkupdate and it cant find anything. if it comes down to the worst i'll probably just have to wait 2hours for the stock firmware to download
Yes. If it does not find anything then you have to wait
maik005 said:
Yes. If it does not find anything then you have to wait
Click to expand...
Click to collapse
Yep. Will update when its done. Thanks for all the help!
-EDIT-
Phone is booting like normal, made it past the problem. Thanks for all the help! you are a life saver!
Didnt work for me. Still frp lock however I did everything correctly and Odin worked as it should. Phone initially booted up in polish but changed this on Language screen a start up, still have "this device has been restored, please enter the prveious gmail account synced with this device??
---------- Post added at 02:34 PM ---------- Previous post was at 02:23 PM ----------
:crying:
done everything right but no working??
N8T0R said:
Yep. Will update when its done. Thanks for all the help!
-EDIT-
Phone is booting like normal, made it past the problem. Thanks for all the help! you are a life saver!
Click to expand...
Click to collapse
baybird said:
Didnt work for me. Still frp lock however I did everything correctly and Odin worked as it should. Phone initially booted up in polish but changed this on Language screen a start up, still have "this device has been restored, please enter the prveious gmail account synced with this device??
---------- Post added at 02:34 PM ---------- Previous post was at 02:23 PM ----------
:crying:
done everything right but no working??
Click to expand...
Click to collapse
Did you download the correct firmware for your phones model number? Because I was trying the SM-G930F firmware when my phone was SM-G930W8 so it wasn't working.
Today I had a software update and come to figure out it was 6.0!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nice man.
are you using at&t sim and currently in america? because i am in asia and i unlocked my phone!
so i barely get any update thing. they say to use at&t sim if i have to update. alas! do tell please
---------- Post added at 09:02 PM ---------- Previous post was at 08:56 PM ----------
plus if some one has zip for MM for lg d850 i will thankful
issues after mm upgrade
Here's what I experienced after update...
Once you upgrade you can't flash back to stock. LG flash tool fails because it couldn't detect the model. After setting up McAfee it disables root and usb debugging. You have to go into McAfee and turn those options off. So it seems like once you go to mm you can't get back to lollipop. I'm also having proximity sensor issues also with the screen going black during a call. I guess once we can get root I'll be able to install another rom.
Hi, I got the notification and I was not in WiFi network so decided to cancel it and check it again once I got to wifi zone. But when I checked next time, I just get a message, your phone is uptodate. I tried rolling date forward to circumvent the 24 hour check, but no luck. Any ideas to get the update notification back ?
no luck updating
tried the update today, it just sends me to twrp recovery screen every time
You can't install a factory update while rooted. Come on guys you should know this.
Sent from my LG-D850 using XDA-Developers mobile app
Update
vishnugs said:
Hi, I got the notification and I was not in WiFi network so decided to cancel it and check it again once I got to wifi zone. But when I checked next time, I just get a message, your phone is uptodate. I tried rolling date forward to circumvent the 24 hour check, but no luck. Any ideas to get the update notification back ?
Click to expand...
Click to collapse
I had the same thing happen to me so what I did to make the phone think I haven't checked for an update and avoid the 24 hour wait I did a hard reset. I want to point out that I didn't care much about all my apps being deleted and you might want to back them up. Note: I was on stock lollipop
Anyone do an adb pull and extract the modem yet? Want to flash it on Fulmics 5.0.
Sent from my LG-D850 using Tapatalk
DARKCHYLDX101 said:
Anyone do an adb pull and extract the modem yet? Want to flash it on Fulmics 5.0.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Please let us know if you get it accomplished.
louvass said:
Here's what I experienced after update...
Once you upgrade you can't flash back to stock. LG flash tool fails because it couldn't detect the model. After setting up McAfee it disables root and usb debugging. You have to go into McAfee and turn those options off. So it seems like once you go to mm you can't get back to lollipop. I'm also having proximity sensor issues also with the screen going black during a call. I guess once we can get root I'll be able to install another rom.
Click to expand...
Click to collapse
Not sure if there is an "anti roll back" But You cannot use flashtools once updating to Lollipop you must use LGUP.
hyelton said:
Not sure if there is an "anti roll back" But You cannot use flashtools once updating to Lollipop you must use LGUP.
Click to expand...
Click to collapse
Where do I get a KDS for the 850 along with the LGUP, seems everything points to the 855? thanks. I can't seem to root after the upgrade to 6.
louvass said:
Where do I get a KDS for the 850 along with the LGUP, seems everything points to the 855? thanks. I can't seem to root after the upgrade to 6.
Click to expand...
Click to collapse
Its KDZ. the D850 is TOT method only.
My Guide:
http://forum.xda-developers.com/showthread.php?t=2785089
But remember its your own risk, not sure if downgrading will brick or not yet from MM on the AT&T Model.
FWIW, if you're experiencing DND issues after the 6.0 update check settings > dnd > advanced > schedule. kept noticing on my moto360 it was switching to dnd for no reason. turns out some scheduling magically appeared. been running 6.0 without a hitch since last night. had to manually disable at&t video calling and a few other things but im happy with it thus far.
cjoeone said:
I had the same thing happen to me so what I did to make the phone think I haven't checked for an update and avoid the 24 hour wait I did a hard reset. I want to point out that I didn't care much about all my apps being deleted and you might want to back them up. Note: I was on stock lollipop
Click to expand...
Click to collapse
I tried doing a factory reset after spending a lot of time to back up data. But after fresh restore, I'm getting the message that your phone is uptodate. I m cursing myself why I dismissed the prompt yesterday. Any other solutions to force update ?
hyelton said:
Its KDZ. the D850 is TOT method only.
My Guide:
http://forum.xda-developers.com/showthread.php?t=2785089
But remember its your own risk, not sure if downgrading will brick or not yet from MM on the AT&T Model.
Click to expand...
Click to collapse
Thanks yes I know how to use the flash tool...my problem is it fails every timeI try going back to stock lollipop.
vishnugs said:
I tried doing a factory reset after spending a lot of time to back up data. But after fresh restore, I'm getting the message that your phone is uptodate. I m cursing myself why I dismissed the prompt yesterday. Any other solutions to force update ?
Click to expand...
Click to collapse
You have to do a hard reset through stock recovery. Don't do it if you are using a custom rom. If you are not experienced I recommend you wait to see if you get another update notification
louvass said:
Thanks yes I know how to use the flash tool...my problem is it fails every timeI try going back to stock lollipop.
Click to expand...
Click to collapse
That is because flashtool you cannot use if your on MM you use LGUP with the TOT file.
hyelton said:
That is because flashtool you cannot use if your on MM you use LGUP with the TOT file.
Click to expand...
Click to collapse
Can you send me a link for it thanks man..i got it thanks
louvass said:
Can you send me a link for it thanks man..i got it thanks
Click to expand...
Click to collapse
It's in the 2nd post of my guide in the link I posted earlier ^^ but just remember at your own risk as I haven't seen anyone try yet. Example like the G4 after a certain point people bricked there AT&T model from downgrading. But if you do risk it and everything went smoothly let us all know!
cjoeone said:
You have to do a hard reset through stock recovery. Don't do it if you are using a custom rom. If you are not experienced I recommend you wait to see if you get another update notification
Click to expand...
Click to collapse
No luck, tried hard reset through recovery twice and before that general reset several times. I'm not getting the notification for the second time
Any other ways to force update ?
Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.
Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse
Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse
First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.
Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.
SU4TL-49 Stock Image for XT1254: https://mega.nz/#!TwYShBCb!OFxwiUnUO2MiOHEVc8XluNP1uPSf5tTBaVdmyZ-mwSA
This package will flash every image in the SU4TL-49 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, download this: https://mega.nz/#!LwhxyCaZ!NZVi3pA77t7Qlxm1gFQr340SHurOAJEhDQsiR8QFbMc. Install it using the Install Image option in TWRP.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Deodexed version here for those who may want it: https://mega.nz/#!zxAEHJjS!hqNDjOGJoE3eI3rwL48h45Lovj764quxFsWP9IsN_Z4
If you need the full, non-TWRP version, here it is: https://mega.nz/#!ao4zmQQB!T2VClxKcTb-ePAhHotvlSR3NCxG0tRY1YEhMtti_H3k
If you get errors while flashing this, try using TWRP Mod 3 instead of Mod 4.
Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...
Nice! Thanks a lot!
rjansen110 said:
Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...
Click to expand...
Click to collapse
1. Yeah, that's kind of what I meant by the last sentence of the OP.
2. That always happens whenever you go from CM to stock. It's harmless.
So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app
joeriv5692 said:
So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.
TheSt33v said:
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.
Click to expand...
Click to collapse
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?
Glad to see the return of @TheSt33v !! Thank you for your work!!
joeriv5692 said:
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?
Click to expand...
Click to collapse
the answers to "one more thing":
1) yes, if you flash stock recovery it will take TWRP off. 2) it will not relock your bootloader.
edit: ****** 3) it will *not* take away all traces you have modded/hacked/rooted
Stock.
NEXT DAY EDIT: i just restored pretty much stock 5.1 su-44. after all the uninstall crud there, i booted to twrp, and flashed this. all went perfectly. Thank you @TheSt33v !!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[emoji92] [emoji95] [emoji95] [emoji95] [emoji95] [emoji109]
edit again: same line added to build.prop enables tethering on this build too.
net.tethering.noprovisioning=true
kitcostantino said:
Glad to see the return of @TheSt33v !! Thank you for your work!!
Click to expand...
Click to collapse
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.
TheSt33v said:
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.
Click to expand...
Click to collapse
TheSt33v said:
Now that we've got some Sunshine in our lives, sadly (not really) it is time for Turboid to be retired. We don't need it anymore.
I think that about covers it. Go forth and flash! Thanks for letting me play dev for a few months
Click to expand...
Click to collapse
Ha ha, brother. I guess i just took this post in the Turboid thread wrong.
-King of Unsolicited Advice
I did a system-only backup in TWRP after updating, so I don't think I need this, buuuut, never hurts to have a 2nd option! 44 did save my bacon so update was possible. ?
Thank you for the De-Odexed build!!!
-King of Unsolicited Advice
Has anyone had issues w this ROM or is it all good?
its all good.
-King of Unsolicited Advice
No luck with de-odexed version
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.
yeah, i can confirm. same issue. the fix was wiping data for the app via TiBup. i use a transparent google drive, though, and had presumed it was just me.
sgeek7 said:
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.
Click to expand...
Click to collapse
Weird. I forget, is Drive a system app in the stock rom? If so, maybe try removing it altogether with TiBu and reinstalling it from the play store?
It might be. The non de-odexed version is having no issues on my phone. Thanks for the idea just in case.
Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?
Is anyone having issues with the play store crashing everything you start it up? I flashed the de-odexed and non-de-odexed but play store keeps crashing every time. Any ideas?
---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------
snugroho3 said:
Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?
Click to expand...
Click to collapse
It's included
Hey guys hope you can help with my oneplus 7 pro. So I did not backup before rooting the device, however, I was able to successfully root it. The problem arose when I wanted to take the twrp official 3.3.1-2 and upgraded to 3.3.1-29 version. I flashed it on the system image in the twrp setting, but it ended up writing over OS. Now there is no OS on the oneplus 7 pro. Do you guys have a suggestion into how I can fix this problem? and bring it back into the rooted phone. I also was hoping if you guys know anyway to lock the twrp with a password in the future? thank you
1] Your TWRP should already have had a pin if you had set a pin (same one) when using the rom
2] Can you still boot into TWRP as recovery? If so then go grab the latest 9.5.7 :
Official : https://otafsg1.h2os.com/patch/amaz...ygen_21.E.11_OTA_011_all_1906040003_25c96.zip
My mirror on AFH : https://www.androidfilehost.com/?fid=6006931924117889610
You should be able to flash it using TWRP if you've not messed up too badly, then you may be back to default rom and can start again.
If you get that far then read the guide on the @mauronofrio TWRP properly and flash everything again. I've also uploaded a rooted 9.5.7 boot image here if you want to try that way instead :
https://forum.xda-developers.com/showpost.php?p=79678478&postcount=522
If the worst comes to the worst then you may be able to boot into fastboot then run :
fastboot boot twrp-3.3.1-29-guacamole.img
Boot into TWRP and try sideloading the whole 9.5.7 rom instead
18os13 said:
Hey guys hope you can help with my oneplus 7 pro. So I did not backup before rooting the device, however, I was able to successfully root it. The problem arose when I wanted to take the twrp official 3.3.1-2 and upgraded to 3.3.1-29 version. I flashed it on the system image in the twrp setting, but it ended up writing over OS. Now there is no OS on the oneplus 7 pro. Do you guys have a suggestion into how I can fix this problem? and bring it back into the rooted phone. I also was hoping if you guys know anyway to lock the twrp with a password in the future? thank you
Click to expand...
Click to collapse
You could always download one of the fastboot ROMs and flash them again. You're obviously unlocked etc so all you'd need to do is fastboot flash system system.img. just make sure it's the same version.
ok since the update I was able to get the twrp installed again, but choose a wrong option in the reboot menu, something to do with edl, now the phone turn on at all :/
I give up, apparently people just can't follow instructions.
djsubterrain said:
I give up, apparently people just can't follow instructions.
Click to expand...
Click to collapse
it was slightly before I read this post :/. Is there anything possible now or am i screwed?
18os13 said:
it was slightly before I read this post :/. Is there anything possible now or am i screwed?
Click to expand...
Click to collapse
honestly I have no idea what I just did, but everything just came back online again
18os13 said:
it was slightly before I read this post :/. Is there anything possible now or am i screwed?
Click to expand...
Click to collapse
MSM tool, guac recovery.
theres a thread in this section. It will wipe the phone.
18os13 said:
honestly I have no idea what I just did, but everything just came back online again
Click to expand...
Click to collapse
Be vewy vewy careful...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just get out of EDL, either hold down the power button or hold - and Power for like 10 seconds until u boot out of it
Ok so I basically pressed the volume and down buttom with the power button, then the phone recovered back to the when I first got it and it got uprooted. Anyway, the whole reason I was wanted to root the phone was so that I can lock the TWRP with a password. This would only give me access to hard resetting the phone. Do any of you guys have a solution to this? its a phone for my little brother, and I want to restrict his access to the internet, but he knows how to hard reset the phone using the volume down and power. however, if I can lock the TWRP with a password he cant get around that part as easily.
18os13 said:
Ok so I basically pressed the volume and down buttom with the power button, then the phone recovered back to the when I first got it and it got uprooted. Anyway, the whole reason I was wanted to root the phone was so that I can lock the TWRP with a password. This would only give me access to hard resetting the phone. Do any of you guys have a solution to this? its a phone for my little brother, and I want to restrict his access to the internet, but he knows how to hard reset the phone using the volume down and power. however, if I can lock the TWRP with a password he cant get around that part as easily.
Click to expand...
Click to collapse
You might be able to do that with a guest account but you can't lockout TWRP with a password, it will use the pin applied to the phone. If you set it up as the default user with a pin then that's the pin that will be applied to TWRP so I would look at setting him up as a guest instead which should keep him out of TWRP too.
djsubterrain said:
You might be able to do that with a guest account but you can't lockout TWRP with a password, it will use the pin applied to the phone. If you set it up as the default user with a pin then that's the pin that will be applied to TWRP so I would look at setting him up as a guest instead which should keep him out of TWRP too.
Click to expand...
Click to collapse
perfect, thanks for the help