Develop Bugs

G2 clockwork recovery

My phone is permanently rooted using visionary, and I have flashed clock work recovery from rom manager, but when I try to boot into recovery it just shows the phone with the red triangle? Can any one help me.
Thanks
Sent from my T-Mobile G2 using XDA App

From what I have read elsewhere, re-flash Clockwork Recovery.

Doesn't work.
Sent from my T-Mobile G2 using XDA App

You're supposed to only download and flash recoveries from Rom Manager if you're on wi-fi since T-mobile caches web pages but I was able to get around this by flashing an older version (in Rom Manager) and immediately reflashing the correct recovery (without rebooting or even leaving RomManager).
Of course you can always download the recovery.img file and fastboot flash it.

me too
Same issue. Trying to boot into recovery gives pic of phone with red triangle.
- I reflashed clockwork recovery (not sure is this helped)
- manually went into recovery manager from rom manager menu which loaded w/o problems
- selected backup and restore
- perform backup
seems like it is working...

Volume-up + power. If you already did that then i dunno
Sent from my HTC Vision using XDA App

fix permissions in rom manager and reflash clockwork

recovery mode
newbie here, or course. back after 2 years away with BBerry, g2 cant get past recovery. i am looking for a way to get my device to turn back on... basically when i try to fastboot, it say i have the wrong image, or no image, fails to load E: sd card failed. i have acces to another G2 so i can get a copy of the stock rom image but has not worked::: i need assistance in this process. what do i need to load from the sd card to make my G2 turn back on or is this what bricking your device is? i have access to the recovery screen and can still load info from the sd card.
thanks for any info.

Are you saying your rom doesn't boot? Are you s-off? And if so can you get into recovery?
FYI - people generally don't fastboot from the SD, are you sure you were in fastboot mode and not hboot?

[Q] Defy Help Cant load Custom Clockwork

Hey I'm new here but this looks like the best place to be for help......... I recently used superoneclick to root my phone that went just fine. I installed GoAPK custom recovery and granted superuser permissions.......... that went fine too but then when i used defy recovery.apk to boot into recovery i realized that i had not turned of usb debugging mode and now i feel screwed........ I have infinite boot loop, however i can still access stock system recovery and i can access bootloader. but now battery wont charge and it just cycles through the M logo!! is there any way to fix this? if im not online just email me
.

Wipe data and cache partition from the stock recovery. Reflash SBF if still bootloops.
Sent from my MB525 using Tapatalk

Well I flashed sbf once and wiped cache partition and factory reset and it still looped. I also have no way to charge battery from phone what about that? can it be fixed even though i booted to GoAPK custom recovery before usb debugging was turned off? can it be fixed or is it permanantly gone......???????

Bricked_Defy said:
Well I flashed sbf once and wiped cache partition and factory reset and it still looped. I also have no way to charge battery from phone what about that? can it be fixed even though i booted to GoAPK custom recovery before usb debugging was turned off? can it be fixed or is it permanantly gone......???????
Click to expand...
Click to collapse
Go buy yourself a Universal Charger & Charge you battery for 7-8 hours, put it back in defy & your good to go again

instead of buying a external charger u can jus put ur battery in someone elses defy and charge it......i went to the store from which i bought mine and asked one of the employees who owned a defy to charge it for me....after that i flashed a official rom using rsdlite and my phone is working again ....good luck

Ok i have my battery charged. Now can anyone please give me an official sbf with instructions on how to properly flash and fix my phone to stop the boot loop please. you all are being very helpful thankyou. now i just need the necessary steps to flash and fix my phone.

can anyone help

I think you should follow the FAQ. First try to wipe data from stock recovery. (Volume down when you turn the phone on) If you done that as i read what sbf did you flased(exact wersion)? Wiped after flasing the sbf?

I don't remember what sbf i flashed. I do know that after i flashed the sbf I had used stock recovery to wipe cache partition and factory reset but I still have the boot loop. I need a new sbf to flash to it

Try to remember. because if you flashed gingerbread or eclair that can cause problems. If you flah a proper sbf for your device it will work.
Sent from my MB525 using XDA App

