Related
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 ...
Disclaimer:
These images are mainly provided for Developers to experiment with, if you flash them you do his on your own accord and abide to the following rules:
!!!IF YOU DO FLASH THEM AGAINST MY ADVICE - DO NOT FLASH THEM WITH FASTBOOT!!!
Use the Nandroid.md5 from here, copy them and the md5 file to you sdcard and use Nandroid recovery to flash them.
- You have to wipe before using these images
- Make Backups before using this images. I am not responsible if they brick your device, kill your cat or start World War 3!
- AGAIN: You should not flash this images directly yet, as this is untested and you will loose root.
Update 4: If you have MD5 mismatches, follow the instructions here and download his MD5 file. After that you should not get any more MD5 mismatches. Also if you got a missing SD-Card after pushing the build.prop.frankenrom then change
Code:
ro.build.characteristics=tablet,nosdcard
to
Code:
ro.build.characteristics=tablet
That should fix it
Update 3: Seems like you do not need (some users even point out that you shouldn't as it caused them FCs) to copy the ressources as described in the last update, if you use the AU-Images. You can add you APN manually and it seems to work just fine. You should copy the build.prop, if you want to use regional features of your device, as I think that market and other apps pull information out of it.
Update 2: Thanks to Simba90 there is now a complete set of working instructions to get the AU images on your XOOM with Nandroid. Read here
Update: So I erased my XOOM again to bring you instructions
Make a new directory on your sdacrd for a new Recovery
Code:
/clockworkmod/backup/2011-07-09.22.22.22
Copy the images and the MD5 file into this directory.
Start into CWM go to Backup and Restore -> Advanced Restore and restore the partitions from the created directory. Then boot into fastboot and apply the rooted boot.img from here
Now you have a rooted AU XOOM. I have it working with O2 Germany here, but only after applying my instructions from here because the AU images are missing the right settings and telephony Databases as well as our beloved frankenrom build.prop. After doing that all I copied the Books app from the Tiamat 1.1 Rom to /system/app and it works out of the box, so there is no need for using the US 3.1 anymore. I will update my thread accordingly.
/Update
Hi,
I took the plunge and relocked my XOOM after applying the Australian System images from the Motorola Dev Site to it, then I updated to 3.1 with System Update, unlocked, applied the CWM Recovery and made a Nandroid Backup. So here go the pristine System images (boot.img system.img and data.img).
Download here
I would not recommend doing my procedure for anyone not keen on updating his/her Bootloader, because it is updated if you do an OTA Update. Instead try the provided images but remember to make a Nandroid Backup beforehand. I have tried the images on my Euro XOOM and they worked flawlessly. I hope they help further Development. I for my part will try to integrate them into my EU/US-Frankenrom.
So have fun now, let the hacking begin.
So does the Australian Xoom use the same GSM 3G that the euro versions do?
Thanks.
Seems it does, my 3G Connection was working with no Problems, but I can not say definitely that everything works, because I used it just for a few hours now, as I wanted to share it as soon as possible that users can start to hack around with it.
lowtraxx said:
I would not recommend doing my procedure for anyone not keen on updating his/her Bootloader, because it is updated if you do an OTA Update.
Click to expand...
Click to collapse
If it updates the bootloader, is it possible to go back to stock and re-root?
Yes it is possible to go back to stock and ReRoot, because you still can OEM Unlock and use Nandroid to recover and get your Root back. But I do not kow if the EURO and AU Bootloader differ.
lowtraxx said:
Yes it is possible to go back to stock and ReRoot, because you still can OEM Unlock and use Nandroid to recover and get your Root back. But I do not kow if the EURO and AU Bootloader differ.
Click to expand...
Click to collapse
Don't know if this relates but Telstra uses the 850mhz 3G frequency, same as the US whereas the other Aussie telcos use the same as Europe does (900mhz).
Lowtraxx
Been using your original post since day one for 3.1 on my euro xoom. Does this now mean you will be able to sort out the dropping 3g and incorrect signal bars now.
Cheers
Lowtraxx
Just thinking actually would you be able to modify this new aus 3.1 to be CWM flashable.
Thanks
Is this the official AU 3.1 Update? When did they get it?
Yes this is the actual Update, they started rolling it out yesterday.
It is already CWM flashable, you have to create a new nandroid-backup folder on your SdCard copy the images and the md5 into it, then you have to wipe and with advanced recovery you can flash every one of the partitions back.
Then i hope that it will come for the EU Retail Version soon!
Lowtraxx
When i try and restor Im getting an MD5 mismatch error
THIS THING WORKS!
thank you mr lowtraxx
backed up, flashed the stock, OTA update
Updated the thread with the latest findings
Hi there,
After i push the FrankenRom build.prop to my Xoom, i lose SD Card?
Is there a work around, or am i being numb?
Thanks
Marshall1975 said:
Lowtraxx
When i try and restor Im getting an MD5 mismatch error
Click to expand...
Click to collapse
same here...
davidebeatrice said:
same here...
Click to expand...
Click to collapse
Hi,
follow the instructions here or download the md5 file there. If you do that, you should not get any MD5 Mismatches.
dexta211 said:
After i push the FrankenRom build.prop to my Xoom, i lose SD Card
Click to expand...
Click to collapse
same here ...
malta72 said:
same here ...
Click to expand...
Click to collapse
in the build.prop change
Code:
ro.build.characteristics=tablet,nosdcard
to
Code:
ro.build.characteristics=tablet
That should fix it
lowtraxx said:
in the build.prop change
Code:
ro.build.characteristics=tablet,nosdcard
to
Code:
ro.build.characteristics=tablet
That should fix it
Click to expand...
Click to collapse
Thanks, but this change doesn't fix the access to the sdcard.
I can't see the sdcard in Settings|storage, and ES Datei Manager too.
I just bought my Gio in the Netherlands. I've rooted it and installed cwm 5.0.2.7 rfs+ext4. I made a backup with cwm so I have a backup of the stock ROM.
3 hours after I bought it I converted my rfs partition to ext4 to install CM7.2 this went well and installed cwm 5.0.2.7 ext4 only (so i can make backups of ext-sd (EXT4)).
My question is if I wanted to go back to the stock ROM how would I go about this ? I am thinking I should do it like this.
I believe I can't restore the backup I made with cwm initially of my stock ROM since I converted the phone partition to ext4. I would need to flash the stock ROM (download it online) with ODIN.
Root it and install cwm 5.0.2.7 rfs+ext4 and restore the backup I made of my stock ROM with cwm. Or is this step pointless and is the backup I made exactly the same as the stock ROM you download online (meaning there are no specific dutch modifications) ?
Tbh i'm quite happy how my phone is working now, I just want to try this so i'm confident I can go back to way it was.
Regards,
oOze
Latest Kies file
Product Code: GT-S5660DSAXEN
Latest firmware: S5660XXKPS/S5660XENKP1/S5660XXKPA/S5660XXKPS
Modified: 9/14/2011 10:12:10 AM
Download
Flash it with Odin
When i tryed to restore stock rom from CWM backup it failed . So here is the latest file for your phone download it and keep it somewhere safe in case u want to go back to stock
o0ze said:
I just bought my Gio in the Netherlands. I've rooted it and installed cwm 5.0.2.7 rfs+ext4. I made a backup with cwm so I have a backup of the stock ROM.
3 hours after I bought it I converted my rfs partition to ext4 to install CM7.2 this went well and installed cwm 5.0.2.7 ext4 only (so i can make backups of ext-sd).
My question is if I wanted to go back to the stock ROM how would I go about this ? I am thinking I should do it like this.
I believe I can't restore the backup I made with cwm initially of my stock ROM since I converted the phone partition to ext4. I would need to flash the stock ROM (download it online) with ODIN.
Root it and install cwm 5.0.2.7 rfs+ext4 and restore the backup I made of my stock ROM with cwm. Or is this step pointless and is the backup I made exactly the same as the stock ROM you download online (meaning there are no specific dutch modifications) ?
Tbh i'm quite happy how my phone is working now, I just want to try this so i'm confident I can go back to way it was.
Regards,
oOze
Click to expand...
Click to collapse
You're right. Restoring a stock rom to a phone that hase ext4 filesystem partitions wont work. The Android OS wont start up. I did test it. Ik teste het
Installing a stock rom with Odin will make the internal system rfs again i did read.
I think installing cwm 5.0.2.7 rfs+ext4 even will make the file system rfs again? Not tested it. Would save 5 min. odin.
Happy testing
Ty for the quick replies.
I downloaded the ROM one that was suggested in the replies.
I had S5660XXKPE_S5660XXKPA_S5660XENKP1.rar I guess thats an older version.
And if you restore a stock rom via Odin, can you restore the CWM backup afterwards in order to regain your original settings and stuff ?
Or doesn't it work that way ?
Otherwise you could always do a full backup using Titanium of course...
WalkerOfTheDay said:
And if you restore a stock rom via Odin, can you restore the CWM backup afterwards in order to regain your original settings and stuff ?
Or doesn't it work that way ?
Click to expand...
Click to collapse
I don't know I guess I will find out but if its the Dutch/Netherlands ROM you posted in the link I won't have to I guess.
I guess i'll have to use Titanium backup anyway since the backup I made with cwm is old already (or lose some data I don't have much I really want to keep now).
o0ze said:
I don't know I guess I will find out but if its the Dutch/Netherlands ROM you posted in the link I won't have to I guess.
I guess i'll have to use Titanium backup anyway since the backup I made with cwm is old already (or lose some data I don't have much I really want to keep now).
Click to expand...
Click to collapse
I didn't post that link ( SilviuMik did )
My 2.3.5 version is S5660XXKS2, which I got from the Android Advice tutorial, guess I don't have the newest either
Right my bad well anyway he said in a other thread its the newest dutch ROM
Code:
GT-S5660 S5660XXKS2 ## 2.3.5 2011 September S5660OXXKS2
Btw: My firmware seems newer, it's from September 2011. It's not official Kies though. It's on SamMobile Firmware Page.
WalkerOfTheDay said:
Code:
GT-S5660 S5660XXKS2 ## 2.3.5 2011 September S5660OXXKS2
Btw: My firmware seems newer, it's from September 2011. It's not official Kies though. It's on SamMobile Firmware Page.
Click to expand...
Click to collapse
I have no ideea which one is newer. U can stay on that no problem Mine is "good" in case of warranty issues and u must bring phone back to where u buyed it , because u can`t bring the phone with another firmware on it other then the one u have in your country Netherlands
Yeah, your right about the warranty, but I sim-unlocked my prepaid phone myself, so I guess I'm out of warranty anyway
Or is there an option to relock too ?
WalkerOfTheDay said:
Yeah, your right about the warranty, but I sim-unlocked my prepaid phone myself, so I guess I'm out of warranty anyway
Or is there an option to relock too ?
Click to expand...
Click to collapse
I have no ideea if u can lock it back . Maybe if u did a backup of /dev/stl5 ( EFS ) folder before u started to modify it for the unlock process and restore it, then it would be locked again, but i am not sure about this never did it
An appropriate CSC file followed by a factory reset should relock.
Hi,
has anyone here please, someone original stock ROM on HTC One V in version, which is in the pictures. The phone is from the Czech T-Mobile, so if it was just such a version, that would be great.
The only problem is that it needs a flashable zip, otherwise you can not install ROM :-/
Thank you soo much
Sorry that I base topic here but in the Android Development topic can not establish
Assuming that you made a nandroid backup when you first rooted, just use that, doesn't have to be a zip. Also make sure you get the stock kernal or just use the kiss kernal that works for stock (thats what I do).
Twner said:
Assuming that you made a nandroid backup when you first rooted, just use that, doesn't have to be a zip. Also make sure you get the stock kernal or just use the kiss kernal that works for stock (thats what I do).
Click to expand...
Click to collapse
Thanks, but my backup is broken - I don´t vhy, but doesn´t works:crying:. That´s the reason why i´m looking for stock ROM
have a lokk at HTCdev
tomhrusk said:
Hi,
has anyone here please, someone original stock ROM on HTC One V in version, which is in the pictures. The phone is from the Czech T-Mobile, so if it was just such a version, that would be great.
The only problem is that it needs a flashable zip, otherwise you can not install ROM :-/
Thank you soo much
Sorry that I base topic here but in the Android Development topic can not establish
Click to expand...
Click to collapse
Have a look at this:
http://www.htcdev.com/devcenter/downloads/P50
Fill in your device, carrier and region.
braunie said:
Have a look at this:
http://www.htcdev.com/devcenter/downloads/P50
Fill in your device, carrier and region.
Click to expand...
Click to collapse
THANKS, but
I tried - device -> ONE V;
carrier -> T-Mobile;
region -> CZ and find files.
Search results are 3 files - CRC, QMR, CRC ...
At all but I do not know what to do with those files - what is this extension, how to install ...
CID my phone is T-MOB004 (Europe)
tomhrusk said:
THANKS, but
I tried - device -> ONE V;
carrier -> T-Mobile;
region -> CZ and find files.
Search results are 3 files - CRC, QMR, CRC ...
At all but I do not know what to do with those files - what is this extension, how to install ...
CID my phone is T-MOB004 (Europe)
Click to expand...
Click to collapse
If your backup is bronken (md5 checksum error) try the thing in my signature, and you can backup.
Other version is to contack Football, and ask him for the RUU for your phone, but that will cost you some money, or contack a friend who has this ver. of the phone and unlocked bl.
Again other, pure stock -> myone or suprimo ROM
Ken-Shi_Kun said:
If your backup is bronken (md5 checksum error) try the thing in my signature, and you can backup.
Other version is to contack Football, and ask him for the RUU for your phone, but that will cost you some money, or contack a friend who has this ver. of the phone and unlocked bl.
Again other, pure stock -> myone or suprimo ROM
Click to expand...
Click to collapse
So I wonder, if I download and install the stock kernel, do not get back to stock app??
I got the phone from T-Mobile Czech and after root I uninstalled that crap T-Mobile there. And since I do not have, so I can´t update via OTA (error in picture)
So if I reinstal stock kernel it helps me?
tomhrusk said:
THANKS, but
I tried - device -> ONE V;
carrier -> T-Mobile;
region -> CZ and find files.
Search results are 3 files - CRC, QMR, CRC ...
At all but I do not know what to do with those files - what is this extension, how to install ...
CID my phone is T-MOB004 (Europe)
Click to expand...
Click to collapse
I downloaded the "CRC 3.0.16 v4.0 97.5 MB". I thought this would be a flash able rom, but now I don't think so. Maybe it's some kind of stuff to cook a rom.
So I'm sorry, that I can't help you.
2.22.113.1
tomhrusk said:
So I wonder, if I download and install the stock kernel, do not get back to stock app??
I got the phone from T-Mobile Czech and after root I uninstalled that crap T-Mobile there. And since I do not have, so I can´t update via OTA (error in picture)
So if I reinstal stock kernel it helps me?
Click to expand...
Click to collapse
The kernel is not a problem, you have stock recovery too if I see it right, the main problem is, that some (or most) of the "stock" programs are missing, so they cannot be updated. This is a common problem tough, I think a perm deroot helps it, but I'm not sure about that. But the stock programs are needed, the kernel hasn't got the simplest thing in this problem. The kernel itself can be signed or custom, the OTA overwrites it, and it does not contains any programs.
Thanks for all for your requests...:good:
It looks like I will not be able to update via OTA...:crying:
dear, tomhrusk
Hello frnd plz go into your phone bootloader give the details. and if your phone bootloader is unlocked then first relocked it.:good:
then i will give u the stock rom link
So i've got a rooted S4 Mini running on stock firmware (4.2.2) and i want to upgrade to 4.4.2.
I've got a few questions about the procedure... What can i do to keep my contacts and text messages? I don't mind the apps much because i can install them again but if there's any way to keep those i'd find it helpful.
Also do i need to make a full backup before? And if so how should i do it?
My phone has the stock firmware from the carrier i bought it from (MEO - Portugal) and the only Portuguese 4.4.2 firmware i found on the samsung website is from Vodafone... Is that a problem? Is there a way to remove everything Vodafone related from the phone after i install it? Will my MEO sim card still work?
Final question, as the phone is rooted, will i need to root it again after?
I know it's a lot of questions but if someone could please help me i'd be very appreciated! Thanks
rkmgz said:
So i've got a rooted S4 Mini running on stock firmware (4.2.2) and i want to upgrade to 4.4.2.
I've got a few questions about the procedure... What can i do to keep my contacts and text messages? I don't mind the apps much because i can install them again but if there's any way to keep those i'd find it helpful.
Also do i need to make a full backup before? And if so how should i do it?
My phone has the stock firmware from the carrier i bought it from (MEO - Portugal) and the only Portuguese 4.4.2 firmware i found on the samsung website is from Vodafone... Is that a problem? Is there a way to remove everything Vodafone related from the phone after i install it? Will my MEO sim card still work?
Final question, as the phone is rooted, will i need to root it again after?
I know it's a lot of questions but if someone could please help me i'd be very appreciated! Thanks
Click to expand...
Click to collapse
To backup your appdata, text messages, contacts, mobile data statistics,.. use Titanium Backup. Dont you sync your contacts with Google? But since your are simply upgrading an official firmware a backup shouldnt be necessary. ´But to be safe make a backup
A Full backup is done by flashing a custom recovery. Look for the thread here in the forum, where this procedure is explained.
If the new firmware will work with your simcard, I dont know since I'm from Europe where the firmwares are universal. For this case you have a full backup to restore if wont work.
To remove bloatware, again, use Titanium Backup.
And yes you have to root again.
XxM4tzexX said:
To backup your appdata, text messages, contacts, mobile data statistics,.. use Titanium Backup. Dont you sync your contacts with Google? But since your are simply upgrading an official firmware a backup shouldnt be necessary. ´But to be safe make a backup
A Full backup is done by flashing a custom recovery. Look for the thread here in the forum, where this procedure is explained.
If the new firmware will work with your simcard, I dont know since I'm from Europe where the firmwares are universal. For this case you have a full backup to restore if wont work.
To remove bloatware, again, use Titanium Backup.
And yes you have to root again.
Click to expand...
Click to collapse
Since I am in the same boat is there anywhere a procedure on how to do upgrade. Mine is also rooted and has 4.2.2. Not sure about CW or anything else. Guess I can do upgrade by loading firmware on flash card then power the device off and press volume down + home + power for a while? Once in download mode just point to file and let it go?
XxM4tzexX said:
To backup your appdata, text messages, contacts, mobile data statistics,.. use Titanium Backup. Dont you sync your contacts with Google? But since your are simply upgrading an official firmware a backup shouldnt be necessary. ´But to be safe make a backup
A Full backup is done by flashing a custom recovery. Look for the thread here in the forum, where this procedure is explained.
If the new firmware will work with your simcard, I dont know since I'm from Europe where the firmwares are universal. For this case you have a full backup to restore if wont work.
To remove bloatware, again, use Titanium Backup.
And yes you have to root again.
Click to expand...
Click to collapse
Thanks for the reply!
I'm about to upgrade the phone from the official 4.2.2 to the 4.4.2... Just one last thing, should it be done through Odin or just put it in the memory card and run it from the recovery mode? I've got the clockwork mod recovery thingy if that helps
rkmgz said:
Thanks for the reply!
I'm about to upgrade the phone from the official 4.2.2 to the 4.4.2... Just one last thing, should it be done through Odin or just put it in the memory card and run it from the recovery mode? I've got the clockwork mod recovery thingy if that helps
Click to expand...
Click to collapse
Is your firmware in ZIP formar?
saopacic said:
Since I am in the same boat is there anywhere a procedure on how to do upgrade. Mine is also rooted and has 4.2.2. Not sure about CW or anything else. Guess I can do upgrade by loading firmware on flash card then power the device off and press volume down + home + power for a while? Once in download mode just point to file and let it go?
Click to expand...
Click to collapse
rkmgz said:
Thanks for the reply!
I'm about to upgrade the phone from the official 4.2.2 to the 4.4.2... Just one last thing, should it be done through Odin or just put it in the memory card and run it from the recovery mode? I've got the clockwork mod recovery thingy if that helps
Click to expand...
Click to collapse
The official firmwares from samsung-updates or sammobile are in .tar-format. You have to flash them through Odin.
Use this guide
http://forum.xda-developers.com/showthread.php?t=2521928
saopacic said:
Is your firmware in ZIP formar?
Click to expand...
Click to collapse
Yes it is in a ZIP format.
XxM4tzexX said:
The official firmwares from samsung-updates or sammobile are in .tar-format. You have to flash them through Odin.
Use this guide
http://forum.xda-developers.com/showthread.php?t=2521928
Click to expand...
Click to collapse
The update i downloaded has an MD5 file and a dll inside.. (?)
rkmgz said:
The update i downloaded has an MD5 file and a dll inside.. (?)
Click to expand...
Click to collapse
md5 should be ok with Odin. I was going to try one of the custom firmwares wich is in zip format. do I install it via pow-vol down?
rkmgz said:
The update i downloaded has an MD5 file and a dll inside.. (?)
Click to expand...
Click to collapse
Unpack the zip and delete the .dll file. You only need the .tar.md5 (I suppose it had this ending).
saopacic said:
md5 should be ok with Odin. I was going to try one of the custom firmwares wich is in zip format. do I install it via pow-vol down?
Click to expand...
Click to collapse
The custom roms are installed in a custom recovery (CWM, Philz Touch, TWRP ; access over power+vol up).
XxM4tzexX said:
Unpack the zip and delete the .dll file. You only need the .tar.md5 (I suppose it had this ending).
The custom roms are installed in a custom recovery (CWM, Philz Touch, TWRP ; access over power+vol up).
Click to expand...
Click to collapse
Thanks.
I have intalled it now together with new kernel. Also installed GAPP so I can sync my data from Google. Seems to work so far.