I am having a very strange problem that i haven't been able to identify why it happens. The problem is that i am building Android 4.4.2 for an H3 based board, i made a few customizations, including a resize on the partitions, so the system partition is around 2GB, Livesuit does flash the nand perfectly with no issues, but when i use phoenixcard for production, the SD card gets flashed ok with no errors, but when i try to make it to burn the nand, the green bar on the monitor stops in the middle and it never gets to burn the nand, the thing is that i need the phoenix card or another tool that lets me flash in production mode. The files that i modified were sys_partitions.fex, Boardconfig.mk and even the boot-resource.ini but phoenix card keeps doing the same specifically when the image gets to be a little bigger, specially the system partition (though i need that partition with that size).
I would really like some help, thanks in advanced.
Related
My 2GB SD used to let me flash my HD2 by putting the LEOIMG file on it.
I didn't use this method much, but it was always a good feeling, knowing I could, at any point, revert back to stock settings (SPL and all that jazz included) in case something goes wrong.
However, after trying out WP7, despite having re-formatted the card, I can no longer use it to do this.
I've tried partitioning with EASUS Partition software, I've tried fdisk under Linux and GPARTED. The card consists of a single FAT16 partition and that one file.
However, if I put the card in and boot the phone up holding down the Volume Down key, it'll enter the bootloader, flash a grey screen for a fraction of a second (I suspect it's the screen that lets me flash from SD card, but then something goes wrong), and then reverts back to the bootloader.
Does anyone know what could be wrong? I'd like to stress that the SD card DID once work fine.
Needs to be fat32 not fat16
samsamuel said:
Needs to be fat32 not fat16
Click to expand...
Click to collapse
Ahh, K. But still the same. :|
did you remove the stangely formatted wp7 partition?
Also, when bootloader flickers grey for a second, that can be bootloader looking at the file and checking it for deviceID and carrier/regionID, and finding a mismatch.
you will get this behavour if, for example, you try flash an incorrect rom (cooked, radio, splashscreen, different language, whatever, something that would require hspl) whilst hspl isn't installed
Ahh, it never occured to me that the file I extracted might have become corrupted, and I kept copying it over and over and over again.
Re-downloading the firmware and extracting the image file worked.
THANKS!
Hi,
I have a working rooted 8gb nook tablet. The tablet has stock recovery installed on it and I don't think I want to change it to cwm at this point, unless I absolutely have to. My question is -- can I use this method to backup my current ROM in case I do mess something up (like deleting build.prop file for instance)? The problem that I have is that the sd card ends up with only 50mb of free space after burning the image onto it and that is obviously not enough for the backup. I tried partitioning the card and creating an ext2 allocation (perhaps I need to use a different kind?) in addition to the tiny 50mb one, but cwm doesn't seem to recognize it and still tries to backup into the tiny space.
I would greatly appreciate any help.
Thank you.
Resize the partition of the SD card using a partition manager, or format the card and put these files on it (in root).
Forgot to mention in my original post that I did try resizing the 50mb partition to 1gb, but then the tablet just stopped booting at all. I had to take out the card and wait for a minute or two before it would start booting normally again.
I will try your files now. Thank you for quick response!
Nope, that did not work, unfortunately. It just booted normally, not from the sd card. But isn't the whole point of burning that image is to make the card into a 50mb one? I don't understand all the technicalities, but that seems reasonable, why else would they make it particularly 50mb large? And resizing the partition doesn't lead me anywhere either, as I mentioned above.
Maybe someone could point me in the right direction?
Right. So, the partition has to be checked as active if using MTP or flags should be on if using the other one. And the magical 50mb size allocation don't matter after all. Gotcha.
Back in December I attempted to update my Nook Tablet to a new build from CM. Something in the process went wrong, and left me without a bootable device. Soon after I packed to move cross country and the unit has been in a box since. I recently got it out to try and fix it but am having a difficult time understanding what happened to it. My assumption is that the internal memory is jacked in some way.
Currently, the unit WILL NOT boot with an SD Card in the slot. The screen stays black. If I remove the SD Card, it will boot.
The unit WILL boot into recovery, but will not write a new rom, always leaves me with a failed write message. (I have to insert & mount the SD Card AFTER I get it booted)
----------------
I am looking for suggestions on which direction to head to next. I have seen one members' video tutorials regarding formatting with ADB. The last time I used it was soon after the Droid X was released but I feel ok in performing the steps.
Is that the route I should take? Am I missing some other step in troubleshooting?
TIA.
--JD
See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for pointers on making a bootable SD card, and http://forum.xda-developers.com/showthread.php?t=2056626 for pointers on how to flash CM10 onto your NT emmc.
digixmax said:
See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for pointers on making a bootable SD card, and http://forum.xda-developers.com/showthread.php?t=2056626 for pointers on how to flash CM10 onto your NT emmc.
Click to expand...
Click to collapse
I appreciate the time you took to reply. However, I have tried creating a bootable SD card already. The tablet simply will not boot with a card in the physical slot, either with a bootable card, or without. If a card is in the slot, the tablet will present a black screen tricking you into thinking it is dead, or otherwise fubar'd. Hence my dilemma on how to proceed.
--JD
jdfgura said:
I appreciate the time you took to reply. However, I have tried creating a bootable SD card already. The tablet simply will not boot with a card in the physical slot, either with a bootable card, or without. If a card is in the slot, the tablet will present a black screen tricking you into thinking it is dead, or otherwise fubar'd. Hence my dilemma on how to proceed.
--JD
Click to expand...
Click to collapse
Use this...
http://iamafanof.wordpress.com/2013...-2-jellybean-sdcard-img-for-nook-tablet-0416/
Just write the image file to your SD card and put it in your nook.
datallboy said:
Use this...
iamafanof.wordpress.com/2013/04/16/cm10-1-android-4-2-2-jellybean-sdcard-img-for-nook-tablet-0416
Just write the image file to your SD card and put it in your nook.
Click to expand...
Click to collapse
I have already done something similar with another build. Doesn't matter what type of SD card I put in the tablet, empty, formatted, bootable, etc... as long as an SD card is in the slot, the tablet will not go anywhere past a blank, black screen. I can however boot the tablet into recovery without an SD card, then mount it within in recovery, and attempt to write a new rom but it always errors out.
Once your NT goes blank/black, if you just leave it alone for say 3-5 min, does it eventually boot to internal recovery?
digixmax said:
Once your NT goes blank/black, if you just leave it alone for say 3-5 min, does it eventually boot to internal recovery?
Click to expand...
Click to collapse
Unfortunately no. Originally, when I got it back it out to fix it, I went for a week thinking the thing was dead. After a few aha moments, thats when I figured out having a card in the slot would keep the screen black.
--JD
jdfgura said:
Unfortunately no. Originally, when I got it back it out to fix it, I went for a week thinking the thing was dead. After a few aha moments, thats when I figured out having a card in the slot would keep the screen black.
--JD
Click to expand...
Click to collapse
My NT would typically try to boot off SD if it finds first partition to be bootable and containing the requisite boot files MLO and u-boot.bin, and if these files are corrupted its screen would stay blank/dark for ~3-5 min then it would boot off emmc. Otherwise, if the first partition is not bootable or does not contain MLO & u-boot.bin, the NT would boot straight off emmc.
I assume that you already tried different SD cards with same results?
digixmax said:
My NT would typically try to boot off SD if it finds first partition to be bootable and containing the requisite boot files MLO and u-boot.bin, and if these files are corrupted its screen would stay blank/dark for ~3-5 min then it would boot off emmc. Otherwise, if the first partition is not bootable or does not contain MLO & u-boot.bin, the NT would boot straight off emmc.
I assume that you already tried different SD cards with same results?
Click to expand...
Click to collapse
Yes that's correct. I am going to go through various steps tomorrow, try it all again in case I missed something. I still feel as if I have corrupted the emmc somehow.
jdfgura said:
Yes that's correct. I am going to go through various steps tomorrow, try it all again in case I missed something. I still feel as if I have corrupted the emmc somehow.
Click to expand...
Click to collapse
FWIW, this link http://omappedia.org/wiki/Bootloader_Project provides an overview of the NT OMAP processor boot process.
Sounds like there might be a problem with your NT SD card reader, as a blind shot maybe you can try blowing compressed air into the empty card slot.
digixmax said:
FWIW, this link http://omappedia.org/wiki/Bootloader_Project provides an overview of the NT OMAP processor boot process.
Sounds like there might be a problem with your NT SD card reader, as a blind shot maybe you can try blowing compressed air into the empty card slot.
Click to expand...
Click to collapse
When I get it booted into recovery, I am able to insert a card and mount it. If I attempt to install a rom at then end of the installation it fails with a write error. So I believe the card slot is good.
Now Booting
After some trial and error, the nearest I can figure is that there is something wrong with the SD->MicroSD adapter I was using. I discovered that both MicroSD cards I had been using were not properly mounting on my phone. I happened to have a new 16gb card in my desk and used that. I was finally able to boot it from the SD card in 4.2.2 - from there, since something was obviously wrong with the partitions on the EMMC, I wrote it back to 1.4.2 stock.
Am now working on get it re-rooted, with 4.2.2.RC5 written to the EMMC.
The two Micro cards I had been using had only ever been used with one adapter. I tried reformatting the cards, to no avail. The 16gb card was reporting a single partition of 9.22gb and the 8gb was reporting 3.54gb on a single partition. Never seen anything like it.
I appreciate all the suggestions and the fresh links given to me for the boot images and such. Thank you very much.
--JD
jdfgura said:
...
The two Micro cards I had been using had only ever been used with one adapter. I tried reformatting the cards, to no avail. The 16gb card was reporting a single partition of 9.22gb and the 8gb was reporting 3.54gb on a single partition. Never seen anything like it.
...
Click to expand...
Click to collapse
I'd suggest you try using a combination of MiniTool and SDformatter (https://www.sdcard.org/downloads/formatter_4/) with the option Full (Overwrite) to delete the existing partition and reformat the entire card.
Hello.
My Father has a Galaxy S II , and he is always complaining that his phone is low on space.
The phone is 16GB and has another 16GB MicroSD card.
Most of his on-board integrated 16GB is free, and his MicroSD card is almost completely empty, the problem is that this phone has a very small Android OS 2GB partition, and every time he installs an app it always leaves something on the OS partition (even after manually moving every possible app to SD using the built in Move To SD, and placing all photos and videos on MicroSD). So even with very few Apps installed his phone is always begging for space since essentially he can only make use of 2GB of his 32GB of storage.
So I have considered maybe the best way to fix this his issue, is to install a Custom ROM on his phone, which only contains 1 Single Partition for the integrated 16GB of storage space, and another partition for the 16GB of MicroSD storage.
Thus eliminating the limited 2GB OS partition. (basically make it like every new Android phone since the galaxy S2)
I have never used a custom Android ROM so this is new to me ( i am more familiar with PC's).
So my primary question before I start looking for info and procedures on rooting and custom roms for this phone is as follows:
IS it possible to even install a new android OS on this phone which will have only one primary partition, or is this phone forever destined to only work as it is now with a small 2GB OS partition? In other words is there a hardware limitation which prevents this phone from addressing more than 2GB for its OS partition?
Thanks for any help you can provide.
mr_interested said:
IS it possible to even install a new android OS on this phone which will have only one primary partition, or is this phone forever destined to only work as it is now with a small 2GB OS partition? In other words is there a hardware limitation which prevents this phone from addressing more than 2GB for its OS partition?
Click to expand...
Click to collapse
You can repartition the phone using a modified PIT file. You will be able to increase the Data partition to avoid the "out of space" when installing or updating apps. The tradeoff is to have a smaller internal SD partition.
I have done it to my S 2.
There is a thread with clear instructions on how to do it. You will have to learn to use Odin, but that will be very useful as long as you have Samsung phones.
Here is the link: [MOD][GUIDE]Partition your internal memory for better App management (Pit Files)
svbarbosa said:
You can repartition the phone using a modified PIT file. You will be able to increase the Data partition to avoid the "out of space" when installing or updating apps. The tradeoff is to have a smaller internal SD partition.
I have done it to my S 2.
There is a thread with clear instructions on how to do it. You will have to learn to use Odin, but that will be very useful as long as you have Samsung phones.
Here is the link: [MOD][GUIDE]Partition your internal memory for better App management (Pit Files)
Click to expand...
Click to collapse
Thanks for the info.
Would it not be easier to just format the phone and start from scratch by installing a new custom Android OS ?
Will starting from scratch with a new OS allow me to set my partitions (just like on a PC) ?
Thanks again.
mr_interested said:
Thanks for the info.
Would it not be easier to just format the phone and start from scratch by installing a new custom Android OS ?
Will starting from scratch with a new OS allow me to set my partitions (just like on a PC) ?
Thanks again.
Click to expand...
Click to collapse
No. You must use the Odin / Pit file to modify partition sizes.
And yes, that assumes you will flash a new rom.
svbarbosa said:
No. You must use the Odin / Pit file to modify partition sizes.
And yes, that assumes you will flash a new rom.
Click to expand...
Click to collapse
Don't forget to mention that re-partitioning your phone will delete all data so do a backup!!!!!
gsstudios said:
Don't forget to mention that re-partitioning your phone will delete all data so do a backup!!!!!
Click to expand...
Click to collapse
Well said.
I did not mention it because it is the first step in the instructions.
But it is never too much to repeat. Backup! Backup! Backup!
Alright, before I begin, here's what I have for my device:
Custom bootloader with the ability to boot any kernel I might need
CWM
OmniROM source tree compatible with my platform
~64 GiB SDXC microSD
Now, the issue is that my device (Acer Picasso ([Iconia A500]) has finally lost its ability to properly read certain partitions of the internal flash memory. Despite several attempts at reformatting the partitions (usually ending up in "this operation doesn't work because I/O error") I am unable to revive those partitions of the flash space. However, I have been able to flash a kernel and get it to boot Lubuntu off an external sdcard.
Nothing against Lubuntu, but I can't exactly play Clash of Clans/MCPE. And OnBoard is a poor replacement for Android's keyboard. It would be really nice if I could do the exact same thing I did with Lubuntu with an Android root filesystem.
Is using an external SD as a root filesystem possible? If so, how practical?
As sidenote, how hard would it be to solder in new flash memory in case it comes to that?