There is a T-Mobile stock 2.2 SBF in the Developer forum. Use the search button it wont bite.
Sent from my MB525 using Tapatalk

I dont remember which one it was but i know for sure that it was not a gingerbread or eclair sbf. so thats out of the problem. i installed custom clockwork GoAPK and hit boot into recovery but my phone had usb debugging on and then it went to boot loop. so do you have a proper sbf i can use. that way i can load the custom clockwork without usb debugging on and flash custom rom on it?

Hey guys i fixed my phone found a good sbf. how do i load custom clockworkmod and how do i flash custom rom.
Sent from my MB525 using the XDA mobile application powered by Tapatalk

Bricked_Defy said:
Hey guys i fixed my phone found a good sbf. how do i load custom clockworkmod and how do i flash custom rom.
Sent from my MB525 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
i prefer the 2ndinit method from here (step 2):
http://forum.xda-developers.com/showthread.php?t=1065798
since your phone is already rooted you can start from enable usb debugging but skip the superoneclick and reboot bit and go straight to installing 2ndinit, and so on.
have fun
edit: sorry, you should start from copying your preferred rom and gapps to the sd card first.

i am using 2nd init. works just fine

ok cause when i use the system recovery method i get boot looped. and rom manager wont work unless i manually install a custom clockworkmod
Sent from my MB525 using the XDA mobile application powered by Tapatalk

Stuck on Motorola logo

This is another one of those stuck on Motorola Logo thread. I tried to search but could not find a problem similar to mine.
I have a rooted defy in India, which was running 2.2.
I followed the steps given in one of the guides here, rooted the phone and installed CM7 on it.
Things were going well for a month now but today I decided to play around with it. I installed the recovery here http://forum.xda-developers.com/archive/index.php/t-944543 and made an android backup. I rebooted the phone but was getting into the M logo with blue LED flashing for a while. I pressed the vol down and entered into boot menu and changed the default to "normal stock". Now I can not boot my phone and am stuck on M logo. I can go to stock recovery though.
What do I do from here? Any help would be greatly appreciated.

CM7 has 2ndinit preinstalled which consists of a custom recovery menu. Why don't you guys read FAQs.
Here's what you can do. Enter the Bootmenu goto Custom recovery and reinstall CM7, you wont lose your apps and settings. Wipe Dalvik cache and reboot.
Sent from my MB525 using Tapatalk

I can no more access custom recovery. If I press the power button, and vol down, I get the triangle with exclamation from where I can go to stock recovery.
Sent from my HERO200 using Tapatalk

why did you install that recovery!!!!?? cm7 already has it!! if you dont mind to lose your data, i think you should reinstall cm7 from the begining, cause i'm pretty sure wipe data from stock recovery wont work

Thanks for the help. I only had stock recovery, which does not have the option for nandroid. That's the reason I flashed this recovery. I don't mind losing data. Where do I begin? The only thing I can access right now is stock recovery.
Sent from my HERO200 using Tapatalk

Thanks everyone. Problem solved. Installed RC 1.5 this time.

[Q] Bricked & out of ideas

I'm pretty new to installing ROMs and I seem to have screwed something up. I was trying to install CM10 but it didn't work. I wiped system and installed from my sd card and all I got was a black screen. I went to restore from my backup, but somehow it got corrupted. I've tried flashing different ROMs, following youtube tutorials, even tried the ROM Update Utility, but no luck.
I'm out of ideas... any help for a poor, ignorant beginner?

Are u able to get into bootloader?if yes,then again flash cm10 and flash the Hellboy kernel,this step u missed that's why it isn't booting.
Sent from my HTC One V using xda app-developers app

mihirengg19 said:
Are u able to get into bootloader?if yes,then again flash cm10 and flash the Hellboy kernel,this step u missed that's why it isn't booting.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
I can get into bootloader. I tried as you said and flashed cm10 and then the hellboy kernel. Now it goes to the white htc screen w/ the red lettering... any ideas?

