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).
Related
First and foremost,
Standard Disclaimer
By flashing this you should understand that I am not responsible for bricked devices. In order to flash this file, you would have already rooted your device, voiding the warranty. YOU are choosing to make these modifications, and I take no blame or responsibility if you brick your device and/or your device catches fire.
I would like to start off saying that I used the eMMC dual boot option referenced here [eMMC]Updated Dual Boot Guide[CM 7.1+][Phiremod 7+][Stock 1.3] and ran into the problem where the main partition (CM7 in my case) was booting normally, however, the alternate partition (Stock 1.3 rooted) would continually boot loop. After research, I found out that it was boot looping due to the incorrect versions of Adobe Flash and Air being installed. They were also installed to /system instead of /data.
I found two excellent guides located here and here that helped diagnose the problem. Unfortunately, these only helped with the primary partition.
In order to fix the boot looping of the alternate partition, I modified the updater-script provided by jaromnelson to reflect the alternate partition.
What this file does is removes the incorrect Adobe Air and Adobe Flash from /system folder on the alternate partition and installs the correct Adobe Air and Adobe Flash to /data folder. DO NOT INSTALL THIS FILE IF YOU ARE NOT RUNNING eMMC DUAL BOOT by Taosaur. If you continue to boot loop after you install, you are not boot looping because of Adobe Air and/or Flash.
To Install:
Download the file located here
Put the file onto your SD Card
Boot into CWM recovery
To be on the safe side, Wipe Cache and Dalvik (not sure if this helps but I do it anyway).
Code:
CWM > Wipe Cache Partition
CWM > Advanced > Wipe Dalvik Cache
Install the attached ZIP through CWM.
Reboot into your alternate partition and enjoy.
I am by no means a developer, just a guy that does a lot of research.
Full credit goes to:
Taosaur for creating the eMMC dual boot guide
jaromrnelson for creating the guide to fixing the boot looping
GMPOWER for the initial ZIP
Do you happen to still have this file, file seems to not exist.
I'm having the same issues you were
You can always upload it here as an attachment
Wow. I can't believe this may actually help someone. All this time, I thought I would have been the only one to encounter this problem. Unfortunately it would not let me attach the file to the post. Anyhow, here is an updated link. I'll update the OP too.
http://www.mediafire.com/?8e8vxgl8haag2a5
Mikey, after looking, it appears that the original referenced thread has been updated to a new method of installing dual boot to emmc. When I get home I will check to make sure that the new version uses the same boot partitions. So for now (until I can check) this zip is only good for the old method.
edit: I looks like the new method uses the same boot partitions (primary system: 0p5 and primary data: 0p6 --- secondary system: 0p9 and secondary data: 0p10) as the old method. So, if you are using the new method and experiencing the same boot loops as before, it should be safe. In reality, I'm not even sure if the Adobe problems exist anymore with the new method. As stated in the OP though, I'm not responsible for bricked devices.
To be honest, my wife has been reading on the nook so much lately, she hasn't let me mess around with it. As soon as she finishes up this book that she's on now, I plan on updating to the newest stock and ICS.
Sent from my LG-P999 using XDA
Always boots to CWM
My problem is a little different, but I'm hoping you can direct me where to go. I've been running the dual boot for about a week and it worked great. Stock on Alt and CM7 Kang on Primary. Today I backed up and then installed a theme that created a boot loop. So I tried to restore from the back up... no good. It boots up the little green Cyanogenmod, says loading, then straight to CWM. Then I tried to format the system, data, cache, and Dalvik, then re-install CM7...same, straight to CWM. I tried from the beginning, repartitioning and installing Stock with CWM... now Read Forever comes up and then to CWM. Suggestions Please.
Hoser88 said:
My problem is a little different, but I'm hoping you can direct me where to go. I've been running the dual boot for about a week and it worked great. Stock on Alt and CM7 Kang on Primary. Today I backed up and then installed a theme that created a boot loop. So I tried to restore from the back up... no good. It boots up the little green Cyanogenmod, says loading, then straight to CWM. Then I tried to format the system, data, cache, and Dalvik, then re-install CM7...same, straight to CWM. I tried from the beginning, repartitioning and installing Stock with CWM... now Read Forever comes up and then to CWM. Suggestions Please.
Click to expand...
Click to collapse
Try this post. Not exactly the same issue, but this person solved his CWM boot loop issue.
http://forum.xda-developers.com/showthread.php?p=23864432
Sent from my Nook Color running ICS and Tapatalk
@Leapinlar
Thanks for the help. That thread was perfect. I'm up and running now!
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Finding installed ROM
sjs_bebop said:
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Click to expand...
Click to collapse
Go into system settings / about tablet (at bottom of settings)
About 3/4 down list you'll see the ROM installed. Also kernel info plus other info.
For updates ;
I go to this link and download directly.
http://download.cyanogenmod.org/?type=nightly&device=encore
Also I copy and paste the md5 sum into MD5 checker (free in play store), run the check.
Reboot into recovery using power button menu and install in TWRP there. I had too many problems using cm downloader, goo manager, etc.
nook color cm10.2 update problems
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Sounds like a problem I had a while back
sjs_bebop said:
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Click to expand...
Click to collapse
You may be having partition problems. I have had either lost the ability to install new nightlies or the ability to backup. Read the instructions through completely first. Get the info together and then start.
If you have a backup App like titanium backup, backup all files and data before anything else. Also if you can, do a backup in recovery before doing the following.
Check this link: http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 by Leapinlar
I set up a 2Gb sd bootable card to run these from using the CWM recovery (If you need help check eyeballer's link below).
I put the partition repair files on it. Also the 1.4.3 Stock rom, the TWRP open recovery. zip 2.4.1.0 (http://forum.xda-developers.com/showpost.php?p=37554712&postcount=129), and the latest Rom you want to install and Gapps.
After following leapinlar's instructions including installing the 1.4.3 Stock rom (fixes other possible problems), then follow eyeballer's install for the Rom, Gapps and recovery here (http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color).
After booting and doing the initial CM setup return to recovery and VERY IMPORTANT ***restore only the data*** Not boot or system from your latest backup. This should get you back up and running. If you have a backup like Titanium restore "newer versions of apps" if you had to use an older recovery backup. Once you have everything set reboot into recovery and do another backup for safeties sake.
Including my wife's Nook I have four units and have needed to do this 4 or 5 times. Takes a little time but has always worked great. I keep the card available and update the Rom, Gapps or whatever else needs changing.
This link also contains a lot of helpful info. I have all these bookmarked on both my PC and Nook.
User Tips http://forum.xda-developers.com/showthread.php?p=25354258#post25354258
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
taodan said:
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
Click to expand...
Click to collapse
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
And yes to answer your question it is a multiROM patch for TWRP
sropedia said:
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
Click to expand...
Click to collapse
Do you have "USB debugging" checkbox, in Developer Options, checked? Also, try reboot your PC and reconect your phone to see whether it shows up as a storage device.
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
playya said:
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
Click to expand...
Click to collapse
I did a full wipe like I usually do. I would use a different version of TWRP if I knew how to change it from within TWRP. I have a follder titled ROOT that I keep all my ROMs and whatnot in, but the problem is that literally none of the folders in my internal storage are showing up from within TWRP. I can't check to see if USB debugging is enabled because theres no operating system on my phone; like I said, I did a full wipe. The fact that no folders show up also means that it doesnt recognize the backup I had. My computer still won't recognize my phone as a storage device after mounting in TWRP. Maybe I'm doing something in the wrong order? Restarting my computer didn't help.I really need to get my phone working on ANY ROM, and I appreciate all the help so far
Hello,
I decided that as I was tired of Google Play's ever growing size and because my phone had started making random error noises I'd try rooting it. I also like trying out stuff with technology. It's proving more difficult than I expected though
Here's what I have / what I did:
1. Rooted phone using update.zip that I got from somewhere on XDA.
2. Put a temporary CWM file and ROM (Cyanogenmod 7.2 which I got via XDA: 'CM_totoro_RC_04').
3. Went into CWM and tried to install the ROM. I can't remember exactly what happened but it looked like it was working i.e. there was an 'installation complete' message but when I boot into recovery mode some blue text comes up and what I'm left with is:
"(Invalid argument)
E: Can't mount /cache/recovery-last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache
(Invalid argument)"
I think there's more than that but that's what I'm left with on the screen.
I did wipe the user data and cache and I have tried a different CWM but there's no change.
I'm using a laptop with a Linux system and it won't recognise the phone in its current state. I think Heimdall is a cross-platform equivalent to Odin but I'd prefer not to get into that as I'd like to try and keep things simple. I have a second phone (which is working and recognised by my laptop) so I can put ROMs etc on its SD card and then physically transfer the SD card into the Galaxy Y.
I do not have a backup of the Galaxy Y before rooting so I don't think it's easy to get back to where it was before I rooted it.
Is the CWM fully compatible with the Galaxy Y? How come the message says that the installation is complete yet it's not working? Am I not following the correct steps after it says installation complete (I think I selected 'reboot' from CWM at this point)? Am I not giving the phone long enough to boot after flashing the ROM (it seems to stop at the Samsung logo screen)? Is it worth trying a different ROM, after all CM7.2 is an unofficial port?
Prior to rooting I hadn't altered anything important i.e. the phone was as it was at manufacture.
On re-reading the installation instructions I note that I didn't:
- Format /system partition
- Install the kernel provided at Download links
I couldn't find the kernel though - was this a critical oversight?
Any help or suggestions much appreciated. Thanks!
To start off with if you are using cm7 you need to be using the cm7 common kernel
You also need to use the ext formatter to convert system to ext
Once that is done you need to reboot to recovery
Format system data cache
Mount system data cache
Flash rom zip
If you still get cache error just make a nandroid backup in cwm then advanced restore cache only
Full instructions and links to everything you need will be on the cm7 rom thread
If all else fails flash stock rom via odin & start again - see my firmware thread Link in signature
Thanks! As seems normal though the information isn't that clear (to me at least). I searched for 'cyanogenmod 7.2 galaxy y' and went to
http://forum.xda-developers.com/showthread.php?t=2537457
In the second post are 2 downloads - I'm assuming it's the first one as I think the one I've already tried the 'totoro' one?
I'll give this a bash later and post back...
ksjs said:
Thanks! As seems normal though the information isn't that clear (to me at least). I searched for 'cyanogenmod 7.2 galaxy y' and went to
http://forum.xda-developers.com/showthread.php?t=2537457
In the second post are 2 downloads - I'm assuming it's the first one as I think the one I've already tried the 'totoro' one?
I'll give this a bash later and post back...
Click to expand...
Click to collapse
That is a very old build
The version of cm7 that roms are based on is
http://forum.xda-developers.com/showthread.php?t=2673610
Kernel required
http://forum.xda-developers.com/showthread.php?t=2673603
Ext formatter
http://www.mediafire.com/download/s6191k8ze9en0l6/ext4_formatter.zip
Follow instructions in this post
http://forum.xda-developers.com/showpost.php?p=50899031&postcount=3
Big thanks for your post - perfect! I now have CM7.2 installed and a less bloated phone
Hey, look what i've done while desperately trying to install GearCM or CM12 ROM. First, i installed TWRP on my i9500 device. After that, i put the GearCM 5.1 and Gapps for 5.1 on sdcard, but i got mad really fast when i saw i can't install ANY ZIP from sdcard, then tried another CUSTOM ROMS, same problem, i wiped cache and system ( ye, system ) ) - dont ask why i did that - Anyway, now i have no system files on phone, and on my sdcard i only got that useless ZIPs.
Ah, forgot to mention, the error showing up everytime i tried to install a zip was : "Zip corrupted, Operation aborted" (something like that ).
NOTE : I can't boot normally, but i can boot in recovery (TWRP) . I can't flash another rom using odin as i can't switch usb debugging ON.
Ah, please, don't laugh too much, im pretty serious
Oh, some1 explain this to me -> I tried to install zip @ adb as i saw explained on a blog -> got stuck at recognizing phone-pc due to driver error, so i decided to try last time installing the custom ROMs( THE SAME ZIPs i got error before) from recovery -> install zips. AND GUESS WHAT, less than 20s rom is installed without any errors, i dont know if to be mad or happy. Atleast explain me what happened there.
wowempire said:
Hey, look what i've done while desperately trying to install GearCM or CM12 ROM. First, i installed TWRP on my i9500 device. After that, i put the GearCM 5.1 and Gapps for 5.1 on sdcard, but i got mad really fast when i saw i can't install ANY ZIP from sdcard, then tried another CUSTOM ROMS, same problem, i wiped cache and system ( ye, system ) ) - dont ask why i did that - Anyway, now i have no system files on phone, and on my sdcard i only got that useless ZIPs.
Ah, forgot to mention, the error showing up everytime i tried to install a zip was : "Zip corrupted, Operation aborted" (something like that ).
NOTE : I can't boot normally, but i can boot in recovery (TWRP) . I can't flash another rom using odin as i can't switch usb debugging ON.
Ah, please, don't laugh too much, im pretty serious
Click to expand...
Click to collapse
*stare and laughing a lot*
*Just kidding, okay? :silly: *
And then;
You have corrupted zips. You need to redownload the package completely (ROM+GApps) and transfer it to your external SD card and flash. You can transfer the downloaded zips by using adb push command or remove your external SD card and plug it to anything else (read: SD card reader; of course ).
Sent from my ASUS_Z00AD
krasCGQ said:
*stare and laughing a lot*
*Just kidding, okay? :silly: *
And then;
You have corrupted zips. You need to redownload the package completely (ROM+GApps) and transfer it to your external SD card and flash. You can transfer the downloaded zips by using adb push command or remove your external SD card and plug it to anything else (read: SD card reader; of course ).
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yeah, maybe im not exactly as n00b as you think. I used exactly the same zips after(same procedure tho), and it worked smooth(i didn'teven touch them).
NOTE : I think i said i tried using adb to install zips but i got a driver error which i couldn't solve.
I've had that issue for some time especially with CM, have you tried verifying the sh1 checksum once you've loaded it onto your sd card?
Thanks.