Database Develop

BSG - Boot script generator

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

[GUIDE] Easy upgrading your i9000 from 2.3.6 all the way to 5.1.1! [Updated 12.07.15]

{
"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 decided to write this quick guide to condense what took me the better part of 8 f**king hours trying to do. The time it took was probably due to a mostly faulty USB port on the phone, AND on my laptop too...
Long story short, I was given this phone after my S5 decided to go for a swim with me. My first Android phone was the Galaxy S+. I then upgraded to the S2 -> S3 -> S4 and thus S5.
I had never used the regular 'S' (non '+' version) before today and sadly there is little support for it. So I thought I would add my first and last guide here on how to get this phone all the way from Android 2.3.6 (latest stock official) right up to 5.1.1. I owe a lot to XDA, so this is my way of helping out. This phone unfortunately is OLD, and thus requires outdated methods of flashing/upgrading that I was not very familiar with. Hopefully this will help you save a lot of time.
It is important to note that not all of these steps will be mandatory! I will try and mark the ones that I don't think are mandatory (and that you may skip). However I will just outline the full steps I took.
First you will need this package that I am going to upload here. Feel free to make as many mirrors as you want.
My apologies in advance if I do not have permission to upload copies/etc. of these files but AFAIK I am allowed to upload these files.
Code:
Files:
https://mega.co.nz/#!PU0xkbrJ
Key:
-Mwl7Ga-FAqAenVC9MDoOadYA0RTcDskQSsKFggZaVM
What we are trying to accomplish!
If needed, downgrade/upgrade your i9000 to Android 2.3.6. This is the latest stock Android version released for this phone. Doing this should fix any corruption issues or any other BS that you may have done to your phone. This still may not be necessary at all.
Install the Semaphore_2.7.4 Kernel & Recovery package (bundled). This is the best Kernel for your i9000 and it also gives you the most stable working Custom Recovery I have found. (I have tested TWRM, CWM & PhilZ and found this bundled CWM to be by far the best (and in this case the only thing that worked for me)).
Flash whatever new Custom Rom that you want. You can flash any firmware even up to 5.1.1 currently.
So let's do this quick, so you don't have to waste 8 hours like I did yes? Hopefully you don't have malfunctioning USB ports like I did too.
Step 1. - Download the file package above.
Step 2. Uninstall Kies if you have it installed. Then reboot your computer. (Step may not be mandatory but I did it)
Step 3. Run the "USB_Drivers_1.5.49.0.exe" installer from the "THESE FIRST" folder. Then reboot your computer again.
Step 4. Put your i9000 into DOWNLOAD MODE (Volume Down + Home + Power) and plug it into your PC. It should be detected, and Windows driver install popup will show up etc.
Step 5. Run "Odin3 v1.83.exe" and hopefully you'll see it connected in COM "X". If not, then try and sort out the driver/cable/port issue. Try another USB port, and don't use any HUBs etc.
Step 6. Extract the "I9000XXJVU CFROOT.rar" and put the contents somewhere. Put the largest file in PDA, the CSC file in CSC and the remaining file in MODEM/PHONE (this is all in ODIN (also we are ignoring the CFROOT file))
Step 7. Hit start and wait. (You may need to add the s1_odin_20100512.pit file in the folder to the PIT section in ODIN if it won't flash. (I didn't have to)
Step 8. Wait for your phone to reboot into old Android 2.3.6. Then shut it down, because we are going to upgrade it AGAIN now that it is fully stock.
Step 9. Boot into download mode AGAIN and connect to your PC.
Step 10. Open up an ELEVATED CMD Prompt (With Admin Privledges) and navigate to the "THESE SECOND\Heimdall Suite + Kernel" folder. Using the command "cd <yourfilepath/Heimdall Suite + Kernel folder>"
Step 11. Run the command: " heimdall flash --kernel zImage --no-reboot " (without quotes). You may have to make the 'kernel' part of the command in CAPITAL letters, for it to work.
Step 12. If (AND ONLY IF) you get an error -12 or something. Then go into the folder "Driver Change For Kernel Flash" and run the "zadig.exe". Choose Options > List all Devices > Serial/etc/device and try one of the 3 drivers and click Replace/Reinstall etc. Then try step 11 again. Keep trying with each driver until it works. <--- THIS STEP ONLY IF STEP 11 DIDN'T WORK THE FIRST TIME!!!!
13. Reboot your phone into RECOVERY MODE! (Volume Up + Home + Power).
14. Wipe Data (Factory Reset). Clear Dalvik etc. etc.
15. Flash whatever .zip of the new ROM you want baby!!
Edit: Here is a second set of instructions that may help with the Heimdall part!
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Note, that I flashed the unofficial OMNI from here (it's Android 5.1.1. and it works beautifully) My thanks to humberos + others:
http://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rom-t3054101
It asked me to reboot recovery many times and complained with a bunch of errors but basically you just ignore all of those errors and keep rebooting and flashing the same .zip again. Eventually you won't see those errors any more at all and the rom will flash flawlessly with the included Aroma/TWRP etc. and voilá! You will have upgraded your old i9000 from 'x' firmware to 'y' firmware (hopefully better). Congratulations on breathing life back into your i9000! Galaxy S! Now you can give it to your mum or something!
Please just hit 'THANKS' if this helped you. I don't need any more, or any less.​Edit: Added some pictures for proof that this works.
The attached CMD picture is what it should look like when the command executed properly and the Semaphore_2.7.4 Kernel was installed. Also it shows the error I got in Step 12 before I used the driver program to change the libusbx drivers so I could flash it properly.
The other pictures show how the installation process looks for Unofficial OMNI ROM, including the Boot logo, and the top image is just a readout of the 'About Device' pane.
========= QUICK FAQ: =========
Q Can I PM you for help?
A: I'd rather not. I don't use the forums much. Post here and maybe I or others can help you out. Also check the README.txt files in the package you downloaded.
Q: The files aren't available any more, can you reupload them?
A: Maybe, ask in the thread. Everything in the package was downloaded from other places: Old 2.3.6 Firmware from Sammobile + Kernel from the above Wiki link etc. Heimdall from Google.
Q: Does this work for the i9001 (Galaxy S+)?
A: Probably not. Try it yourself at your own risk.
Q: Does Wi-Fi/Something else work?
A: Wi-Fi does, see the top picture. As for other stuff, I don't know, try it for yourself and see!
Q: I prefer using TWRP Recovery for this phone an-
A: I don't care. I tried 4 other custom recoveries and none of them worked except the one I listed.​

Hallo I have a galaxy s2 model i9100 which was on stock official android 2.3.6 gingerbread and I upgraded it to CWM 12.1 ANDROID 5.1 Custom rom....and then got these bugs.....
1.....the BACK button, OPTIONS button dont work...also the MENU/HOME [middle] button works as back button. .....its not a hardware problem coz they worked very well on Gingerbread the previous rom
2....when I call some one...he doesnt hear me and I also dont hear him....its the same issue when I activate loud speaker or insert HEADSETS.....
ITS NOT A HARDWARE PROBLEM because things were working well when on official android 2.3.6 stock......and also all the speakers work well on other apps....also, people dont hear me during calls and yet the mic WORKS VERY WELL FOR VOICE and VIDEO RECORDING FOR OTHER APPS including camera and voice recorder.....BUT STILL PEOPLE DONT HEAR ME DURING CALLS......
I then took it back to official android 4.1.2 jellybean AND I STILL HAVE THE SAME ISSUES......STILL THE BUTTONS DONT WORK and also i dont hear people during calls and they dont hear me either......PLEASE HELP ME...this is a software problem.....I have tried factory reseting the phone and wiping all data on phone and still the same issue. ........AM NOT AN EXPERT TO ANDROID
THANKS....
[email protected]​

Update to Marshmallow QD1 via recovery

You can directly flash the QC1 ROM from the following thread using ODIN to get to QC1:
https://forum.xda-developers.com/att-galaxy-s5/general/g900aucs4dqc1-odin-update-v6-0-1-t3588730
Once you are on QC1, download the following, move to external SD card and flash using recovery.
QC1 - QD1
https://www.androidfilehost.com/?fid=817550096634765645
I will continue posting new OTAs here to the best of my ability.
Older files:
PA2 - PA3
https://www.androidfilehost.com/?fid=24651430732236961
PA3 - PH2
https://www.androidfilehost.com/?fid=24651430732236960
PH2 - PH3
https://www.androidfilehost.com/?fid=312968872162492662
PH3 FULL ROM
https://www.androidfilehost.com/?fid=457095661767099488
PH3 - PH4
https://www.androidfilehost.com/?fid=529152257862672546
PH4 - QA1
https://www.androidfilehost.com/?fid=745425885120714574
QA1 - QB1
https://www.androidfilehost.com/?fid=673368273298937968
QB1 - QC1
https://www.androidfilehost.com/?fid=457095661767151941

RK said:
I took the OTA so I cannot test these files. USE AT YOUR OWN RISK. These are downloaded from AT&T official FOTA server.
You MUST be on PA2 to start this process.
THIS WILL ERASE ALL YOUR DATA.
Copy to EXTERNAL SD card and apply update from SD card in recovery.
PA2 - PA3
https://www.androidfilehost.com/?fid=24651430732236961
PA3 - PH2
https://www.androidfilehost.com/?fid=24651430732236960
Click to expand...
Click to collapse
can you explain how you got these files? is there a way for me to do it for the g870a?

Big thanks @RK ! Everything is well !
{
"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"
}
Sent from my SM-G935F using Tapatalk

PG3 to PA2
PA2 to PA3
PA3 to PH2
Worked perfectly!

phillytemptation said:
can you explain how you got these files? is there a way for me to do it for the g870a?
Click to expand...
Click to collapse
The first boot after you take the OTA, dial *#8736364#. This brings up the firmware update menu. Click on 'Result'. There, you will see a screen that looks like the one attached.
Here is how things worked for G900A:
I went to the server URL in the attached image using stock Samsung browser. This downloaded a file named desc and then I got a prompt to download the OTA. I clicked OK and the download started and failed.
However, the failed download did create a file named desc.bin on my phone. I clicked on that file and to my surprise, I got a pop up menu that had a download option. I selected download and then finally the full 911mb file named desc.bin downloaded on my phone.
I renamed it, changed the extension to zip and uploaded it!

RK said:
The first boot after you take the OTA, dial *#8736364#. This brings up the firmware update menu. Click on 'Result'. There, you will see a screen that looks like the one attached.
Here is how things worked for G900A:
I went to the server URL in the attached image using stock Samsung browser. This downloaded a file named desc and then I got a prompt to download the OTA. I clicked OK and the download started and failed.
However, the failed download did create a file named desc.bin on my phone. I clicked on that file and to my surprise, I got a pop up menu that had a download option. I selected download and then finally the full 911mb file named desc.bin downloaded on my phone.
I renamed it, changed the extension to zip and uploaded it!
Click to expand...
Click to collapse
thanks so much! hopefully I can find someone who can do it on the active for us =]

now, i have to go back from pg3 to pa2!
thanks!
-----------------
guys, i have a question
am i need to backup my External SD card?
or just backup device storage will fine?

you just need to backup your device storage :good:
-----------------
guys, i have a question
am i need to backup my External SD card?
or just backup device storage will fine?[/QUOTE]

This worked for me after the OTA failed at 92℅ and put me into a bootloop. I used odin to get to PA2 and then applies each of the files above. Now I am on a fresh build of marshmallow. Thanks.

​
yaboijay2029 said:
you just need to backup your device storage :good:
-----------------
guys, i have a question
am i need to backup my External SD card?
or just backup device storage will fine?
Click to expand...
Click to collapse
[/QUOTE]
These recovery operations do not wipe external SD. They just wipe internal storage.

RK said:
​
Click to expand...
Click to collapse
These recovery operations do not wipe external SD. They just wipe internal storage.[/QUOTE]
Unfortunately for those of us not on AT&T is our only option
Sent from my iPhone using Tapatalk

reillyman01 said:
This worked for me after the OTA failed at 92℅ and put me into a bootloop. I used odin to get to PA2 and then applies each of the files above. Now I am on a fresh build of marshmallow. Thanks.
Click to expand...
Click to collapse
Thanks, good to know others have also experienced the bootloop once setup gets to 92%
PA2->PA3->PH2 worked great! No OTA
Looks like AT&T have pulled the PH2 update from their download servers

Hi,
I'm on PA2 but PA2-PA3.zip not working for me. It gives sideload.zip error in recovery. Any thoughts plzzzz????????

Thank you so much -
Worked perfectly. I was on PG3. (PG3 to PA2, then PA2 to PA3, and then from PA3 to PH2).
I am on Cricket wireless, and I am not able to receive these OTA updates directly with my AT&T branded G900A. So this is a blessing.. Cheers to all of you

I still have no luck with these files
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------
Can somebody provide Odin flashable version of PH2?

drahmadzia17 said:
I still have no luck with these files
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------
Can somebody provide Odin flashable version of PH2?
Click to expand...
Click to collapse
Does not exist yet. These files is the only way to go for now. What error do you see? Re download the files and try again. Make sure you copy the files onto an external SD card before applying the update using recovery.

It says "sideload.zip error (Status 7)"
Flashed multiple times, changed SD Card but in vain. Anhow thnx for replying, I'll wait for some better solution.

great!
it works perfectly!
honestly, i don't know what exactly different between PG3 and PH2. but not bad!
finally we who out of usa got official MM

Just tried this on my S5 that was stuck on PA2, and it worked great. Now on MM !!!

+1 success. Finally. But neither zip from this thread worked. I’m not sure that it all makes sense, but I’ve retraced my steps to success here in case it helps anyone else. (Even if only to point out my own incompetence.)
My S5 was on OI5 (Given to me for free and SIM locked. I give up waiting for root, so might as well update this new fancy mp3 player of mine.)
1. In Odin, flashed to PA2 from here. (AP, CP and CSC, but not BL, like a commenter mentioned.)
I also skipped PA1, since I saw someone saying it was unnecessary... (It later gave me an Error Status 7 when I even tried.)
2. Back in Odin, flashed all PA components now, including BL, since in Recovery PA2-PA3.zip and PA3-PH2.zip both failed, E:Error in /sideload/package/update.zip (Status 7).
3. I searched the internet and found different steps with additional update zips http://www.androidsage.com/2016/08/03/how-to-update-att-galaxy-s5-to-android-6-0-1-marshmallow-g900aucu4dpg3/:
PA2 --> PE3 --> PF3 --> PF8 --> PG3 --> PH2
4. In Recovery, flashed G900A_PA2-to-PE3_OTA.zip from the above Android Sage link.
Phone is now on Android 6.0.1.
5. Still, for good measure I continued flashing (in Recovery) PF3, PF8, etc. For each, installing from SD was successful, but Recovery still said PE3. After a full reboot and initial setup, it now reads as PG3, the latest update before PH2, which fails to install.
Flashing PA2 - PA3 and PA3 - PH2 still return an Error Status 7, though. I’m sure it’s some noob mistake on my part. Yet, I’m already on 6.0.1, so not sure I care.
A triumph, huge success.

Hard Brick on Asus ZenPad S8 (Z580CA) or Z580C

HARD BRICK NO MORE!!! Asus ZenPad S8.0 Fix
I made the sad retarded mistake in updating a manual zip file thru CMW... I know retarded... anyways this caused the tablet to Hard Brick bootloader only with very little options, you might even have your serial number showing up as all 1's.
Usually this isn't a big deal sadly this tablet gets little to no love on the internet it seems... This is a guide to help anyone un-brick their tablet
Step 1. First this is more of a windows 10 issue than anything but some driver installs thru the Asus Flash Tool might fail.. something to do about Driver Certificates, so you'll want to disable that on your Win 10.. here a tutorial link for more youtube link HERE
Step 2. Installing the proper Drivers if you haven't already, which will all be in this zip folder HERE
Make sure you installed the ADB-Setup | Intel Android Drv Setup | Asus Android USB Drivers | Asus Flash Tool Installer 1.14
Step 3. Next you'll want to download the .raw file for the ZenPad can be found HERE
Step 4. Open your Asus Flash Tool Installer, boot up your device in the boot mode. (Hold Down the Volume Up + Power ) till you see a little android man with a hardhat.
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .raw file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
{
"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"
}
Now you may still get on a bootloop when it restarts, if that happens simply again restart in boot loader screen and do a hard reset and you'll be good to go! Afterwards just throw that new Marshmallow update in the internal and restart .. and you'll device will ask if you want to update now u got your tablet back and Marshmallow!!! I hope this helps if you have any troubles with the links, images please feel free to let me know pm or reply to this post!!! Best of Luck!
.RAW File was provided by Portzebie! Thanks again bud!!

Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.

tfq535 said:
Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.
Click to expand...
Click to collapse
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessary but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.

portezbie said:
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessar but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.
Click to expand...
Click to collapse
Thanks again, it worked like a charm.

bert_747 said:
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .img file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
Click to expand...
Click to collapse
Thanks for the guide.
The link to your screenshot is missing.

PMikeP said:
Thanks for the guide.
The link to your screenshot is missing.
Click to expand...
Click to collapse
Sorry bout that, screen shots should be working.

a little question,
is it possible to get xfstk files to restore a corrupt bootloader?
thx,,,

ASUS Flashtool doesn't start flashing
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong

These instructions do not work for Ubuntu. I find it very hard to believe that there is only a Windows version of the flash tool available.

Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.

Yes you can upgrade
Servaas said:
Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.
Click to expand...
Click to collapse
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles

edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.

Servaas said:
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.
Click to expand...
Click to collapse
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work

edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
edu47 said:
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work
Click to expand...
Click to collapse
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.

Servaas said:
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.
Click to expand...
Click to collapse
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.

edu47 said:
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.
Click to expand...
Click to collapse
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.

Servaas said:
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.
Click to expand...
Click to collapse
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/

edu47 said:
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/
Click to expand...
Click to collapse
This zip file also doesnt register, nothing pops up and no, when pushing the update button it also does nothing.
It would seem that the OP provided a nice 5.0 raw file that renders your tablet un updateble.
I'll be returning this tablet and going for the only available option in the netherlands the samsung 8 incher.

Z580C tablet is bricked, it happened on update, I think battery was too low. Screen is black all the time, under windows device manager it connects as other devices, MOOREFIELD device with no drivers and I can hear from windows sounds that it reboots after some time. All post #1 drivers are installed.
Please help.
Thank you

magnus_bn said:
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong
Click to expand...
Click to collapse
Had the same problem and what I did to make it work was.
1. Lunch Asus Flash Tool
2. Connect device in download mode (volume up + power)
3. Wait for device to be visible in Asus Flash Tool ( Serial number + blue dot) - you may need to restart tablet using reboot droidboot
4. Select model number
5. Point to raw file and choose to erase data (accept the prompt )
6 Hit Start
What I also did prior to that was factory reset of tablet
hope that helps you

[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro

Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64

Nice, that is what we need .. Thanks Liam

How can i load twrp? Fastboot boot command, didnt work

DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread

Not working for me get a error file is to large to download when try to flash

dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools

liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same

Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?

Not working for me. Both sims dissapear and phone keeps FC.

pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"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 see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app

error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash

pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared

liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app

NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc

Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it

mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?

liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1

Great thanks!
But can we update OTA to B2 with this?

@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?