Related
Hi all,
My first rom is paysrom 5.1. So to get this rom i flashed 3.4.3-11 uk sbf. I know, i can't downgrade for 2.51.1.
For installing rom in different post, we need to flash another sbf. That's the first instruction before flashing rom. That's mean to downgrade the 3.4.3-11 uk sbf.
I saw after many search that we can't downgrade sbf without brick the phone.
Now how can try differents roms?
Need help, please.
I ask some different people on some different post and have many different answer.
1/ flash sbf boot only after wipe everything and flash the rom
2/ install 2ndinit and flash the rom you like after wipe everything, without changing your sbf
3/ restore nand backup rom you like and flash sbf after
...
Wich is to safe ?
The problem : i live in madagascar and they don't have motorola support here if i brick the phone. Need to send the phone in europe.
Sent from my MB525 using XDA App
I've find an affordable solution so I've decided to modify the original thread in order to give immediately to all who reads the correct procedure.
Later on this message you can still see the original start of the thread, for future references.
________________________________
How to downgrade from Froyo 2.2.2 v3.4.2-177 to Eclair 2.1 v2.51.1.
Requirement:
- Defy Android 2.2.2 v3.4.2-177 (probably other versions also) flashed from the phone itself or from direct sbf original file and RSD Lite.
- Rooted. You can use SuperOneClick on both android version.
- Defy Recovery 1218 0326 signed.apk. you can find it here.
- A nandroid backup of the old Eclair system (made by yourself otherwise you can quite easly find one on the internet and on XDA)
- the original full sbf file of Eclair system (many are here) in order to create a fixed sbf or directly the fixed sbf.
- Moto Android Firmware Depacker V.1.2 a3.exe (a Windows executable that need Dot Net FX 2.0 and it's able to pack and unpack OEM sbf files).
- RSD Lite and obviously the USB Windows Moto drivers.
Before proceding you need to create or to obtain such called fixed sbf made from the same version you're going to downgrade, so from Eclair 2.51.1.
You can find such fixed sbf online but for safety I prefer to made it by myself. It's so easy.
1. open the original full sbf with Moto Android Firmware Depacker V.1.2 a3 and split to folder;
2. remove CG31.smg and CG39.smg
3. open the extracted folder (the same you've just removed the files) and compile files.
The resulting file is the fixed sbf file you'll need soon ;-)
The procedure:
1. Install drivers and RSD Lite on pc and test the driver. USB debug must be always OFF (exepted for the superonclick rooting procedure)
2. Root the Froyo, reboot, install Defy Recovery and push to the sdcard the nandroid backup of your Eclair. The backup dir should be placed here: /sdcard/goapkrev/backup/
3. open Defy Recovery app and tap recovery boot.
4. wipe data/factory (so your're gonna loose everything on Froyo. Make a backup before, if you want)
5. restore the nandroid backup of the Eclair system.
6. pay attenction to reboot and immediatly push power + vol up in order to go to the bootloader mode. Otherwise the boot will loop and you need to pull the battery off.
7. with RSD Lite flash the fixed sbf. Wait untill the automatic reboot ends, and RSD Lite tells you PASS.
You've done
The M logo is now white, the standard recovery is restored, the haptic feedback works and everything is Eclair
If you appreciate, a thanks is more than enought
________________________________
Original start of the thread:
I've decided to open a new thread because I still don't find a final, safe, topic on how to downgrade from the latest Froyo to Eclair.
There are many topic on it but seems there are a little confusion.
The XDA official topic on the Developers page called "SBF - Service Flash -files "READ THIS FIRST if you try to flash new stock sbf" says litterally:
If you have flashed direct Android 2.2 via sbf -->
No direct downgrade for all 3.4 Froyo beta ROMs to Android 2.1 or official Android 2.2
No direct downgrade for 2.51.1 and 2.59 Eclair
I do not know what a "beta" Froyo is, but I know that I was able to switch from Defy Android 2.2 Froyo OEM JRDNEM U3 3.4.2 164-003 BLUR France to MIUI and viceversa using RSD lite for Froyo and zip install for MIUI.
Or MIUI is not a "beta" as intended before, but the JRDNEM U3 3.4.2 164 was the OEM france edition.
In any case here my question, and my situation:
Question: what is the real safe way to downgrade from 3.4.2-177 en.it to 2.51.1 en.it ??
My actual situation: I have Froyo 3.4.2-177 en.it, and it was direct sbf flashed; but I have a copy of my previous Eclair 2.51.1 by. Nandroid.
Is that procedure correct and really safe?
________________________________
1. Boot from Froyo in advanced recovery, factory reset and dalvik erase and ...
2. restore a nandroid backup of my previous Eclair and ... reboot.
3. the reboot should loop because the partitions are different signed or the nandroid backup is not able to overwrite the froyo bootloader, right?? so ...
4. pull battery and push again while press volume + to go bootloader (this should work 100%?? any possibility of complete dead defy?? It's really possible to ALWAYS and in any conditions access bootloader in order to connect RDS lite?).
5. Flash with RSD Lite a fixed sbf, where that should means: open the OEM 2.51.1 sbf with MotoAndroidDepacker-1.2alpha3, erase CG31 and CG39, repack and that's a ready to work fixed sbf?? reboot
________________________________
After that my old Eclair should work even on a Froyo bootloader?
I need to downgrade only because I have all my configuration on the old system, and I would have the occasion to copy some configuration settings before going definitively to Froyo.
Is that downgrade safe or dangerous?
After the downgrade is it possible to direct flash back the original Froyo 3.4.2-177 sbf with RSD Lite like before?
Thank you in advance for all your kind reply.
That will work
SeaFargo said:
It's really possible to ALWAYS and in any conditions access bootloader in order to connect RDS lite?
Click to expand...
Click to collapse
Yes.
Until your phone will enter into bootloader mode ( volume up button before turning on ), you'll be able to flash via RDS lite.
Thank you, mpiekp
Thanks to carlo93, also.
But Carlo, my phone should always be able to load in bootloader mode? In other words, can I, with the mentioned procedure, corrupt the boot sector in such a way to NOT be able to boot in bootloader mode anymore?
or ... is there a way (so I can pay very very attenction to avoid it) to corrupt the bootloader mode?
I know that till I reach bootloader mode I always be able to flash with RSD Lite. But can I, working with roms (nandroids and sbf), be able to crash the bootloader mode so I can't reach it anymore or not?
SeaFargo said:
But can I, working with roms (nandroids and sbf), be able to crash the bootloader mode so I can't reach it anymore or not?
Click to expand...
Click to collapse
Maybe if something goes wrong while flashing a sbf via RSD Lite ( i.e. black out during a flashing, i hope this will never occur... )...
Otherwise there's no reason of being afraid .
Question for update
currently i m running cm7 rom for gingerbread. if i revoke back to original one . (i messed up big time cause i didnt get a chance to make a nanodroid backup of my own eclair ).. so i guess i have to follow ur tutorial to revert back to my eclair 2.1 update one firmware version = 2.59
what i wanna know is if i would b able to get the official froyo via msu if i revert back to my original eclair 2.1 firmware 2.59 using full sbf method.. is it at all possible ?
Nandroid restore + fixed sbf
joydeep1985 said:
currently i m running cm7 rom for gingerbread. if i revoke back to original one . (i messed up big time cause i didnt get a chance to make a nanodroid backup of my own eclair ).. so i guess i have to follow ur tutorial to revert back to my eclair 2.1 update one firmware version = 2.59
what i wanna know is if i would b able to get the official froyo via msu if i revert back to my original eclair 2.1 firmware 2.59 using full sbf method.. is it at all possible ?
Click to expand...
Click to collapse
Dear joydeep1985, first of all I've never flashed CM7 so I don't know how to go back from it to original Froyo, but I have no reason to doubt it is different from going back from MIUI, that I've tested. So a complete wipe, than a full Froyo sbf flash should work.
After that, to downgrade to Eclair, I have read in many forum, in XDA also, thant the direct Eclair sbf flash with RSD Lite procedure doesn't works!
The original sbf are made to upgrade from previous system or to repair the same version system, but are not enough to downgrade from a more recent system.
A nandroid backup only can do so, in conjuncion with a fixed sbf as I mention in this guide.
I do not know the exact reason why, maybe nandroid is able to restore overwriteing much more than the original Eclair full sbf.
In any case I can confirm thant, from a flashed full OEM Froyo, it is possible to succesful downgrade using nandroid + fixed sbf.
If you do not have a nandroid backup file that's not a big problem. There are many in internet, and in this forum also.
SeaFargo said:
Dear joydeep1985, first of all I've never flashed CM7 so I don't know how to go back from it to original Froyo, but I have no reason to doubt it is different from going back from MIUI, that I've tested. So a complete wipe, than a full Froyo sbf flash should work.
After that, to downgrade to Eclair, I have read in many forum, in XDA also, thant the direct Eclair sbf flash with RSD Lite procedure doesn't works!
The original sbf are made to upgrade from previous system or to repair the same version system, but are not enough to downgrade from a more recent system.
A nandroid backup only can do so, in conjuncion with a fixed sbf as I mention in this guide.
I do not know the exact reason why, maybe nandroid is able to restore overwriteing much more than the original Eclair full sbf.
In any case I can confirm thant, from a flashed full OEM Froyo, it is possible to succesful downgrade using nandroid + fixed sbf.
If you do not have a nandroid backup file that's not a big problem. There are many in internet, and in this forum also.
Click to expand...
Click to collapse
that was really a nice reply.... one more thing i would like to know .... in clockworkmod i dint get to see the nanodroid option.. also when i extracted the zip it gave me some img files .... like boot.img,android_secure.img etc in the nanodroid backup... when i put all the files under /sdcard/clockworkmod/backup and then choose the option restore . it doesnt seem to work at all. also due to no options such as present in clockworkmod > 3 i am not able to understand why its not working . how to make it work with clockworkmod >3 ???
In Froyo I've used Defy Recovery 1218 0326 signed.apk (the link is on the guide).
It works perfectly.
And the dir in wich you have to push the nandroid backup files is:
/sdcard/goapkrev/backup/
So at the end it will result something like:
/sdcard/goapkrev/backup/Eclair-2011-06-07
Beaware that the all path must be named without spaces.
one more question i have ... after my downgrade will i be able to update from motorola msu ? for official froyo update ? if i have to get that what i need to do ? can u please explain what are the requirements if i have to get the software update from motorola msu ? so that after my downgrade to eclair (i dont have my original nanodroid backup) i can update from motorola official MSU ?
joydeep1985 said:
one more question i have ... after my downgrade will i be able to update from motorola msu ? for official froyo update ? if i have to get that what i need to do ? can u please explain what are the requirements if i have to get the software update from motorola msu ? so that after my downgrade to eclair (i dont have my original nanodroid backup) i can update from motorola official MSU ?
Click to expand...
Click to collapse
I still do not know, because my Eclair was personally deblurred, and without Blur the "update firmware" doesn't works.
But I can confirm that, from this procedure downgraded Eclair, it will be perfectly possible to upgrade to Froyo by flashing its full sbf file with RSD Lite.
In any case I suggest to keep a copy in your PC for future references of:
- the OEM full sbf files of all the versions of Android you've using (from here and from a lot of places over the internet);
- the Nandroid backup of the installed, factory reset, versions of Android you've using (so before downgrade and afrer the factory reset make a nice backup of your actual Froyo);
- the zipped copy of the pulled system dir of the versions of Android you've using (by the command example like this: adb pull system "D:\Temp\Defy\pull system Froyo Defy")
SeaFargo said:
I still do not know, because my Eclair was personally deblurred, and without Blur the "update firmware" doesn't works.
Click to expand...
Click to collapse
oops that might be a problem cause my personal one came with blurred ...and the service flashes found in the link you provided are all without blur ( as you have stated ) so arent there any method left then ? so that i can revert back to original motoblur 2.1 update 1 eclair ? cause the service flashes doesnt contain motoblue where as my defy had motoblur in it
joydeep1985 said:
oops that might be a problem cause my personal one came with blurred ...and the service flashes found in the link you provided are all without blur ( as you have stated ) so arent there any method left then ? so that i can revert back to original motoblur 2.1 update 1 eclair ? cause the service flashes doesnt contain motoblue where as my defy had motoblur in it
Click to expand...
Click to collapse
Can't you find a Eclair blurred nandroid backup?
The full sfb file of the link of my guide DOES contain blur.
You just need a nandroid backup or the OEM Eclair Blur (so still not deblurred).
But if you find a deblurred modded Eclair nandroid backup it's OK the same! Is even better!!
Than, to future upgrade to Froyo, you can flash one of the many OEM full sbf, almost all blurred. ;-)
okay cool ... so like for now you mean i have to flash with nanodroid + fixed sbf = my current system (its deblurred and wont work)
so from that to make it work i have to find a full sbf (provided on your like flash it and bingo it has all )
and then i can upgrade from msu ... thats d procedure right ??? sorry for being complete noob
joydeep1985 said:
okay cool ... so like for now you mean i have to flash with nanodroid + fixed sbf = my current system (its deblurred and wont work)
so from that to make it work i have to find a full sbf (provided on your like flash it and bingo it has all )
and then i can upgrade from msu ... thats d procedure right ??? sorry for being complete noob
Click to expand...
Click to collapse
I have a litte difficulties undertanding your english ...
In any case, the fixed sfb is just a sort of bootloader, and it never contains app, system app, blur, and anything like that. It's just a bootloader that works for the scope.
The fixed sfb must be made from the same version of the nandroid backup. So for a nandroid backup Eclair, you have to use fixed sbf from Eclair.
Do not mix versions!
lol... sorry my bad ... was excited tht time .. so dint get to check out my punctuations ... .. sorry for being so bad in my reply and my english ........ got it for the time being .. the official froyo is yet to release in india . so i guess i have time till then ... until that i m jus making it sure that i get my eclair back in working condition before the official froyo update is out in msu ..... would try out this on weekend ... though pretty new in making sbf and nanodroid stuffs ....
many thanks for the help
Hey
I'm still on my 2.1. Got my nandroid backup, and now, how do I "create" a SBF file of my Eclair? Cuz it's a little bit hard to find it online. Hope there is a tool in wich I can do that.
"- the zipped copy of the pulled system dir of the versions of Android you've using (by the command example like this: adb pull system "D:\Temp\Defy\pull system Froyo Defy")"
May that be the answer?
Thank you so much.
Fixed sbf
victorvasconcelos said:
how do I "create" a SBF file of my Eclair?
Click to expand...
Click to collapse
I've clearly explained in the guide!!
This are the lines :
Before proceding you need to create or to obtain such called fixed sbf made from the same version you're going to downgrade, so from Eclair 2.51.1.
You can find such fixed sbf online but for safety I prefer to made it by myself. It's so easy.
1. open the original full sbf with Moto Android Firmware Depacker V.1.2 a3 and split to folder;
2. remove CG31.smg and CG39.smg
3. open the extracted folder (the same you've just removed the files) and compile files.
The resulting file is the fixed sbf file you'll need soon ;-)
But can I create a full SBF of my own Eclair? Because I can't find a full SBF of my carrier online
Sorry if I'm getting it wrong, hehe
Thaks for helping!
I don't know ...
About If you can create an sbf from just a nandroid backup ... I do not know, but I do not think so.
Otherwise whould be possible to restore anything without the need of any sbf, and I I've never find a guide telling so ...
In any case, give an accurate reserch over the internet for your country sbf. If it exists in your phone, should exists in "the cloud" somewhere ...
Hey guys my buddy asked me to root rom and install a kernel on his one v from virgin mobile. being as i have done this before to multiple phones i was happy to help. i unlocked the bootloader, rooted it. everything was smooth up til there. i did not put a rom on it yet because he urged me to install a kernel so he could overclock his one v. i was aprehensive but i did it anyway. now his phone wont work. im not surprised but i need to fix it. ive tried installing roms to make it work because the backup ive created in twrp wont boot. so im thinking its a kernel problem. no matter what rom i use it will either not boot it will freeze at the screen that says htc and with the red wording below it. or it will boot into the rom and then freeze or run for about 30 sec then restart and it will repeat this until it dies. ive looked everywhere for ways to get it back to stock ive flashe countless roms none work ive flashed many kernels and none work as well. please help. i would like to get it working on a rom with a working kernel but i will put it back to stock if i have to. any help is greatly appreciated. thank you for your time.
You could flash a ruu ....but the problem is you don't have your software number ...or you have to go to another Rom ...which will make the phone boot normally .but don't forget to flash its specific kernel ...if you don't so that the Rom won't boot
What he said. I recommend using the RUU to restore back to stock.
Re-reroot/unlock it, then read more on which kernel to use. You most likely are using the wrong kernel.
What rom are you using currently - ?
What Kernel did you flash - ?
What error do you get with TWRP - ?
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Nazz45 said:
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
Click to expand...
Click to collapse
Nazz45 said:
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Click to expand...
Click to collapse
Ok. That's good. You use the same ICS kernel with the same ICS roms. No need to keep reflashing. I wouldn't flash a JB rom using a ICS kernel though.
Use this zip - http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
1. Extract the Boot.img from that zip and Fastboot flash boot boot.img in Bootloader
2. Wipe everything. Factory Reset, Dalvik, and System.
3. Flash an ICS based rom, Sense, or CM9.
4. Flash this after rom to get wifi working the zip above or below to fix Wifi.
http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
Just ran the RUU and it did work everything is back to stock. the sprint RUU worked. i ran into a snag installing the Android SDK it wouldnt recognize that i had my Java JDK. even after messing with my registry it still wouldnt work so i just downloaded the x86 jdk and it worked. its unfortunate cuz now i have a jdk in x64 and x86 and its taking up space on my ssd. oh well i hope it doesnt mess with eclipse. i am now going to unlock the bootloader again and re root it and install probably cm9. thank you for all your help i will post again after i attempt to re unlock reroot and rom. thanks again
hello every body
is there a .ftf file with root and cwm in it ?
i need it because every time i try a rom and have a no boot i need to flash a stock rom and root it and install cwm w then i can try again with another rom so is there a prerooted ftf file with cwm preinstalled ?? or is there a shorter way ??
sorry about my bad english (it is not my first language)
AW: ftf with root and cwm
ash-ta said:
hello every body
is there a .ftf file with root and cwm in it ?
i need it because every time i try a rom and have a no boot i need to flash a stock rom and root it and install cwm w then i can try again with another rom so is there a prerooted ftf file with cwm preinstalled ?? or is there a shorter way ??
sorry about my bad english (it is not my first language)
Click to expand...
Click to collapse
that was also my first question on xda, good old times...
No, it's not possible, ftf. files can only be made by Sony, so you've got to do always the same prodecure for flashing, rooting,....
Sent from my LT18i using xda app-developers app
Master of Bisaster said:
that was also my first question on xda, good old times...
No, it's not possible, ftf. files can only be made by Sony, so you've got to do always the same prodecure for flashing, rooting,....
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
thank you so much for your answer
so i think i will keep doing that long thing again and again
That's a really tedious procedure you're following. When I try a custom ROM and don't like it, all I do is:
1) If switching between an ICS ROM and a JB ROM and vice versa, reflash the kernel, then reflash the ROM.
2) If moving from one ICS ROM to another, or one JB ROM to another, just reflash the ROM.
3) If moving from ICS/JB to GB or vice versa, flash the stock ROM, flash the kernel, and then flash the custom ROM.
You don't need to keep on flashing the stock ROM, rooting it, installing CWM, then installing the custom ROM. Kernels, as far as I know, usually come with recovery installed. If you're in a bootloop, just follow the pertinent steps from the list outlined above.
MarcSinger said:
That's a really tedious procedure you're following. When I try a custom ROM and don't like it, all I do is:
1) If switching between an ICS ROM and a JB ROM and vice versa, reflash the kernel, then reflash the ROM.
2) If moving from one ICS ROM to another, or one JB ROM to another, just reflash the ROM.
3) If moving from ICS/JB to GB or vice versa, flash the stock ROM, flash the kernel, and then flash the custom ROM.
You don't need to keep on flashing the stock ROM, rooting it, installing CWM, then installing the custom ROM. Kernels, as far as I know, usually come with recovery installed. If you're in a bootloop, just follow the pertinent steps from the list outlined above.
Click to expand...
Click to collapse
that is rghit but the problem is i need the cwm for flashing the new rom and i have no boot (just sony logo) i cant enter the cwm so i find that i need to reinstall the cwm and try again
if i say any thing wrong please correct it to me maybe you teach me some thing that is new to me
ash-ta said:
maybe you teach me some thing that is new to me
Click to expand...
Click to collapse
Go read the stickys, get some basic knowledge and learn something for yourself, then ask questions about what you don't fully understand, on an existing thread that you found while Googling.
bootloader locked or unlocked because it sounds like you have a locked bootloader, if it is unlocked then why dont you flash a kernel eg. kernel rush with CWM already on it ?
ash-ta said:
that is rghit but the problem is i need the cwm for flashing the new rom and i have no boot (just sony logo) i cant enter the cwm so i find that i need to reinstall the cwm and try again
if i say any thing wrong please correct it to me maybe you teach me some thing that is new to me
Click to expand...
Click to collapse
You don't need to install CWM again, even if you're in a boot loop. Once the phone reboots, keep pressing the "down" volume rocker, as you always do, and you'll enter into recovery. If you're moving to a different Android version (for example, ICS to JB), switch off your phone and flash the appropriate kernel. Then all you need to do is reflash your previous ROM or flash any other ROM that you want. However, that's only possible if you've download your previous and/or other ROMs onto your SD card, too. Do you do that before you flash?
I don't have any experience with locked bootloaders, but the user above IS of the opinion that you might be on one. If that's the reason you're having to go through so many steps to flash a ROM, why don't you try unlocking the bootloader of your phone? I'm more than certain your phone's not covered under warranty anymore, and unlocking the bootloader is definitely not going to fry your phone or anything of the sort.
Hi guys I have a relocked HTC desire 816 and I want to return back to a locked phone to receive updates any help please !!��
Gabriel g said:
Hi guys I have a relocked HTC desire 816 and I want to return back to a locked phone to receive updates any help please !!��
Click to expand...
Click to collapse
Do you mean you have an unlocked boatloader and you want to relock it? You need to use ADB/fastboot on a P.C. with your phone in hboot/fastboot mode and enter"fastboot oem lock" into your command prompt window in the ADB folder then your boatloader will relock. You would also need to be on your stock recovery as well with your system unrooted and stock with no alterations to your system files to then do stock updates. Hope this helps.
thoctor said:
Do you mean you have an unlocked boatloader and you want to relock it? You need to use ADB/fastboot on a P.C. with your phone in hboot/fastboot mode and enter"fastboot oem lock" into your command prompt window in the ADB folder then your boatloader will relock. You would also need to be on your stock recovery as well with your system unrooted and stock with no alterations to your system files to then do stock updates. Hope this helps.
Click to expand...
Click to collapse
No, I relocked it and I want to lock it
Gabriel g said:
No, I relocked it and I want to lock it
Click to expand...
Click to collapse
If it's your boatloader you are referring to "locking" and you originally "unlocked" it you just need to use ADB/fastboot and the command prompt I gave you with your phone in hboot/fastboot mode and USB debugging enabled in your developer settings on your phone to "relock" your boatloader. As long as you're on stock recovery and haven't modified any system files you will be able to do stock updates after that. Hopefully that's what your wanting to do and I'm not just misunderstanding what your wanting and if I am I apologize.
thoctor said:
If it's your boatloader you are referring to "locking" and you originally "unlocked" it you just need to use ADB/fastboot and the command prompt I gave you with your phone in hboot/fastboot mode and USB debugging enabled in your developer settings on your phone to "relock" your boatloader. As long as you're on stock recovery and haven't modified any system files you will be able to do stock updates after that. Hopefully that's what your wanting to do and I'm not just misunderstanding what your wanting and if I am I apologize.
Click to expand...
Click to collapse
Thanks a lot but I have another question, when I relock it will I get updates ?
Gabriel g said:
Thanks a lot but I have another question, when I relock it will I get updates ?
Click to expand...
Click to collapse
Yes. As long as your not rooted and have no system modifications and are on stock recovery you will be able to do stock updates
thoctor said:
Yes. As long as your not rooted and have no system modifications and are on stock recovery you will be able to do stock updates
Click to expand...
Click to collapse
Modified how ? I flashed cyanogenmod and installed Dolby audio and beats audio is this consider modifications?
Gabriel g said:
Modified how ? I flashed cyanogenmod and installed Dolby audio and beats audio is this consider modifications?
Click to expand...
Click to collapse
Yes I believe those 2 mods change your system files to allow their codecs to work so they are modifications. Root, Xposed frameworks,WP.mod_ko to enable system write permissions etc... all can be modifications that need to be "undone" before updating a signed stock OTA or signed RUU( Rom update utility). Unsigned stock firmware in the form of compiled zips or TRWP/CWM nandroid backups supposedly need less to be stock but I have never restored from anything but "signed" stock RUU's so YMMV. I personally don't want to flash someone's personal nandroid backup to my phone because I don't know what if anything isn't "stock" on it.
That's a personal philosophy and I know they upload them for a reason to help those who can't find a signed update or use one but as long as I can I will because when you flash someone else's personal backup you flash the good and the bad, if any. Hopefully you backed up your stock rom before flashing Cyanogen mod , as I have it in my phone as well, and then you can just restore it when you want, reflash your stock recovery, lock your boatloader, unroot and then do any stock OTA's. I also believe you can flash your stock recovery , unroot in Cyanogen mod, remove mods and flash a stock RUU over your current ROM but I've also never personally done that . I just restore my stock backup , reflash my stock recovery, unroot, lock my boatloader and do stock update that way.
Best advice I ever got here was to backup and keep my stock ROM in a nandroid backup to micro SD card before any flashing of new custom roms, find your stock zip or RUU exe and save it to your computer just in case and the same for your stock recovery because you never know when you might need it and I have. Multiple times and it's all in a folder on my computer. If it's a U.S. variant the RUU's are on HTC's website. If not most are found online. Just don't flash the wrong firmware or it could brick your device.
thoctor said:
Yes I believe those 2 mods change your system files to allow their codecs to work so they are modifications. Root, Xposed frameworks,WP.mod_ko to enable system write permissions etc... all can be modifications that need to be "undone" before updating a signed stock OTA or signed RUU( Rom update utility). Unsigned stock firmware in the form of compiled zips or TRWP/CWM nandroid backups supposedly need less to be stock but I have never restored from anything but "signed" stock RUU's so YMMV. I personally don't want to flash someone's personal nandroid backup to my phone because I don't know what if anything isn't "stock" on it.
That's a personal philosophy and I know they upload them for a reason to help those who can't find a signed update or use one but as long as I can I will because when you flash someone else's personal backup you flash the good and the bad, if any. Hopefully you backed up your stock rom before flashing Cyanogen mod , as I have it in my phone as well, and then you can just restore it when you want, reflash your stock recovery, lock your boatloader, unroot and then do any stock OTA's. I also believe you can flash your stock recovery , unroot in Cyanogen mod, remove mods and flash a stock RUU over your current ROM but I've also never personally done that . I just restore my stock backup , reflash my stock recovery, unroot, lock my boatloader and do stock update that way.
Best advice I ever got here was to backup and keep my stock ROM in a nandroid backup to micro SD card before any flashing of new custom roms, find your stock zip or RUU exe and save it to your computer just in case and the same for your stock recovery because you never know when you might need it and I have. Multiple times and it's all in a folder on my computer. If it's a U.S. variant the RUU's are on HTC's website. If not most are found online. Just don't flash the wrong firmware or it could brick your device.
Click to expand...
Click to collapse
Thank you very much , one last question , I backed up my "stock Rom" before I do anything , I backed up even the stock system files , then flashed cyanogenmod after that I restored my backup which it's system files are "stock" and relocked the boot loader ,will I receive updates ?
Gabriel g said:
Thank you very much , one last question , I backed up my "stock Rom" before I do anything , I backed up even the stock system files , then flashed cyanogenmod after that I restored my backup which it's system files are "stock" and relocked the boot loader ,will I receive updates ?
Click to expand...
Click to collapse
Yes , as long as you don't "dirty flash" over Cyanogen mod with your stock backup. Always do a factory reset before flashing between different roms then wipe cache and dalvik cache in recovery before reboot into system. You also need your stock recovery flashed back as well before locking your boatloader. Otherwise I use TWRP.
thoctor said:
Yes , as long as you don't "dirty flash" over Cyanogen mod with your stock backup. Always do a factory reset before flashing between different roms then wipe cache and dalvik cache in recovery before reboot into system. You also need your stock recovery flashed back as well before locking your boatloader. Otherwise I use TWRP.
Click to expand...
Click to collapse
Thank you very much man :good:?
Gabriel g said:
Thank you very much man :good:
Click to expand...
Click to collapse
Your welcome and good luck.