Related
Hi everyone,
I'm looking for some pointers on the path to 2.1 on my x10 Mini Pro, and hoping the wealth of knowledge between you all can set some things straight for me?
I'll apologise in advance if I ramble at all or don't make much sense... I've been browsing forums for hours and am suffering from mild cross-eyedness and slight brainfreeze.
The scenario;
I have an x10 mini pro, running 1.6, on Vodafone UK. Yes, the ONLY network that have not yet provided the 2.1 update for x10mp users. The phone was rooted with universal androot and also had astro file manager and titanium installed. For about three months I have had the 'starting download' hang problem in Market which I have not been able to fix. I hadn't really wasted much time on it as it was of little importance at the time however I now want to update some things and can't. Today I got annoyed and did a factory reset, hoping to resolve the problem. It didn't, and now I have a blank canvas of a phone.
I didn't back up before doing the reset as call logs and txts are of less importance that the files on my sd card, which remain untouched. I don't really have any other 'important' stuff on the phone right now.
I realised shortly after that I had a backup from December which I ran, as a last ditch attempt, this did not restore my lost applications, but did restore some user data. I noted that my root privileges and titanium were gone too
B*gger it, I thought, since I've lost all my data I may as well go for a generic NON-Vodafone installation of Android 2.1, and hopefully that will also fix the Market issue.
I've had a look on forums here and would like to run the 2.0.2.a.0.24 firmware posted by shivenjuneja.
I've downloaded this via pc, and understand I need to also install the flashtool and xrecovery, both of which I have downloaded and saved in a folder on my laptop.
Now remember, market was not an option so I've downloaded universal androot via pc too and have saved this to the root of the SD card.
With my primitive blank phone, I am unable to browse to it without a file manager, so now I need to download Astro File Manager again.
I decide to have a probably fruitless attempt of doing this via the market (because saving it on the SD card is pointless as I need it installed in order to browse to it!) and much to my amazement, it's worked!! Woohoo Market is working again! But hell, I've still lost everything on my phone so I'll perservere with my android update, thank you very much.
Ok, now while waiting for Astro to download, I remember that I've also read on the forum that the upgrade to 2.1 is likely to be stuck in a booting loop if I upgrade with user data on the phone. If I do a factory restore I will lose my file manager and root privileges that I will shortly be installing, right?
So now, at this hour, I'm wondering exactly what order I need to do everything in to get 2.1 on my phone.
To install 2.1 I need to install the flash tool and xrecovery. To install those I need root, to root I need Astro and before doing any of this I need a phone that has no user data on it.
D4mn you Vodafone.
Could anyone advise the best method to do all of the above i.e in what order to do it all, or point out if there is anything obvious I haven't accounted for.
I don't usually have a problem with this sort of thing, hopefully it will look clearer tomorrow!
Thanks in advance
K
Also, does registering your google login to use the Market count as 'user data' when you upgrade? I ask as I may need to download and install Astro again from the market, if it's still working after another reset?
A lot of view and no replies? I could really use your advice guys if anyone could oblige...
From further reading I understand that I need busybox to install xrecovery and that I also need to be on 2.1 054 as xrecovery won't install on 1.6?
Is this correct?
It sounded so simple initially to flash from 1.6 to the latest version of 2.1, whereas now I need this to install that, need to be on the later version to install the app I need to use to flash to the next version up, and have to have a bunch of other apps and tools installed in order to the able to run anything!
All I want is a rooted 2.1 with all the network and SE bundled crap removed, so I can start putting my phone back to how I bl00dy want it with the apps I choose!
I hate you Vodafone. IhateyouIhateyouIhaveyouIhateyou
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
If only you have working CWM installed. You could just flash this Superuser3.0.7.
Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.
It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.
Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!
Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..
There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.
Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.
yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face
To whom ever can help out, I have a Galaxy Tab 2 7.0, and cannot seem to get my problem resolved by myself. I have somehow inadvertently managed to install an update.zip that had or had no relations to this particular OS of this particular model of android.
My problem is that I wanted to be able to, migrate my apps to the external SdCard or extSdCard, and I think I used an update.zip designed for the cellphone HTC Evo 4g. Not realizing that I will be later unable to use the restore feature from a previous backup I had made using CWM 6.0.1.0 to recover from my inadvertent mistake (not to comfortable making a backup, and thinking I can restore properly anymore, like I can on my cellphone that I am spoiled with).
Silly of me to think I could use an update.zip designed for another type of device such as the HTC Evo 4g, but… (anyway my bad what was I thinking…?). The update.zip, by the way is "dtapps2sd-2.7.5.2-signed", like I mentioned this is clearly designed for the HTC Evo 4g, and not for the Samsung GT2 7.0.
The problem I experience now is not complete lose of my GT2 7.0 device I can still install and change out OS through the CWM-Recovery and install apps through the Android Market. I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Now my question is, how is-it possible to resolve this issue. I have tried to complete a fresh install of the OS, CWM-Recovery, and also attempted to wipe everything possible that the recovery will allow, but I am not expecting much, as I cannot even get the backup and restore feature to work efficiently enough to provide me with what I need it to do…
I have provided this post with a download of the update.zip I used as well as the version of the OS I have provided my Samsung GT2 7.0. If anyone can shine some insight on what direction I should attempt to do to resolve this issue I would be more that interested to take a look at what I could use to correct this error of mine…
-Samsung GT2 7.0 - OS (Use the Download link above the Rosewell signature)
http://forum.xda-developers.com/showthread.php?t=1784318
-dtapps2sd-2.7.5.2-signed
http://www.mediafire.com/?7jpc5oudzt6o76p
I might be comfortable to ADB Shell into my device to make changes, or if one was able provide me an update.zip/script that would be great. Also is there a better recovery out there than the ClockWorkRecovery.
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Sent from my GT-I9300 using xda app-developers app
Mohamedselim said:
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Click to expand...
Click to collapse
Mohamedselim, Thanks...
Will look into this..., any links by the way in regards to the "fresh firmware with a pit file"...?
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
imnuts said:
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
Click to expand...
Click to collapse
Yeap...!, I have tried this already, have had no promising results...
This is the only compatible version of a .pit file...;
http://forum.xda-developers.com/showthread.php?t=1642744
Can anyone provide me another one for the GT-p3113...?
Just checking in..., and wondering if anyone has a solution for this...?
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
RomsWell said:
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
Click to expand...
Click to collapse
MultipleMonomials said:
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
Click to expand...
Click to collapse
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Ok, so I was successful in taking RomsWell and MultipleMonomials advice, and was able to return my device back to "Normal" state, including "Stock Recovery". But I still have the original problem as in my request I asked in my first post...
I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Click to expand...
Click to collapse
I think now, if I cannot get a sizable remedy..., is just to try and send it in Samsung so they can take a look at it...
Any suggestions...?
FYI; I have also tried connecting to Kies, but due to the inability to posses a "MTP" (Media Transfer Protocol), is the reason I cannot connect to my SdCard & extSdCard. I can "PTP" (Picture Transfer Protocol) into it, using "adb shell", but not using "MTP"...
So I do not know how much "MTP" has to do with this relationship of the other three items that I mentioned in my bullet list in my quote, but...
Anyway, I don't know what I am trying to say, but thank you two, for getting me this far...!
grassy-sneakers said:
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Click to expand...
Click to collapse
Did you try formatting internal storage in CWM?
MultipleMonomials said:
Did you try formatting internal storage in CWM?
Click to expand...
Click to collapse
I am not quite confident on how much this will work. As I have tried this multiple times to wipe "Wipe Factory/Data", "Wipe Cache", including all the partitions under the "Advance" section found in CWM Recovery. Even using TWRP Recovery.
Per this post; I just attempted to flash a "Stock Rom", but not before doing a factory/data, cache wipe using "Stock Recovery", including after a successful install...
No luck, the same problem still exist as above...
Ok, this was all just the rudest experience I put my self threw. As I have an HTC Evo 4g - cellphone and have become comfortable with installing ROM's, Kernels, and Updates.zips, as well as, other modification. All threw the Recovery designed for this particular device, and don't get me wrong there has been a couple of times. Maybe more than a couple, more like a few times I have installed incompatible downloads I find in the XDA forums. Which makes this screw up, difficult form me to know that as long as you can get into a Download/Bootloader or a modified Recovery designed for a particular device that was successful flashed correctly. Well the screw up are easily redeemed/recoverable.
So, to make a long story short. After having called Samsung Customer Care (the 1-800-SAMSUNG) number, it seems to have been a External SdCard getting in my way from having been real short from sending my Tab off to the repair department (where ever it is...). I in fact already had it in an envelope, all I needed was an address to send it to. Anyway the nice person on the other side of the phone requested that I remove my External SdCard, and confirm that I was able to get into my "Storage" tab under my settings. Well after success getting this option back, I then made the suggestion that maybe my Eternal SdCard is corrupt or incorrectly formatted. She then agreed maybe this is the case. After ending the phone call. I quickly restarted my Tab, again only to find out that I was no longer receiving the error messages like mentioned above, which is great, because after multiple flashes of "Stock Roms w/Stock Recovery", and forcing myself to believe that it was a system install error. It in fact the External SdCard in place preventing me from throwing my Tab against the wall / in the mail to Samsung Repair Center...
"Man what an ordeal...!!!"
Thanks to all that helped with the suggestions, as to what direction I most defiantly tried.
I am now in the process, since I am living back in Stock mode. To receive an OTA (Over The Air) Update, and am still in the process of seeing if this thing still possess any residual silent errors...
I will keep you posted.
If not, well it off to happy rooting for me...!!!
That is it, my problem is resolved. Damnedest thing this problem of mine, it seems the only thing I screwed up was the micro SdCard. to the point it was the cause of all the error I received when I started up the device, as well as when I attempted to access my storage through me settings options...!!!
Now re-rooted, and a happy camper, Cheers...!
I just bought a Chinese phablet and was excited about the good deal I got for $250. The phone (Ginwave G503) arrived on Monday and I was disappointed to learn that the retailer did not install google apps as they do for some of their chinese phones. I figured I would just look around the internet and just install them myself. This proved to be much harder than I thought. I came across a German forum for Chinese phones and installed the google apps package that one user had uploaded to my system/app/ folder and it didn't work. I was told in the forum that It might not fork because I used some old files for Android 2.3. So they pointed me to a thread with a newer version and I deleted everything I had copied into the system/app/ folder and then replaced them with the new files. Then even less worked. My phone didn't ring anymore, sound didnt work, and the play store wouldn't even start at all anymore (it gave me a download manager stopped error or something like that). So then I figured out that those files were probably for Android 4.1 and my phone has Android 4.0.4. So then I found a package on rootzwiki for 4.0.4. I again deleted all the stuff i had put in the system/app/ folder and did a factory reset.
When I restarted the phone I was not able to install my ES File Explorer from my SD Card again. When I click on it it asked me if I want to install to phone or SD card, no matter what i select it says "X Application not installed". So I went into the chinese app store that was on the phone (called 360 followed by some chinese symbols) and actually found ES File Explorer on there. But when I tried to install it from ther, it downloaded and then gave me the same error. No matter what apps I try to install, I get this error now. What can I do? Did I break my phone?
If I did end up breaking the Rom and can't find a replacement rom for this phone online is there like a universal android version that can be installed on any phone? Would there be any way I could somehow play a new Android on my phone without having to know how to program something
Wow.. This forum is extraordinarily worthless
u should think before bought a phone/tablet from china,dude...
agstwn21 said:
u should think before bought a phone/tablet from china,dude...
Click to expand...
Click to collapse
At this point, it's not where he bought it from, it's what he did to it. Sorry to say OP, but you're very far up ****'s creek.
If you can't get ahold of the factory ROM and no one has made an aftermarket ROM for your device, you're going to have to learn to compile yourself. I wouldn't advise you do that, however. Based on your original post, you don't do any research before mindlessly flashing any old thing from the internet to your device.
If I'm coming off as a ****, that's because you want to call xda worthless when you clearly have your head up your ass. Someone might've tried helping you before you insulted the forums.
The only thing I can suggest now is using recovery mode to factory reset your device. This might only work if you still have your factory recovery; you never mentioned that you flashed a new one and I can't imagine you flashed anything to your phone without a custom one... But again, reading your OP it sounds like you just flash things all willy-nilly.
BTW, your device didn't have gapps because it's probably not approved by Google to access the play store. No access to play store = no gapps.
stefan0325 said:
I just bought a Chinese phablet and was excited about the good deal I got for $250. The phone (Ginwave G503) arrived on Monday and I was disappointed to learn that the retailer did not install google apps as they do for some of their chinese phones. I figured I would just look around the internet and just install them myself. This proved to be much harder than I thought. I came across a German forum for Chinese phones and installed the google apps package that one user had uploaded to my system/app/ folder and it didn't work. I was told in the forum that It might not fork because I used some old files for Android 2.3. So they pointed me to a thread with a newer version and I deleted everything I had copied into the system/app/ folder and then replaced them with the new files. Then even less worked. My phone didn't ring anymore, sound didnt work, and the play store wouldn't even start at all anymore (it gave me a download manager stopped error or something like that). So then I figured out that those files were probably for Android 4.1 and my phone has Android 4.0.4. So then I found a package on rootzwiki for 4.0.4. I again deleted all the stuff i had put in the system/app/ folder and did a factory reset.
When I restarted the phone I was not able to install my ES File Explorer from my SD Card again. When I click on it it asked me if I want to install to phone or SD card, no matter what i select it says "X Application not installed". So I went into the chinese app store that was on the phone (called 360 followed by some chinese symbols) and actually found ES File Explorer on there. But when I tried to install it from ther, it downloaded and then gave me the same error. No matter what apps I try to install, I get this error now. What can I do? Did I break my phone?
Click to expand...
Click to collapse
Before anyone ever uses a new device thee shall make a Rom Backup; just in case... (at least i would do this).
Anyway; i don't understand why you've put the *.apk file inside the \System\apps folder...
You should try (have tried) to install Android SDK (If you've not installed already); and install the *.apk through adb.
Check these:
http://www.xda-developers.com/xda-tv-2/pro-tip-number-4-installing-applications-using-adb-xda-tv/
[and]
http://forum.xda-developers.com/showthread.php?t=879701
I don't believe that the operating system blocks "Google Apps / Play Store". Either way i'm not going to say that it is impossible. But it doesn't make much sense.
But like "rockingondrums" said; If your device doesn't have have "gapps"; it's probably because it's not approved by Google to access the play store.
No access to Play Store = No "gapps"...
(Never seen that happening though)
Also you didn't need to root your device for that. "Play Store" doesn't require Root Permissions...
In order to help you (and help yourself up); I've done research for you (just because i understand your situation).
1st of all you shouldn't insult XDA Forum. This Forum has loads of information scattered around. Just dig like everyone else... There's probably the info you need. Yes it may take hours, day or months if you have no idea of what you're messing with. If the info is there, just don't expect people to do the research for you...
But, XDA is far from being "worthless". I've lost the count of how many times it helped me; and what i've learned is priceless. (And i still don't know everything i want to know ^^)
2nd; [Get your Device Working]
If you haven't messed up much... (Like flashing a wrong Rom)
Use "Recovery Mode" to "Factory Reset" your device.
I'm not sure if the method i'm about to show, works for every device or for your device; but it's a good example.
On my device i would do:
- Turn off the device;
- Press and hold in the following order: Camera Button; Then Volume - and then Power Button; let it vibrate 3 times; and then release the buttons.
In other words; this will "Reinstall / Reset" your system. You'll see in your screen if it works. Just dont turn off your device in any way while it's executing that operation.
Note: It may be different on your device. If it is... You have to search for a different method that will work for you.
Search this forum, Google, or Ginwave Website (if it has one...)
After this; i recommend you to do some search and learn on how to backup & restore your device.
Search XDA Forum. Grab some examples, compare the info you've got; then backup that device.
3rd; If you've flashed a wrong Rom; then you really have to compile your own, as i also couldn't find a Stock or Custom Rom for your device.
Note: If you (ever) find a Rom for your device; remember that it has to be A ROM FOR YOUR DEVICE! AND NOT SOME OTHER. Otherwise you'll probably end with a dead device...
And that would be sad and wasted money.
Here's a good example on how to flash a Rom and a good place to start with:
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Do some more reasearch; and now don't ever say that XDA is worthless.
P.S - Experienced People aren't here every day and every hour just for you... Sometimes you've got to wait and pray for a god answer (lol - so true...).
I hope this helps solving your problem.
Best Regards;
stefan0325 said:
If I did end up breaking the Rom and can't find a replacement rom for this phone online is there like a universal android version that can be installed on any phone? Would there be any way I could somehow play a new Android on my phone without having to know how to program something
Click to expand...
Click to collapse
Hi,Did you have chance to find ROM-replacement? D you have any ROM image for this Ginwave GnoteM?
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Bumping in desperation here! Can anyone just paste in their build.prop? I'm on UVLJ1 (haven't had time to do the latest update due to root).
hmm... you should be able to go into download mode and flash the stock rom to recover the phone i think?
I think this is the answer. Flashing stock will give you what you need, it can be done through CWM (gee one's flashable zip for instance).
Wipe system/data through the format menu.
I wish I knew what a build.prop was.
installed it and rebooted my Samsung Relay and the screen went black. I pressed the power button and nothing happened.
The phone is now officially a paperweight. Also I had root privileges.
Can you help me please, I do not know what to do?:crying:
tacoman3148 said:
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Click to expand...
Click to collapse
I'm not very good at this also,but...Can you connect your phone to your computer and mount your phone from cwm and get the build.prop file that way?Or maybe do a factory reset?