Related
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
EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...
I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!
Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.
Got it after several tries
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2
So,
I'm a dumbass and accidentally flashed an "update package" rather than a full ROM. I can not get past the "HTC ONE" white screen now..I have full access to recovery and bootloader, but can't boot the phone to mount as "Disk Drive" so I have no way to put the .zip file I need on the SD Card. Is there a way to put the correct .zip...even a stock ROM onto the SD Card without the phone being able to boot? I looked around and couldn't find anything.
Thank you so much.
-Brian
Boot the phone into recovery, go to mounts and storage, mount system. In adb push the file to /sdcard/
Sent from my HTC VLE_U using xda premium
If you need more details, let me know
Sent from my HTC VLE_U using xda premium
strker45 said:
If you need more details, let me know
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Sent you a PM. Thank you
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hi, I'm working on exactly the same thing. I am only about 20 hours in and have learned quite a bit, but not having an SD card you can slip into a PC card slot is a major challenge. I have managed to get recovery back on the phone, and am successfully connected via fastboot. I can't figure out the ADB shell...I've installed SDK manager and have tried to enter the ADB shell, but cannot. Keep getting error messages. WHen I attempt to flash a rom via fastboot, the process starts, but then quits with the error that my media does not include android-info.txt or android-product.txt. I have tried every tmo ROM available, and the Nandroid back up. It is a paper weight? Thanks to anyone who can shed some light!
rjsvoon said:
Hi, I'm working on exactly the same thing. I am only about 20 hours in and have learned quite a bit, but not having an SD card you can slip into a PC card slot is a major challenge. I have managed to get recovery back on the phone, and am successfully connected via fastboot. I can't figure out the ADB shell...I've installed SDK manager and have tried to enter the ADB shell, but cannot. Keep getting error messages. WHen I attempt to flash a rom via fastboot, the process starts, but then quits with the error that my media does not include android-info.txt or android-product.txt. I have tried every tmo ROM available, and the Nandroid back up. It is a paper weight? Thanks to anyone who can shed some light!
Click to expand...
Click to collapse
That's not how to flash roms, perhaps that's why. If you don't understand adb you really should not be rooting or unlocking anything until you have a better understanding of the tools you have available. Otherwise you end up in here asking if your phone is bricked when really you just have no idea what you're doing in the first place. Flash recovery in fastboot, then flash the rom from recovery.
Sent from my HTC One S using XDA
Yea I figured it out..I had a recovery working though.
With regards to rsvjoon,
As stoneyjonez said...you need to flash a recovery (Say CWM Touch) using fastboot...something along the lines of "fastboot flash recovery recoveryimagefilehere.img" and then reboot into recovery...etc etc.
I followed this this step-by-step process exactly and got it to work, I recommend the same.
Cheers
hello...i as well need a step by step about pushing the rom to /sdcard/ in adb....if you could pm me that i would be thankful!
Thanks...and you're right. But I have successfully flashed CWM recovery...I just can't get anything on the phone to flash. Fastboot starts the process but ultimately I get an error with each rom I try that it can't continue because I'm issing those two text files. So anyway, your point is well taken. In the past, once I had recovery, I'd just slip the micro SD card into my computer and pop a rom on it. totally different deal without that capability.
---------- Post added at 07:59 AM ---------- Previous post was at 07:57 AM ----------
brwetz said:
Yea I figured it out..I had a recovery working though.
With regards to rsvjoon,
As stoneyjonez said...you need to flash a recovery (Say CWM Touch) using fastboot...something along the lines of "fastboot flash recovery recoveryimagefilehere.img" and then reboot into recovery...etc etc.
I followed this this step-by-step process exactly and got it to work, I recommend the same.
Cheers
Click to expand...
Click to collapse
Thanks brwetz. That is exactly the process I followed when I originally rooted my phone...and everything was swell. I fongooled things when I flashed a custom rom (which also worked just fine) and then decided to restore my Nandroid. for whatever reason, that process left me in recovery with nothing on the SD card to flash back.
Thanks again for the response.
rjsvoon said:
Thanks...and you're right. But I have successfully flashed CWM recovery...I just can't get anything on the phone to flash. Fastboot starts the process but ultimately I get an error with each rom I try that it can't continue because I'm issing those two text files. So anyway, your point is well taken. In the past, once I had recovery, I'd just slip the micro SD card into my computer and pop a rom on it. totally different deal without that capability.
Thanks brwetz. That is exactly the process I followed when I originally rooted my phone...and everything was swell. I fongooled things when I flashed a custom rom (which also worked just fine) and then decided to restore my Nandroid. for whatever reason, that process left me in recovery with nothing on the SD card to flash back.
Thanks again for the response.
Click to expand...
Click to collapse
What *I did* to put a .zip file on my phone without being able to boot it up was this:
-Go into Recovery -> Mounts and Storage.
-Plug your phone into your computer using USB cable
-Make sure it says "Unmount /sdcard/" and "Unmount /system/". If they do not say that, just press them (they are toggles)
-Make sure the ROM.zip file is in the same directory as your AndroidSDK/adb (for example, mine is C:\AndroidASK\)
-Go into command prompt and type "cd c:\whereveryouradbislocated"
-Once you are in your AndroidSDK (adb) directory, type "adb push romname.zip /sdcard/romname.zip
-Unplug phone from computer, close command prompt
-Go back in Recovery to main menu and do a factory reset/wipe cache partition/wipe dalvik cache (I can explain those more if needbe)
-Again go back to Recovery Main Menu -> Install Zip from SD Card -> Choose file from SD Card -> Select the romname.zip file you just pushed from your computer and install that .zip
-Reboot phone, be patient as it will take a minute to completely boot up.
-_-_-_-_-_-_-_-_-_-_-_-
If you need further instructions, please PM me.
All of this information deserves much thanks to strker45 and doktartaru for their endless help getting me through the process.
EDIT:
Should I make a walkthrough thread about this just incase anyone else has this problem?
brwetz said:
What *I did* to put a .zip file on my phone without being able to boot it up was this:
-Go into Recovery -> Mounts and Storage.
-Plug your phone into your computer using USB cable
-Make sure it says "Unmount /sdcard/" and "Unmount /system/". If they do not say that, just press them (they are toggles)
-Make sure the ROM.zip file is in the same directory as your AndroidSDK/adb (for example, mine is C:\AndroidASK\)
-Go into command prompt and type "cd c:\whereveryouradbislocated"
-Once you are in your AndroidSDK (adb) directory, type "adb push romname.zip /sdcard/romname.zip
-Unplug phone from computer, close command prompt
-Go back in Recovery to main menu and do a factory reset/wipe cache partition/wipe dalvik cache (I can explain those more if needbe)
-Again go back to Recovery Main Menu -> Install Zip from SD Card -> Choose file from SD Card -> Select the romname.zip file you just pushed from your computer and install that .zip
-Reboot phone, be patient as it will take a minute to completely boot up.
-_-_-_-_-_-_-_-_-_-_-_-
If you need further instructions, please PM me.
All of this information deserves much thanks to strker45 and doktartaru for their endless help getting me through the process.
EDIT:
Should I make a walkthrough thread about this just incase anyone else has this problem?
Click to expand...
Click to collapse
Thanks very much! I'll do this when I get home tonight. I'll let you know how it goes...If i get it up and running I'll buy you a CASE of beer!
Not a problem.
I posted a more in-depth walkthrough here. Hope it helps possibly even better.
brwetz said:
Not a problem.
I posted a more in-depth walkthrough here. Hope it helps possibly even better.
Click to expand...
Click to collapse
I am back in business! I was able to flash the CWM Rom 9.0.0 and then ultimately restored the stock Nandroid made available here. It's a beautiful thing. I bought you some beers! Thank you very much.
Anybody know how to flash the rom through fastboot instead of recovery by pushing the boot.img and system.img from the ruu? sd card isnt mounting in recovery for whatever reason so I don't have access to the .zip files on my sd card. more details in my post from brwetz's thread here.
Thanks in advance for any help.
rjsvoon said:
I am back in business! I was able to flash the CWM Rom 9.0.0 and then ultimately restored the stock Nandroid made available here. It's a beautiful thing. I bought you some beers! Thank you very much.
Click to expand...
Click to collapse
How are those beers? hahaha
Beer music
brwetz said:
How are those beers? hahaha
Click to expand...
Click to collapse
You're the one that should be drinking the beers! Did you not receive donation?
rjsvoon said:
You're the one that should be drinking the beers! Did you not receive donation?
Click to expand...
Click to collapse
lol wow no I didn't..I didn't even know we could do that. I'll update my PayPal...
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
E:Mount: Unable to find partition for path '/[email protected]_Edition_V02.zip'
Error flashing zip '/[email protected]_Edition_V02.zip'
Updating partition details..
Click to expand...
Click to collapse
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Nekrom4n said:
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Click to expand...
Click to collapse
I can not remember,
Is the update a complete rom ??
If not,then install OC V.3 instead..
Nekrom4n said:
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Click to expand...
Click to collapse
Try Clockwork, this 4.2 is weird. I can do a backup in TWRP, but it cannot find what I placed on the sd card, so I have to use Clockwork for some reason....
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
same issue
i have the same proble only im stalling from /mnt/sdcard not from root.
On htc one s3..........
have been withoutmy droid for weeks!
samo problem
I have the same issue but when i put the ROM in a folder it does not work.
I have a goophone i5 and i wiped my system have no OS on it only TWRP.
I need to install a new recovery can anyone help me i am a noob for this !
Thank you
What command are any of you using to push the file??
Thx Josh
problem
lj50036 said:
What command are any of you using to push the file??
Thx Josh
Click to expand...
Click to collapse
i am trying to install a rom from the TWRP recovery .
i uploaded the file on the external SD card .
Nekrom4n said:
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! As soon as I put the zips (PA4.4 + gapps) into my sdcard folder my nexus 7 was able to install w/ out fail.
Nekrom4n said:
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
How did you changed to your root directory to sub directory
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.