I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!
Unbelievable
CC CEO said:
I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!
Click to expand...
Click to collapse
i would recommend to go back to your backup (you did do a backup right?)
just flash the data, system, and boot .img files back
since you're doing Hero im guessing you have the newer SPL
you might run into a roadblock trying to fastboot so if you cant get the fastboot to work then boot into recovery mode and then go into a command prompt and run the following:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
this will let you access your memory card
get the HardSPL from here
copy it into your card as "update.zip"
now apply the update with ALT+S
after its done you can reboot back into the bootloader with ALT+X and typing
reboot bootloader
Click to expand...
Click to collapse
now you should be able to flash you backups like usual
nope didnt make a backup...i know..
but...
i was able to format my sdcard back to its original state and i flashed google ion back on the phone. question is are there any lingering affects to the phone itself? in setting up the ext2 or anything on the stock card might i have pushed or pulled something i shouldnt have from the internal storage if i didnt create a backup??
if so. how would i fix this?
if you Alt+W'd the phone there wont be any lingering effects,,,, its wiped and wont bother you no sunder!
I was having the same problem as you, as I too am only using the stock 1gb sdhc that came w/ the g1.
just did searching on here and I got it up n running.
I'm thinking maybe you did like me and pushed the /app_s/ folder while the SD was mounted to your pc, this is what I am guessing was my issue.
I've come to that conclusion since I've done the push w/o mounting the SD
Also I found that I had to be in the app_s folder on my computer to push it right, at first I was pushing it and it was going into /system/sd/app_s/app_s
Here's Haykuro's original instruction's
Installation:
1. Download http://www.droiddeveloper.com/hrbuilds/app_s.zip
2. extract "app_s" into your sdcard's ext2 partition.
3. Download http://www.droiddeveloper.com/hrbuilds/hero-signed.zip
4. Place on regular sd card.
5. Reboot into recovery, wipe and flash.
6. Enjoy.
--
for step 2... make sure you are in the actual app_s folder when you do the following command and make sure the sd card is NOT mounted.
adb push app_s /system/sd/app_s
--
follow the rest of the instruction's as stated and you should be fine.
now, to get it running smoother...
follow the tutorial here...
http://forum.xda-developers.com/showthread.php?t=521251
also within the thread there's tip's on moving the Rosie.apk along w/ widget's to internal memory, I just focused on the larger widget's, the largest being the weather one.
hope this help's.
just one noob tryna help another noob out ;-)
please help
When i am doing the update.. i am getting this error.. .
E: Can't chown/mod /system/xbin (not such file or dir)
E: Failure at line 12: set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
installation aborted."
please help!!
Hi, I have a Nook Simple Touch device with a traditional problem of improper backup of 76 MB before rooting.
Now I have managed to retrieve files from the /rom partition (/devconf folder with 20 files like serial no, public key etc.) - I have them in my laptop as regular files as well as 16 MB partition image on SD card.
Would anybody be so kind to offer a full recovery method? I believe backup of somebody's full image and then overwriting the /rom partition would revive the device?
How much of your partition table is left, if any, and how familiar are you with linux?
Were it me, I might have a go at creating just the first partition - boot from noogie, connect to a linux box, and use fdisk to create the partition.
I'd then try doing a
dd if=single.partition.backup.img of=/dev/mmcblk0p1
(writing my boot backup to the partition I just created) and see if that file wasn't enough to bootstrap the other partitions. Depending on how you created the backup, you may have the boot flag set and the partition table stored; so long as you haven't actually put data on the other partitions yet, it may be possible to at least trigger the onboard restore.
These are values that work on the glow, and I believe on the touch as well:
Disk /dev/block/mmcblk0: 2000 MB, 2000683008 bytes
128 heads, 32 sectors/track, 954 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
Of the partitions, I still have:
- boot (I believe it is somewhat corrupted, but this I can restore from the backup)
- NOOK (FAT32) - should be OK, I see files in it;
- cache (Ext3)
- data (Ext3) - seems to be corrupted
Missing: factory (Ext2); one untitled partition and one unallocated segment.
Backup was created with Roadkil's DiskImage, with a source being the locigal drive (original boot partition).
I'm not good at Linux, but I know how to create partitions using Windows tools.
OK, I can try to recreate the boot partition and the rom partition, and restore the backup to it, then I'll see what happens.
Disk configuration for NST is different from the NSTG:
Cylinters: 238 Heads: 255 Sectors: 63
Nook is resurected!
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Yes, you save my nook. Thanks to your method i could revived my /rom.
but all is not done for me . i have a UK NST Glow and the glow is not working. I would like to update to firmware1.2 and may be this glow will function again. But When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Hello, new here so hope it's ok to hijack this thread slightly, seems the original issue has been solved and I think my problem is similar although I'm way out of my depth here... I've managed to brick my nook, and although I took a backup which is AFAIK correctly sized 1.86gb I can't restore it. I've tried putting noogie and cmw on the sd card but it's refusing to boot, I suspect I nonced the partition table up and can't even get the nook to register when I plug it in to the PC now. I suspect is obvious I'm a dumb noob but if anyone could help point me in the right direction it would be much appreciated
welcome to the brave new world of the "bricked forever" and endless nights.
Nobody blames you since everybody and their mothers seem to fall into the trap even if they are told to make a good backup.
i had read so much threads to resurect my nook that i don't exactly know how i made it through, but here are some indications:
Here are the objectives:
1) make a correct backup of your bricked nook: -> you can make after all stupid commands and you 'll come back to this point.
2) you'll have to resurect your /rom or your rombackup.zip (inside factory).
3) have the correct partition of your nook
4) reinstall the rom
for 2) this thread gives a way to get back your /rom. read carefully even roustabout's comment can really help
for 3) thanks to Renate NST in this http://forum.xda-developers.com/showthread.php?t=1805936&highlight=to+stock and her script "nookpart.sh" i could have a correct size for my partition. (method with wizard partition gives wrong cylinders alignement). read all of this thread it is really rich.
for 4) if you reach that point that should be easy.
Thanks for the welcome and the reply jjinkou2.
I'm guessing I need to work on the nook through a PC. I've currently got 2 PCs, one running window 7 and one on vista, I'm mainly working on the W7 machine. When I plug the nook in to it, a device briefly shows up as the h: drive in My computer but then immediately disappears and so I can't actually access it yet. I note that roustabout mentions working in Linux, if I had a Linux machine available would it be easier to get it to recognize the nook?
Edit: Just tried plugging the nook into my vista machine (which it has not been used on before) and the Found New Hardware window briefly pops up but then vanishes and I get a message on the taskbar: Device driver software was not successfully installed - OMAO3630 Device unplugged. Is there a fix for this pelase?
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
you'll need to install android sdk and check usb install in the extra.
Search for a file named "ADB + Fastboot + Drivers.zip" in the forum to easily have the adb.
With windows the usbdriver can be tricky to install. i had to use usbdview (look for it in google) and uninstall all B&N mass storage and OMAP3630.
The driver for usb inside the previous zip might not work also. i found one in the forum but can't find it right now.
Edit
found the usb driver that worked for me
http://forum.xda-developers.com/showthread.php?t=1125094
Excellent, thanks very much! Not entirely sure how I managed it but I managed to get to a point where I could use the method shown by budriunas and my nook is now working again, albeit with an older firmware and the glow light isn't working but at least it's not bricked! Now just to get the light working and then root the damn thing without killing it....
budriunas said:
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Click to expand...
Click to collapse
Thank you so much. My nook is back. I described my work in http://forum.xda-developers.com/showthread.php?p=34746242#post34746242.
jjinkou2 said:
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Click to expand...
Click to collapse
how did you do a partition table?? i have run nookpart.sh but i still get the problem : "When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
nookpart.sh will partition the internal memory exactly like it was.
This is important if you actually still have valid data but the partition table was destroyed.
If partitions are not looking correctly they may need to be formatted.
Don't be too quick to repartition/reformat until you know what the situation is.
i have used nookpart.sh but still no good, here is the result when i execute nookpart.sh. Everything works except internal storage not mounted correctly i think, i want to update to 1.2
edit: see my thread http://forum.xda-developers.com/showthread.php?p=48015536#post48015536 for more details
can anyone help me please i need to retrieve msgstore.db.crypt7 from my internal memory i have rooted my phone and have omega custom rom.i accidentally deleted the whole folder using es file explorer what's app only retrieves the message back 7 days ago and i need to go back further more,i have tried undelete and digger disk both dont find the internal memory i have tried several applications but wont find my phone i have enabled usb debug mode still wont find my phone i have heard recuva works but sgs5 doesnt have usb mass storage but on my pc windows 7 it shows portable device so i can see my internal and external but not through programs can anyone help me please?
bump any help please?
If you did the smart thing i.e. turned your phone off immediately after you deleted the file, you should be able to recover it. But if you kept mucking around (in addition to not having a backup of your phone), all bets are off. You may well have overwritten the database if you continued to use the phone.
Your best bet would be to copy the area of phone memory where the database is or was. That both preserves a copy of what is recoverable and lets you avail yourself of the large number of PC based data recovery programs available.
The following terminal (CLI) commands should image (make an exact copy) of the /data and /system partitions to your external SD card. Then use a PC based data recovery program to recover the deleted file. Check these commands for typos before executing them. A typo could make a real mess of your phone's file system.
$ su
# dd if=/dev/block/mmcblk0p25 of=/extSdCard/data.img
# dd if=/dev/block/mmcblk0p23 of=/extSdCard/system.img
.
fffft said:
If you did the smart thing i.e. turned your phone off immediately after you deleted the file, you should be able to recover it. But if you kept mucking around (in addition to not having a backup of your phone), all bets are off. You may well have overwritten the database if you continued to use the phone.
Your best bet would be to copy the area of phone memory where the database is or was. That both preserves a copy of what is recoverable and lets you avail yourself of the large number of PC based data recovery programs available.
The following terminal (CLI) commands should image (make an exact copy) of the /data and /system partitions to your external SD card. Then use a PC based data recovery program to recover the deleted file. Check these commands for typos before executing them. A typo could make a real mess of your phone's file system.
$ su
# dd if=/dev/block/mmcblk0p25 of=/extSdCard/data.img
# dd if=/dev/block/mmcblk0p23 of=/extSdCard/system.img
.
Click to expand...
Click to collapse
Thanks i've tried every recovery software for android but it's not detecting any of the internal memory as sgs5 does not have usb mass storage i have enabled usb debug settings i have the samsung usb drivers but it shows up on my windows 7 as a portable device.
do you recommend any decent software or tutorial's which might help me recover it.
Thanks for your help!
xxmcvapourxx said:
i've tried every recovery software for android but it's not detecting any of the internal memory as sgs5 does not have usb mass storage
Click to expand...
Click to collapse
You didn't follow any part of what I suggested, so it's a mystery why you quoted my post. I specifically advocated using PC based data recovery software, not an android app. And at no time would you need your S5 to be in MSC (mass storage) mode.
Use the posted commands to copy your memory contents to a SD card, plug the SD card into a PC and then use a PC based data recovery app. The commands can be entered from a terminal emulator app, TWRP or an ADB shell session CLI.
Good luck
.
LVM is a logical volume manager. It joins underlying physical partitions into a pool which can be divided to virtual partitions. Since there are no real partition layout changes, hard bricking is a lot more difficult (but not impossible).
You may have BlePart installed previously, it makes no difference. You can use stock partition layout.
WARNING: LVM requires you to install LVM compatible ROMs. Do not install non-LVM ROM if you have LVM installed.
All your data will be wiped.
Current space division
If you would like to change this, open the zip META-INF/com/google/android/update-binary, find the partition sizes, and modify data partition size (the total space is nearly 3GiB so watch the space).
System - 800MiB
Cache - 10MiB
Data - 2000MiB
Internal SD - rest of the free space
Requirements
LVM-compatible recovery installed
Strongly recommended: Unlocked pink screen
How to install
Download the zip from downloads below
Save it to your phone's EXTERNAL SD card
Reboot to recovery (if you notice errors it is normal, since LVM is not yet installed)
Install the zip from your external SD
Your phone will automatically reboot in 3 seconds
How to uninstall
Method 1
Download the zip from downloads below
Save it to your phone's EXTERNAL SD card
Reboot to LVM recovery
Install the zip TWICE (first time it will notify you LVM is installed, second time it uninstalls it)
Your phone will automatically reboot in 3 seconds
Method 2
Install any non-LVM recovery (TWRP recommended as some older CWM recoveries cannot format vfat properly)
Reboot to recovery
Wipe/Format system, data, cache, internal storage partitions (and repair file system if errors occur)
Reboot recovery
Method 3
Install stock ROM
Downloads
BlePart-LVM-11
Hello, Blefish
These lines i need to change? When i clean applications i have empty space in "System" 220mb, and "Data" i have 270mb empty space.
/sbin/lvm lvcreate -L 700M -n system lvpool;
/sbin/lvm lvcreate -L 10M -n cache lvpool;
/sbin/lvm lvcreate -L 2350M -n userdata lvpool;
/sbin/lvm lvcreate -l 100%FREE -n media lvpool;
Click to expand...
Click to collapse
P.S. Can i delete directly application from system.new.dat?
Good,thanks!
BlePart-LVM-11 uploaded.
This change is minor. It only simplifies installing/uninstalling and makes it easier for the end user. It also adds necessary checking mechanism to make sure the user is installing LVM from a proper location with proper tools.
My external sd card don´t work, can I still get it done?
MazdaGTI said:
My external sd card don´t work, can I still get it done?
Click to expand...
Click to collapse
Through ADB sideload you can do it . You need to install necessary drivers and ADB if you are on windows. Technically it is possible to use ADB and push the zip to /tmp/ for example, and install from there aswell.
I am not responsible for any damage that might happen to you, your phone, your sdcard your dog and so on, you are responsible for your own actions.
This is a Linux guide, asking about how to on windows will get no replies as I don't use windows.
First thing you need is a micro sdcard class 10, size up to you, in this guide I am using a 32 bit.
You need a micro sdcard reader.
insert the micro sdcard into your reader, insert reader into computer.
Open gparted
find your micro sdcard, delete entire contents format as fat32.
now make two partitions ext4 size up to you.
in this guide I made first one 1GB and other one 6GB
you should now have 3 partitions ALL 3 must be primary
1 fat32
2 ext4
when finished partitioning sdcard, remove from computer place in phone.
reboot into recovery
open micro sdcard on your computer
create a folder on your micro sdcard
call the folder dual_boot copy below file to this folder
https://www.androidfilehost.com/?fid=745425885120701124
your folder should look like this.
Install > dual_boot
Now all you see in this folder is lineage-p6601-Sdcard.zip
look to lower right of twrp you see install image click it.
now you see all the files.
select twrp_sdcard_recovery.img
next you are given 3 choices Boot, Recovery, System image.
choose recovery
swipe to confirm
back
back
back
reboot recovery
now before you continue
mount system
adb shell
busybox df -h
/dev/block/mmcblk1p3 5.8G 12.0M 5.5G 0% /data
/dev/block/mmcblk1p2 975.9M 1.3M 907.4M 0% /system
if you don't see similar to above don't continue
what above shows is data and system both empty and mounted to sdcard.
if you have above you can continue if not repeat steps until you do.
unmount system
install > dual_boot > lineage-p6601-Sdcard.zip
you should see detected filesystem ext4 for /dev/block/mmcblk1p2
let install finish
reboot system
once you see the word android
adb shell
df -h
you should see similar
/dev/block/mmcblk1p2 992M 638M 353M 65% /system
/dev/block/mmcblk1p3 5.7G 43M 5.7G 1% /data
let boot finish
download gapps place on your micro sdcard
once booted, setup, reboot to recovery and install gapps.
reboot system
the above is to setup dual boot, once setup is complete, to switch between OS, boot into recovery
navigate to dual boot
look to lower right of twrp you see install image click it.
choose which boot.img you want to use
next you are given 3 choices Boot, Recovery, System image.
choose boot
swipe to confirm
reboot system
phone_boot.img is the current OS you have on your phone, in my case v17 if you are running something other than v17, use it's boot.img instead, rename to phone_boot.img and replace the one you downloaded from this guide.
to boot to sdcard select sdcard_boot.img
if you just reboot, whatever the current boot.img that you flashed on your phone will be what OS it boots into, the OS is only changed if you flash another boot.img
if you need to backup rom on your phone you would need to flash twrp_phone_recovery.img else you can only backup sdcard OS.
Notice you will see BELOW!!!! on LineageOS
DO NOT TAP TO FIX!!!!!
DO NOT TAP TO FIX!!!!!
DO NOT TAP TO FIX!!!!!
On phone you will see this.
DO NOT TOUCH IT!!!!!
DO NOT TOUCH IT!!!!!
DO NOT TOUCH IT!!!!!
Note first time switching between OS, may take sometime as each OS, is adjusting to new sdcard.
After that should be just like a normal boot.
I have dual booted every device I own for years, never had a problem.
The OS, doesn't care where it's installed works great, no matter if on phone or sdcard.
can i swipe the notification of sd corrupt and new sd? or is persistent?
Alex19Gam said:
can i swipe the notification of sd corrupt and new sd? or is persistent?
Click to expand...
Click to collapse
I wouldn't.
Sent from my Life Max using Tapatalk