Problems after emmc KitKat rom install nook HD+ - General Questions and Answers

To preface: History--I have some experience installing tenderloin mods for hp Touchpad. More currently, I spent 2 days reading about first, an SD Install for my nook HD+, and then an emmc install for same. I felt ready to go forward but did not prove a smooth process.
To date, I have verygreen's process executed with the following issues:
Failed gapps install...I believe.
Notification of processes being stopped, ie, clock.
Cannot log onto Play Store--"Authentication is required. You need to sign into your Google Account. Retry" Pressing Retry loops back to same message.
Oddness or unexpected results:
I expected all my apps and accounts to disappear with Rom install but all and perhaps more exist. My gmail app and account opens with emails from time before install but no new downloads since. Internet works as wi-fi connected fine.
Procedures that got me into this pickle:
1. Using Pretec 8GB Class 10 Micro SDHC, which btw my nook found fairly easily, I used the following sw to prep and populate it for install.
a. win32diskimager-v0.9-binary
b. sdcard-cwm-early9.img
which btw reduced my Micro sdhd partition to just the minimal size needed to perform the needed function w/o space for rom or gapps. Grrr
2. Downloaded cm-11-20140303-NIGHTLY-ovation to "download" folder inside nook...yes, I forgot both the cwm-recovery-ovation-6 and the gapps.
3. Began to install NIGHTLY and rebooted but as you probably expected it stopped at "nook".
4. Rechecked verygreen's procedure list with facepalm, tried to install forgotten files onto flash mem where there was no room(see above), rebooted into nook to download missing recovery file and pair of gapps files -- pa_gapps-modular-full-4.4.2-20140301-signed and pa_gapps-stock-4.4.2-20140301-signed
5. Install begun with boot to flash and then, yes then decided to use cwm to backup pre-existing rom. Tried to backup to /sdcard with following android reply:
SDCARD cwm-based recovery v6.0.4.6
SD Card space free: 6133MB
Backing up boot...
Backup of boot completed.
Backing up system...
Can't mount /system!
6. Perhaps a backup to emmc?
SD Card space free: 4495MB
Backing up boot...
Backup of boot completed
Backing up system...
Can't mount /system!
7. Oh...I'm not done (it was late).
Choose default backup format
tar (default) //why change something I don't understand?
Default backup format set to tar.
CAN'T SEEM TO SOLICIT A WAY TO BACK OUT OF HERE! Later I discover the power button as backout, but until then...
8. free unused backup data
Freeing space...
Done freeing space
Freeing space...
Done freeing space
Choose an image to restore first. The next menu will show you more options.
-2014-03-04.05.37.33/
Advanced Restore -----------Upon reflection, perhaps I shouldn't have proceeded
--Restore boot
--Restore system
--Restore data
--Restore cache
--Restore sd.ext <<== this one looks interesting
Backup & Restore
Yikes! Finally found power button
//Reboot and install of forgotten recovery file, then Rom. Rebooted, downloaded 2 gapps files(see above)
9. SDCARD CWM-based recovery v6.0.4.6
--Couldn't open directory
--Couldn't open directory
No files found.
--Installing: /emmc/0/download/pa_gapps-modular-full-4.4.2-20140301-signed.zip
Finding update package...
Opening update package...
E: Can't open /int-data/media/0/download/pre_gapps-modular-full-4.4.2-20140301-signed.zip
(bad)
Installation aborted //Why? File truncated at about 7KB due to bad download
10. Not to be deterred, another download.
SDCARD cwm-based recovery v6.0.4.6
No files found
...Installing: /emmc/0/download/pa_gapps-modular...etc
Finding update package...
Opening update package...
Installing update...
################
//Graphics display
################
PA GApps Full Modular 4.4.2 20140301
Mounting system...
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error in /int-data/media/;0/download/pa_gapps-modular-full-4.4.2-20140301-signed.zip
Installation aborted
I guess what I am hoping for is a forensics examination(but not in depth). I hope the excessive detail can be skimmed for a quick assessment of my nook's status. IOW, is there a simple fix. Should and can I start all over?
Thanks for whatever help is offered.

I have to admit that I didn't expect a response to this post.
I had begun researching a Rom installation for my nook days before my actual attempt but had neglected to open an account where I discovered the 10-post rule. Had I known I would not have been allowed to post into the forum I had studied to make that install I don't think I would have attempted it until much later. Now I am left to post a specific and detailed account into a general topic Q & A forum without any chance to attract a person familiar with a nook HD+ ROM installation. No problem...I'll just get started on learning how to program for Android and installation of Roms and how they are...designed and all the rest.

