Related
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
If its going to the stock recovery, its working fine! when you are on stock recovery menu, choose install packages (or whatever it is) and that will get you into clockwork recovery.
But its not loading to clockworks revovery. It just goes to standard start up when that option is selected.
correction
Sorry correction- I try that, and it says "signature verififaction failed- installation aborted." Why?
cpkfolief2 said:
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
Click to expand...
Click to collapse
why are you using ROM manager to flash the recovery if your on SMX ? SMX has bali 2.2 in it wich has CWM built into the kernel so your recovery should be the RED voodoo CWM recovery by default. and if stock blue recovery is coming up for some reason yu should be able to reinstall packages cause SMX has the modded stock recovery already
No no no, I'm not on smx- I'm trying to install the darn thing. I'm still on the stock rom. When I boot into recovery there are 4 options-
Reboot now
Wipe data
Wipe cache
Install packages
When selecting install packages, it fails via signature verification. There are no cwm recovery options available, either.
ooh .. your problem is you have to be rooted which im sure you already are ..
then go to the CWM thread in the DEV section and apply the modded recovery to system/bin . this will make the recovery ignore the signature check so you can flash CWM then SMX
use root explorer or adb push this file
http://dl.dropbox.com/u/2993191/recovery
to /system/bin
then put this file on the root of ur sd
http://dl.dropbox.com/u/2993191/update.zip
and put maximus x rom on ur sd
reboot recovery
reinstall packages
now ur in cwm
- Wipe Data/Factory Reset
- Wipe Cache Partition
Go to mounts and storage
UNMOUNT CACHE
MOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM
install zip from sd
choose zip from sd
look for maximus x rom install and u should be good
after you flash, go back to mounts and storage (before rebooting) and make sure your mounts look like this
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
this is as easy as i can put it
Thank you very muych for your persistence to help! I am a noob and cannot find the ty button. I'm a newb, I know.HOWEVER....…I am not a newb to this in general, and I have tried that already. I read that forum . Duh!this is what happens when trying to move the file to sys.bin:
Root explorer says:
Paste operation failed-
Does not say why. I found a solution! Another forum says to downgrade to stock recovery e2, then cwm will work. But I have to get odin and crap. So if there is something I'm STILL missing, and can't move the file there for that reason, don't hesitate to enlighten me.
you need to move the modded recovery to /system/bin/recovery, anything that tells you to downgrade is not correct, as we do not have anything to 'downgrade' to. The modded recovery from Krylon does the same thing. you should be following this:
1. download the recovery.zip from krylon
2. extract the .zip and copy the recovery file to your sdcard
3. use root explorer to copy the recovery from the sdcard to /system/bin/recovery
if it fails, make sure that /system is mounted as read write, rather than read only, there should be a button in root recovery to mount read/write.
Thank you sir! I was comitting a syntax error... maybe by attempting to copy the file from the wrong directory. No, the downgrade works... I was reffering to e2 recovery for samsung rather than e3 which requires signature ver. But that takes waaaaaay longer. So thank you. I was trying to copy the whole zip, rather than the actual file because I thought I had extracted it(stupid). But yeah. Ty! Will see if cwm works now.
Glad to hear that it worked for you, let me know how cwm works out for you, as well as whatever parts come after that for you. Don't forget the Thanks button if someone helps you
The files are in their proper places, all is right.
But when I boot into recovery, I am startled with fright!
For its still normal, its still stock-
So help me ill throw this phone like a rock!
Haha. But seriously. Still same issue.
FAILS TO INSTALL ANYTHING
"Signature verification failed- installation aborted."
It seems I will have to do it the hard way by installing e2. This was this issue for the galaxy s.
Why does no one else with a sidekick have to do this!!!!? Why is it not giving y'all signature verification errors! Why is there no video yet?
Sig verification issues relate to the recovery. it should still look like stock, as the original CWM is a fake flash. Make sure you have the cwm update.zip from Krylon's thread in your sdcard.
It is!!!!!! I think I'm going to cry.
Recovery is saved (overwrite) as instructed.
Update is on sd card as instructed.
Can't be corrupted, deleted files and tried again.
Boot into recovery and stock shows (as it should.)
Re-install from package (only option other than data wipe and reboot)
Whole signature failure
Signature verification failure
Installation aborted. :'(
i'll make you a script and a zip of everything to do this for you later, but that won't be until a bit later, still have to drive my girl home. in the meantime, can you try redownloading the cwm from ayo's original post? also, have you tried the rom manager version of cwm?
Roger that.
And it would be greatly appreciated. If it is, however, just another list of the instructions as mentione previously in this thread, or in the original rom post, forget it. But if there's something new then sure. Heck, a video would be great. I'm sure I wouldn't be the only one watching it either. And I will redownload all of it again(non-existant jesus christ) and try again in the meantime. Thank you again for your effort and supporth surely it must be that I am the only on with this issue. So I am unique on xda! Silly video...
i could even go so far as to skype someone to SHOW them ive got it right or what i have done, in which case i would hope for an "ah ha!now that thurz ya problem right thur neow."
Ok, I have a script for you, it's semi-tested? I already have root in my adb, so I can't test it as well, but it should work. let me know what happens. just unzip this, and run the run.bat.
this will reboot you into recovery after it's done, so make sure you're not doing anything on your phone when you run it.
https://sites.google.com/a/stephenduvick.com/www/files/sk4gtestoneclickroot.zip?attredirects=0&d=1
Credit to Noobnl for the original script, and krylon for the fake flash.
So how exactly do I run the run.bat? Its not an exe or script file... is there a command list I need to put in? (Gawd, the last custom rom I installed(cliq xt) was so much easier, before there even was a clockwork mod. It was easier, and that was when it was the hard way!) And my phone is already rooted, sure that doesn't matter though.
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
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...
I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed. I do not have a functioning MicroSD.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
Copied question to a better thread
It's now in the Android Q&A, see:
http://forum.xda-developers.com/showthread.php?p=28256764
Just getting used to the forum here.
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
If you can manage, push a similar framework (taken from someone else) using adb...
Typed using a small touchscreen
How?
jezus101 said:
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
Click to expand...
Click to collapse
You can flash a ROM using Clockwork instead of Odin? I totally missed that memo! Tips please
I found that Clockwork required the file to be in the internal SD folder -- I couldn't access the External SD card under any circumstance. There was no way to get a file to the internal file system without a functioning ROM. This is still confusing me. Maybe I had the wrong version of Clockwork or was doing it wrong. Not for lack of trying.