Edited Build prop attached.
Edit: Realized someone else also found it before me... I need to learn to read...
You will also need to change the permission to prevent bootloops
from Adb shell or terminal on your phone
su
remount -o rw,remount /dev/block/mmcblk0p12 /system
chmod 644 /system/build.prop
remount -o ro,remount /dev/block/mmcblk0p12 /system
and... what exactly is this?
graemegb said:
and... what exactly is this?
Click to expand...
Click to collapse
What do you think it is? Cant you read lol
tianqi said:
Change ro.build.version.full=Blur_Version.4.1.83.MB860.ATT.en.US in the build.prop
Edited Build prop attached.
Click to expand...
Click to collapse
I'm looking for solution, and I found this solution somewhere else also... Anyway, did this work for you?
Sent from my MB860 using XDA Premium App
graemegb said:
and... what exactly is this?
Click to expand...
Click to collapse
Heh, it is this guys 'fix' for motoblur not logging in on 2.3.4. I tried it before, and it did not allow me to sign is still but maybe it works for him.
_Dennis_ said:
Heh, it is this guys 'fix' for motoblur not logging in on 2.3.4. I tried it before, and it did not allow me to sign is still but maybe it works for him.
Click to expand...
Click to collapse
You need to make another account tho...
tianqi said:
You need to make another account tho...
Click to expand...
Click to collapse
Any way to use existing account?
Sent from my MB860 using XDA App
I wonder if something like this could be used to fix the fingerprint scanner since there's a line that talks about it.
jiggytom said:
Any way to use existing account?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Might be other work arounds out there but with this one, you need a new account, you can however register using your old email again
How do i get back to the Blur login? I skiped it the first time and it has not asked me to login again.
NYG-SBXLII said:
How do i get back to the Blur login? I skiped it the first time and it has not asked me to login again.
Click to expand...
Click to collapse
Through the Accounts app maybe?
not there in accounts
thx, or click music store
Just click on Social Networking, and it will get you to sign in with Blur again
isnt blur just contacts and media sync? i frgot i wasnt signed in...im not missing anything by not being signed in am i? i dont sync my social media to blur to save battery
Ugh...I put the build.prop file in my /system/ folder and I rebooted. Now my phone's in a bootloop, what'd I do wrong >_>
EDIT: After I do a battery pull and start it up, it goes to the lockscreen, freezes and goes back into a bootloop. ...
Pizza4Breakfast said:
Ugh...I put the build.prop file in my /system/ folder and I rebooted. Now my phone's in a bootloop, what'd I do wrong >_>
Click to expand...
Click to collapse
Wrong permissions?
LayzeeEyez said:
Wrong permissions?
Click to expand...
Click to collapse
Hmm, how would I check this?
Pizza4Breakfast said:
Hmm, how would I check this?
Click to expand...
Click to collapse
Through Root Explorer, but I guess you'll have to reflash since you're in a bootloop.
LayzeeEyez said:
Through Root Explorer, but I guess you'll have to reflash since you're in a bootloop.
Click to expand...
Click to collapse
Arghh >_> so I have to reflash a Full 1.8.3 sbf and then the HK 2.3.4 again?
Pizza4Breakfast said:
Arghh >_> so I have to reflash a Full 1.8.3 sbf and then the HK 2.3.4 again?
Click to expand...
Click to collapse
There was an unlocked 1.83 that I think the2dcour (http://forum.xda-developers.com/showthread.php?t=1138204) uploaded so you don't have to unlock again. But its not up right now so I guess you'd have to flash back to 1.83, then flash the unlock sbf, then the 2.3.4 build again.
There might be an easier way not sure, but idk.
Related
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
jlem26 said:
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
Click to expand...
Click to collapse
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
regaw_leinad said:
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
Click to expand...
Click to collapse
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
jlem26 said:
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
Click to expand...
Click to collapse
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
spatel9114 said:
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
Click to expand...
Click to collapse
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
lol very,very true!
RUU has test-key. thats means no protected apps. You should have flashed one of the many roms based on this RUU(damage,fresh or darchlegend even though its based on the Legend RUU). There already set to go.
Anyway I can do that now?
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
jlem26 said:
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
Click to expand...
Click to collapse
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
regaw_leinad said:
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
Click to expand...
Click to collapse
Don't be sorry, I wasn't really aiming that at anyone in particular, I was just hoping to head off the thread turning into a point and laugh at the RUU users.
spatel9114 said:
Anyway I can do that now?
Click to expand...
Click to collapse
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Well I modified the build.prop last night and now all the apps are showing up in the market.
jlem26 said:
Well I modified the build.prop last night and now all the apps are showing up in the market.
Click to expand...
Click to collapse
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
MILH0U5E said:
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
Click to expand...
Click to collapse
Yeah it is pretty easy, just need to get your build.prop, then in wordpad, if using windows use wordpad not notepad, just have to make a few changes. After that you clear the market cache. When I did this last night, none of the protected apps showed up, however this morning they all did. So for reason it may take a bit to work right but it did work. Just checked and root manager is showing in my market too.
I'll just post one I found online. If you adb push this to /system/ it should work.
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
@Kcarpenter, maybe dont post inflammatory stuff like this and instead be helpful and we wont have drama?
@Jlem
Good to see you got it going. You should share your build.prop (or link to instructions) so others that may have made the early (and quite risky) install of the RUU could get it going. That would be a nice thing to do
Personally I think you're crazy for trying that RUU!!! hahaha ! I'm glad someone did, and I hope it all works out for you.
edit:And you did! good work
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
+1 Truth.
I have a feeling many people will do this.
danknee said:
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
spatel9114 said:
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
Click to expand...
Click to collapse
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
jlem26 said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
or adb remount first.
Not my work, sed took ivan's rom and added the the sholes fingerprint.
Full Market should work fine in it now.
http://www.multiupload.com/X0LZ3W1RSL
Awesome. Thanks for uploading this.
jcase said:
Not my work, sed took ivan's rom and added the the sholes fingerprint.
Full Market should work fine in it now.
http://www.multiupload.com/X0LZ3W1RSL
Click to expand...
Click to collapse
Thanks sed .......
and jcase
are there a few specific files that were changed so i could manually push those instead? done my own customizing and, if possible, would like to avoid pushing all those edits again
but thanks for the work
gohamstergo said:
are there a few specific files that were changed so i could manually push those instead? done my own customizing and, if possible, would like to avoid pushing all those edits again
but thanks for the work
Click to expand...
Click to collapse
For existing roms, use my script.
jcase said:
For existing roms, use my script.
Click to expand...
Click to collapse
ah alrighty. ill search for it. since i dont see a link in the OP.
edit: got it. twas in the later pages of your market fix thread.
EDIT2: flashing over an existing Ivan .8 with a dalvik-only wipe works great. got all my previously purchased apps now and no apps wiped
gohamstergo said:
ah alrighty. ill search for it. since i dont see a link in the OP.
edit: got it. twas in the later pages of your market fix thread.
EDIT2: flashing over an existing Ivan .8 with a dalvik-only wipe works great. got all my previously purchased apps now and no apps wiped
Click to expand...
Click to collapse
Without it working, I'm 1" away from doing a wipe.
Some claim success without a wipe, some say they need it, and some say they wait a couple of days.
I'm playing the waiting game.
gohamstergo said:
ah alrighty. ill search for it. since i dont see a link in the OP.
edit: got it. twas in the later pages of your market fix thread.
EDIT2: flashing over an existing Ivan .8 with a dalvik-only wipe works great. got all my previously purchased apps now and no apps wiped
Click to expand...
Click to collapse
I tried a dalvik-wipe then flash but I still couldn't find tapatalk in the market. I had to do a full wipe.
pkopalek said:
I did this, exactly, only using dalvik, from my existing 0.8t2.
adb shell
su
cd system
cd app
rm -r VVMStub_v3.apk
.... says it's Read Only.
trying to chmod it, can't it's Read-Only (despite my superuser access)
All in system/app is Read-Only. I can't even chmod.
Can't remove VVMStub_v3.apk
teeter.apk
com.android.launcher2.apk
that's all I tried, then I quit and I flashed my nandroid restore point back to the original 0.8t2 from BEFORE market fix.
Now I can manipulate my apps again.
Click to expand...
Click to collapse
you forgot to mount
adb remount
adb shell
rm -r /system/app/VVMStub_v3.apk
that's it
Using the Market Fix Ivan's ROM. Having an issue with app updates now.
About 1/2 a dozen of apps had updates pop up for me today. The update would download then go into "install" then return an "insufficient memory" error. Strange thing is that if the update was 700kb or less, the update would install. Larger updates like Handcent (~1.7M) would error out.
An uninstall and redownload/install of the problematic apps would work so I wasn't stuck other than resetting up apps like Handcent.
jcase did try to help me on IRC but I'm a tard when it comes to trying to copy/paste from the cmd window.
Im new to forum but Ive been trolling for the past couple days. I currently rooted my Vibrant with One Click GalaxyRooter. Then purchased Root Explorer to view the hidden files and folders that I need to get to in order to remove some of the stock .apk and odex files.
Im currently in the /system/app directory and the first thing that I want to remove is that avatar icon and files. I long press the file in root explorer to delete it and it allows me to. Only problem is that when I go back or refresh the directory everything is still there even when I reboot my phone.
Any suggestion.
AnthonyJFranks said:
Im new to forum but Ive been trolling for the past couple days. I currently rooted my Vibrant with One Click GalaxyRooter. Then purchased Root Explorer to view the hidden files and folders that I need to get to in order to remove some of the stock .apk and odex files.
Im currently in the /system/app directory and the first thing that I want to remove is that avatar icon and files. I long press the file in root explorer to delete it and it allows me to. Only problem is that when I go back or refresh the directory everything is still there even when I reboot my phone.
Any suggestion.
Click to expand...
Click to collapse
When using Root Explorer, on the top part of the screen, press [Mount R/O] and try again. I think that might solve the issue. Post up the results!
Why didn't you just uninstall the files via titanium backup?
Master™ said:
Why didn't you just uninstall the files via titanium backup?
Click to expand...
Click to collapse
Forget what I said, use Mater's method. lol
I do see the Mount R/O in the top right hand section of the screen and I pressed it but it seems like it didnt do anything. It just shows my memory used / free and r/w [ Mount R/O]
I tried deleting a file still was there when I came back into the directory
How do I access the file directory in Titanium Backup
AnthonyJFranks said:
How do I access the file directory in Titanium Backup
Click to expand...
Click to collapse
You don't access the file directory. Titanium Backup will show you a list of ALL apps installed. You simply click and press uninstall. Simple, no fuss. You can even make a backup before you uninstall it in case you need it later. Done.
Use Titanium Backup like everyone said, I also had the same problem with other Root Explorers. Also be sure to delete the .zip file because it might cause problems later. Also do you know what trolling means? I think you meant lurking, because trolling implies you've been trying to get people angry.
I didn't even notice he said he had been trolling LOL. Get back troll! My brain automatically assumed lurking.
AnthonyJFranks said:
Im new to forum but Ive been trolling for the past couple days. I currently rooted my Vibrant with One Click GalaxyRooter. Then purchased Root Explorer to view the hidden files and folders that I need to get to in order to remove some of the stock .apk and odex files.
Im currently in the /system/app directory and the first thing that I want to remove is that avatar icon and files. I long press the file in root explorer to delete it and it allows me to. Only problem is that when I go back or refresh the directory everything is still there even when I reboot my phone.
Any suggestion.
Click to expand...
Click to collapse
Your system is set to read only.
Follow the instructions found in this post (forgive me i'm too new to post links, and i want to give credit to the solution):
hxxp://forum.xda-developers.com/showpost.php?p=8643744&postcount=6
Code:
$ mount -o rw,remount -t rfs /dev/block/stl9 /system
Run the command from terminal, and you should then be able to delete the files that you want.
Here do this I had this happen awhile back this worked
AustinKnight45 said:
Download busybox from market then run it and update it then after it updates and you have the latest busybox go back to root explorer and delete the bloat ware dont know why this works but it does.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
AustinKnight45 said:
Here do this I had this happen awhile back this worked
Click to expand...
Click to collapse
sentences without periods are hard to read.... ha
This didnt work
Sent from my SGH-T959 using XDA App
eatspaper said:
Your system is set to read only.
Follow the instructions found in this post (forgive me i'm too new to post links, and i want to give credit to the solution):
hxxp://forum.xda-developers.com/showpost.php?p=8643744&postcount=6
Code:
$ mount -o rw,remount -t rfs /dev/block/stl9 /system
Run the command from terminal, and you should then be able to delete the files that you want.
Click to expand...
Click to collapse
I tried this and it didn't work as well I got a error message that said operation not permitted
Sent from my SGH-T959 using XDA App
Any suggestion on whats going on, I know its rooted the super user always pops up when ever a couple apps or on
Sent from my SGH-T959 using XDA App
AnthonyJFranks said:
I tried this and it didn't work as well I got a error message that said operation not permitted
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Did you SU in the terminal first before you ran the command?
As the title suggest, I have a 2.21 based Nexus One. And I use a Mac. Is ther an easy way to root it?
ajaffarali said:
As the title suggest, I have a 2.21 based Nexus One. And I use a Mac. Is ther an easy way to root it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
He's right. There is nothing really different about the mac rooting process since the SDK tools are generally the same.
efrant said:
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
Click to expand...
Click to collapse
This guide was for the main 2.2.1 update. Since the last time that post was edited, there was a second 2.2.1 OTA pushed, which I believe was a small fix for adjusting partitions or something similar and gave a slightly different build number. You know if this still works for FRG83D?
Xel'Naga said:
This guide was for the main 2.2.1 update. Since the last time that post was edited, there was a second 2.2.1 OTA pushed, which I believe was a small fix for adjusting partitions or something similar and gave a slightly different build number. You know if this still works for FRG83D?
Click to expand...
Click to collapse
Rooting by the method quoted works on all Android builds to date.
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
ajaffarali said:
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
Click to expand...
Click to collapse
The guide is prob missing a step. Make sure you change the permissions on busybox to allow it to run before you try using it. Try chmod 755 busybox
ajaffarali said:
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
Click to expand...
Click to collapse
Make sure you actually did get root, I had to run the first step a few times until I got the root prompt on my friends phone.
efrant said:
The guide is prob missing a step. Make sure you change the permissions on busybox to allow it to run before you try using it. Try chmod 755 busybox
Click to expand...
Click to collapse
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
ajaffarali said:
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
Click to expand...
Click to collapse
First thing to do after rooting is to make a backup. You would be surprised as to how many people forget to do this.
ajaffarali said:
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
Click to expand...
Click to collapse
First, flash any custom recovery if you already hadn't.
Then make a nandroid backup. It's a 'must' so you can go back if custom ROM flashing goes wrong. Also, backup your applications and their data is recommended.
hey
is someone working on temp root for tf ?
just wanna change few things in the tablet so i dont need perm root
+1 this would be great for me too.
With the newer firmware, no. With the ones that allow you to root, just stop as soon as you get the root prompt (#), and thats temproot.
The newer firmware fixes the exploits that used to enable temproot
Tortel1210 said:
With the newer firmware, no. With the ones that allow you to root, just stop as soon as you get the root prompt (#), and thats temproot.
The newer firmware fixes the exploits that used to enable temproot
Click to expand...
Click to collapse
Does this mean zero chances of this happening or just hasn't happened yet?
Well, no. You can root, do whatever the hell you want, and then unroot.
goodintentions said:
Well, no. You can root, do whatever the hell you want, and then unroot.
Click to expand...
Click to collapse
How would you unroot? Manually delete the su.apk and busybox?
ccb1208 said:
How would you unroot? Manually delete the su.apk and busybox?
Click to expand...
Click to collapse
remount /system rw
delete /system/app/Superuser.apk
delete /system/xbin/su
reboot
Or you could just leave it rooted like any sane person would do...
Gary13579 said:
Or you could just leave it rooted like any sane person would do...
Click to expand...
Click to collapse
I would if I wasn't planning on selling mine...
ccb1208 said:
I would if I wasn't planning on selling mine...
Click to expand...
Click to collapse
I made an extra 50 bucks selling my HP Touchpad because I sold the fact that I had added Android onto it. i see it as a benefit to the next buyer.