[Q] Original ED1 build.prop - Verizon Droid Charge

Would someone mind posting the original Droid Charge ED1 build.prop file? I attempted to modify mine to work with Netflix, but all I did was break my market. Aaaand of course I didn't keep a backup.

Here's mine:
filesonic.com/file/1039316854
I've already changed ED1 to ED2 to prevent the update.

Thanks very much! Worked perfectly.

Thank you so much, this helped me out after i changed the screen density with jrummy root tools. I had to find a build prop and it happened to be one with the software bypass. Kudos on the build prop. very awesome since recovery through nandroid isnt available yet i am just waiting on a rom if not i will try making one myself (thought i dont have time so itd be purely for personal use i guess till the pros get on it lol)

how do u change ed1 to ed2???i tried but it wont save.

brandonaspencer said:
how do u change ed1 to ed2???i tried but it wont save.
Click to expand...
Click to collapse
You need to mount /system as read-write. Also, why don't you just update to ED2, at this point, there is no reason not to.

Related

Super User 2.3 Availble !!!!!

I see talk the the Super User Root has been upgraded to 2.3. It's suppose to be much better than the current one. Will we have to uninstall the current one before applying the new root? Has anyone made an attempt to install SU 2.3 in a Captivate yet?
Qmotion said:
I see talk the the Super User Root has been upgraded to 2.3. It's suppose to be much better than the current one. Will we have to uninstall the current one before applying the new root? Has anyone made an attempt to install SU 2.3 in a Captivate yet?
Click to expand...
Click to collapse
my update.zip is getting it added soon.
edit---
uploading now
edit---
up now
http://forum.xda-developers.com/showthread.php?t=751934
I rooted my phone using the pimp my cap. PDF. If I wanted to unroot. Could I just delete the original update.zip file and replace it with out flashing back to stock? The reason I'm asking is I don't have a pc. (im on mac) and I can't use odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
What will we have to do to replace the old version? Can one be installed on top of the other?
?
Qmotion said:
What will we have to do to replace the old version? Can one be installed on top of the other?
?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=682828
there is an update.zip that will do what you need.
So what your saying is you just install the new update.zip as we did during the first install?. As stated that means we don't have to uninstall or go back to the stock rom. It pays for us noobs to be certain.
Qmotion said:
So what your saying is you just install the new update.zip as we did during the first install?. As stated that means we don't have to uninstall or go back to the stock rom. It pays for us noobs to be certain.
Click to expand...
Click to collapse
yup, flash over
DONT UPDATE TO THIS. I did, and now I get force close after force close, I can't load a backup ROM at all. Going to unroot and root again hoping to get back to the previous version.
designgears said:
yup, flash over
Click to expand...
Click to collapse
Ok so just install over my current root? Or flash to stock then root?
Sent from my SAMSUNG-SGH-I897 using XDA App
Smallsmx3 said:
Ok so just install over my current root? Or flash to stock then root?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
install over your current root
flashman2002 said:
DONT UPDATE TO THIS. I did, and now I get force close after force close, I can't load a backup ROM at all. Going to unroot and root again hoping to get back to the previous version.
Click to expand...
Click to collapse
designgears said:
install over your current root
Click to expand...
Click to collapse
OK, now I'm confused. I almost did it. I'm scared now....
Designgears, you have done this to your phone and it works now. Flashman did you figure out what you did wrong?
The only thing I can figure is I updated through ROM manager. I imagine people that are using the update.zip should have no issues from what I read in the Superuser thread. I am not going to try again for a couple days to be sure, but people are able to make it work without issue. I figured with it showing up in ROM manager it would have been safe to load that way, as I upgraded to 2.2.2 when I first got ROM Manager.
Qmotion said:
OK, now I'm confused. I almost did it. I'm scared now....
Designgears, you have done this to your phone and it works now. Flashman did you figure out what you did wrong?
Click to expand...
Click to collapse
Just did mine, works fine.
Is this just the updated Su 2.3.1 ??
I see that you also have the http://www.multiupload.com/BCLH94FNVD file on the other thread that seems to include the new root file. Or does this update.zip file include everything?
Excuse me for being extra carefull. Better safe than sorry.
I actually want to install the file that includes the sideloading. I haven't made that mod to my phone yet.
Does the BCLH94FNVD file include everything all in one shot?
designgears said:
my update.zip is getting it added soon.
edit---
uploading now
edit---
up now
http://forum.xda-developers.com/showthread.php?t=751934
Click to expand...
Click to collapse
If I may.. Was there a changelog? I mean.. 2.2 grants needed privilege. Not trying to be sarcastic at all but I see so many people worried about this or that it left me wondering what was new.
I tried it and it said the update was aborted. Didn't give a reason. I took out the original update file and replaced it with the new one. Should I have left both files in?
Maybe I'm not asking the question right. The link to the update file you added to this thread. Is it for the EliteSuperRooter or is it just for the 2.3.1 root OR would we still have to add the file on the other thread that seems to include the new root file. Or does this update.zip file include everything?
mostyle said:
If I may.. Was there a changelog? I mean.. 2.2 grants needed privilege. Not trying to be sarcastic at all but I see so many people worried about this or that it left me wondering what was new.
Click to expand...
Click to collapse
In the General Android Dev forum there is a changelog and he changed a ton of stuff.
edit - It was in Apps and Games my bad.
http://forum.xda-developers.com/showthread.php?t=682828
for lazy ppl this is what different between 2.2 and 2.3.1
(New for 2.3)
- New layout of main app
- Full logging
- New request layout
- Fixed boot/widget bug
- Date/time format options
- Better notification system
- New icon
- Better allow system
- A whole mess of code cleanup
- Rearranged drawables so that only one apk needs to be built for any firmware
(New for 2.3.1)
- Big bugfixes
- Better support for landscape mode
- better support for ldpi devices
The question is, what does this offer that my current superuser doesn't?

