Are there any tutorials out there that walk you thru the process step by step? I understand the buring iso image and booting from disk, but i dont understand the partition thing.
which partition would be good for leedroid (best performance / most app space) ?
Also, when flashing leedroid (or any other rom), do you flash the radio in the same manner as the rom itself? (SD card .zip)
Sorry. im trying to read as much as i can, but its mostly words, which doesnt help a noob like myself.
thanks
You will boot from the disc that you burnt the ISO to and follow all the instructions. That will give you s-off once it's all done and it should boot into whatever set-up you had before.
To flash a new partition table you will need to use ABD. You will to flash the new table and then re-install your ROM or recover a NANDroid backup. If you restore a back up though, make sure it will fit in the new partition sizes.
So if i download the latest leedroid "With .MD5", is the .MD5 the partition for the internal memory?
Sike-1 said:
So if i download the latest leedroid "With .MD5", is the .MD5 the partition for the internal memory?
Click to expand...
Click to collapse
What is MD5?
MD5 stands for ‘Message Digest algorithm 5′, and for most applications, MD5 represents something like a digital fingerprint so that you can be sure a file is exactly the same whether it is stored here, there, or anywhere. It’s a very effective way ensure a digital signature and file integrity.
So why use MD5?
If you’ve ever downloaded a large file, you probably want to be sure that the file wasn’t corrupted in the process. This is particularly true with things like disk images, where using a corrupt ISO to install software can lead to disaster (I once used a corrupted ISO file to attempt a Linux install, bad idea). Using the MD5 Hash, you can be sure that the file you have on your machine is digitally identical to the original file from the source. Many sources of large files will offer an MD5 Hash to compare your file to so that you can be sure the file has transferred completely and without any molestation.
Awesome. Thanks a bunch man
Related
Ok I don't want to sound like a retard here but there are a few things that I really want to find out if you guys don't mind.
1). Extended Rom is located in the hidden partition of PPC Devices, that the device installs after a hardreset right? Where is my Device ROM located? The one I flash onto it, is it in the hidden partition or another place(as hidden partition content can be deleted)?
2). What about the ROM files that comes in the *.exe format, those that can flash your device?
3). How do I backup my current ROM to a *.exe format so I can go back if I have to?
Thanks a million!!!!!!
Ok, here you go:
1) It is in a partition of its own, not the same one as extended ROM. And most of it is visible as your windows directory.
2) No such thing. Rom files can be NBF or BIN (also some other NB extensions). If you have an exe file, it is the setup app that has the ROM image stashed some ware (resource maybe). The exe does the work, but it is not a ROM image.
3) As you understand from answer 2 you can't. You can backup your image to SD, but it is somewhat complex and depends on the device and version of bootloader. There are instructions in the WiKi.
Warning!
If you are new to ROM changing you should only use official update and head the warnings about loosing all data, having power connected and battery full during update and not being able to downgrade (without some hacked software).
Also using custom ROM will void your warranty.
Feeling a noob to ask, even after flashing almost daily a new rom.
I want to clean some files from my sdcard. I backed up some importand files like Nand backup files from the folder clockworkmod.
I would like to know if it's save to remove the file "update.zip" or should i leave it or put it back after a reformat of my sdcard?
(If it's important to know. . . I'm running clockworkmod recovery 3.1.0.1 with s-off.)
Nemesco said:
Feeling a noob to ask, even after flashing almost daily a new rom.
I want to clean some files from my sdcard. I backed up some importand files like Nand backup files from the folder clockworkmod.
I would like to know if it's save to remove the file "update.zip" or should i leave it or put it back after a reformat of my sdcard?
(If it's important to know. . . I'm running clockworkmod recovery 3.1.0.1 with s-off.)
Click to expand...
Click to collapse
I would copy it to your PC for safe keeping just in case.
You shouldn't need it. Once you flash a zip, the contents are unzipped and written somewhere e.g. /system for a rom. The zip is just the storage method.
Also, you downloaded it from somewhere, right? Just download again!
Still you never know. Unless you have zero space in your hard drive it can't do any harm!
I didn't download it, I think it comes from using the app clockworkmod (does someone know this?).
But you're right, It's a small file and I can put it back on the sdcard after I reformatted it.
Nemesco said:
I didn't download it, I think it comes from using the app clockworkmod (does someone know this?).
But you're right, It's a small file and I can put it back on the sdcard after I reformatted it.
Click to expand...
Click to collapse
Is this the file?
/sdcard/clockworkmod/recovery-update.zip
I think that recovery would rebuild this folder, including the zip, after a complete reformat if your sd, same as the other folders would get rebuilt by the rom.
I'm not 100% on that though, hope someone will confirm!
No, it's /sdcard/update.zip (but it's the same size as recovery-update.zip)
Oh, something complete offtopic, I see a lot of abbreviations here on the forum but I don't know what FC means.
Can someone tell me what it means?
FC=Force Close. Good you don't know it, means you don't get them?
I think your update.zip is seperate from recovery then. First advice still stands, you shouldn't need it but no harm to keep the copy. I guess you could unzip on PC to see what's in there?!
hi,
i think you are using rom manager, it should comes from this app.
if right, you should have got a folder ingherited from RM (rom manager) with another update.zip (but to be confirmed since long time a don't use anymore RM)
atm (at the moment)
Thnx for your reply's. It was usefull for me.
Can I close this topic myself and mark it as solved?
yes you can marked as solved by edit the title but yiu can t close this post
Is it possible to install Android on Kaiser without SD? Has anyone investigated bundling the /system partition with tinboot so the whole thing is installed with a single KAISIMG?
I ask because I have one Kaiser whose SD reader is broken. If I could install more than a kernel, I could try risky changes to fix the NAND driver. If I brick the phone or kill its flash, it's no big loss.
No, you can't do it now, maybe i can suggest you to look after a method do dump the nand after install and use it as kaiser image
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
PoXFreak said:
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
Click to expand...
Click to collapse
I don't think thats l1q1d idea... perhaps a complete nand dump, and reflash it to another kaiser.
The kernel and partitions must be configures before the dump...
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
This is possible, in fact there was a time where an empty img file was being incorporated into the NBH where on a windows NBH the system files would normally be copied. A windows NBH consists of a number of parts, I can't remember what they are all called right now, but they can all be merged using NBHmerge. I can't give you specific instructions but there's no reason why it can't be done, not sure it'll be much fun though!
n2rjt said:
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
Click to expand...
Click to collapse
pre-beta that you're testing on HTC What ??
daedric said:
pre-beta that you're testing on HTC What ??
Click to expand...
Click to collapse
HTC Wizard. I have two of them, which I have named Radagast and Gandalf. It's my all-time favorite smartphone, although it is obviously even more obsolete than the Kaiser. I use one of them as my primary phone whenever Android is giving me fits. Right now I'm testing H3r7 beta 2 preview where the cook has adeptly squeezed WM6.5 into a tiny, fast, stable package.
If I knew that I wouldn't have given my Wizard away...
I thought Ham3r was finished when he hit 6.1 but I stand corrected...pfft.
help androidinstall.tgz
please share for me : file androidinstall.tgz 2.1 or 2.2 but must run wifi and 3G.
Send for me by: [email protected] thanks i come from VietNam
I think with the proper memory map Android could be installed via FrankenKaiser or something of that sort. Something that addresses the NAND directly through OEMSBL, bypassing the need for a HardSPL. Of course the phone would have to be CID unlocked to do this, but I think it's possible to install via CustomRUU if the mapping was done beforehand.
I have read somewhere that NAND marked as bad in the map still gets "written" to, meaning whatever is supposed to go there is put there and never read. Once unmarked the written info comes back, but that requires a full format anyway.
I say very possible...
I have stopped trying to do this, but wanted to record my latest thoughts in case someone reads this in the future.
I think the best way to install Android on a Kaiser that can't read its sdcard is to edit the initrd then use recovery mode:
* install adbd so it gets started in recovery mode
* allow the menu when sdcard is not installed
* change scripts to look for /data/andboot
* change recovery mode to mount /data partition to usb
Then, of course, you boot the kernel, use the menu, enter recovery mode, transfer androidinstall.tgz and androidupdate.tgz to /data/andboot, then install system, install updates, clear data, and run. If something doesn't work, adb shell or adb push can help.
I think it's too much work to be worth it on this old phone.
SO basically im trying something out and i need to add a partition to my android device thats about 100mb big. Is this possible? the Sdcard wont work as a partition
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
CNexus said:
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
Click to expand...
Click to collapse
will modifying that file be able create an extra 100mb partition so when i hook it into my comp two partitions show up?
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
CNexus said:
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
Click to expand...
Click to collapse
Alright thanks im looking into it know do you know how to dump one from a phone? as google is not bringing up anything besides info on what it is
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
CNexus said:
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
Click to expand...
Click to collapse
its a 16gb lph 710 ill look into heimdall thanks
What's your current bootloader version? If not known, run
Code:
getprop ro.bootloader
In a shell on your device/terminal emulator app
And then post the last three alphanumeric characters
Sorry I realized the bios of a comp doesn't recognize the android phone as a peripheral or a mountable boot device which ruins my plans as of now I'm going to try to find a way to at least get the bios to pickup the SDcard if I can I'm doubtful though
Trying to upgrade to MM (and then use LeeDroid). Currently on LP 5.1, with LeeDroid.
M9 is:
S-Off
CID is 11111111
MID is 0PJA11000
Following this thread.....http://forum.xda-developers.com/one-m9/general/guide-t3301504
Along with the one from Sneakyghost......http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Running the fastboot flash zip Firmware_xx.zip command.....I get an MID error. SneakyGhost's file is 0PJA10000. I get the error code 10. So....reading his Post #5 to recover from this, I unzip his file, change the android-info.txt file to match my MID on my M9, zip it all back up....and retry.
This is what I get:
fastboot flash zip M9_3.35.401.12_FullStock_wipe.zip
target reported max download size of 800000000 bytes
sending 'zip' (135654 KB)...
OKAY [ 7.890s]
writing 'zip'...
(bootloader) HOSD CL#671758
(bootloader) ERR zip file count(70) is inavlid
(bootloader) ERR zip header or handle is invalid
(bootloader) ERR zip header or handle is invalid
(bootloader) ERR can not seek to 1th image offset -1
(bootloader) [email protected]
FAILED (remote: 12 RU_ZIP_ERROR )
finished. total time: 9.912s
Any help/ideas on how to get past this? Did I miss something?
Thanks in advance!
You zipped it back up incorrectly. The better approach is to use an app that allows you to edit the file inside the zip.
OK. Is there a recommendation of an app to do this? MAC based (preferably, as that's 99% of my use), but I do have an older Windows 7 laptop.
A couple of Google searches are really all over the place on the topic of editing files inside a zip file. Many say it can't reliably be done, some say it still changes the ZIP filesize/other info (which would put me back to this issue).
Thanks!
sttw1fa said:
OK. Is there a recommendation of an app to do this? MAC based (preferably, as that's 99% of my use), but I do have an older Windows 7 laptop.
Click to expand...
Click to collapse
I use B1 Free Archiver and I've used it to edit android-info.txt files inside firmware zips in the past. The OSX archive program does not work for flashable zips as it adds in extraneous files and does not archive it correctly for this purpose.
I suppose it's possible to mess up editing files inside a zip if you use the wrong program, and it would indeed break the signature for a signed firmware file. That may be what people are referring to.
Thanks for the info on B1 Free Archiver....installed on my MAC, and changed the android-info.txt file pretty effortlessly inside the zip file.
Then went through the install/upgrade of MM, new recovery, and then finally LeeDroid r85.
Unfortunately....most of the app back up files seem to be useless (or gone), as the path to the external SD card got renamed during the entire process (which I don't understand, as I thought the SD card wouldn't be touched). Several of the apps don't allow changing the SD Card backup path, and several that did...the backups (folders) aren't there anymore. I did verify the various app backups using ES File Explorer Pro before starting (and after). Basically was a mess for my most used apps, but all other data (music/images/videos) went untouched as far as I can tell.
So...went back to a TWRP Nandroid backup from earlier today. Will redo all the important app backups elsewhere.....and try again.
MM changed paths and permissions to the sdcard, and I had similar issues with some apps when I upgraded. But you're on MM firmware now, so the rest is gravy.
sttw1fa said:
Thanks for the info on B1 Free Archiver....installed on my MAC, and changed the android-info.txt file pretty effortlessly inside the zip file.
Then went through the install/upgrade of MM, new recovery, and then finally LeeDroid r85.
Unfortunately....most of the app back up files seem to be useless (or gone), as the path to the external SD card got renamed during the entire process (which I don't understand, as I thought the SD card wouldn't be touched). Several of the apps don't allow changing the SD Card backup path, and several that did...the backups (folders) aren't there anymore. I did verify the various app backups using ES File Explorer Pro before starting (and after). Basically was a mess for my most used apps, but all other data (music/images/videos) went untouched as far as I can tell.
So...went back to a TWRP Nandroid backup from earlier today. Will redo all the important app backups elsewhere.....and try again.
Click to expand...
Click to collapse
I see you got your main issue resolved. No need to answer your PM then I reckon.
I explicitly mention in my posts on page one that you need to use the right archiving program or at least know how to set up your preferred archiver with the required parameters so the zip would flash. Although I do not have any clue about Mac's...
Regarding the SDCard name: you better find a decent solution for your apps because each Marshmallow ROM reflash will create a new unique name for the SDcard. It will happen all over again next time you clean flash. I personally use Titanium Backup to back up a few important apps from which I know that they will have no issues with restore, and made it a principle I follow obsessively, to clean flash and clean setup - meaning I go through every single of my 200 something apps and set it up again manually except for those with important databases with no cloud backup - like my drive log book for instance.
Yeah....MACs sometimes complicate things. I'd never needed to edit a file in a zip file, hence the start of the issue, which was 'learning something new'.
And...I'll re-install Titanium Backup for going forward with MM. I had basically abandoned it. It caused a big pain one time when using on my M8 back when upgrading back in the 4.x versions. I then switched to just managing phone and app backups via the SD card manually (it never got touched for me between 4.x and 5.x, so it worked OK), and then some apps had backup online options (dropbox, etc.). Always worked well til hitting MM. I'm only in the 140 app range....and only about 10-12 that really need heavy duty backup options like TB.
Up and running with MM and LD r85 since this morning.
Thanks all!