my phone is rooted for a few months and now i decided to reset my device after restart i am stuck in cwm recovery loop.
cwm recovery is working and is displayed every time i restart
odin is not detecting my device
usb debugging is off as it has been reset
please help
used pdanet+ from http://forum.xda-developers.com/show....php?t=1983470
and minimal adb from http://forum.xda-developers.com/show....php?t=2317790
tried some commands like restart bootloader
dont know what to do ahead
any commands to flash stock recovery or delete cwm recovery from phone using adb or cwm
EncryptedWonderkid said:
my phone is rooted for a few months and now i decided to reset my device after restart i am stuck in cwm recovery loop.
cwm recovery is working and is displayed every time i restart
odin is not detecting my device
usb debugging is off as it has been reset
please help
used pdanet+ from http://forum.xda-developers.com/show....php?t=1983470
and minimal adb from http://forum.xda-developers.com/show....php?t=2317790
tried some commands like restart bootloader
dont know what to do ahead
any commands to flash stock recovery or delete cwm recovery from phone using adb or cwm
Click to expand...
Click to collapse
As far as CWM works properly, connect phone to your computer and "mount usb storage" you can install a recovery that provides "reboot to download mode"
In case you have Samsung i8552 as i read in your profile info this --> CWM 6.0.4.7 flashable ZIP is the latest recovery for your phone.
Question: Have you tried entering "DOWNLOAD" mode manually by pressing "Vol down + home + power" while device is turned off?
in download mode my phone is not recognised because usb debugging is off after reset
used samsung driver and pdanet+ driver
only in cwm recovery is phone detected
using cwm recovery installed custom rom even after that phone enters cwm recovery loop
i had deleted cache partition and followed instructions for the rom
update:
after using kies,odin detected my phone
after that successfully flashed stock recovery
all is well now
Related
Please help! I am new to this and am worried I bricked my phone.
I successfully rooted my Verizon Samsung Galaxy Nexus using a toolkit. It was then working fine with 4.2.2. I wanted to install Shiny Rom 4.4.2. I thought I successfully backed up apps and data using Titanium Backup.
I successfully moved the correct zip files to my phone, and realized I needed Clockworkmod recovery. I followed a procedure to get this on my phone by using my computer's command prompt. I successfully booted into Clockworkmod recovery and followed the process of wiping data/factory reset, successfully installed radio and bootloader recommended to install with ShinyROM but got stuck and could not install the ShinyROM itself. I think it is because it requires a later version of Clockworkmod. The one I downloaded using the procedure was 5.5.0.4, but I think I need a later version. I tried following the same procedure using my computer's command prompt and it got stuck at "waiting for device". I cannot get out of Clockworkmod recovery now (even battery pull, etc.). I then found some threads saying I need to restore my old ROM first. (I think) the only ROM on my phone is ShinyROM. I am stuck and stressed out because I do not know of a way of "pushing" the new version of Clockworkmod to my phone.
Can I fix this, or do I need to start shopping?
[email protected] said:
Please help! I am new to this and am worried I bricked my phone.
Can I fix this, or do I need to start shopping?
Click to expand...
Click to collapse
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
memaro_maro said:
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
Click to expand...
Click to collapse
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
[email protected] said:
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
Click to expand...
Click to collapse
set up fastboot and flash twrp then.
xzilem said:
set up fastboot and flash twrp then.
Click to expand...
Click to collapse
Thanks. I found another thread that led me to the same conclusion, except I was able to do it with CWM and fastboot the latest version using ADB sideload. I still haven't posted enough to link, but here were the details from user camblue.
"
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not" have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
"
Successfully rooted my device and went onto flashing cwm for it.
used recovery manager as suggested by many users.
recovery manager app deleted the stock recovery and did not flash anything else in its place
So...
No recovery
Holding Vol up & down buttons dont take me to Recovery or fastboot mode.
the phone simply reboots.
Tried flashing the recovery with adb by command prompt
but the device simply doesnt reboot into fastboot mode.
Need Solution over this problem ASAP:crying:
I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.
Was updating my phone tonight and saw that it was recommended that I update TWRP first.
I did what I thought was a manual update of TWRP which turned out to be flashing the TWRP image to the bootloader and the recovery. Dumb mistake but oh well. Now my phone will boot up into the boot menu (reboot/boot to bootloader / download mode / recovery mode / power down). When I boot into bootloader or recovery, the phone simply reboots to the same menu. When I reboot to download mode, it takes me to another similar menu.
Although my computer recognizes some kind of connection from the phone, I have be unsuccessful in getting ADB to recognize my device.
I have tried downloading the stock RUU (http://www.htc.com/us/support/rom-downloads.html) but I am having trouble running the .exe. At times it says my phone's battery is too low to continue, and other times it simply says USB cable error. I have tried multiple cables and different computers.
Any Suggestions?
I ended up trying a few different combinations of RUU and USB cable, eventually one worked and I was able to factory reset back to the original rom.
Thanks for anybody who came in here to take a look
Try to flash rom with rom RUU.zip
i have oppo r7S and iam unable to boot into Recovery mode ans fastboot
my phone is not rooted
please help me to install a recovery
pmal19 said:
Was updating my phone tonight and saw that it was recommended that I update TWRP first.
I did what I thought was a manual update of TWRP which turned out to be flashing the TWRP image to the bootloader and the recovery. Dumb mistake but oh well. Now my phone will boot up into the boot menu (reboot/boot to bootloader / download mode / recovery mode / power down). When I boot into bootloader or recovery, the phone simply reboots to the same menu. When I reboot to download mode, it takes me to another similar menu.
Although my computer recognizes some kind of connection from the phone, I have be unsuccessful in getting ADB to recognize my device.
I have tried downloading the stock RUU (http://www.htc.com/us/support/rom-downloads.html) but I am having trouble running the .exe. At times it says my phone's battery is too low to continue, and other times it simply says USB cable error. I have tried multiple cables and different computers.
Any Suggestions?
Click to expand...
Click to collapse
My HTC One M9 no enter recovery and bootloader only show battery and bootloop and I can't flash via recovery or bootloader or RUU, so my question is if exist the tool to flash something to sdcard with Win32DiskImager.exe + debrick.img to boot from sdcard so I made this before with samsung SGH-I747 that recover to the live that phone
Hi all,
I have a Lenovo TB3-730X tablet.
Recently I wanted to flash a custom ROM but it turned out it was not compatible and the tablet was messed up.
What I did before reaching at this messed up state was:
1) Flash TWRP recovery
2) Copied the custom ROM into SD card and installed it, the installation failed and boot failed. The tablet stuck in the logo screen forever
3) I tried to install the stock ROM back using PC and SP Flash Tool but the latter never managed to connect to my tablet.
4) I manually copied the system.img and boot.img from stock ROM into SD card and tried to install them manually using TWRP by selecting "System Image" and "Boot" partitions respectively. After this and before rebooted the tablet, TWRP reported that "No OS is installed". I went ahead and rebooted the tablet anyway and now it keeps restarting. It shows the logo screen for few seconds and then restarts over and over again. I cannot connect to TWRP recovery mode anymore as the Volume-UP / Volume-DOWN + Power button are being ignored. I am not sure if the TWRP was gone after flashing the boot with boot.img. Also the tablet cannot be connected to the PC at all because it keeps restarting and it doesn't get stable to the logo screen as before so that the USB connection cannot be established. This means I cannot use "adb" from PC to connect to recovery mode using "adb reboot recovery" command
I really stuck here and would appreciate any help.
Thanks in advance!