Official LineageOS 14.1 for Samsung Galaxy Note 8.0 GT-N51xx
### REQUIRES FULL WIPE A.K.A. CLEAN INSTALL ###
# download odin for windows
http://forum.xda-developers.com/showthread.php?t=2711451
# flash this recovery via odin (AP button)
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
# unofficial nightly build
https://visi0nary.de/builds/full/
# official weekly build - n5100 3G
https://download.lineageos.org/n5100
# official weekly build - n5110 WIFI
https://download.lineageos.org/n5110
# official weekly build - n5120 LTE
https://download.lineageos.org/n5120
# flash gapps via recovery
http://opengapps.org/
Thanks a lot to @BlueFlame4 and @walter79 for their build server !
XDA:DevDB Information
[ROM] Official LineageOS 14.1 for GT-N51xx, ROM for the Samsung Galaxy Note 8.0
Contributors
rgib
Source Code: https://github.com/LineageOS/android_kernel_samsung_smdk4412/tree/cm-14.1
ROM OS Version: 7.x Nougat
Version Information
Status: Alpha
Created 2017-01-06
Last Updated 2017-03-06
Congrats Sir. Always the best. Thank you
Congratulations Roberto! You should be really proud of this as a first release.
I promise you all you will NOT be disappointed with this first Lineage release and marshmallow will be but a distant memory..... ?
Thanks Roberto. Excellent effort. ???
Sent from my GT-N5120 using Tapatalk
Just for information, for my N5100 the SIM-card was not detected after a dirty flash. Didn't want to wipe and clean flash so I went back and can't provide logs. As written, just for information.
mielletseed said:
Just for information, for my N5100 the SIM-card was not detected after a dirty flash. Didn't want to wipe and clean flash so I went back and can't provide logs. As written, just for information.
Click to expand...
Click to collapse
New OS, therefore requires a clean flash to start with, a dirty would just cause no end of pain...
mielletseed said:
Just for information, for my N5100 the SIM-card was not detected after a dirty flash. Didn't want to wipe and clean flash so I went back and can't provide logs. As written, just for information.
Click to expand...
Click to collapse
Try to backup you cm-13.0. Then clean install my unofficial LineageOS 14.1 build and report if you get SIM-card.
Mine works.
rgib said:
Try to backup you cm-13.0. Then clean install my unofficial LineageOS 14.1 build and report if you get SIM-card.
Mine works.
Click to expand...
Click to collapse
After a full wipe I got SIM-PIN-dialog, seems to be working
No I try to use your build and restore my data ...
@rgib: an other information: there were two errors while installing.
Code:
I:operation_start: 'Flashing'
Installing zip file '/external_sd/0_Installation/lineage-14.1-20170106-UNOFFICIAL-n5100.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Target: samsung/kona3gxx/kona3g:4.4.4/KTU84P/N5100ZTCNL6:user/release-keysTarget: samsung/kona3gxx/kona3g:4.4.4/KTU84P/N5100ZTCNL6:user/release-keys
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...
performing update
Patching system image unconditionally...
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/13c23145f94d68015632f2cd29899c1aaf9ad199/
1557766144 bytes free on /cache (0 needed)
erasing 224813 blocks
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 757 blocks of new data
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 734 blocks
wrote 168403 blocks; expected 168403
stashed 0 blocks
max alloc needed was 4096
[COLOR="Red"]E:unknown command [log]
E:unknown command [log][/COLOR]
deleting stash 13c23145f94d68015632f2cd29899c1aaf9ad199
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
/tmp/install/bin/backuptool.sh: cd: line 113: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory
script succeeded: result was [1.000000]I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 0MB, free: 8872MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
@rgib
Installed your lineage-14.1-20170107-UNOFFICIAL-n5120.zip from firmware stock after a wipe data and cache.
Gps not work
Sim not work
Bluetooth instable
wifi with mac correct :works
camera works
Here my logs
Thanks for your what you are doing for us and Happy new Year!!
mielletseed said:
@rgib: an other information: there were two errors while installing.
Code:
E:unknown command [log]
E:unknown command [log
Click to expand...
Click to collapse
All cm14 based builds have given / are likely to give this error. It's nothing to bother about.
kaworuxda said:
@rgib
Installed your lineage-14.1-20170107-UNOFFICIAL-n5120.zip from firmware stock after a wipe data and cache.
Gps not work
Sim not work
Bluetooth instable
wifi with mac correct :works
camera works
Here my logs
Thanks for your what you are doing for us and Happy new Year!!
Click to expand...
Click to collapse
Flashed Rom found the same as quoted
Logs attached
Cheers
Al
tu sei il migliore
installed the 7.01.2017 build for gt-n5100 :
GPS/location works fine
SIM works fine ( incoming outgoing ok, haven't tested data though ...)
WIFI Mac ... Works fine
Bluetooth transfers ... works fine
camera can take photos but not videos app crashes in video mode
SD cards work but inbuilt file manager won't open SD card files, asks for root access mode, tried enabling root access for apps and adb in dev mode as well as file manager but nothing happens...
wish you a very Happy New Year and thank you for your efforts .....
arnob2014 said:
camera can take photos but not videos app crashes in video mode
SD cards work but inbuilt file manager won't open SD card files, asks for root access mode, tried enabling root access for apps and adb in dev mode as well as file manager but nothing happens...
Click to expand...
Click to collapse
CM file manager is very buggy still - try deleting a directory named ".android_secure" from your sdcard if it exists (but you will need different file manager to do this, others will work)
Camera - try 3rd party apps, e.g. camu, cameringo, open camera - some / all / none may work better
All work fine..thanks very much dev for your works..thumb up.!
ROM - lineage-14.1-20170107-UNOFFICIAL-n5100
GApps - open_gapps-arm-7.1-pico-20170107
Root(systemless) - SR2-SuperSU-v2.79-SR2-20170103215521
Camera - Open Camera
@rgib FYI if you wanna use the built in update mechanism from LOS use https://visi0nary.de/api as OTA host. Example: https://github.com/visi0nary/android_device_elephone_p8000/blob/cm-12.1/system.prop#L170
Buff99 said:
All cm14 based builds have given / are likely to give this error. It's nothing to bother about.
Click to expand...
Click to collapse
I can confirm that. Exactly the same errors during installation. Beside that I get the "new SIM card detected" error which was there sometimes in CM13. I need to do some further testing, but the device seems pretty stable.
rgib, you really make me appreciate my Note 8 after all this years. Thanks!
i'm very impressed with the first build ! thanks a lot Roberto !
TibReg said:
I can confirm that. Exactly the same errors during installation. Beside that I get the "new SIM card detected" error which was there sometimes in CM13. I need to do some further testing, but the device seems pretty stable.
rgib, you really make me appreciate my Note 8 after all this years. Thanks!
Click to expand...
Click to collapse
Try to update baseband
Related
Hi devs,
Are you aware of any work (for other Android phones, for instance), where an altered mtd kernel driver was used to allow (raw) root access anyplace within flash memory? (For example, maybe a raw pseudo-partition which overlaps all the other partitions?) The stock mtd driver creates devices in the kernel device tree only for specific partition slices (boot, system, recovery, data, cache) - for obvious safety and security reasons.
After all these months, I stumbled across this tonight
Code:
C:\foo>fastboot oem listpartition
...
INFO[radio]:(OTHER) block start=0, size=332 (42496 KB)
INFO[hboot]:(RAW) block start=333, size=6 (768 KB)
INFO[misc3]:(RAW) block start=339, size=2 (256 KB)
INFO[mfg]:(RAW) block start=341, size=2 (256 KB)
INFO[sp1]:(RAW) block start=343, size=6 (768 KB)
INFO[misc2]:(RAW) block start=349, size=3 (384 KB)
INFO[mfg2]:(RAW) block start=352, size=3 (384 KB)
INFO[recovery]:(RAW) block start=355, size=40 (5120 KB)
INFO[boot]:(RAW) block start=395, size=20 (2560 KB)
INFO[system]:(YAFFS) block start=415, size=1360 (179520 KB)
INFO[cache]:(YAFFS) block start=1775, size=1040 (137280 KB)
INFO[userdata]:(YAFFS) block start=2815, size=1276 (168432 KB)
INFO[misc]:(RAW) block start=4091, size=5 (640 KB)
INFO[microp]:(OTHER) block start=0, size=0 (0 KB)
INFO[nv]:(OTHER) block start=0, size=0 (0 KB)
INFO[tp-melfas]:(OTHER) block start=0, size=0 (0 KB)
OKAY [ 0.071s]
finished. total time: 0.071s
I had never seen references in the Eris forums to the misc3, mfg, sp1, misc2, or mfg2 partitions - I suppose one or more are for boot images. Maybe interesting to boot a kernel image that had access to them, and have a peek at them?
bftb0
You are venturing into an area that is slightly beyond my current level of understanding. (Although we can all learn more.)
Is this even close to what you are looking for?
http://forum.xda-developers.com/showthread.php?t=754805
I'm thinking not, since they appear to be resizing the existing partitions, which doesn't seem to be quite what you are looking for.
I was asking about this a while back to see if anyone was able to get read access to the splash1 (i'm guessing sp1) partition so we could dump the REAL original splash screen for people that needed to go back to full stock. This was basically the only thing that is left out of going to stock since the "original" boot image that I had used for the android skateboards in my post about changing the boot logo was just a resized version I found online somewhere which is slightly bigger than the original if you look closely. I had some info laying around somewhere but it was definitely something about people modifying the mtd drivers in the kernel to get this done.
Without the modified drivers there is no way to do a FULL nand dump at this point.
gnarlyc said:
You are venturing into an area that is slightly beyond my current level of understanding. (Although we can all learn more.)
Is this even close to what you are looking for?
http://forum.xda-developers.com/showthread.php?t=754805
I'm thinking not, since they appear to be resizing the existing partitions, which doesn't seem to be quite what you are looking for.
Click to expand...
Click to collapse
Well, I'd seen that before - but THANK YOU - your post encouraged me to do a better job of searching, and I came up with this:
http://forum.xda-developers.com/showthread.php?t=542688
[SIZE=+2]Awesome![/SIZE] It appears that no mtd kernel hack is needed - as long the Eris kernels we are using accept those parameters (obviously, a little additional work is needed to get the offsets correct for the Eris).
I knew that partitions could be resized - but I wasn't aware that you could add new partition definitions. If it works for the Eris, then cool. (I have to say - the G1/G2/Hero devs surely have turned over a lot of stones that have helped us.)
bftb0
Mohahahhahahahaaha (rubbing hands together deviously). I smell either some interesting development or at least some interesting information coming out of this.
It's working.
More details later.
Flash Memory Map for the Eris:
Code:
PARTITION START END SIZE(1KB) SIZE(128KB) NOTES
radio 0x00000000 - 0x02980000 42,496 332 (3)
- gap! - 0x02980000 - 0x029a0000 128 1 (3)
hboot 0x029a0000 - 0x02a60000 768 6 (2)
misc3 0x02a60000 - 0x02aa0000 256 2 (5)
mfg 0x02aa0000 - 0x02ae0000 256 2 (6)
sp1 0x02ae0000 - 0x02ba0000 768 6 (4)
misc2 0x02ba0000 - 0x02c00000 384 3 (4)
mfg2 0x02c00000 - 0x02c60000 384 3 (4)
recovery 0x02c60000 - 0x03160000 5,120 40
boot 0x03160000 - 0x033e0000 2,560 20
system 0x033e0000 - 0x0dde0000 174,080 1360
cache 0x0dde0000 - 0x15fe0000 133,120 1040
userdata 0x15fe0000 - 0x1ff60000 163,328 1276
misc 0x1ff60000 - 0x20000000 640 5
( You can verify the above on your own phone with a combination of examining /proc/mtd, "dmesg" output immediately after the boot, and output of "fastboot oem listpartition" )
(1) Note all partitions are aligned to a 128-KB boundary (0x20000 - 18 bits)
Presumably this is why "fastboot oem listpartition" reports sizes in this unit
(2) Hboot images from HTC for the Eris have always been exactly 512 KB. Slack space is here,
but I found nothing but 0xFF's in the slack area.
(3) Attempting to dump the from this partition produces many, many error messages of the form:
mtd: MEMGETBADBLOCK returned -1 at 0x02940000 (errno=5)
mtd: MEMGETBADBLOCK returned -1 at 0x02960000 (errno=5)
(4) On my phone, dumps of partitions "sp1", "mfg2" and "misc2" produced un-interesting data blobs: all 0xFF's
Note that I have never flashed a custom boot splashscreen.
(5) Nearly "empty" - bytes not 0x00 or 0xFF are all string data (including CID)
(6) Contains "interesting" string data (including handset ID, manufacturing date, etc) and other binary data. Performing interesting handset operations and then recapturing a partition dump (before/after) and performing a binary diff could reveal strategic locations.
[SIZE=+1]HOW-TO[/SIZE]
Most people have absolutely no business doing this - you have been warned.
Under no circumstances should you hand-type any of these addresses; a simple typo could lead to disaster.
Code:
fastboot -c " mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata) " boot recovery-RA-Eris-v1.6.2.img
will produce the standard kernel partition mappings. Note the leading and trailing spaces in the quoted string - and that the order of appearance is critically important
You may append one or more** of the following, separated with commas as shown in the above (standard mapping) command.
[email protected](radio)
[email protected](hboot)
[email protected](misc3)
[email protected](mfg)
[email protected](sp1)
[email protected](misc2)
[email protected](mfg2)
** I performed individual boots adding only one non-standard partition, and can not guarantee that a disaster will not result if you try to append more than one - or all of them - in one boot.
You can verify the additional partitions have been kanged into the kernel's device tree with
adb shell cat /proc/mtd
and may dump individual partitions via the command "dump_image" (provided by Amon_RA in /sbin), as in the following example:
mount /sdcard
dump_image mfg /sdcard/part.mfg.img
bftb0
If you just want to dump a specific Eris flash memory partition(s) off your phone, there is an even easier method. (Doh!)
Prerequisites:
- 1.49.2000 S-OFF bootloader is installed on your Eris.
- working device drivers on PC and fastboot utility
Steps:
1) Connect via USB to your PC and put phone in FASTBOOT mode (Power up with Send+End)
2) Get the partition names listing using
Code:
fastboot oem listpartition
3) Using the following fastboot syntax, plug in the desired partition name (PNAME):
Code:
fastboot oem saveprt2sd PNAME -n PNAME.bin -a
for example, the "sp1" partition:
Code:
$ fastboot oem saveprt2sd sp1 -n sp1.bin -a
... INFOSaveImageToSD partition file name:sp1
INFOSaveImageToSD output file name:sp1.bin
INFOCmd5 CMD_TIMEOUT
INFOsdcc_poll_status(): i=21
INFOCmd5 polling status timed out
INFOSD: CMD5 fail, rc=2 ..
INFOSD 2.0
INFOHC card
INFO Searching free data sectors....
INFO [SAVE2SD] 131072 bytes saved.
INFO [SAVE2SD] 262144 bytes saved.
INFO [SAVE2SD] 393216 bytes saved.
INFO [SAVE2SD] 524288 bytes saved.
INFO [SAVE2SD] 655360 bytes saved.
INFO [SAVE2SD] 786432 bytes saved.
INFO [SAVE2SD] Done.
OKAY [ 1.728s]
finished. total time: 1.728s
Yep, it really is that simple.
bftb0
Does anyone know where I can find property files for Folio 100. I think that mblaster and DerArtem know the answer and when I type
Code:
sudo make_ext4fs -l 268435456 -a system output_file/system.img path_to_your_rom/folder_name
I get:
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 999/16384 inodes and 65063/65536 blocks
error: open_output_file: open: No such file or directory
Click to expand...
Click to collapse
Please help and sorry if I posted in wrong path
The system.prop is in the root of the repository, the default.prop is in the ramdisk subdirectory.
Here is DerArtems repository (seems to be the most up to date atm): https://github.com/DerArtem/android-device-betelgeuse
Don't know what is wrong with the make_ext4fs. I usually don't run it as root, but in principle this should not be a problem.
Thanks and do you know is this folio honeycomb kernel source?
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
What this mean? Can't find system.img?????????
error: open_output_file: open: No such file or directory
Found solution!!!
>>>>x_x<<<<...>>>>new error:
error: do_inode_allocate_extents: Failed to allocate 418 blocks
Jon2555 said:
Thanks and do you know is this folio honeycomb kernel source?
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
Click to expand...
Click to collapse
DerArtem started this, but afaik he never finished it.
Jon2555 said:
>>>>x_x<<<<...>>>>new error:
error: do_inode_allocate_extents: Failed to allocate 418 blocks
Click to expand...
Click to collapse
Sorry, never seen this error...
Thanks
Sent from my IDEOS S7 Slim using XDA App
I found what was the error. Size of files was bigger than 268 mb that I set when I want to pack system.img.
EDIT: It won't flash system.img. Only hope is to delete some files when packing if size is larger than 268.4 mb.
Hello!
I think this post may be of more relevance to Development. But unfortunately, I do not have enough posts to do so. I usually don't have to post at all, thanks to searching.
This time I can't seem to find an answer to my problem, so here it goes;
I have an Eris that I'm using at the moment. I rooted it(or so I thought) back in the day. It seemed to work fine back then, and everything was dandy.
Never went about installing a custom ROM though, so I attempted. After I started it up, I realized I had made the worst mistake of them all. I didn't make a nandroid backup of the stock ROM. After a couple boot loops of the Cyanogen logo, I powered it into the bootloader to find that "S-ON" was showing. I cried a little at that moment.
If I try to install any other ROM(stock, EvilEris, etc.), it does not work. And after a couple of attempts of trying to install CM again, now only getting to the skateboarding androids, I have no idea what to do.
Does anyone possibly have a solution to this? I'm at a complete loss not being able to actually boot the phone into the ROM.
Also, everytime I try to just throw a PB00IMG.ZIP on the root of the SD card, it says there's "No image!"
Thank you for any help,
-Kickore
kickore said:
Hello!
I think this post may be of more relevance to Development. But unfortunately, I do not have enough posts to do so. I usually don't have to post at all, thanks to searching.
This time I can't seem to find an answer to my problem, so here it goes;
I have an Eris that I'm using at the moment. I rooted it(or so I thought) back in the day. It seemed to work fine back then, and everything was dandy.
Never went about installing a custom ROM though, so I attempted. After I started it up, I realized I had made the worst mistake of them all. I didn't make a nandroid backup of the stock ROM. After a couple boot loops of the Cyanogen logo, I powered it into the bootloader to find that "S-ON" was showing. I cried a little at that moment.
If I try to install any other ROM(stock, EvilEris, etc.), it does not work. And after a couple of attempts of trying to install CM again, now only getting to the skateboarding androids, I have no idea what to do.
Does anyone possibly have a solution to this? I'm at a complete loss not being able to actually boot the phone into the ROM.
Also, everytime I try to just throw a PB00IMG.ZIP on the root of the SD card, it says there's "No image!"
Thank you for any help,
-Kickore
Click to expand...
Click to collapse
Before you try the PB00IMG.zip, are you going into the Wipe menu and choosing the option "Wipe data/factory reset" before restarting the phone? If not, try starting in Recovery, do just that, and then try to restart. (Depending on the CM ROM you are installing, you may need to install a Google apps zip as well, if you have not already done so. However, it will boot without Google apps - you just will not have the market.)
This is what happens when I go to wipe/factory reset the phone.
I'm sorry I wasn't a bit more descriptive in my first post.
I have clockwork mod recovery 2.5.0.1.
...With S-On...
This picture shows why I can't love anything.
Since you have clockwork recovery, definitely do not try a PB00IMG.zip. There have been bricked phones from this.
See this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9
This may be a good idea. That line "Can't read MISC" - I wonder if you have some bad blocks on that partition (or others)? Anyway, read through that post I listed above, flash that zip file, and it will create a file on the SD card called "MTD_Inspect.txt". Let's see what that shows.
(I think that once we determine the state of flash storage, the best bet may be to flash the Flashback_21v2, which will return the phone to stock, unrooted, and then you can re-root using ScaryAlien's modified version of JCase's 1-click root app to get Amon_RA recovery on the phone. Getting S-OFF going forward may not be such a bad idea, but one step at a time.)
Listen to doogald, he's giving you some good advice!
doogald said:
Since you have clockwork recovery, definitely do not try a PB00IMG.zip. There have been bricked phones from this.
See this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9
This may be a good idea. That line "Can't read MISC" - I wonder if you have some bad blocks on that partition (or others)? Anyway, read through that post I listed above, flash that zip file, and it will create a file on the SD card called "MTD_Inspect.txt". Let's see what that shows.
(I think that once we determine the state of flash storage, the best bet may be to flash the Flashback_21v2, which will return the phone to stock, unrooted, and then you can re-root using ScaryAlien's modified version of JCase's 1-click root app to get Amon_RA recovery on the phone. Getting S-OFF going forward may not be such a bad idea, but one step at a time.)
Click to expand...
Click to collapse
Sorry it took a minute.
Here's what the MTD inspect gave me.
Code:
Eris MTD Partition Status Report Generated on Fri May 18 22:11:36 UTC 2012
PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS
misc /dev/mtd/mtd0 655360 0 5 0 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 20 20 0 0 0
system /dev/mtd/mtd3 178257920 1350 1360 0 0 0
cache /dev/mtd/mtd4 136314880 9 1040 18 0 0
userdata /dev/mtd/mtd5 167247872 1 1276 0 0 0
#################################### misc PARTITION ###################################
Partition Symbolic Name: misc
Partition (character-special) Device: /dev/mtd/mtd0
Partition Total Size: 655360
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
#################################### recovery PARTITION ###################################
Partition Symbolic Name: recovery
Partition (character-special) Device: /dev/mtd/mtd1
Partition Total Size: 5242880
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
#################################### boot PARTITION ###################################
Partition Symbolic Name: boot
Partition (character-special) Device: /dev/mtd/mtd2
Partition Total Size: 2621440
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 20
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### system PARTITION ###################################
Partition Symbolic Name: system
Partition (character-special) Device: /dev/mtd/mtd3
Partition Total Size: 178257920
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1350
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### cache PARTITION ###################################
Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 18
ECC corrected: 0
Number of bad blocks: 9
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### userdata PARTITION ###################################
Partition Symbolic Name: userdata
Partition (character-special) Device: /dev/mtd/mtd5
Partition Total Size: 167247872
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
Apparently, I have a few.
Ok, the next step is probably to try what is in this post: http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
That post mentions that you should download a decent ROM, but I think that you are already there.
Just a quick note: you should also read the warning in bright red here: http://forum.xda-developers.com/showpost.php?p=11652502&postcount=40
Never mind, I'll quote it:
ErisMTDNuke_v0.9.zip IS EXTREMELY DANGEROUS AND SHOULD NOT BE USED WILLY-NILLY. IT'S ONLY USE IS FOR DESPERATE, LAST-RESORT MEASURES - CLOCKWORK "SOFT BRICKINGS" WHERE PARTITION CORRUPTION IS EVIDENT.
Click to expand...
Click to collapse
At this point, please understand that your phone is bricked and it may not come back. Let's see what the ErisMTDNuke does, though.
I mentioned earlier the thought of unrooting by flashing Flashback and then re-rooting with JCase's 1-click app. That's still a possibility, too. That will at least replace the Clockwork Recovery with stock Recovery. However, the other way is to flash the CM7 ROM that you were going to flash anyway and replace the recovery using the app GScript Lite.
Flashback can be downloaded from here: http://forum.xda-developers.com/showthread.php?t=792026
You can download the one without the radio, if that's what you want to do.
Anyway, let's see what ErisMTDNuke does. Good luck.
Dear doogald,
You are the coolest person on the internet. You have saved my phone by referencing forum posts made years ago that I totally couldn't figure out by myself.
Thank you very much.
I'm happy to announce that my phone has completed it's boot into stock, and I can now drag down my lock screen and activate my phone on the Verizon network.
I'll take to Jcase's one-click app tomorrow.
Thank you again,
-Kickore
P.s. Seriously, the coolest person on the internet ever.
Wow, that's awesome. Thanks redirected to bftb0, who did all of that work.
The way to install Amon_RA is here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
You should be able to use Scenario 5 in the first post (the JCase 1-click app method) that ScaryAlien mentions that it works with stock or stock-based ROMs like xtrSENSE. Just remember that 1-click works like this:
- allow third party app installs in settings->applications
- install the app (you may need the free app Astro File Manager to actually install by opening the .apk file in that app and choosing to install the app)
- run the 1-click app
- shut down and restart the phone - don't restart in recovery; restart as if you were going to make a phone call
- shut down and restart in Recovery by holding VolUp while booting
At some point I'll also post what you'd need to do to get the S-OFF engineering bootloader on, which will allow you to fastboot flash to recover any future problems (which, knock wood, will not happen...)
I attempted Jcase's app. It did give me Amon_RA's Recovery. It did not give me S-Off though, which I'm assuming is why you mentioned the engineering bootloader in your last post.
On a side note, I decided to experiment with something that wasn't clockwork mod, and found that I can flash custom ROMs with this Recovery. I also backed up my stock one this time, JUST IN CASE!
Well, it worked and I'm running GSB v4.5!
Still, I really appreciate it regardless of who originally found/wrote the documentation on how to do it. I'm a user with like 5 posts due to everything being figured out usually, and you're still helping instead of "GOOGLE IT."
So thank you.
kickore said:
I attempted Jcase's app. It did give me Amon_RA's Recovery. It did not give me S-Off though, which I'm assuming is why you mentioned the engineering bootloader in your last post.
Click to expand...
Click to collapse
Which version of the bootloader do you have? It will either be 1.46.0000, 1.47.0000, or 1.49.0000. (The method to get the 1.49.2000 S-OFF depends on which you have now, IIRC.)
I currently have the 1.47.0000.
kickore said:
I currently have the 1.47.0000.
Click to expand...
Click to collapse
Ok. I am away for the weekend, but will try to get some detailed instructions ASAP. The generalized instructions, though (and it's quite a few steps, sorry to say):
- get a copy of the root PB00IMG.zip file onto the SD card
- get a copy of Flashback (with radio) onto the SD card
- get a copy of ScaryAlien's version of JCase's 1-click root app on the SD card (which I belive you have)
- Nandroid backup when you have now
- start in HBOOT and let the phone run the root PB00IMG.zip (it should detect and ask you to flash it automatically). This gives you 1.49.2000 S-OFF with an old version of the Eris ROM
- * Run the JCase root app (this gets you Amon_RA Recovery back)
- Flash Flashback with radio (this gets you the updated radio back - the root PB00IMG.zip file will flash an older version of the radio)
- Run the JCase root app again to root the phone
- Restart in Recovery and Nandroid Restore GSB
- restart and you'll be back where you were with S-OFF
- (Important) Erase the PB00IMG.zip file from the SD card (or rename it or move it into a folder).
(I may have missed a step - this is off the top of my head. Also, the step with * may be wrong - I think that the root ROM is Android 1.5 and JCase's root app may not run. I don't recall - I'll need to check on that one...)
There is no need! I figured it out from what you said. I'm not really that new at this whole rooting process... But I'm not a programmer and would not have been able to do anything otherwise. I really do appreciate your help.
Thank you so very much!
-Kickore
Edit:
As a suggestion, perhaps making a new guide for anyone who comes to this forum can easily get the files which are now dead links. As well as follow a comprehensive guide on the rooting process.
I have a NOOK tablet 16GB that is somehow locked from modifying partitions
I have tried
the repart image , which has worked many times for me in the past
the AdamOutler Ubuntu Disk
formatting / wiping options in various versions of CWM and TWRP
fastboot erases
fastboot formats
dd'ing /zero to various partitions
parted
sgdisk
a zillion scripts
something at a low level is preventing modifications to the partitions
Im wasting far too much time on this , but I hate being beat (-:
I have a backup of rom and factory , and dd images of stock parttions so I am 100% comfortable with something that
will COMPLETELY ZAP the device
if I boot a known good CM10 image from SD card, it fails to boot , I was assuming if I could get a running android from the card, I'd have access to lots of tools... , but it just fails to tun CM10
any help appreciated.
Thanks
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
sagirfahmid3 said:
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
Click to expand...
Click to collapse
Thanks for responding, Yes, I have tried multiple ways to to zap the table and it doesnt stick.
sgdisk -Z, sgdisk -z parted,
no matter what I do the partitions remain untouched.
I reboot and it still boots into an old stock OS that has a FC shortly after startup, and the internal recovery (factory) , which I can not overwrite, gives the please restart and try again message.
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
mikeataol said:
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
Click to expand...
Click to collapse
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
sagirfahmid3 said:
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
Click to expand...
Click to collapse
Hi, no, I didnt forget to "write" after the "o"
/tmp # ./gdisk /dev/block/mmcblk0
./gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Command (? for help): o
o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
y
Command (? for help): w
w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
/tmp # q
/tmp #
after reboot
Command (? for help): p
p
Disk /dev/block/mmcblk0: 31105024 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): CE21388C-B927-4A5C-91CE-DBD1DE4AB3BC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535678
Partitions will be aligned on 256-sector boundaries
Total free space is 1285 sectors (642.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 256 511 128.0 KiB 8300 xloader
2 512 1023 256.0 KiB 8300 bootloader
3 1024 31743 15.0 MiB 8300 recovery
4 32768 65535 16.0 MiB 8300 boot
5 65536 163839 48.0 MiB 8300 rom
6 163840 262143 48.0 MiB 8300 bootdata
7 262144 1019903 370.0 MiB 8300 factory
8 1019904 2273279 612.0 MiB 8300 system
9 2273280 3145727 426.0 MiB 8300 cache
10 3145728 5242879 1024.0 MiB 8300 media
11 5242880 30535639 12.1 GiB 8300 userdata
Humm...wow, that's pretty crazy. Try writing zeroes to your emmc and then retrying.
# dd if=/dev/zero of=/dev/block/mmcblk0
Hi to everyone.
I make some changes in vold partiitons encryption, but I can't test it on emulator with android 5 because it every time make images again after encryption:
emulator: WARNING: system partition size adjusted to match image file (550 MB > 200 MB)
emulator: WARNING: data partition size adjusted to match image file (550 MB > 200 MB)
Creating filesystem with parameters:
Size: 576716800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7040
Inode size: 256
Journal blocks: 2200
Label:
Blocks: 140800
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35200 inodes and 4536/140800 blocks
With andtoid 4.4 I had no this issue. How can I disable this?
It happend because last android 5 latest kernel broke fs during encryption.
I download android 5 stable repo and it works