For going into bootloader press and hold power for 10+ seconds and when screen goes black release power and press and hold volume down until u get into bootloader.then select fastboot from the menu and then flash kernel.then go back to bootloader and from there go into recovery and do a full wipe and then flash cm10
Sent from my HTC One V using xda app-developers app

mihirengg19 said:
For going into bootloader press and hold power for 10+ seconds and when screen goes black release power and press and hold volume down until u get into bootloader.then select fastboot from the menu and then flash kernel.then go back to bootloader and from there go into recovery and do a full wipe and then flash cm10
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Same result... it seems like everything's working when I do it, but when I reboot I just go back to the same screen w/ the red letters.

i'll help you:
these steps are to be made in the EXACT order:
reboot into bootloader, flash Hellboy latest kernel (for GSM if you are GSM, i don't know if this kernel is for CDMA also. If you have CDMA, please flash Super Sick kernel).
after the kernel is installed, use the menu to reboot to your recovery or use adb and type
Code:
fastboot reboot recovery
when you are in the recovery, do these:
factory reset
wipe system
flash the desired rom - in your case CM10
reboot the phone
let it stay for 1 min after the reboot
reboot again in the recovery (use the menu from within the rom to reboot to recovery)
flash gapps package for jellybean;
reboot the phone
the phone will now stay a little longer until it reboots because dalvik will decompile the google apps you've just installed.
congrats, your phone is working
P.S: the line to flash your kernel onto your device, is:
fastboot flash boot boot.img (you have to rename the kernel you downloaded to "boot.img")

Why u know post in correct sections
Sent from my One V using xda premium

1ceb0x said:
i'll help you:
these steps are to be made in the EXACT order:
reboot into bootloader, flash Hellboy latest kernel (for GSM if you are GSM, i don't know if this kernel is for CDMA also. If you have CDMA, please flash Super Sick kernel).
after the kernel is installed, use the menu to reboot to your recovery or use adb and type
Code:
fastboot reboot recovery
when you are in the recovery, do these:
factory reset
wipe system
flash the desired rom - in your case CM10
reboot the phone
let it stay for 1 min after the reboot
reboot again in the recovery (use the menu from within the rom to reboot to recovery)
flash gapps package for jellybean;
reboot the phone
the phone will now stay a little longer until it reboots because dalvik will decompile the google apps you've just installed.
congrats, your phone is working
P.S: the line to flash your kernel onto your device, is:
fastboot flash boot boot.img (you have to rename the kernel you downloaded to "boot.img")
Click to expand...
Click to collapse
Thanks! One hiccup, when I try to do factory reset it fails saying, "unable to mount '/sd-ext'. What does that mean?

Okay, I think I'm getting closer! I guess the twrp recovery I was using was bad or bad for my phone, because I flashed an old version and on reboot it went into loading the rom, I guess from a previous flash. I went back into bootloader, flashed supersick kernel, factory reset, wiped system, went to recovery and flashed the rom. I let it reboot and now it's stuck in a boot loop. I went ahead and put it into recovery and flashed gapps and rebooted. Still in a boot loop. Any ideas now? I really appreciate the help...

Try with Cwm...
Sent from my One V using Tapatalk 2

http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.4.5-primou.zip
this is the latest CWM Recovery for HTC one V GSM *(primoU)
http://goo.im/devs/maxwen/CM10-primou/boot-HELLBOY-CM10-201212011716.img
Hellboy Kernel for CM10 *from maxwen's post.
http://d-h.st/FSE
All in one tool for HTC one V
so, to start, reboot in recovery by using volume DOWN + Power. Once you are in the bootloader press fastboot and plug the USB cable in the phone ( you will see fastboot will change into "fastboot usb") then open the All in one tool and flash the kernel from the link, flash the recovery from the link *(all in one v interface is prety intuitive you cant get lost). and after you do this follow Icebox's steps into CWM. Factory reset, wipe data, flash room, reboot, flash gapps, reboot. enjoy phone!
thanks to all the devs that created these tools !

bahubali67 said:
Try with Cwm...
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Same bootloop....
Oh and it said it couldn't mount "sd-ext" during the wipe

I have the could not mount error in CWM sometimes aswell, but what i do is, factory reset, reboot in recovery, wipe data, reboot in recovery, flash rom, reboot to ROM, reboot recovery, flash gapps, reboot rom.

rzarectha said:
I have the could not mount error in CWM sometimes aswell, but what i do is, factory reset, reboot in recovery, wipe data, reboot in recovery, flash rom, reboot to ROM, reboot recovery, flash gapps, reboot rom.
Click to expand...
Click to collapse
Still boot loopin'.... but the loop is getting longer at least..

did you try to flash the recovery provided in the All In One tool ? there's a recovery image included in the archive there, try to flash that recovery and with that recovery see if you can run the reset to factory

rzarectha said:
did you try to flash the recovery provided in the All In One tool ? there's a recovery image included in the archive there, try to flash that recovery and with that recovery see if you can run the reset to factory
Click to expand...
Click to collapse
I forgot to mention that I'm virgin mobile cdma version so I can't use that cwm because it's gsm, right? I'm also flashing supersick kernel instead of hellboy. Can I use hellboy with cdma?

gdubya9 said:
I forgot to mention that I'm virgin mobile cdma version so I can't use that cwm because it's gsm, right? I'm also flashing supersick kernel instead of hellboy. Can I use hellboy with cdma?
Click to expand...
Click to collapse
U must use cdma kernel. (for gsm, there different. Kernel)
Sent from my One V using Tapatalk 2

ah sorry, i did not know you are primoC, in allinone you also have a CDMA recovery, i dont know about the CDMA kernel but everyone talks about supersick so yeah, try to research what version of supersick you need for CM10 and flash that one

Well, I seem to just be going in circles... nothing I've tried has worked.. still getting boot loop. Flashing supersick and CM10 hasn't worked. I've tried it with cwm and twrp. My factory reset still says failed to mount sd-ext.

I dont know how much different is primoc from primou, but i remember i had a reset to factory in the bootloader aswell. and, as i said, i had the problem with mounting but i rebooted recovery and did each task (reset, flash) in a new recovery boot. i am brainstorming here but i am out of ideas, we are missing something here clearly, but as long as you have acces to the bootloader hope is not lost

Not Loading up issue

Hi there, hopefully some one could help, i have a galaxy w i8150,The issue is when you turn the phone on its not loading android,it sticks on the samsung logo.i have tryed a factory restore using the recovery utilities but to no avail still sticks,now the question is how do i reload the OS or even the ics upgrade without being able to install clock work and or root the phone?
Please help

all im telling you will b depending on the ability to get to ur recovery or at least download mode
1st if u already have CWM recovery and able to access it then go pristine then install any custom rom you want
2nd if u dont have CWM recovery or you can't access it then ull have to go to download mode and install the recovery from thr (using odin of course) then do 1st step
3rd if its not working for you then install stock rom using download mode and odin
4th if u can't even get to download mode then ur hard bricked

So, from what I read I know that you're just having a soft brick. You want to keep your warranty by not rooting or installing a custom recovery, right?
The only possible way is to flash a stock Rom using Odin. You can't upgrade to ICS because we don't have any stock ones, so as soon as you upgrade you get root and lose you warranty.
Hope I helped
Sent from my GT-I8150 using xda app-developers app

1st step. Chill down.
Now. Allow your device to remain idle with battery removed for around 30 minutes.
If you already had CWM. Do these accordingly.
1. Fix permission
2. Wipe cache
3. Wipe data/Factory reset
4. Wipe everything wipable in Mounts& Storage list(EXCEPT EXTERNAL SD).
5. Wipe dalvik
6. Wipe cache again
7. Fix Permission(above is the Pristine Method)
8. Restart Recovery
9(optionA). Flash your ROM in if you want custom(and gapps in needed) Then fix permission again.
9(optionB). Quit recover and enter download mode and Restore stock ROM in using ODIN.
If I did not mistake the situation, I experienced similar situations once. At least such steps got me out of it.