Ok so i am going to need a little bit of help here.
I the process of trying a method i found to apply the OTA update i forgot to do a nandroid backup.
I first pushed a recovery i thought was the stock one.
Then i locked the phone
then I pushed another recovery on top of it after the phone was locked.
The last step is preventing me in entering recovery.
Everytime i try to get in it comes back to the bootloader saying:
TAMPERED / RELOCKED / Security Warning.
As you can see, i screwed up.
What i am trying to accomplish though is do manually create a nandroid using ADB.
Now the problem i am having is that the tar command does not seem to preserve the sym links AND user/group.
the tar command i used was
tar -cvhf /sdcar/backup/system.ext4.tar /system
I am pretty trying to do the same thing as CWM recovery but from the command line.
How can i accomplish this?
Thanks a ton
well you cannot flash files with a relocked bootloader, So thats the reason you're having issues pushing recovery, Re-unlock the phone and try again.
And also, Stock recovery does not support nandroid backups. Flash CWM in fastboot, make a nandroid, Flash stock recovery, re-lock bootloader and all will be good.
**TAMPERED**
RELOCKED
Security Warning
Is normal when you have custom software on a locked device. Reverting to stock will clear this up
Oh and next time, Please post in the correct section, This belongs in Q&A.
Flame flame flame flame flame....
sent from a guy living in a van down by the river
azzledazzle said:
well you cannot flash files with a relocked bootloader, So thats the reason you're having issues pushing recovery, Re-unlock the phone and try again.
And also, Stock recovery does not support nandroid backups. Flash CWM in fastboot, make a nandroid, Flash stock recovery, re-lock bootloader and all will be good.
**TAMPERED**
RELOCKED
Security Warning
Is normal when you have custom software on a locked device. Reverting to stock will clear this up
Oh and next time, Please post in the correct section, This belongs in Q&A.
Click to expand...
Click to collapse
I will use the correct section. I promise.
I just thought that Q&A was just general questions about the phone.
Now, I would re-unlock it, but this creates a factory reset and erases everything which is what i am trying to avoid.
I am half screwed though since when i first unlocked it i did a nandroid backup.
So technically, i just need to tar up the /data folder.
Any idea on how to do this in my current state?
Just unlock it again via HTCdev. After it's unlocked download stock recovery. AFter that use the "fastboot flash recovery recovery.img" and then relock it. You will not have security warning. You get security warning after you lock bootloader but recovery is still custom. The newly locked bootloader signature checks recovery and gives you the *Security Warning*. Good luck
Edit: You do not need to erase anything. The only thing that erases all your stuff running an RUU or a different backup. All you need is stock recovery. Also if you don't flash recovery but you unlock bootloader also the security warning will be gone. easy.
shootind5nukes said:
Just unlock it again via HTCdev. After it's unlocked download stock recovery. AFter that use the "fastboot flash recovery recovery.img" and then relock it. You will not have security warning. You get security warning after you lock bootloader but recovery is still custom. The newly locked bootloader signature checks recovery and gives you the *Security Warning*. Good luck
Click to expand...
Click to collapse
I will unlock, and i've done it before. The problem is that unlocking resets to factory defaults meaning everything is erased.
I need to pretty much backup the data folder, then unlock, but without the recovery.
its a bit of a challenge.
But thanks though.
unlocking does not delete anything.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
Nothing gets erased. I've unlock and relocked my phone 100 times.
shootind5nukes said:
unlocking does not delete anything.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
Nothing gets erased. I've unlock and relocked my phone 100 times.
Click to expand...
Click to collapse
Pretty sure it does.
BUT, let me try with my phone.
The phone i screwed up is my wife's.
I'll say this a third time.
UNLOCKING YOUR PHONE DOES NOT RESET ANY DATA. IT JUST UNLOCKS BOOTLOADER.
---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------
PM sent
shootind5nukes said:
I'll say this a third time.
UNLOCKING YOUR PHONE DOES NOT RESET ANY DATA. IT JUST UNLOCKS BOOTLOADER.
Click to expand...
Click to collapse
Alright alright...
Dont want to piss you off.
I appreciate the help. Just gave you 3 thanks.
I really dont want to screw this one up.
if you have a wife, you'll understand. She will chew me alive if i do something stupid (again )
I'll give it try
Im moving this. go look for your thread in the Q and A section...
shootind5nukes said:
I'll say this a third time.
UNLOCKING YOUR PHONE DOES NOT RESET ANY DATA. IT JUST UNLOCKS BOOTLOADER.
---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------
PM sent
Click to expand...
Click to collapse
Well, it reset my data.
Fortunately everything I care about can be easily restored but if one uses Hasoon's all-in-one kit I can say that your data will be wiped. It won't touch the 'sdcard' data but all apps and settings will have to be restored.
shootind5nukes what method are you using to unlock that doesn't wipe?
So, no response on the magical method to unlock without wiping?
michaelh99 said:
So, no response on the magical method to unlock without wiping?
Click to expand...
Click to collapse
No magical method.
I ended wipping everything.
Sorry
Adrien, I was replying to shootind5nukes who was yelling at you for not understanding his magical method for unlocking the bootloader without wiping the phone. Which he didn't share.
michaelh99 said:
Well, it reset my data.
Fortunately everything I care about can be easily restored but if one uses Hasoon's all-in-one kit I can say that your data will be wiped. It won't touch the 'sdcard' data but all apps and settings will have to be restored.
shootind5nukes what method are you using to unlock that doesn't wipe?
Click to expand...
Click to collapse
For me it also wiped everything
michaelh99 said:
Adrien, I was replying to shootind5nukes who was yelling at you for not understanding his magical method for unlocking the bootloader without wiping the phone. Which he didn't share.
Click to expand...
Click to collapse
I figured, but i should have posted earlier the results of my experiment.
At the end, nothing would work.
I ended up wiping out everything and twice.
The first time, i installed the nandroid and radio and used Titanium backup to reinstall the apps.
Somehow, this method caused some issues and the battery would drain really fast.
I just reinstalled everything but this time by hand and redownloading everything from the market.
Related
friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding. I have tried to reflash a new rom/ flash boot.img and the new rom installs and the same thing occurs. I know if i flash a default rom i will have to relock the BL but i will lose the ability to flash anything in the future?
some details you wil probably need on my screen
evita pvt ship S-on RL
S-ON( i have a feeling it has to do with this)
h-boot 1.09
radio 0.17.32
i have tried clean rom and viper rom and i get the same issue. suggestions?
all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.
DJSYNTHVIRUS said:
friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding.
Click to expand...
Click to collapse
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.
DvineLord said:
all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.
Click to expand...
Click to collapse
im going to fix permissions and see if i can reflash clean rom if that doesnt work i will try to update twrp then repeat. thanks for the help
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
redpoint73 said:
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.
Click to expand...
Click to collapse
can you suggest anything i cant figure out why its force closing like that? please and thank you
DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
Boot into bootloader, then select recovery. You'll be able to tell which one you have then.
---------- Post added at 02:53 PM ---------- Previous post was at 02:51 PM ----------
DJSYNTHVIRUS said:
can you suggest anything i cant figure out why its force closing like that? please and thank you
Click to expand...
Click to collapse
CWM is not supported by the HTC One X/XL. TWRP does, which is why you're having some issues. I would recommend flashing TWRP over before you flash anything else. Doing something wrong on CWM could lead you in the path of being a proud owner of a $500 paper weight.
DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.
redpoint73 said:
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.
Click to expand...
Click to collapse
thnx to all of you, when booting into recovery i get into TWRP so it is most likely as you say my buddy who gave it to me most likely flashed CWM then TWRP , so your suggesting doing the above in that order?
Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.
ill try it thanks
QUOTE=redpoint73;33819696]Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.[/QUOTE]
Hi,
I just wiped all my data from the device using TWRP without Unlocking the bootloader . Now I'm stuck @ google logo screen
is there anyway to unlock the bootloader (Fastboot & adb cmds aren't working) /install the Android OS ?
Pls help...
Regards,
Gokul Krishnamoorthy
i cant comprehend what you were trying to accomplish in doing this. i also dont understand how you were able to install twrp without unlocking the bootloader, unless you relocked it after installing twrp. you wont have fastboot commands with it being locked.
can you boot into the bootloader? if so, unlock it, if that's what its gonna take to fix your errors
xBeerdroiDx said:
i cant comprehend what you were trying to accomplish in doing this. i also dont understand how you were able to install twrp without unlocking the bootloader, unless you relocked it after installing twrp.
Click to expand...
Click to collapse
This made me laugh lol.
xBeerdroiDx said:
i cant comprehend what you were trying to accomplish in doing this. i also dont understand how you were able to install twrp without unlocking the bootloader, unless you relocked it after installing twrp. you wont have fastboot commands with it being locked.
can you boot into the bootloader? if so, unlock it, if that's what its gonna take to fix your errors
Click to expand...
Click to collapse
Yes i relocked it after installing TWRP..
I can able to boot into the bootloader.. but how to unlock it??? fastboot and adb cmds aren't working...
Gokul Krishnamoorthy said:
Hi,
I just wiped all my data from the device using TWRP without Unlocking the bootloader . Now I'm stuck @ google logo screen
is there anyway to unlock the bootloader (Fastboot & adb cmds aren't working) /install the Android OS ?
Pls help...
Regards,
Gokul Krishnamoorthy
Click to expand...
Click to collapse
I think you are confused on what you did/ are trying to do. If you hold volume down and power button it will take you to fast boot, if you can get there, you are in good shape still.
---------- Post added at 12:16 PM ---------- Previous post was at 12:15 PM ----------
Gokul Krishnamoorthy said:
Yes i relocked it after installing TWRP..
I can able to boot into the bootloader.. but how to unlock it??? fastboot and adb cmds aren't working...
Click to expand...
Click to collapse
why would you relock it? People unlock it for a reason, not to just install a recovery wipe the phone and then relock it.... That would not make sense and you can wipe it using factory reset.
Do this: http://forum.xda-developers.com/showthread.php?t=2507905
Toolkit: http://forum.xda-developers.com/showthread.php?t=2508817
some users are not a big fan of toolkits but I have never had a problem with them.
mistahseller said:
I think you are confused on what you did/ are trying to do. If you hold volume down and power button it will take you to fast boot, if you can get there, you are in good shape still.
---------- Post added at 12:16 PM ---------- Previous post was at 12:15 PM ----------
why would you relock it? People unlock it for a reason, not to just install a recovery wipe the phone and then relock it.... That would not make sense and you can wipe it using factory reset.
Do this: http://forum.xda-developers.com/showthread.php?t=2507905
Toolkit: http://forum.xda-developers.com/showthread.php?t=2508817
some users are not a big fan of toolkits but I have never had a problem with them.
Click to expand...
Click to collapse
Thank you So much ... You're an :angel: .. I unlocked the bootloader :good:
Gokul Krishnamoorthy said:
I unlocked the bootloader :good:
Click to expand...
Click to collapse
now leave it that way unless you're setting it up for return. cheers
How did he manage to get TWRP without unlocking the bootloader? he locked it after flashing TWRP or there is any way to bypass the bootloader without unlocking it??
Crap Crap Crap Crap Crap!
I forgot to Titanium Backup before doing the OTA update. Is there any way to get root back?
I am stock with root. I got root originally by unlocking the bootloader and doing the temp TWRP and then back to stock and relock.
My current state is 4.4.2 locked with stock bootloader. Is there any possible way to get root back without wiping the device?
Frick!
Thanks in advance
MrGrimace said:
Crap Crap Crap Crap Crap!
I forgot to Titanium Backup before doing the OTA update. Is there any way to get root back?
I am stock with root. I got root originally by unlocking the bootloader and doing the temp TWRP and then back to stock and relock.
My current state is 4.4.2 locked with stock bootloader. Is there any possible way to get root back without wiping the device?
Frick!
Thanks in advance
Click to expand...
Click to collapse
Just wondering... why would you ever want to relock the bootloader?
If the bootloader is locked and you don't have root, you're going to have to wipe it.
MrGrimace said:
Crap Crap Crap Crap Crap!
I forgot to Titanium Backup before doing the OTA update. Is there any way to get root back?
I am stock with root. I got root originally by unlocking the bootloader and doing the temp TWRP and then back to stock and relock.
My current state is 4.4.2 locked with stock bootloader. Is there any possible way to get root back without wiping the device?
Frick!
Thanks in advance
Click to expand...
Click to collapse
if you unlocked the bootloader once already, it doesn't automatically lock again. just flash TWRP again and then you can flash Super SU.
fastboot flash recovery (TWRP filename).img
*EDIT* didn't see that you relocked the bootloader... like above... why would you want to do that?
Lucke said:
if you unlocked the bootloader once already, it doesn't automatically lock again. just flash TWRP again and then you can flash Super SU.
fastboot flash recovery (TWRP filename).img
*EDIT* didn't see that you relocked the bootloader... like above... why would you want to do that?
Click to expand...
Click to collapse
Honestly. I hated the little icon on the startup screen.
That is more or less what I figured. Well ****e! My own damn fault.
*Goes to take his medicine and reload everything.*
There used to be a way to root the nexus 10 without unlocking. That is why I asked.
Don't wipe yet hold on a sec
sent from my HAMMERHEAD neXus
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
If u have root use this. https://play.google.com/store/apps/details?id=net.segv11.bootunlocker your post says your stock with root, correct? Im confused:what::what: never mind i guess you don't have root
sent from my HAMMERHEAD neXus
CRIME INC. said:
Don't wipe yet hold on a sec
sent from my HAMMERHEAD neXus
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
If u have root use this. https://play.google.com/store/apps/details?id=net.segv11.bootunlocker your post says your stock with root, correct? Im confused:what::what: never mind i guess you don't have root
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
Too Late. I am all back up and running now. It really isn't that big a pain, just time consuming. I relocked before because some said that there are ways to defeat the pattern lock via an unlocked bootloader. Since all I really want is root for Titanium Backup and AdFree, I figured why make myself more open to attack. *puts tinfoil back on head*
MrGrimace said:
Too Late. I am all back up and running now. It really isn't that big a pain, just time consuming. I relocked before because some said that there are ways to defeat the pattern lock via an unlocked bootloader. Since all I really want is root for Titanium Backup and AdFree, I figured why make myself more open to attack. *puts tinfoil back on head*
Click to expand...
Click to collapse
Well at least now you can use that app i linked, to lock and unlock your bootloader at will
sent from my HAMMERHEAD neXus
Greets,
I think I may have bricked my Droid Maxx but I'm hoping someone can verify before I deem it a paperweight. I was on SU-2-3.3 and used Sunshine on it to unlock it and then TWRP to root it. After fully booting up the phone and verifying root, I rebooted into TWRP and ran a full back up w md5. After that, I booted up the phone and used supersu survival mode and then took the OTA update. Now the phone boots to fastboot, but says "boot failed" under any of the options. It won't go into recovery nor will it normally boot up. I tried to use RSD to reflash to the latest version but it just said flash failed at the first file and says something about downgraded security, etc. So now, I can get into fastboot mode and the phone connects and is detected but won't let me flash anything... it was unlocked via Sunshine, but I may have borked it up somehow. Thoughts?
Try a more recent firmware but check your recovery
Sent from my D6616 using Tapatalk
I took the OTA... is there something more recent? Also, I've tried to flash other recoveries but I get "boot failed" at the fastboot menu.
ohhhh you must mean try and use a more recent firmware via RSD. I'll give that a shot
Ok i tried a newer firmware via RSD, now the fastboot mode shows "failed to read signatures for partition aboot" RSD fails at flashing partition gpt.bin
Since I seem to have a partition related error, would this LINK help my situation at all?
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
t3knokon said:
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
Click to expand...
Click to collapse
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
t3knokon said:
Since I seem to have a partition related error, would this LINK help my situation at all?
Click to expand...
Click to collapse
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
BladeRunner said:
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
Click to expand...
Click to collapse
Ok to clarify, after I unlocked via sunsine on 2-3.3, I rooted and I took the over the air so now I'm on the newer bootloader. Post those events I started to receive "failed to erase partition xxxx" I also just tried reflashing individual images from 4.4.4 su6-7 release and I still receive back "failed to erase... failed to flash... etc." I can get into fastboot mode but it seems crippled somehow.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
t3knokon said:
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
Click to expand...
Click to collapse
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
BladeRunner said:
well, he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet
....
Click to expand...
Click to collapse
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
crack.mech said:
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
Click to expand...
Click to collapse
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
t3knokon said:
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
Click to expand...
Click to collapse
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
BladeRunner said:
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
Click to expand...
Click to collapse
Thanks for that. I posted there as well... from a software standpoint, I'm curious to know what would be denying access to the partitions...
I messaged jcase and he looked at logs for the sunshine preinstall and they were clean. It's possibly a hardware failure unless someone else with bootloader knowledge, knows how to get around the partition permissions access. thoughts?
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
t3knokon said:
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
Click to expand...
Click to collapse
the prognosis is not good.
VBlack messaged me about shorting a pin to put the phone in Qualcomm Downloader mode... and then pushing software onto it to at least try to the partitions set up and get the bootloader in a manner which will allow for writing. If that doesn't work, there's nothing else to do. I read up on it extensively, and it's now a last ditch effort. I've never take apart a phone in that manner before, so it'll be a first for me.
Similar boat, here...using a programmer cord, I can flash a ROM onto the Maxx, but it stumble-boots into BP Tools mode after 3 or so failed 0-battery/unlocked bootloader warning screen loops. I can get it into bootloader with program cord, or first thing with factory cord. It won't charge at all, battery is new. Izzit hosed?
Sent from my XT1254 using XDA Free mobile app
Can I relock bootloader, and flash completely stock if I need?
Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked
suzook said:
Can I relock bootloader, and flash completely stock if I need?
Click to expand...
Click to collapse
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Bradl79 said:
Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked
Click to expand...
Click to collapse
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices
effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
Things are missing in recovery. Im hoping they forgot vs take the feature out.
Bradl79 said:
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices
Click to expand...
Click to collapse
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
intruda119 said:
Things are missing in recovery. Im hoping they forgot vs take the feature out.
Click to expand...
Click to collapse
Ah, got it. That sucks. :'( Thanks!
effmsee said:
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
Ah, got it. That sucks. :'( Thanks!
Click to expand...
Click to collapse
if all else fails we do have an unbrick tool, but from what i have read, u can no longer sideload with ur bootloader locked and there is not install from internal storage from stock recovery
I learned the hard way. Soft brick in the first hour of ownership.i thought I really broke something until eventually a few others reported on it. B
Op I would wait
I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.
BoboBrazil said:
I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.
Click to expand...
Click to collapse
Certain I did something wrong. But I tried the same thing initially and would bootloop to recovery after factory reset. Wasn't a biggie learned about the new a/b system in the process
Somewhat related question:
If you relock the bootloader, does Widevine go back to L1?
One user reported no. Is it really a permanent change of the Widevine status to unlock it?
I might be able to deal with 480p netflix, but if I sell this phone someday it sucks for the next owner.
No worry just try mega unbrick guide used it to relock bootloader and flash stock hydrogen os it can recover your device from even hardbrick I tested it for safety it works like charm so I recommend you that
Can anyone who has unlocked and re-locked their bootloader check their Widevine status in DRM info?
I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works
noppoer2 said:
I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works
Click to expand...
Click to collapse
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated
kailashnj said:
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated
Click to expand...
Click to collapse
Reinstall your rom ( i believe 5.1.6 ) to get rid of TWRP & root
Factory reset
Then on fastboot " fastboot oem lock"
Data & internal storage will be wiped
Which means post following the steps origins bootloader will be locked and I will not get the warning again right at the start of the phone
All you can do is try but first make a Nandroid just in case this falls through
Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.
thealexwu said:
Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.
Click to expand...
Click to collapse
Lock as you unlocked in cmd by typing lock instead of unlock. It will make a wipe, so I recommend make backup before.