Related
Feel free to post your findings in this thread if you have updated to 2.2 (SUCCESSFULLY, (this isn't an "I bricked my phone" thread)) via the leaked OTA from this site.
That said, I have noticed a couple things I wanted to mention. Now whenever I plug my phone into my PC a notification bubble pops up and says CD ROM found and quickly launches a new tab on my PC for the Verizon Wireless Media Manager. Has anyone discovered a fix for this yet?
Also, I wanted to add a couple of screenshots from Quadrant and Linpack
From recovery with /system mounted to remove Verizon PC nag:
mv /system/etc/CDROM.ISO /system/app.disabled/
I've noticed that HTC skinned the "Recent App" window and the keyboard is multitouch now. I haven't had much time to mess with anything else though. criDikal's post fixes the Verizon pop-up too.
criDikal said:
From recovery with /system mounted to remove Verizon PC nag:
mv /system/etc/CDROM.ISO /system/app.disabled/
Click to expand...
Click to collapse
I have the system mounted as you said and I get the message
"mv: "can't rename 'system/etc/CDROM.ISO': Not a directory"
htc_woe_is_me said:
I have the system mounted as you said and I get the message
"mv: "can't rename 'system/etc/CDROM.ISO': Not a directory"
Click to expand...
Click to collapse
don't forget the leading '/' on /system/etc/CDROM.ISO
criDikal said:
don't forget the leading '/' on /system/etc/CDROM.ISO
Click to expand...
Click to collapse
I just copied and pasted exactly what you wrote into the command prompt. The next prompt reads exactly:
mv: can't rename '/system/etc/CDROM.ISO' : Not a directory
DO I have to make the directory for it somehow?
htc_woe_is_me said:
I just copied and pasted exactly what you wrote into the command prompt. The next prompt reads exactly:
mv: can't rename '/system/etc/CDROM.ISO' : Not a directory
DO I have to make the directory for it somehow?
Click to expand...
Click to collapse
You need to put a space after CDROM.ISO
mv /system/etc/CDROM.ISO /system/app.disabled/
htc_woe_is_me said:
I just copied and pasted exactly what you wrote into the command prompt. The next prompt reads exactly:
mv: can't rename '/system/etc/CDROM.ISO' : Not a directory
DO I have to make the directory for it somehow?
Click to expand...
Click to collapse
Ah, I apologize. I see where the problem is.
In recovery (ClockworkMod) after mounting '/system'...type 'adb shell' to obtain a root command prompt.
You should then be able to perform the mv command.
I just did an adb shell in recovery and did the following,
rm /system/etc/CDROM.ISO
Click to expand...
Click to collapse
Not too worried about needing that ever so some of us just deleted it.
kentoe said:
I just did an adb shell in recovery and did the following,
Not too worried about needing that ever so some of us just deleted it.
Click to expand...
Click to collapse
I still couldn't get the mv command working but the rm did the trick. Thanks.
Also why is the Quadrant rating for the Nexus One 2.2 so much higher? I figured we had the better device
You probably didn't already have a app.disabled directory. Should have done a 'md /system/app.disabled' before doing the mv command.
htc_woe_is_me said:
I still couldn't get the mv command working but the rm did the trick. Thanks.
Also why is the Quadrant rating for the Nexus One 2.2 so much higher? I figured we had the better device
Click to expand...
Click to collapse
If I'm not mistaken they both use the same processor. It could be that the N1 comes with a lot less bloatware maybe and no sense? Just a guess though.
1. When receiving an incoming call with a facebook-synced contact you will see their current facebook status scrolling across the call screen.
2. The pattern lock screen is a bit different (seems to be less error-prone)
3. Atleast for me, handcent SMS is not blocked(visually) by the keyboard anymore when receiving a pop-up text while the phone is locked.
We really need to get a list of known bugs (fixes if avaliable) and known updates!
I love that the screen shows both landscape views now.
I saw somebody complaining that it cant go upside down.... why?
Nobody is ever happy lol
Another thing I noticed was if you go to Messages>Menu key there is a new button that says Push messages with a picture of a globe on it (I was guessing www). Anyway what does that do? I press the button and it just says No push messages.
One more thing.. my reception strength seems to have gotten better. I went from having 1-2 bars avg in my house to 2-4 bars and I've never seen 4 bars here. Lovin FroYo over here.
Sent from my rooted Incredible with Froyo
Anyone else notice that it doesn't pause media playback after removing the headset?
Before, with Pandora or the builtin music player, when I removed my headphones, music would pause. Now.. it doesn't.
Also when I hang up from a call that previously paused playback, it doesn't resume again. I have to navigate back to the app and press Play.
Once the official version is out it will be smooth sailing. Just another week or so...
Thanks for the tips on removing the nag screen.
And below are my screenshots.....
Pretty stock 2.2 leak with some fixes applied.
onetimeuse said:
Thanks for the tips on removing the nag screen.
And below are my screenshots.....
Pretty stock 2.2 leak with some fixes applied.
Click to expand...
Click to collapse
Nice scores. Do you have any apps installed besides what came with the stock FroYo? Did you remove any apps? Just wondering because my scores were never that high...
Until I installed Hydra ocuv ov kernel..
I have a bunch of apps installed...maybe 30 or so in addition to what was stock Froyo. At that time I hadn't deleted any apps, but just today I renamed a bunch to prevent those processes from starting up. Got similar results.
Edit: Actually, Astro backs up 74 apps, so maybe I have more than 30...
Isn't Hulu supposed to be playable on Froyo? Doesn't seem to work on the Evo with netarchy's Froyo stock-rooted ROM. I've been researching this topic for a fix, and I've seen something done for Nexus One and CM6 users but I don't want to loose 4G. I thought being able to watch Hulu was one of the most hyped about features of having Froyo.
You need a hacked version of Flash, and to change your UAString to Desktop. Search in the Nexus One forum for details.
Engadget has a walkthrough for the Nexus One. All but actually playing a video worked great on my Evo running CM6 :/. maybe you will have more luck on the Sense browser..
Here's another link I found for the Nexus One: forum.xda-developers.com/showthread.php?t=688054
I tried installing the apk but it would not not install.
XevoX said:
Here's another link I found for the Nexus One: forum.xda-developers.com/showthread.php?t=688054
I tried installing the apk but it would not not install.
Click to expand...
Click to collapse
Did you by chance already have flash installed? If yes, you need to uninstall it first.... If no, what was the error? Did you use adb to install? or? I have that version installed on my phone (running cm6)...
Hairongreenfire said:
Engadget has a walkthrough for the Nexus One. All but actually playing a video worked great on my Evo running CM6 :/. maybe you will have more luck on the Sense browser..
Click to expand...
Click to collapse
I have Hulu working just fine via the default browser on CM6 nightly and RC1. Read the instructions and try again.
I appreciate the help fellas, but I'm looking for a stock-rooted Froyo solution. With the CM6 ROM you have to give up 4G, FM Radio, etc.
[QUOTE=spiicytuna;7455905]Did you by chance already have flash installed? If yes, you need to uninstall it first.... If no, what was the error? Did you use adb to install? or? I have that version installed on my phone (running cm6)...[/QUOTE]
How do I go about uninstalling Flash? I tried installing the apk straight up with estrong.
XevoX said:
I appreciate the help fellas, but I'm looking for a stock-rooted Froyo solution. With the CM6 ROM you have to give up 4G, FM Radio, etc.
spiicytuna said:
Did you by chance already have flash installed? If yes, you need to uninstall it first.... If no, what was the error? Did you use adb to install? or? I have that version installed on my phone (running cm6)...
Click to expand...
Click to collapse
How do I go about uninstalling Flash? I tried installing the apk straight up with estrong.
Click to expand...
Click to collapse
1) Uninstall Flash from the Settings>Applications>Manage Applications>All menu.
2) Install the hacked Nexus One version of Flash with Hulu support, via ADB.
3) Open any page in your browser then go to the url "about:debug" (without the quotes) and then go to Menu>Settings. Scroll all the way down to the bottom, select UAString, and change from Android to Desktop.
4) Go to http://www.hulu.com/
5) Enjoy.
drmacinyasha said:
1) Uninstall Flash from the Settings>Applications>Manage Applications>All menu.
2) Install the hacked Nexus One version of Flash with Hulu support, via ADB.
3) Open any page in your browser then go to the url "about:debug" (without the quotes) and then go to Menu>Settings. Scroll all the way down to the bottom, select UAString, and change from Android to Desktop.
4) Go to http://www.hulu.com/
5) Enjoy.
Click to expand...
Click to collapse
doesnt seem to uninstall that way...
mrloserpunk said:
doesnt seem to uninstall that way...
Click to expand...
Click to collapse
The leaked Sense 2.2 ROM has Flash 10.1 installed from the get-go, so you can't uninstall it in a traditional way. If you go into /system/app/ there is install_flash_player.apk. I renamed it "install_flash_player.apkz" (this makes it so Android doesn't recognize it, pretty much the same as just deleting it) so I could see what that would change. It doesn't remove Flash 10.1 from Menu > Settings > Applications, but it did stop Flash from loading in the browser. You could try that, but I don't know how far it'd get you.
cloud858rk said:
The leaked Sense 2.2 ROM has Flash 10.1 installed from the get-go, so you can't uninstall it in a traditional way. If you go into /system/app/ there is install_flash_player.apk. I renamed it "install_flash_player.apkz" (this makes it so Android doesn't recognize it, pretty much the same as just deleting it) so I could see what that would change. It doesn't remove Flash 10.1 from Menu > Settings > Applications, but it did stop Flash from loading in the browser. You could try that, but I don't know how far it'd get you.
Click to expand...
Click to collapse
I tried that way. Still get the can't install error. Flash
Uninstall is greyed out in stock 2.2 with root.
if you're rooted, use adb, shell in, navigate to where the apk is in system/app, rm it, then navigate to the data/data/ folder that the data is stored, rm that too. reboot. install the modified flash apk.
if you know part of the file name (adobe, or flash, or whatever), use adb shell, then
find -name "*partofthenameyouknow*.*"
it'll spit out the locations of the apk, data, and cache. then just rm -rf all those files. reboot. install the modified flash apk
timothydonohue said:
if you're rooted, use adb, shell in, navigate to where the apk is in system/app, rm it, then navigate to the data/data/ folder that the data is stored, rm that too. reboot. install the modified flash apk.
if you know part of the file name (adobe, or flash, or whatever), use adb shell, then
find -name "*partofthenameyouknow*.*"
it'll spit out the locations of the apk, data, and cache. then just rm -rf all those files. reboot. install the modified flash apk
Click to expand...
Click to collapse
Im getting closer. I did what you said. Was able to get the Flash 10.1 from the Nexus forum installed. When I got to Hulu, it still gives me "not available on your platform" error.
Edit: I forgot the about:debug command. Although, I did that, it still didnt work. I then downloaded the Hulu app made by someone, and
whala, Hulu is working.
Thanks
what hulu app? I could not locate it.... man this looks like a pain in the rear.... no way to simply change the way hulu see's my EVO? like a useragent string or is flash giving me away?
Owell, at least southparkstudios is working fine
mrloserpunk said:
what hulu app? I could not locate it.... man this looks like a pain in the rear.... no way to simply change the way hulu see's my EVO? like a useragent string or is flash giving me away?
Owell, at least southparkstudios is working fine
Click to expand...
Click to collapse
Actually, not a PIA at all.
Just fyi, I didnt use any ADB commands, just did it all on the phone using SUFBS.
1> Simply what was mentioned above. Remove the Adobe Flash stuff from the System/app and Data/Data area.
- I did this by renaming the directories using SUFBS on my phone.
2> Reboot Phone.
3> Install the Modified Flash (Found in the Nexus Thread)
- Once again, I just downloaded on the phone and used SUFBS to install.
4> Reboot Phone
5> Go to Browser, type about:debug and GO. Then go to Settings and down at the bottom, change the UAString to Desktop.
6> Whala.
This thread helped me out alot: (Widget here too).
http://forum.xda-developers.com/showthread.php?t=686765&highlight=hulu
AWESOME! Huge help, I got it done using winSCP. Incredibly easy. Thanks alot! Today has been a great day for my Evo... it got 2.2, SSH, Flash w/hulu... whats next a gold back cover? Thanks again!!
This fix (manually deleting the apk's) requires a full root, right?
dallashigh said:
This fix (manually deleting the apk's) requires a full root, right?
Click to expand...
Click to collapse
Yep.
Is Hulu still working for you guys? I get "The requested video cannot be displayed in your region" message now. I read that this will happen after you reboot....
mrloserpunk said:
doesnt seem to uninstall that way...
Click to expand...
Click to collapse
If you still havent got it to work,grab Android Mate from the market and use that to install the hacked flash version.It will ask if you want to replace the original flash so there is no need to uninstall it first.Then do the about:bug from your browser and you'll be good to go.
tsunami0ne said:
Yep.
Click to expand...
Click to collapse
Thanks. I was 99% sure, but I wanted confirmation before I wasted any of my time.
I am an Unrevoked3 user (I know, I know. No lectures please), and was pretty pissed about this. Then I discovered that NAND is unlocked when I'm in the ClockworkMod recovery. So I booted into recovery and did the following on my PC:
Code:
adb shell
mount -o rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o rw -t yaffs2 /dev/block/mtdblock6 /data
cd /system
mv install_flash_player.apk install_flash_player.ap_
cd lib
mv libflashplayer.so libflashplayer.s_
cd /data/data
rm -r com.adobe.flashplayer
cd com.android.browser/app_plugins/
rm -r com.adobe.flashplayer
umount /system
umount /data
exit
adb reboot
Then I installed the hacked APK, did the UA fix and was rockin and rollin.
Note the remount flag is not necessary above, because the partitions are not already mounted. In fact, if you try to use the remount flag, it will fail. I have .tar backups of the two directories deleted, if anyone by chance needs them to restore.
tsunami0ne said:
Is Hulu still working for you guys? I get "The requested video cannot be displayed in your region" message now. I read that this will happen after you reboot....
Click to expand...
Click to collapse
When you reboot, the UA reverts to default and you have to change it back to Desktop again.
This is for n00bs like myself that had to search around before getting into this and doing it correctly. A lot was copied from the Inc S thread, but felt the instructions were needed here so no need for searching there and crowding their forum with our questions: http://forum.xda-developers.com/showthread.php?t=1039015
Psneuter exploit is working on DInc2, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Install the HTC Sync software or PDANet software to install drivers for your phone to Windows
2. Ensure that the device is in USB Debug mode, go to Settings > Applications > Development and "tick" USB debugging and plug in your phone to your PC
3. Unzip the attached .zip into a directory (like c:\adb)
4. Open a command prompt by going to start > run and running CMD, and cd to the directory where you extracted the .zip (like cd \adb)
5. Type "adb devices" > enter, and ensure that your device has been detected
6. Run the "pushroot.bat" file
7. Type "adb shell /data/local/tmp/getroot" > enter
8. Type "adb shell" > enter
9. You are now in # prompt. Type "/data/local/tmp/pushroot"
After the last step, a new # line appears. That's it! You're temporarily rooted
You have to redo steps 7, 8, 9 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.
I run Bloat Freezer to rid the VZW apps
u can actually use the exact same process as the incS
I said that and linked to the Inc S thread for doing it
I just added in some steps for the issues I ran into, since it was my first time trying to do something like this and so others have a step by step to follow
And also so we have have something for this forum...thanks though
OK, question... if I do a temp root on the DInc2, then restore my wife's Titanium Backup to the new phone, can I also perminantly get rid of the VZW Bloatware, then reboot without Temp Rooting from that point on? (I know I will lose full Backups as well as SetCPU, etc. but will the Bloatware removal cause issues?)
I use Bloat Freeze and the VZW crap never comes back after a reboot when I have the "Alternate Freeze method" checked in the preferences, which is the Titanium Backup method
Maybe I am doing something wrong. I get to step #9 with
$ /data/local/tmp/pushroot and get
mount: operation not permitted
and a few more permission denied lines.
??? thanks in advance
Looks like the getroot did not work/run right, when you do step 8, the shell should start with the '#', not the '$'
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
xgunther said:
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
Use Titanium to freeze it. Don't delete it. Freezing works, but if you delete it it will just come back.
Sent from my ADR6350 using XDA App
I have done all the steps correctly up until step 5, well the problem is after typing in adb service, i get an extensively long list of different commands, and then the next step is to type in pushroot.bat, and when i do, heres what i get in return
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: dervice not found
C:\adb>
I dont know the problem...i do have Ongoing HTC Charge. USB Debugging connected. And PdaNet Connect (USB)
What could be the problem?
That should be adb devices, not serices
After that, you should see your device listed. When you typed services, the list you got was basically a help list for adb commands, since you did not type a valid one
Double check to make sure your device is detcted, if it is not, go to Windows' Device Manager and make sure the proper drivers were installed for your DInc
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
mykenyc said:
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
Click to expand...
Click to collapse
You must "freeze" them with bloat freezer or a similar app.
xgunther said:
You must "freeze" them with bloat freezer or a similar app.
Click to expand...
Click to collapse
With only a temp root wouldn't any bloat freezing reset on reboot?
x Eacott said:
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Click to expand...
Click to collapse
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
sixteen2nd said:
With only a temp root wouldn't any bloat freezing reset on reboot?
Click to expand...
Click to collapse
Negative, Freezing works on the temp root after a reset, just make sure if you use Bloat Freeze that you select the alternative freezing option (Titanium Backup method) when you do it
LowFire82 said:
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
Click to expand...
Click to collapse
There are a lot of things that could prevent adb from picking up your device... easiest would be to double-check that you have the USB Debugging option enabled on the device. The next easiest would be to make sure you have the correct drivers installed. I'd recommend using an app like USBDeview to see an extended list of all your installed USB drivers, and then deleting anything related to HTC/Android/adb. You can then reinstall the correct drivers which I believe LowFire mentioned in his OP.
/threadjack
Ahh! OK, I had to do a Master Reset of my wife's Inc2, previously it had TempRoot working.
I followed the instructions from the beginning after it was reset, but I cannot get TempRoot access. MyBackup Pro, Titanium, Root Explorer all say there is no root access. I get the phone listed at adb devices and get no errors running the commands. Anyone have issues gaining root?
xgunther said:
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
I have the same issue...just another # line after typing in the string from step 9 and hitting enter
What did you do?
Hello!
I flashed CM9 nightly on my GSM Galaxy Nexus a few days ago, and it has worked like a charm ever since. Until a few hours ago, that is...
I dug around in the CM-specific settings and (unfortunately!) ended up finding the Advanced settings, more specifically the CPU frequency setting. Just to see how it would handle things, I tried setting the max. frequency to 350 MHz (aka the default min. frequency). I was very surprised to see that the game Road Trip worked perfectly, and so I chose to keep it this way to save energy; I ticked "restore on boot". Later on, the phone rebooted during a phone call, but I thought, "oh, it's a nightly, this is to be expected."
What I noticed a few seconds thereafter (what is my real problem) is that the boot animation froze a few cycles in (after running at full fps for about one cycle), and the phone rebooted again, running into the same problem.
I still have this issue, even after factory resetting and reflashing the nightly (which I thought would remove the freq. "lock", but didn't).
Does anyone know how I can fix this? Is it as easy (or hard, because I can't access the actual system) as flashing some CPU-fixing ROM, or do I need to do something more, even send it to repair?
Thank you guys!
Go to revovry.
Go to Mounts and storage.
Format /system.
Format /cache.
Format /data.
Flash rom.
Flash Gapps.
Wipe data/factory reset.
Reboot.
tingen said:
Go to revovry.
Go to Mounts and storage.
Format /system.
Format /cache.
Format /data.
Flash rom.
Flash Gapps.
Wipe data/factory reset.
Reboot.
Click to expand...
Click to collapse
Did that, but the problem persists.
Anything else I can try?
swefse said:
Did that, but the problem persists.
Anything else I can try?
Click to expand...
Click to collapse
You have to wipe the init.d file.. in there is the script that is locking your boot settings...
zapford said:
You have to wipe the init.d file.. in there is the script that is locking your boot settings...
Click to expand...
Click to collapse
How exactly do I do that? From some advanced menu in CWM or somewhere else?
Now I got some help over on Google+:
Adb remount
Adb shell
rm /system/etc/Init.d
Click to expand...
Click to collapse
but the last command gives me a no such file or directory...
Where in the system structure is init.d?
swefse said:
Now I got some help over on Google+:
but the last command gives me a no such file or directory...
Where in the system structure is init.d?
Click to expand...
Click to collapse
'adb shell'
'su'
'rm -rf /system/etc/init.d/' - folder/file names in android (as in Linux) are case-sensitive.
if it still gives you "file or folder not found"
'ls /system/etc/i*'
do you see /system/etc/init.d/ or not? if not, either your current rom hasn't created that folder yet (case of AOPK comes to mind, user had to create dir manually), or it doesn't support init.d scripts at all.
bk201doesntexist said:
'adb shell'
'su'
'rm -rf /system/etc/init.d/' - folder/file names in android (as in Linux) are case-sensitive.
Click to expand...
Click to collapse
'su' might have worked (it said
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
'rm -rf /system/etc/init.d/' returned
rm -rf /system/etc/init.d/
Click to expand...
Click to collapse
Does this mean it worked, and that it is safe to reboot?
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Should be, give it a try.
BTW, booting a device is cpu intensive, hence the boot loops at low frequency
swefse said:
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Click to expand...
Click to collapse
@ Tubes6al4v:
Nope, didn't work.
Btw, 'ls /system' returns
bin
Click to expand...
Click to collapse
Is that normal?
My failsafe is to use fastboot to push a stock image over. Just keep in mind it will wipe your sd card.
Tubes6al4v said:
My failsafe is to use fastboot to push a stock image over. Just keep in mind it will wipe your sd card.
Click to expand...
Click to collapse
So I'll follow this guide?
http://forum.xda-developers.com/showthread.php?t=1366806
Just one more n00b question: Can I pick whichever image I want, even though my phone came with 4.0.1?
If not, how do I know if it's ITL4D or ITL4F?
swefse said:
'su' might have worked (it said
'rm -rf /system/etc/init.d/' returned
Does this mean it worked, and that it is safe to reboot?
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Click to expand...
Click to collapse
if 'su' errors, then you don't have su binary installed. you wouldn't be able to delete /system/etc/init.d even if it was there. you should see a lot more stuff inside /system/ though.
swefse said:
So I'll follow this guide?
http://forum.xda-developers.com/showthread.php?t=1366806
Just one more n00b question: Can I pick whichever image I want, even though my phone came with 4.0.1?
If not, how do I know if it's ITL4D or ITL4F?
Click to expand...
Click to collapse
before you go restoring to stock, go in bootloader and try:
'./fastboot erase cache'
'./fastboot erase userdata'
see if it boots.
'adb logcat >> logcat.txt' would help debugging as to why the device is bootlooping as well.
Or is it easier to use this, and not have to worry about what version it is/was?
http://forum.xda-developers.com/showthread.php?t=1392310
swefse said:
Or is it easier to use this, and not have to worry about what version it is/was?
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
that's your choice. if you do use that toolkit (or any toolkit, for that matter), read instructions well.
I was redirected to this guide to get the fastboot drivers (and fastboot): http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
When I open "install-superboot-windows.bat", though, it says "waiting for device", and stops there.
Should I just have downloaded it and continued with the first guide (linked a few posts above), or should I have clicked "install-superboot-windows.bat"?
Edit: Now when I tried "install-superboot-windows" a second time, it rebooted the phone, but into Android (resulting in the usual freeze-reboot). I'm stuck, please help me!
Now I tried flashing MCR Ir9, which I had laying around on the internal memory, but it screwed up even worse: Now I don't even get past the first "Google" + unlocked boot loader icon screen.
Should I maybe just send it to Samsung, and foot the bill, before I brick it forever (if I haven't already, that is), or do you guys know what to do?
swefse said:
Now I tried flashing MCR Ir9, which I had laying around on the internal memory, but it screwed up even worse: Now I don't even get past the first "Google" + unlocked boot loader icon screen.
Should I maybe just send it to Samsung, and foot the bill, before I brick it forever (if I haven't already, that is), or do you guys know what to do?
Click to expand...
Click to collapse
Pull batery, VOLUP+VOLDOWN+POWER into fastboot/bootloader. Reflash stock with fastboot.
bk201doesntexist said:
Pull batery, VOLUP+VOLDOWN+POWER into fastboot/bootloader. Reflash stock with fastboot.
Click to expand...
Click to collapse
I'll try that, and let you know how it works. Thank you!
Now it was successfully recovered and works again, thanks to fastboot and the wonderful convincing of you, bk201doesntexist!
Thank you!
I am using Sandvold's ROM but, starting from some days ago, I encountered a big problem: during startup, my Desire freezes and cannot terminate the boot sequence. Even a nandroid restore is not able to fix it: I have to factory reset the device and, after that, restore works. I haven't changed anything, I don't know what could cause this problem, which is very annoying.
I use the latest version, 0.18.2.1.
What could I do?
I'm using the same version of the ROM and for a while now it has been randomly freezing up and I have to physically remove the battery to be able to restart it, after which it resets the date back to January 1980.
Today it froze up and it is also stuck in a boot loop. Tried wiping the dalvik cache and that didn't work so I'll do the factory reset like you suggest. I don't really want to have to switch back to a GB ROM though as I really like ICS.
Same problem here, the problem started when I rebooted today. Running sandvold 0.18.1.
After some digging I could identify a rough source of the problem, but I'm not Android guru, so it will take somebody more experienced than me to figure this out. Essentially, what happens, is that the system_server goes into a loop and keeps on crashing and getting restarted. I've attached the logcat for the gurus.
I'll try reinstalling and possibly wiping to see if that helps.
Just a quick followup, I had to do a full wipe to get back to working order. Attached is a comparison logcat. I don't really understand how Android boots, so I would kindly ask the more knowledgeable devs to have a quick look. Thanks!
After setting the phone up and rebooting, the problem is back again. Seems like there is a time/date-related bomb in sandvold 0.18.
The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Actually I didn't try to install anything from .apk so it can be related to the installation process itself.
Also the same problem has 0.17.1.1 (I don't сheck all versions, just the last ones of majors).
---------- Post added at 09:47 AM ---------- Previous post was at 09:20 AM ----------
0.16.1 - the same problem.
Steps to reproduce:
1. Wipe and install ICS
2. Add google account (at that point the phone still survives a reboot nicely)
3. Install any soft from Play
4. Reboot and enjoy the bootloop
Add: update of an existing soft from Play still causes a bootloop.
dietwice said:
The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Click to expand...
Click to collapse
Someone with posting privileges should report this problem in the developer's forum...
roberto.zanasi said:
Someone with posting privileges should report this problem in the developer's forum...
Click to expand...
Click to collapse
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.
dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Click to expand...
Click to collapse
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.
roberto.zanasi said:
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.
Click to expand...
Click to collapse
I also tried to do this via Terminal, and my "su" is ok.
But it doesn't work.
It looks like commands are being executed successfully, but it in fact they aren't.
Same problem for me...I'll try to fix it following your help!!! I let you know!!
It work, but I'm not able to "install" the edit Play Store downloaded!!! Reboot work, but no Play Store present among my applications!!!
I find com.process.vending in my application list, but it's a grey icon whit the small sd symbol!
I'll try again to uninstall it!
I have the same problem but, when I tried to use the dietwice's method, I found only the Vending.apk on /system/app folder. So I removed it, replaced with the Vending.apk file downloaded and I continued to follow the method and then I rebooted the phone.
The boot loop is present also after this, so I'd like to know if the fact that I didn't found com.android.vending and com.android.vending.updater is a signal that something was wrong even before applying the dietwice's method.
Someone can answer to my question, please?
I have the same problem as freakymonkey. Any Ideas?
gartenriese said:
I have the same problem as freakymonkey. Any Ideas?
Click to expand...
Click to collapse
I have flashed the ROM again from ClockworkMod recovery and, first to make the reboot, I used the dietwice's method and everything went OK! :good:
On the first boot something went wrong with synchronization with my gmail account, but after a reboot (without boot loop) everything worked fine.
I restored everything but sd-ext and it (re)booted fine, so it has something to do with that. Maybe some Google Play Store data is still on there? How can I get rid of these?
EDIT: Ok, I found some files, will try to delete them tomorrow.
Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.
Click to expand...
Click to collapse
matteo.rek said:
Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
Click to expand...
Click to collapse
I have been unable to get the Play Store back on my HTC Desire. I have followed the above steps exactly but no shortcut appears on the applications screen.
I have tried wiping the dalvik cache, even did a fresh install of ICS Sandvold Rom but no luck.
Could it be because of the default a2sd?
Any assistance much appreciated guys