.....................
Rootshell file on the cooking 2.1/2.2 thread
Click here for the file.
To flash to 1.6
Go Here
Legen...wait for it...darryy!!
Awesome i saw ur post in the dev thread made my day!
Two questions 1) you mentioned in the dev thread it was restarting quite often is that fixed?
2)is there any means to flash it in internal memory?
muzik_demon said:
Legen...wait for it...darryy!!
Awesome i saw ur post in the dev thread made my day!
Two questions 1) you mentioned in the dev thread it was restarting quite often is that fixed?
2)is there any means to flash it in internal memory?
Click to expand...
Click to collapse
1. Yes, thats fixed, it works fast and stable ! (there's one big problem - sdcard is not properly seen for camera/music), still testing it ..
2. Yes, it will be possible to flash into internal memory later.
1) For the first problem i recommend throwing a pm to zdzihu- he has employed the same technique to get dual boot in x10 and his rom is able to access sdcard for camera/music but we cant mount sdcard
2) If flashing into internal memory is straightforward then i recommend it since it will solve all the above problems
Looking forward to testing
(where can i get x8.img and data.img? or are you gonna release it in some time?)
Well done pulpoff2, I will test this solution, when I gone back home from work. Thanks
thank you . i am downloading the flies .
pulpoff2 said:
So far so good!
I started a new thread cause other one is filled up with junk.
Following my weekend theory, I finally managed to boot 2.1 on X8 with root.
I will post the files shortly.
The process is quite complicated for now, but early testers are welcome.
So, to start u need :
1. Flash 1.6 and root it
2. Copy busybox and rootshell to /system/bin
3. chmod 4755 /system/bin/rootshell
4. copy chargemon.txt into /system/bin/chargemon
5. chmod 777 /system/bin/chargemon
6. copy data.img and x8.img to SDCARD root directory
7. Flash 2.1 KERNEL ONLY (put 2.1 firmware files, remove system.sin and userdata.sin from firmware directory, than flash)
8. reboot your new 2.1 pre-rooted X8 !
Wasted weekend .. was it worth the hassle guys?
Cheers!
Here are the files you need to boot :
pulpX8.rar
ext.rar contains e2fsck to check .img for errors before booting, if you will not install these, booting should work anyway.
P.S. this is a very early stage solution now, wait until I make it clean, or try it if you are a flash maniac
Click to expand...
Click to collapse
how to find rootshell?
isaac12 said:
how to find rootshell?
Click to expand...
Click to collapse
Its on the cooking 2.1/2.2 thread
Click here for the file.
To flash to 1.6
Go Here
thanks... flash only kernel.sin without amss.sin amss_fs.sin cache.sin fota0.sin fota1.sin simlock.ta and update.xml?
isaac12 said:
thanks... flash only kernel.sin without amss.sin amss_fs.sin cache.sin fota0.sin fota1.sin simlock.ta and update.xml?
Click to expand...
Click to collapse
No, do as I wrote in first post, move 2.1 files over 1.6 files, than just remove system and userdata and flash than..
This just keeps getting better and better
Sent from my E15i using XDA App
pulpoff2 said:
No, do as I wrote in first post, move 2.1 files over 1.6 files, than just remove system and userdata and flash than..
Click to expand...
Click to collapse
I'm flashing all files without system and userdata .phone booting only sonyericsson logo. overwrite files and delete user data and system?
pulpoff2 said:
So far so good!
I started a new thread cause other one is filled up with junk.
Following my weekend theory, I finally managed to boot 2.1 on X8 with root.
I will post the files shortly.
The process is quite complicated for now, but early testers are welcome.
So, to start u need :
1. Flash 1.6 and root it
2. Copy busybox and rootshell to /system/bin
3. chmod 4755 /system/bin/rootshell
4. copy chargemon.txt into /system/bin/chargemon
5. chmod 777 /system/bin/chargemon
6. copy data.img and x8.img to SDCARD root directory
7. Flash 2.1 KERNEL ONLY (put 2.1 firmware files, remove system.sin and userdata.sin from firmware directory, than flash)
8. reboot your new 2.1 pre-rooted X8 !
Wasted weekend .. was it worth the hassle guys?
If the answer is yes and you would like me to spend some time and make this perfect, don't forget the "donate" button.
Cheers!
Here are the files you need to boot :
pulpX8.rar
Firmware 2.1 (rus)
Firmware 1.6 (uk)
ext.rar contains e2fsck to check .img for errors before booting, if you will not install these, booting should work anyway.
P.S. this is a very early stage solution now, wait until I make it clean, or try it if you are a flash maniac
UPDATE
The system.img now comes with LauncherPro and other goodies, some vaporware removed and GingerBread (2.3) black theme !!!
Donation count : $0
Click to expand...
Click to collapse
may be superuser.apk put inside of your firmware?
dviktor said:
may be superuser.apk put inside of your firmware?
Click to expand...
Click to collapse
It is inside the x8.img, as well as su and rootshell and busybox.
So if phone gets stuck on boot, connect adb and u can get root in console and fix problems.
and if i am right understand all running files be booted from sd card? and if it's unmount the phone will be still work? or it will be freezing or rebooting? and may be then we can start 2.3 on expiria x8?
dviktor said:
and if i am right understand all running files be booted from sd card? and if it's unmount the phone will be still work? or it will be freezing or rebooting?
Click to expand...
Click to collapse
/system and /data are mounted from x8.img and data.img from Sdcard.
This is good to debug problems, without need to reflash the phone every time.
Once we have the Xrecovery for X8, it will be easy to replace/update files like on X10i.
Without sdcard, you will have 2.1 kernel with 1.6 system, it will get stuck on boot, but adb shell will work (with root!), so you can investigate/fix problems/put new /system files.
pulpoff2 said:
/system and /data are mounted from x8.img and data.img from Sdcard.
This is good to debug problems, without need to reflash the phone every time.
Once we have the Xrecovery for X8, it will be easy to replace/update files like on X10i.
Without sdcard, you will have 2.1 kernel with 1.6 system, it will get stuck on boot, but adb shell will work (with root!), so you can investigate/fix problems/put new /system files.
Click to expand...
Click to collapse
I'm flashing all files without system and userdata .phone booting only sonyericsson logo. overwrite 1.6 files and delete user data and system?. how to long wait for booting phone?
pulpoff2 said:
/system and /data are mounted from x8.img and data.img from Sdcard.
This is good to debug problems, without need to reflash the phone every time.
Once we have the Xrecovery for X8, it will be easy to replace/update files like on X10i.
Without sdcard, you will have 2.1 kernel with 1.6 system, it will get stuck on boot, but adb shell will work (with root!), so you can investigate/fix problems/put new /system files.
Click to expand...
Click to collapse
so, if i take a normal files with undeleted (clean) from system/app, and copy it in phone with root, i can delete x8.img and data.img from sd card? i am just a curator of 4pda (russian) thread by X8 phone. becouse i ask you about everything
Well... I am a new guy, I am happy that the root was released, however, I don't know about the post, so is there a detailed version with pictures please?
Regards
Sent from my E15i using XDA App
how to set chmod in windows vista?
Related
Hey guys so I haven't been following much lately due to exams. But I just found out Recovery was released for X10 and want to install it.
So I just wanted to know how I could safely remove 2.2 from my phone. I remember some guy deleting the folder off his sdcard and wrecking his phone. How do I avoid it?
mackdaddy187 said:
Hey guys so I haven't been following much lately due to exams. But I just found out Recovery was released for X10 and want to install it.
So I just wanted to know how I could safely remove 2.2 from my phone. I remember some guy deleting the folder off his sdcard and wrecking his phone. How do I avoid it?
Click to expand...
Click to collapse
Just do a clean install of whichever ROM you want using flash tool then install recovery mode onto that.
mackdaddy187 said:
Hey guys so I haven't been following much lately due to exams. But I just found out Recovery was released for X10 and want to install it.
So I just wanted to know how I could safely remove 2.2 from my phone. I remember some guy deleting the folder off his sdcard and wrecking his phone. How do I avoid it?
Click to expand...
Click to collapse
what u need to do mate is fairly simple. you need to delete a file and a folder.
boot into 2.1, open root explorer and make sure you are in R/W mode.
delete the chargemon file from /system/bin and delete the /sdcard/freeX10 folder
the freex10 folder contains all the data files for the 2.2 rom
the chargemon file contains the boot hijack that allows you to multi-boot. without this file (if you delete it all together like i am suggesting) the phone will simply boot into 2.1
once you have booted back into 2.1, you can setup the recovery menu
hope that helps mate, and thanks for not posting in the Dev thread!!!
mrtim123 said:
what u need to do mate is fairly simple. you need to delete a file and a folder.
boot into 2.1, open root explorer and make sure you are in R/W mode.
delete the chargemon file from /system/bin and delete the /sdcard/freeX10 folder
the freex10 folder contains all the data files for the 2.2 rom
the chargemon file contains the boot hijack that allows you to multi-boot. without this file (if you delete it all together like i am suggesting) the phone will simply boot into 2.1
once you have booted back into 2.1, you can setup the recovery menu
hope that helps mate, and thanks for not posting in the Dev thread!!!
Click to expand...
Click to collapse
Thank you so much, that worked like a charm.
Also LOL @ the dev thread comment. I am not really that retardo.
Hey guys,
I accidently removed the framework-res.apk from /system/framework
Off course the phone isn't booting anymore, is there any way to push back the file or get the phone working again?
Rooted with z4root, but adb shell isn't working anymore to mount /system r+w :/
Fast help is really appreciated...
Unless you've got xRecovery installed you'll have to reflash, there is a way to save data but I don't recall it.
I remember someone mentioned either in the Flash tool thread or the AOSP Thread that you can use the Flash Tool to flash only the system.sin this way you won't loose your apps/data... But you'll reinstall the whole system back. I've never try this but you should try if this doesn't work you'll have to reflash anyway...
Just put in the "firmware" folder the system.sin file and delete everything else, run the flash tool and follow instructions....
Jim
Thanks for the help! Got everything working again
Just replaced the system.sin and loader.sin - all my data still remains!
BlackTigerX said:
Thanks for the help! Got everything working again
Just replaced the system.sin and loader.sin - all my data still remains!
Click to expand...
Click to collapse
I'm glad to help however you'll have to re root/ enable JIT etc... again since you've replaced the system with a fresh install
Sent from my X10i
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
racht said:
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
Click to expand...
Click to collapse
yess, thank you! now i found a mkfs.yaffs2 for arm processors for android. it's verry slow.
so i made my sdcard to ext2, and now i try to "extract" my img.
so ... It's used to ?
trapacska said:
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
Click to expand...
Click to collapse
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
propc said:
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
Click to expand...
Click to collapse
it's cool! thank you. now i try to debrand the oroginal x8 rom.
trapacska said:
it's cool! thank you. now i try to debrand the oroginal x8 rom.
Click to expand...
Click to collapse
you know what. i've found a better method to change permissions
1-mount original system.img
Code:
mkdir tmp/1
sudo mount -o loop /your/system.img/path /tmp/1
2-clone permissions from original system.img to your system folder
Code:
chmod -R --reference /tmp/1 /your/new/system/path
and the permission fix done!
EDIT: tested. and worked. I've finally created my own modified ROM (running on sdcard)
EDIT2: some problem with root permissions, will work on it
thank you i found a way to fix permissions too:
1. unyaffs original system.img
2. in busybox shell mount it to r/w
3. copy xrecovery and su and superuser to fresh rom.
(for me it works well without xrecovery fix permissions)
if there is some error, you can fix it with xrecovery
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
bnight said:
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
Click to expand...
Click to collapse
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
propc said:
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
Click to expand...
Click to collapse
/system/framework (for a skin)((but the all folder))
trapacska said:
/system/framework (for a skin)((but the all folder))
Click to expand...
Click to collapse
thanks. will try porting from htc legend 2.2 rom later.
I've been looking at a lot of tuts and stuff for making a ROM, because getting system.img from the official ROM is a bit tedious
First reinstall a Android 2.1.
Then root it.
Install a XRecovery.
Then backup it.
Now you will get system.img in backup folder.
Click to expand...
Click to collapse
quote from: http://forum.xda-developers.com/showthread.php?t=888227
I Rooted with SuperOneClick v1.65, then stuck on xRecovery using the adb shell to mount the system folder as r/w, then copying the files from sdcard to system/bin. This way i didn't have to install RootExplorer and put in my google account details
then, i just backed up and here it is:
http://www.mediafire.com/file/xb64e5mp6q6fmdb/StockBaseROM.zip
Zip contains:
- cache.img
- data.img
- nandroid.md5
- system.img
Now all you need to do is set up a kitchen
i'm following this tut to make a ROM(probably with none of my own creations (will credit those who need it) but with stuff like JIT and Wireless N enabled etc. oh and ofc it'll look pretty )which i'll share when i've completed
crap, though you meant you ported 2.1 AOSP
Mikevhl said:
crap, though you meant you ported 2.1 AOSP
Click to expand...
Click to collapse
nah nah, i'm no dev, just a learner. haah
I Highly suggest you follow the steps in this post first (http://forum.xda-developers.com/showthread.php?t=920347)
Froyo is completely stable and will give you a back up OS in case anything happens or you want to do something that doesn't work in HC.
Steps:
If anyone knows how to shrink a partition using parted please let me know. This would eliminate steps 2 & 3
QUICK EDIT WARNING: PLEASE READ: THIS IS BASED ON THE DUAL BOOT FROM ROOKIE1. FROM WHAT I KNOW THIS DOES NOT WORK ON 1.1.0 ONLY 1.0.1
(Note: Requires adb)
1 ) Have a working honeycomb v02 sd card (v03 has a custom kernel which causes rotation issues on the eMMC).
2) Install EASEUS (Windows) or gParted (Linux)
(if you need help with this just PM me)
3) Shrink the second partition of the SD card to 400mb
4) Download and extract my zip to your android/platform-tools folder
5) Run Internal.bat
Make sure not to format your sdcard from your nook while using this.
< standard disclaimer - I'm not responsible for whatever damage you did to your NC >
Also, the reason I did not post a clockwork zip or a dd img for system is I'm unsure of the legality of it, if someone else would like to then by all means do so.
PM me for any questions, and I would like to say thanks to samuelhalff, as without his help I never would've gotten it running from internal memory
Also, please make sure you know how to recover your nook color back to stock. Not only if something goes wrong, but since honeycomb isn't fully working yet.
That being said, if you run the dual-boot script first from rookie1 you'll always be able to fall back onto froyo to fix any issues.
----------------------------------------------------------------------------
How this works:
It copies the system partition from honeycomb onto the internal memory.
It then pushes my boot.img to your sd card.
Finally it overwrites your boot.img with mine
(My boot.img contains everything from rookie1's dual boot alongside the needed jar files included on honeycombs boot.img)
Download link:
http://www.multiupload.com/0TTH2OJS3C
Uploading fixed version now
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And for those who like doing everything manually. Here is Sam's modified uRamdisk. Make sure its on the bootpartiton alongside the jar files included in deeper-blue's release
Ramdisk: http://www.multiupload.com/90H38OX0S9
Also, the first time it starts up may take a few min. So be patient before trying to restart it
Thanks this will be very useful for myself and others. I'll report back with any issues.
Why must my laptop break today of all days?
Sent from my SPH-D700 using XDA App
marcusant said:
Why must my laptop break today of all days?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sorry to hear that. I would say you could do it without one but you need the modified ramdisk inside my boot.img
Hey maybe i'm doing something wrong but i keep getting this error message:
rm failed for *, no such file or directory
i am not an expert on adb so this may be my fault, just reporting feedback for you.
tgallant21 said:
Hey maybe i'm doing something wrong but i keep getting this error message:
rm failed for *, no such file or directory
i am not an expert on adb so this may be my fault, just reporting feedback for you.
Click to expand...
Click to collapse
its not rm * its "rm * -r" as that is the recursive switch...
MattJ951 said:
I Highly suggest you follow the steps in this post first (http://forum.xda-developers.com/showthread.php?t=920347)
Froyo is completely stable and will give you a back up OS in case anything happens or you want to do something that doesn't work in HC.
Steps:
QUICK EDIT WARNING: PLEASE READ: THIS IS BASED ON THE DUAL BOOT FROM ROOKIE1. FROM WHAT I KNOW THIS DOES NOT WORK ON 1.1.0 ONLY 1.0.1
(Note: Requires adb)
1 ) Have a working honeycomb v02 sd card (v03 has a custom kernel which causes rotation issues on the eMMC).
2) Download and extract my zip to your android/platform-tools folder
3) Run Internal.bat
Make sure not to format your sdcard while using this.
Note: I'm not sure if you need to clear your data partition or not. I did, but it may not be required.
the steps under froyo would be : something similar to this (I dd'd HC data partition to the internal, so i'm not 100% sure of this)
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk1 /
mkdir data_temp
mount /dev/block/mmcblk0p6 data_temp
cd /data_temp [B]MAKE SURE THIS COMMAND WORKS BEFORE CONTINUING[/B]
rm * -rf
exit
< standard disclaimer - I'm not responsible for whatever damage you did to your NC >
Also, the reason I did not post a clockwork zip or a dd img for system is I'm unsure of the legality of it, if someone else would like to then by all means do so.
PM me for any questions, and I would like to say thanks to samuelhalff, as without his help I never would've gotten it running from internal memory
Also, please make sure you know how to recover your nook color back to stock. Not only if something goes wrong, but since honeycomb isn't fully working yet.
That being said, if you run the dual-boot script first from rookie1 you'll always be able to fall back onto froyo to fix any issues.
----------------------------------------------------------------------------
How this works:
It copies the system partition from honeycomb onto the internal memory.
It then pushes my boot.img to your sd card.
Finally it overwrites your boot.img with mine
(My boot.img contains everything from rookie1's dual boot alongside the needed jar files included on honeycombs boot.img)
Click to expand...
Click to collapse
You have verified this working with your boot.img? Mine gets hampered during the boot and locks up... I had the same issue when I was building my ramdisk for this purpose.... I am going to continue to look into this and will post anything I find.
Cheers!
A quick question:
You say not to format the SDCard while using this. Does this mean that there are still some system files on the SDCard after the procedure is done or can I format my card as FAT32 once the whole operation is done?
Ooglez said:
A quick question:
You say not to format the SDCard while using this. Does this mean that there are still some system files on the SDCard after the procedure is done or can I format my card as FAT32 once the whole operation is done?
Click to expand...
Click to collapse
I believe I may have included an incorrect boot.img in my original upload, im reuploading it now.
As for formatting the sd card, i'll clairfy that in the OP. Don't format the sd card from inside the nook. formatting it inside a computer is fine.
MattJ951 said:
How this works:
It copies the system partition from honeycomb onto the internal memory.
It then pushes my boot.img to your sd card.
Finally it overwrites your boot.img with mine
(My boot.img contains everything from rookie1's dual boot <B>alongside the needed jar files included on honeycombs boot.img)</B>
Click to expand...
Click to collapse
I think I see the issue, your dd image is lacking those jar files... I am going to try and add those files to my boot partition and go from there.... Disregard! per the post above this one.......
modembug said:
I think I see the issue, your dd image is lacking those jar files... I am going to try and add those files to my boot partition and go from there.... Disregard! per the post above this one.......
Click to expand...
Click to collapse
The boot.img must be from another project I was working on. It's using the wrong u-boot.bin and is missing the jar files. Updating main post in 20 seconds once it finishes uploading
And its up.
http://www.multiupload.com/KPDAPGYXSI
Also thanks for the feedback.
MattJ951 said:
The boot.img must be from another project I was working on. It's using the wrong u-boot.bin and is missing the jar files. Updating main post in 20 seconds once it finishes uploading
And its up.
http://www.multiupload.com/KPDAPGYXSI
Click to expand...
Click to collapse
Thanks for updating so quickly. I've been waiting to run Honeycomb off of EMMC. I'll let you know how it goes.
MattJ951 said:
The boot.img must be from another project I was working on. It's using the wrong u-boot.bin and is missing the jar files. Updating main post in 20 seconds once it finishes uploading
And its up.
http://www.multiupload.com/KPDAPGYXSI
Also thanks for the feedback.
Click to expand...
Click to collapse
I am getting ready to dd that image over as we speak, i will report back shortly...
No problem, let me know if it works and if it doesn't ill try updating it again. (I personally have it working but I didn't use a script, i entered the commands manually. Also make sure youre using v02 [though note: HC runs faster for some reason if you copy the data partition from v03 and dd it to the internal while running v02's system. v03 has problems with the kernel due to the 90degrees thing deeper added]
MattJ951 said:
No problem, let me know if it works and if it doesn't ill try updating it again. (I personally have it working but I didn't use a script, i entered the commands manually. Also make sure youre using v02 [though note: HC runs faster for some reason if you copy the data partition from v03 and dd it to the internal while running v02's system. v03 has problems with the kernel due to the 90degrees thing deeper added]
Click to expand...
Click to collapse
I am having issues with it locking up on "Android _ " could be due to crap on the data partition from the last boot.img... cleaning it off and trying again. Yeah I took a look at your bat file and just ran things manually... i have issues with unknown bat/sh files lol
UPDATE: okay, so its still locking up... did you dd the data partition or any of that stuff over as well? as of right now, i am running your boot.img and i DD'd the system partition from a working HC-SD, and i removed all files from the internal /data partition....
modembug said:
I am having issues with it locking up on "Android _ " could be due to crap on the data partition from the last boot.img... cleaning it off and trying again. Yeah I took a look at your bat file and just ran things manually... i have issues with unknown bat/sh files lol
Click to expand...
Click to collapse
Let me know if it works. The "Android _" screen originally locked up for me because of the uRamdisk. I'll upload the one Sam sent me which is included in the boot.img but maybe is causing problems for you.
The modified uRamdisk is now in the OP.
Nada, still no dice.... I have all the folders from HC /Boot with your boot files replacing uboot, uramdisk etc.. Still running into the same issue, might need to work busybox into this thing to see what is going on...
UPDATE: going to try dd'ing the /data part over to emmc /data..
modembug said:
Nada, still no dice.... I have all the folders from HC /Boot with your boot files replacing uboot, uramdisk etc.. Still running into the same issue, might need to work busybox into this thing to see what is going on...
UPDATE: going to try dd'ing the /data part over to emmc /data..
Click to expand...
Click to collapse
Thats not the problem. I realized my mistake.
where i wrote
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p1
it should be
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p2
if you run that it should boot correctly.
uploading a fixed version to the OP now
MattJ951 said:
Thats not the problem. I realized my mistake.
where i wrote
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p1
it should be
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p2
if you run that it should boot correctly.
uploading a fixed version to the OP now
Click to expand...
Click to collapse
which is why i run commands manually ;-) yeah I double check prior to DD and i have pushed the correct partition to /system... i have now pushed /data over and still no love... Can you dd your /boot and post it?
modembug said:
which is why i run commands manually ;-) yeah I double check prior to DD and i have pushed the correct partition to /system... i have now pushed /data over and still no love... Can you dd your /boot and post it?
Click to expand...
Click to collapse
That actually is my current /boot inside the 7z. Also i can't think of a reason why it wouldn't work.
I'll format my NookColor and try it to see if I can figure out whats going wrong.