Solved
bupkus said:
I have to admit that I didn't expect a response to this post.
I had begun researching a Rom installation for my nook days before my actual attempt but had neglected to open an account where I discovered the 10-post rule. Had I known I would not have been allowed to post into the forum I had studied to make that install I don't think I would have attempted it until much later. Now I am left to post a specific and detailed account into a general topic Q & A forum without any chance to attract a person familiar with a nook HD+ ROM installation. No problem...I'll just get started on learning how to program for Android and installation of Roms and how they are...designed and all the rest.
Click to expand...
Click to collapse
Solved:
While lurking around I found this post about rebooting into recovery without using the microSDHC card used during the original install of a CM ROM.
From there I installed the gapps successfully.
Very happy with the way my nook performs now.

Related

Receiving Exclamation point

Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
GManLynx said:
Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
Click to expand...
Click to collapse
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Alright, I'm sorry but I came the G2.... And I was wondering what NVFlash is? I'm gonna google it, but it will be nice if you answer it too.
Setting up NVFlash
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
darbear5610 said:
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
Click to expand...
Click to collapse
yup and when u get ready for commands u can copy and paste them
techboydino said:
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Click to expand...
Click to collapse
First - the above is the truth - learned the hard way by many.
From the "triangle" comment, I would have thought you were not able to get into recovery anymore, but you said you had tried flashing in recovery - are you still able to get into recovery? Also, when you said you moved the file to the SD - internal or external?
You could re-download the ROM on you computer and/or move the one you downloaded when in USB connect mode if you can connect through USB. and then try flashing it again.
Otherwise - did you do an nandroid back-up first (add that to the G2X Club rules). If so, and you can get into recovery, you can restore it through recovery. If not, you are truly back to square one (except for rooted).
At some point, you need to NVflash a real recovery. The one-click method in the Dev section is the easier way to go. If you can't get into recovery (you only see the triangle and it only does a factory reset), then you HAVE to start there.
Yeah I am still able to get to recovery mode. And external sdcard.
I think i'm just gonna go staright to the NVFlash way. I have a history class today so I have a hour and a half to burn.
And thanks guys for all the inputs.
I'm loving my G2x so far. So fast and sleek
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Alright thanks. I just installed via NVFlash and now I will try again to install CM7
player911 said:
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Click to expand...
Click to collapse
Agree with all the above (I have and use both), except for making nandroids, which was not mentioned above. The only ones where I have had a check-sum issue with trying to restore are nandroids I did with ROM Manager. I would stick with doing them straight from recovery.
Others have had issues with flashing nightlies also, but I have not noticed that as I always head straight to recovery to flash.
Question - I had flashed real recoveries with ROM manager on MT4G - why the "false" recovery issue on G2X?
So player, once I have NVFLASH and CWM, I can download ROM manager to backup/restore/flash any ROM from the list without worrying about anything?
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
I would redownload the zip file over the computer, happened to me before with a different rom, make sure it doesnt unzip. and then drag it to your SD card.
Okay I am perfomring that now, will edit with results.
My goodness... I think you fixed it for me. I feel like an idoit. I've been saving it to hte internal Sdcard i didn't even know that was possible.
Damnit... same problem.
Yay I got it. Thanks so much guys for all the help.
GManLynx said:
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
Click to expand...
Click to collapse
The ROMs were probably going to the internal SD by default. Just move them with a file manager to the external SD (unless you set up recovery to use the internal SD).
Also, do not rename them update zip - leave the names as-is so you will know what your are dealing with if you have multiple ROMs .
Then you flash it as a zip file on SD card - not as "update.zip" - that would be for the OTA update - if we ever actually see one for the G2X!
Good job Gman
Different roms put the external SD card in different places.
By default Rom Manager is set to read/write to /sdcard/... not /sdcard/external_SD that is the norm with the stock(based) roms.
Once you have CM7 on there and everything setup under standard conditions, Rom Manager will work as it should.

[Q] Infuse zip flashing stuck at "Finding update package"

Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes
Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?
yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)
baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links

Cyanogenmod Repack set_metadata_recursive error

Recently, I found a repack of Cyanogenmod 12 for the Gionee M3. I decided to install it, but all that happened was that it wiped my system partition and spat out this error:
Code:
"ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:systemset_metadata_recursive: some changes failed"
According to the TWRP file manager, there was nothing at all in the system partition but a folder called "bin" (which I suspect was added when TWRP asked me if I wanted to root it). I went through the installer script, but I was having some trouble because I can't tell what half of it actually does. From what I can tell, though, it copied the releasekey, then formatted the partition, then went through a big long list with "symlink" a lot of times and what looked like a list of every file that would be in the new system partition. It quit, from what I can tell, after it got down to the "metadata" section which began with a "set_metadata_recursive" command.
Does anybody know what this means, and how I can work around it?
(I'd experienced an error with this same ROM before, but it told me to do a factory reset. Now I'm having this error instead.)
Hello,
To better assist you, your thread will be moved to your device forum linked below.
http://forum.xda-developers.com/t/gionee-m3
The experts there may be able to help.
Okay, I've installed PhilZ instead of TWRP and I can now flash Lollipop ROMs. But CyanogenMod is still failing. It still just says (when I try installing SuperSU immediately after flashing) that there is no system or data partition. But the first zip (the Cyanogenmod one) doesn't throw any errors.
I got the zip from blu-dev.com.

[Completed] SOLVED Galaxy Tab 10.1 help

Edit: SOLVED
Hoping someone can roughly point me in the right direction. I'm not very savvy in flashing new ROM's, but I had success with my phone recently, so I decided to try and update my tablet and it's not going so well. It's a Samsung Galaxy Tab 10.1, model GT-P7510MA, which I believe is wifi only. I started off by following the youtube tutorial: 0eAQzxwEVjY
I did *not* make a backup, so shame on me right off the bat, but at least now I've learned this lesson.
There is no OS, but TWRP v2.2.0 is installed and I'm able to boot into it just fine. I'm able to transfer/push files via command line on my windows machine, but I did find something that seemed odd, which is that the top level directory is not named "/sdcard", instead it's just "/". When I transfer files, I have to name the the path "/" for them to show up in the top level directory. If I use "/sdcard", it looks like they upload, but I have no idea where they go. Not sure if there's any significance there, but figured I'd mention it.
The problem is that I can't seem to install any OS. I've tried Nameless 4.4.4, Clockworkmod 10.1, and AOSP 6.0. They all fail the same way, I'll type out what it says below:
--Install /aosp-6.0-p4-20151211.zip ...
Finding update package...
E:unknown volume for path [/aosp-6.0-p4-20151211.zip]
E:Can't mount '/aosp-6.0-p4-20151211.zip'
* Verifying filesystems...
* Verifying partition sizes
Error flashing zip '/aosp-6.0-p4-20151211.zip'
Another strange thing is that when I tried the aosp-6.0-p4wifi, it said that this device was a p4, which I don't think is correct, but that's why I tried the p4 version. It errors just the same. I've also tried to update TWRP, but I'm not sure you can update TWRP from within TWRP? I've tried using the file "twrp-2.8.7.-picassowifi.zip" and it errors the same as the OS'.
Edit: It's been sitting here powered on for a bit and then went to the blue teamwin screen and would flash off every five seconds or so. I figured this was maybe a screensaver? Next it powered off and on restart, all the files I've uploaded are no longer visible.
Any guidance is much appreciated.
Final edit: Kind of embarrassing...all I needed to do to find the /sdcard directory was just scroll down a little through the folders on the left (I thought it was supopsed to be the top directory). I'm pretty sure the 7510 is a wifi only version, but for some reason, none of the wifi ROM's I've tried will work. It gives an error and says my device is a p4 and not a p4wifi. Anyway, neither of the wifi/p4 Marshmallow ROM's will work, but all I had to do was wipe cache/delvic/system (I did do this several times) and factory reset (had not done this before) and install Cyanogenmod for p4 with the recommended Google Apps and all is working well.

[Completed] (Nexus 5) Error 7, made multiple mistakes, "assert" fix isn't working

As I understand, my situation is fairly specific, and so I need to address a few points:
This is my first time rooting a phone- I've made several mistakes but managed, at this point, to avoid bricking my phone
I'm using a Nexus 5, and flashing the pwnphone system (Android Open Pwn Project)
I've followed all the standard steps (except one... see below) for unlocking, rooting, and using TWRP as my recovery
I've also successfully flashed AOPP once, although I made an error I couldn't fix during setup and needed to reinstall
To my stupidity, I forgot to make a Nandroid backup on both attempts
I've just used TWRP to wipe my phone's Dalvik/ART Cache, system, data, and cache, assuming I could reflash the same zip I used before
MD5 check is disabled
Zip validation is disabled
Okay, so let's get down to the heart of the issue now. My phone is sitting here, plugged into my computer, I have a command prompt running, and adb is working properly. I try to flash THE SAME ZIP file I used, just before, to start from a clean slate AOPP install, and now I'm recieving an Error: 7.
I looked up the fixes for this, and ran into a problem: I'm already using the most recent version of TWRP- and I just made an alternate AOPP.zip where I removed the asserts from /META-INF/com/google/android/update-script. I was hoping this would solve my problem, but it didn't.
Now, instead of getting an Error: 7, I'm getting an "invalid zip format" notice with very little other information.
Installing zip file '/sdcard/aoppfix.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file format!
Error installing zip file '/sdcard/aoppfix.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
I have no idea what to do at this point. In my earlier error, I failed to make a Nandroid backup file- and much to my dismay- I can't even find one someone has uploaded elsewhere which I could use to at least have a functioning phone to to boot into.
Can someone please help figure out what my next course of action is?
Hi and welcome to XDA Assist !
I`ve searching and I couldn`t find that rom on the Nexus 5 development forums so it`s hard to figure out what`s the problem
Your attempts to modify that script are courageous but I`m afraid that is more than a script issue
Try to flash a different rom with xda support and you`ll get more info and help , good luck !

Categories

Resources