Hi to all, i made a python program that help user to install/update the system.
With this program you can stop using the android boot menu, you can put all in the script.
What you can do with Boot Script Generator:
- install system
- update system
- backup system, data (with old and new method)
- apply updates
- clean data and system
- install apps located in /sdcard/andboot/apps
UPDATE 22 / 08 / 2010
New interface
Add new backup options
Add image size options
No more press d-pad or volume up
No more install procedure
cross platform and only python is needed
you can choose where install
NAND - SD - IMAGE both for system and nand
and what you want to do before boot
Little how-to
flash modded nbh or put initrd.gz in andboot for haret users
open python script in a terminal:
Code:
python bootscriptgenerator.py
then choose what you want to do, (i.e first install)
put install-seq.sh in your sd in andboot folder (with other files)
turn on the phone.
you don't need to touch any button just wait
As you can see you can change many things.
Update initrd and nbh on 4/7/10
If you are an "haret" user use this initrd.gz
Boot Script Generator (right click on link -> save as file)
Simple how-to run android from windows - Simple guide to flash android on Nand
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It could be very useful if you want to speed up your system update
Reserved
Exciting, now you just need to make a android app as well to do this, that way you can set the options and hit reboot
Good job
I'm just working on it.
i think that next dzo nbh will include this changes
Any feedback?
Strange...
I download the latest version of python (2.7).
When I select any options in your tool, and want to create the .sh, impossible to find it !! I think he's not created...
I use it in a windows PC (Windows XP pro SP3).
I try with all options and it's the same thing. Sorry for that.
I hope you can find the problem.
Cheers.
l1q1d said:
Any feedback?
Click to expand...
Click to collapse
I make a simple modification, try with updated version
Source code...
I will try but when I want to download the link in first page, I've the source code...
Could you upload your tool ?
Cheers.
l1q1d said:
I make a simple modification, try with updated version
Click to expand...
Click to collapse
Re update link (extract with win rar/7-zip or other)
Hi l1q1d,
I've download this new version but same result : no product file...
I try to find it in my PC but no file...
I don't know how to help you
Thank you for your release of your tool key mapping
I'm on holiday now : go to Spain...
Cheers.
l1q1d said:
Re update link (extract with win rar/7-zip or other)
Click to expand...
Click to collapse
Hi,
I try to install Android on a Polaris and created an install script with your bootscript creator, but it always stops with the error:
'd: invalid number '512
where 512 is the size of the data image I have set in the creator gui.
Am I doing something wrong?
Thanks in advance
Abomb
Could you please submit a screen shot of your settings and the output file? Thanks
Here they are.
I forgot to mention that I commented out the data.img remove part, because that part gives me the error that the script file did end although a "then" was expected or something like this. But seeing as I do a fresh install and have no old data.img I thought it should not be a problem.
Any other error before?
Could you please test with 256?
Thank you
I tried two things, first with 265 MB and the disk.img remove code left in, the second time with the code commented out.
The first time I got a bootlog.txt that I attached here, the second time I got the error again
'd: invalid number '256
but sadly no bootlog.txt. Oh and no error before the invalid number one.
I update a new version of bootscriptgenerator
Try now
I tried with the new version, but exactly the same thing, tried first with disk.img delete code left in, second time commented that out.
Error messages were the same, first time bootlog was created, second time not.
I also double checked if I was using the new version of the creator.
Could you please make a test with this.
Please don't edit it (it could be a windows endline problem)
With the file from your last post it works!
Did I do something wrong then?
I didn't edit the .sh file for the first try, only when that didn't work I edited it.
The problem is the windows end line.
It isn't your fault is WINDOWS :-(
i update a new version, now i need someone to test it
Related
I plan on installing the CyanogenMod once I get my Nexus One. I have heard many positive things from him, especially from G1 owners
My question is, is the Cyanogen wiki guide sufficient for someone who can read and understand directions? It's located here:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod
I have read everything and it seems to be laid out nicely! I haven't encountered any steps that were confusing at all.
My only question is the lack of partitions. I've watched some youtube videos and they are always taking about setting up partitions (using words like "ext4" and "ext6"). But this guide doesn't mention anything regarding this. Does this guide do the partitions automatically without user intervention?
edit:
I actually do have questions.
Regarding the "Flash Recovery."
1. Note: The Recovery.img should NOT be on the SD Card, it should be in the current working directory.
2. On the command prompt you opened earlier, type in the following command.....
Where exactly is the current working directory? Do I need to select it or do Ii simply enter the command "fastboot flash recovery Recovery.img"
Many thanks! I haven't done anything yet but just want to go over the steps so I don't get lost!
the working directory will likely be the tools directory of your SDK, or whatever directory you have fastboot.exe in.
Before writing in fastboot flash recovery, you need to navigate to the tools directory in the cmd prompt, either by typing "cd" then the /route/to/the/directory, or in vista and above, go to the tools directory, right click while holding shift and go to the option "open command window here"
Don't worry about partitions unless you intend to use apps2sd.
Easiest way to parition for apps2sd is with amon ra. Just follow the prompts, no directions required. Figuring out what size you want those partitions or swap, not so easy. I searched for ages without coming across anything concrete. Ended up going 64 meg swap, 1 gig ext 4 and the rest FAT.
the working directory is the place you extract the AndroidSDK file (usually in the local C drive, so it may look like this: C:\AndroidSDK-windows\tools\
once you install the usb drivers and get adb/fastboot working, you'll usually be running cmd commands from inside the "tools" folder
those directions in his wiki are perfect; as for partition, if you want to use Apps2SD, it's really simple to do as it's one of the options under Amom-RA's recovery image
Thanks guys!
So the partitioning is actually related to Apps2SD? This means that I do all the partitioning after the rom is installed?
Before, all data is lost when you partition. You can mount the sd after you partition while in amon ra and move the rom over then dismount it. Before you flash wipe everything. My advice would be to do a nandroid on the old sd to start. Then copy all files from the old sd to the pc, only takes a minute.
EDIT:
I went to the following http://forum.xda-developers.com/showthread.php?t=613217 and it worked that way. I am not sure why that method works but it does
Hmm it seems I have trouble already.
After I install the USB drivers via Android SDK, and then enable usb debugging mode,
When it installs drivers, one of them doesn't install:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried using USDBDeview to remove em and reinstall em, but I end up with the same message.
I am using Windows 7 64 bit
attached below is my android sdk settings:
and what happens when i go to command prompt:
Ok if driver isn't installed, go into device manager and update Nexus One driver yourself.
Browse for this DIR C:\AndroidSDK\android-sdk-windows\usb_driver (where you have installed it etc)
Just seen you're edit, my bad.
Leoncc said:
Ok if driver isn't installed, go into device manager and update Nexus One driver yourself.
Browse for this DIR C:\AndroidSDK\android-sdk-windows\usb_driver (where you have installed it etc)
Click to expand...
Click to collapse
No apologies! You are correct though. That is the why to install it if it can't automatically find it
Anyway, I managed to install it! The instructions are very clear so props to whoever created that wiki page!!
I do have one more question and it's regarding Apps2SD.
On this page, it gives instructions on how to enable and disable it.
When I go to the option menu, it doesn't allow me to select it. It's faded out. What do I do to go about enabling this?
i thought cm's instructions were enough; but thanks to the help i got here, i was able to root.
bozeefus said:
I do have one more question and it's regarding Apps2SD.
On this page, it gives instructions on how to enable and disable it.
When I go to the option menu, it doesn't allow me to select it. It's faded out. What do I do to go about enabling this?
Click to expand...
Click to collapse
Usually that means you need to partition or if you are partitioned to switch to ext 4 on CM
Hi, Can someone please dump/backup the system.img from baltic P500 or have a offical update for baltics. Thanks
Just do a backup and upload it. Thanks
No one here from Baltic States?
Hey, just show me how to do it, and I will give you.
hi, please use this guide: http://forum.xda-developers.com/showpost.php?p=8917870&postcount=12
or if you have Thunderg installed, then just do a backup and upload these files.
thanks
Hmm, could you be more specific? I just bought this Optimus One like two days ago, and I'm feeling very newb (it's my first Android).
What do I have to do, to give you that system.img and what is that system.img file?
Hi, the system.img a backup from Android /system partition is a main part of the android. But this guide we just dump that /system partition, it's the easiest way.
I'll try to help you do that:
1. Is your phone rooted?
If you haven't done that, then use Z4Root(super easy app ) and you can get it from here: http://www.upload.ee/files/997919/z4root.1.3.0.apk.html
Download that file and copy to sd card and install.
Open that installed app and root your phone
If you need help with that, then there is little how to here: http://www.worldofnubcraft.com/285/rooting-a-lg-optimus-one-android-phone
2. OK, rooting done, now we need terminal app: You'll find that from Market. Just search "Android Terminal Emulator" it's from Jack Palevich and install that.
3. Now open the Terminal Emulator and enter these commands without "" and hit enter after command, these 3 command should be it:
"su" it asks for a root privileges and you allow that
"cd /system"
"tar zcvf /sdcard/system-dump.tar.gz *" and wait when it finishes. it takes some time. It's done when you see #, it takes couple of minutes max.
4. That file is now on your phone SD card and upload that system-dump.tar.gz file to somewhere and let me know
Are you sure about that?
I'm sorry, but it's not working. It gives me an error "tar not found". Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By the way, what you can do with that file? What it contains? I'm just a newb, and I want to know everything about Android.
EDIT:
Is it possible to do that dump with Thunderg?
Go to market and install app called "BusyBox" and download / install BusyBox with this tool. After that it will work.
yes, i forgot busybox install that and give a new try
Ok guys, I got it. Before putting it live, I would like to know one thing. Does it contains any personal data, if so, what exactly? Sorry, for being so paranoid.
hi, it won't contain any of your personal data. Personal data is stored mostly on /Data partition and we didn't dump that. Thanks
Ok, so here you have it.
Optimus_One_Baltic_ROM_dump.zip - 89.2 Mb
And it's only contains branded ROM with no changes? That's great. What program do I need to restore my ROM to the branded one, if I'm going later to change it?
i think you should look to Thunderg... it's best way to make a full backup and restore after
Ok so allot of people have been asking, if kdz can’t see my phone then how do I flash.
This is a simple yet effective solution that I have found.
This will work even if
• usb debugging is off
• You made a factory reset
• Device wont boot
Before I start I need to give thanks to @mircea89fzr for providing this tutorial
http://forum.xda-developers.com/showthread.php?t=2409308
Step 1
Head over to http://lg-phone-firmware.com/ and download a kdz image for your device
Step 2
Download LG_KDZ_FW-Update_OfflineFix.ZIP (attached) thanks to @mircea89fzr
Step 3
Run B2CAppSetup.exe inside the KDZ_FW_UPD_EN folder and make sure you install the drivers then close the program
(if you get program not responding undo changes you made in the next step and give it some time)
Step 4
Open notepad as Administrator(Go to windows menu, type notepad and right-click and run in Administrator mode)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 5
Open the hosts file (c:\windows\system32\drivers\etc)
And add this line 127.0.0.1 csmg.lgmobile.com
Then save and exit
Step 6
Go to windows menu, type cmd and right-click and run in Administrator mode.
Drag auto.vbs over command prompt and hit enter.
Step 7
Click OK until you get this
Step 8
Make sure Type is set to 3GQCT and phone mode to DIAG. Select your KDZ file and click Normal web upgrade test.
Step 9
Click on Upgrade Start.
Step 10
Click on Clear phone Software update Registry and then click OK.
Step 11
You upgrade will start and then give you this message
Step 12
Disconnect the usb cable
Remove your battery
Reinsert your battery
Plug in the cable
Power on
Then Click restart
Step 13
Your Device will be detected for a split second and the flash will continue.
If it gives you the pop up again repeat step 12
Step 14
Flash may get stuck at 4% of update
Repeat step 12
Step 15
Remove the line in the host file
Step 16
All done
slipsystem said:
All done
Click to expand...
Click to collapse
this is the copy of this http://forum.xda-developers.com/showthread.php?t=2409308 thread ???
AXD96 said:
this is the copy of this http://forum.xda-developers.com/showthread.php?t=2409308 thread ???
Click to expand...
Click to collapse
My apologies I should have made it more clear this is not a guide to flashing a kdz image as it was already discussed in this thread.
http://forum.xda-developers.com/showthread.php?t=2409308
this is a guide to flashing the kdz if your computer does not see your phone. It is more about step 11 on wards.
my apologies if I am offending the forum rules but I did give proper thanks and I have mentioned mircea89fzr so that he can see that I created this thread and message me if it is a problem.
the reason I posted this is because a lot of people have asked me how you flash when your device is not detected. referring them to this single post http://forum.xda-developers.com/showpost.php?p=45988501&postcount=23 does not help people as it does not explain how to get to that point. the user would then have to page back to find the tutorial. I made this guide so that they can see step by step in one post.
I will have no problem removing the post if mircea89fzr requests but I would make a suggestion to include steps 11 on wards as an addon to the original post.
slipsystem said:
My apologies I should have made it more clear this is not a guide to flashing a kdz image as it was already discussed in this thread.
http://forum.xda-developers.com/showthread.php?t=2409308
this is a guide to flashing the kdz if your computer does not see your phone. It is more about step 11 on wards.
my apologies if I am offending the forum rules but I did give proper thanks and I have mentioned mircea89fzr so that he can see that I created this thread and message me if it is a problem.
the reason I posted this is because a lot of people have asked me how you flash when your device is not detected. referring them to this single post http://forum.xda-developers.com/showpost.php?p=45988501&postcount=23 does not help people as it does not explain how to get to that point. the user would then have to page back to find the tutorial. I made this guide so that they can see step by step in one post.
I will have no problem removing the post if mircea89fzr requests but I would make a suggestion to include steps 11 on wards as an addon to the original post.
Click to expand...
Click to collapse
ok
it's only a question
I'm stuck at 4% i.e flasher is not detecting my phone, what to do?
P.S i'm using "download mode" from boot-up bcuz my phone is bricked already
Hello All,
I have a Nexus 6 (Hence the reason I'm posting in this thread) and I am not able to take screenshots after upgrading to Marshmallow 6.0. I would think to post in the thread of the current rom I'm running but I also full wiped and tried a different rom with the same result.
Every time I try and take a screen shot it says "Couldn't capture screenshot. - Can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." I would post a screenshot of what it's doing but... well... I think you get the point. I have plenty of storage space and I have dived into the various permissions settings on 6.0 but have yet to find out how to fix it.
Has anyone else had this problem across multiple roms and no luck with screenshots?
Currently running:
Chroma Oct-10-2015
Kernel:
3.10.40-Chroma-v1.01
Go to the screenshot directory and try to manually create any file there using your usual file manager/explorer.. If that fails,.it may be that the permissions are screwed which sometimes happens when you copy sdcard data back whilst in recovery.
If that sounds like your problem, there is a zip you can flash. Do NOT use "fix permissions" in recovery.
Flash this*zip*via recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
Located from thread: http://forum.xda-developers.com/showthread.php?t=2239421 by @osm0sis
danarama said:
Go to the screenshot directory and try to manually create any file there using your usual file manager/explorer.. If that fails,.it may be that the permissions are screwed which sometimes happens when you copy sdcard data back whilst in recovery.
If that sounds like your problem, there is a zip you can flash. Do NOT use "fix permissions" in recovery.
Flash this*zip*via recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
Located from thread: http://forum.xda-developers.com/showthread.php?t=2239421 by @osm0sis
Click to expand...
Click to collapse
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Sent from my Nexus 6 using Tapatalk
mkgarrod said:
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Try this. Boot into TWRP select Advanced, File Manager go to /sdcard/pictures hit Select, chmod 755, confirm, reboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mkgarrod said:
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Click to expand...
Click to collapse
Witek_M said:
Try this. Boot into TWRP select Advanced, File Manager go to /sdcard/pictures hit Select, chmod 755, confirm, reboot.
Click to expand...
Click to collapse
Why are you still in ES? The problem isn't permissions, it's ownership. Use my zip as was suggested by @danarama.
The permissions zip worked,
As to why I was "still in ES?" I like to have an understanding of how everything works. May not be the quickest way to fix a problem, but it allows process of elimination on my side to see what specifically the issue is.
I appreciate the .zip and suggestions everyone! Thanks!
osm0sis said:
The problem isn't permissions, it's ownership. Use my zip as was suggested by @danarama.
Click to expand...
Click to collapse
@osm0sis, You are amazeballs!! Ran into this same inconvenience the last couple of days. Swyped a quick search, quite effortlessly arrrived here, where I can thank you for the fruits of your labour. And I do mean ALL of your work across XDA. I appreciate you much! ?
Take screenshot on your PC
Well, I think maybe you can try taking the screenshot of your Nexus 6 on computer. Just don't do it on the phone if it keeps failing. Android Manager can do this and save the picture on your PC.
is it working now?
You can try to rename pictures to pictures2 and reboot your phone, this was a quick solution on the oneplus one, if it works, but it's a dirty solution.
Hi guys.
While I was looking for an appropriate firmware, I found a website where I could get an update for the Chinese version, which provides the newest Flyme 8 for this device.
https://www.flyme.com/firmwarelist-138.html#3
Download update.zip from here. And download TWRP from here.
I flashed this build with TWRP. To use TWRP you need to have your bootloader unlocked.
To unlock this, please, follow https://remoteunlockservice.com/payment.php (paid). Then flash TWRP, I'm attaching here, using the fastboot mode:
Code:
fastboot flash recovery /path/to/new_recovery.img
I needed to remove lines until the line containing
Code:
delete_recursive("/cache/backup");
in file update-script by the path
Code:
meta-inf/com/google/android/
inside update.zip.
Then I put the modified update.zip to /sdcard and flashed that update.zip using TWRP
Enter TWRP (power + vol+, then release power and hold vol+ up to the vibration). Connect the device with a USB-cable and transfer tool-root_unlock-Testing-Pro7.zip and update.zip to the internal memory.
Flash update.zip and immediately flash tool-root_unlock-Testing-Pro7.zip which I'm attaching here.
Log in with your Flyme account on the phone.
To get the root access please follow the instructions under the link https://mroot.flyme.cn/index.html to make an application (press 申请授权) and download the root app from https://mroot.flyme.cn/download.html.
Filling out the application, you'll encounter some Chinese characters.
Here is some translation:
Flyme 账号 — Flyme Account
Root 授权设备 — Your Device
姓名 — Your Name
手机号码 — Phone Number, use fake Chinese phone number 12345678901
PSN — get this parameter from the root app you have installed
CHIPID — the same as PSN
申请理由 — tell the reason why you need the root access. As for me, I specified, "I need to install the Russian localization for the Chinese firmware."
Wait a few days or less. The single big button in the root app will become active (its color will change from light gray to blue). Pls remember, that you must be logged in your Flyme account. Tap that button and wait until the rooting completes. In the end you'll see a picture which implies your phone has been rooted (an open padlock beside a phone) .
Grats! Now you have the newest rooted firmware.
References: https://4pda.ru/forum/index.php?showtopic=902543
Reserved
Noob question. I'm using a meizu m8 and I was wondering if this method will work on my phone. Do I just have to upgrade my firmware and follow your instruction is that correct? My current firmware is Flyme 7.1.6.0G
Sorry, but I have checked the relevant thread on 4pda, and the method there is dramatically different.
Hi, did you have an idea of why with unlocked BL, fastboot tell me "FAILED (remote: not allowed in locked state)" ?
Device is pro7 P25 64Gb version
Thx !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
myxomop25 said:
I needed to remove lines until the line containing
Code:
delete_recursive("/cache/backup");
in file update-script by the path
Code:
meta-inf/com/google/android/
inside update.zip.
Then I put the modified update.zip to /sdcard and flashed that update.zip using TWRP
Click to expand...
Click to collapse
Should I delete up to delete_recursive("/cache/backup")
Or including this line ?
I tried both way but I always receive error 11. Also tried to copy updater-script from custom firmware
Also tried to install Meizu Pro 7 AOSP Beta V3.zip
That goes ok, no errors but phone starts only in twrp
Have no Ideea why
tintome said:
Also tried to install Meizu Pro 7 AOSP Beta V3.zip
That goes ok, no errors but phone starts only in twrp
Have no Ideea why
Click to expand...
Click to collapse
that means your phone still have orange state enable .
Try flashing magisk insatller zip v18 after flashing the Aosp rom.