Sooo, I got my OTA update for Tiny's CM rom today from GooIM. And low and behold... now I can't seem to access my Clockwork Recovery Mod. I enter Rom Manager, order it to reboot to Recovery, and comes to Fastboot. Or, the two finger salute, Pwr/DnVol yields the same result.
Now the phone insists that it's still Soff, Hboot 0.92, and the like... Rom Manager insists that ~it~ can detect CWM 5.0.2's presence, but any attempt to actually boot into it just results in me ending up on the Fastboot screen.
After various attempts at battery pulls and and at reinstalling RomManager and CWM, I tried instead to flash in an image for TWRP both from the GooIM app, and from ADB. That went nowhere as the phone just keeps returning remote access denied type errors in ADB, and merely booted to fastboot and stayed there till I rebooted it normally when done via the app.
Also, the refresh feature seems to have gone kerplooey. From within the rom it just restarts and sends me to the fastboot screens when I ask it to go nuclear, and if I try it from the fastboot screen, it just restarts.
So, I could use some help at this point on how to retake control of my Dinc. Right now I can't change rom's, wipe the caches, etc...
eoraptor said:
Sooo, I got my OTA update for Tiny's CM rom today from GooIM. And low and behold... now I can't seem to access my Clockwork Recovery Mod. I enter Rom Manager, order it to reboot to Recovery, and comes to Fastboot. Or, the two finger salute, Pwr/DnVol yields the same result.
Now the phone insists that it's still Soff, Hboot 0.92, and the like... Rom Manager insists that ~it~ can detect CWM 5.0.2's presence, but any attempt to actually boot into it just results in me ending up on the Fastboot screen.
After various attempts at battery pulls and and at reinstalling RomManager and CWM, I tried instead to flash in an image for TWRP both from the GooIM app, and from ADB. That went nowhere as the phone just keeps returning remote access denied type errors in ADB, and merely booted to fastboot and stayed there till I rebooted it normally when done via the app.
Also, the refresh feature seems to have gone kerplooey. From within the rom it just restarts and sends me to the fastboot screens when I ask it to go nuclear, and if I try it from the fastboot screen, it just restarts.
So, I could use some help at this point on how to retake control of my Dinc. Right now I can't change rom's, wipe the caches, etc...
Click to expand...
Click to collapse
Reflash cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot.
How to flash - http://pvillecomp.com/?page_id=79.
Then see if you can access it. If you can do a full wipe, and then either restore a backup or flash a rom of your choosing.
I would aslo recommend using Team Wins recovery now its more user friendly has some tools you might find handy and well touch based lol
Sent from my rooted GameBoy Color!!! ^¬^
Took me a month, but I finally got past both my frustration and some meat-space interruptions. Yes, the instructions provided by cmlusco did the trick, thank you SOOOO much.
And ironically, I WAS going to install TWRP onto the device, elzimmer, but when I booted it up, it said it had the OTA update to install, so I let it do that first *rolls my eyes* On reboot I found out that that had tanked the recovery mod before I could even begin doing the factory resets and so forth.
Either way, thanks again both of you.
Related
I was running calkulin's rom on my evo but I decided to give cyanogen a run for its money. I was successful in installing cyanogen 6.1, and when i went to go install the addons, they didn't install properly for whatever reason. I went back into recovery mode and did a wipe of the device and went to install a fresh install of culkulin .. but instead of selecting the item "install zip from sd card" i selected "install update.zip" even though I didn't have an update.zip on my device.
After it tried to do that, it asked me if i wanted to reboot, i selected yes, and now i can't get into recovery mode. I can get into fastboot, but when i try and select recovery, it goes to the white HTC EVO 4G screen, then it goes to the screen with the phone, a red triangle with the exclamation point. If i press vol up + power, it brings up the menu to install from update.zip, wipe cache, wipe data, and reboot. I've selected all the options, i'm LOST.
i'm on a 2010 macbook pro .. I have windows 7 installed via VMware but it doesn't want to recognize my phone.
I was able to install adb on my mac, but it still can't recognize the phone. Any help is much appreciated, i don't want a $300 paper weight. Thanks!
Somehow your recovery might have been overwritten. Download a recovery image, go into fastboot and run the following command:
fastboot flash recovery recovery.img
Where recovery.img equals the filename of the recovery image.
Amon_RA has a PC36IMG.zip of his recovery so you don't have to use command prompt at all, just go to bootloader and flash.
http://forum.xda-developers.com/showthread.php?t=705026
i don't have a way to access the commands via terminal or dos to my phone. my computer can't recognize my device .. i'd prefer to do this via OSX because W7 via vmware isn't stable on my machine.
where can i download a custom image .. i may be able to run it via unrevoked, but when i run unrevoked, it gives me the error Device "- exec'/system/bin/sh' failed: No such file or directory (2) -" is not supported at this time.
Sounds like recovery is corrupted, download pc36000.img fkr amon_ra 2.2.1, put it into your root folder of sd card and give it go from fastboot.
I am typing name of recovery from my memory, so it can be wrong.
I read other posts about typing fastboot recovery installation commands, but you have said your adb is not working, so give this a try.
Sent from my PC36100 using XDA App
I'm not sure how to get adb running on the mac but it should be fairly easy. I'd read up on getting your phone connected with adb/fastboot then get the custom recovery img file.
Then you'll do:
fastboot flash recovery recovery.img
(I'm not sure if amon has a readily available image file but you can get the img file for clockworkmod for the evo here: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Just click the evo link, copy it to your fastboot folder and rename it to recovery.img just to make it easier.
Edit, if you have an sdcard apater (or maybe put the card in a digital camera or something so you can access it) you can put this PC36IMG.zip file on it: http://www.mediafire.com/file/s3vsgfwcz5po8hs/PC36IMG.zip
then boot your phone with boot loader, it'll scan the file and hit volume up to apply the update.
Had issue yesterday, my phone would boot directly to fastboot. My issue was a corrupted SD card. I bought a new one and it did the same thing but was able to reformat and it works! Never had this issue until i start pushing dalvich cache to SD. Anyhow check your SD card, try another on see if you can boot a zip from fast boot.
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
dizzle247 said:
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
Click to expand...
Click to collapse
Glad to hear. Disaster averted
dizzle247 said:
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
Click to expand...
Click to collapse
He never said what worked. I am having the same issue and would like to know what worked.
Im actually stuck on the htc evo screen. I can access fastboot as well. Where do i go from there.
I'm having almost the exact same problem as dizzle247. I've tried to flash PC36.img and tried using a new recovery.img but it keeps on sending back to the beginning. I don't know if the fact that my phone is set to S-on has anything to do with it but if I try to switch it off it fails.
Please help
The same thing happened with my phone. How did you end up solving the problem?
If you're in that situation, gona have to run an RUU.
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
GrooGrux said:
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
Click to expand...
Click to collapse
Unfortunately, most people that had this problem were never able to get out of it. It happened mainly on AOSP based roms. I'm typing in past tense because it was a fairly common problem a few months ago, haven't heard much about it since.
You can try running an RUU. If it doesn't work and you have insurance, you may need to take it in and eat the $100 deductible.
Some people were flashing radios through hboot and pulling the battery until the device wouldn't even turn on, then taking it in.
However you want to handle it is up to you. I wish that someone had found a solution, but I'd try everything you can find before taking it in. Every phone is different, something may work for yours.
Sent from my PC36100 using Tapatalk
hmmm, can any1 shed some light as to WHAT worked? other ppl have same problem, it would help if they stated the actual solution lol.
tooill said:
hmmm, can any1 shed some light as to WHAT worked? other ppl have same problem, it would help if they stated the actual solution lol.
Click to expand...
Click to collapse
There is no solution most of the people that have had this happen got a replacement
Sent from my PC36100 using XDA App
ugh >.<, i wanna fix mines and sell it, i cant replace it.. i bought it and had it flashed for boost, but now it has that problem so idk what to do with it..
Same problem need help evo4g
GrooGrux said:
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
Click to expand...
Click to collapse
I'm having the same issue need some help
Hi,
I hope this isn't a repeat, but I've searched here and Google to no avail. It may be I'm not searching the right things, because I'm not quite sure how to succinctly describe this problem.
I've rooted my DInc, with S-Off enabled. I'm running CyanogenMod 6.1 now, installed from ROM Manager, which is no version 3.0.0.7. I've got ClockworkMod 2.5.1.2 installed as well. When I first rooted my phone, etc. about a month ago, I made a nandroid backup, so I figure its time to make another one. Open ROM Manager, go to Make a New Backup, choose a file name, it reboots into Fastboot. If I then select "Reboot" by pressing the Power button, the phone boots back to Cyanogen and there is no (new) backup file in the clockworkmod/backup directory, where I expect it.
If I select "Bootloader" from the Fastboot menu, it takes me to the HBoot menu, with the options "Fastboot", "Recovery", etc. Then, an error message appears very quickly, about missing PB31IMG.zip files. I'm not sure about the exact text of the message since it disappears so quickly, but I've searched around and it seems to be because that file is missing from the root of my sd card (I checked on Windows, its not because the file is renamed to .zip.zip or something). Solutions such as formatting the sd card to FAT32 (it is, according to Windows) and reflashing ClockworkMod from ROM Manager do not help.
After the error message disappears, I am able to select "Recovery" from the HBoot menu, and the screen flashes the white with black text "HTC Incredible" startup screen before dropping me back into the Fastboot menu. At this point, I usually just give up and reboot and keep using the phone as normal.
Does anyone have any idea where the problem lies? Can someone link me to the proper PB31IMG.zip file for my phone/ROM/radio?
Radio: 2.15.00.07.28
HBOOT - 0.92.0000
Thanks!
Have you tried reflashing ClockworkMod from within ROM Manager?
Personally, I've never had this happen, sorry if reflashing doesn't help
dmbhaggis said:
Have you tried reflashing ClockworkMod from within ROM Manager?
Personally, I've never had this happen, sorry if reflashing doesn't help
Click to expand...
Click to collapse
Yeah, that's how I was reflashing ClockworkMod. Thanks anyways.
Try going into ROM Manager go all the way to the bottom to All clockworkmod recoveries and try flashing a different version of CWM Recovery...
jackbtha1 said:
Try going into ROM Manager go all the way to the bottom to All clockworkmod recoveries and try flashing a different version of CWM Recovery...
Click to expand...
Click to collapse
Flashing back to 2.5.1.1 appears to have worked...does anyone have any idea why 2.5.1.2 is apparently broken (probably just on my device)?
Thanks!
I've seen other people reporting problems with 2.5.1.1 & 2.5.1.2 on amoled devices. They've suggested going back to 2.5.0.5.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
my bad didnt see last part
darthbith said:
Hi,
I hope this isn't a repeat, but I've searched here and Google to no avail. It may be I'm not searching the right things, because I'm not quite sure how to succinctly describe this problem.
I've rooted my DInc, with S-Off enabled. I'm running CyanogenMod 6.1 now, installed from ROM Manager, which is no version 3.0.0.7. I've got ClockworkMod 2.5.1.2 installed as well. When I first rooted my phone, etc. about a month ago, I made a nandroid backup, so I figure its time to make another one. Open ROM Manager, go to Make a New Backup, choose a file name, it reboots into Fastboot. If I then select "Reboot" by pressing the Power button, the phone boots back to Cyanogen and there is no (new) backup file in the clockworkmod/backup directory, where I expect it.
If I select "Bootloader" from the Fastboot menu, it takes me to the HBoot menu, with the options "Fastboot", "Recovery", etc. Then, an error message appears very quickly, about missing PB31IMG.zip files. I'm not sure about the exact text of the message since it disappears so quickly, but I've searched around and it seems to be because that file is missing from the root of my sd card (I checked on Windows, its not because the file is renamed to .zip.zip or something). Solutions such as formatting the sd card to FAT32 (it is, according to Windows) and reflashing ClockworkMod from ROM Manager do not help.
After the error message disappears, I am able to select "Recovery" from the HBoot menu, and the screen flashes the white with black text "HTC Incredible" startup screen before dropping me back into the Fastboot menu. At this point, I usually just give up and reboot and keep using the phone as normal.
Does anyone have any idea where the problem lies? Can someone link me to the proper PB31IMG.zip file for my phone/ROM/radio?
Radio: 2.15.00.07.28
HBOOT - 0.92.0000
Thanks!
Click to expand...
Click to collapse
I have the exact same problem, except my hboot reports as 0.78 I believe. Either way, the hboot menu is as far as I can get. Any other selection causes continual reboots. This started happening after a spontaneous reboot while driving down the road. I wasn't even using the phone. I do have the latest Clockwork on it, but it really doesn't matter because I can't get to the Clockwork menu anyway. Just the fastboot menu.
It says that USB is enabled in the hboot menu, but with it plugged into my PC, it won't show up in Windows. It's obviously not far enough into the boot cycle to do that.
Any suggestions would be awesome. I see about a dozen other topics started complaining about similar issues. If I leave it sit on the hboot menu, it'll sit there forever and is stable, so I don't believe it's a phone issues. It's almost like, if it were a PC, the boot sector is messed up and it needs an fdisk /mbr. I understand, that doesn't work, I'm just pointing out that I believe the behavior to be the same.
Thanks to anyone that can help!
I guess that, with no way to get into Clockwork and no way to replace Clockwork, I'm kind of stuck. Replacing Clockwork was an idea, but I'm not sure how to do that since hboot is all that's available and I can't choose any options without it rebooting continually. Is there a way to just plug the phone in and reflash Clockwork from my laptop with a Windows app on the laptop?
hackules said:
I guess that, with no way to get into Clockwork and no way to replace Clockwork, I'm kind of stuck. Replacing Clockwork was an idea, but I'm not sure how to do that since hboot is all that's available and I can't choose any options without it rebooting continually. Is there a way to just plug the phone in and reflash Clockwork from my laptop with a Windows app on the laptop?
Click to expand...
Click to collapse
Do you have Rom Manager installed on your phone? If you do you can always use the last option to install a different version of Clockwork. Give that a try...
I can't get past the "hold down and power" menu. That works fine, but anything I pick reboots the phone. I can't get into the OS at all because it just continually power cycles after I choose from the boot menu. I re-flashed Clockwork and no luck and I've re-flashed the entire phone to stock, same thing. It IS stable and the recovery menu you though. I can jump around in the menu, turn USB on and off, etc, just not boot into anything. It's literally like a computer that needs fdisk /mbr as all of the data seems to be where it should be.
I would try to flash any custom and see if that gets the phone to boot normally.
I took the stock build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000 and zipped it as PB31IMG.zip and when it boots, it'll take the images and flash them. It flashes all of the images in the zip and it takes a little bit to do that. Then it goes back to the menu and I restart it and it goes into the cycle again...
Hmmm. I would have used the unrooting guide to go back to stock just to get the phone back up and running and then unroot it again. If you do go that route DO NOT apply the 7.28 radio again because you will brick you phone being that you already have that radio flashed on your phone. What custom ROM or Kernel were you running before all this happened? I would try flashing that again but clear the data and cache first and see if that gets the phone up again.
I'm currently running the latest Senseless Revolution ROM and did upgrade to the latest ROM manager, but haven't flashed anything yet so no problems........yet!
Should I downgrade to CW 2.5.1.2 anyways since it was a bit sluggish when checking for MDsum?
I've read about some people having crazy problems and others actually not reporting anything bad......so what is the verdict? I'm trying to prepare myself first rather than finding out when my phone is stuck
I seem to be having some of the same problems. I upgraded ClockworkMod to 3.0.0.5 and was able to successfully boot into recovery. I installed CM 7 nightly, then ended up restoring to a backup of CM 6.1.
Now I can't access recovery, when I try I get stuck at the white droid incredible screen. My phone can still boot up so I tried downgrading ClockworkMod to 2.5.1.4, but it says an error occurred while flashing the recovery.
any ideas?
nate23 said:
I seem to be having some of the same problems. I upgraded ClockworkMod to 3.0.0.5 and was able to successfully boot into recovery. I installed CM 7 nightly, then ended up restoring to a backup of CM 6.1.
Now I can't access recovery, when I try I get stuck at the white droid incredible screen. My phone can still boot up so I tried downgrading ClockworkMod to 2.5.1.4, but it says an error occurred while flashing the recovery.
any ideas?
Click to expand...
Click to collapse
Are you renaming recovery to PB31IMG.ZIP and updating through hboot?
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
Are you renaming recovery to PB31IMG.ZIP and updating through hboot?
Click to expand...
Click to collapse
thanks, that fixed it!
I have a G2. I decided to root it using the guides on Lifehacker and Cyanogens wiki. I got a temproot using Visionary, and permaroot using terminal. Everything went swimmingly. I only used download links that I found on Lifehacker and on Cyanogen's site (the same places I got the guides to root my phone) I attempted to root my phone and put CM7 on it. I backed up everything with Titanium Backup. I downloaded Rom Manager, flashed ClockworkMod Recovery to get the latest version, downloaded CM7 through Rom Manager, and attempted to install it as well as backup existing ROM and wiping data and cache. My G2 returns to the HTC startup screen and just stops.
I tried to do a factory reset, it just stops at the same area. I tried doing a factory reset from the startup options (power and down volume), nada. I tried reflashing ClockworkMod Recovery, zilch. I restored my backup from Titanium, nothing.
The phone works, I'm able to do everything I would normally do on it, but I just can't get this to work and I don't know where I went wrong or how to fix it. I have experience with UNIX based systems so I know how to work a command line to an extent and I know that part went off without a problem. I just can't figure out what's going on with it.
can you connect to your phone using adb? if you can access the shell you might be able to figure out why it's hanging.
ADB
I'm not sure I've tried ADB, any tips?
Are you talking about hooking it up to my computer as an alternative method to flash it? I had a bit of trouble with that because my computer is currently down (I just moved and don't have the room to set it up yet). I think I need a copy of the original ROM for my phone as well, if I get that I believe I can restart the whole process and do it right this time. Any ideas where to get it?
yes hook it up to the PC, even if it's in a bootloop you might be able to access the phone's system to do repairs using adb to enter the shell.
check this thread: http://forum.xda-developers.com/showthread.php?t=865685
it also explains how to use it
http://developer.android.com/guide/developing/tools/adb.html
this one got all the adb commands.
I'm not sure about the log command, but there's a way to call on the system log to see where it fails.
it's not recommended to flash an original image again, you can try to restore the backup of the original ROM (nandroid backup) if you made one...
hope this can help you.
Sounds like there is a problem with your recovery, try to manually flash recovery using flash_image instead of ROM Manager.
Use this thread for a guide: http://forum.xda-developers.com/showthread.php?t=902493
You can get the latest version of CWM (currently 3.0.2.4) here: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html just scroll down to the link that says "HTC G2"
After you flash try to manually go into recovery by shutting down the phone and powering it up while holding the volume button down, this should bring you into the bootloader menu and allow you to launch recovery.
Thanks!
I'll give that a try as soon as I can, thanks for the assistance!
Hello All,
I recently rooted my EVO3D using the HTCDEV method because the bootloader was version 1.5.
Here are the steps I followed to root (sorry for the copy and past but I want to be as detailed as possible)
Files Used
su 2.3.6.3
TWRP Recovery
Steps Taken:
1)Take both the su.zip and recovery.img files and put them in your sdk tools folder.
2)Now do the following in ur command prompt, hitting enter after each command.
3)Code:adb push recovery.img /sdcard/And,
4)Code:adb push su-2.3.6.3.zip /sdcard/Then,
5)Code:adb reboot bootloaderUr phone will go to fastboot and should look like the after picture above. Now you can flash the twrp recovery, so do,
6)Code:fastboot flash recovery recovery.imgIt will ouput something like this,
7)Code:sending 'recovery' <5068 KB>... OKAY////writing 'recovery'... OKAY///finished. total time: 11.355sNow you have twrp recovery, so you can navigate to it. On ur phone, use the power button to pick bootloader, then scroll down to recovery and pick that. You will then be booted into recovery.
8)Here you can pick "install zip" and then pick the "su-2.3.6.3.zip"
It will flash, the you can pick "back to main menu", then "reboot system now"
9)You will boot back up and have working Superuser. I have had no trouble with Titanium Backup, Root Explorer, Quick Boot or any other app that requires root. Before you do too much, it would be good to go back to recovery and do a Nandroid backup. Always best to get one ready before you start modding anything.
All of this worked fine, and the phone was "unlocked."
Then, I flashed the most recent version of CleanRom (2.7)
Again, the phone worked fine, battery life was a little crappy.
I decided to flash Ziggy's kernel.I flashed the kernel simply by putting on the SD card, and then rebooting into recovery. This worked fine as well, but I noticed some of the buttons for example the menu popups displayed volume where it should have said more, or bluetooth options where it should have said preferences. so this is where the trouble started, I downloaded kernel manager, and flashed silverneedle through that program. Now, I am stuck at the White HTC Splash screen bootloop. The phone turns on and after 15 seconds reboots, and reboots, and reboots.
What Ive attempted:
I have done countless wipes and clears of the dalvik cache and cache
ive formatted the system and the date sections (advanced menu in twrp)
ive reflashed the rom after wiping countless times
ive tried flashing different kernels in recovery to no avail
factory reset and wipe havent helped
im not concerned losing the contents of the SD card
I need help because I already had two phone claims in the past 11 months, and if I claim another lost phone I will lose insurance for life with Asurion (sprint)
anytips or help would be greatly appreciated
i can provide any additional info
Similar situation, Not sure if you've already solved the problem but I'm going to copy paste my solution from another thread...
Hi, I'm not sure if this is the right place to ask but this is a preety derp question. I've gone across the internet and tried a lot of reflashing to repair my sort of "bricked" evo. What happened, was that I had a evo 3d s-on htc bootloader unlocked, with custom recovery -clockwork..anyways I had flashed the leedroid 3d 4.0 rom and It worked the only problem was my wifi, so i attempted to flash another kernel onto it, but I had accidently flashed "Rcmix" kernel which I later found out was cdma =.=. so now my phone keeps rebooting at the htc screen, it would just load up with the green htc letters, then after 10 seconds or so it'd reboot, and then begin the process again. I can boot into bootloader and recovery but whatever I flash doesn't seem to work including restoring my backups...and then the battery died so i couldn't even charge it or go in. But i managed to work out I could load into bootloader from the CMD and the furthest i've gotten to is to have the bootloader show FASTBOOT USB. SO I must be getting somewhere...? I did read that i had to load from the cmd and not just from power+vol down..but I'd appreciate any help towards restoring my phone to the way it is or at least before i flashed the rcmix.
Just a note tho I've tried factory resetting but all i get is that it loads into recovery at the bootloader options i dont get "clear storage" as an option and "restore to factory settings" and what not just boots me into recovery agian.
EDIT:
I Managed to fix the phoneeee!!!..just for future preferences and anyone else who has this problem...
I followed bits and piece of IL DUCE's advice to izzy spun, the important part was booting the recovery from cmd. I wasn't able to "erase recovery" But I tried just booting it,
First I would remove the battery,
Put it back in,
Plug the usb cable in
1. Type command, from your Adb/fasboot folder, "adb reboot-bootloader"
2. After that I made sure my bootloader said "Fastboot USB", and then I issued the command, "fastboot boot cwm-4.0.1.4-shooteru.img" or with whatever recovery you had..
3. From there I restored from my backups my original rom. Rebooting, and fixed.
--- and It worked. At the time I was on clock work recovery, i only had the Revolutionary recovery img. Cwm-4.0.14.-shooteru.img to be exact,
after going in there I just cleared the cache and davlik and then, proceeded to restore my backups (I'm not sure if it would've worked if I had re-flashed the leedroid or a custom rom)
and then I simply rebooted the phone, and it got back into my phones original state before leedroid (as I had Only backedup before then)....
Apologies for the lengthly post, but I guess reading does help, but I've been going nuts before I managed to fix this. Just thought I'd leave this post incase someone were to need this.
Same problem
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
awsomepanda20 said:
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
Click to expand...
Click to collapse
What your going to have to do is flash the original kernel you started with. thats why your in a bootloop
Similar problem
Hi everyone!
I have a kind of similar problem, so I won't post it in a new thread.
Yesterday I rooted my phone following this guide: androidforums.com/evo-3d-all-things-root/494212-complete-newbies-guide-rooting-flashing-evo-3d-roms-kernels-using-fastboot . html (i am not allowed to post links to prevent spam).
I unlocked it with htcdev and installed a custom ROM without getting any errors. After restarting the phone, it got into a boot loop; it showed the starting animations of htc and the ROM and then shut down again.
Here some more information:
-Evo 3d Europe gsm
-hboot 1.5
-s-on
-image version 3.28.401
-installed ROMs using clockworkrecoverymod (as proposed in guide)
I have tried these ROMs (all leading to boot loop):
ICS NonSense
Cyanogen Mod 10 – DisarmedToaster (v. 1.4 and 1.5)
Jelly Bean 3d (by Ubuntuz)
SAD 2.1 DEsenseX
I installed the ROMs by doing:
Connect device via usb > flash boot.img via fastboot (from pc) > clear Cashe/UserData/DalvikVM > install rom.zip from sdcard > reboot
I really don't know what to try
Any ideas how I could install a running Android OS are highly appreciated.
Thx for any help
Problem solved!
Ok, I solved the problem by simply relocking the phone and installing the stock ROM with the RUU.exe
RUU.exe
I'm glad someone else mentioned Relocking before running the RUU. I've read several posts be others that have actually stated that Relocking wasn't necessary but in order for the RUU to take you have to Relock. IF you get a chance check out CoolICS Rom and MeanRom both are pretty good.
Thanks all for the help, had to revisit this issue today.
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk