Related
deleted htc framework file and phone doesnot start.
After rooted my htc One X. In the process of removing at&t crap ware I accidentally deleted something that said htc frame work.
From then on my phone would not start. I unlocked my phone as well. How ever I didnot have any custom ROM installed or didnot have any back up done.
When I tried to reboot my phone after deleting the htc frame work file, it would not start. HTC icon would show up and it would not go further.
These are the things I did.
1. I flashed CWM.
2.I flashed TWRP.
3.I finally flashed CWM. 5.8.3
Then I went to fastboot mode and
removed Dalvik Cache, Erased the sd card
and tried to 'mount usb storage' but it would say
"unable to open ums lunfile(no such file or directory)SD card space free:10169MB"
My phone though shows as a removable disk , when i click on the icon it would say " Please insert disk into removable disk." I tried to save a custom ROM on my memory card and flash it but my system doesnot detect my phone.
Can some one please help me?
Thank you.
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Lock bootloader run ruu start over. Next time the very first thing you do is make a nandroid back up.
redpoint73 said:
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Thanks for the quick reply.
When I tried to mount my phone as usb it would not. I mentioned that as well.
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online. Without installing a custom ROM and run RUU , do you think my phone works
Adding a note to it. my phone is s-on and did not have android sdk installed on my machine. i tried all this using fastboot files and twrp img.
Thank You
in00b said:
When I tried to mount my phone as usb it would not.
Click to expand...
Click to collapse
You mentioned you tried to mount USB using fastboot (I've never mounted USB using fastboot, so I can't comment on that). Try mounting USB within TWRP, and see if that works. FYI, the USB mount feature in CWM does not work, and CWM does not really support our device, and has major issues. That's why its strongly recommended you use TWRP and not CWM.
in00b said:
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online.
Click to expand...
Click to collapse
Website seems to be too busy now. As long as its not 2.20, it should be okay. Normally, I would caution against randomly searching around the internet for things and flashing them, and instead getting them here instead. But briefmobile is Kenneth Penn's website, and he is a known developer on XDA.
in00b said:
Without installing a custom ROM and run RUU , do you think my phone works
Click to expand...
Click to collapse
You deleted part of the OS, so I'd say no. It doesn't boot does it? Then it doesn't work.
Also, please click "Thanks" to the post that help you.
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
No, you can only have one recovery. Flash one, you overwrite whatever you had before.
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
I'd stay away from CWM. I know it used to cause problems, but I don't know if it does anymore.
Most everybody here (in the One XL forums) prefer TWRP anyways.
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
in00b said:
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
Click to expand...
Click to collapse
Did you lock your bootloader before running the RUU?
Butters619 said:
Did you lock your bootloader before running the RUU?
Click to expand...
Click to collapse
nope my phone was boot loader unlocked and s-on.
in00b said:
nope my phone was boot loader unlocked and s-on.
Click to expand...
Click to collapse
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Butters619 said:
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Click to expand...
Click to collapse
thanks i will try unlocking my phone and get back to you.
in00b said:
how do i relock my phone.that doesnt turn on at all. all i see is htc screen and it wouldnt go any further.
Click to expand...
Click to collapse
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
qwertyaas said:
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
Click to expand...
Click to collapse
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
But in almost every thread things have to be said 2-3 times which is ridiculous
Butters619 said:
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Click to expand...
Click to collapse
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
in00b said:
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
Click to expand...
Click to collapse
See that thanks button. Go through this entire thread and press it for everyone who helped you (aka everyone). Especially gunny.
And remember, things that sound important (framework, build., etc...) typically are important random assassinations typically get the shooter in trouble
18th.abn said:
random assassinations typically get the shooter in trouble
Click to expand...
Click to collapse
lol
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Butters619 said:
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
Click to expand...
Click to collapse
Maybe he's more a fan of the Butters cartoon character than he is Totoro?
Hey guys, im trying to flash my htc one xl to viperXL. I've gotten TWRP on it and I made a backup and installed ViperXL but it keeps going to a boot loop.I managed to get it into recovery and it showed that my SDCard was wiped. I couldnt restore it, any help? I will provide more detail if asked. I just want to restore it to stock
Please someone help me ;( I just want to get back to stock.
Did you factory reset in bootloader?
Sent from my Evita
SD has been corrupted. Possibly because you did a factory reset in bootloader (known bug) as mentioned in the previous reply.
Plug the device into a Windows PC, go to device manager and format the SD. Then mount the SD in TWRP and move a ROM to the device, and flash.
timmaaa said:
Did you factory reset in bootloader?
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
SD has been corrupted. Possibly because you did a factory reset in bootloader (known bug) as mentioned in the previous reply.
Plug the device into a Windows PC, go to device manager and format the SD. Then mount the SD in TWRP and move a ROM to the device, and flash.
Click to expand...
Click to collapse
Holy ****! thank you!!!!!! I searched everywhere for a fix. You guys are lifesavers I thought It was bricked for good!!!!!
Zehmistah said:
Holy ****! thank you!!!!!! I searched everywhere for a fix. You guys are lifesavers I thought It was bricked for good!!!!!
Click to expand...
Click to collapse
Also don't forget if you are S-ON that you should flash the boot.img manually after you flash a new ROM. I use TN_WIN_Boot_Installer to ease this task.
drubin333 said:
Also don't forget if you are S-ON that you should flash the boot.img manually after you flash a new ROM. I use TN_WIN_Boot_Installer to ease this task.
Click to expand...
Click to collapse
What's hard about "fastboot flash boot boot.img" to begin with.... Using tools only adds risk
Or flashimagegui
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?
I RMA'd my device and need to reset the tamper flag. I followed the instructions here in the forums, but it is not working. I've tried 2 different methods.
1) Download the flashable zip file and use fast boot to boot into TWRP. The problem with this is that once i boot into TWRP, it does not recognize any files in the sdcard/downloads folder.
2) Download boot unlocker from the playstore. I need an unlocked and rooted device so this seems pointless as I will need to unlock and relock my boot loader to use this.
Someone please help.
ILowry282 said:
I RMA'd my device and need to reset the tamper flag. I followed the instructions here in the forums, but it is not working. I've tried 2 different methods.
1) Download the flashable zip file and use fast boot to boot into TWRP. The problem with this is that once i boot into TWRP, it does not recognize any files in the sdcard/downloads folder.
2) Download boot unlocker from the playstore. I need an unlocked and rooted device so this seems pointless as I will need to unlock and relock my boot loader to use this.
Someone please help.
Click to expand...
Click to collapse
in short do u want to unroot ur phone completely ?!! watch this video completely and follow it
http://youtube.com/watch?v=-L2fMZl027E
Sent from my Nexus 5 using Tapatalk
ILowry282 said:
I RMA'd my device and need to reset the tamper flag. I followed the instructions here in the forums, but it is not working. I've tried 2 different methods.
1) Download the flashable zip file and use fast boot to boot into TWRP. The problem with this is that once i boot into TWRP, it does not recognize any files in the sdcard/downloads folder.
2) Download boot unlocker from the playstore. I need an unlocked and rooted device so this seems pointless as I will need to unlock and relock my boot loader to use this.
Someone please help.
Click to expand...
Click to collapse
Re-root the device with TWRP. Then download bootunlocker and reset the tamper flag. Then flash the factory image, relock the bootloader, and you'll be good to go.
rahil3108 said:
in short do u want to unroot ur phone completely ?!! watch this video completely and follow it
http://youtube.com/watch?v=-L2fMZl027E
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I followed that video and it did not work. First off, I can't find that zip file anywhere. The link on the xda forums doesn't give me the correct file. Second, I have a mac. For me to boot into TWRP using fast boot, it required the boot loader to be unlocked. If I unlock the boot loader to boot into TWRP via fast boot, TWRP doesn't recognize any files in the downloads folder.
ILowry282 said:
I followed that video and it did not work. First off, I can't find that zip file anywhere. The link on the xda forums doesn't give me the correct file. Second, I have a mac. For me to boot into TWRP using fast boot, it required the boot loader to be unlocked. If I unlock the boot loader to boot into TWRP via fast boot, TWRP doesn't recognize any files in the downloads folder.
Click to expand...
Click to collapse
Bro,
1. Flash the factory image in fastboot
2. Download the latest TWRP recovery and rename it to twrp.img and put it in the fastboot folder and download this zip http://forum.xda-developers.com/attachment.php?attachmentid=2467503&d=1387666907 and put it on the phone`s sdcard.
3. Go into bootloader mode and flash the downloaded zip in recovery, just type in cmd: `fastboot boot twrp.img` and you`ll boot into twrp recovery.
4. Done, you`re device is locked and the tampered flag is reset.
Oeps saw you have a Mac so look here:
Full tutorial: http://www.youtube.com/watch?v=PX4R6IhcoTM.
---------- Post added at 08:15 AM ---------- Previous post was at 08:06 AM ----------
[/COLOR]
BirchBarlow said:
Re-root the device with TWRP. Then download bootunlocker and reset the tamper flag. Then flash the factory image, relock the bootloader, and you'll be good to go.
Click to expand...
Click to collapse
Wrong order bro, and why would you have to reroot to flash twtp as long as the bootloader is unlocked. Once the bootloader is locked you can`t flash the image anymore
gee2012 said:
Wrong order bro, and why would you have to reroot to flash twtp as long as the bootloader is unlocked. Once the bootloader is locked you can`t flash the image anymore
Click to expand...
Click to collapse
Because you need root to run BootUnlocker in order to reset the tamper flag. Resetting the tamper flag is the first thing you should do, relocking the bootloader is the last.
BirchBarlow said:
Because you need root to run BootUnlocker in order to reset the tamper flag. Resetting the tamper flag is the first thing you should do, relocking the bootloader is the last.
Click to expand...
Click to collapse
You don't need root for that bro and relocking and resetting the flag goes in one go with the bootunlocker script at the end.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
gee2012 said:
You don't need root for that bro ☺
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
You do to use the BootUnlocker android app.
rootSU said:
You do to use the BootUnlocker android app.
Click to expand...
Click to collapse
No, i was talking about this script http://forum.xda-developers.com/attachment.php?attachmentid=2467503&d=1387666907 from here http://forum.xda-developers.com/showthread.php?t=2239421 to reset the tampered flag and relock the BL.
gee2012 said:
You don't need root for that bro and relocking and resetting the flag goes in one go with the bootunlocker script at the end.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
The OP stated he couldn't get the script to work or didn't know how. My advice was that he use the app instead.
BirchBarlow said:
The OP stated he couldn't get the script to work or didn't know how. My advice was that he use the app instead.
Click to expand...
Click to collapse
Oke, initialy i thought he had a windows PC and saw later he had a Mac. Does the Bootlocker app also reset the tampered flag? Haven`t used it myself yet.
gee2012 said:
Oke, initialy i thought he had a windows PC and saw later he had a Mac. Does the Bootlocker app also reset the tampered flag? Haven`t used it myself yet.
Click to expand...
Click to collapse
Yep it does. With BootUnlocker, you don't even need the script, and you can lock/unlock the bootloader any time without wiping your data and you can also reset the tamper flag.
BirchBarlow said:
Yep it does. With BootUnlocker, you don't even need the script, and you can lock/unlock the bootloader any time without wiping your data and you can also reset the tamper flag.
Click to expand...
Click to collapse
Yeah it's great too. I keep my bootloader locked and tamper flag reset. This way, no one can access my data except through recovery. What I hope for next is locking recovery
</offtopic>
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
rootSU said:
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Android.Addiction said:
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Click to expand...
Click to collapse
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Aerowinder said:
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Click to expand...
Click to collapse
So far I've just been running the steps inside ./flash-all.sh manually:
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-hammerhead-kot49h.zip
I can add this extra step before the above commands if needed:
fastboot erase userdata
Thanks man!
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Lanchon said:
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Click to expand...
Click to collapse
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
The steps the last guy quoted did flash factory images before locking.
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
lol yes he did, sorry! i thought he run the toggle-lock/reset-tamper script. my bad.
EddyOS said:
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
Click to expand...
Click to collapse
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
rootSU said:
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
Click to expand...
Click to collapse
In a nutshell, although the guide in my signature covers all bases with the OPO as I wrote it when I had one!
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Lanchon said:
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Click to expand...
Click to collapse
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
all N5 have tamper flag. it was introduced mid life of the N4 via a bootloader upgrade. i had an N4 at the time and thought that move was sh*tty.
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
Yes it does
EddyOS said:
Yes it does
Click to expand...
Click to collapse
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
EddyOS said:
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
Click to expand...
Click to collapse
yes, we've established the steps are ok and it was my misreading.
but regarding my warning about locking with non working stock recovery: its not been documented, but im sure it happens all the same! the bootloader uses a recovery (presumably the one recovery we know and not an image embedded in the bootloader itself) to wipe data. and it would be a mistake to unlock before wiping. so the bootloader does the wipe-then-unlock by delegating everything to the recovery. no recovery, no unlock.
gee2012 said:
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
Click to expand...
Click to collapse
When connected in fastboot, type
fastboot oem device-info
And it'll show device tampered true or false
To get it all back to stock, flash the factory image completely then boot TWRP (don't flash it) and run the bootunlocker script found in the Nexus 5 unroot thread