Develop Bugs

[Q] Rom manager, rom backup and red exclamation point

Hi
I am trying to backup my current rom from my rooted Tmo G2(just for trying because i could get the original rom from the xda wiki.
When i click on the backup rom, my phone reboots and tries to go onto recovery mode, but then i get that black phone and the red exclamation point. after that i cannot do anything.
I have to remove the battery to reboot the phone.
What am i doing wrong here?
thanks

The red exclamation means your still in stock recovery. Reboot the phone, go into ROM Manager and flash the recovery TWICE. I had this same problem and flashing it a second time solved it
Sent from my T-Mobile G2 using XDA App

you are a genius.
I did update the recovery before trying, but this time, i did it twice in a row and that did the trick
thanks again

Same problem but flashing it twice still doesn't fix it?
pretty much what i said above... I have the same exact problem so when i =read this i flashed it twice and still get the red ! arrow when i backup it restarts? any other ideas?

If you get this image, just hit Vol (+) and Power. This will continue you to recovery and you can see whether you are still stock or CW Recovery. I am CW, but I will sometimes get the triangle image.

I think you have to flash twice because of root permissions.
My G2 did not ask me for superuser permission until after it had already downloaded the recovery and was in the process of installing it.
The second time you flash it, ROM manager will already have the superuser permission it needs to successfully install it.
I think that the initial (unsuccessful) installation of recovery is what gets ROM manager to ask for superuser access.
So if you have a way to grant ROM manager su permission before installing, it SHOULD work the first time. I don't really know how to test this theory yet though.

I temp rooted + flashed the recovery part 4 times now, "successful" each time, but on "ROM Backup", the red exclamation mark is the only thing that works..
DesireHD

AlCapone said:
I temp rooted + flashed the recovery part 4 times now, "successful" each time, but on "ROM Backup", the red exclamation mark is the only thing that works..
DesireHD
Click to expand...
Click to collapse
Do you have Desire HD ? If so, you are in the wrong forum, this is the Vision forum (G2/Desire Z).
If you do have a Vision, then I suspect the problem is that you don't have S-OFF. Temp root is enough to run ROM Manager, but not enough to flash a custom recovery.

ok, thanks that might be it - still ..strange that it detects the recovery software as installed after boot - maybe it's just saving the information and fakes it. ?
yes, I am in wrong forum - just searched for this issue, and it seems like it is just the same.
Thanks.

AlCapone said:
ok, thanks that might be it - still ..strange that it detects the recovery software as installed after boot - maybe it's just saving the information and fakes it. ?
yes, I am in wrong forum - just searched for this issue, and it seems like it is just the same.
Click to expand...
Click to collapse
If you don't have S-OFF, then your recovery partition (plus others) is write-protected in hardware. So the software thinks it's writing to it, but the data is just being held in cache. When you reboot the cache is lost so you see the old image (i.e. stock recovery) again.

Remember to have "USB Debugging" enabled, i've just spend over 2hrs tbefore i've figured it out...

I just perm rooted my G2 using the Visonary + gfree (No ADB) method, and it worked on the 1st try. I am also trying to backup my stock rom, and was wondering about the steps. I have ROM Manager, and I know that I need to flas ClockWorkMod Recovery, But do I do it before I attempt to backup my current ROM, or after? Do I need to erase recovery before flashing ClockWork?

omarsalmin said:
The red exclamation means your still in stock recovery. Reboot the phone, go into ROM Manager and flash the recovery TWICE. I had this same problem and flashing it a second time solved it
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
This worked perfectly for me. Thank you!

[SOLVED] Clockwork Recovery won't boot after update

Hey, everyone. After installing the latest Clockworkmod Recovery, I have not been able to boot into recovery. I can still boot regularly just fine, but I'm getting to the point where I'm feeling like a new ROM. I've attempted to access recovery from ROM Manager and hboot, but when the phone reboots, the splash screen hangs. I tried reflashing recovery, but it hasn't helped at all. Anyone have any ideas?

Flash a different version of clock work
Sent from my ADR6300 using Tapatalk

I was going to ask where I could find that, but I see it right in your signature. Thanks a ton!

pickleman77 said:
I was going to ask where I could find that, but I see it right in your signature. Thanks a ton!
Click to expand...
Click to collapse
you can also just flash alternative recoveries in ROM manager

[Q] Weird bootloop issue

Alright, so I dun goofed. If some kind soul could help me with this, or just point me in the right direction.
How I dun goofed:
I used the All-In-One Toolkit to unlock bootloader and flash a custom recovery. After that I pulled the boot.img out of the PrimoC CM10 rom and used the toolkit to flash that as the kernel (I realize now this was extremely stupid).
Symptoms:
Cyanogen loading screen comes up and just hangs there. When hboot runs it says "SD checking...Loading...[PK76DIAG.zip] No image! Loading [PK67DIAG.nbh] No image! etc etc etc" eventually, though, I can access the bootloader and from there, the recovery. But when I try to restore my original set up and then reboot the stock Virgin Mobile rom does the same thing and just hangs on the HTC loading screen.
Details:
-Virgin Mobile (CDMA)
-bootloader unlocked, custom recovery (TWRP v2.2.0)
I've tried everything I can think of. I've used the recovery's restore feature, I've tried to reflash a different kernel. Nothing
Any help would be greatly appreciated. Thanks.

Try cm9 ROM and try to flash the ICS boot.img cm10 causes weird problems sometimes
Sent from my One V using xda app-developers app

basalate said:
Alright, so I dun goofed. If some kind soul could help me with this, or just point me in the right direction.
How I dun goofed:
I used the All-In-One Toolkit to unlock bootloader and flash a custom recovery. After that I pulled the boot.img out of the PrimoC CM10 rom and used the toolkit to flash that as the kernel (I realize now this was extremely stupid).
Symptoms:
Cyanogen loading screen comes up and just hangs there. When hboot runs it says "SD checking...Loading...[PK76DIAG.zip] No image! Loading [PK67DIAG.nbh] No image! etc etc etc" eventually, though, I can access the bootloader and from there, the recovery. But when I try to restore my original set up and then reboot the stock Virgin Mobile rom does the same thing and just hangs on the HTC loading screen.
Details:
-Virgin Mobile (CDMA)
-bootloader unlocked, custom recovery (TWRP v2.2.0)
I've tried everything I can think of. I've used the recovery's restore feature, I've tried to reflash a different kernel. Nothing
Any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
ok do the following
go to the fast boot menu
recovery
factory reset
wipe cache/dalvik cache
go here
http://forum.xda-developers.com/showthread.php?t=1878994
download the ROM
download boot.img
first flash the boot img in command prompt
then don't restart
go to recovery and flash the ROM
now restart
PM me if problem persists

cybervibin said:
ok do the following
go to the fast boot menu
recovery
factory reset
wipe cache/dalvik cache
go here
http://forum.xda-developers.com/showthread.php?t=1878994
download the ROM
download boot.img
first flash the boot img in command prompt
then don't restart
go to recovery and flash the ROM
now restart
PM me if problem persists
Click to expand...
Click to collapse
HOORAY! That did the trick. Thank you so much. My hat is off to you sir. :laugh:

basalate said:
HOORAY! That did the trick. Thank you so much. My hat is off to you sir. :laugh:
Click to expand...
Click to collapse
M glad to help and really glad it worked....hf
Sent from my One V using xda app-developers app

[Q] Is my recovery bricked?

6-7 months ago i had jelly bean(cm) installed on the device, the camera was not working so i decided to restore the backup of my stock 4.0.3.
When i did that everything was working fine, until one day(yesterday) i tried to enter the recovery to flash some custom rom again.
Problem was every time i enter the cwm 5504 i get a lying down android with a red exclamation mark on its belly.
I thought maybe the cwm messed up somehow so i rebooted into the bootloader and with adb i flashed recovery.img(cwm 5504) again.
And i still had that android red triangle problem.. Is my recovery unusable anymore or wut?

IceVip said:
6-7 months ago i had jelly bean(cm) installed on the device, the camera was not working so i decided to restore the backup of my stock 4.0.3.
When i did that everything was working fine, until one day(yesterday) i tried to enter the recovery to flash some custom rom again.
Problem was every time i enter the cwm 5504 i get a lying down android with a red exclamation mark on its belly.
I thought maybe the cwm messed up somehow so i rebooted into the bootloader and with adb i flashed recovery.img(cwm 5504) again.
And i still had that android red triangle problem.. Is my recovery unusable anymore or wut?
Click to expand...
Click to collapse
The stock ROM has a recovery script that will over write your recovery each boot, its been covered quite a bit.
Delete /etc/install-recovery.p or rename it, then install your recovery, it'll stick.
Tapatalked from my HTC DNA - MoKee

pio_masaki said:
The stock ROM has a recovery script that will over write your recovery each boot, its been covered quite a bit.
Delete /etc/install-recovery.p or rename it, then install your recovery, it'll stick.
Tapatalked from my HTC DNA - MoKee
Click to expand...
Click to collapse
Geez pio, you're one of the kindest developers here! The trick you said with the renaming nailed it, i installed cyanosaki 2.3 successfully!
Thank you very much duuude <33

stuck at google logo ?! need help

i had paranoid 4.2.2
then i entered in recovery -> format data (tw recovery 2.5)
pushed with adb rom and gapps (crDroid)
flashed, wiped
all started normally, but at first re-boot -> stuck at google logo :S !
i tried to do everything again and again, stuck...
now i cant flash zip... got "unable to open zip"
and cant push something with adb becouse i got "Read-only file system"
what i have to do !? :S

im the doctor said:
i had paranoid 4.2.2
then i entered in recovery -> format data (tw recovery 2.5)
pushed with adb rom and gapps (crDroid)
flashed, wiped
all started normally, but at first re-boot -> stuck at google logo :S !
i tried to do everything again and again, stuck...
now i cant flash zip... got "unable to open zip"
and cant push something with adb becouse i got "Read-only file system"
what i have to do !? :S
Click to expand...
Click to collapse
Fastboot
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Fastboot
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Fastboot, and... :\ ?
edit
just did a Format data, pushed another rom and seems all went right, but at first re-boot again stuck
what the hell !?

im the doctor said:
Fastboot, and... :\ ?
edit
just did a Format data, pushed another rom and seems all went right, but at first re-boot again stuck
what the hell !?
Click to expand...
Click to collapse
so why dont you flash back to stock with fastboot?

Zepius said:
so why dont you flash back to stock with fastboot?
Click to expand...
Click to collapse
im flashing a 4.2.2 rom, i want to realize if this is a 4.3 problem related or not.

im the doctor said:
im flashing a 4.2.2 rom, i want to realize if this is a 4.3 problem related or not.
Click to expand...
Click to collapse
Believe me stock 4.3 will boot. If it doesn't your phone is dead..
Sent from my Galaxy Nexus using XDA Premium HD app

i flashed 4.3 with WugFresh toolkit, now works fine, btw recovery mode doesn't work,
vol+, vol-, power -> run in recovery -> red triangle with a dead android :\
this means i need to re-flash a recovery ?
if i install goomanager and use "install open recovery script" is enought ?

im the doctor said:
i flashed 4.3 with WugFresh toolkit, now works fine, btw recovery mode doesn't work,
vol+, vol-, power -> run in recovery -> red triangle with a dead android :\
this means i need to re-flash a recovery ?
if i install goomanager and use "install open recovery script" is enought ?
Click to expand...
Click to collapse
That is stock recovery.
If you are rooted, goomanager should be able to flash a recovery. If you are on a stock ROM, the recovery-from-boot script will replace the custom recovery with the stock one on a reboot. If you want a permanent custom recovery, you will have to rename or delete /system/recovery-from-boot.p(this is the patch) or /system/etc/install-recovery.sh(this is the script that tries to install the recovery). I am unsure if goomanager makes it permanent, I have never used the app to flash a recovery before.

Flashed twrp with toolkit, and flashed a custom rom, everything seems ok now, so if someone has problem...
TL;DR
install WugFresh toolkit, be sure driver are installed (you can test driver with 1 click)
download and flash google factory image, again just 1 click,
install new recovery, this is the third click
Thx for help

im the doctor said:
Flashed twrp with toolkit
Click to expand...
Click to collapse
this hurts my brain.

Zepius said:
this hurts my brain.
Click to expand...
Click to collapse
ahahah, i agree, but i tried with goomanager and... nothing :\

im the doctor said:
ahahah, i agree, but i tried with goomanager and... nothing :\
Click to expand...
Click to collapse
That hurts my brain more.
you couldve accomplished everything you did without a toolkit by using fastboot/adb. people need to learn these tools.