Related
Hi, this is my first post in this forum. I tried to be a good newbie and read quite many threads before posting. And there are already great HOW-TOs available, but I have some more detailed questions for which I could not find my answer in this forum yet.
So here is what I want to do: Backup the full device (To be able to restore it in to the state it was in once it came from the operator)
here is what I so far did:
Step 1:
Application Unlock the Device
Step2:
Back-up personal data with PPCPimBackupV2.8
Writing down device information (such as Rom version, Radio, Device ID…)
Backup most of the registry (using extract function in MobileRegistryEditor)
Rom-Version: 1.37.774.3 SVE
Radioversion: 1.00.25.03
Protokollversion: 52.26a.25.09H
Device SPL: SPL-1.37.0000
Step 3:
Back-up ROM
With itsutils and pdocread.exe.
Now 4 .raw files: part00, part01, part02, part03
Step 3:
BackupSPL:
A. Used itsutils with
Pmemdump.exe 0xa8000000 524288 SPLdumped.nb
B. Also downloaded the official SPL-1.37 (just to make sure / google)
-----------------------------------------------------------
I would like to back-up everything needed to return it to the original state before fooling around with ROMs.
So my question is how to I backup the:
1. Is there a way to just read in the complet memory of the device (e.g in a raw file, that covers all from bootloader, OS, RADIO etc [so a full image of the device] sorry for asking / might be quite stupid question)
2. CID (how to find out at what memory position this is stored)
3. RADIO ROM (is this already included in the raw files from step 2?)
Steps after that to flash the new ROM so far seem rather clear to me as they are in detailed descriped in this forum. Will be my first Rom flashing and decided to stick with a official ROM for now. The main purpose for flashing the device is to change from Swedish to English and to get some bug fixes for the device.
So thank you guys for the help already provided.
Would be great if you can give me a hint on this.
ThoTho,
Perfectliy explained your interest, its' just the same thing that iv'e been trying to do since I started to see all these ROMs availables.
What I've found in another forum (only that this in Spanish, I hope you do not bother ) is that this could be done with SPB, so I will try to do so to check if it is that easy.
Hopefully we'll get some help.
Gus66
Hi,
as I've seen on the SPB homepage, the backup tool backups all the data, but I would like to backup the factory rom because I use czech language on my device and I didnt see original czech rom.
Or should I hard reset the device, make and then make the backup with SPB?
The created exe is than a genuine rom file or just some program file with the contacts/mail/etc backups that can only be run in WM environment?
you can get your manufacturers ROM either from their website or direct from HTC
i know i can get vodafones ROM in a nice application
warning: this tool is for flashaholics. The ones who know all risks of flashing roms and like to live in the fast lane
Note for HD2-users: Although this version can be also used for the HD2, you may like this version more (the HD2 version doesn't require that you provide a "preflash" .nbh file - see further).
- Description:
FlashaholicRUU (FRUU) is a customized version of the HTC Rom Update utility that will simplify the rom update proces by:
1. performing a task29 before updating a rom
2. allowing the user to navigate through the dialog windows without having to check checkboxes (s)he has seen a gazillion times before.
3. allowing the user to use only the keyboard to go through the dialog boxes (enter -> next window, esc -> quit fruu)
- Prerequisite
Task 29 is performed by flashing a .nbh file before the (custom) rom file. Because the tool is meant to be general applicable for all devices you need to provide this "pre flashable" .nbh file yourself. In principle you can use any .nbh file for this. To speed up this first step though it is recommended to use a radio for your own device or better yet, a .nbh file containing only the splashscreen for your device. Rename this file (radio, splashscreen ) preflash.nbh and put it in a directory together with your custom rom file (may have any name as long as it has an .nbh extension) and the general_FlashaholicRUU.exe. Make sure there aren't any other files in the directory.
For the rest follow the instructions described in the section Usage
- Usage:
This program will take you through the steps of performing a Task29 (formatting your roms storage memory) and then flashing a new rom. It is not advised to use this if you are totally new to flashing roms as if it is done incorrectly you will end up with no rom on your phone and a permanent look of terror on your face
This is not for noobs!!
1. Make sure your phone is booted up
2. Sync your pc and phone
3. (you may skip this step if you've read the prerequisite) Copy the general_FlashaholicRUU.exe file to a new folder with JUST the roms .nbh file present and a rom you want to flash before you flash your rom. Rename this last rom file, the one you want to flash first, preflash.nbh
4. Run the general_FlashaholicRUU.exe and follow the instructions in the program
5. Click on the "perform task29" button to format your roms memory
6. As soon as the percentage bar reaches 100% hold your "volume down" button and continue holding until the phone reboots and enters the bootloader screen
NOTE: If you get a white screen with "hTC" in the middle then you need to take out your battery and enter bootloader mode manually before continuing (take battery out and put it back in, then hold the volume down button and briefly press the power button. Keep holding the volume down button until the bootloader screen appears).
7. When the white box in the bottom of the bootloader screen says "USB" then click on "Flash Rom" in the Flashaholic program
8. Follow the onscreen instructions and lastly click on "Flash" to flash the rom to your phone
9. You will now have a percentage bar on your phone and your new rom is being flashed
10. Once your Rom has flashed your phone will reboot and you can go through the setup screens.
Run your new Rom for a few hours, search for another one and start again with step 1 (if you want to become a real senior flashaholic)
NOTE: There is no need to perform a Hard Reset after flashing the Rom using this program as the Task29 performs a much more thorough job.
--------------
When you want to flash a rom without performing task 29 (for example when you want to flash a new radio) just hit <ESC> on the first screen of step 1. This will take you right to step 2 in which you can flash your rom
Click to expand...
Click to collapse
(Thanks to mskip for writing this brief but comprehensive manual)
- Video:
Video of the app on a computer of a fellow flashaholic: http://www.youtube.com/watch?v=hn3pGbW-vag. Thank you claub. Keep on flashin'
- Note to chefs:
You can pack FRUU with your Roms. You can even customize FRUU for your Rom series. For example you can use your own images, text, info etc. I have written some general instructions about customizing the RUU here. (Notice that in FRUU ModelID.fig is used for the first task29 step and RUU.fig is used for the second step. The dialogs for the first step are part of RUUResource.dll. Dialogs for the second step you will find in CustomizedRomResource.dll. Instead of the setup.bat and setup.vbs I mentioned in the aforementioned post I used the files run.bat and run.vbs. For exra information you can PM me)
- Donations:
Thank you!
Thanks to: doloop (for his non-mtty task 29 tool)
---------
Note: this tool should work for any (newer) htc device. Nevertheless make sure that your bootloader will support task 29 and that experiments with mtty task 29 has positive results for your device (look at the development section for your device forum)
Devices on which this tool is reported to work:
* Leo (HD2)
* Rhodium (Touch Pro 2, Tilt 2)
* Topaz (Diamond 2, Pure)
* Raphael (Touch Pro, Fuze)
* Diamond
(please pm me or report your device in this thread if the tool worked also for your device and that device is not in this list yet)
Click to expand...
Click to collapse
Happy flashing
appelflap said:
Rename the radio rom file to radio.nhb[/COLOR]
Click to expand...
Click to collapse
Not Radio.nbh? Isnt it typo?
Petulinek said:
Not Radio.nbh? Isnt it typo?
Click to expand...
Click to collapse
Yes, it is a typo. Should be radio.nbh
sure need to test.
what diff between task 32, task 29 and task 28
im on blackstone, so that using only task 29
core7x said:
sure need to test.
what diff between task 32, task 29 and task 28
im on blackstone, so that using only task 29
Click to expand...
Click to collapse
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Task 29 formats the device.
It should work on the blackstone. From what I've read the bootloader supports those commands. As far as I know those commands are also supported by the bootloader of other newer HTC devices as well.
Make sure you have HSPL installed. (or how it is called for your platform)
-----
(BTW for anyone who like to experiment with the above util, you can extract the exe and examine run.bat ...
If the RUU's in this package don't work use the RUU for your device. Open it with a hexeditor. search for "task" and change the digits "28" behind it to "29" and save it as "Task29.exe". Do the same again, but now change "28" to "32" and save it as RomUpdateUtil.exe. )
appelflap said:
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Task 29 formats the device.
It should work on the blackstone. From what I've read the bootloader supports those commands. As far as I know those commands are also supported by the bootloader of other newer HTC devices as well.
Make sure you have HSPL installed. (or how it is called for your platform)
-----
(BTW for anyone who like to experiment with the above util, you can extract the exe and examine run.bat ...
If the RUU's in this package don't work use the RUU for your device. Open it with a hexeditor. search for "task" and change the digits "28" behind it to "29" and save it as "Task29.exe". Do the same again, but now change "28" to "32" and save it as RomUpdateUtil.exe. )
Click to expand...
Click to collapse
clear, will do that
core7x said:
clear, will do that
Click to expand...
Click to collapse
You naughty boy... naughty naughty naughty
appelflap said:
You naughty boy... naughty naughty naughty
Click to expand...
Click to collapse
joke only, by the way. im flasholic rom person.
core7x said:
joke only, by the way. im flasholic rom person.
Click to expand...
Click to collapse
I kinda hoped that you noticed the ironic undertone of my reply
appelflap said:
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Click to expand...
Click to collapse
OK, this sounds like a bad idea taken even further.
Hard reset reloads nvram and ram from flash. Radio and bootscreen are in flash, so a hard reset will do nothing to them.
Unless HD2 is different from all other HTC devices (I seriously doubt it, but do not know), stock ruu should flash radio and bootscreens found in custom roms just fine. This makes sense, of course, because carriers don't release different ruu's just because radio update or bootsplash are included in .nbh.
As to erasing flash before flashing....what a waste of time. I can imagine almost no case where this would be beneficial, and it certainly is wasteful in 99.99% of cases. Why would you want to degrade memory 2x as fast (or more) on a routine basis? Flashing RARELY (like never) fails to overwrite, and when it does, it won't help you to have 0's where it fails.
gguruusa said:
OK, this sounds like a bad idea taken even further.
Hard reset reloads nvram and ram from flash. Radio and bootscreen are in flash, so a hard reset will do nothing to them.
Unless HD2 is different from all other HTC devices (I seriously doubt it, but do not know), stock ruu should flash radio and bootscreens found in custom roms just fine. This makes sense, of course, because carriers don't release different ruu's just because radio update or bootsplash are included in .nbh.
Click to expand...
Click to collapse
Not when you just want to update your radio without updating or resetting the os
As to erasing flash before flashing....what a waste of time. I can imagine almost no case where this would be beneficial, and it certainly is wasteful in 99.99% of cases. Why would you want to degrade memory 2x as fast (or more) on a routine basis? Flashing RARELY (like never) fails to overwrite, and when it does, it won't help you to have 0's where it fails.
Click to expand...
Click to collapse
If i don't do a format before flashing a new rom - time has shown me this again and again - i get some serious battery drain problems. Of couse I like to pass this step... but..
and with respect to your other advice, this is a tool for flashaholics you know. I don't think flashaholics worry very much about the memory of a device they use for 1-2 years max.
appelflap said:
If i don't do a format before flashing a new rom - time has shown me this again and again - i get some serious battery drain problems. Of couse I like to pass this step... but..
Click to expand...
Click to collapse
I totally quote appelflap on this one.
I've never ever had battery drain problems with my flashes, the very first time I had those is when I attempted at flashing just a new radio radio keepin the rom and the data. Before thatm, flashing a new radio always was done when flashing a whole new rom, and after a task29 anyway.
After that "radio only" flash, hell ensued, as no matter the radios I changed thinking it was the radio version's fault, I was getting up to 16% drain overnight, and anyway not lower than 12%, against a normal 4-5%, with a standby drain of 20mA and more, against a normal of 4-7mA.
Next thing I did, task 29 + radio + rom and now I'm getting a whopping 3% drain overnight with my current rom combo, never went so low.
Tested this morning on a Raphael (ATT Fuze). Worked well. Task 29, radio flashed and ROM flashed. No problems at all.
Also tested with a Rhodium(ATT Tilt2). Same results.
Makes ROM flashing much faster. Now if there was just someway of not having to press the down volume button at the end of task 29 it would be perfect.
Good work Appelflap!!!
resqman said:
Tested this morning on a Raphael (ATT Fuze). Worked well. Task 29, radio flashed and ROM flashed. No problems at all.
Also tested with a Rhodium(ATT Tilt2). Same results.
Makes ROM flashing much faster. Now if there was just someway of not having to press the down volume button at the end of task 29 it would be perfect.
Good work Appelflap!!!
Click to expand...
Click to collapse
Thanks for testing! I think you helped a whole lot of flashaholics
BTW: If you have a original nbh file of the first bootscreen of your device(-s) you can use that instead of a radio ... For now, (till I uploaded a new version) just rename the bootscreen to radio.nbh and put it in the folder from where FlashaholicsRUU is run. Flashing a bootscreen in the first task 29 step is so much faster.
EDIT: about putting the device back in bootloader after the first task 29 step: if I only knew the bootloader command for it I could make it work without any problems. So if anybody has any idea, please let me know, I can hexedit the RUU to execute this command right after task 29 is performed.
appelflap said:
Thanks for testing! I think you helped a whole lot of flashaholics
BTW: If you have a original nbh file of the first bootscreen of your device(-s) you can use that instead of a radio ... For now, (till I uploaded a new version) just rename the bootscreen to radio.nbh and put it in the folder from where FlashaholicsRUU is run. Flashing a bootscreen in the first task 29 step is so much faster.
EDIT: about putting the device back in bootloader after the first task 29 step: if I only knew the bootloader command for it I could make it work without any problems. So if anybody has any idea, please let me know, I can hexedit the RUU to execute this command right after task 29 is performed.
Click to expand...
Click to collapse
Might it be possible to have it check for the existence of a radio.nbh file and if it doesn't exist skip that? I know it is handled by a batch file so there must be a way around it.
I flash a lot of ROMs but I rarely flash radio or bootscreen
resqman said:
Might it be possible to have it check for the existence of a radio.nbh file and if it doesn't exist skip that? I know it is handled by a batch file so there must be a way around it.
I flash a lot of ROMs but I rarely flash radio or bootscreen
Click to expand...
Click to collapse
The bootscreen or radio is needed in step 1. Task 29 is performed after flashing one of these. I will look for another solution when my HD2 is repaired.
appelflap said:
The bootscreen or radio is needed in step 1. Task 29 is performed after flashing one of these. I will look for another solution when my HD2 is repaired.
Click to expand...
Click to collapse
I have performed task29 on both Fuze and TP2 without having to flash a radio.
From the task29 section of the Rhodium forum:
Originally Posted by SacTilt
Some of you are making this too difficult. I've posted this before, as this is all that needs to be done. Task29 does not remove your radio or your splash screen. It only clears the ROM, therefore, all you need to do is run Task29 and then flash your ROM. This is how I do it from the PC.
Connect to PC via Active Sync/WMDC.
Execute Task 29.
When phone boots to "Touch Pro 2" screen (or whatever your splash screen happens to be), I hold down the volume down button while hitting the reset button.
Once I'm on the Bootloader screen, and it shows "USB", I flash the new ROM from the PC as I normally would.
When the phone vibrates, indicating the ROM upgrade is complete, I disconnect the phone from the computer.
Click to expand...
Click to collapse
Obviously I am missing something here
resqman said:
I have performed task29 on both Fuze and TP2 without having to flash a radio.
From the task29 section of the Rhodium forum:
Obviously I am missing something here
Click to expand...
Click to collapse
Thanks for your feedback! This was exactly the feedback that I was looking for.
The task29 tool from the rhodium forum flashes a ruu_signed.nbh that is specifically brewed for the rhodium. Indeed flashing this file doesn't touch anything.
Problem is I can't use such device specific files for a universal flashing tool. That's why I use radio nbh. So that I'm sure that the tool runs task 29 with a nbh file that is accepted by the device that is flashed.
The ruu_signed.nbh that task29 uses for the rhodium is 8.5 mb large. This will take more time to flash than a bootscreen (which is 0.7mb) but less than a radio (which is > 10 mb). May I suggest to use this tool with a bootscreen nbh it is soooo much faster.
Anyway when I get my device back I will look if I can brew a small nbh file that doesn't change the bootscreen or radio. I will target it to different devices and wrap it up for each specific device.
Again, thanks for your input.
-------------------------
Edit: I've attached the nbh file that is used by the rhodium task29 tool. Use this one instead of a radio. It doesn't alter you radio nor your bootscreen. Although the file is named radio.nbh it isn't a radio (the current test tool need that filename). You can try this for your rhodium.
appelflap said:
-------------------------
Edit: I've attached the nbh file that is used by the rhodium task29 tool. Use this one instead of a radio. It doesn't alter you radio nor your bootscreen. Although the file is named radio.nbh it isn't a radio (the current test tool need that filename). You can try this for your rhodium.
Click to expand...
Click to collapse
I understand now. It's not really a big deal for me to flash a radio. It would be a lot of work for you to have to create a signed ruu for every device.
Thanks
Thanks!!!!
Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
vuedesprit said:
Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
Congratulations. You win the "most questions asked in a single post" award.
Sent from my Desire HD using XDA App
That is a ridiculous amount of questions, and the thread is in completely the wrong area of the forum. I'm sure you'd find the answer to pretty much all your questions if you looked hard enough, but to answer the one about multi-touch. It is multi touch and all the games I've played from your example 'Gameloft' are multi-touch, so I don't know what you're smoking buddy, but ease off.
1. Inb4 "search".
2. Wrong forum.
3. No really, try searching. At least 30% of that is googleable.
Sent from my Desire HD using XDA App
Ok guys, thank you all for your replies, and yes I knew that a war and flames will go on here, but seriously if you think this is ridiculous or newbie or most dumb questions, do not turn the way of the thread or flame me, my intentions are to make this as a one small guide for most new androids functions, it's not a bad thing to do, in fact I will learn as much as other new users here, no one is asked to answer all those ridiculous questions, just answer what you know about, guys please take it seriously and easy, saying look harder will not help the thread, it may help me personaly, but be sure that I did a lot of search, and it will not hurt to put everything in one place, and as you can see, I answered most of the questions up to what I gathered, you can correct me about my answers, put your thoughts or not answer at all, but please be constructive here, and if you all think that i'm in the wrong forum, or asking too much, or asking ridiculous questions, please moderator feel free to do what you think is better for the forum.
Sorry guys for bothering you. Thank you for your response.
N.B.: just to be more accurate, I tried the prince of persia pre installed on the phone by the dealer, and it was not multi touch, so you cant walk and use any of the right actions at same time.
@vuedesprit: Good thread, and thanks for taking all the criticism from the more experienced users.
@all chimers chiming the "use search, wrong forum" tune: c'mon guys, there's at least 2 of us reading this thread going, it's about time all this information got consolidated into one place! The easier it is to find this information, the easier it would be for more of us to get engaged in the process and thus further development, enhancement and adoption.
While our "friendly" mod is doing his best to keep the forums clean, they're as fragmented as ever and from time-to-time, it becomes necessary to consolidate the information into a single thread. I'm sure most of you started some place too and remember the time not so long ago when it was difficult to find even the most basic info? I think by sharing your knowledge, you will gain a much better following and the platform will gain much better adoption.
My 2 cents worth anyways...I've had my DHD for 3 days now and I too am struggling to perform even the most basic tasks.
We really need a questions and answers sub forum
Fair enough, maybe my first comment was a bit rash, but I didn't mean to appear rude. I shall try to answer some questions here:
GENERAL.
1. From my own experience all games advertised as multitouch are exactly that. I don't know about the version of PoP that you have installed from carrier, but I do find that odd.
2. Hard reset is a little perverse with the new "fastboot" hibernation feature that HTC have implemented. You have to go to MENU>SETTINGS>APPLICATIONS and disable "fastboot" (this is where confusion may arise as this is not the bootloader fastboot that allows images to be flashed)!! Now when you hold down the power button and get the option to power off, you will properly power off the phone. Next if you hold "VOLUME DOWN" and "POWER" buttons you will reboot into HBoot, from here the VOLUME UP/DOWN keys navigate the menu and POWER selects menu options.
3. Not sure about this one.
4. Since the release of FROYO you can go to MENU>SETTINGS>APPLICATIONS>MANAGE APPLICATIONS then select any app and move to either SD or to phone memory.
5. The folders on the SD card are mostly generated by the phone when you first insert it. The user guide and HTC sync software are there to move onto your PC for safe keeping. If you insert a freshly formatted SD card, the phone will make fresh folders such as DCIM for pictures, etc...
SYSTEM INFO.
1. Baseband is radio software.
2. Kernel is the linux kernel that is running below Android, this can be updated separately from the main ROM, radio etc. HOWEVER CAUTION IS ADVISED AS CERTAIN KERNELS WILL NEED NEW MODULES FOR HARDWARE TO FUNCTION CORRECTLY as you will see from the wifi modules bundled with the OC kernels.
3. Build number pertains to HTC's internal software version classification (some are built specific for carriers) they are generally released via RUU (ROM Update Utility aimed at windows) or OTA (Over The Air update received on phone [again sometimes carrier specific]). Release keys pertains to the fact that the firmware has been signed by HTC (I think).
4. Software number, basically as above.
OTA ACE with Radio.
1. As Above.
2. ACE: internal HTC name for Desire HD (also reportedly known as "SPADE")
ROOT DESIRE HD ETC.
Most of what you have written is pretty much correct.
MORE THINGS TO KNOW ABOUT.
1. http://developer.android.com/guide/developing/tools/adb.html
2. http://www.busybox.net/about.html
3. http://android-dls.com/wiki/index.php?title=Fastboot
4. eMMC write basically means that you can write to the internal phone (normally protected) memory such as /SYSTEM, this is what S-OFF allows you to do whenever you want. However, the modules that allow the ENG HBoot image to be flashed are what really accomplish this in the first place so theoretically you could just run that module every time you wanted to write to /SYSTEM but that would become very tedious very quickly. I can't really explain further, as I don't have the knowledge.
5. EXT2 or EXT4 are filesystem structures just like FAT, FAT16, FAT32, NTFS, HFS+ etc, EXT4 is newer and more advanced than EXT2 and therefore is more efficient. (kinda general but you get the idea. NEWER=BETTER)
6. ROM manager, find this in the android market, it is free, you install it on your phone and with the addition of clockworkmod it gives you the ability of flashing ROMs etc. USE WITH CAUTION.
I hope that this answers or clarifies most of what you have asked or said, please feel free to cut and paste any of this info into your first post so that we can actually consolidate this.
P.S. I too am a complete android noob and this is my first android phone, I have picked this info up mainly from this forum so all credit for information goes to XDA-DEVELOPERS.COM and not me.
Cheers,
Dok
berek9999 said:
congratulations. You win the "most questions asked in a single post" award.
Sent from my desire hd using xda app
Click to expand...
Click to collapse
+1111111111^2
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
Click to expand...
Click to collapse
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
2-What are the buttons combinations for the different operations like hard reset & boot loader?
Click to expand...
Click to collapse
boot loader = turn phone off. then, volume down + power on.
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
Click to expand...
Click to collapse
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
Click to expand...
Click to collapse
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
Click to expand...
Click to collapse
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
Click to expand...
Click to collapse
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
How to root Desire HD install h-boot (S-Off) and Clockwork recovery?[/U][/B]
Click to expand...
Click to collapse
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
Click to expand...
Click to collapse
android application. eg, visionary+.
2-Hboot
Click to expand...
Click to collapse
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
Click to expand...
Click to collapse
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
Click to expand...
Click to collapse
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
Click to expand...
Click to collapse
see above.
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
Click to expand...
Click to collapse
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
1-What is adb?
Click to expand...
Click to collapse
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
2-What is busybox?
Click to expand...
Click to collapse
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
2-What is fast boot?
Click to expand...
Click to collapse
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
3-What is eMMC write?
Click to expand...
Click to collapse
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
Click to expand...
Click to collapse
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
This thread is amazing!!
We had a lot threads like this in the HTC Blackstone Board of pocketpc.ch....
Hope to get more threads like this in every device category....
Thumbs up
Perhaps Threadstarter can write the answers in the first post...??
50chickens said:
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
boot loader = turn phone off. then, volume down + power on.
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
android application. eg, visionary+.
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
see above.
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
Click to expand...
Click to collapse
Thank you very much.
Hi guys, here's some stuff for you to play and cook custom roms for your beloved(?) fathom.
I'm sorry for the delay but I really couldn't release those tools before.
Please note that I don't have a tool to decrypt other roms. To decrypt those vs750 roms, I had to hack the flash procedure, using an ARM disassembler attached on the flashing tool during a flash. It took me almost 2 weeks to find out a way to get decrypted files without bricking the phone, so hopefully you'll enjoy this and will build great Fathom roms.
Special thanks to trueg for experimenting/testing these tools.
So what do you need ?
- the last lg kitchen (available here)
- a decrypted rom (v5 or v7 available the the bottom of the kitchen's 1st post)
OR
- a full vs750 v7 kitchen (everything ready to cook)
mirror : bad upload, back soon
*****************************
Full vs750 v7 Kitchen info :
- SYS is already extracted (in 21000 folder)
- XIP is already modified to work with erviuskitchen (no more dsm files)
- OEM is stock v7, nothing more, nothing less
Build Procedure :
- Add your packages to EXT folder as usual
- Launch erviuskitchen.exe
- Select vs750, 21000 for ext, sys, xip
- Choose the packages you want to add/remove
- Check 6.5 aku and build rom
- Launch start.bat
- Select vs750 (9)
- Hit "u" to build rom.bin (you must use "vs750" as the beginning of the file name)
- flash it as described below
*****************************
Now the steps to flash the phone :
1- Install drivers
- LGUnitedMobileDriver_S4981CAN33AP22_ML_WHQL_Ver_3.3
- LGWindowsMobile_USBDriver_WHQL_ML_Ver_1.0
- LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0
You should easily find them (or more recent version) using your favorite search engine.
2- Install the flash tool
The only one that I know of being able to flash decrypted roms is LGNPST. Sorry, you'll have to search for it on the web (shouldn't be too difficult to find).
If using lgnpst, you'll also need to register this dll (using regsvr32 vs750.dll in a dos command prompt)
3- Connect the phone
To be able to connect the vs750 to lgnpst, you have to be in composite mode (on the phone, go to "settings/connections/Switch usb" then select "VzAccess Manager", click "save" and finally wait for it to reboot.
It's possible to flash this phone in emergency mode (if anything goes wrong and the fathom doesn't boot), but if you do so, you might lose your nv (and MEID info). To boot in emergency mode, shutdown your phone, unplug it, then press the "5" key on the keyboard and while keeping it down, plug the usb cable.
Don't do it unless necessary.
4- Save NV (just to be able to recover in case of problems)
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe, it should detect your phone (filename on the top right panel should be "VS750.dll").
- Click on "phone settings", wait a few secondes for a new window to appear
- Click on read button
- It will create a VS750_COMx.nvs in C:\LG Electronics\LGNPST
- Close the windows and click on "click here to continue".
5- Flash the Rom
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe
- Go in provision Tab (should be selected by default)
- Select Upgrade
- BIN file : "c:\VS750\BIN\VS750XXX5.BIN"
- Check SCR File, then select "C:\VS750\SCR\VS750VZ7_04.scr"
- Check PRL, Nam1 (uncheck nam2), select "C:\VS750\PRL\58006 - EVDO OEM Factory Default.prl"
- Don't check Eri file
- Click on "start"
- Keep fingers crossed for approximately 10min. The phone will reboot a few times, this is normal.
- Enjoy your 1st VS750 custom rom
Also note that for lgnpst to accept your rom, its name will need to start with "vs750".
And don't worry, there is almost no risk of really bricking the phone (especially if you saved the nvs).
I can confirm that you don't need to be too concerned about bricking your phone. As long as you can boot in to emergency mode and you have a backup of your NV data (made with LGNPST - it's very important that you do this - heck make two copies) you can recover it from an unbootable state.
TrueG
Would you be able to provide a pre-configured pack for the Fathom? I am trying my best to figure out how to get the kitchen working, but I haven't gotten it to fully work.
Thanks in advance.
-EDIT- I need to go back to school and learn to read - I saw LGNPST written 3 times, but only 1 was the program. The other 2 were component addons for it, all 3 having version numbers attached to the filename (hence my confusion lol).
@Pizzaboy: I'll help out with getting a filepack together. Which version of windows are you working with? Win7/WinXP, 32bit/64bit
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit
I run 7, both 32 and 64. My main dev is a 64bit system, and my porta-dev is a 32bit.
I've tried following the directions on the kitchen page, but I can't seem to get the XIP to work. It throws errors when I have to start pushing buttons.
da_reeseboy said:
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit
Click to expand...
Click to collapse
XP 32bit
TrueG
I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.
da_reeseboy said:
I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.
Click to expand...
Click to collapse
If you get something working on XP, i'll be able to get it working on 7.
I'm mostly lost on getting the V5 ROM set to work in the kitchen. I've never done a ROM before, and most of the tutorials are either really long and confusing, or really short and confusing...
Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?
da_reeseboy said:
Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?
Click to expand...
Click to collapse
When i hit step 9 in the Kitchen walkthrough, I push "realloc p" and it throws errors. Then when I get to the kitchen, it can't see the XIP and won't let me build a ROM.
@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.
spocky12 said:
@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.
Click to expand...
Click to collapse
could you make a v5 one too? V7 has too many bugs to make it a base personally.
Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.
spocky12 said:
Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.
Click to expand...
Click to collapse
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?
pizzaboy192 said:
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?
Click to expand...
Click to collapse
Totally possible, we just need to have a working base to start from.
Thanks Spocky for the uploads.
I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.
pizzaboy192 said:
I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.
Click to expand...
Click to collapse
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.
da_reeseboy said:
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.
Click to expand...
Click to collapse
I wonder if we could hybridize this... Take the OEM stuff from the V5 rom and the XIP from V7... would it work?
It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.
da_reeseboy said:
It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.
Click to expand...
Click to collapse
I'm waiting for files to copy on my netbook and I'll see what happens and if the ROM builds.
I'd be a little cautious of drivers, as there's some reason that there were so many issues with the 3G connection dropping on the V7 rom, I'd want to pin it on the WWAN drivers...
Forum:
If this specific question is in another thread, please forgive me and redirect me.
If not, any instruction would be greatly appreciated.
Equipment:
Visual Land, Prestige 7
Model # VL - 107
ICS 4.0.3
Baseband 1.0
Kernel 3.0.8+
Build # 86F5-D1-H1-MO1-1718.20120327
Objective:
To create a backup/recovery img/dump of the existing stock ROM, without having to add "clockwork", "cynogen", etc...
Software on Hand:
Windows 7
Livesuit 1.09
Virtualbox
Ubuntu via Virtual Machine
Please detail everything and speak to me as if I were a little child...
Thanks in advance!
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Can this be done with ADB?
ruscan.calin said:
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Click to expand...
Click to collapse
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
gth826a said:
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
Click to expand...
Click to collapse
I understand now this is a tablet so it's common problem for some
well you have to find a way to root device to get access to system files then use a rom dumping tool just take a look here or here
nobody can tell you for sure how to do that this is device specific I do not know to much about that particular tablet just try
I just got this tablet today, and it's rooted out of the box.
Not sure if that helps you, but I wanted to contribute if I could.
[signature]
Recovery for Galaxy Ace 2 - i8160
Hi,
Any chance of a simple recovery for the Galaxy Ace2 i8160 ?
VL107 Update Down To 4.0.3/4.0.4
Hello,
I've been trying to figure out how to change my VL-107's OS, and a Recognized Contributor pointed me to this thread.
I've downloaded LiveSuit, but I can't figure out how to make it work. If at all possible, I need two things: an .img file for 4.0.3 or 4.0.4, and instructions on how to apply this update via command prompt or a program that utilizes command prompt.
I have Windows 8.1, my VL-107 (Visual Land Prestige 7), and LiveSuit (which I'd really rather not use).
The only experience I have in flashing involved using command prompt, and I'm much more comfortable doing this than relying on a program to do everything "behind the scenes". Otherwise, I would also be willing to put an .img file on my tablet's "SD card" and apply the update through Recovery mode.