Related
First of all thanks to Amon_RA for this. I had no part in creating this. I am just providing a how to flash it. There may be an eaiser way but this is what worked for me.
First let me say I am on a Mac. If you are on windows the adb commands should work fine but I can't say how to get adb working for you.
1. download flash_image Here Link updated 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download Amon_AR's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
I made an automator script the help all of you having problems getting adb working. Make sure you have the android sdk downloaded and named android-sdk Put it in your home folder and then run this script. Let me know how it works for you.
Disclaimer: I am not responsible for any damage you may do to your phone. I am only providing instructions on what worked for me. This is very beta. Good luck. Enjoy the nandroid goodness.
First link is Dead...........
ooopps Srry my bad, Its up.
You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
adb push flash_image to /system/bin
Click to expand...
Click to collapse
I don't think there's a "to" in that command either. lol
testing567 said:
You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
I don't think there's a "to" in that command either. lol
Click to expand...
Click to collapse
Thanks. I don't think the "to" is going to work either. I made the corrections.
Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.
Will this put the regular android on it or keep it the same, sorry just kinda getting started with android
coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
For testing567:
Do all the adb shell commands run as root against the 2.1_root install ... or maybe the above could be simplified even more by just running "adb root" first?
For Austinjs0102 (not a question)
This process only applies (at the moment) to phones with "2.1_root" - there isn't a path at present to go from "2.1_leak" to a rooted phone. Assuming that a way to roll back (or get root) for "2.1_leak" eventually is found, then the answer to your question is this: it is a process to apply a custom recovery partition to the phone that include tools that will allow you to perform complete phone backups and restore operations. This can be critical for devs who are experimenting with writing boot or system partitions to their phones - if something goes wrong with their experiments, they can "boot" their phone into recovery mode and restore back to a working configuration. To reiterate, though: this only applies to phones that are already rooted.
bftb0
Thanks a bunch that helps clear up info.
hopefully the hard working dev's here find a 2.1 leaked fix for us early people, if not then i may need to lose the phone lol.
Austinjs0102 said:
Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.
Click to expand...
Click to collapse
I am in same boat as you...
Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc
DocTauri said:
Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc
Click to expand...
Click to collapse
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Doc,
I understand exactly what you are getting at... and also think I can explain why it's not easy.
First - what has been discovered so far was not a "root break-in", but rather an engineering ROM with root "built in". It is cryptographically signed so that a production phone will recognize the .zip file as a valid ROM. That first validation step has nothing to do with version numbers.
If the "SPL" on an unrooted phone was doing something as simple as looking at a couple of bytes in the initial file downloaded to the phone, then yes - doing what you suggest would work... just patch a few bytes using a hex editor. Unfortunately, the phone SPL is quite sophisiticated: it verifies the crypto signature on the entire zip file first, unpacks that zip, and then examines the contents of an individual file within the zip archive (and possibly even unpacks one of the YAFFS image files and then looks in a file within the YAFFS image) to read version numbers.
That means that the fundamental issue is the cryptographic signature on the .zip file. If you do anything which breaks step #1, step #2 (version # checks) are never reached. Certainly an individual file could be byte-patched, and then images and zip files could be re-assembled... but you would have no way to sign the zip with HTC's private key. Or you could even attempt to byte-patch the zip file - but then that would break the crypto signature. Either way, the crypto signature on the zip file is no longer valid.
If you have HTC's private RSA key, let us know!
bftb0
bftb0 said:
coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
Click to expand...
Click to collapse
I added the reboot because. All I would get is out of memory errors. The reboot fixed that.
e.g.
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)
northmendo -
That first link (that you corrected) now points to the recovery image, not "flash_image".
Note that the "flash_image" executable which Amon_RA originally included with his first recovery (.zip) is identical to the /system/bin/flash_image binary which ships on the Eris with 1.5 (1.17.605.1); the md5sum signature (of both of those files) is:
16559f2c27d08ff1ddfcaca05fbf10fb flash_image
That's also the same md5 signature as the "flash_image" file which was posted to dl.dropbox.
I don't have 2.1_root installed on my phone, but if the same binary is already on the phone after installing the 2.1_root ROM, there's no need to include those steps in your instructions. It is also possible that even if the "2.1_root" version of /system/bin/flash_image is different, it would also work.
Note that the only reason I bring it up is that your instructions might be (a) unnecessary, and (b) are encouraging folks to overwrite a binary that is already on the phone. No harm (but unneeded) if it is the same, and unknown harm if it is different.
Also (while I'm at it)
901167f6b5541b488c8e0404bceb0631 recovery-RA-eris-v1.6.2.img ***
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
[Edit]***Wow, my post was obsolete the moment I posted it - don't know how I missed Amon_RA's announcement post. Note that there appears to be several versions of "v1.6.2" floating around now - make sure to check his post if you want the most recent.
bftb0 said:
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
Click to expand...
Click to collapse
I will keep the link updated to the newest version here. Also I tried the quicker method without success. I will try it again when I get home from work.
Thanks
bftb0 said:
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Click to expand...
Click to collapse
Sorry, didn't mean to. Understood on the explaination. I didn't realize it was a different rom image, I thought the key had been broken, allowing someone to resign a modified image.
Thanks!
Doc
I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?
sdk issues for flashing recovery...
Hey guys,
Im a noob but here's whats going on, Ive downloaded sdk extracted it to my c drive, ive downloaded all the required packages reccomended in the forum, Ive up dated my driver and still my machine doesnt recognize my phone...
Ive also extracted the recovery image to my tools directory and added the the path in enviromentals...
So at this point Im stuck as to how to get my pc (xp) phone and sdk in sync in order to get this recovery image working...So any advice would be highly appreciated. Thanks in advance.
Chris
Spencer_Moore said:
I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?
Click to expand...
Click to collapse
You could try this.
If you have your phone pluged in and type in to the terminal
adb reboot recovery [hit enter]
After you phone reboots it should come up with text options to do back-ups and restores. Do you get any of that?
Anyone know the key combo to get into recovery without adb?
having issues getting adb
got the command prompts working in xp, however while trying the methods here in the forum i am getting adb not foud errors. Any suggestions?
I do the flash without further study, and I accidentally flash my samsung fascinate with I9000 Pit 512, and now I can't get back to stock verizon. Can anyone please help me?
thanks.
kenpachi069 said:
I do the flash without further study, and I accidentally flash my samsung fascinate with I9000 Pit 512, and now I can't get back to stock verizon. Can anyone please help me?
thanks.
Click to expand...
Click to collapse
I did something similar.. don't worry too much.. yet..
Let me find my post on this.. basically, I had to flash the US cellular kernel, then it would allow the stock fascinate kernel to take.
So flash US cellular..
then flash stock Fascinate
Here
http://forum.xda-developers.com/showpost.php?p=8195563&postcount=43
thank you
Thank you for a quick reply. I will try and let you know..
namebrandon said:
I did something similar.. don't worry too much.. yet..
Let me find my post on this.. basically, I had to flash the US cellular kernel, then it would allow the stock fascinate kernel to take.
So flash US cellular..
then flash stock Fascinate
Here
Click to expand...
Click to collapse
I tried, and it still doesn't work. I think the problem is not the kernel. The problem is the PIT file that I also flashed. I need to map to the right place, I can't find i500 PIT file anywhere. I hope someone can direct me. thanks.
kenpachi069 said:
I tried, and it still doesn't work. I think the problem is not the kernel. The problem is the PIT file that I also flashed. I need to map to the right place, I can't find i500 PIT file anywhere. I hope someone can direct me. thanks.
Click to expand...
Click to collapse
I've got it at home, but not here. I got it from angel (fallingup) originally. PM him.
namebrandon said:
I've got it at home, but not here. I got it from angel (fallingup) originally. PM him.
Click to expand...
Click to collapse
If you get home can you upload it for me, please?
Thanks.
Gotta love dropbox. extract from zip.
namebrandon said:
Gotta love dropbox. extract from zip.
Click to expand...
Click to collapse
Nice, thank you so much. Now i just have to find the right file to flash it back. Where do i get the file for pda, phone, and csc?
Sorry, I am really noob to android. Once again, thank you for all the help.
kenpachi069 said:
Nice, thank you so much. Now i just have to find the right file to flash it back. Where do i get the file for pda, phone, and csc?
Sorry, I am really noob to android. Once again, thank you for all the help.
Click to expand...
Click to collapse
You only use PDA.. And rarely would you ever use the PIT file.
You can find the stock odin files here, in the first post.
http://forum.xda-developers.com/showthread.php?t=782204
namebrandon said:
You only use PDA.. And rarely would you ever use the PIT file.
You can find the stock odin files here, in the first post.
Click to expand...
Click to collapse
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
kenpachi069 said:
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
Click to expand...
Click to collapse
What does..? I don't know what "it" is man.. Is that during recovery?
Regardless, if you're getting that output from the phone, we're heading in the right direction.
Well after I do the system restore, it just reboot and that's what it say.
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
It won't start up.
kenpachi069 said:
Well after I do the system restore, it just reboot and that's what it say.
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
It won't start up.
Click to expand...
Click to collapse
Ok.. You need to start over.. using the files from the post I linked to..
Start Odin, and flash the /system file. You use the PDA box. You do not put anything in PIT.
Then do the same thing, but use the stock kernel file.
Then do the same thing, and use the stock recovery file.
namebrandon said:
Ok.. You need to start over.. using the files from the post I linked to..
Start Odin, and flash the /system file. You use the PDA box. You do not put anything in PIT.
Then do the same thing, but use the stock kernel file.
Then do the same thing, and use the stock recovery file.
Click to expand...
Click to collapse
There is a PIT file in that thread now. Use it if you flashed another phone's pit file.
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
I am stuck at this after doing one click restore odin3 for captivate on galaxy s i500.
i can get to download mode, using homemade jig.
please someone help me when i flash my phone to atleast normal mode. please
kenpachi069 said:
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
Click to expand...
Click to collapse
This means ur phones file systems those 2: stl11 is your /system/ and mmcblk0p1 is your /data/ and if it cant read it then that means you must have had voodoo 5 enabled and it converted all of ur file system to ext4
Sent from my SCH-I500 using XDA App
atinder said:
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
I am stuck at this after doing one click restore odin3 for captivate on galaxy s i500.
i can get to download mode, using homemade jig.
please someone help me when i flash my phone to atleast normal mode. please
Click to expand...
Click to collapse
I have several questions...
1) Why does getting into download mode require a homemade jig?
2) What were you running before you tried to restore back to stock?
....oh what was that third one....OH YEA
3) Why on gods green earth would you use the one click restore for the captivate on the fascinate!? If you got it from here...you'll notice that in all caps in the title it says "CAPTIVATE ONLY". le sigh.
This is the thread with the files you need: http://forum.xda-developers.com/showthread.php?t=782204
I'm not sure if the one click restore also writes over your modem...but if it did you need to go into irc (irc.freenode.net #samsung-facinate) and ask someone for it.
In addition, if you were running voodoo before doing this you'll need someone more acquainted with these sort of facepalm dilemmas. These people can also be found in irc.
Advice: Read Read Read....and don't think about or mention taking your phone in to verizon. The irc gods will smite you.
If you flashed another galaxy S's ANYTHING, you now have a brick.
Now go ahead and pat yourself on the back. You've earned it.
Also, this thread is totally in the wrong section. Just sayin'.
Sent from my SCH-I500 using XDA App
times_infinity said:
If you flashed another galaxy S's ANYTHING, you now have a brick.
Now go ahead and pat yourself on the back. You've earned it.
Also, this thread is totally in the wrong section. Just sayin'.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
False..
It's a stupid move, but far from a brick.
atinder said:
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
Click to expand...
Click to collapse
You need to follow this http://forum.xda-developers.com/showthread.php?t=804784
Redwing said:
I have several questions...
In addition, if you were running voodoo before doing this you'll need someone more acquainted with these sort of facepalm dilemmas. These people can also be found in irc.
Advice: Read Read Read....and don't think about or mention taking your phone in to verizon. The irc gods will smite you.
Click to expand...
Click to collapse
Completely agree.
Sup I know there is a hack for ext4 on the nexus s but haven't seen anything for the NS4G. Is it the same hack or what? If so it seems a little complicated to get going with the tutorial given. Does anybody have a better tutorial or if there is a different hack for the 4g can you direct me to it please? Much appreciated.
Sent from my Nexus S 4G using xda premium
Joshhayes801 said:
Sup I know there is a hack for ext4 on the nexus s but haven't seen anything for the NS4G. Is it the same hack or what? If so it seems a little complicated to get going with the tutorial given. Does anybody have a better tutorial or if there is a different hack for the 4g can you direct me to it please? Much appreciated.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
not sure what "ext4 hack" youre talking about, but there is an ext4 mount script. itll give you a little speed/performance kick overall. but its not really a hack, its a fix. type this in a terminal emulator app..
su(press enter)
mount -o remount,noauto_da_alloc /data /data(press enter)
youll have to type it in after each reboot. or you can use an app to run it after each boot. most custom kernels already include it or some version of it, stock doesnt include it.
Use dsixda's rom kitchen to unpack boot.img: http://forum.xda-developers.com/showthread.php?t=633246
Then do this: http://forum.xda-developers.com/private.php?do=showpm&pmid=4452832 and repack.
snandlal said:
Use dsixda's rom kitchen to unpack boot.img: http://forum.xda-developers.com/showthread.php?t=633246
Then do this: http://forum.xda-developers.com/private.php?do=showpm&pmid=4452832 and repack.
Click to expand...
Click to collapse
That second link seems to not work, it says this "Invalid Private Message specified. If you followed a valid link, please notify the administrator"
Joshhayes801 said:
That second link seems to not work, it says this "Invalid Private Message specified. If you followed a valid link, please notify the administrator"
Click to expand...
Click to collapse
fter unpacking the boot.img go to BOOT_EXTRACTED/ramdisk and open the file init.herring.rc and add the following in green to the following to lines and save:
Code:
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/system /system wait ro noauto_da_alloc
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata /data wait noatime nosuid nodev noauto_da_alloc
Sorry bout that
Sweet. Thanks. I'll be doing this later after I run errands.
Sent from my Nexus S 4G using xda premium
snandlal said:
fter unpacking the boot.img go to BOOT_EXTRACTED/ramdisk and open the file init.herring.rc and add the following in green to the following to lines and save:
Code:
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/system /system wait ro noauto_da_alloc
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata /data wait noatime nosuid nodev noauto_da_alloc
Click to expand...
Click to collapse
I think I've done everything right and getting ready to flash soon. How will I know if it worked?
So I did everything you said, repacked (no errors, everything worked fine) now when trying to flash it gives me this "error in/tmp/sideload/package.zip (status 6)" Do you have any clue why this would happen?
EDIT: NVM I fixed it.
I don't understand why people want to make it harder on themselves. just run the script, it does the same thing.
simms22 said:
I don't understand why people want to make it harder on themselves. just run the script, it does the same thing.
Click to expand...
Click to collapse
It's not really hard...it's actually kind of easy with that particular kitchen. Plus I am willing to do it all because I like learning.
Joshhayes801 said:
It's not really hard...it's actually kind of easy with that particular kitchen. Plus I am willing to do it all because I like learning.
Click to expand...
Click to collapse
good answer
Hmm
Tried to flash the repacked rom and got stuck in a bootloop. Really can't find anything on why this happened or how to fix. Restoring nandroid as we speak.
simms22 said:
good answer
Click to expand...
Click to collapse
Lol. yeah well we all gotta start somewhere. I practically live on xda as it is, so I may as well learn as much as I can and hopefully become a contributor in some way. It started as just wanting to dink sound with my own device but now that I know that I CAN do it. I want to go further with it.
Sent from my Nexus S 4G using xda premium
I've been flashing N7 with no issues as recently as over the weekend. Today I tried to flash a new ROM and it failed. Tried a second, different ROM, same result. Do not know what I did. Any thoughts?
Error log would help greatly.
How do I get/generate the log? Haven't had to do it before.
Thanks,
Paul
The logs= errors displayed on the screen provided by the interface you use to flash the rom (recovery, computer...)
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
do I need to create a partition? Never get more details despite the tease.
Thanks,
First -
Try and download a different (NEWER) TWRP. Re-flash TWRP. Try again
or
Have you tried completely wiping the device? And pushing a ROM from ADB or using a USB OTG and Memory stick?
I had issues with my nexus becoming VERY unstable. Leading to issues.
I completely, and I mean completely, wiped. To the point that all that device basically had was a recovery, and a bootloader.
I proceeded to flash again, BOOM all fixed up.
Is there a new TWRP?
I did a factory restore after wiping everything thing, if that is what you mean?
It was working as expected last week, don't know what I did to screw it up
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
ibsk8 said:
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Did this, and it said it copied but I am unable to locate it. It says 0\media\data But that folder structure doesn't exist, at least according to file expert
Will a complete wipe/restore create a partition?
pmgreen said:
Will a complete wipe/restore create a partition?
Click to expand...
Click to collapse
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
pmgreen said:
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
Click to expand...
Click to collapse
Focus your efforts here; it certainly looks like a first-order problem.
bftb0 said:
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
Focus your efforts here; it certainly looks like a first-order problem.
Click to expand...
Click to collapse
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
pmgreen said:
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
Click to expand...
Click to collapse
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
bftb0 said:
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
Click to expand...
Click to collapse
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
pmgreen said:
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
Click to expand...
Click to collapse
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ su
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
bftb0 said:
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ such
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
Click to expand...
Click to collapse
Thanks bftb, you are correct it's a can't open zip. No error than fail and it can't open the zip. It says updating partition but nothing changes
The file names are from the developers, once of which I recently successfully flashed. Tried coping the log to the SD card, but unable to find /data/media/0. Do I need to recreate a partition?
(FYI there was an auto-correct typo in my prior post - "su" not "such". Derp)
pmgreen said:
Do I need to recreate a partition?
Click to expand...
Click to collapse
No. (There is no way to do that with the tools we have anyway)
Unless what you mean by "recreate" is rebuild/reinitialize a filesystem in a partition - that's a possibility.
You need to try and figure out why you can't read files.
As a workaround, you can put files on a USB key (FAT formatted, not NTFS) and using TWRP access them by putting the USB key on the other end of a OTG cable.
Your posts are a bit vague - I can't even tell if you have tried other ROM files, whether you checked them to see if they are the correct size/checksum, etc.
pmgreen said:
Tried coping the log to the SD card, but ...
Click to expand...
Click to collapse
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
bftb0 said:
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
Click to expand...
Click to collapse
I am not familiar using ADB pull. Tried using a root file manager to access the log but don't see.
Greatly appreciate your help, let me know what other info I should paste.
Thanks,
Is there any roms for US version p8 lite with snapdragon chip? I see few custom roms but doesnt say which version of the phone is for.
https://download.mokeedev.com/?device=chm_cl00
btw any honor 4c (SD version) roms should work
Audriuskins said:
https://download.mokeedev.com/?device=chm_cl00
btw any honor 4c (SD version) roms should work
Click to expand...
Click to collapse
thanks for your help. but got a error when i flash the rom. device is not correct
claudiuslu2011 said:
thanks for your help. but got a error when i flash the rom. device is not correct
Click to expand...
Click to collapse
Are you sure that you have Snapdragon version?
claudiuslu2011 said:
thanks for your help. but got a error when i flash the rom. device is not correct
Click to expand...
Click to collapse
It give you the error becuase your device is not signed in update-script. You need to add it by yourself
Audriuskins said:
Are you sure that you have Snapdragon version?
Click to expand...
Click to collapse
yes snapdragon 615
XTutorials said:
It give you the error becuase your device is not signed in update-script. You need to add it by yourself
Click to expand...
Click to collapse
I went to update-script and add my device id to it, i got another error saying "error executing updater binary in zip"
Also tried this like claudiuslu2011 and got the same error. Before error message, twrp gives the following output
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at /system; no such file or directory
unmount of /system failed; no such volume
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Is this implying the system partition has a different name than /system?