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.
Hi,
I am pretty new in this. Tried to flash my HD2 to an Android ROM today, but got stuck on the installation part from SD (install ZIP from SD).
When the HD2 is booting I get the CWM-based Recovery screen V4.0.1.4
When I select "install ZIP from sdcard" i select the ZIP on the sdcard.
Install starts and i get the screen "Have fun with DUNGPHP's ROMS"
Processing system, please wait. After a while the installation is automatically aborted with the errormessage:
E:Error in /sdcard/DHD_3.06.405.1_Sense_3.0_v1.3_EU.zip
(Status 0)
Installation aborted.
What is going wrong?
The steps I followed:
1. I flashed the cLK loader and Recovery
2. I installed the google usb driver on my pc to connect to phone
3. I did run fast_resize.bat from cLK folder
4. I did run fastboot_install_recory.bat from the cLK folder
5. I followed the installationsteps on my phone for installing the ROM.
Before all this I did flash the latest HSPL and Radio.
What I noticed, is when i boot the device and get the cLK screen (with options boot recovery, boot sboot etc.) i see in the header "RADIO-UNKNOWN" allthough i flashed Radio 2.15.50.14.
What can be wrong? Hope someone can help me..please
Thanks!
Regards,
Edwin
E:Error in /sdcard/DHD_3.06.405.1_Sense_3.0_v1.3_EU.zip
Click to expand...
Click to collapse
id try redownload the file again.
Also, you didnt use magldr to copy the file to sd did you? it doesnt handle large files well. Either use cwm sd transfer or use a card reader.
I've tried 2 ROM's, both with the same error.
I also copied the ROM's (ZIP) on the SD directly with my laptops SD-slot.
Any clue what can be wrong?
Edwin
Tried more things. I used several SD cards, results are all the same, error during installation.
I tried to install 2 ROM's:
- Desire_S_sense3.5_Android.2.3.4_v1.3_EU.zip
- DHD_3.06.405.1_Sense_3.0_v1.3_EU.zip
Both ROM's gave the same error during installation "error in ZIP", and on both my SD cards.
I downloaded a different ROM, CMYLXGOs.Stock.Desire.HD.v1.0.7n.NAND.RMNET.NO-SQUASH-MDJ.S10.4OC_CWM.zip.
That one was installed successful. But after rebooting system, the recovery mode was still coming up.Selecting normal boot gave an error, there was no loader.
I am really stuck now, hope someone can help me.
Edwin
Man try doing a hard restore I think something went wrong in your process of installing cwr not in your process of installing rom . Install cwr again and than try again. It should work !!!
Click thanks if I helped you.
Hello, my tablet is TF300TG WW 9.4.4.40, unlocked bootLoader with custom recovery CWM
What I did is I went to
1-Asus support downloaded the appropriate upgrade which is "WW_epaduser_10_4_3_7_UpdateLauncher.ZIP"
2-copied the zip file as it is "WW_epaduser_10_4_3_7_UpdateLauncher.ZIP" and also copied whats in it which is "TW_epad-user-10.4.3.7.zip"
3.got the exclamation mark which is telling me there is an update
4.restart
5.It went automatically to the custom recovery CWM
6.I assumed I need to factory reset/and clear dalvik
7.then install from sdcard
8.tried "WW_epaduser_10_4_3_7_UpdateLauncher.ZIP" and failed immediatly
9.tried "TW_epad-user-10.4.3.7.zip" and it took some time then failed saying
"script aborted (no error message)E:Error in /sdcard/WW_epad-user-10.4.3.7.zip (status 7)
Installation aborted
I searched for a way to get back the stock recovery image and couldnt ..
Any suggestions please?
Check that the SD card is formatted to FAT32 if NTFS it will give that error if memory serves me correctly.
.
Sent from my ASUS Transformer Pad TF300TG using Tapatalk 2
Hello
http://forum.xda-developers.com/showthread.php?p=32942956#post32942956
newstargate said:
Hello, my let is http://forum.xda-developers.com/showthread.php?t=1928865TF300TG WW 9.4.4.40, unlocked bootLoader with custom recovery CWM
What I did is I went to
1-Asus support downloaded the appropriate upgrade which is "WW_epaduser_10_4_3_7_UpdateLauncher.ZIP"
2-copied the zip file as it is "WW_epaduser_10_4_3_7_UpdateLauncher.ZIP" and also copied whats in it which is "TW_epad-user-10.4.3.7.zip"
3.got the exclamation mark which is telling me there is an update
4.restart
5.It went automatically to the custom recovery CWM
6.I assumed I need to factory reset/and clear dalvik
7.then install from sdcard
8.tried "WW_epaduser_10_4_3_7_UpdateLauncher.ZIP" and failed immediatly
9.tried "TW_epad-user-10.4.3.7.zip" and it took some time then failed saying
"script aborted (no error message)E:Error in /sdcard/WW_epad-user-10.4.3.7.zip (status 7)
Installation aborted
I searched for a way to get back the stock recovery image and couldnt ..
Any suggestions please?
Click to expand...
Click to collapse
Hi, please follow my post on page two of the discussion in the TF300 general of this forum....the topic is "All your TF300TG jelly bean needs"....works flawlessly....remember, please take out sd card before flashing.....flash from internal sd....or you lose that card. So reported and please hit thanks
Sir please search before opening a new thread
Thanks and thread closed
I guess my real question is what's the best way about flashing this rom
1) Reboot into recovery
2) Wipe data
3) Install ROM
4) Install GAAPS
5) Clear cachse/dalvik/etc.
6) reboot
?
Well bricked my phone (sort of)
I got the (Status 7)
installation aborted error
I used the att CM file which is compatible with the Bell version in Canada.
Can someone please help ?
ask in q&a, where this post belongs. cheers
So my phone is messsssssssssed. I got the status 7 error -- and it aborted. So I went to try to sideload the rom (after editing the file -- there was a fix for this) and it says sideload started -- it's waiting for me to send the file
BUT I CAN'T GET ADB TO RECOGNIZE MY PHONE.
am i screwed ? I installed the drivers and stuff and still it won't recognize my phone ... do i have to reboot the computer ?
So my phone is messsssssssssed. I got the status 7 error -- and it aborted. So I went to try to sideload the rom (after editing the file -- there was a fix for this) and it says sideload started -- it's waiting for me to send the file
BUT I CAN'T GET ADB TO RECOGNIZE MY PHONE.
am i screwed ? I installed the drivers and stuff and still it won't recognize my phone ... do i have to reboot the computer ?
update your recovery.
Where did you get the rom and what did you edit in it?
also I would suggest wiping system when you flash new roms, not just data/caches
Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?
digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!
error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?
baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?
baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).
digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?
baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
baytee said:
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app
Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).