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
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
Alright so looks like I did something completely stupid and now my phone won't finish the boot process. I was looking at some remappings for the recent key to the menu option and from a post in the development section I found a thread in the International One X development forum that had re-odexed files so that the recent key stayed as the recent key and holding the home button became the menu key. Since they were re-odexed and I had root access I figured I would just manually replace them on my phone with Root Explorer...bad idea. The files were:
System/Framework/android.policy.odex
System/Usr/keylayout/qwerty.kl
After I moved them and reset permissions I rebooted my phone and now it goes through the first couple of boot animations but gets stuck on screen that displays beats audio at the bottom.
I really need to know what to do to fix this. When I plug my phone into my computer it recognizes it as a new \drive, but I don't have access to any of it (still says I need to mount). I also have the android SDk and adb installed if thats of any help. I would really like to not lose any data so hopefully thats possible.
Please help me with this if you have any knowledge of what to do.
Just one little quick update. Even though my computer won't let me access my One X as a drive, when I use command prompt and adb to check for adb devices my One X is listed.
Run the at&t ruu exe file, located in the Dev section.
tanman21 said:
Run the at&t ruu exe file, located in the Dev section.
Click to expand...
Click to collapse
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
ErikWithNoC said:
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
Click to expand...
Click to collapse
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
stnguyen09 said:
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
Click to expand...
Click to collapse
Thanks for your comment. I used the RUU and it kept my personal data so its not a big lose. Had to reinstall a few apps, but for most of them (games at least) my saved data was still there.
I tried a lot using adb and just couldn't get it to work. I don't the phone got far enough through the boot process for root access to be allowed. I was able to run the one click root tool while it was in its stuck boot phase, but it still wouldn't give me permission to modify the /system portion of the phone to be read/write.
All in all though this was a great learning experience. Prior to this happening I knew nothing about adb and now I know commands for pulling, pushing, remounting, shell commands, and other things. I also learned how to fix a softbrick (first one) and what RUU is.
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
Hello -
I have done weeks worth of research in my spare time before finally caving in and asking for help. I believe my situation irritatingly enough is different than typical no os corrupt sd card issues and I have not been able to find a solution here or on the www unless I am forgetting something simple. Here's why:
I am S-Off
I have super cid
I have access to bootloader
I have access to recovery which is TWRP 2.3.1 and I can access terminal command
My card WONT MOUNT (meaning no fixing permissions, no wiping external sdcard or side loading)
If I reboot system, it freezes at the initial boot screen image with the Viper logo and the red developer caution statement below it
Fastboot and ADB do not recognize my phone and I have used every one click, script, and trick on this website and others using different drivers, Android SDK and all the different drivers I can find. No Dice.
I DO HAVE AN HTC EVO 4G LTE that I htc dev unlocked, s-off, supercid etc on this very laptop (Windows 7) this week so I have a pretty good idea what what doesn't work in terms of drivers/scripts with my current laptop configuration.
I have used Ubuntu as an installed desktop and as a live cd. This is as close as I have been to having my phone recognized in adb or fastboot. I was using the SD FIX see here http://forum.xda-developers.com/showthread.php?t=1942519 (What I don't get is why that thread was closed. Makes no sense to me that since a particular version of TWRP becomes available, that it would render that fix obsolete when its obvious how many scenarios can come up in particular with these HTC One Xs and not everyone is going to have a specific version of recovery. Anyway... this brings me to Ubuntu. And this is as close as I have been to success with getting back into my sdcard so I can command prompt/flash my way outta this mess. It was the only version of the SD fix I could find which of course was for Mac, Linux or Ubuntu. In terminal when the script would initialize it comes back as "Fastboot: Permissions Denied" or something to that effect. That was last night.. or errr.. this morning and I'm determined to do this.
Has anyone heard anything about a way to create a virtual sd card using AVD in an old version of the SDK? From what I can see it looks fairly simple. What I have dug up sounds easy enough but not sure why I haven't come across it here or anywhere else or nobody else has mentioned it? However, I am not a dev and perhaps it being a couple years old, counter measures have been put in place by these phone companies... lol we'll see... Thank you so much for your time.
I have attached a snap shot of my bootloader screen. Yes, I know the screen is cracked lol
The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita
timmaaa said:
The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita
Click to expand...
Click to collapse
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk
bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
How did you wipe your sd card to begin with? If you wiped it in the bootloader with the factory restore option then this will currupt your sd and the only option is to connect to your pc or computer and under my computer right click the drive of your phone and format the sd card that way and this will restore your sd card to working order but you must have all the right drivers installed for your phone. Which installing HTC sync will install all the right drivers
Sent from my HTC One XL using xda app-developers app
I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP
31ken31 said:
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you mean literally plugging my phone into my pc...going into device manager, seeing if the sdcard is being picked up.. of course I have. I can freely go between recovery TWRP 2.3.1.0.0. and bootloader and I can even boot the system even tho there isn't an OS and get as far as the VIPER logo with the developers text below it in red. I have both windows and Ubuntu and I have tried everything. I have gone into what files and folders I do have on the phone and using terminal in recovery I have found all the proc contents in tact.. all the dev contents in tact and sub folders... all the usb folders and contents I believe are still there too. Including fastboot. HOWEVER, after days of trying every adb usb driver combination imaginable... including editing .inf files, and taking signature verification off win 7.. I still can't get my phone to be picked up when i plug it in. Every once in a while I will get the bell sound when I plug it in to a usb port but when I look in device manager nothing...but when I plug my evo 4g lte in its whamo... ding ding and no issues. As far as this phone goes...I see all the files and folders there but even even ran htc drivers in compatability mode with XP... nothing.
I am learning how to create virtual sdcard images and how I can potentially be able to attach it to a devices sdcard giving one the ability to transfer or delete files which could help some folks get back into their devices...Also, here is a really cool idea although still in its infancy and how you can mount an sdcard as an mtp device using a fuse filesystem based on libusb. https://github.com/hanwen/go-mtpfs So at this point there are options out there but only pretty heavy manipulation of data and extentions and stuff over my head lol..
dtonshel said:
I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP
Click to expand...
Click to collapse
Hey thanks. Yup. This is exactly what I need to do. It's just that last time I tried to run the sdfix script in terminal using ubuntu i ran into a permissions issue. fastboot-permission denied or something to that nature. Do you know what that means? Thanks tho I will give this a shot.