Hi,
I have got my TP2 and found that install "Ara Loc install" and done with the installation, the steps went fine till i found arabic on my system
Now i need to remove the arabic completely and get it back like it was i have tried the following:
1. Disabled Arabic support
2. Hard reset ( Clear storage data )
3. Hard reset ( HW style)
and still can find the arabic installed, looks like the update has patched the rom or something, so is there a way i can compelety bring it back to its original rom ? and if i tried to reinstall the original ROM from HTC would it allow me although its the same rom version ?
Regrads,
Related
hi,i bought an unbranded,unlocked and unrooted desire but later rooted it so as to install a custom rom.I messed up the flashing process and would like to go back to the original 2.1 build that came with the phone?I do I go about it please?Still have the 2.1 but the system seems to be messed up.all apps now download onto the phone's memory not SDcard.I messed btw the " partition and wipe / factory reset" steps which resulted in the wiping of the stored system data and apps.
Hi, just download and run RUU on your pc, follow the guide and you'll be fine You get the links here in Development section of Desire.
Also note that you'll lose all your data in your phone.
Hello,
I plan to upgrade my Australian (Telstra) Motorola Defy to an Android 2.2 (Froyo) ROM that is ideally without Motoblur.
I have comprehensively read hundblues of the Defy modding threads through Search, Browsing and Cross-Links on XDA, however there are still a few areas I am still unsure about and feel the need to ask.
I absolutely require downgrade-ability back to the Telstra stock firmware (A variant of 2.21), Because if I become affected by the Speaker issue, then I will need to restore to stock for Warranty.
I am also conscious of using the Chinese 2.2 ROM due to risk of blowing the Camera Flash LED.
Maintaining Downgrade-ability
Higgsy has made a thread how to upgrade to 2.2 (Froyo) without losing downgrade-ability, but I am not clear on a few points, my comments are in blue
Instructions in the thread:
"Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here [http://www.sorensiim.dk/higgsy/.sbf/2.2CN_SBF.zip] Is this the unmodified Chinese 2.2 ROM?
Need the system.img nandroid and boot/devtree.sbf – Download here [http://www.sorensiim.dk/higgsy/TMOB_US_3.42_Files.rar] This must be the "Tmob 3.42 system image(pre rooted)"
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear [http://www.sorensiim.dk/higgsy/GB_3.4.2_system.img.rar]
• Flash the Chinese .sbf by RSD lite OK I understand that the Chinese 2.2 ROM is downgrade-able, makes sense so far
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder) What makes this 3.4.2 ROM different from the others in that it is still downgrade-able?
• Once restoblue pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done. See below about Camera Flash LED issue
If you want to use the GB release then just restore the system.img from the GB release. Similar to the T-Mobile 3.4.2 ROM, what makes this UK 3.4.2 ROM downgrade-able?
"
If there has been a modification done to the T-Mobile / UK 3.4.2 images provided which makes them downgrade-able, what is it?
Can it can be applied to other 3.4.2 ROMs too (eg: Finland 3.4.2 155-002 which is Blurless).
Based on Which SBF code group prevents downgrade, I am guessing that the CDT(CG31) has been removed from the image (to keep CDT on version 2), but I'm also guessing that this would also screw up SYSTEM (CG39) because that would also need to stay on version 2, when 3.4.2 uses (and needs to be?) version 4 (or else it will screw up the signature?).
Preventing the Camera Flash LED from blowing when the Chinese 2.2 ROM has been used
I seem to have found two theories on this one:
1. Higgsy's 'Devtree' theory (see thread above) that the Devtree in the Chinese 2.2 ROM is causing the issue, and a Devtree copied out of a different ROM should be used. (This leads to more questions: What is the Devtree? Where is it located? How is the Devtree copied out of a ROM? I can't find any information about Devtrees)
There is a followup post in this thread in reference to the Devtree theory which says "I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?"
I am not sure if this users's reference to the "flash fix" is referring to the 'Devtree' fix or if it was another "flash fix" that they tried. Nor do I know if the user followed the instructions for this "flash fix" correctly, but it is casting some doubt if the Devtree fix is correct or not?
Also in the instructions above, if the T-Mobile or UK 3.4.2 image is flashed after the Chinese 2.2 ROM was installed, wouldn't the non-Chinese Devtree already have been installed?
2. 'build.prop' theory
The post reads:
"I was going through build.prop for some thing else and noticed these settings on my 3.4.2-145 build.
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
What are these set to for the Chinese ROM?"
There are no followup posts to this to confirm the values of the Chinese ROM, to confirm that this prevents Camera Flash LED burnout, or to confirm that this doesn't work.
Or use the downgradable method I list in my post (http://forum.xda-developers.com/showthread.php?t=977989).
That way you dont have to flash any chinese firmware and worry about camera/flash issues.
Your ROM seems to be just what I am looking for. I want to be as close to the Stock Android Experience as possible (I've tried Motoblur and it's not for me) and without the bloat.
I have a few questions about the process that Barebones uses, because I think that it's important to learn what I'm actually doing.
"2. Restore your Froyo Nandroid of choice.
Barebones: CEE3.4.2_155-002_DEBLUR.Nandroid.zip"
I guessing that this contains ONLY the SYSTEM partition, which has been taken from the unmodified CEE 3.4.2-155-002 Deblur ROM, as the SBF method would change the version making it un-downgradeable?
"Flash the fixed sbf.
Barebones: Fixed.CEE.3.4.2_155-002_DEBLUR.zip"
I guessing that this "fixed" version contains unmodified CEE 3.4.2-155-002 Deblur partitions PDS, LBL, MISC, BOOT, CACHE, USERDATA & KPANIC, but not CDT (To allow downgrade), SYSTEM (To allow downgrade, it has already been installed at Step 2 instead?) and RECOVERY (To retain Clockwork Recovery)?
"5. Reboot into Froyo; install Clockwork Recovery; copy Barbones to sdcard.
Barebones: Barebones_12-signed.zip"This must be the bit where all the modifications of Barebones itself are made? And hasn't Clockwork Recovery already been installed to the RECOVERY partition from Step 1 or does Clockwork have elements that need to be reinstalled? (eg: in the BOOT/SYSTEM/USERDATA partitions)
"Swype, Gtalk, Voice Commands, GreekIME, CarDock, Recovery, and Easy Installer -> Download update.zip"With the Extras package, can these components be installed separately or are they all installed together? Some of these extras may not be applicable like GreekIME (If the user is not Greek).
Is the Swype in the package the same as the latest Beta from beta.swype.com and isn't Clockwork Recovery supposed to be already installed?
Also, is there a way to reinstall some of the 'Removed' APKs like BlurAlarmClock, Calculator, ClockWidget, DLNA, Quickoffice, WeatherWidget (assuming that these APKs will still work on their own) or will I need to copy them before installing Barebones_12-signed.zip
Finally, you have done a great job so far and it is far better than anything else out there for the Defy at the moment, thank you.
My only bit of [constructive] criticism (and I am by no means ungrateful) is that I think that some of the Added & Value Added features of Barebones (especially the Wallpapers and Sounds) would be more suited to the Extras package (as optionals) to keep in line with the goal rather than being bundled in the Barebones package.
Barebones faqs. . .
Why its downgradable ?
This works is because the fixed sbf has partitions taken out; specifically CG31 (CDT) and CG39 (System). Reason being these are the parts of the sbf that prevent you from downgrading. So, this lets you make up the rest of a 'whole' rom using the nandroid; and bingo Froyo with downgrade.
Barebones.zip ?
Unlike some of the other roms posted here, which are nandroids, this one is based on an update-script. Meaning it just changes a stock rom into Barebones; does not restore a complete system. So a factory reset is not enough.
Why install clockwork a few times ?
Nandroid doesnt come with the app, my rom doesnt come with it; yes clockwork is installed just not the apk, so you need that to boot into recovery. Reason why, defy bootloader is locked - so recovery has to be initiated from within the android os, hence bootstrap.
Update.zip ?
If you read the build info it states that it copies all the extras to the sdcard. While Easy Installer is the only program in that update that get installed automatically. Point being you use it to install whatever you feel is missing and delete the rest.
Other apk's not in update.zip ?
Not my problem, I cant please everyone; and I'm not going to make update.zip's with every apk under the sun. The update.zip is already half the size of my rom, so . . . Barebones ? Maybe use adb to pull /system/app after you restore the nandroid and before Barebones. You could then copy them back to the /system/app folder after Barebones is installed. If you try to install the apk's before Barebones they will be erased by my update-script. To be honest I probably didnt include most of these apk's because they must be installed to the /system/app folder (eg: MediaGallery, BlurAlarmClock). They just wont install to /data/app.
But its not Barebones . . . .*tear
OK I get it guys, my 380kb of extra noise's offends, so wait for v1.3 if its too much. This is my first android phone, I got it in December; I learned to cook this rom in that time (so google and read). So lets face it, I make this rom for my phone; just sometimes other people like it too.
Hope this clears up a few things . . . and enjoy the rom.
Hello Folks,
today the Touchscreen of my DHD stopped to work completely. Its fully unrooted,and right at the Moment i use LeedDroid 2.2.2.
My DHD was sold from O2 Germany...
Do i have the chance to unroot it fully without Touchscreen? I am able to boot my DHD into CWM.
Or maybe someone has another Tip what i can do in that Situation?
Many thanx in advance...
try a wipe (factory reset), and if that doesn't help flash the rom again.
If the hardware is dead you can flash back to stock via ADB.
ex here but via ADB:
http://forum.xda-developers.com/showthread.php?t=998044
Go in the ROM thread in the stickies and check the guide to install custom ROM.
Then redo on the other way (it's explained).
Of course if the previous post works (wipe+fresh install) it's much better
Factory-Reset and Installation of a new Rom i already tried with no success.
And i think a Flash-Back of Stock wont be a Problem... The Problem is,that i now cannot change the Super-CID...
Any other Tips?
Hi!
You read the topic, I will tell you what happened.
I rooted my phone (Galaxy W - original DBT sales code with I8150XXLA2_I8150DBTKJ1_I8150XXKL3), it was a little tricky.
Originaly it had the LA2 Stock Firmware on it and I had to flash a lower firmware (I8150XXKL3_OXXKL2_XEU) on it. After this I could root my phone.
OK. I played a little bit around and the biggest mistake (i think) - for me - was to test the [ROM] GingerICE 1.0 (Android 2.3.6, Custom .35 Kernell).
After I did my phones language was malaysian I think. I could turn it to English but I didn't like the FW and I only wanted to test it.
The next thing I did was to flash a stock Firmware (again the I8150XXKL3_OXXKL2_XEU), a strange thing was that in the telefon infos the phone was not mentioned as root, but it wasn't really unrooted.
When I connect to KIES it says my phone is incompatible and can't be updated.
If I try to select the sales code via the *#272*IMEI# combination there is only XEU, the original DBT (for germany) is gone. There are 10 or more others to choose, but not DBT.
So I really wanted to unroot and put a stock firmware on it to give it a rebirth and get it as it was as I got it. (or 99% percent as I got it)
First I used the DooMLoRD_v1_UNROOTING tool, it went through everything fine (I read everythng in the DOS Box) and suceeded, but the phone was NOT unrooted! There was no superuser, but it is STILL ROOTED.
Then I tried the unroot.zip file.
I first rooted it again, to have the CWM recovery and after that I turned the Samsung into recovery mode and choose the unroot.zip from the recovery menu and - surprise - it is STILL ROOTED!
I can't believe it. People have problems to get their device rooted, I have problems to unroot mine.
The best thing would be a reset to sales code DBT and any stock firmware - don't matter how old.
Are there any ideas what I can do?
I wanted to post it in the development section but I have to write 10 posts first.
If someone could help me you would make me really happy!!
CU
lienot
Lienot said:
Hi!
You read the topic, I will tell you what happened.
I rooted my phone (Galaxy W - original DBT sales code with I8150XXLA2_I8150DBTKJ1_I8150XXKL3), it was a little tricky.
Originaly it had the LA2 Stock Firmware on it and I had to flash a lower firmware (I8150XXKL3_OXXKL2_XEU) on it. After this I could root my phone.
OK. I played a little bit around and the biggest mistake (i think) - for me - was to test the [ROM] GingerICE 1.0 (Android 2.3.6, Custom .35 Kernell).
After I did my phones language was malaysian I think. I could turn it to English but I didn't like the FW and I only wanted to test it.
Click to expand...
Click to collapse
Hi,
my solution would be:
1. Backup everything manually what you can!
2. Flash via ODIN ClockWorkMod Recovery on your device(english). Scroll down to other and select ClockWorkMod.
If you prefer a german instruction. Runterscrollen zu Sonstiges ;-)
3. Once ClockWorkMod is flashed, go to the recovery:
a) backup and restore -> backup to external sdcard
b) backup and restore -> restore from external sdcard
This is to make sure the files aren't corrupted, if this is successful you can be sure everything is backupped. If you get a MD5 mismatch something went wrong. Try again!
c) wipe data/factory reset -> confirm
d) wipe cache partition -> confirm
e) mounts and storage -> format system -> confirm
f) mounts and storage -> format cache -> confirm
g) mounts and storage -> format data -> confirm
4. You restart your phone in Download Mode and flash the german DBT firmware using this instruction, which is provided in the thread under Firmwares.
If you prefer a german instruction.
5. Now you will have to flash again the ClockWorkMod recovery to restore your data.
Than open ClockWorkMod Recovery and:
backup and restore-> advanced restore from external sdcard -> select the backup -> Restore data -> confirm.
Now if you want the stock recovery back(needed for OTA updates) instood of ClockWorkMod, than go to the Others or Sonstiges and select the stock recovery, and flash it on your device.
6. Now you should have a fresh and unrooted device like you have never rooted/flashed!!!
Oh yeah, the reason why you have to make these complicated steps: Because you were flashing all different kinds of firmwares, you system will be a mess. To make sure your device is not a overwritten old firmware these steps are necessary.
Flashing via ODIN does not delete all old data !!!
greets
THE-E
Hi!
I just read your answer. Thanks A LOT for this step by step answer.
I will try this, but I can't do it this evening, but as soon I did it I will post if it was sucessfull.
I am from Germany - you seem to be from germany too?
I think there a lot of smartphone/computer "freaks" from germany in boards all around the globe!
Anyway, my english isn't perfect but good enough to read instructions and follow these.
Again thanks a lot,
CU
lienot
Yes once you have flashed the stock ROM do a factory reset to ur phone n best to format ur SD to be sure
Sent from my GT-I8150 using xda premium
andynroid said:
Yes once you have flashed the stock ROM do a factory reset to ur phone n best to format ur SD to be sure
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
But it is important to make a backup on your physical sd card. ClockWorkMod does not backup the SD card.
But if you ask me, it is not necessary to format the sd card(internal). External sd is anyway not required to format.
And yes I am from Deutschland :-D If you have problems with my explainations, just PM me, I will answer you in german.
greets
THE-E
P.S.: You are welcome. A click on the thanks-button is fair enough ;-)
Hi!
1st - Sorry for the late answer. I am a little lazy in writing.
Everything is fine now! My Samsung W is absolutely unrooted.
When I use the *272... combination it gives me no choice, there is only DBT and this is - at the moment - exactly what I wanted to have.
I had wiped the handy and the cache before and it didn't worked well, but after I did the things you wrote "format/mounts and storage..." it finally worked!
Thanks again, I will 100% percent keep on flashing, but it is a little different with the galaxy W. I had the SGS2 before and there were dozens of ROMS and it was no problem to change anything in the phone, there was a solution for everything.
I'll give the Galaxy W a little time, until then I love my Phone as it is.
I didn't want such a big phone anymore, it is just tooo big, so I stepped down to the W.
Have a nice evening,
CU
lienot
Hi in performance terms the SGS2 is much superior than the galaxy W? Besides the screen size.
Hey guys!
Sorry if this matter has already been approaced, but... i wouldn't know what keywords to search for.
I have a Gio, that came with gingerbread 2.3.4 and was updated to 2.3.6 via samsung update app.
Due to veeeery low internal storage i need a lighter rom so i thought of LightOrange v7. Wasn't keen on it but something had to be changed.
My device wasn't rooted, so i made no backups of any apps or the rom that was already on it, nor did i have any rom managers installed.
I went into cfw (i understand it's called - power button + home key) and from there i selected update from sd card. The new rom installed with the pretty interface, and when it was done it told me to reboot.
At startup, the first startup screen appeeared (the one where "samsung" is the only word) and then went to the second screen (where it says ~samsung galaxy gio S5660) and it got stuck there.
I entered the cfw again, and did a factory reset, clear cache, reinstall and so on, but all i get is the phone getting stuck at that second startup screen.
So... what is there to do?
Will another rom placed on the sd card -> installing from cfw do the trick? or is my path to repairing the device longer?
Hey
I'm not sure if installing a new rom over the old one will help, you can always try I guess
But you can also just start for scratch and just get your phone back to stock rom using this guide: THIS
And if I'm understanding you correctly you didnt install any recovery to backup and install the custom rom? Because I think you're going to need CWM as recovery.
Hope it helped
Solved.
Installed clockworkmod from sd card, using the default "update from sd card'".
And from there installing a rom was as simple as it should be
It would have been usefull if someone had given me this solution as a reply to my thread...