Related
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
Hey guys, unfortunately my first post here will be under messy circumstances but I've managed to mess my phone up pretty bad.
I have an AT&T HTC One X. I'm running on Windows 7 64bit, all drivers updated, permissions set, etc. etc.
I was supposed to be flashing Cyanogenmod 10 when I ran into an error in that was in the actual zip file. Prior to installing TWRP I had Clockwork mod installed. I flashed TWRP onto my phone & have been using that since.
My noob hiccup was instead of deleting just the zip file I managed to wipe the entire sd card, backups included (I'm an idiot, I know).
Now I don't have an os and cannot run in debugging mode in order to get adb to function properly. When I adb I cannot access /system/ nor /sdcard/. I can only access /data/ & of course installing CM10 through that directory has resulted in more fails.
Please tell me there's a way to salvage this. Thanks in advance...
Notorio said:
Hey guys, unfortunately my first post here will be under messy circumstances but I've managed to mess my phone up pretty bad.
I have an AT&T HTC One X. I'm running on Windows 7 64bit, all drivers updated, permissions set, etc. etc.
I was supposed to be flashing Cyanogenmod 10 when I ran into an error in that was in the actual zip file. Prior to installing TWRP I had Clockwork mod installed. I flashed TWRP onto my phone & have been using that since.
My noob hiccup was instead of deleting just the zip file I managed to wipe the entire sd card, backups included (I'm an idiot, I know).
Now I don't have an os and cannot run in debugging mode in order to get adb to function properly. When I adb I cannot access /system/ nor /sdcard/. I can only access /data/ & of course installing CM10 through that directory has resulted in more fails.
Please tell me there's a way to salvage this. Thanks in advance...
Click to expand...
Click to collapse
I would just relock downloader through fastboot and run the ruu and go again...u can't mount through recovery?
omario8484 said:
I would just relock downloader through fastboot and run the ruu and go again...u can't mount through recovery?
Click to expand...
Click to collapse
Well I just fixed the sd card issue but now for whatever reason /system won't mount. do i need to install superuser first or something?
copy rom to sdcard and flash
DvineLord said:
copy rom to sdcard and flash
Click to expand...
Click to collapse
Tried 5 times now, same error every time:
E:Unable to mount '/system' (tw mount)
Error flashing zip '/sdcard/cm10_endeavoru-ota-eng-noeri-019'
*Shrugs, sorry for being a pain. Not sure what's left after this...
wrong phone this is the evita forum. you dont have a endeavoru.
DvineLord said:
wrong phone this is the evita forum. you dont have a endeavoru.
Click to expand...
Click to collapse
Ah, I was flashing the rom for the global one x not xl *facepalms
Thanks, it seems to be in working order now...
Notorio said:
Ah, I was flashing the rom for the global one x not xl *facepalms
Thanks, it seems to be in working order now...
Click to expand...
Click to collapse
Stick to ROMs in this specific (AT&T One X) forum, and you won't go wrong again (at least not in that way).
Or check out my Index thread to see the ROMs in an organized list: http://forum.xda-developers.com/showthread.php?t=1671237
So I've had a bit of bad luck mixed with poor timing. Here's the run down.
I have an Asus Transformer TF101 which was running the stock rom.
I rooted my Tablet a few weeks back without any problem. Things were great. Then, I tried to upgrade to Jelly Bean from ICS using Team EOS (I followed these 2 threads mainly, http://www.transformerforums.com/fo...ficial-faq-teameos-4-android-4-2-x-tf101.html & http://forum.xda-developers.com/showthread.php?t=2063406)
I put the ROM and all the files needed onto my micro SD card.
I booted into TWRP and followed the instructions. Things seemed to have gone great. When I rebooted, I saw the new splash Logo upon bootup and awaited it to do it's thing. It never did. I let it run for an hour and it never made it into the OS.
I rebooted, went back into TWRP with plans to redo the procedure, only now the microSD card slot is not being picked up. I tried multiple micro SDs of different sizes (1GB-32GB), I've tried inserting before boot up, inserting after bootup, inserting after bootup and then rebooting the device. No luck.
I bought a USB adapter that plugs in where the power plug goes, hoping I could run the files off a USB flash drive. or a micro SD card within a USB flash drive. No luck.
I am running Teamwin's TWRP 2.3.2.3
My backup from nandroid happens to be on my microSD card too. So I can't use it to recover the old OS either.
TL;DR: Micro-SD card stopped working after a failed attempt to flash an OS. OS and backups are on the microSD card. PC recognizes the device but won't let my access the hard drive.
Does anyone have any suggestions on what to try?
Thanks!
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.zip /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
frederuco said:
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.blob /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
Click to expand...
Click to collapse
Thanks so much frederuco! I will be trying this later today and will update this post as soon as I do.
I just wanted to say good luck, and we are all counting on you.
Almost there!
frederuco said:
I just wanted to say good luck, and we are all counting on you.
Click to expand...
Click to collapse
The update! I followed your instructions, while on the cmd prompt, I got no confirmation that the files were moved, but they appear to be on the device now. When I go to reinstall through TWRP, the flashing fails. I am going to do some digging around the forum to see what solutions there may be, but if you (or anyone reading) has an idea, do tell.
I will be sure to update this thread if I fix it, including the solution I found.
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
frederuco said:
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
Click to expand...
Click to collapse
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
db1984 said:
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
Click to expand...
Click to collapse
Yes, that would do it!
frederuco said:
Yes, that would do it!
Click to expand...
Click to collapse
Alright, so I got past the logo, Android upgraded all the Apps and is now "Starting apps" .. it's been here for about 10 minutes. I think I can take it from here.
The ADB push was the solution.
Waited another 15 minutes. Nothing happened (stayed at Starting apps)
Restarted device. Booted up as it should and I am now all set. Thanks again!
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
bsoplinger said:
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
db1984 said:
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
Click to expand...
Click to collapse
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
frederuco said:
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
Click to expand...
Click to collapse
Nope, nothing was in the dock. I actually didn't have the keyboard dock plugged in during the "crisis"- I did try getting TWRP to read a card from it once, that was about it.
I read somewhere else, that once you let the battery die on it's own, and recharge, the "never powers off" issue goes away for many people (haven't seen one specifically relating to EOS on TF101, but the other symptoms were spot on)
I'll be checking out the Google Now tweak in a bit.
I'd been running a custom kernel on my Transformer since about a week or two after I bought it at a Black Friday sale simply because it would keep running on the stock ICS ROM. Changed to KAT kernel when I moved to EOS. You might want to consider a custom kernel if you have a Transformer that suffers from the reboot issue like mine did.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
db1984 said:
-snip-
Click to expand...
Click to collapse
You may want to try doing a full format in TWRP, and using the superwipe full scripe from the ARHD thread, then formatting again, wipe cache and dalvik, push the latest EOS, KATkernel and Gapps to the device, wipe dalvik cache and cache, flash EOS, wipe dalvik cache and cache, boot into the ROM, boot back into twrp, wipe cache and dalvik, flash Gapps, wipe cache and dalvik, boot into the ROM, boot back into TWRP, wipe cache and dalvik, flash KATkernel, wipe cache and dalvik, cold-boot into the ROM.
That should set you up with the most stable your tf is going to get, it seems erroneous and like a ton of work, but I strongly believe in doing this whenever I flash a new rom setup, I've gotten to doing it in about 10 minutes now.
Just an update.
EOS's random reboots were getting pretty bad. Happened a few times while I was working on a few docs (thankfully Evernote had autosaved)
I also noticed when the screen would go off, it would eventually turn back on and attempt to reboot, getting stuck at the Asus loading splash (pre EOS logo). I ended up re-flashing with my newly gained leet adb skills (thanks frederuco ) and went with Cyanogenmod 10. I've only had 1 random reboot since and Google Now seems to work 90% of the time.
I'm sure there are some more things I can do to fine-tune it, still getting a hang of everything.
Thanks again for everyone who's helped.
Hi guys
It has been a long time since my phone has been this bad.
So last night I go to charge my phone because I had ZERO battery. So I turned it on and then plugged it in. The phone booted fine but then I noticed that the screen was not shutting off. I even tried hitting the "Go to sleep" button from the pull down menu and nothing happened. I also realized the phone was not loading my calendar. When I went into the file manager it didn't show SDCARD 1 or 2.
I decided to clear the memory (dalvik + cache) = SAME PROBLEM
I did a factory restore = same problem
Finally I cleared the system = now i have no OPERATING SYSTEM ON THE PHONE
I went to the external sd card and tried to install the latest version of OMNI....IT SAYS IT CANT READ FROM THE SD CARD.
I also tried to copy the file from external sd to internal sd card and it says FAILED
I don't' know what to do...
I am using Team Win Recovery Project 2.6.3.0
I have the latest omni rom on my external sd card. I can see it but install fails.
Please help :crying:
mfisher0 said:
Hi guys
It has been a long time since my phone has been this bad.
So last night I go to charge my phone because I had ZERO battery. So I turned it on and then plugged it in. The phone booted fine but then I noticed that the screen was not shutting off. I even tried hitting the "Go to sleep" button from the pull down menu and nothing happened. I also realized the phone was not loading my calendar. When I went into the file manager it didn't show SDCARD 1 or 2.
I decided to clear the memory (dalvik + cache) = SAME PROBLEM
I did a factory restore = same problem
Finally I cleared the system = now i have no OPERATING SYSTEM ON THE PHONE
I went to the external sd card and tried to install the latest version of OMNI....IT SAYS IT CANT READ FROM THE SD CARD.
I also tried to copy the file from external sd to internal sd card and it says FAILED
I don't' know what to do...
I am using Team Win Recovery Project 2.6.3.0
I have the latest omni rom on my external sd card. I can see it but install fails.
Please help :crying:
Click to expand...
Click to collapse
Calm down dear. Same happened with me. I formatted /system and find that I don't have any operating system in my mobile.
Just pluggin your mobile in recovery mode to your PC. transfer the file-> Flash the ROM-> Gapps -> BINGO..
BTW, wrong area for creating a thread.
Don't worry. Do what D™ said.
Alternatively you can use "adb sideload" method. I used it once with Philz recovery. In sideload method, you won't need to copy the file in Sdcard. File existing on pc can be directly flashed. This would help if you still face problems copying file to Sdcard. Search it on google. You will find steps for it.
A bit more clear please...
D™ said:
Calm down dear. Same happened with me. I formatted /system and find that I don't have any operating system in my mobile.
Just pluggin your mobile in recovery mode to your PC. transfer the file-> Flash the ROM-> Gapps -> BINGO..
BTW, wrong area for creating a thread.
Click to expand...
Click to collapse
Hey
Ok I am a bit calmer knowing I didn't brick my phone or anything...
But when I connect my phone to my computer I know it is connected (I see GTi9103 in device manager with an "!" ) but I cant transfer files.
Could someone provide a link to the adb method or maybe give a bit more advice on this problem..
Thank you guys!
mfisher0 said:
Hey
Ok I am a bit calmer knowing I didn't brick my phone or anything...
But when I connect my phone to my computer I know it is connected (I see GTi9103 in device manager with an "!" ) but I cant transfer files.
Could someone provide a link to the adb method or maybe give a bit more advice on this problem..
Thank you guys!
Click to expand...
Click to collapse
It must installed drivers.. If u cant access the storage, just flash ics via odin and further known actions.
Sent Using my MOTO© G® from Tapatalk Pro - D™
Thanks dude! I will give it a try and post a response! It was just so strange that I couldn't see any of the drives (sdcard 1 or 2) in filemanager. I guess something must have got corrupted? Right now I am trying to push from adb method mentioned from Nikhil.
I am following this procedure.
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
PS. the android SDK is massive!
ADB FAIL
ADB IS WAY TOO complicated for me right at this moment (actually exhausted).
********Can someone provide me with a ICS download link? *******************
I'm going to try out the ODIN method
http://forum.xda-developers.com/showthread.php?t=1406664
again thanks to ALL who are constantly helping out!
mfisher0 said:
ADB IS WAY TOO complicated for me right at this moment (actually exhausted).
********Can someone provide me with a ICS download link? *******************
I'm going to try out the ODIN method
http://forum.xda-developers.com/showthread.php?t=1406664
again thanks to ALL who are constantly helping out!
Click to expand...
Click to collapse
Download Stock Indian ICS
Btw, adb sideload method is as follows.
0. Install adb for windows (assuming you have windows). (There shouldn't be any driver missing)
1. Enter into sideload mode in recovery
2. Open cmd in computer with the directory in which zip file is kept. (shift + right click -> open command prompt here would do)
3. Enter adb sideload xyz.zip
Thats it.
I've tried it with TWRP recovery in my friend's phone. It didnt work. But When I tried with Philz recovery, It worked well.
Anyway, if you are finding it complicated, flash stock ics.
Edit : Did you try "mount usb storage" in recovery? because it is required to do. else computer won't recognize your device.
success!
OK so I successfully flashed via ODIN....Can I directly flash omni now? I am assuming yes...Can I flash it through ODIN?
Also can you recommend any good versions of ICS? It is really quite a bit faster than omni...
AGAIN thank you all
mfisher0 said:
OK so I successfully flashed via ODIN....Can I directly flash omni now? I am assuming yes...Can I flash it through ODIN?
Also can you recommend any good versions of ICS? It is really quite a bit faster than omni...
AGAIN thank you all
Click to expand...
Click to collapse
Omni is best until now.
you can't flash omni via odin. Flash Philz or TWRP first and then flash omni.
Lv5 ZCLPD is best ICS Rom. But I would choose Omni over Lv5,
reinstall twrp?
Nikhil said:
Omni is best until now.
you can't flash omni via odin. Flash Philz or TWRP first and then flash omni.
Lv5 ZCLPD is best ICS Rom. But I would choose Omni over Lv5,
Click to expand...
Click to collapse
Do I need to reinstall TWRP>??
mfisher0 said:
Do I need to reinstall TWRP>??
Click to expand...
Click to collapse
Reinstall!
Not if you already installed it.
Read OP of discussion thread. Instructions are there. You will find everything you need.
ICS will faster for few days and then it slow down.. hang.. GB is best for our device..
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
temme how to recover the system folder. i have a system folder on my desktop. help me. my phone isnt turing on
If you can get into fastboot and recover you can restore your phone. You just need a complete ROM, and restore it with mfastboot method.
It doesn't matter if you wiped system, you can do that in TWRP, if you reboot it won't boot into the OS (obviously) but go into fastboot mode.
Download mfastboot, a ROM image, and go through the command lines. There is a FAQ on how to restore.
felmaster said:
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
Click to expand...
Click to collapse
Also TWRP/CWM has support for adb, u just need to install the drivers manually. Then you can push whatever you want.
Of course you can try restoring stock as suggested above.
How did u fixed it? :/
As a last resort there is always OTG (this thing has OTG support right?). Life was so much simpler when you could just put your sd card into a card reader and put your zip on there. A quick google search makes me think its got support, but who knows