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
Related
Apologies if this is already answered somewhere or should have been common knowledge - I'm new to Android. I feel like I've read through all the appropriate threads but haven't found the answer.
I wanted to simply remove some of the stock apps from my G2X. I can't get adb connected while in CWM recovery. I've done the following:
- Installed android sdk
- Installed LG adb driver
- Rooted with SuperOneClick
- Installed Rom Manager from the market and "fake" flashed ClockworkMod Recovery
- Booted into CWM and made a nandroid backup
- Factory reset using stock recovery
- Restored nandroid backup using CWM - works fine
Now, I believe all I need to do is get adb connected in recovery mode, mount /system and delete any .apks I don't want; however, the adb device is not present when I boot to CWM recovery. adb works fine when booted normally. As a result, I obviously can't start adb shell. Oh, and I've tried this from XP 32bit and Win7 x64. What am I missing?
Did I need to flash CWM to the actual recovery area using NVflash for this to work? I'd rather not do this for warranty purposes (especially this soon) unless absolutely necessary. Incidentally, the other USB devices (virtual serial port, modem, and storage devices) do show up while in recovery - just not the adb device.
I'm open to other methods of stripping .apks. I don't yet know anything about modifying and repackaging a nandroid backup, if that's possible, or I would try that route.
Any guidance would be greatly appreciated.
Thanks!
EDIT: I've resolved my particular issue by just remounting /system as rw while the phone is booted normally. This still doesn't answer the CWM adb question, but at least for now, I guess I don't need that.
I believe you can just use Root Explorer (or another type of file manager) to delete or freeze the apps that you do not want. Not sure if this belongs in development.
This will be moved soon enough, and you didn't search enough since i know there is threads talking about this. Do a search again. mod plz move this to the right area.
Maybe a freeze is one way to go, but obviously a cleaner way is remove the apps, which should be possible with this method and others.
I did search - a lot - in this forum and others. I found no one directly addressing adb not working in CWM on the G2X. I saw one poster here mention they had a similar issue, but only on XP and no one responded to that either. If you know of a thread with this information in it, please enlighten me.
Maybe this isn't the right forum to post in, but the question is directly about CWM flashed to a rooted G2X and access using adb...
I just use titanium backup's Chuck Norris Mode.
I've resolved my particular issue by just remounting /system as rw while the phone is booted normally. This still doesn't answer the CWM adb question, but at least for now, I guess I don't need that.
Root Explorer is your best friend, a simple delete is all you need, make sure you mount before entering system
davemayo2000 said:
I've resolved my particular issue by just remounting /system as rw while the phone is booted normally. This still doesn't answer the CWM adb question, but at least for now, I guess I don't need that.
Click to expand...
Click to collapse
Haha, plenty of answers, none of which answer your main concern. I too have been mystified by the lack of adb functionality while in recovery. I have come to the conclusion that it's simply not functional with this very early version of clockwork recovery for our phones and probably not a high priority for the devs at the moment as theres probably plenty of other issues deemed more urgent. Especially considering there are many work-arounds to solve this particular missing function. Hopefully I'm wrong though.
Sent from my LG-P999 using XDA Premium App
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
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
SlickAl41 said:
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
Click to expand...
Click to collapse
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Ryanscool said:
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
Click to expand...
Click to collapse
Heimdall did it. Thanks for pointing me that direction. :highfive:
SlickAl41 said:
Heimdall did it. Thanks for pointing me that direction. :highfive:
Click to expand...
Click to collapse
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
SlickAl41 said:
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
Click to expand...
Click to collapse
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Ryan79 said:
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Click to expand...
Click to collapse
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
SlickAl41 said:
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
Click to expand...
Click to collapse
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
SlickAl41 said:
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
Click to expand...
Click to collapse
Hey Alan, sorry... been away from the forums for a couple days. But it looks like you got it figured out you are correct on the Heimdall command, the only thing different that I did is that I already had root explorer purchased... so after the SuperUser install I just ran it to move the install_recover.sh to my SD card
Glad to hear you got it working!
I am trying to Flash the Stock ROM on my Galaxy Y PRO after it is gone into a bootloop (by itself), i am using ODIN , but it got stuck on Flashin the recovery img
i tried all The USB ports of my computer and only 1 worked. Please i need help and a sure answer thx
MultipleMonomials said:
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Click to expand...
Click to collapse
How to use Heimdall when I have bl, ap, etc
My TF300 is on stock and is unrooted with a locked bootloader. However, despite this, it is no longer booting into the stock ROM. It gets stuck on the bootanimation phase with the loading circle constantly circling round, even after a few hours. It hasn't moved on from this stage unfortunately and I was wondering if there was anything that could be done? I know I could try wiping my data, but there are files and app data that I would not like being lost so is there any way they would be salvageable? Thanks for any help
If ADB is accessible, you could pull /sdcard/, and save it on your computer.
While waiting at the animation, plug it in to your computer, open a terminal, cd into whichever directory ADB resides, and run
Code:
adb devices
If it returns your tablet, then run
Code:
adb pull /sdcard/
adb pull /data/
It should copy everything from your internal storage and your app data into the directory containing ADB, but I'm honestly not sure if you could pull /data/ without root access. And even if you did, I'm not sure how you could safely restore the files without breaking something (or especially without root). At the very least, you'll have the contents of your internal storage.
At that point, you should be OK to wipe your data.
If that doesn't work, then assuming you're on the 4.2 bootloader, you could boot into the bootloader by holding Volume Down as you start your tablet, and you will automatically be in fastboot mode. This should allow you to flash a stock blob with fastboot. Instructions to do so have been posted throughout this forum.
If all else fails, it should still be under warranty since it's locked, so you could get a free replacement. I'm thinking the data wipe should be enough, though. Good luck.
Thank you kindly. I'll thank you later as I seem to be out of thanks today. Admittedly though, I'm not too experienced with this stuff and don't really know which directory ADB is in
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
UndisputedGuy said:
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
Click to expand...
Click to collapse
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
EndlessDissent said:
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
Click to expand...
Click to collapse
Thanks again for your help. I'll need to look into using fastboot to flash a stock blob.
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
UndisputedGuy said:
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
Click to expand...
Click to collapse
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
EndlessDissent said:
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
Click to expand...
Click to collapse
Thanks! I shall probably try that soon, but I currently want my files from the download folder so will have another stab at that. Thanks again for the assistance :good:
I have been able to pull some files using ADB and thank you greatly for your assistance in doing so. I hadn't really used ABD before but now I'm more familiar with it, so thanks. I have a question regarding using the fasboot method to flash a stock blob. Do I need an unlocked bootloader for flashing a stock blob? The guides I've found have suggested as such. My bootloader is locked.
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
EndlessDissent said:
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
Click to expand...
Click to collapse
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
I was just about to post that your first step should be to wipe data and see if it boots before we get caught up in fastboot. That is a last resort here. If wiping data may work, fastboot is more work than necessary.
Just to confirm that my tablet did indeed start working again after wiping the data although the stock Asus Backup App fails to restore my app backups from a while ago. It stops at 15%.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Hi people. Ive just bricked my Relay by installing Chainfire3D(dont laugh at me I know im stupid)))). So can anyone do a backup the system by Recovery mode and send me to my email [email protected] or attach it here, I will put it in my SD and do a restore from recovery mode(i didnt brick it fully, I guess its called softbrick).
I would really appreciate anybodies help. Please people I really need help...Thanks in advance)))
Just flash a new ROM in recovery, or if you plan to just do a restore of a system partition you would need to give out more information as to flash the correct one as each ROM will have a different system partition
the cavaca
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.
SuddenGun007 said:
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.
Click to expand...
Click to collapse
Thanks man, really appreciate your help.
HaykKarapetyan said:
Thanks man, really appreciate your help.
Click to expand...
Click to collapse
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.
SuddenGun007 said:
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.
Click to expand...
Click to collapse
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2
HaykKarapetyan said:
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2
Click to expand...
Click to collapse
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.
SuddenGun007 said:
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.
Click to expand...
Click to collapse
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
605 MB I should have said......what I meant was that in your first reply you told to install rom and then flash recovery and I dont think all that is done by only these 5 steps
HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK. It really is a 3 step process, but since you soft-bricked your phone you can't simply copy the stock-system.zip to your sdcard and flash that in recovery. You will need adb to communicate with your phone while in recovery.
SuddenGun007 said:
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK.
Click to expand...
Click to collapse
So in 5th step I should locate to that 605mb.zip,without extracting it
stimuli erpio
HaykKarapetyan said:
So in 5th step I should locate to that 605mb.zip,without extracting it
Click to expand...
Click to collapse
Yes that is correct, the recovery when it installs will unpack it for you.
SuddenGun007 said:
Yes that is correct, the recovery when it installs will unpack it for you.
Click to expand...
Click to collapse
Alright man, thanks. Still installing the freaking drivers)))
HaykKarapetyan said:
Alright man, thanks. Still installing the freaking drivers)))
Click to expand...
Click to collapse
I am using Linux, otherwise I would try to send you the drivers.
You might be able to use this http://www.solvusoft.com/en/update/drivers/mobile-phone/samsung/t-mobile/sgh-t699/model-numbers/
SuddenGun007 said:
I am using Linux, otherwise I would try to send you the drivers.
Click to expand...
Click to collapse
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))
HaykKarapetyan said:
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))
Click to expand...
Click to collapse
Oh crap I didnt see you had a link there, let me check that one out
This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.
SuddenGun007 said:
This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.
Click to expand...
Click to collapse
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???
HaykKarapetyan said:
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???
Click to expand...
Click to collapse
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo
SuddenGun007 said:
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo
Click to expand...
Click to collapse
Ok so if I download this and lets say put this zip in c:\Android what command should I run in cmd???