Urgent ..... i cant restore my NST :( - Nook Touch General

guys , iam very shocked
i have make and image from boot partion when i boot with noogie and i was about 289 MB , but when i root my device and minimaltouch and i set some mistake in steps then i decide to backup my device again , when i download partiotion wizard and delete all 7 partition and when i write my image to my device when i had boot up with noogie image ..... when i try use my nook ... it's just say start up ur nook then stopped to load
any urgently help :crying:

Sorry, I have no experience with any of these automatic tools.
Generally speaking, it's a bad idea to delete partitions.
Yes, I know that's a bit late to say now.
I'd really like to know why so many people have problems with these things.

when i write the image to my nook device , it's appear that there's 5 partions not 7 partions , may that the reason , i can upload my image if anybody can help with that
i just need any solution to run back my nook again

Don't you have an old full backup with a size of about 2 GB?
If you have that, writing it will restore all your partitions.
The standard Nook factory recovery does not do partitioning.
It requires that the partitions be set up and working already.

ok , let me tell u how i make backup
first i do noogie image on my memory (2GB) and then boot with it and my nst screen say rooted for ever when i connect my device to pc then there's a partition named (boot) and other partition cant be opened..... then i used diskimage and take image from the memory it self (partition named boot) then i saved to my pc and compress it and was about 300MB
when i root my device with minimaltouch and crashed with me , then i deceide to use my recovery , then i boot my nook with noogie image and then open partitioning program then i found 7 partions in my nook , then i del them all ( i didnt format but after many times i failed to make recover then i make format with fat32) and then used diskimage to write the image to sd disk and there's another disk cant bemount ...... when i run my nook , it's just stop at screen "your nook device start up" ..... then i tried many times , no hope , so ....... what the mistake i do
and when i write the image , i checked my device partitions , it's just 5 (4 partitioned and the 5th one unallocated .... )
when i back to home ..... i post an image about my partitions after do image and if u want check my image , i can upload it
and for check how u make back/restore NST , check this
http://forum.xda-developers.com/showthread.php?t=1142983
i hope anyone provide me any info/help
thx to Renate for supporting me

When you are using Noogie and a Windows desktop, only the first (boot) partition will be visible.
You will get a drive letter for it.
If you go to disk management in Windows, you will see that there are 7 partitions, although only the first has a letter.
I would have suggested that you use Win32DiskImager.
It will take a drive letter but save the entire physical device, including all 7 partitions.
You will end up with a file on your desktop of 2 GB.
I'm not sure whether your 300 MB is a full backup or not.

there's some pic of my device after every time i write backup image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
there's another pic from original backup i must have when i do write image
so , i need nook , cache and userdata partions
if they comment in all nook devices , so anybody can write this image that i have to flash and add this partitions from another original nook and save back up .....is this will work or anyone get what i mean???
anybody can do it , or can help me and need my back up , i can upload it for him
thx at advanced

I'm getting really confused what is going.
I have no idea what you have for backups.
Do you have anywhere a file like something.img with a size of 1,9XX,XXX,XXX?

speedman2202 said:
there's some pic of my device after every time i write backup image
Click to expand...
Click to collapse
The good thing - you have you factory partition, so you can restore generic image, then roll your unique settings.
I'm not giving you any details - you need to do lot's of reading yourself.

Renate NST said:
I'm getting really confused what is going.
I have no idea what you have for backups.
Do you have anywhere a file like something.img with a size of 1,9XX,XXX,XXX?
Click to expand...
Click to collapse
Renate , i told u in the previous post how i i make recovery ,and the image i take was about 300MB only , not 2 GB as u say ...... i just provide u an pic of my nook partition after i write my backup image ( the first pic) and i provide u the partitions i must have when i write the image on my nook , i just show the deference between my nook partitions and normal nook partitions .... i only missed 3 partitions ( nook , cache and userdata partitions) beside my other 5 partitions then i guess my nook work again
did u get what i mean?????
ApokrifX said:
The good thing - you have you factory partition, so you can restore generic image, then roll your unique settings.
I'm not giving you any details - you need to do lot's of reading yourself.
Click to expand...
Click to collapse
i have think about that , that the first 2 partitions (boot , factory) is very important to my nook device and have all unique info , so can u help me or provide me a full recovery image with my unique info that i can run back my nook??
also if u provide me any links or thread i will be thankful to u
ty all

I wasn't clear from that 2nd image whether you had such a backup.
You have to recreate the partitions.
The easy way would be to restore a full physical backup.
The other way is to manually recreate the partitions.
Your boot is bombing because there is no data or cache partition.
They don't need anything in them, but they have to exist.
Maybe somebody can tell you an easy way to recreate them.
On my Nook, the partitions are as follows:
Code:
[b]Partition Type Start End Size (bytes) Mount[/b]
--------- ---- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 1 38 79,691,776 /boot
mmcblk0p2 vfat 39 46 16,777,216 /rom
mmcblk0p3 ext2 47 141 199,229,440 /factory
mmcblk0p4 142 926 1,646,264,320
mmcblk0p5 ext2 142 285 301,989,888 /system
mmcblk0p6 vfat 286 405 251,658,240 /media
mmcblk0p7 ext3 406 525 251,658,240 /cache
mmcblk0p8 ext3 526 926 840,957,952 /data
Unused 927 933 14,680,064

Based on what you're showing in the restore, you have a good shot at recovering. You have a partition called /factory, and there are files in it.
What happens if you let it fail to boot 8 times (ie, power it on, let it 'get stuck,' power it off, power it back on again) ?
I don't know if the recovery scripts can get your extended partition and its sub-partitions working for you again or not. If they can, that's the way to get them to do it.
If not, you will need to learn the tools for doing it. I would recommend either setting up vmware player and linux in that, or finding a USB-bootable linux distribution, booting from that and then using it to work on fixing that extended partition.
In either case, you will need to boot from Noogie so that you can use fdisk or gparted to create the remaining partitions you need. Hopefully, the recovery file available in the partial restore you've done has the ability to do that for you, though I don't know if it does.

speedman2202 said:
i have think about that , that the first 2 partitions (boot , factory) is very important to my nook device and have all unique info , so can u help me or provide me a full recovery image with my unique info that i can run back my nook??
also if u provide me any links or thread i will be thankful to u
Click to expand...
Click to collapse
I haven’t been through full restore from generic image fortunately (for me!).
I can neither give you detailed instruction and nor help if something goes wrong.
I don’t even know if we have the detailed instruction on how to restore from generic image and roll in unique factory setting (in one place)
But I’m sure forums have all those questions answered.
Search is you friend.

i am think about if i got an nook backup and modified the factory partions that i replaced all files , then i burn it
i guess my nook will run back?
how u think about it guys

speedman2202 said:
i am think about if i got an nook backup and modified the factory partions that i replaced all files , then i burn it
i guess my nook will run back?
how u think about it guys
Click to expand...
Click to collapse
Yep. That's exactly how is should work.
Once you restore it, don't forget to write step-by-step instructions for others

the main problem , from where i can get an original backup nook device that i will work on???
anyone have an backup for it's nook (before he start use it or even root is preferred) and upload for me , i will be thankful for him
anyway i have another question to u Renate
u say cache and userdata partitions they must be exist but they r empty , how about the nook partitions???
i guess it's have the file system , it's it????

I've been waiting for somebody to jump in and tell you how you can partition your Nook's internal card.
If you have a Linux desktop system you can boot with Nookie and partition it, I believe.
ClockworkMod can't partition the internal card.
You need all seven partitions set up in the right order.

speedman2202 said:
the main problem , from where i can get an original backup nook device that i will work on???
anyone have an backup for it's nook (before he start use it or even root is preferred) and upload for me , i will be thankful for him
Click to expand...
Click to collapse
"original backup nook" was posted somewhere on this forum, I just can't formulate search string to find it.
I guess, I'm trying hard enough.
Try instruction from this post.
http://forum.xda-developers.com/showpost.php?p=27893293
And read whole thread as well
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
Renate NST said:
I've been waiting for somebody to jump in and tell you how you can partition your Nook's internal card.
If you have a Linux desktop system you can boot with Nookie and partition it, I believe.
ClockworkMod can't partition the internal card.
You need all seven partitions set up in the right order.
Click to expand...
Click to collapse
If you like GUI, you can use "parted".

i am ask about if anyone have unrooted nook and take an backup of it's device ..... can he upload it for me that i can edit it that i use for my own nook?

UP

Related

[ANSWER] Safe Partitioning - How to confirm?

As we all know, most of our phones have at least a couple of bad blocks in the NAND memory. The biggest and most common problem because of this is that when you create a partition of 'x'MB, the actual partition will be 'x-something'MB. This is because partitioning does not account for bad blocks.
So if a ROM requires 150MB of /system partition (which you create - using HD2 Toolkit or cLK 1.5), you *might* end up with less than 150MB. ROM devs usually factor this in and give a room of at least 5 ~10 MB for installing additional stuff in /system as well as bad blocks. But you will have a problem if the 150 MB partition you create has enough bad blocks making it less than, in my example, 145 or 140 MB.
The most safest way I have seen to make sure you /system has enough space-
Extract you ROM's zip file, and check the size of the directory named system
Repartition your phone like you normally do
Boot to ClockWorkMod and format all partitions
Mount the /system partition in ClockWorkMod
Connect your phone to your computer, ensure you had ABD drivers installed
Head to QtADB and download the most appropriate version for you - there is one for Linux x86, Linux x64, Windows and Mac. Also download the required binary files for Linux, Windows or MacOS. Extract all QtADB zip as well as the binary zip to the same directory. Launch QtADB. On first launch, if it asks for the binaries, point it to the right directory
In QtADB, select the "Phone Info" icon. You will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see from the image, my /system is 195.31 MB. I had partitioned my NAND for 200 MB system partition, but am losing 4.69MB to bad blocks
If I am installing a ROM, I need to make sure the system directory in its zip file does not exceed this size, or increase the partition size accordingly.
Also, when flashing a ROM, you can refresh QtADB to see the /system partitioning filling up. Make sure the actual space in the system partition is 10 or 15 MB larger than the ROM's system directory. The most common symptom of an inadequate system partition is bootlooping, and other weird/ uncommon behavior.
Hope this little guide helps at least some of us. Happy Flashing
ph03n!x said:
As we all know, most of our phones have at least a couple of bad blocks in the NAND memory. The biggest and most common problem because of this is that when you create a partition of 'x'MB, the actual partition will be 'x-something'MB. This is because partitioning does not account for bad blocks.
So if a ROM requires 150MB of /system partition (which you create - using HD2 Toolkit or cLK 1.5), you *might* end up with less than 150MB. ROM devs usually factor this in and give a room of at least 5 ~10 MB for installing additional stuff in /system as well as bad blocks. But you will have a problem if the 150 MB partition you create has enough bad blocks making it less than, in my example, 145 or 140 MB.
The most safest way I have seen to make sure you /system has enough space-
Extract you ROM's zip file, and check the size of the directory named system
Repartition your phone like you normally do
Boot to ClockWorkMod and format all partitions
Mount the /system partition in ClockWorkMod
Connect your phone to your computer, ensure you had ABD drivers installed
Head to QtADB and download the most appropriate version for you - there is one for Linux x86, Linux x64, Windows and Mac. Also download the required binary files for Linux, Windows or MacOS. Extract all QtADB zip as well as the binary zip to the same directory. Launch QtADB. On first launch, if it asks for the binaries, point it to the right directory
In QtADB, select the "Phone Info" icon. You will see something like this:
View attachment 1081288
As you can see from the image, my /system is 195.31 MB. I had partitioned my NAND for 200 MB system partition, but am losing 4.69MB to bad blocks
If I am installing a ROM, I need to make sure the system directory in its zip file does not exceed this size, or increase the partition size accordingly.
Also, when flashing a ROM, you can refresh QtADB to see the /system partitioning filling up. Make sure the actual space in the system partition is 10 or 15 MB larger than the ROM's system directory. The most common symptom of an inadequate system partition is bootlooping, and other weird/ uncommon behavior.
Hope this little guide helps at least some of us. Happy Flashing
Click to expand...
Click to collapse
Thanks for this, I've been looking for a way to check something like this out. I don't have the time now though, but I might try it later depending again on time constraints. I feel that for now I'm OK since I've only had the phone since Jan 2011 and I used SD Android for quite a while before switching to NAND, but it never hurts to know things like this. Thus far though the recommended partition size has always worked for me and I've always seen 2-3Mb space free in the 'System ROM' setting in Titanium backup.
In fact, that gets me wondering can you literally just do step 1, then flash a partition size larger than needed (e.g. for a 150Mb ROM flash a 200Mb partition), calculate how much space you should have free (i.e. 50Mb in this case), check in Titanium Backup how much space you actually have free and subtract the latter from the first, giving you the free space? If this would work, it would save even more time.
Of course, I may be COMPLETELY misunderstanding what the 'System ROM' thing in Titanium Backup is, tbh I'm not into the technical side of things very much.
@Nigeldg- Titanium Backup is something I used to check the sizes earlier. But then, it's not quite accurate. My 200MB /system partition shows as 209MB in Titanium
I have never had any issues in using a bigger partition than required. I initially had a 445 MB as default when I was trying out a bunch of ROMs...
Swyped from my HTC HD2 (ICS 4.0.4)
ph03n!x said:
@Nigeldg- Titanium Backup is something I used to check the sizes earlier. But then, it's not quite accurate. My 200MB /system partition shows as 209MB in Titanium
I have never had any issues in using a bigger partition than required. I initially had a 445 MB as default when I was trying out a bunch of ROMs...
Swyped from my HTC HD2 (ICS 4.0.4)
Click to expand...
Click to collapse
Actually I see you're right, my 165mb partition reads as 173mb. Still, perhaps it's consistently 8-9mb over? Just a guess, although I would obviously need someone with a different partition size to confirm this
Nigeldg said:
Actually I see you're right, my 165mb partition reads as 173mb. Still, perhaps it's consistently 8-9mb over? Just a guess, although I would obviously need someone with a different partition size to confirm this
Click to expand...
Click to collapse
For a raw sizing, open terminal emulator (or ADB shell) and type df
Again, this wont count the bad blocks you have...
when you wantto flash a new rom, first resize the system partition with more 10M than the new rom needed... it is a simple method to solve the problem...
Good find ph03n!x !!! I just use root explorer to determine my partition sizes. Lucky, ive only had bad blocks in my userdata partition. (Knocks on wood) Hopefully i wont have anymore
ph03n!x said:
@Nigeldg- Titanium Backup is something I used to check the sizes earlier. But then, it's not quite accurate. My 200MB /system partition shows as 209MB in Titanium
I have never had any issues in using a bigger partition than required. I initially had a 445 MB as default when I was trying out a bunch of ROMs...
Swyped from my HTC HD2 (ICS 4.0.4)
Click to expand...
Click to collapse
I know this thread is a bit old now and generally I don't bring up an old thread again, but in Tytungs CM9 there was a short discussion about this and I was given a solution by agbommarito:
agbommarito said:
Titanium Backup has an option under GUI Preferences to change its interpretation of memory. If it is set for binary units, a kilobyte = 1024 bytes and Titanium will display MiB. If it is set for decimal units, a kilobyte is 1000 bytes and Titanium will display MB (without the little "i').
165 MiB (where a MiB is 1024x1024) = 173 MB (where a MB is 1000x1000).
Click to expand...
Click to collapse
So if anyone wanted to check their partition size, they CAN just use Titanium to do it
@nigeldg, I tried that and am getting 200MB, which is indeed my partition size- but it is not accounting for the bad block I have in my /system!
_
Swyped from my HTC HD2 (ICS 4.0.4)
ph03n!x said:
@nigeldg, I tried that and am getting 200MB, which is indeed my partition size- but it is not accounting for the bad block I have in my /system!
_
Swyped from my HTC HD2 (ICS 4.0.4)
Click to expand...
Click to collapse
Alright I get it now. Perhaps flashing a larger partition size, then seeing how much free space you should have in /system versus seeing how much space you actually have in /system would do the trick (basically a combination of the first thing I suggested a while back and the new solution as well). Of course, this wouldn't tell you how many bad blocks you have but the amount of space which is taken up should be sufficient data. Again, I'm not sure whether or not this would work but in theory I think it should.
Well, my point is to check the partition size before flashing a ROM, making sure the actual size on /system is sufficient- by checking the size of the system directory in the ROM's zip
_
Swyped from my HTC HD2 (ICS 4.0.4)

Using 16GB card for streak 5 internal SD

Hmm... this is quite interesting which i taught i want to show you guys this... screenshots taken from my streak 5 of course
When you guys see the red arrow pointing to what... you guys will know what i mean :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-----------------------------------------------------------
UPDATE:
While i was playing around today, i managed to get it like in the image below. See where the red arrow pointing at? Neat isnt it?
-----------------------------------------------------------
p/s: Using 16GB Kingmax class 10 microSDHC for internal and external sd
Now you guys are curious how i managed to do that?
FIRST OF ALL:
You need to open the streak housing ... follow the link below and good luck.. be gentle and be careful .. just do it slow and steady and you will be ok ... no need to rush anything there ... :good:
http://www.ifixit.com/Teardown/Dell-Streak-Teardown/3512/1
------------------------------------------------------
NEXT - SELECT APPROPRIATE USER TYPE:-
LINUX USERS:
Just follow this link > http://forum.xda-developers.com/showpost.php?p=24799755&postcount=65
WINDOWS USERS:
first.. get this... http://www.alexpage.de/usb-image-tool/
make sure it is USB Image Tool 1.59 when you download...
next get gparted-live-0.13.1-2.iso
burn it to the CD...
- after you have extracted the usb image tool... open USB Image Tool.exe
- select the corresponding usb drive and click backup, save it something like streakinternal.img
- it will take some time to complete ( have instant noodle for the time being )
- once done... replace the sd card that you want to transfer the image to and click restore and select the earlier streakinternal.img
- again.. it will take some time to complete (you can have snack this time )
note: make sure the target sdcard is the same or bigger in size (obviously)...
- once completed...
- reboot your pc and insert the burned CD earlier... let it boot from it... just press enter to everything it ask until it fully loaded into linux environment
- gparted should already show your sdcard drive there... it should show /dev/sda1 and below it got two more partition /dev/sda5 (ext3) and /dev/sda6 (ext3)
- select /dev/sda1 and right click it and select move/resize
- there should be visual displaying the drive structure and on the right, there should be arrow, drag it to the most right, click ok
- now, select /dev/sda6 and right click it and select move/resize
- again, on it, there should be arrow on the right, drag it to the most right and click ok
- once all that done, click apply and it will start to do its work..
- let it completes it work and your sd card now should be able to be use as internal sd...
- your streak should be able to boot straight away.. no need to wipe cache or something like that...
- have fun having big internal sd
p/s: i wrote this based on my memory, i hope i dont messed it up
------------------------------------------------------
POSSIBLE FAQ:
-- 01 --
Q - Will the method used gone if i do factory reset?
A - Nope. You can safely do it and the structure will be maintained.
-- 02 --
Q - Can i use more than 16gb card?
A - Theoretically, yes.
-- 03 --
Q - Can we use this as sd storage as well?
A - Sorry. We cant because it is formated in ext3, so windows see it as unformatted medium.
-- 04 --
Q - Cant we create shortcut in external sd to access it?
A - Sorry. We cant because symlink does not work on any windows formatted medium since external sd usually formatted in fat32
-- 05 --
Q - Cant we mount this at all?
A - Somebody has tried it before but since the internal sd never meant to be accessed externally, the support is pretty much impossible.
-- 06 --
Q - How can we access it and where is it located?
A - To access the space, you can use root explorer and wifi file explorer (anything similar will do) and it is located at /data from /
Therefore, you must be rooted to access it.
-- 07 --
Q - So, what the hell am i supposed to do with those huge extra GBs?
A - Well, you can brag bout it to your friends, saying it got this huge internal sd space and can install hundreds of applications or games and still got space left for more.
------------------------------------------------------
MORE ADVANCED MODS.:
If you think having large innerSD is not enough, we could have larger /system dir and possible dual usb mount support by default (in the near future hopefully) for our streak 5.
Have a visit to the link below...
http://forum.xda-developers.com/showpost.php?p=31643924&postcount=98
-------------------------------------------------------
Our streak 5 might be old but it is still competitive regardless
.
Did u change internal storage?we can use that as sd storage or not?
Sent from my Dell Streak using Tapatalk 2
Which SD card is this? I mean make and class...
Sent from my Dell Streak using xda premium
details please..!!!
BEEN TRYING WITH 16GB CARD...REIMAGED THE CARD WITH EXT3 AND ALL BUT IT WOULD NOT ACCEPT 16GB CARD......PLEASE GIVE US MORE DETAIL ON HOW TOs....THANKS IN ADVANCED..
He just installed a 16gb card and formatted it properly.
You must use extended partitions and not primary ones, at least that's what the stock card is set up as
TheManii said:
He just installed a 16gb card and formatted it properly.
You must use extended partitions and not primary ones, at least that's what the stock card is set up as
Click to expand...
Click to collapse
Does the benefit come from the class of the sd card or the size? or is it the format (ext3vs4 or some such thing)?
ellisna said:
Does the benefit come from the class of the sd card or the size?
Click to expand...
Click to collapse
class for sd card means speed... so the higher the better..
Speed class determines it's actual read and write speed, FS is important as ext4 is the most efficient fs currently available.
It's supposed to be a good deal faster then yaffs2 and more efficient then ext3
TheManii said:
Speed class determines it's actual read and write speed, FS is important as ext4 is the most efficient fs currently available.
It's supposed to be a good deal faster then yaffs2 and more efficient then ext3
Click to expand...
Click to collapse
i go on and make it ext4 both for cache and data for the internal sd.. boots up normally and yes... you can see something faster...
its a shame that the CWM 6 not supported ext4 and therefore nandroid backup is impossible for now...
i also tried and make both internal and external sd not in the slot... and see if streak manages to boot up or not.. well... it stuck at dell logo.. lol
so internal sd is a must so that phone can boot due to the needs of use cache and data dir...
I can easily make a build that supports it, it's just that the rom must also support it.
The rom could likely be modified to mount /firstboot as /data, but there's not enough partitions to also have /cache on the nand.
TheManii said:
I can easily make a build that supports it, it's just that the rom must also support it.
The rom could likely be modified to mount /firstboot as /data, but there's not enough partitions to also have /cache on the nand.
Click to expand...
Click to collapse
i see...
well i am using longhorn 2.9.3...
CWM 6 cant read ext4 because how the script work? i really thought it could since it is newer and i know streakmod had issues with ext4...
but when i am thinking back.. it seems it have same baseworks...
It's turned off on the normal S5 build as ext4 requires additional modules, as it normally doesnt use ext4 I simply built it with them off.
I dont recall of CWM 1.8/2.5 (which streakmod is based off of) even supports ext4, the earliest one I can confirm it does is 4.0 as that was the 1st version built against the stock GB recovery. GB was the 1st rom that uses ext4 by default (on devices that launched with GB or newer)
Themanni.
Can we have a third partition on the inner sdcard??? To use as external storage. If so can you help/guide how to!
Sent from my ST25i using xda premium
I havnt actually tried it (but I plan to some day in the future): just manually make the partitions and add an extra one onto the end for /system.
At that point: unless you follow a standardized layout, you're going to need to manually build CWM as CWM needs to know ahead of time the layout and size of the partitions it's going to deal with. If it doesnt it could lead to corrupt filesystems on flashes/nandroids.
If I ever do build it, it'll either be for a 8 or 16 gb card with a defined set of partitions.
You'll also need to modify the rom to actually boot from innerSDx too.
TheManii said:
It's turned off on the normal S5 build as ext4 requires additional modules, as it normally doesnt use ext4 I simply built it with them off.
I dont recall of CWM 1.8/2.5 (which streakmod is based off of) even supports ext4, the earliest one I can confirm it does is 4.0 as that was the 1st version built against the stock GB recovery. GB was the 1st rom that uses ext4 by default (on devices that launched with GB or newer)
Click to expand...
Click to collapse
well... i would appreciate if you could make it support by default of ext4... no harm to it right?
lol.. i really thought streakmod comes from 4.0 but it seems i missed that... man ... streakmod really so obselete..
TheManii said:
I havnt actually tried it (but I plan to some day in the future): just manually make the partitions and add an extra one onto the end for /system.
At that point: unless you follow a standardized layout, you're going to need to manually build CWM as CWM needs to know ahead of time the layout and size of the partitions it's going to deal with. If it doesnt it could lead to corrupt filesystems on flashes/nandroids.
If I ever do build it, it'll either be for a 8 or 16 gb card with a defined set of partitions.
You'll also need to modify the rom to actually boot from innerSDx too.
Click to expand...
Click to collapse
although i really welcome additional 3rd partition.. dont it have issues with mounting? because how streak works and meant to be, it never have one such as sd-ext ... i mean... some have tried to make it appear on windows but failed miserably.. and thus gave up on it.. and since the fs is ext type, we do need to install driver for it such as Ext2Fsd to make it able to read and write on windows... also.. for media file, it may not detect it unless we explicitly want the third partition to be used only for storage .... but if we can make it able to detect media.. that would be even better...
currently that work wonder is by using wifi file browser for now... for storing file inside /data
sd-ext is/was rather redundant as the S5 has a very large (for it's time) /data.
If anything you'd be better off making a large partition to mount as /sdcard and chainmount the real sdcard as /sdcard/sdcard2 or just /sdcard2 on ICS.
I have no idea how easy/hard all this is, I havnt tried any of it.
It really depends on if the kernal can detect additional partitions beyond innerSD0p6
I've bugged n0p about adding MTP into the ICS kernal so you can simply have a very large /data + /data/media, but he's not interested.
(though like it sounds, it only works on ICS or newer, it was introduced in HC 3.2, but we dont have a rom for that)
TheManii said:
sd-ext is/was rather redundant as the S5 has a very large (for it's time) /data.
If anything you'd be better off making a large partition to mount as /sdcard and chainmount the real sdcard as /sdcard/sdcard2 or just /sdcard2 on ICS.
I have no idea how easy/hard all this is, I havnt tried any of it.
It really depends on if the kernal can detect additional partitions beyond innerSD0p6
I've bugged n0p about adding MTP into the ICS kernal so you can simply have a very large /data + /data/media, but he's not interested.
(though like it sounds, it only works on ICS or newer, it was introduced in HC 3.2, but we dont have a rom for that)
Click to expand...
Click to collapse
thats what i have been trying to do this past weeks.. making it /sdcard and chainmount the real sdcard as /sdcard/sdcard2 but to no avail... as it has no real solution to it...
mtp support is a huge leap since many says it has better file handling protocol but if its get added to ics that we have here.. wow.. that one is a huge plus for us.. :good:
have you edited your vold.fstab?
You need to edit that and change the mounts in your ramdisk at the minimum to do so

[GUIDE] External2Internal Ultimate

I thought about this idea more than a month ago when i came to know that the partitions could freely be altered, but i could not put into practice until i got my 32 gb card yesterday.
so basically, after following my guide you will have:
* supersized data partition (12 gigs): no more move to sd needed unless for huge games (i'm thinking fifa12 and asphalt7) and then again the stock move to sd feature will work as expected (it will move data to the actual external sd card)
* external sd card mounted as internal sd card: nothing to say here, just does what is expected
* real internal sd (ums partition) shrinked to minimum (half gig) because it needs to stay present: used to mount a swap file (optional)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What you will need:
* g.lewarne hydracore 4.3b kernel: you don't need it for anything special, but it's the most amazing kernel, and gavin is the most devoted developer ive seen on the n7000. cheers gavin and keep up the good work :good:
* swapper2: if you want to use the swap file (see at the end)
so be warned, i'm no real specialist here, so i'm not aware of the no dos, i just got my guide to work through trial and error and getting information from other threads.
so if you follow my guide you're almost good, if not you may cause an atomic bomb to fall over your city, not my problem :silly:
enough chit chat for now let's head directly for the guide:
1. reboot to recovery, and connect your phone to your pc
2. run a command prompt and type the following (wait a little bit until the adb server starts on the phone, you can verify it by typing "adb devices" if you get a serie of digits then you're good to go.
Code:
adb shell
parted /dev/block/mmcblock0
you'll get into the parted interactive shell, this is where serious work done
Code:
did i remind you to backup your system,
this is your last stop before the no back point
so you just might wanna "move" all your internal sd stuff to the external sd,
and backup your system to the external sd also
(you just need to restore the data partition afterwards the rest of the system is safe but who knows :p)
ps: you can do your backup on cwm without leaving adb shell on the pc just like you will do the format later thanks to cwm
remove the partitions
Code:
rm 10
rm 11
make the new changed size partitions
Code:
unit b
mkpart primary 1174405120 14680064511
mkpart primary 14680064512 15216934911
name 10 DATAFS
name 11 UMS
now in cwm go to mounts and storage and select "format /emmc" and "format /data"
in parted type "print" and you should see this output
Code:
Number Start End Size File system Name Flags
1 4194304B 25165823B 20971520B ext4 EFS
2 25165824B 26476543B 1310720B SBL1
3 27262976B 28573695B 1310720B SBL2
4 29360128B 37748735B 8388608B PARAM
5 37748736B 46137343B 8388608B KERNEL
6 46137344B 54525951B 8388608B RECOVERY
7 54525952B 264241151B 209715200B ext4 CACHE
8 264241152B 281018367B 16777216B MODEM
9 281018368B 1174405119B 893386752B ext4 FACTORYFS
10 1174405120B 14680064511B 13505659392B ext4 DATAFS
11 14680064512B 15216934911B 536870400B fat32 UMS
12 15216934912B 15753805823B 536870912B ext4 HIDDEN
now the hardest part is over, restore your data partition and you will be able to boot you system normally. and you go to your storage information you will find that your app storage is now 13gigs and the usb storage is just 500 megs yay
to switch the sd with the internal you will have to modify vold.fstab file(thanks to ciphray for his guide on how to do so)
you can use the modified file from ciphray thread here which i didn't beacuse his file was smaller
so i just pulled the file to my pc
Code:
adb pull /etc/vold.fstab vold.fstab
modified it with notepad++ or any dev text editor (don't use windows notepad it will mess the file)
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
and push it back to phone + change permissions
Code:
adb push vold.fstab /etc/vold.fstab
chmod 644 /etc/vold.fstab
restart your phone and voila
as a final step you can use the now pretty useless internal space (500megs remember) as a swap sapce
download swapper2 from the play store here https://play.google.com/store/apps/details?id=lv.n3o.swapper2
run it and go to settings
set swap place as /sdcard/external_sd/swapfile.swp
set swap size to the max
set the swappiness to 20 ( you can rise the value a little but don't put a high value or the system will do much swapping all the time -value of 100 means any memory not used actively will be swapped- )
wait until the process finishes then reboot your phone
you can verify that swap is working by typing "free" in the shell if the line beginning with swap is not all zeros then you're swap is working.
hope my guide will be usefull, and don't hesitate to ask me any question
Awesome, thanks! Will try it out when I get some time
If you want more app space you can erase the hidden partition and get more space.
Sent from my GT-N7000 using Tapatalk 2
Okay, I've performed the whole thing, and just a few remarks on my experience
If you want to modify the vold.fstab straight from recovery without having to reboot first, you can simply mount the system partition, and retrieve the file from /system/etc/vold.fstab instead of /etc/fstab
More importantly, following your instructions, I ended up in a situation where my apps previously moved to the sd card weren't recognized. I've solved this by modifying my vold.fstab as follows:
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
That way, all my apps were properly recognized without issues. I'll probably be moving them back to phone now though.
Will be trying this setup over the next few days and see how it performs, but one caveat I missed is that you may not be able to install the whole of some apps on the data partition, as some the data will always be stored in the sdcard/Android folder, which would make the 12GB on /data less useful than I initially thought, unless I'm missing something of course
Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!
zongamin said:
Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!
Click to expand...
Click to collapse
here you are, look at the OP
i didn't realize the screenshot like was corrupt
if you read the op i mentioned the resulting sizes after the mod
sd storage will be mentioned as 500 megs (actually taken from the internal emmc) that i use for swap space
Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2
As far as I know, the HydraCore kernel doesn't allow swap, so it's unuseful to setup a swap file with swapper. Also, presently no Note kernel has swap enabled.
Carefully crafted on my Galaxy Note, for your eyes only
Hydracore 4.1 since has swap enabled in its kernel.
Sent from my GT-N7000 using Tapatalk 2
I'm sorry, I didn't know Gavin had listened to what I had asked oh so many times
Carefully crafted on my Galaxy Note, for your eyes only
travis82 said:
Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
i was fearing that the phone won't boot if the partition isn't available after a clean setup.
so i decided to leave the small size partition and make it useful for swap instead.
btw does anyone know how to use a bigger swap file with swapper2?
I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth
antique_sonic said:
I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth
Click to expand...
Click to collapse
just type print on the parted shell
and then you can recalculate new sizes for the data partitions, it should work like a charm
So... Im a USER, and there are part I am a bit confused about... BUT ill ask anyway!
It seems that if I wanted to resetup the partitions, I wouldnt need to mess with the pit files correct?
OR, because I want to totally KILL USB Storage, dedicate the entire internal memory to /data, and make /sdcard TRULY my sdcard, would I truly need to mess with the pit file?
Has anyone tried with killing off /ums completely?
Any help is appreciated. Also, I am using the i717 (AT&T GNote version), but my desire is the same so I figured Id post here...
EDIT: im not too worried about rom flashing, I normally slim down ROM's before I flash them, so Im not afraid of changes that have to be made (in txt files) in order to have them work properly on a UMS'less modded device. However, I do need to find out how to properly backup the pit file before I even THINK Of messing with it.
do i have to redo the whole procedure if i flashing nightly every time?
Anyone tried this on JB roms?
Hello?
Sent from my GT-N7000 using Tapatalk 2
jaguaralani said:
Anyone tried this on JB roms?
Click to expand...
Click to collapse
+1
I get 64 gb sandisk microsd card. I want to use this mod on jb stock LSC rom.
Can we use on jb roms?
GT-N7000 cihazımdan Tapatalk 2 ile gönderildi
Helpppppp
Envoyé depuis mon GT-N7000 avec Tapatalk
JB ready
I've tried it worked fine on Ultimate and Alliance ROM. Just edit vold.fstab in /etc after install new ROM. Replace 11 to auto and { } to { }. Now I need help if anyone have the original partition info, incase I wanted to restore.

Tutorial: How to unbrick/unroot Nook Simple Touch Glowlight

TUTORIAL: How to unbrick/unroot Nook Simple Touch Glowlight​
First at all, sorry for my english errors, I´m from Brazil and I read in english much better then I write.
And, considering what I´ve learned here, I´ll try to retribute with this post. So, please, disconsider my errors.
In my first day with NSTG, I´ve bricked the device when I try to unroot when I formated all partitions (with MiniTool) and write my backup file.
The problem was: I made a wrong backup file, which have only 76mb! So, at this point, I needed to recover formated partitions/data.
Some people was affraid to share their backup image beacuse it contains personal informations about the Nook. In fact, the ROM partition contains all nook info.
My conclusion was, I need to recover my ROM partiton (with all nook info) and get a image to overwite with ROM. This is my solution for bricked nook or to return to stock parameters (unroot). If you formated your NSTG accidentaly or want to unroot, this will work for you.
What it does:
Recover accidentaly formated NSTG or Unroot for those don´t have backup file.
What you will need
(I can´t post external links)
Download Nook Simple Touch Glowlight Image (without Rom partition): goo.gl/W4OYy (280.74mb)
Download Tools Pack: goo.gl/6ulSC (15.13mb)
This pack contains: (if you already have, don´t need to download)
-MiniTool Partition Wizard
-WinImage
-Roadkil.Net - Roadkil's Disk Image​
Download noggie.img (http://forum.xda-developers.com/showthread.php?t=1577494)
Download 7-Zip if you don´t have how to decompress .7z files (google it)
2 SD´s Cards (or at least 1 SD card)
Instrutions
I presume you downloaded all files above, unzip in a directory.
Do a backup of your Nook even if it is partial bricked!!! http://forum.xda-developers.com/showthread.php?t=1142983
Warning: ignore this step may brick your device permanently.
-Recovering Partitions of a NSTG Accidentaly Formated:
Write noogie.img in a SD Card with WinImage (run as Administrator)
Insert SD in Nook and Boot ("Root Forever")
Open as Administrator MiniTool Partition Wizard.
Select Nook drive and click in "Partition Recovery Wizard".
Do a copy of "rom" partition to another SD card (or format noogie card and paste rom)
Click in "Apply" (top bar in the left) and wait complete the modifications
-Writing the image:
Open DiskImager, in "Write Image" tab select the Phisical Disk with 1.86Gb and Target file: NSTG-backup-norom.img
Click in START and wait until complete.
-Writing the "rom" partition
This step will put the personal information back in NSTG. Your NSTG must have to booted with noogie (showing "Root Forever") and the SD with "rom" partition attached in card reader.
Open MiniTool Partition Wizard.
Copy from SD "rom" partition to the second space in nook disk (in the unlocated espace between "boot" and "factory" partitions)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have some size problem to paste the partition in this unlocated space, try to first resize the rom partition to 15mb and the paste (I did this and works).
2. Apply all changes.
Finishing
At this point you will have a working device, but you can do a hard reset just in case (power on with two side buttons pressed).
Or, restore to factory (8 boots).
Good Luck.
Hi folks,
I think would be more helpful if a good soul share a NST backup image beyond the NSTGL available in this post (posted by me). I dont have the NST, but is very easy to remove the ROM partition, just delete with MiniTool Partition Wizard.
Many people, when rooting Nook, dont do propperly the backup.
Can anyone donate a backup image? :good:
Thanks in advice.
Thank you
I recovery rom partition but just only files not partition exactly. I just create a Fat partition format in partition number 2 and put those files in there and voila it works after second reboot.
Thank you very much!
ROM deleted
Great !
What can i do when deleted my ROM - Partition ? - I forgot a backup argh !
belomfautor said:
Great !
What can i do when deleted my ROM - Partition ? - I forgot a backup argh !
Click to expand...
Click to collapse
Hi, you can do this:
-Recovering Partitions of a NSTG Accidentaly Formated:
Write noogie.img in a SD Card with WinImage (run as Administrator)
Insert SD in Nook and Boot ("Root Forever")
Open as Administrator MiniTool Partition Wizard.
Select Nook drive and click in "Partition Recovery Wizard".
Do a copy of "rom" partition to another SD card (or format noogie card and paste rom)
Click in "Apply" (top bar in the left) and wait complete the modifications
Please Guide me
I don't understand this step:
-Writing the "rom" partition
This step will put the personal information back in NSTG. Your NSTG must have to booted with noogie (showing "Root Forever") and the SD with "rom" partition attached in card reader.
Open MiniTool Partition Wizard.
Copy from SD "rom" partition to the second space in nook disk (in the unlocated espace between "boot" and "factory" partitions)
----------
Do you have any video show the way to do that?
Or you can divide into smaller step
I completed write the image to NOOK already but cannot follow the Step 2 when using Minitool Partition Wizard, now my device is still brick
Please help :crying:
Now I understand the way
But when I write the image to Nook, I don't see the .rom partition?
What I need to do to display the .rom partiion?
Please help
---------- Post added at 12:45 AM ---------- Previous post was at 12:24 AM ----------
Could you please export the format partion of SD card which have .ROM partion to an .img file?
I have successully restore my NOOK after restore my fail backup image --> it show .rom partiion
Thanks a lots
Luckily for me when you created that Thread
Thanks a lots again
A Friend from Vietnam
hi everybody,
I have a NST, without back up
I've removed all partition with mini tool partition and now my PC can't see the NST when I connect it wit USB cable.
I've read a lot of tread, but no one solution works....
please, can some of you help me?
Is there a way to use the NST by booting it only from SD?
Thank you all
bestcaster said:
hi everybody,
I have a NST, without back up
I've removed all partition with mini tool partition and now my PC can't see the NST when I connect it wit USB cable.
I've read a lot of tread, but no one solution works....
please, can some of you help me?
Is there a way to use the NST by booting it only from SD?
Thank you all
Click to expand...
Click to collapse
Hello,
I have the same problem after trying to root my Glowlight Nook. Can anybody send be an instruction or links to download the needed Images ?
Thanks
Thank you!
oh my god! you are the most awesome person alive! ever!
I got this as a birthday gift,and spoilt it on my first day!
Now,its back! *phew*:good:
hello,
have a big problem i bricked my NSTG i think on boot i only get an "install failed" i dont have a backup of the rom partition, but i have the rombackup.zip, is this enough for recovering? what have i to do now? i followed this tutorial, but it didnt help
greets,
marcel
Thanks for the post. I was able to unbrick my Nook Simple Touch Glow after doing something similar to what you did, ipedro3, creating a 75mb backup. My Nook is awake but won't connect to the computer properly unless there is an sdcard inserted. I use Calibre to send books to my Nook and Calibre thinks that my sdcard is the main memory of the Nook. I hope this makes sense and that someone has some advice.
aknas22 said:
Thanks for the post. I was able to unbrick my Nook Simple Touch Glow after doing something similar to what you did, ipedro3, creating a 75mb backup. My Nook is awake but won't connect to the computer properly unless there is an sdcard inserted. I use Calibre to send books to my Nook and Calibre thinks that my sdcard is the main memory of the Nook. I hope this makes sense and that someone has some advice.
Click to expand...
Click to collapse
I have the same problem. I think the internal storage has some sort of problem so the device cannot connect to the partition. Can someone help please.
The device works but when we go to Setting/Device Info, the Available Storage shows "Not available" instead of the storage of the partition.
cukem10 said:
I have the same problem. I think the internal storage has some sort of problem so the device cannot connect to the partition. Can someone help please.
The device works but when we go to Setting/Device Info, the Available Storage shows "Not available" instead of the storage of the partition.
Click to expand...
Click to collapse
Does anyone have any new ideas on how to fix this?
cukem10 said:
The Available Storage shows "Not available" instead of the storage of the partition.
Click to expand...
Click to collapse
You may have trashed the /media partition.
You can check and/or fix that with noogie and PartitionMagic.
You can check and/or fix that with ADB shell.
Thank you
Renate NST said:
You may have trashed the /media partition.
You can check and/or fix that with noogie and PartitionMagic.
You can check and/or fix that with ADB shell.
Click to expand...
Click to collapse
Thank you very much for replying.
As I have noogie and Partition Magic, I will try to fix it. I have very limited knowledge about this so I am a little nervous.
I have both Windows and Ubuntu on my laptop so can you please write a tutorial for this issue?
Thank you very much. At least I know the tools that I need to have.
Many many thx man!! i have followed your instructions and it is booting now... it is asking me to configure my nook now!!! THX!!!
question when i copied my saved ROM partition to the nook, i had to resize it to 15mb as you said but now my nook ROM partition is 15mb... does it matter?
how do you do a factory reset? you said boot 8times? what does that mean? should i actually do a factory reset?.... I assume that i need to root my nook again also?
when i connect the nook with my pc via usb mode, it shows 2 removable drive but none is accessible.. it's empty (2nd one probably cuz i don't have sd card inserted) but my nook drive is no more accessible??
I have done a factory reset also.
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
Renate NST said:
You may have trashed the /media partition.
You can check and/or fix that with noogie and PartitionMagic.
You can check and/or fix that with ADB shell.
Click to expand...
Click to collapse
how to do it with partition magic?
cukem10 said:
Thank you very much for replying.
As I have noogie and Partition Magic, I will try to fix it. I have very limited knowledge about this so I am a little nervous.
I have both Windows and Ubuntu on my laptop so can you please write a tutorial for this issue?
Thank you very much. At least I know the tools that I need to have.
Click to expand...
Click to collapse
I'll try to fix this week too. Have you had any luck?

[HELP][Half-Solved!] No Internal Memory.

Sup!
The problem is, that after i install ROMs via NAND+ext i cannot simply use it, because after rebooting it shows htc logo and then screen goes black.
I used only NAND roms before, because my sd card always failed to create an EXT partition on it.
But idk why, few days ago i noticed that while wiping, it didn't skip EXT partition like always, so i created one via TWRP recovery and tried to install some roms on ext.
I've done several full-wipes etc, but always it succeeds with installation, and then it goes black screen on rebooting.
What can be the problem? I thought it might be boot.img-related, but same thing occurs in 2nd rom i try to install.
I don't want to go back to old NAND rom, so if you guys could help me out, i would be really happy.
I spent several hours looking for a solution, but no positive results..
Also, i had a problem in trying to reanimate my phone via Fastboot/ADB; simply because i don't know how to proceed from bootloader to fastboot to get my phone connected with pc commands...
I tried to flash this and that ROMs.
Regards!
you could try;
changing recovery (eg 4ext), i always seem to have trouble with twrp flashing sboot, 4ext works ok
increase sboot or boot size
format ext4 with 4ext recovery
not used fastboot much, there is a tutorial here http://forum.xda-developers.com/showthread.php?t=2277112
hope this helps
if not post your setup, partition sizes etc.
Thanks for reply Robbie!
Firstly, i cannot find 4EXT recovery to flash it straight from PC :/ Any other recommended recovery's?
Secondly, not sure if i understand sboot and boot resizing correctly.
Also, when i flash TWRP for example, in config file when i change system ya[/B ] to 280mb is it enough? I mean, when i change size via HD2Toolkit, it automatically applies CWM...
http://goo.im/devs/Xylograph/Various/Recoveries/NAND
flash it using existing recovery
in later versions of clk you can easily resize your partitions, sometimes increasing boot partition may solve booting problems.
eg black lk from here http://www.mediafire.com/download/n0aa6qv88t3n1sv/black_lk_20130506-Ex-TWRP_2_5_0_5.zip
extract it, browse to leoimg.nbh using hd2 toolkit "install custom NBH/NB RUU" and install.
Then flash 4ext using the included recovery.
Profit?
Robbie P said:
http://goo.im/devs/Xylograph/Various/Recoveries/NAND
flash it using existing recovery
in later versions of clk you can easily resize your partitions, sometimes increasing boot partition may solve booting problems.
eg black lk from here http://www.mediafire.com/download/n0aa6qv88t3n1sv/black_lk_20130506-Ex-TWRP_2_5_0_5.zip
extract it, browse to leoimg.nbh using hd2 toolkit "install custom NBH/NB RUU" and install.
Then flash 4ext using the included recovery.
Profit?
Click to expand...
Click to collapse
Never thought of going to CLK though
Okay, i have clk now.
So i need to put 4ext zip into SD card throught TWRP usb plugging, and then install it straight from twrp?
Update!
I flashed 4EXT, althought i had strange code message after flashing it:
Code:
Writing recovery partition...
All done.
Updating partition details...
E:Failed to mount '/system' (MTD)
Partition details updated
Anyway, it seems to load w/o problems
Whats my point... i noticed, that i have ext2 partition on my phone, not ext4.
Can it cause black screen problem?
What to do now?
(So many questions..)
~EDIT~
i used built-in partitioning to get EXT4 partition, then installed tytung's rom again, ofc succeed etc.
But after reboot i see htc logo for 1 sec, then black screen ... sigh
ZathuraPL said:
Update!
I flashed 4EXT, althought i had strange code message after flashing it:
Code:
Writing recovery partition...
All done.
Updating partition details...
E:Failed to mount '/system' (MTD)
Partition details updated
Anyway, it seems to load w/o problems
Whats my point... i noticed, that i have ext2 partition on my phone, not ext4.
Can it cause black screen problem?
What to do now?
(So many questions..)
~EDIT~
i used built-in partitioning to get EXT4 partition, then installed tytung's rom again, ofc succeed etc.
But after reboot i see htc logo for 1 sec, then black screen ... sigh
Click to expand...
Click to collapse
You need yaffs2 for nand for android to work
lolerpro8 said:
You need yaffs2 for nand for android to work
Click to expand...
Click to collapse
Okay, but... how to...get it ?
~EDIT~
Reflashed SlimRom with ext, but it hangs on htc logo again..
ZathuraPL said:
Okay, but... how to...get it ?
~EDIT~
Reflashed SlimRom with ext, but it hangs on htc logo again..
Click to expand...
Click to collapse
so, what are your partition sizes, nand and sdcard?
remember, if using nand with data on ext, you can afford a huge 350mb system partition or more since your data (apps and stuff) is on your ext4 sdcard partition.
Please provide details
Robbie P said:
so, what are your partition sizes, nand and sdcard?
remember, if using nand with data on ext, you can afford a huge 350mb system partition or more since your data (apps and stuff) is on your ext4 sdcard partition.
Please provide details
Click to expand...
Click to collapse
Here it goes!
recovery 8
boot 5
misc 1
system 235
userdata 157
sboot 10
cache 5
+ i have 2gb ext4
SlimRom requires about 210 system partition, so i set 235.
ZathuraPL said:
Here it goes!
recovery 8
boot 5
misc 1
system 235
userdata 157
sboot 10
cache 5
+ i have 2gb ext4
SlimRom requires about 210 system partition, so i set 235.
Click to expand...
Click to collapse
increase system to 350mb and reinstall "nand with dataonext" and see
Robbie P said:
increase system to 350mb and reinstall "nand with dataonext" and see
Click to expand...
Click to collapse
htc
...
...
SLIMbean
...
...
...
so far it went past htc logo, but it keeps showin me SLIMbean animation
humm..
~EDIT~
i went to setup wizard, but it kept crashing. I forgot to flash gapps as in thread...sigh.
wiped system partition, flashed gapps, and now booting.
Hopefully it will get to work now!
edit2:
htc logo for about 5 minutes already
EDIT3:
i fully wiped phone, reflashed rom and gapps, it booted (waited like 15min though), but i have some strange problems with going through setup wizard again.
Mainly it stops working after few minutes, and it launches again and again. Sometimes i make till wifi/gmail sync, but for example it keeps obtaining wifi for like minute, in meanwhile Calendar Memore stops working... then it freezes, stops working, and from beginning...Once i made it through Google GPS localization.
The ****...?
Okay, after wipe and reflash, i faced same situation, but not sure why, Setup Wizard after 10 minutes of struggling allowed me to finish setup :highfive:
I still received "Calendar Storage has stopped working" every 10 seconds, so i cleared cashe of it in settings, seems to be solved.
Now, the only issues i face are:
- my phone shows me no internal storage at all...
In settings > apps, Internal storage bar is all grey without any numbers, also i cannot even update Nova Launcher because of insufficient space.
It would be quite sad to have my phone finally working, but with no storage to install basic apps like facebook, etc
-as i want to reboot my phone, it popped Setup Wizard again... WHAT THE!
Please help me with these problems...! :laugh:
EDIT:
i googled ''a bit'', and tried to copy busybox from /system/xbin to /system/bin, but i see no positive results..
Problem has changed.
Another update, but now quite positive.
After reflashing Slimrom and tytung's one over n over, i tried to flash tytung's 4.2.2, well, it succeeded.
Now i have 1,2gb of internal free memory, and it all seem to work flawlessly.
No idea why previous 2 roms didnt work 100%'ly :/
I think i won't do anything now, i am happy to have 4.2.2 features now, after 1 years of being stuck with 4.1.2
Anyways, big thanks for you Robbie. You are my life-saver once again!!!
Have a good night y'all, yawn
###EDIT###
Rom runs smoothly, i have 1,2Gb of internal memory, but my Google Play tells me "No connection. Retry" everytime i open it
Which means i canno't update/download anything.
Tried clearing cache,data,force stop,reboots, still no profits >.< im not into factory reset again though..
_____ EDIT _____
After wake up, around 1 hour of previous usage, i had black screen... rebooted -> Setup Wizard (although no errors or fCloses, only again no internal memory )
ZathuraPL said:
After wake up, around 1 hour of previous usage, i had black screen... rebooted -> Setup Wizard (although no errors or fCloses, only again no internal memory )
Click to expand...
Click to collapse
it sounds like your ext4 partition (/data) is not being recognised.
Since you have to reflash, try deleting all partitions and format whole card with official formatter, then set up your ext4 partition again, use recovery to format it.
Try install again.
What is your sd card make, and class?
Robbie P said:
it sounds like your ext4 partition (/data) is not being recognised.
Since you have to reflash, try deleting all partitions and format whole card with official formatter, then set up your ext4 partition again, use recovery to format it.
Try install again.
What is your sd card make, and class?
Click to expand...
Click to collapse
hold on, gonna plug it through 4ext and try to format
Will edit when im done
_____________________________
Done formatting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also created 2 ext4 partitions (who will forbid lol) 1,5 and 1gb.
Now will flash SlimRom and gApps, i will update again as i get some new info
Robbie P said:
What is your sd card make, and class?
Click to expand...
Click to collapse
about sd card? umm, i think it's SanDisk, but what class... i don't remember.
UPDATE.
I hope that system will survive the night without problems..
Everything runs quite good, i have problems with syncing contacts, but i think i will bypass it.
I connected to Google Play, i have 1,2 Gb of internal memory, so this is positive.
One problem is that when i try to install apps from GPlay, blue bar keeps running infinitely... like something blocks apps from installing.
Gonna try uninstalling GPlay updates, maybe it will help..
Will update again tomorrow!
UPDATE.
Nope.
Again, after about an hour, system started cutting me off more and more processes, so i rebooted, and then i had infinite Cyanogenmod boot animation...
I think im gonna try freaking 4.1.2 with DoE or Nand...
This sd card makes me wanna break this phone into puzzles
PACman 1.2 doesnt work with Ext , but on NAND i have only 197mb of free internal storage after fresh install I wish i could increase this

Categories

Resources