Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw
thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
@thetinyjesus You could also try this app. No PC necessary.
Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe
thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.
Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks
If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.
Okay once im back home ill show the output
Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.
Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
Anyone?
Related
Have full Nand root with Clockwork recovery 1.8.2.1. Every time I try to do a nandroid back up, either from within rom manager or directly from recovery, it errors out. It says "E:Can't open /tmp/recovery.img" when doing directly from recovery. When doing from within rom manager, it'll boot into the recovery screen with the yellow triangle and the android, but sticks there.
Any ideas?
I got the same error earlier and didnt think anything of it til i went to recover and it failed at the md5 sum check. Good thing i still had another one from today.
Did you ever figure out what the problem was?
Nope i still cant seem to backup. Anyone else with full nand unlock unable to nandroid?
Anyone able to help us out? its kinda a big problem not to be able to backup..
Also when im in recovery I see that /tmp/recovery.log is not accessible, nor is it a file. I tried to create it but /tmp is read only.. I did the full nand unlock and can write to /system while android is running.
Can we get some acknowledgement of this issue? I really dont want to do anything until i can backup again, and its killing me
Mast3rpyr0 said:
Anyone able to help us out? its kinda a big problem not to be able to backup..
Also when im in recovery I see that /tmp/recovery.log is not accessible, nor is it a file. I tried to create it but /tmp is read only.. I did the full nand unlock and can write to /system while android is running.
Click to expand...
Click to collapse
This is a major issue. Not only can I not backup, but I can't seem to flash any new roms either. I am stuck with what I have. I haven't heard anything from any of the devs. Anyone? Bueller? Buelller? Bueller?
I just reflashed the root PC36IMG and started over, took out nand unlock. Im perfectly ok with rebooting to recovery to when i want to write to /system. kinda a fail safe i guess.
Works for me, but I use the actual nandroid and not clockwork nandroid.
warmthsound said:
Have full Nand root with Clockwork recovery 1.8.2.1. Every time I try to do a nandroid back up, either from within rom manager or directly from recovery, it errors out. It says "E:Can't open /tmp/recovery.img" when doing directly from recovery. When doing from within rom manager, it'll boot into the recovery screen with the yellow triangle and the android, but sticks there.
Any ideas?
Click to expand...
Click to collapse
Hey guys, thanks for the bug report. I'll fix this today!
Hi Koush,
I seem to still be getting this error, as well as "E:Can't make /tmp/update_binary" when I try to flash new kernels.
I can still apply new ROMs and some other updates without issue, other than the aforementioned recovery.log error.
This is on a HTC Desire using the latest version of ClockworkMod as installed by ROM Manager.
What version of Clockwork are you using?
I was using the newest version of Clockwork flashed from the newest version of Rom Manager and I was still getting this error in the recovery:
E:Can't open /tmp/recovery.log
I tried flashing back to an older version but it said the same thing.
I had to reflash the stock recovery img to get my Nandroid backup to work.
Dsmithjr said:
I was using the newest version of Clockwork flashed from the newest version of Rom Manager and I was still getting this error in the recovery:
E:Can't open /tmp/recovery.log
I tried flashing back to an older version but it said the same thing.
I had to reflash the stock recovery img to get my Nandroid backup to work.
Click to expand...
Click to collapse
Which version does it say in the recovery window I'm trying to figure out if the flash actually worked
Koush said:
Which version does it say in the recovery window I'm trying to figure out if the flash actually worked
Click to expand...
Click to collapse
Sorry Koush, I uninstalled it last night when I was having the issues and I can't remember the version numbers (it was pretty late). From what I can remember, the Rom Manager was version 2.0.0.5 I think, and the Recovery was 2.0.2.X maybe? I can't really remember. It did say the right number in the recovery window.
Last night I wiped and installed a new ROM on my phone, then installed Rom Manager from the market and flashed the newest recovery. It looked like everything was working but when I tried to flash a ROM, the phone would reboot into recovery, print a few lines of text on the screen, and then just reboot right away. So I rebooted to recovery from Rom Manager and it booted to your recovery, but it gave me the error at the bottom of the screen.
I flashed an older recovery (version 1.0.8.2 or something) and it did the same thing. Maybe I'll re dl it and try again today.
2.0.1.4, which is what ROM Manager 2.0.0.5 reports as the latest.
Just tried flashing 2.0.2.0 from the experimental section in ROM Manager, but when I rebooted to retest it seems ClockworkMod itself reports v1.8.2.1
I did this using unrEVOked 2 on a Mac, a few weeks back, which apparently should have installed ClockworkMod 2.0.1.0 - as ROM Manager reports 2.0.2.0 is present and gives no errors on flashing new versions, how can I resolve this?
Edit: Just rebooted into ClockworkMod v1.8.2.1 and tried to manually flash the 2.0.1.4 and the 2.0.2.0 recovery update zips but these too failed immediately with the "E:Can't make /tmp/update_binary" error.
Can you adb shell into your phone while in recovery and type "mount"?
I have the same problem,but I just can Backup~!I don't know why^^^
first, sorry if this is the wrong section.
my phone right now is stuck booting to the white htc evo screen, sitting for a second, then rebooting back the the white screen, and just looping like that.
before it started doing that, i was on my phone, with bootmanager, i installed jared's ics rom to a slot, and then i booted to it. the install of the gapps wasnt quite working correctly, so i was gonna install it to the phone then nadroid, then put it in a slot. so i when straight from my slot 1 rom, to recovery, flashed the phonerom update.zip then did a backup of my phonerom before installing the ics rom. after doing the backup, i installed the new rom, and gapps, hit reboot, and now im looping.
thats the best description of my situation, i really hope someone can help out, if any more information is needed, let me know
thanks in advance
-Alex
I would best do a full wipe and restore a backup if possible, then try to reconfigure bootmanager. Did you check that 'flash large boot.img' option?
i cannot get into recovery, i forgot to mention that. is there a way to do that over adb? i have nands and roms on my computer
thanks for quick reply
aadcrasher said:
i cannot get into recovery, i forgot to mention that. is there a way to do that over adb? i have nands and roms on my computer
thanks for quick reply
Click to expand...
Click to collapse
As an it just keeps rebooting when you try to go to the bootloader?
And well the only way is if you were to extract the boot image of a working rom, and flashed it using fastboot; and no problem.
i can get into bootloader, but not recovery. and i dont think i have any .img's
aadcrasher said:
i can get into bootloader, but not recovery. and i dont think i have any .img's
Click to expand...
Click to collapse
What happened when you choose recovery? Have to tried re-flashing a recovery?
Also, extract a rom zip, then copy the boot.img from that rom into your adb tools folder. From the bootloader, select fastboot, connect to pc, from adb run:
fastboot flash boot boot.img
fastboot reboot
i was thinking i should try flashing a recovery, but i didnt know if that would mess it up. when i select recovery, it does the same bootloop. im gonna try that with fastboot
tried that with fastboot, and no dice. gonna find a recovery and flash it, see what happens
actually, i pushed the boot.img, now its booting the ics rom, which is not the boot.img that i pushed
aadcrasher said:
i was thinking i should try flashing a recovery, but i didnt know if that would mess it up. when i select recovery, it does the same bootloop. im gonna try that with fastboot
tried that with fastboot, and no dice. gonna find a recovery and flash it, see what happens
actually, i pushed the boot.img, now its booting the ics rom, which is not the boot.img that i pushed
Click to expand...
Click to collapse
The boot may have been corrupted and went with the old rom.
Well see if you can get into recovery, do a full wipe > new rom > re-try bootmananger.
it didnt boot successfully, but now i can get into recovery. its still acting a little strange. like i just did a wipe and factory reset, and it still tried to boot into the ics rom? maybe its messing up cause of bootmanager. idk.
im gonna flash a new recovery. i try to boot into the recovery, and it goes to white screen, then reboots, and goes into the rom
i cant get anything to work/stick, i flashed a recovery (cwm) and it looked like it was gonna work, then i couldnt flash something on my sd, it said it couldnt find it. so confused
i cant get anything to work/stick, i flashed a recovery (cwm) and it looked like it was gonna work, then i couldnt flash something on my sd, it said it couldnt find it. so confused
aadcrasher said:
i cant get anything to work/stick, i flashed a recovery (cwm) and it looked like it was gonna work, then i couldnt flash something on my sd, it said it couldnt find it. so confused
Click to expand...
Click to collapse
I would try amon ra recovery; CWM has caused known problems for some users.
any chance of a link?
nvm, its just under the cwm links on the page i found earlier
ya, it still doesnt see my sd. and using fastboot to install the boot.img doesnt seem to be working either
aadcrasher said:
ya, it still doesnt see my sd. and using fastboot to install the boot.img doesnt seem to be working either
Click to expand...
Click to collapse
For the sd card, try this > http://forum.xda-developers.com/showthread.php?t=695243
I'm heading out now; hopefully someone else can take over.
okay, thanks for the help
that did the trick to make it recognize my sd, but still cant get it to boot
aadcrasher said:
okay, thanks for the help
Click to expand...
Click to collapse
No problem man.
i cant get cache to unmount in recovery, and i cant get the phone to hold a recovery, i have to keep flashing via fastboot
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
Cwm 5.0.2.7 all day.
Sent from my SGH-T989 using xda app-developers app
I have exactly the same issue. I had problems trying to wipe cache on CWM 5 so I installed through Goo, now when I boot into recovery, it gets stuck on TEAMWIN screen.
files- images
make sure you have the file in the right place wwhen you know you do get the switcher and then down ld. the file again i had to trial and error it a few times :victory:
The newest twrp gets stuck for me too. I just flashed back to a cwm
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Same issue here on the Telus T989D. Any solutions without using cwm?
You can always try the manual method if your brave and familiar with the terminal. Go to Team Win's for our phone here: http://teamw.in/project/twrp2/101. Download the .IMG file and follow the instructions under Download - Recovery Image Method (using dd): Not hard but doublecheck your typing before hitting enter or you'll brick your phone.
I'm not responsible for any actions taken because of this post. Good Luck, its worth it in the long run.
Sent from my SAMSUNG-SGH-T989 using xda premium
One small problem with that.....
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
This worked for me:
reflash CWM, flash superwipe, install TWRP through goomanager.
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
dailo23 said:
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
Click to expand...
Click to collapse
I flashed that version through Odin and it seems to be running just fine. I wiped caches and now TWRP appears to be working normally :fingers-crossed:
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
EDIT: Wow I guess I didnt read the critical part where your stuck on the recovery boot screen so the attachment below wont help.... JUMP DOWN TO POST #21 AND FOLLOW IT TO RECTIFY THE GETTING STUCK ISSUE
Here, try this file guys. Someone over in the Jedi threads made a CWM flashable TWRP zip. You can thank me for bringing it to your attention if you want, but I did not create this ( I just clicked on the attachment paperclip for the thread and browsed through all the attachments because I knew I saw it somewhere in the development section...)
I also checked TWRP's own website and for the Hercules, v.2.3.1.1 is the latest version supported for our device so far but I only found 2.3.0.0 packed in a recovery flashable form.
Just flash it via CWM like any other zip and once its done it'll reboot your device automatically to system, so just reboot it back to recovery to make sure it worked. It did for me when I did awhile back with v.2.2.2.0 and I just used the below file to flash and update it in TWRP to v.2.3.0.0
Hope it helps
incgnito said:
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
Click to expand...
Click to collapse
i just started having this exact problem with the cache partition. it will freeze on me whenever i try to reformat it, i can't unmount it, etc. i also get stuck on the twrp "teamwin" blue start up screen. have you figured out a solution?
edit- got it working again.. ended up odin flashing twrp 2.2 and i was able to wipe everything and install the new rom stuff.
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Will you kindly explain how you did this?
y0urm0msname said:
Will you kindly explain how you did this?
Click to expand...
Click to collapse
What exactly is your issue?
Eks Dee Aye said:
What exactly is your issue?
Click to expand...
Click to collapse
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
y0urm0msname said:
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
Click to expand...
Click to collapse
Do you currently have CWM or TWRP as your recovery?
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
Currently the non-functioning TWRP. I tried flashing CWM from the Rom Manager app, but that froze too. Looking for a reliable fix. I do not have a preference for recovery.
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
If you have either I guess it doesn't really matter. Just install/flash the attached file below just like you would any other rom via your recovery.
After it installs reboot back into recovery and you will see the old recovery replaced with the latest TWRP for the T989.
Lemme know if this works for ya.
Eks Dee Aye said:
Just install/flash the attached file below just like you would any other rom via your recovery.
Click to expand...
Click to collapse
This is the part I don't understand. If my TWRP is stuck, how do I install/flash via my recovery?
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
hi, recently i decieded to install CM11 on my samsung galaxy nexus, i downloded it and then i reset facotry my phone, but when i wanted to install it from Bootloader i got an error, then i thohgt it cause of old bootloader so i wanted to update it but THE problem showed up, i cant come into my android it wont be come, please help me out
If all you did was a normal factory reset, it should boot up fine. If you did something like wiped system, then you need to get to a computer and use ADB. If you wiped system then you have nothing to boot to
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
the error is: set_metadata_recursive: some change failed
E:erro in /sdcard/0/0/cm-11-20131130-UNOFFFICAL0maguro.zip
(stat7)
insstalation aborted.
the.farbod said:
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
If you have a backup though, why cant you just restore the backup? Can you not get into the recovery anymore?
kinda curious, OP why didnt you just wipe everything in recovery mode and flash it??
1) adb reboot bootloader
2) fastboot flash recovery ***recovery.img*** (i like to rename the image to "recovery" for the ease of my own useage)
3) press vol rocker to recovery mode and flash away!
I personally use TWRP, but a lot of people prefer CWM, they are both amazingly easy to use.
worst case, you flash the stock 4.3 image from google to get everything back on track.