Related
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk
mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app.
Click to expand...
Click to collapse
ADP builds of Android do not have TMobile apps such as Amazon MP3. This has been discussed ad nauseum if you had bothered to search.
mimic1011 said:
I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
It's a protected app. If you need it that bad that I suggest you go back to an RC build and do research before blindly flashing whatever build of Android is at the top of the forum.
mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
If you still have the RC firmware you can just unzip it copy the amazon apk out and install it into the adp the amazon works. I dont think anyone has the IM app working though
We should have an official rc update from tmobile real soon, which will have amazon mp3, myfavs, etc...
Just open a RC33 update.zip and extract the file from /system/app. Then you can install it by adb push.
Verified as working. I just added it to the app folder of Dudes 1.1 build and then did the update and it works just great. Purchased and downloaded a song to verify.
Here it Is
http://droiddeveloper.com/com.amazon.mp3.zip
enjoy it works for me...
Really Bad,
In Germany it cannot charge my creditcard... It has enough money on it.
I have the dude's 1.5 version, and cant seem to get it running. It forces closed upon trying to open. Any thought? It is saved to my SD in the app folder.
TIA
Read my guide
http://forum.xda-developers.com/showthread.php?p=3763025
TY SolemnWishing, this is how I got the app on my SD card to begin with - yours is a very helpful thread for a n00b like me. Unfortunately, I was never able to get the app to open. I am not sure how I could have messed it up - pretty simple, I navigate to the app folder on my SD and click the apk file which proceeds to install Amazon MP3. No go.
If you have any ideas on what the problem might be I would appreciate the input.
Thanks again for your great tutorial
Hmm... I assume you deleted the .zip and renamed it to .apk, what firmware are you using?
I am using firmware 1.5. Yes I renamed to apk. I wants to work, just force closes before it fully loads. I also have this problem with oi music player. It used to work, now no longer loads. I wonder if my SD card is the problem. It is 8 gb, but I am sure only like a class 2 card.
Strange. I have JF 1.5 and installed the Amazon app the normal way for any app on the G1 and have rebooted several times. The app still works. I thought if you did not push the app to the G1 it would need to be reinstalled each time you reboot the device?
Well, I am pretty positive it was my SD card - after writing my post this morning I pulled the SD card and have not been anble to get the phone back since. This thread pretty accuratly describes what is going on...long story short, i think I fried my SD card and as a result am stuck on Splash 2. I have wiped several times...
http://forum.xda-developers.com/showthread.php?t=516874
uggg...all for mp3's!!!! any thoughts and lots of luck would be appreciated.
K
Ahh I did the same thing. Here is what you need to do, you will need to force format it. Windows will NOT detect the card, and it may even freeze your computer. Put the phone into another device, such as a palm pilot or another cell phone and format it from there. It shouldn't take very long, and when it is completed, it will likely say the memory card only has 5Kb or so of memory on it. NOW insert the card into your computer and reformat it into a FAT32 format (+Ex2 for apps to SD) and you should be good! Of course, you will need to reload all your files though. That will fix your SD card. As for your phone... you will need to completely reflash a new firmware onto it, as right now starting up your phone is looking for items on your SD card which it may need, which no longer exist.
edit: if that doesn't work, completely start from the beginning by flashing the dreamimg.nbh file for rooting.
I was able to reformat the SD card, lost all my backups of course, and had to reflash dreaming.nbh and start from scratch. No biggy, at least i still have my phone.
thanks for all the tips...once i get my card re-partioned, I will try the Amazon.apk again.
K
I got it to load - thanks for all your help.
K
No problem at all, glad I could help.
Here's a odd one!
I was using my S7 to research an issue with my Samsung LED Smart TV. I found a How To, noticed a file path at the top of the page and backed up one page. It had several links, one of which was "How to Power Cycle a Customers Network". That sounded interesting so I clicked on it.
As soon as I clicked on the link my S7 turned OFF. I turned it back ON and it was stuck on the Dell logo. I pinned holed and tried again. It stuck again.
I booted into the recovery menu and tried to boot from there but it again got stuck. I had to do a factory reset. I use My BackUp Pro with a external SD card, it wasn't that painful and other than my email to setup, I'm back up.
Anyone see anything like this before?
Here a link to the nasty page for the brave to try: http://support-us.samsung.com/cyber/popup/iframe/pop_troubleshooting_fr.jsp?idx=151038&modelname=&modelcode=&session_id=P7mLwJcB60VpLrLWp3vgvhhXtfh2XSS3p78q2QlvhT3McsST29T1%21-1964052360%211228160092%211329276619709
Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install
cdzo72 said:
Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install
Click to expand...
Click to collapse
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.
wptski said:
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.
Click to expand...
Click to collapse
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.
cdzo72 said:
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.
Click to expand...
Click to collapse
I'm sure that a reset must wipe everything out, true? A reset barely a month ago. Your saying that monthly maintenance is needed?
I don't reinstall Windows monthly as that's a last resort at any time.
NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.
cdzo72 said:
NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.
Click to expand...
Click to collapse
Both for rooted devices and no good for me.
wptski said:
Both for rooted devices and no good for me.
Click to expand...
Click to collapse
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please
cdzo72 said:
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please
Click to expand...
Click to collapse
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??
wptski said:
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??
Click to expand...
Click to collapse
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes
cdzo72 said:
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes
Click to expand...
Click to collapse
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.
wptski said:
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.
Click to expand...
Click to collapse
Then you definitely had/have a corrupt package and the renaming is a sign of a read only problem trying to surface sounds like to me
I ... may have bricked my Droid 4. I won't go into details unless somebody asks, but I don't think it's necessary. I AM able to get to the recovery mode though, I just have nothing to recover from.... I misplaced my back-up.
So, I need SOMETHING to flash my phone to. 4.0/2.0/I don't care, I just need any rom/SBF to make this bad boy boot again. Anybody have anything?
I saw and downloaded the first thing that shows up when you google "droid-4-system-dump-wallpapers-ringtones.html" (link doesn't work because I'm new) But, I was unable to make anything of it.... What do I do?
Just to help others avoid the same fate can you please let us all know what you did?
zeroibis said:
Just to help others avoid the same fate can you please let us all know what you did?
Click to expand...
Click to collapse
Well, in hindsight it was kind of dumb. I rooted it, and began to remove all of the VZW sponsored apps. Once I did that, it cleared out a lot of memory (storage AND ram) but seemed to come with the downside of preventing my "settings" activity opening up. As in, whenever I hit "menu" then "Settings" from the main launcher, it would force close behind the scenes (logcat showed the stack trace for the settings activity).
I spent the next day trying to fix that issue, copying "settings.apk" from that link I mentioned earlier to my root director, but that didn't fix it. So, I went and tried copying entire folders over. This is the embarrassing part... I hit a 'delete' button on the "system/apps" folder, got about 30 force close windows, and am now stuck in a bootloop.
Doing the "power + both volume buttons" still gives me the recovery menu, but I don't have anything to recover to, as I was stupid and didn't think to make a backup.
Dwebtron said:
Well, in hindsight it was kind of dumb. I rooted it, and began to remove all of the VZW sponsored apps. Once I did that, it cleared out a lot of memory (storage AND ram) but seemed to come with the downside of preventing my "settings" activity opening up. As in, whenever I hit "menu" then "Settings" from the main launcher, it would force close behind the scenes (logcat showed the stack trace for the settings activity).
I spent the next day trying to fix that issue, copying "settings.apk" from that link I mentioned earlier to my root director, but that didn't fix it. So, I went and tried copying entire folders over. This is the embarrassing part... I hit a 'delete' button on the "system/apps" folder, got about 30 force close windows, and am now stuck in a bootloop.
Doing the "power + both volume buttons" still gives me the recovery menu, but I don't have anything to recover to, as I was stupid and didn't think to make a backup.
Click to expand...
Click to collapse
No files are floating around at this time. You really screwed yourself over on this one. Go back to Verizon and beg. You chose to void your warranty.
Dwebtron said:
Well, in hindsight it was kind of dumb. I rooted it, and began to remove all of the VZW sponsored apps. Once I did that, it cleared out a lot of memory (storage AND ram) but seemed to come with the downside of preventing my "settings" activity opening up. As in, whenever I hit "menu" then "Settings" from the main launcher, it would force close behind the scenes (logcat showed the stack trace for the settings activity).
I spent the next day trying to fix that issue, copying "settings.apk" from that link I mentioned earlier to my root director, but that didn't fix it. So, I went and tried copying entire folders over. This is the embarrassing part... I hit a 'delete' button on the "system/apps" folder, got about 30 force close windows, and am now stuck in a bootloop.
Doing the "power + both volume buttons" still gives me the recovery menu, but I don't have anything to recover to, as I was stupid and didn't think to make a backup.
Click to expand...
Click to collapse
I'm curious about this too - I deleted a bunch of vzw garbage. I did make a copy of of everything with titanium backup first but when I tried re-installing one of them it just hung while another re-installed fine.
I had a similar issue with one app - I had to go into /system/app and change it form RO to RW. Once Read/Write was enabled, Titanium was able to restore the app.
I have been playing it safe and only freezing the apps, not deleting them. I have had no FC or any odd behavior. I figured with an allocated 3 gb to applications, at this time gaining an extra 100MB of storage space is superfluous...especially with no SBF available.
As mentioned above, try going to the VZW store and getting an exchange. I'm certain an .sbf will be released at some point but it could be weeks/months before that happens.
And for future reference/anyone else reading this thread...never delete system apps! Just freeze them. Yes they will still be taking up space, but they won't be using any memory and they won't show up in your launcher so it's basically the same thing...except with freezing it is 100% reversible and will still allow you to receive updates.
Can someone upload these files from D4:
/system/build.prop
/system/default.prop
Freeze Apps
SGMD1 said:
As mentioned above, try going to the VZW store and getting an exchange. I'm certain an .sbf will be released at some point but it could be weeks/months before that happens.
And for future reference/anyone else reading this thread...never delete system apps! Just freeze them. Yes they will still be taking up space, but they won't be using any memory and they won't show up in your launcher so it's basically the same thing...except with freezing it is 100% reversible and will still allow you to receive updates.
Click to expand...
Click to collapse
What is the best way to freeze apps? I know you can do this with Titanium Backup. Do you need the pro version in order to do this? Are there other apps out there that also allow you to freeze apps?
kwyrt said:
What is the best way to freeze apps? I know you can do this with Titanium Backup. Do you need the pro version in order to do this? Are there other apps out there that also allow you to freeze apps?
Click to expand...
Click to collapse
You do need the Pro version of Titanium Backup to freeze apps I believe. There are free apps that will do it (i.e. Bloatware Killer) but I am not really familiar with them.
Skrilax_CZ said:
Can someone upload these files from D4:
/system/build.prop
/system/default.prop
Click to expand...
Click to collapse
http://db.tt/LymDelkf
That zip contains the 2 files you asked for. Anything else you need just ask and I can pull it for you. I havent done a dd of all the partitons yet but will be doing that as soon as I can.
cellzealot said:
That zip contains the 2 files you asked for. Anything else you need just ask and I can pull it for you. I havent done a dd of all the partitons yet but will be doing that as soon as I can.
Click to expand...
Click to collapse
The link that I was referring to in the first post SHOULD have every file from the D4.
I meant if he needed any of the other partitions besides the system.
I wanted to give him exactly what he asked for because he is avery sharp guy who may help us out with this device.
Unfortunately I did the same (though not as bad...I just can't open any of my contacts). I changed the permissions for /system/apps but I still am hanging at restoring in Titanium Backup. Are there any other directories that should have changed permissions to get some of these apps restored?
Also, lesson learned....freeze no uninstall
mattlgroff said:
No files are floating around at this time. You really screwed yourself over on this one. Go back to Verizon and beg. You chose to void your warranty.
Click to expand...
Click to collapse
Yeah so what? Why do people feel the need to post condescending comments for no reason? Its because of mistakes and screwups that the community progresses. There will be files floating around by the weekend, I'm sure.
I'm in the same boat... I bricked by droid 4... now waiting for a sbf file... someone said go to vzw and beg... has anyone ever tried that, after bricking your phone? what did you say? and did it work?
I'm just trying to figure out how to get vzw to replace this phone.
---------- Post added at 09:05 PM ---------- Previous post was at 08:56 PM ----------
reigndropz said:
Yeah so what? Why do people feel the need to post condescending comments for no reason? Its because of mistakes and screwups that the community progresses. There will be files floating around by the weekend, I'm sure.
Click to expand...
Click to collapse
The files will be released by the weekend? YAY... how do you know?
Also what does it take/what has to be done for someone to release these sbf files?
jgardner said:
Unfortunately I did the same (though not as bad...I just can't open any of my contacts). I changed the permissions for /system/apps but I still am hanging at restoring in Titanium Backup. Are there any other directories that should have changed permissions to get some of these apps restored?
Also, lesson learned....freeze no uninstall
Click to expand...
Click to collapse
That's the only path I had to change. Do you recall if you happened to have moved an app to a different path (perhaps to the sd-card) then removed it?
Are there multiple apps you are trying to restore? If so, have you tried restoring them one at a time?
im going to wait for the sbf files before any major modifications to my phone, then we can all start the fun
i just froze apps to prevent them from running, im not worried about space since i put in a 32GB SD card
I think it's very wise to wait for the firmware to be released, but it's worth noting that the term SBF is a mistaken reference to the old format for firmware files and that all dual core Motorolas have fastboot support now and RSD Lite has been modified to support this and uses xml.zip files that are sets of signed images rather than the Single Binary File(SBF).
This is a very important distinction to be made as the new format and boot menu provide many more options for controlling the flash process for the end user and it is ultimately much safer and more flexible.
Please find at the URL below my copy of the stock ROM (Version C) for the D415, with my modifications included.
The D415 is a great phone for the price, and it came with many cool features. However, the phone still has an amateur streak running the stock ROM. Some of LG's apps are great on this phone, but some of them are downright useless for most of us. T-Mobile added their own pushy bloatware to the mix as well. The end result, as we all know, is a usually fluid, but at times clunky and awkward experience using the device. I was impressed the first day I had it, but I wanted to make it better that first day as well. I wanted to get rid of all the useless stuff, and polish it into something I wouldn't be embarrassed to pull out in front of a client. I liked a lot of what LG did here, and wanted to hold on to that, but I also wanted a few changes:
Root:
FOTAkill
SuperSU installed on first boot
Polish:
Small UI sounds changes
Boot Animation
Replaced Flashlight App (thanks to xbmi, consider a donation in the app)
Added Heads Up
Removed foo foo themes
Added Bookmarks Sync
Replaced Stock Messenger with AOSP MMS
Debloat:
LG Memo & Widget moved to user apps
LG Music & Widget moved to user apps
Visual Voicemail moved to user apps
Weather widget moved to user apps
Apps removed completely:
LG Contacts widget
TMobile TV
Lookout
CarrierIQ
Maps
Mobile Life
Streetview
Talkback
T-Mobile My Account
T-Mobile Name ID
Voice Dialer
Youtube
Amazon
Chrome
Cloud Print
Drive
Easy Home
Gmail
Google Plus
Google Calendar
Play News Stand
Play Books
Play Game
Play Movies & TV
Play Music
Google Search
Google TTS
Hangouts
Stock Calendar
To do:
AOSP Keyboard (IDK what I'm doing here yet. It's crashing when I put it in now).
Version E (need to learn how to extract KDZ)
Instructions:
Download zip to SD
Reboot to Recovery
Wipe Dalvik, cache, data, system.
Install zip
Reboot and enjoy
Thanks to @Daisuke1988 for the original flashable stock rom.
Feedback welcome in replies!
I just got this phone today. I hate it but this should make it much better. Thanks guys!!
Sent from my SGH-M919 using XDA Free mobile app
Keep poking around with it. There are a lot of hidden gems sprinkled in by lg that will really cause you to like this phone. I came off of a nexus 5 to this. I chose it for the price tag, you can't beat $7 a month and get the build quality and battery life. I would buy again. The only thing I miss is a decent camera. But the stock camera app helps with auto focus mode.
Will it work on d405?
catbro said:
Will it work on d405?
Click to expand...
Click to collapse
Good question, it would be nice
Sent from my LG-D405 using XDA Free mobile app
I guess I have to try this evening, if nobody's trying till then I will report back
If the pure stock ROM works in the 405, this one should as well. I'm not sure myself without looking it up.
I have a D41510c and when I tried to install this rom, it failed. I'm restoring a backup, but I will try again in a while.
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
jb3p76 said:
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
Click to expand...
Click to collapse
I'm re-downloading, hopefully this will work!
I can deodex this but you will have to wait till Tuesday for me to upload it. or is it already deodexed?
I had thought about it but honestly haven't learned how to yet. Was I mistaken to think the payoff would not have been that great? Either way, I can wait til Tue, I know others will want it deodexed. Thanks!
I tried again, but it failed...
E:Error executing updater binary in zip
E:Unable to mount '/system'
EDIT: I was able to boot into the rom, but it's extremely slow
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Before I get too far down the rabbit hole can anyone confirm they have successfully flashed this and its working out for them?
jb3p76 said:
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Click to expand...
Click to collapse
Well, I rebooted and it's faster now. I used towelroot to get root. Nohing appeared about the permissions. I was able to update the binaries using TWRP.
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
jb3p76 said:
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
Click to expand...
Click to collapse
I use ROM Toolbox Pro, and when I went to start it the first time, it said root check had failed. That's why I used towelroot. I'll continue to test things and report back to you. So far, it's pretty smooth.
Weird. Can you tell me if the SuperSU apk is to be found in /system/apps/bootup?
I'm doing a backup so i can wipe and install fresh again. I'd like to mess around with the root stuff and see if I can figure that out. Did you happen to get a listing of which files are missing?
Hello gentlemen,
I'm back, with a what I hope is a minor issue. I hope someone can help me.
I have the following head unit (Universal Model):
KLD Universal model S07 - RK3181 (quadcore)
800x480 resolution - KK 4.4.4_23072015
MCU version MTCB-KLD2-V2.67 (Jul 09 2015 19:15:51)
Kernal version 3.0.36+ [email protected] #396 (Wed Jul 22 17:40:16 CST 2015)
Build number RK3188-ENG4.4.4 23072015.09:09:11
CPU ARMv7 1.6Ghz (x4)
It is rooted via the factory settings method. But other than that it is pretty much still stock (I added a cooling fan). The only other apps I add where PowerAmp, PowerAmp Toast, Xposed Framework, XposedMTC, and Lucky Patcher (I believe this app fully unlocks the PowerAmp app). I have had no issue with it for the last 7 months.
However, the other day it took a long time to bootup. Now I have some google service errors: "the process com.google.process.gapps has stopped"
I have to keep on clicking "OK" in order for the error pop-ups to close. I have to repeat this several times until all the pop-ups finally stop. Other than that, everything else is working properly. Although I notices that Xposed and PowerAmp Toast do not start (no icons on the top notice bar).
I tried going to Settings/App Manager/Google Service Framework - and then I click Forces Stopped it, Disable, Clear Data, Clear Cache, Enable. Then I reboot, but I still get the same google service errors.
Can someone please help me fix this? Any help will be greatly appreciated.
Thanks,
Galo
PS - One other thing. This is related to the XDA website in general. How can I get rid of that stupid side panel (Analysis & Opinion / More XDA New). It keeps on automatically scolling and gets in the way of reading and typing. It is really annoying. Can someone tell me how to switch this off. Thanks again
Lucky Patcher has a "clear cache" option. Maybe try that? Should force all the Android apps to optimize at boot and maybe fix your issues.
Hello BullGawd,
I already tried that. I also tried going into Settings/App Manager and clearing the cache for Google Services Framework.
I even tried by pressing the small reset botton on the face of the head unit. I am trying to avoid doing a factory reset from the recovery screen.
Has anyone had this issue with this these head units? How did you get this error fixed.
Thanks,
ggee
Hi guys,
My unit is stock. But I think I am just going to flash a newer version of the factory firmware (kitkat 4.4.4). In the old threads there used to be two repositories. One was the huifei-fileserver, and the other was a Google Drive site. Now I only see the huifei-fileserver.
Anyways, I downloaded the latest KLD RK3188 800x480 firmware:
http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/
However, it looks like the firmware .img file is made up of two parts. Both are zip files and each one contains a .img file.
-Am I supposed to merge both of these files into one .img file? If so, how do I do this?
-Or am I supposed to put both of these .img files into the root of the sd card (then insert to the gps slot)?
I know how to flash and update the firmware. However, I have only ever seen this process done using one .img file - not two. Can someone please clarify what to do with these two files in order to flash them properly. I do not want to gamble and brick my unit.
Thanks,
ggee
is one an mcu.img file? If so, remote that and only flash update.img
Dave
TT_Vert said:
is one an mcu.img file? If so, remote that and only flash update.img
Click to expand...
Click to collapse
Hello,
The first zip file says Part1 and its 204MB in size. This zip contains one update.img (634MB when extracted). The second zip file says Part2 and its 91MB in size. This zip also contains one update.img (yet it is the same size when extracted - 634MB). This is confusing and should be something easy and straight forward.
I am not sure if both of these files need to be merged. If they are supposed to be merged, how would you do this (what app does this).
-OR-
I am not sure if both update.img files need to be copied to the root of the sd card. However, both files cannot have the same name within the same directory, otherwise one file will overwrite the other. One file name will need to be changed. But I believe once you change the name, the head unit will not recognize it as a firmware image anymore.
Can someone please clarify this.
Thanks,
ggee
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
TT_Vert said:
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
Click to expand...
Click to collapse
Hello,
Yes, these are winrar files and I also use the winrar software. Sorry, I tend to use the word "zip" when talking about compressed file formats in general. Both files I am speaking about are winrar (Part1 and Part2). And each has an update.img file. How do I combine the files? Is there a special function within winrar?
BTW - do you have any idea about my original problem (google services stopped working)? Since I have not gotten a definitive answer, I was thinking about either doing a factory resetting, or just updating the firmware and mcu. I decided to update and that is why I'm stuck on these two "winrar" files, and how to combine them.
Thanks,
ggee
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Dave
TT_Vert said:
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Click to expand...
Click to collapse
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
There is no fix but myself and another person did try a bunch of different versions so search for it to find the most stable version.
gguevara said:
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
Click to expand...
Click to collapse
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
vinpee said:
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Click to expand...
Click to collapse
sciux said:
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello guys,
Yes. I was able to correct the problem.
All I did was re-flash the stock firmware rom. You can either re-flash your current version (if you have the update.img file for your head unit model). Or you can find the post in the Android Auto forum that lists most of the stock firmware roms. Make sure you select and download the correct one for your head unit type and model. I simply went back to the seller and asked them to send me the latest official stock firmware rom.
If you have certain apps and setting that you want to keep, make sure you make a back up before re-flashing the rom. Otherwise you will have to reinstall the apps and setting. Since I am basically keeping my head unit in a stock status (except for normal root), I just skipped the back up step and re-flashed the rom.
Extract the .zip or .rar of the firmware rom image. Then copy it to an SD card and insert it into you head unit. Reboot the head unit into recovery mode. Make sure to clear caches while you are in the recover mode, before re-flashing the rom. Then follow the menus for flashing the rom.
Later,
ggee