Related
This is an exploit, I take NO RESPONSIBILITY if this does ANYTHING bad, your fault not mine, it was only tested on the firmware mentioned below. If you redistribute it, republish, work it into a all in one click, please link back and PROPERLY credit me.
Tested on the
ro.build.date=Mon Jan 30 10:42:53 KST 2012
ro.build.version.incremental=ZV9.479A6632
Update for the VirginMobile LG Optimus V
Your phone needs to be updated to the above build, and potentially needs a factory reset before this works, but it works fine. This will allow you to flash recovery without being root. After flashing recovery, flash this zip http://dl.dropbox.com/u/8699733/rootme.zip to install su, superuser and disable re-flashing of the stock re covery
LinuxMac Script + files:
https://github.com/CunningLogic/GorditaRoot
Flash_image:
https://github.com/CunningLogic/GorditaRoot/blob/master/flash_image
Recovery:
http://www.mediafire.com/?vzc5k8taj9smmll (Credit BobZhome)
Windows users run the commands manually
GNU nano 2.2.2 File: Gordita.sh
Code:
#!/bin/sh
echo "GorditaRoot 1.0 by jcase / TeamAndIRC"
echo "for the VM670 Optimus V"
echo "March 21st 2012"
echo "Follow me! http://www.twitter.com/TeamAndIRC"
echo "Donations are optional http://forum.xda-developers.com/donatetome.php?u=2376614"
echo "-"
echo "Recovery taken from http://forum.xda-developers.com/showthread.php?t=1197991"
echo "-"
echo "Pushing recovery to /data/local/"
adb push VM670NH_recovery.img /data/local/recovery.img
adb push flash_image /data/local/
adb shell "chmod 755 /data/local/flash_image"
echo "Removing old sensor config, setting up symlink attack"
adb shell "rm /data/amit/*"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config.ini"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config2.ini"
echo "Rebooting to execute symlink attack, to chmod 666 the recovery block device"
adb reboot
adb wait-for-device
sleep 10
adb shell "rm /data/amit/*"
adb shell "/data/local/flash_image recovery /data/local/recovery.img"
echo "Recovery flashed! Enjoy"
Having trouble identifying whether or not you completed the root process? Quickly test for root access with Root Checker Basic
Confirmed working on a phone donated just for this purpose!
Started with stock firmware, Android 2.2.1, baseband VM670ZV4_60401001, generic android recovery
Flashed the VirginMobile Security Update from their website, became VM670ZV9_60401001 ZV9.479A6632
Manually walked through above script by jcase via gtalk, and using the exploit, was able to flash BobZhome's CWM for the VM670, reboot into it and made a backup.
Flashed the su zip, and all is well in Optimus V land again.
HUGE THANKS TO JCASE FOR TAKING THE TIME TO RE-ROOT THE VM670!!!
I only wish I understood what it all meant--so I could be excited, too!
wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
Means ppl who couldnt root before, now can
wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
i was gonna ask the same thing LOL
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
jlear3 said:
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
Click to expand...
Click to collapse
The update is not being pushed, because the OTA mechanism doesn't work on the OV. You have to go to the VM website and download the update from the phone FAQ.
The only advantage is a new radio, which give slightly improved performance.
Thank you very much!
I installed the update to my (unmodded) backup phone without thinking about whether or not I'd be able to root the handset after applying it. DOH!
I have just been using this phone as a WiFi device so far. I have run the battery down and recharged it once and installed a few apps on it. So I will run it down, recharge it again and then do a factory reset before I try rooting it just to make sure that I don't hose it.
It's a good idea to check all the steps before you start ...
Finally ran my battery down for the second time. So, I recharged, ran a factory re-set and ran the shell script on my Linux box to root the phone.
Oops!
The file VM670NH_recovery.img downloaded as VM670NH_recovery.bin and the system can't find/stat it! Hit ^C and bailed!
Hoping, hoping, hoping ...
Good! It's not bricked!
Renamed the recovery file, re-ran the script. Success!!
Rebooted into recovery, flashed rootme.zip
==> Did a nandroid backup.
Downloaded root check basic app and confirmed that it has worked.
So, for other modders trying this out:
Check your files and file names before you start! When I looked at Gordita.sh the first time I found that what I had downloaded was an HTML file with the script embedded in it. Copied and pasted from the OP and then checked again to make sure I had the right content.
Of course if you are running the adb commands manually then this won't happen to you.
But, as I noted above, I didn't cross-check that the recovery file that the script would be looking for had the right file name extension (.img, not .bin), so don't be me.
That said, jcase: Thank You Very Much!! Not only for developing this root exploit but also for making one that is robust enough for someone like me to goober it up and still come out unburnt!
After all of this , can you make it a hotspot in quick settings?
The setting dialog is there ..
H0daddy said:
After all of this , can you make it a hotspot in quick settings?
Click to expand...
Click to collapse
Once I rooted my phone I installed a modified ROM. And then another one, and then ...
I saw your question a bit ago and since I no longer had the stock ROM installed (and had never used Quick Settings to enable the hotspot feature before) I didn't know. I still don't. Here is the story on that ...
I just restored the ZV9 ROM from backup today and then installed the Quick Settings app. I can say that the app still has the option to enable the hotspot available and that it tries to set it up. However the phone I am using hasn't been activated yet and the 3G network isn't provisioned on it. So all I get is a message saying the network isn't available.
So, it looks somewhat promising. Maybe someone who has an activated phone with the ZV9 ROM can test it out and let you know.
And if I activate this phone before you get a useful reply I'll test it to see if it works.
So happy to see this
Please assist
Got up to step adb shell "chmod 755 /data/local/flash_image"
But got back "no such file."
CWM
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
knicks791 said:
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
Click to expand...
Click to collapse
so you have bobz recovery installed?... i assume youve tried rebooting to recovery form the powered off state via the key combo (HOLD home+vol down+power, RELEASE after the LG logo), and tried instal zip from sd again?...
try:
http://forums.projectopencannibal.net/beta-releases-11/lg-optimus-v-v2-1dev1-(10-09-2012)/
http://forums.projectopencannibal.n...1-universal-installer-for-lg-optimus-devices/
Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.
Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app
otonieru said:
Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
Well, I don't even get the blue light on boot to indicate it is waiting for me to push the button...
Additionally, I keep finding a lot of chmod/rm/ls permission denies whenever I tried to reinstall superuser, or use the PC installer for CWM and Titanium keeps FC whenever I try to start it.
I just ran rootchecker and got this:
Congratulations! You have root access!
Superuser Application Status:
Superuser application - version 3.0.7 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/bin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your R800x device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Any thoughts?
edwinen said:
Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.
Click to expand...
Click to collapse
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.
chery2k said:
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.
Click to expand...
Click to collapse
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.
edwinen said:
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.
Click to expand...
Click to collapse
Do not use an auto-installing app for CWM.
If you are on windows, use RecoveryX.
Sent from my Kindle Fire
Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.
lightningdude said:
Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.
Click to expand...
Click to collapse
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)
edwinen said:
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)
Click to expand...
Click to collapse
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.
lightningdude said:
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.
Click to expand...
Click to collapse
Yeah... well, whenever I try to do anything with adb shell, i get permission denied, I can't even ls!!!
how about re-flashing kernel? doom kernel should bring along CWM as well...
otonieru said:
how about re-flashing kernel? doom kernel should bring along CWM as well...
Click to expand...
Click to collapse
Hmm.. well looks like my only option is to wait for my bootloader unlock... but I have not heard back from them in about 5 days.
They r quite slow in replying email, contact them via gTalk directly.. or just pay 1st (like what i did), when they receive the money they will feel more responsible to finish the service, LoL
Sent from my R800x using xda app-developers app
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
For now i will suggest to falshback to original stock via flashtool..
Sent from my R800x using xda app-developers app
Well.. ended up unlocking the phone, and been messing with various options. Nothing seems to be working quite well, although it is because I am trying to use CM10 and CM9 which dont seem TOO stable.. but eh... Thanks for all the help everyone!
Hi, First I'm not a clever man, nor do I know what I did to brick it but, I used
"LCD Density Modder" on the market and bricked my phone.
https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&hl=en
My phone is bricked, it won't load anything past "Google", I've taken out the battery and put it back in MULTIPLE times, I've tried to reboot into Recovery Mode and get a red Triangle with an error.
I'm on 4.1.1 GSM model, Rooted and Stock ROM.
Is there anyway to fix this issue without completely wiping out my phone? The last backup I did was a week ago by hand, with click and drag.
Thanks for any help, I would appreciate it.
That's not bricking. And the red android is the stock recovery. Your going to need to flash a recovery and flash another ROM.
Sent From My Toro+ via White Tapatalk
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Or this
Sent From My Toro+ via White Tapatalk
Oh, wow, thanks, and that will save my files?
Is there a step by step process? I...am not a clever man =| or if there's a keyword I can search. Thanks...
I'm asking because I can't transfer files via USB to my Galaxy Nexus, nor does my computer detect it.
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Ignore the post I just made,
I found it manually, and rebooted the phone but it's still black screen when I pushe d it to the phone.
"build.prop /system/" sounds wrong though...but I am still shocked I was able to pull it.
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
smartedpanda said:
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
Click to expand...
Click to collapse
So what did you do exactly? Did you pull the file from your ROM first, modify it, and then push it back?
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
smartedpanda said:
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
Click to expand...
Click to collapse
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
It's to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
efrant said:
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
Click to expand...
Click to collapse
- Didn't know it was a hassle, my apologizes. I'll try to do it the old school method.
trevd said:
Its to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I had a feeling it was a permissions issue, but wasn't sure how to fix it.
I'll start pulling up the command prompts...wish me luck, thanks for all the help so far guys. I'll do two backup a week from now on, instead of weekly.
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
smartedpanda said:
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
Click to expand...
Click to collapse
Probably missed this step:
efrant said:
In the CWM menu on your device, navigate the mounts menu and click mount /system
Click to expand...
Click to collapse
efrant said:
Probably missed this step:
Click to expand...
Click to collapse
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
smartedpanda said:
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
Click to expand...
Click to collapse
Did you change the permissions like trevd suggested?
While booted in CWM with /system mounted:
adb shell chmod 0644 /system/build.prop
If that still doesn't work after a reboot, I suggest you re-flash grab the system image for 4.1.1 from Google's site, extract the system.img, reboot your device into the bootloader, and type: fastboot flash system system.img. It won't wipe your device, but it should fix anything that was messed up. (It will also remove root and busybox and whatever else you have installed on the system partition.
)
FINALLY! SUCCESS! I forgot the permission like you mentioned, but it didn't work the first two times, guess I mistyped something, it worked the third time.
I honestly appreciate all the help, and all the inputs. My phone is at 100%, and I'm doing a backup as we speak now.
efrant said:
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Click to expand...
Click to collapse
I know this thread is dead but I would like to say that this is the single most useful post I've seen in ages! I was looking around for nearly an hour and every post resulted in saying "reflash rom"...
Then I saw this, and worked!! My phone is her old self again
thumbs up!
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
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???
OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?
schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.
rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.
Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.
Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT