Database Users

[Q] Radio update - rebooted to static picture

Hi
I have recently had my HTC Wildfire rooted after the fantastic AlpharevX contribution.
I've played around with different ROMs, and since I experienced problems with GPS in CM 7.1 RC1, I decided to go for a Radio update.
I have CWM recovery 3.2.0.0, which according to this general Wildfire thread is not compatible with flashing the current radio versions.
I therefore downloaded the Radio zip-file, copied it to my SD root dir and started ROM Manager and selected update ROM from SD card.
I checked "Backup current ROM" and "Wipe Dalvik cache" and pressed OK to the different dialog boxes.
It then rebooted to a black screen with the little green Android and a warning sign with an exclamation mark in it.
It has just stayed there for more than 10 minutes now.
I read somewhere that flashing radio can be riscy, and also that one must have patience and not interrupt anything. Therefore I haven't dared touching it without seeking advice...
What should I do? Am I supposed to press anything to continue, or should I try to turn it off (either using power button or by battery removal)?
Kind regards, Martin
UPDATE: I lost patience and decided to click on the different buttons. By clicking the power button, it displayed that I had entered CWM Recovery 3.2.0.0 and the log states:
Finding update package...
Opening update package...
Verifying update package...
E: failed to seek in /cache/update.zip (Invalid argument)
E: signature verification failed
Installation aborted.
I have just rebooted for now... Is it somehow possible to have two different CWM Recovery versions installed, such that I can boot directly into 3.2.0.0 and maybe enter 2.5.x.x. from ROM Manager?

you must flash clockworkmod recovery in rom manager then click run in recovery mode (second option) in rom manager then phone will reboot and got temporary CWM 2.5.0.7 and you can flash radio in this version

ziemjak said:
you must flash clockworkmod recovery in rom manager then click run in recovery mode (second option) in rom manager then phone will reboot and got temporary CWM 2.5.0.7 and you can flash radio in this version
Click to expand...
Click to collapse
Thanks a lot...
I just updated the radio.
Now I also now how to flash Froyo custom ROMS. CWM 3.2 only allowed me to flash Gingerbread ROMs.

moderator pls close thread problem solved

Hi since we are at it, I also have a question about radios...
My Bluetooth used to work just fine on my htc stock ROM before switching to CM 7.0.3, I could both send and receive files from my mac.... well the thing is I can only receive them now, I can't get my wildfire to send anything to my mac! (already tried the app from the market, I think it's called Bluetooth File Transfer)
Anyway do you think a radio upgrade or in my case downgrade could fix this? I currently have 13.55.55.24H_3.35.20.10.

A500 Bootloop. Tried to flash TegraOwners Rom, now no rom works

I can access my recovery, and flash roms from the SD, however no matter what ROM I tried, I get a boot loop.
I have Skrilax_CZ bootloader v8
CWM Recovery v5.5.0.x
Any suggestions or ideas?
Thank you!

Another note, I used to have a working rom in my downloads folder on the device, however from recovery, when i go to choose zip from internal storage i get "E:Can't mount /sdcard/"
Thank you!

jrichardsMav said:
Another note, I used to have a working rom in my downloads folder on the device, however from recovery, when i go to choose zip from internal storage i get "E:Can't mount /sdcard/"
Thank you!
Click to expand...
Click to collapse
Just tried to do a restore on a backup I made sometime ago.
I got "Error formating data"
Rebooted, and I get a screen saying
"Encryption Unscuccessful" with a button to reset tablet
I press that, tablet reboots to recovery, and i get an android bot with a spinning pentagram, then the bot is on its back with a red exclamation point.

Okay got it booting! Well, booting to honeycomb, everything is kind of a blur right now, but I flashed a 3.2 rom
got the enter a password screen
did the following:
http://forum.xda-developers.com/showpost.php?p=33607638&postcount=9
Now i can boot to android, but i can't boot to a recovery!!
Help?! lol

jrichardsMav said:
Okay got it booting! Well, booting to honeycomb, everything is kind of a blur right now, but I flashed a 3.2 rom
got the enter a password screen
did the following:
http://forum.xda-developers.com/showpost.php?p=33607638&postcount=9
Now i can boot to android, but i can't boot to a recovery!!
Help?! lol
Click to expand...
Click to collapse
Im actually on 3.1! and I've rooted 3.1. I'm trying to install a recovery image now, TWRP or CWM. I've tried the Goomanager method and the Acer REcovery Installer method, both force close before the recovery is installed.

jrichardsMav said:
Im actually on 3.1! and I've rooted 3.1. I'm trying to install a recovery image now, TWRP or CWM. I've tried the Goomanager method and the Acer REcovery Installer method, both force close before the recovery is installed.
Click to expand...
Click to collapse
Had to install ARI from PLAY, not MARKET.
Now flashing 4.2 + gapps. Crosses fingers.

jrichardsMav said:
Had to install ARI from PLAY, not MARKET.
Now flashing 4.2 + gapps. Crosses fingers.
Click to expand...
Click to collapse
Everything working. 4.2.1 on A500 is very nice. Multi user is beautiful.

Sorry have only just seen your posts - awesome you managed to get yourself fixed!!!!
So you had HC 3.1 with the v8 bootloader and you flashed the JB rom directly from there?? I know doing it this way has worked for me in the past its great to know someone else has luck doing it as well...
one more thing can you edit the subject line of your original post to "fixed" or "solved" - this will help others who may be in the same postion!!!
thanx and have a great 2013!!!
dibb

Sure can, if I can figure out how to edit the title.
I had 4.1, a tegraowners rom, then i had a random reboot and no matter what rom I flashed it would fail.
I tried to install a 3.1 rom, which gave me the encrypted message asking me for a password.
I then booted to fastboot, ran a few commands that I found, and got 3.1 working.
Rooted, Installed a new recovery (mine was botched) and got 4.2 working on it!
I'd like to learn more about rom development. Any good places to start?

Thanks for that...can't help re rom dev but XDA have new site"xda-university" there's a bit about rom dev there that may be helpful...good luck tho
Sent from my GT-I9300 using Tapatalk 2

Can't boot into recovery help!

I have a rooted Nexus 4 running stock 4.2.2 and recently it has started playing up. If I try to back up the ROM it reboots and I get left at an Android screen showing a Green robot picture that says "No command". I tried changing from Clockwork Mod recovery to TWRM but it made no difference. Can't seem to find any answers hence my need to post this thread. Any ideas please?

What did you do to the phone before you noticed it was acting up?

From efrant's android 101 sticky:
I see an Android lying on its back when I boot into recovery. Why?
What you see is the main screen of the Nexus stock recovery. To access the menu, you need to push and hold power and press volume up.
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 4 using xda premium

projectvii said:
What did you do to the phone before you noticed it was acting up?
Click to expand...
Click to collapse
I was in ROM manager and was trying to do a back up of my rom which I have done many times before, it usually results in a reboot into CWM where the backup takes place?

[Q] Defect CM10.1, Teamwin Recovery defect, fix & install KitKat

