Related
I rooted the phone through the oneclick method went through command prompt typed in adb reboot recovery and its taking me to the samsung recovery mode I looked through the run.bat in command prompt an it said it flashed the 3.0 clockworkmod but nothin so I tried the 2.5 one still nothing I did the Odin flash to stock tried 2.5 still nothing then flashed it to the 3.0 one and still the clockwork is not coming up any suggestions?
down load rom manager and when you open it, at the top it says "flash clockworkMod Recovery" go ahead and do it and i think then you will be ok..
you still need the one click with clockwork redirect..
I tried that an it keeps saying error
apop90 said:
I tried that an it keeps saying error
Click to expand...
Click to collapse
Don't you think it would be helpful to tell us what that error is? It's probably because you have the stock kernel which doesn't work with Rom Manager. There are instructions in a couple threads from the past week on how to manually install clockworkmod.
bud had this happen.. just reran the oneclick a second time and was good to go
are you still getting # in adb and can u 3finger to clockwork?
also trt installing the lates superuser from market and when u "adb reboot recovery" make sure u check phone and allow permission
Sorry it reads error downloading I tried doing the tar file for the leaked test build and still it came up as invalid
What is three finger never heard of that and also how can I flash a kernel without a flash recovery image? Thanks.
The three finger death grip is where you hold vol down + camera + power to boot into recovery.
You usually use clockworkmod to flash a different kernel. The other way is to use the epic all-in-one root and recovery (not the one-click). It has an option to replace the kernel with, iirc, the andromeda kernel, which will let rom manager install cwm.
Or you can search for the threads that give instructions on how to install cwm without a computer.
Ok so that three finger works is that the best kernel to use for 2.2 and what is the most reliable rom out
Another thing Ive tried dk28 ext4 kernel, phoenix and andromeda kernals they all work for me but when I do the three finger and flash a rom it gets stuck one did work which was Epic Experience but when it went through it said it was still on dl18 not dk28 so what am I missing? Thanks
The official froyo update starts tomorrow. I would just wait until that hits xda. I wouldn't be surprised if a pre-rooted cwm flashable update made it here by tomorrow night or some time Tuesday.
I finally got it!!!! Thank you for the help
I am on LG1 stock ROM, rooted with arcadia3go's debugfs attack (http://forum.xda-developers.com/showthread.php?t=1827518). Root process worked and I installed CMW at the end of the steps.
I further verified that CMW (version 5.8.4.5 from that post) worked after the immediate reboot, and I was able to make a Nandroid backup of my phone.
What's strange was that, after some time when I needed to flash a mod or just to make a further nandroid backup, I booted into recovery mode only to find that the the stock 3e recovery was back and CWM was lost. This happened twice so it is not by accident. The only solution to me is to rerun ADB command dd to re-instate CWM, workable but annoying.
Any idea?
further info: at 3e recovery screen, under the normal menus, there is something like:
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
No idea...what I would do though is Odin back to stock and then root and install CWM via mrRobinsons method in the dev forum. It's worked out for me perfect. The only thing different is that i'm running v6xxx CWM now instead of v5xxx
Did you try going to recovery using terminal emulator? Try doing so if are rooted.
Open the terminal emulator then type su
Now type reboot recovery.
See if it still takes you to the 3e recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
krips2003 said:
Did you try going to recovery using terminal emulator? Try doing so if are rooted.
Open the terminal emulator then type su
Now type reboot recovery.
See if it still takes you to the 3e recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
after seeing 3e recovery using keys (Vol-Up+home+power), I tried adb shell->su->reboot recovery but it still took me to 3e recovery.
Gadgetz said:
No idea...what I would do though is Odin back to stock and then root and install CWM via mrRobinsons method in the dev forum. It's worked out for me perfect. The only thing different is that i'm running v6xxx CWM now instead of v5xxx
Click to expand...
Click to collapse
The reason i used debugfs attack for root is that I didn't have to re-install/configure all apps already installed. I have TiBu but still have some doubts about restoring with user app+data.
I guess what you suggested will work, I just want to see if there is an easy to solve my problem.
btw, if you could point me to v6xxx, I will try that version.
rivendell said:
The reason i used debugfs attack for root is that I didn't have to re-install/configure all apps already installed. I have TiBu but still have some doubts about restoring with user app+data.
I guess what you suggested will work, I just want to see if there is an easy to solve my problem.
btw, if you could point me to v6xxx, I will try that version.
Click to expand...
Click to collapse
If you just odin the root injected LG1 via mrRobinsons method everything will remain as far as apps and data.
via my ParanoidedAndroided GS3
Found the problem and solution
I think I may have found the problem and solution to this CWM lost issue: while I was flashing CWM to the last version as of writing, 6.0.1.2, I noticed that at adb command "reboot recovery" after the "dd" command, it did reboot into the 6.0.1.2. Then when I click "reboot normal", the next screen alerted me something like "flash stock recovery at reboot" and so I selected the default "Disable recovery flash", and then after that, the CWM recovery seems to stay.
In short, after manually installing CWM with ADB command, I had to immediately reboot into recovery (with ADB) and run reboot normal once to disable the stock recovery, and that's the solution.
Just want to share it, though none of those posts about installing CWM mention that at all.
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?
Hi hoping someone can help, I accidentally wrote the wrong file to my system partition and am stuck at smartwatch 3 logo.
i tried pc companion and it tells be there "no software available for my device" all i can get to is fastboot mode stock recovery is gone too
I wrote twrp to it but as of yet have not been able to launch it. its running 5.1.1 os and i cant remember build number other than it began with an L
Please help
ZR1
if you read this and know i have no hope please let me know that too please
seems like if i had stock partitions images i could flash using adb i"d be good yes?? no?
I do not have time to help right now, but since you can get to fastboot, you are probably fine. Find the stock 5.1.1 recovery and boot to it. Then sideload the latest update. You will be good to go.
The command in a terminal window is...
Code:
Fastboot boot <stock recovery.img>
Alternatively, you can boot to twrp and install a twrp flushable zip.
Good luck.
Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.
zr1 said:
Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.
Click to expand...
Click to collapse
Have you tried Sony Companion to repair your watch?
If you were running 5.1.1, then the recovery you mention is for 5.0.1, so that might be the reason why you can not boot into it. See if you can find the stock recovery for 5.1.1
I have used the following method a couple of times now to get me out of trouble after playing around with my SW3
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
You can then use the stock recovery you already have and update via OTA files to get it back to the latest firmware or via Sony Companion.
I had the exact same issue after I did fastboot flash using corrupt system.img (which wasn't a snapshot that could be flashed but rather a tarball). Since you have TWRP installed you can confirm this by trying to mount system partition in recovery mode. After it fails, connect to recovery via adb and view latest kernel messages (dmesg). It should show something like "failed to locate ext4 filesystem".
If this is your case, you can use TWRP restore function to restore system from your TWRP backup. It will then erase the partition, mkfs.ext4 and write the files from tarball. This did the trick for me.
(If you don't have backup, try looking for downloads in other threads here)
Edit: Re-read your post. Since your TWRP is broken, try hotbooting it using fastboot boot new_boot.img (you can take it here)
ebones thank you thank you thank you
I had downloaded new_boot img already so im not sure what i was doing wrong but i did what you said and she booted right into TWRP i now have to sideload the right update.zip file and run it in twrp correct?
edit; having trouble sideloading wear-supersu.zip what is the correct command?
GOT IT!!! I installed stock rom from this thread http://forum.xda-developers.com/sma...rom-repacked-stock-rom-swr50-version-t2988087 through TWRP and it works cant thank you guys enough
Thanks ZR1
I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks
rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else
rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not