Booting and Image from SD - myTouch 3G, Magic Android Development

Hi. I was wondering whether its possible to modify the SPL (I guess that's the part that will need to be modified first) in order to allow booting a full system from the SD card.
This would allow testing images without having to flash them to the device NAND.
The advantages would be that the process would be both faster (no NAND flashing) and probably safer (you can always get a new SD card).

Related

Is there any way to update my Himalaya Using SD Card ???!!!

Hi
Is there any way to update my Himalaya Using SD Card ???!!!
like Qtek 1010 opening device in bootloader then inserting the card that contain the rom
is there any way to do the same thing to update Himalaya to 2003se or 2005 ??!!!
Thanks for your help
my question is, why you didn't use your PC ?
My answer is
my phone socket has damaged , i can't connect to to pc just i can charge
iam using blue-tooth to sync between computer an my XDA II
Well, yes and no, I think.....
MohamedYousri said:
Hi
Is there any way to update my Himalaya Using SD Card ???!!!
like Qtek 1010 opening device in bootloader then inserting the card that contain the rom
is there any way to do the same thing to update Himalaya to 2003se or 2005 ??!!!
Thanks for your help
Click to expand...
Click to collapse
......there is a way to flash the XDA system rom from an SD card, in fact it is
quite easy IF you have already flashed the ROM via USB in the usual way and
then use the bootloader to dump it to a spare SD card. In fact I tested it and
it works perfectly. Even flashed my XDAII with 3.5b.40CS ROM from SD card
in under 5 minutes and with no connection to PC of course. In fact I took a
silly risk and did it unpowered too (just don't tell anyone - ok)
This means in theory I could dump my WM5 ROM to SD card. Copy the raw
data to a file and give you instructions to make your own SD ROM image to
flash your XDA via the SD socket. but.....
Unfortunately I think there is another catch. I only have one XDA so I can't
test this, but I believe when you dump a system ROM using the "d2s" bootloader
command it sticks a 411 byte header to the SD card. This appears to contain
system/SD card specific info / crc data which is generated by the bootloader
program. I assume this is to stop someone accidently (or purposely) loading
a system ROM from one XDA to another. I'm thinking your XDA would reject
the SD card as invalid (although I don't know for sure)
but...I also think there is a way round this. If you can create an SD dump of
the ROM that is already in your XDA (which you should do anyway as a
precaution) then you could strip the 411 byte header from your SD card image
and write it over the top of the header in the image I give you. Then this
should flash ok (it might fail the checksum at the end, but should flash ok)
BUT (and this is the real problem) If your serial / USB link on the XDA is damaged
I can't think of a way to instruct the bootloader to dump your header + ROM
image to the SD card. We've sort of come full circle. You need to update ROM
via SD card because your USB connection is broken, but you can't get a
SD dump header because you need the USB connection.
The only ways round this would be for someone to dissamble the bootloader code
and maybe write a PPC app to create a valid header record.
Anybody got any ideas?
S_F
sawyer_family said:
BUT (and this is the real problem) If your serial / USB link on the XDA is damaged
I can't think of a way to instruct the bootloader to dump your header + ROM
image to the SD card. We've sort of come full circle. You need to update ROM
via SD card because your USB connection is broken, but you can't get a
SD dump header because you need the USB connection.
The only ways round this would be for someone to dissamble the bootloader code
and maybe write a PPC app to create a valid header record.
Anybody got any ideas?
S_F
Click to expand...
Click to collapse
This is exactly my problem my serial / USB link on the XDA is damaged
Waiting for help
thanks for your help
sawyer_family said:
......there is a way to flash the XDA system rom from an SD card, in fact it is
quite easy IF you have already flashed the ROM via USB in the usual way and
then use the bootloader to dump it to a spare SD card. In fact I tested it and
it works perfectly. Even flashed my XDAII with 3.5b.40CS ROM from SD card
in under 5 minutes and with no connection to PC of course. In fact I took a
silly risk and did it unpowered too (just don't tell anyone - ok)
This means in theory I could dump my WM5 ROM to SD card. Copy the raw
data to a file and give you instructions to make your own SD ROM image to
flash your XDA via the SD socket. but.....
Unfortunately I think there is another catch. I only have one XDA so I can't
test this, but I believe when you dump a system ROM using the "d2s" bootloader
command it sticks a 411 byte header to the SD card. This appears to contain
system/SD card specific info / crc data which is generated by the bootloader
program. I assume this is to stop someone accidently (or purposely) loading
a system ROM from one XDA to another. I'm thinking your XDA would reject
the SD card as invalid (although I don't know for sure)
but...I also think there is a way round this. If you can create an SD dump of
the ROM that is already in your XDA (which you should do anyway as a
precaution) then you could strip the 411 byte header from your SD card image
and write it over the top of the header in the image I give you. Then this
should flash ok (it might fail the checksum at the end, but should flash ok)
BUT (and this is the real problem) If your serial / USB link on the XDA is damaged
I can't think of a way to instruct the bootloader to dump your header + ROM
image to the SD card. We've sort of come full circle. You need to update ROM
via SD card because your USB connection is broken, but you can't get a
SD dump header because you need the USB connection.
The only ways round this would be for someone to dissamble the bootloader code
and maybe write a PPC app to create a valid header record.
Anybody got any ideas?
S_F
Click to expand...
Click to collapse
I know this Idea. Once, I have tried to back up my WM2003 sistem to my SD card use d2s command using mtty software. Actually in theory I succeed to make back up image in SD Card and if there is something happen, I just flash by SD card. But I have never tried this step, because I succeed to install WM5.
In that time I make image system from my PDA. But in this case, MohamedYousri need such as thing system, not from PDA but from PC. But I don't know how to make image files from PC. If there is somebody can tell how to make it, I agree with you. I think it is possible to flash from SD card.
Another way MohamedYousri should make image from another PDA (with WM5 sistem) and put it in his device
selangkahlagi said:
Another way MohamedYousri should make image from another PDA (with WM5 sistem) and put it in his device
Click to expand...
Click to collapse
Do you mean to upgrade XDAII with WM05 and then make an SD image and flash my XDAII ??
Do you think that will work ??!!
MohamedYousri said:
Do you mean to upgrade XDAII with WM05 and then make an SD image and flash my XDAII ??
Do you think that will work ??!!
Click to expand...
Click to collapse
If some body have XDA II with WM5, and then you back up /make an image in SD card. And with that card flash your XDA II, I think in theory it should work. but I never try this way, because my device still work well
There is a development tool by SBP called 'clone'... It will clone identical devices but it is commercial and expensive... but SBP provide a trial version:
http://www.spbsoftwarehouse.com/products/clone/?en
I hope this help........
Features
* One device is configured, the rest are subject to clone
* The average device cloning time is about 3 minutes.
* Self-extracting and self-executing image file on an SD card
* Assigned location of the target clone image files
* Providing individual names and IP addresses for clones.
sawyer_family said:
......there is a way to flash the XDA system rom from an SD card, in fact it is
quite easy IF you have already flashed the ROM via USB in the usual way and
then use the bootloader to dump it to a spare SD card. In fact I tested it and
it works perfectly. Even flashed my XDAII with 3.5b.40CS ROM from SD card
in under 5 minutes and with no connection to PC of course. In fact I took a
silly risk and did it unpowered too (just don't tell anyone - ok)
This means in theory I could dump my WM5 ROM to SD card. Copy the raw
data to a file and give you instructions to make your own SD ROM image to
flash your XDA via the SD socket. but.....
S_F
Click to expand...
Click to collapse
Would you please give step by step guide how did you dump to the SD card, and how did flash XDAii from SD card?
Thank you
llbasha said:
There is a development tool by SBP called 'clone'...
Click to expand...
Click to collapse
That clones everything from the location of your first clicks on the Welcome screen up to everything you installed, your data, your settings, your registry tweaks, your skins, you can even select if you want to restore the date and time of the clone or leave the new device's time intact.
But it does not clone the OS or anything in ROM.
After some bad experiences both with Activesync backup and with another commercial backup, I only trust Clone. And next week I'm going to use it to transfer my software and settings to another Himalaya. Disadvantage: I'll have to remove all my personal files (contacts, tasks...) from that other device.
Hello,
So is there any way, how to flash my XDA2 via SD card ? My data connector is broken, so I completely cannot use computer/USB connection. I mean some program, which transfers *.nbf files to SD card in form, that is understandable for XDA2's bootloader etc. Or if some developer like helmi, buzz,... can convert last WM6 ROMs to SD-image form.
Thanks
not that i know of

[Q] How to copy ext partition on sd

I am about to get a bigger sd card and want to know is there a way to copy my old ext partition from the old sd to the new one?
im not exactly sure but this is what i would try:
1. in recovery, make a nand+ext backup (lets hope you have amonra. i believe you can also do this in clockworkmod but i dont how)
2. turn off your phone, put in your new sdcard, boot into recovery, and partition it to your liking (preferably the same size as your old partition)
3. copy (not cut) all data from your old sdcard to your new sdcard (this means that your newly created backup from step 1 should now be on the new sdcard). this can be done by doing this:
put your old sdcard back into your phone
plug your phone into the computer
copy everything on your sdcard onto the computer
now put your new sdcard into the phone
copy everything from the computer back onto the phone
4. boot into recovery and restore your backup
im not sure if this will work. you are doing this at your own risk (but i dont think anything should go wrong. in the event that anything does go wrong, just put your old sdcard back into your phone.)
I'll second sweet n sour. Amon Ra will allow you to back up sd ext
Sent by Salvaged Supersonic!
Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] Missing pb99diag and pb99img

Let's start with the history.
- Bought a HTC Desire.
- Used unrevoked, clockwordmod to flash Cyanogenmod (made backup of HTC Froyo/Sense installation).
- Used same tool to flash back the backup.
Now I want to install a new ROM with A2SD+. Used GParted Live CD to shrink the FAT32 partition (8 to 7GB) and created an EXT3 partion after the FAT32 one.
My problem: when booting into recovery by pressing volume down and the power button, the loader (hboot ??) is trying to find several pb99img and pb99diag files in the root of the SD card. Some posts talk about partitioning going wrong but I might have deleted the files from the card ("hey whats that file, don't know what it does, let's remove it).
Do I really need those files or should I wait 5 minutes (why does it even need that long to realize the files aren't present). If I need them, can I get them somewhere? Or just ignore it, continue to Clockwordmod Recovery and flash a new ROM from a ZIP file on the SD card?

[Q] Can anyone boot any Smartphone from the external SD Card?

These are my current problems:
1) I lost my Galaxy S3 overboard!
2) I had not made a backup because I detest Kies. Kies crippled my PC performance and hid my backed up (*.sbu) files from the PC file system.
3) I want to avoid the use of all proprietary software on my PC in order to manage my backups (including OS backups).
Proposed solution:
1) Buy a replacement Smartphone (a Galaxy S4?) which has an external SD Card slot.
2) Flash a custom bootloader with complete Backup / Restore functionality.
3) Backup Function: A complete phone Backup, (i.e. OS, Apps, Data and MyFiles), is made to a new folder in the root of the external SD Card. I can give this folder any name, e.g. “OriginalPhone” or “2013-04-21” etc.
4) A single file in the root of the external SD Card called “current.txt” contains a single folder name - that of the default folder for booting, e.g. “2013-04-21”.
5) Normal Booting uses the files originating from the folder specified in “current.txt”.
6) If there is no change detected in the boot files of the “current” boot folder, the phone boots “normally” from the OS copy in NAND flash if this results in a quicker boot than booting directly from the external SD card.
7) Booting with a combination of keys enables the Bootloader Restore function which allows the user to choose the boot folder to restore from.
8) I can use my PC file manager to manage all OS and data files for archive, backup and restore purposes. I will not need to use any proprietary software!
9) If I lose my phone again, I simply buy the same model as a replacement, change the bootloader, copy my most recent backup folder from my PC to a new SD card, insert the new SD card into the phone, and restore my "complete phone".
Can anyone help me to create a custom bootloader with complete Backup / Restore functionality that can boot any Smartphone from the external SD Card? Thanks in advance!
how to boot my smartphone from external SD card
Menumaster1 said:
These are my current problems:
Hello
It is the second time, I buy a Smartphone and after the garanty time (1 month after it due to software error my smartphone doesn't work anymore.)
I have bougth a honor 7 premium. During installation process may be due to obsolesence programmed or battery low during loading, it stucked I think in boatloader /EMUI (emui install failed error). the honor image stays and also after wipe cash partition and wipe to factory reset, it doesn't start.
I would like to start and if possible flash a new android SW on the honor 7 to be able to connect to it.
Actually I can not connect it with the PC. It is not visible.
Is it possible? Do you have any boot SW I can put on SD card. It would be very helpful.
My wife needs his mobile before leaving for 3 weeks on monday.
Feedback would be very greatfull
thanks in advance
Click to expand...
Click to collapse

Install OS with full wipe over magisk and modified boot

If I want to run the August os with full wipe, is there any reason to unroot or re-install stock boot before running the .bat? I want a complete return to stock and new set-up. Before Pixel/Pie, this was never an issue but wanted to be sure
Nope, when flashing the stock factory image with the "flash-all.bat" it automatically wipes everything (even the internal storage), and then it flashes the all stock system.
No need to do it manually since it does that itself.
Tenn3r is spot on.
Just to reinforce what he said however, you will loose ALL data on the "SD card" if you run the full install. Make sure you copy anything you want to keep to another device prior to wiping. I'm use to running phones with a physical SD card and you could wipe the main memory/drive without effecting the SD card. But since the Pixels don't have a physical SD card, that space is on the main memory/drive and it does get wiped.
Thank you both. I'm aware of what a full wipe does but the warnings are always applicable. This dual slot thing on Pie is new for me (owned most Nexus devices from GNex on) as is Magisk.
I've been having issues that I want to make sure do not relate to "stuff" I have done or installed. Safe Mode hasn't provided me with any clues so waited for this Aug update to wipe.

Categories

Resources