Related
im gona send my phone in as a replacement, but i want to make sure everything looks stock before it send it in, i found a couple of ways to return to stock but i keep getting signiture verified failed, and i assume its because i have an unlocked bootloader, can any 1 help?
You should be able to find the stock rom for unlocked users in the development section. Just flash that and you will be back on stock.
But you can't re-lock the bootloader. When you unlocked it you voided the warranty, and it stays that way.
If it is a physical hardware problem, you should be able to still get warranty though.
Sorry, I meant to say my bootloader is locked, I don't have a problem with the rom, but the recovery. I am on ra recovery atm and I want to go back to google's stock. Is there anyway to do that?
Im pretty sure this works for all phones but if you flash Official OTA it will put everything back to stock(except bootloader if it has been unlocked) but doing this you will also loose root as well
i would wait for some one to tell you another way to get back to stock recovery, im sure there is a way to do it in adb or something.. Flashing the official OTA should be like a last thing wanting to do
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
codearray said:
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
Click to expand...
Click to collapse
He cant do fastboot, he has locked Bootloader.
yeah, it saids verification failed and wouldnt let me flash anything onto it
oops my bad. I had an unlocked bootloader. My other phone is locked.
sent from outter space
vvaffles said:
yeah, it saids verification failed and wouldnt let me flash anything onto it
Click to expand...
Click to collapse
Yeah i had the same problem when i tried to revert mine to stock. My bootloader was lock and wouldnt let me reflash the stock rom with verification failed.
NOT SURE IF THIS IS THE CORRECT WAY, DO AT YOUR OWN RISK :
I renamed the image to PASSIMG.zip and booted into bootloader. The bootloader automatically searches for PASSIMG and when it found it went through an update/installing process which took about 5minutes. When it booted phone was unrooted again, and had the stock recovery.
Once that was done, i installed the FRF85 (i think) update.zip from bootloader recovery, then did the same with update.zip for FRF91.
Again not sure if this was the correct way as i have never seen posts directing to do it this way - have posted questions about it in the past week or two, but never got any responses...
I'm gonna bump this thread up again. I tried downloading the original PASSIMG file for the stock and when I try and flash it by putting it on the SD card I get that the main file is older and the install is aborted. I can't fastboot the files because my bootloader is not unlocked. I'm currently running a FRG83 based ROM, does this matter? I'd like to return my phone to stock recovery and stock ROM, but so far every attempt has been met in failure... I guess it's an irony of rooting a phone without unlocking a bootloader. If you have to send it in for repairs you have to unlock the bootloader to return to stock, or you can't return to stock and you're left with custom recovery and root... either way HTC knows you're rooted. I know my issue is a hardware issue, but it would be my luck they decide to void my whole warranty.
You can't just PASSIMG your way back from FRG83, if you have it - since there's no PASSIMG for FRG83 yet (at least I'm not aware of one, and looks like Google isn't either), and the system is designed not to flash older builds. Trying to use PASSIMG to return to older builds requires some heavy preparations (has to be rooted, then downgrading HBOOT and probably flashing initial system.img from an older build through adb in recovery, using flash_image). It's possible and not very hard to do, but most probably beyond "1-click-root"ers' skills. All the relevant info is in the Wiki, so if you want to attempt it - you can try.
Unrooting FRG83 (reflashing stock recovery from FRF91, removing su and Superuser.apk from root shell) might be easier.
Also, put attention that if the phone has SLCD screen - the official stock FRF91 won't work on it.
I actually was able to PASSIMG to FRG33 then OTA back to FRG83. which I thought was odd due to the fact that I was on a FRG83 based rom. Oh well, it's 100% back to stock now. So even though people say that a rooted/unlocked phone only voids your software warranty I don't have to worry about it. Yay for keeping a locked bootloader.
Dear all,
I know I am kind of stupid at first... applied an OTA from Motorola recently and found that I lost root. Now that I have found that my bootloader will NOT be flashed by any mean, RSDLite or sbf_flash, it stays FOREVER at 90.73. What can I do? Thanks for any help. Other parts flash fine it seems...
Kings
If you only want root back try universal androot. You only have to install it and press one button to activate root. For me this worked. If you want recovery back, try flashing one of those sbf with vulnerable bootloader. You can find them here:http://and-developers.com/sbf:milestone
The easiest way is to flash GOT's beta. That will give you a vulnerable bootloader and root at the same time.
Recovery is one thing, bootloader another.
There's nothing wrong with the 90.73 bootloader, afaik.
I've got the 90.73 on my phone and I don't feel any need to update it to 90.74. The only known difference is the key used to boot to the recovery (camera vs. x) and the ability to flash an older firmware (bootloader won't let you to downgrade to a firmware older than your current bootloader version).
To update the bootloader, you would need to use the special mbm update sbf.
But as I've said, I don't know about a single reason to do it (unless your camera button is broken ).
I think his problem is, that after the update his root is lost and he wanted to apply it via recovery. But the bootloader is no longer vulnerable and so he cant apply the update.zip. Am i right?
No. As kabaldan said, bootloader and recovery are two different things.
thank you for all of you.
my problem is that I cannot put ANY of the vulnerable recovery on my milestone. it seems to me that this is motorola's new trick, as I cannot find the script within system/etc that will replace whatever recovery you have with a non-vulnerable one as some other post describes. I am not 100% sure though.
You can find a tutorial on kabaldans website for making the recovery vulnerable. There is also your case inside. Maybe this will help you. Also your issue could be solved by flashing a full sbf, where this script isnt implemented. You could flash on of GOT's sbf, they have vulnerable recovery.
Oh, thank you very much to all of you. Since everybody is so certain Moto does not bring up anything new, so I reviewed my process again...
And found that... I am so stupid!
I did not unzip the Open recovery zip file but renamed it to update.zip instead.
And I also thought that applying vulnerable bootloader will change my bootloader version...
Thank you very much for all of your patience.
I need to return my phone to stock (S-ON, CID: GLOBA001) and i cant seem to be able to find the appropriate files. Any help would be greatly appreciated.
Nastradamus said:
I need to return my phone to stock (S-ON, CID: GLOBA001) and i cant seem to be able to find the appropriate files. Any help would be greatly appreciated.
Click to expand...
Click to collapse
There is no RUU for WIND, afaik. Sorry
alray said:
There is no RUU for WIND, afaik. Sorry
Click to expand...
Click to collapse
Is there somewhere i can maybe find a saved backup of stock ROM. Or do you know any other way i can get back to stock ROM with S-ON? Thanks for your help!
Nastradamus said:
Is there somewhere i can maybe find a saved backup of stock ROM. Or do you know any other way i can get back to stock ROM with S-ON? Thanks for your help!
Click to expand...
Click to collapse
Do you need to get back to stock for warranty purpose?
What is your firmware version? (fastboot getvar all) or (fastboot getvar version-main)
alray said:
Do you need to get back to stock for warranty purpose?
What is your firmware version? (fastboot getvar all) or (fastboot getvar version-main)
Click to expand...
Click to collapse
Yea I want to send my phone in under warranty due to a problem with the wifi where it doesnt work and just gets stuck on ON. From what ive read everyone who had this problem ended up sending in their phone and just got a replacement. I originally had this problem while I was in stock so I tried out a custom ROM to see if that would fix the problem.
After putting a custom ROM didnt fix the problem, to try get back to stock I used a guru reset file. The CID from the reset file didnt match my phone but I gave it a shot. So now my phone has stock rom with android 4.3. Then I wanted to get an OTA so everything else would go to stock like kernel (Im fairly new to rooting and stuff so that's what I understood would happen). But my phone wont accept an OTA, after downloading for a bit it basically says that some modifications have been made to the software so it cant get the OTA.
I cant get my getvarall until later when I get home but from the about menu in the phone it says that the softwarenumber is 3.22.661.1 (is that firmware version?). ill post my getvarall when I get home.
If there's a way that you know I can get back to stock, that would be awesome. Thanks alot for your help.
Nastradamus said:
Yea I want to send my phone in under warranty due to a problem with the wifi where it doesnt work and just gets stuck on ON. From what ive read everyone who had this problem ended up sending in their phone and just got a replacement. I originally had this problem while I was in stock so I tried out a custom ROM to see if that would fix the problem.
After putting a custom ROM didnt fix the problem, to try get back to stock I used a guru reset file. The CID from the reset file didnt match my phone but I gave it a shot. So now my phone has stock rom with android 4.3. Then I wanted to get an OTA so everything else would go to stock like kernel (Im fairly new to rooting and stuff so that's what I understood would happen). But my phone wont accept an OTA, after downloading for a bit it basically says that some modifications have been made to the software so it cant get the OTA.
I cant get my getvarall until later when I get home but from the about menu in the phone it says that the softwarenumber is 3.22.661.1 (is that firmware version?). ill post my getvarall when I get home.
If there's a way that you know I can get back to stock, that would be awesome. Thanks alot for your help.
Click to expand...
Click to collapse
3.22.661.1 is telus ROM. I need to know what is your firmware version (from the bootloader or from the getvar all) so we can check if there is anything available to restore your phone (most likely a Nandroid backup). Both your software version and firmware version must be the same.
For warranty to be valid. your phone must be 100% stock which mean stock rom and firmware, no tampered flag in the bootloader. bootloader status must be "locked" (not re-locked or unlocked). Removing the tampered flag and resetting the bootloader to "locked" require s-off. There is nothing available for WIND (no RUU, no nandroid backup (to confirm with your firmware version)). So flashing a custom rom before checking for these files was not a good idea. When the phone is under warranty, you should always send it for repair because troubleshooting it by flashing custom roms (and unlocking the bootloader) void the warranty, unless you can return your phone to 100% stock (files needed and s-off needed).
But sometime, ppl are lucky and HTC will repair the phone even if its not stock. If they think the custom software might have caused the wifi problem, then they will charge you for the repair. If its an hardware defect, then you might get it repaired at no cost, at HTC discretion.
For ota update, you can't use them atm because the software version (TELUS) doesn't match your firmware version and CID (WIND)
Btw, is your wifi problem only on lollipop? I had some problem too and it was caused by the power saver mode. Disabling it (or at least the wifi power saver option) solved my issue. Just in case...
alray said:
3.22.661.1 is telus ROM. I need to know what is your firmware version (from the bootloader or from the getvar all) so we can check if there is anything available to restore your phone (most likely a Nandroid backup). Both your software version and firmware version must be the same.
For warranty to be valid. your phone must be 100% stock which mean stock rom and firmware, no tampered flag in the bootloader. bootloader status must be "locked" (not re-locked or unlocked). Removing the tampered flag and resetting the bootloader to "locked" require s-off. There is nothing available for WIND (no RUU, no nandroid backup (to confirm with your firmware version)). So flashing a custom rom before checking for these files was not a good idea. When the phone is under warranty, you should always send it for repair because troubleshooting it by flashing custom roms (and unlocking the bootloader) void the warranty, unless you can return your phone to 100% stock (files needed and s-off needed).
But sometime, ppl are lucky and HTC will repair the phone even if its not stock. If they think the custom software might have caused the wifi problem, then they will charge you for the repair. If its an hardware defect, then you might get it repaired at no cost, at HTC discretion.
For ota update, you can't use them atm because the software version (TELUS) doesn't match your firmware version and CID (WIND)
Btw, is your wifi problem only on lollipop? I had some problem too and it was caused by the power saver mode. Disabling it (or at least the wifi power saver option) solved my issue. Just in case...
Click to expand...
Click to collapse
The problem started when I had stock kitkat and persisted when I tried a custom rom based off lollipop (MaximusHD) and jelly bean which I currently have from the telus gurureset file. Yea I messed up by rooting and flashing custom rom in hopes of fixing the problem. Now I just want to get back to stock with relocked bootloader and hope it gets through warranty.
Ill post getvarall later today when I get home. btw there are a couple things I should black out before posting that right? Could you tell me which ones?
Thanks
alray said:
3.22.661.1 is telus ROM. I need to know what is your firmware version (from the bootloader or from the getvar all) so we can check if there is anything available to restore your phone (most likely a Nandroid backup). Both your software version and firmware version must be the same.
For warranty to be valid. your phone must be 100% stock which mean stock rom and firmware, no tampered flag in the bootloader. bootloader status must be "locked" (not re-locked or unlocked). Removing the tampered flag and resetting the bootloader to "locked" require s-off. There is nothing available for WIND (no RUU, no nandroid backup (to confirm with your firmware version)). So flashing a custom rom before checking for these files was not a good idea. When the phone is under warranty, you should always send it for repair because troubleshooting it by flashing custom roms (and unlocking the bootloader) void the warranty, unless you can return your phone to 100% stock (files needed and s-off needed).
But sometime, ppl are lucky and HTC will repair the phone even if its not stock. If they think the custom software might have caused the wifi problem, then they will charge you for the repair. If its an hardware defect, then you might get it repaired at no cost, at HTC discretion.
For ota update, you can't use them atm because the software version (TELUS) doesn't match your firmware version and CID (WIND)
Btw, is your wifi problem only on lollipop? I had some problem too and it was caused by the power saver mode. Disabling it (or at least the wifi power saver option) solved my issue. Just in case...
Click to expand...
Click to collapse
My firmware version is 5.11.1500.8
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?
did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.
Hi everyone
Here's the situation
A few days ago i sent my pone to repair because i messed up with the IMEI and need it to be restored, the guy flashed it bak to stock and left the root in my phone, i unrooted manually and when i restarted my phone it said "Custom Binary blocker by FRP".
Then i flashed back the stock firmware with odin, and then i get this error "Security Error This phone has been flashed with unofficial firmware" and it does not leave me to unlock it via Device Unlock.
I have tried to Factory reset via recovery after i flashed the stock firmware
At this point i don't know what to do, so if you help me it i'll be very appreciated!
Have you resolved this issue?
If not, there's like hood you have messed up efs
Your imei and s/n probably not correct now.
You will need to repair your imei.
Using Z3x.
I used to have same issue, but got it resolved.