Hello,
I currently have installed CM 10.1-20130709-NIGHTLY-mb526 (Android 4.2.2, 2.6.32.9-AeroKernel), but I had a problem yesterday (phone would not boot).
So I did a Cache/Dalvik wipe, and after reboot it optimized all the apps but looped at "opening apps".
So today I decided to reinstall the above mentioned rom. But after installation it turned out to be defect somehow (e.g. the unlock screen will never appear, altough it is activated; in the swipe down menu the right-above button won't appear/won't work; browser won't turn on; home button does not work etc.).
So I decided to give KitKat a try. I visited this page by Quarx and I would begin with the Recovery Update. I put the update recovery zip on the sd card and install it via TeamWinRecovery.
After reboot, the TeamWinRecovery won't turn on and it simpy reboots. So now I am stuck. How do I install/recover TeamWinRecovery (or any necessary Recovery to install KitKat?).
After the installation I can simply install the latest KitKat rom, right? Or is there anything else necessary (kernel update etc.?). If I don't like KitKat, can I simply flash the latest CM10.2 rom?
Thank you very much!
Edit: The first rom i woul like to try is cm-11-20140117-NIGTHLY-mb526 (this is the KitKat, right?) and if this is not stable enough for me I would install cm-10.2-20131020-NIGHTLY-mb526 (Jelly Bean, right?). The reason I want to change is that I do not think the CM10.1 I have installed is neither stable nor perfomant.
Edit2: I tried the GooManager but it did not work! After reboot into Recovery screen stays black and reboots again.

mrkernelpanic said:
Hello,
I currently have installed CM 10.1-20130709-NIGHTLY-mb526 (Android 4.2.2, 2.6.32.9-AeroKernel), but I had a problem yesterday (phone would not boot).
So I did a Cache/Dalvik wipe, and after reboot it optimized all the apps but looped at "opening apps".
So today I decided to reinstall the above mentioned rom. But after installation it turned out to be defect somehow (e.g. the unlock screen will never appear, altough it is activated; in the swipe down menu the right-above button won't appear/won't work; browser won't turn on; home button does not work etc.).
So I decided to give KitKat a try. I visited this page by Quarx and I would begin with the Recovery Update. I put the update recovery zip on the sd card and install it via TeamWinRecovery.
After reboot, the TeamWinRecovery won't turn on and it simpy reboots. So now I am stuck. How do I install/recover TeamWinRecovery (or any necessary Recovery to install KitKat?).
After the installation I can simply install the latest KitKat rom, right? Or is there anything else necessary (kernel update etc.?). If I don't like KitKat, can I simply flash the latest CM10.2 rom?
Thank you very much!
Edit: The first rom i woul like to try is cm-11-20140117-NIGTHLY-mb526 (this is the KitKat, right?) and if this is not stable enough for me I would install cm-10.2-20131020-NIGHTLY-mb526 (Jelly Bean, right?). The reason I want to change is that I do not think the CM10.1 I have installed is neither stable nor perfomant.
Edit2: I tried the GooManager but it did not work! After reboot into Recovery screen stays black and reboots again.
Click to expand...
Click to collapse
Hello, i had a similar problem and i finally flashed a new sbf then CM10.1 and after that CM10.2 and it worked. As for recovery the only way that worked for me is with cwm through 2init.apk. CM11 seems unstable atm...

PerryTrademark said:
Hello, i had a similar problem and i finally flashed a new sbf then CM10.1 and after that CM10.2 and it worked. As for recovery the only way that worked for me is with cwm through 2init.apk. CM11 seems unstable atm...
Click to expand...
Click to collapse
sbf is not a option for me!

mrkernelpanic said:
sbf is not a option for me!
Click to expand...
Click to collapse
SBF is the only option. The reason why CM10.1 didn't work as intended is that you must have used full gapps.
Sent from my Nexus 7 using Tapatalk

Hi,
I think I used the minimal Gapps linked in the thread! And no, sbf is not an option right now as I do not have acces to a Windows based PC where I have rights to install software!
Any other solution how I can restore/install TeamWinRecovery? Should I try 2ndinit?
Thanks anyway and regards kernel

There is a method through ADB explained by @YetAnotherForumUser in CM11 thread by Quarx. This if you can enter in boot menu.
Sent from my MB526 using Tapatalk

adb is neiher an opion, I currently have no acces to a computer with root-acces!
I read somewhere that 2ndinit won't work wih a custom rom installed, ist this correct?
Regards kernel

Yes is correct. You must start from sbf when you have access to a computer.
Sent from my MB526 using Tapatalk

mrkernelpanic said:
adb is neiher an opion, I currently have no acces to a computer with root-acces!
I read somewhere that 2ndinit won't work wih a custom rom installed, ist this correct?
Regards kernel
Click to expand...
Click to collapse
What about a linux live session?
Sent from my MB526 using xda app-developers app

[Q] Stuck in recovery mode upgrading CM 10 to CM 11

I was running CyanogenMod 10.1.x versions, using ROM Manager to upgrade as new ones were available. However, when I tried to upgrade to 10.2.1 it kept rebooting every several minutes, showing the new bootup screen with the rotating arrow. I tried upgrading to version 11...M9 also with ROM Manager and now it only comes up in recovery mode (CWM v6.0.3.1). There seems to be no way to finalize the installation. I can't sideload from the PC, since, although DeviceManager shows "Google Galaxy Nexus ADB Interface," I do not see any entries in Device Management or in the Explorer, so I can't offload a full backup, nor can I use adb to sideload the new CM. I can't instal from the internal sdcard, since it starts with "...Installing /sdcard/update.zip" and then can't find it - it comes up with the "(no such file or directory)."
Since (except for Device Manager) nothing on the PC recognizes a connection with the Nexus 10, I'm pretty much out of options. I can do a complete "wipe data/factory reset" I suppose, but would like something not so drastic (given no backup). When I look at CWM's display of mounted and unmounted storage, sdcard is unmounted and won't mount. I've even done a full wipe and factory reset, with the same results.
A brand-new install of the Samsung USB Drivers 1.5.33.0 through Skip's app now results in an error message when I reattach the tablet saying the driver install failed. I still show the device in Device Manager.
I have Skip's Universal Android Toolkit v1.0.2 and it seems to recognize that a Nexus 10 is connected, but can't do anything to it (it expects you are originally booted to Android, not recovery.
This is my first Samsung device, so I'm totally unfamiliar using Odin and haven't figured out how to use it to correct the problem.
It seems that, if I can sideload a copy of CM 11, I should be okay, but all roads look closed.
Any ideas?
I'm locked in a loop.
'

Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!

Thanks - will keep trying.
demkantor said:
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Click to expand...
Click to collapse
I downloaded the latest Android SDK with platform tools and put the cm zip file in the directory with adb.exe. On the tablet, in ClockworkmMod Recovery, I selected "install zip from sideload." The tablet went into sideload mode and instructed me to type "adb sideload <filename>. So I typed: "adb sideload cm-11-20140805-SNAPSHOT-M9-manta.zip" and hit the enter key. The PC reported 100% downloaded. The tablet listed:
Restarting adbd...
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I'm at least communicating between the PC and tablet, but the update is still failing. Any hope of trying to flash standard ROM, re-root, and start again?

You need to update your recovery, grab the latest TWRP or CWM .img for manta and flash in via fastboot first, then boot to new recovery then flash ROM

Thanks, I grovel at your feet!
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.

Beartooth01 said:
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Click to expand...
Click to collapse
Great to see @demkantor help get you back up and running ..
@Beartooth01 Can you plz add "SOLVED" to the thread title
Thx Josh