Related
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
I recently acquired a Photon Q LTE after being an Epic 4G user for years. I've flashed and rooted and beat that Epic 4G to bits over the years, but I can't seem to get CWM installed on this device for the life of me.
I've verified I've unlocked the bootloader and followed the directions in shabby's thread (http://forum.xda-developers.com/showthread.php?t=1856480) and on a couple other sites (http://www.andromods.com/basic-how-...r-user-install-cwm-recovery-photon-q-lte.html and http://www.androidegis.com/how-to/root-and-install-clockworkmod-recovery-on-motorola-photon-q-4g/), but it never seems like CWM wants to stick. Fastboot sends the file fine and says it writes it, but whenever I try to boot into recovery, I get the old school factory recovery with the Red Triangle and the Android System Recovery (3e) header, which is the factory bootloader (right?). Obviously SU isn't going to load in there.
My wife was playing with my new phone before I had a chance to do so (it was a gift), and I think she ran the latest OTA updates before I had a chance to even touch it. Looks like I'm running SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4, so I don't know if this has been tested with that or if I'll need to revert to a lower version, root, and then upgrade.
Any help would be greatly appreciated.
Thanks!
sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.
yogi2010 said:
sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.
Click to expand...
Click to collapse
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.
orty said:
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.
Click to expand...
Click to collapse
ok, i see. damn that's odd, because i haven't seen anyone run into this. i'm trying to think if there
is a way to boot straight into recovery from the bootloader, without booting up the system. i don't think you will be able to modify the file in /system without SU.
---------- Post added at 09:15 PM ---------- Previous post was at 09:11 PM ----------
come to think of it, i think there is a rootkit somewhere here that will install SU without flashing recovery. can't find it atm tho... but i believe it is said to still work on your software version..
actually if i remember correctly, i think it might be Dan Rosenberg's Motofail2Go exploit:
http://forum.xda-developers.com/showthread.php?t=1940594
the other thing you might try is flashing TWRP recovery instead of CWM. i am not sure but maybe TWRP automatically disables the recovery-from-boot file. i used TWRP and i see my file is already renamed and i never consciously did that!
I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!
orty said:
I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!
Click to expand...
Click to collapse
i just posted at the same time as you, so if you didn't see it, perhaps TWRP recovery is worth trying too!
Motofail2go got SU installed, which allowed me to rename that file. Then was able to follow the procedure to install CWM just fine.
Thanks much for the help!
Great, glad you got it working!
Did CWM not stick on my Photon Q ?
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!
penguinpal said:
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!
Click to expand...
Click to collapse
Yeah, sounds like you got into recovery properly by holding volume up while powering on. But it also sounds like your CWM might have gotten overwritten. If you did get SU installed, you can use a file program like Root Explorer or ES File Explorer to look for recovery-from-boot.p in your /system directory, and rename it to recovery-from-boot.bak. then reflash CWM.
smorealt rorer
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?
penguinpal said:
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?
Click to expand...
Click to collapse
Yep, correct on both counts you'll see the option 'backup and restore' in CWM.
Well no go on the rename - recovery-from-boot.p cannot be renamed because the file system is read-only.
I installed Total Commander and when I try and remount / as r/w with it I get re-mount error su called failed. Seems my su is not the real thing.
Will it work if I install CWM and boot straight from the download into the CWM - can I rename the file from there somehow?
If you can get adb access in CWM, there should be a command to rename that file, i'm not sure if it would be from adb shell or not... perhaps Google it or someone else will chime in here. You would probably need to flash SU first, then try adb and type su first and see if you get # prompt.
Otherwise you can go thru the full cycle- flash CWM, boot straight into recovery, flash SU, reboot and rename the recovery file, reflash CWM. Using adb in CWM would be the more elegant way, haha.
I am OK with full cycle - just explain this to me --> boot straight into recovery, flash SU,
I think I know how to boot straight into recovery -> but how do I flash SU from there?
Do I have to get the su.zip onto the phone before I boot into recovery? How do I do that?
Which reminds me of another question the http://forum.xda-developers.com/showthread.php?t=2017748 thread says
Bugs:
Usb mass storage isnt working,
Is this still true? Does this mean if you install CWM you can't mount your phone as mass storage in anyway ?
Yeah, load the SU zip onto your phone before going into CWM, since usb storage might not mount. Easiest way might be just to DL the zip on the phone by going to the thread on the phone, then navigate to your downloads folder in CWM to flash it. Otherwise if you have a more recent version of Ubuntu, you might be able to access device storage thru usb to transfer the zip... or else you can do that in Windows(or Mac maybe?).
Edit: flashing CWM won't break usb storage in general, it just doesn't seem to mount in CWM.
Great - so I downloaded the SU.zip from my phone and it is in /sdcard/Download for later. So I assume loading CWM does not erase what is in the download folder ?
And thanks for explaining that CWM just break usb mount in CWM not generally.
Much Much appreciated.
CWM shouldn't erase whats in the download folder. If it does, there's an issue there.
And why not just use MotoFail2Go to push in SU and then use RomManager from the appstore to flash CWM from the OS itself, because that fixes the rewrite issue as well and is a much simpler process?
CMNDR
since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip
penguinpal said:
since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip
Click to expand...
Click to collapse
i always keep a Windows installation around, just for certain programs. but, by doing this the manual way, at least you get to see what is being done, instead of programs doing it for you
This is a Loki'd ClockWorkMod Recovery TOUCH file that I created on my AT&T Samsung Galaxy S4 SGH-I337 with the UCUAMDL baseband.
Flash using loki_flash in a Terminal window (how I did mine) or ADB using the command loki_patch recovery cwm.lok. If running in a Terminal window, make sure you have SU access first and that the cwm.lok file is in the same folder as the loki_patch file. I placed both of mine on the root of my external SD card.
After flashing this I rebooted into Recovery via ROM Manager and Touch was installed.
Hope this helps someone else!
Can you give clearer, more specific instructions on how to use this?
this is pre-lokid whe build by builder.clockworkmod.ckm
Sent from my SGH-I337 using Tapatalk
jd1639 said:
Can you give clearer, more specific instructions on how to use this?
Click to expand...
Click to collapse
UnRar the file and copy the CWM.LOK file onto your SD card.
Download and save the loki_flash file from here:https: // github dot com/djrbliss/loki/tree/master/bin
Copy the loki_flash file onto your SD card in the same location as the CWM.LOK file.
Open a Terminal session (download and install your favorite Terminal app from the Play store)
In the Terminal window type:
[email protected]:/ $ su
[email protected]:/ # cd /<path to location you saved the files to>
[email protected]:/ # ./loki_flash recovery cwm.lok
* Note - not responsible if this bricks your device. Your best bet is to read up on how to do this yourself at https:// github dot com/djrbliss/loki, save your own aboot.img file and built your own CWM.LOK file.
blackwing182 said:
this is pre-lokid whe build by builder.clockworkmod.ckm
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If this recovery.img file was downloaded from http://www.clockworkmod.com/rommanager then it is not loki'd by default. I actually just tried to flash the .img file i downloaded from there and it gave me the unauthorized BS and i had to heimdall the stock recovery image back on.
ROM Manager has a script that it runs AFTER the recovery.img file is downloaded that loki's the recovery.img, then flashes it to the device.
Question....
jakew02 said:
If this recovery.img file was downloaded from http://www.clockworkmod.com/rommanager then it is not loki'd by default. I actually just tried to flash the .img file i downloaded from there and it gave me the unauthorized BS and i had to heimdall the stock recovery image back on.
ROM Manager has a script that it runs AFTER the recovery.img file is downloaded that loki's the recovery.img, then flashes it to the device.
Click to expand...
Click to collapse
I have full root access with SuperSU on sgh_i337 NC1 SELinux permissive. I froze all Knox related apps with TiBu. You flashed and soft bricked... now my question is.... Is it Knox that gave you the warning about the unauthorized flash attempt? I don't think I can flash traditionally anyway with the boot loader the way it is, but I havnt found anyone else that's fully rooted 4.4.2 either, so this is an original question lol. If I soft brick, I'm pretty well dead at this point, but in for a dime, in for a dollar I guess lol. After a 15 hour hack session fighting with Knox I don't wan to lose now :cyclops: I need a recovery though,
Lt1streconbn said:
I have full root access with SuperSU on sgh_i337 NC1 SELinux permissive. I froze all Knox related apps with TiBu. You flashed and soft bricked... now my question is.... Is it Knox that gave you the warning about the unauthorized flash attempt? I don't think I can flash traditionally anyway with the boot loader the way it is, but I havnt found anyone else that's fully rooted 4.4.2 either, so this is an original question lol. If I soft brick, I'm pretty well dead at this point, but in for a dime, in for a dollar I guess lol. After a 15 hour hack session fighting with Knox I don't wan to lose now :cyclops: I need a recovery though,
Click to expand...
Click to collapse
This thread is from 2013, and it's referring to the old MDL firmware. Your on NC1, which came out nearly a year after this was posted... the reason your phone is softbricked is because any loki-based recoveries,etc do not work on devices MF3+. Your want to check out this thread to get help in restoring your device. Remember, next time to look at the date of the posting and to read around the forums before trying to modify your device if you are unsure what you are suppose to be doing.
Your need to use Odin, to flash your phone back to stock NC1. It's in the thread I linked above....
I'm not soft bricked lol... I'm trying to figure out how far I can push it without that happening I have su in /system/xbin & /system/bin... Long story but I needed it there while I was restricted to root access only in terminal emulator for a few hours getting Knox to take a nap. I have learned new respect for that dang little app!!!! I actually got full root without PC/Linux support In 4.4.2 that's... Probably the reason's Knox never saw it happening lol I'm still messed on recovery besides safe strap unfortunately, but I'll take SuperSU over towelroot or safe root any day I grabbed a nap and I'm deodexing my system apps and framework now. I was kinda excited and didn't notice the date... Ty for the help, but Ialready have stock firmware I'd need. I'll head over to the newer thread... I actually have an idea on the boot loader from the decompiled Knox file I've gone thru. The boot loader IS locked, but we have a very limited exploit. Knox has been revamped five times that I caught I believe, and it ridiculously still had the ability to safely uninstall itself like it done early on lol. Crazy! Anyhow tks... I'll head over there. This was just funnier than when I found 'vold 2.0 the vengence' rofl
Argh! Pulling my hair out over this one. I've been flashing custom ROMs and rooting my phones for years now, since my old HTC G1. Even had KitKat running on my HTC Desire 4G!
... but this Sidekick is proving another matter. I've been through forum after forum, all saying the same things on how to root/flash this thing, but I haven't managed to get anything to work! So, here's step-by-step of what I just did and the result I get every single time, no matter the initial method:
1: Fired up ODIN3.
2: Wiped the user data and cache from the stock recovery (Android System Recovery (3e)).
3: Connect USB cable, reboot phone into download mode (using the battery-pull method).
4: Successfully flash to stock ROM, reboot.
5: Sign in with Google, enable WiFi.
6: Run SuperOneClick, reboot.
7: Grab ES File Explorer from the Market, after it updates.
8: Attempt to replace "recovery" in /system/bin with custom
... and here's where things break. Doesn't matter what version of SuperOneClick I use (and I've tried from 1.9.1 through 2.2.3), nor does it matter what exploit I select. What happens? Well... aside from everything on-screen claiming to be okay, and everything claiming it's working, once the rooting is "successful", I reboot like it says, see that SuperUser is in the applications, it shows me an su binary version...
... but anything that tries to run super-user (ES File Explorer included) that gets added to the super-user list simply does not work. I can't over-write the recovery, can't delete or muddle with anything that requires elevated privileges, and the ROM Manager for sure won't work because I can't get CWR installed.
I love my phones with keyboards. I really do. I'd love to keep this thing, but the stock firmware is driving me up a wall (especially that stupid media scanner). So if anyone has any ideas to throw at me, care to offer some? Haven't a clue at this point what I'm doing wrong.
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
demkantor said:
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
Click to expand...
Click to collapse
Awesome! I'll give this a go once I'm all done with today's activities and see if it works.
Well, apparently I have root access for the moment, but it is denying my replacing of /system/bin/recovery - in adb shell, it states "Filesystem is read-only", so I re-mounted /system -rw and no dice. Going to attempt to try again in a moment, after a reboot.
Okay, so since there's a problem with all of this, I'm going to try that second ROM (KD2 I think it was) - but as I recall, it was on a very slow server. Plus I have a load of things to do tomorrow, so it probably won't be until tomorrow evening sometime when I'll be able to flash it. Once I've used Odin to re-flash, I'll get back to you.
Well, I had to dissect "t839-Sidekick4G-UVKG2-One-Click.jar" and remove the xml file from within it, but I acquired the necessary package to upgrade to KG2 from KD1 through Odin3. Took a while to figure out just how to deal with it, and I was successful in flashing... and I even replaced the recovery file after rooting it again!
... however, now it just sits there at the "T Mobile Sidekick 4G" start-up screen when I attempt to boot into recovery, so now I'm preparing to re-flash it again to recover the stock recovery. So... still more on this, later.
EDIT: Also, I named the tar file "KG2OdinHeimdall.tar", since I basically ripped it right off the "HeimdallPackage.tar" file from the Heimdall one-click thing. Turns out, it apparently works just fine if you remove the .xml file from the original tar.
Finally!
I ended up having to use my own method to get the KG2 update installed because the one-click program kept crashing on me when selecting "Show all devices", and I opted to use AntTek Explorer (all you have to do is go into the program's options and it'll attempt to acquire admin privileges, if the device is rooted) to copy the recovery file to /system/bin - but your post worked for everything else, once I got past not being able to copy the recovery file.
I opted for the CM6 package and it's quite fast! Thank you loads, demkantor!
Nice! I'm glad all worked out well for you!
If you get a chance try out the one gingerbread ROM, its cool to see it running but there are still driver issues so keyboard is borked, really makes it pointless to have on this phone...
But there are a few nice froyo ROMs ready to be played with, someday development will hopefully pick up again
Until then, happy flashing!