[Q] Got OTA 2.3.2 update, still rooted!!!!

don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
By "still rooted" do you mean you still have the superuser.apk or can you actually still boot into CWM? Because an OTA will not delete those apps but it WILL break root.
oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
The update doesn't wipe the phone at all, it only patches certain files in the /system partition, so it doesn't actually delete the su binary in /system/bin or the superuser.apk in /data/apps.
The update script does, however, do a recursive chmod of the permission on /system/bin, and that broke root on my phone. Even though the files were still there, and some apps thought that I was still rooted, many root things (like Titanium and Root Explorer's ability to mount /system as R/W) wouldn't work.
I've seen some reports that root stuck, but I'd advise flashing the su update again...it's quick and easy to do with CWM, and it will fix the permissions to make sure none of your apps have any issues.
Are you sure the update actually occurred? Your android version and build number have changed?
so, now i have
Android version - 2.3.2
Kernel - 2.6.35.7-g7f1638a
Build number - GRH78C
if start titanium backup - can see that superuser permission granted
Market access working perfectly - i hav an acces for paid apps
Can grab screen with ShootMe
dont remember how did i root - seems i just run some script on ubuntu notebook
Thanks for everybody for replies
yes, going into CWR can easily update the permissions recursively
not sure but probably i am on superboot loader (not SWR)
being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.
RogerPodacter said:
being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.
Click to expand...
Click to collapse
He's saying that he thought the OTA would unroot him, not that being rooted would keep him from OTAing.
Funny how the update seems to impact the root of people differently. It definitely broke mine, even though it didn't erase the files.
Oh oops my bad I mis read!
The update didn't break my root
sagech said:
The update didn't break my root
Click to expand...
Click to collapse
it seems new uppdate does not unroot phones with superboot rooting
No Update
Hello,
I tried to update my phone but I am now looking since 10 minutes at the little Android and nothing happens.
There was a short message where the Clockworkrecovery said something like it could not verfy the update file.
Should I just put out the battery and try to reboot?
Edit:
The Clockwork recovery came up again and I selected to reboot the phone. Now it's still running on 2.3.1.
What have I done wrong?
Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S
Bronk93 said:
Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S
Click to expand...
Click to collapse
Yes, exactly!
So is the solution maybe to wait till the 2.3.2 version is available at the ROM Manager?

Official T-Mobile US OTA Update 2.2.1 Froyo 34.4.9

Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
how is it? faster than 2.1?
Oh yeah. More bloatware, but that's easy to remove. Internet speed is faster. Phone is more responsive. Nice to have the Hotspot feature now. Overall a worthy upgrade. Now to wait for 2.3
can i use this update for my finland rom 3.42? or this is just for TMo version?
runeblade said:
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
Click to expand...
Click to collapse
Would you happen to have original t-mobile 2.1 in sbf format?
Unfortunately no-one has one for the US. I'm guessing you updated to the leaked version? The good news is that if my suspicion is correct a nandroid backup of this should play fine with the updated firmware. If you look at the difference its minor. 34.4.9 vs 34.4.4. I have not yet had the time to make one yet. I'll try to do so tonight.
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
nanek921 said:
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
Click to expand...
Click to collapse
Its an update zip file signed by company so you should enter stock recovery by power+vol down and then select update from zip.
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
no clue said:
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Click to expand...
Click to collapse
Beach_Head said:
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
Click to expand...
Click to collapse
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
The leaked T-Mobile SBF was fast too.
But yeah, an official one would be better.
If the Nandroid method doesn't work, I hope someone posts an SBF soon...
no clue said:
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
Click to expand...
Click to collapse
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
No worries!
Is there any way to edit the build.prop file so that I can get the update to work?
runeblade said:
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
Click to expand...
Click to collapse
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
I have the string. I'm just wondering if it would work if I do edit it...
Where do I locate logwrapper?
runeblade said:
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
Click to expand...
Click to collapse
I just loaded this update.zip on my fiance's Defy...didn't wipe data or cache, it's booting right now....stuck at the T-Mobile "Stick Together" screen, waiting for the initial long boot
EDIT: Booted, running 2.2.1 now! So far so good, it's a little slow but it would be while it catches up. I have an Atrix and it's almost the identical interface.
can you make a sbf file of entire build?
Nandriod back up please! im dying for it
zencoran said:
Nandriod back up please! im dying for it
Click to expand...
Click to collapse
just flash the update.zip...why bother with a nandroid?

[REQ] Stock Nandroid

I'm getting a critical error in RSDlite... B655 I believe. I've tried 3 different computers with the drivers and rsd setup correctly. I've flashed this same sbf multiple times before without fail. For some reason the phone is kicking this error and I can't get back to stock for warranty purposes. Does anyone have a Nandroid of their stock Cincinnati Bell 2.1 I can use to get back to stock so I can get it replaced under warranty? All I need is the boot and System images I believe. If anyone can help me out I would appreciate it. Thanks.
Check out Mioze7Ae's replies in this thread. You can also look here
3rdstring said:
Check out Mioze7Ae's replies in this thread. You can also look here
Click to expand...
Click to collapse
Thanks man, that should work. I'm after the barebones restore so the first link was perfect.
EricDET said:
Thanks man, that should work. I'm after the barebones restore so the first link was perfect.
Click to expand...
Click to collapse
If you are taking your phone in, don't forget to unroot and delete Superuser.apk

[Q] Need stock build.prop

Does anyone have a stock build.prop for the VZW LTE Galaxy Note 10.1?
I modified mine and didn't make a backup and then found out the OTA update won't work because my build.prop is modified. After looking at the updater script, I think either a build.prop from before the upgrade or after the upgrade will satisfy the requirements.
Alternatively if someone knows if factory reset will restore it, that will be fine too. I don't think it does since I have seen so many stories of people bricking their device by modifying the build.prop and then a factory reset doesn't fix it.
Confirmed factory reset does not restore it.
Here ya go.
Also, rename sdm.apk so ya dont get those ota's
*Madmoose* said:
Here ya go.
Also, rename sdm.apk so ya dont get those ota's
Click to expand...
Click to collapse
Unfortunately that didn't work. I wonder if even the last modified date has to match.
I am actually trying to get the OTA to work. I have OTA Root Keeper, so I am not worried about OTA taking away root.
I'm honestly not sure that I even care if I can't get root back. The only thing I use root for now is modifying DNS to use Fool DNS to block ads, but that interferes with Hulu sometimes. Such a bummer too. It's nice watching the screen blink a couple times and then voila, commercial break is over.
Samsung gave me instructions to flash with OEM firmware, so I am going to try that.
Thanks for posting that up so quick though!

Categories

Resources