Develop Bugs

Flashing Gio from ODIN with .tar.md5

I dowloaded my stock firmware from samfirmware.com and now i would like to flash it. It is a single tar.md5 package. I would like to known how to flash it. I searched, but it was not much help to me. Do i use the single package option in ODIN?
- i have never used odin, but i have flashed alot of roms so im not completely stupid when it comes to this stuff.

Yes, one package

Once you have Odin
To do so
The file "GIO_v0.1.ops"
You will find in the package of Odin
{
"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"
}
You put the file you downloaded md5
How do you see "PASS!" disconnect and if appears
"Close serial port and wait until rebooting" a disconnect, and wait until the phone turns on, of course, disconnect the cable.
It says Samsung on the phone remove the battery and enter the Recovery Menu
select "wipe"
select reboot
READY
I already have the new rom

Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?

AlwaysDroid said:
Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?
Click to expand...
Click to collapse
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium

Cant find?
voetbalremco said:
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
Im trying to flash a file called S5660MUGKG3_S5660MBMCKG3_BMC. When ever i try to one package i cant seem to find it? Can anyone help me with this?

Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
How do I unzip it? Can I use winrar and extract?

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
Yay I got it!
Thanks for your help!
Is it fine if it says 1 (COM10) ? and also its keeps on showing the boot animations over over... wont go further and on odin it says pass. should i keep on waiting or is somthing wrong? is it bricked?

1 (COM10) is simply to indicate the serial port number assigned to your phone by Windows and the Samsung USB driver in Odin.
Your phone is boot looping, some might consider this a soft brick. My best guess is that you previously installed a ROM that formatted your /data and /cache partitions from the stock RFS format to ext4 instead. The stock 5660M ROM doesn't support ext4.
Reboot in the stock recovery, either with "adb reboot recovery" or by using the home and power keys simultaneously.
From there, wipe user data and cache, or something similar I don't recall the exact wording, but I do remember they were two separate commands.
Reboot, should work now. Use ddms (part of the Android SDK) to see what's going on under the hood if you feel like it.
I take it computers are a relatively new thing for you to ask how to unzip files. My best advice: make very regular backups and read instructions carefully. Losing data is not cool. Losing someone else's data is worse. (I'm guessing you're on the family computer here...)

Adb sideload error

hi, I've tried to clean install oos 4.0.3 with adb side load and it show me error 'cannot read .zip'
when I enable adb trace, it show me error like this
adb sideload ota.zip
load_file: 324: 1020 | load_file: could not allocate 1504196936 bytes
* cannot read 'ota.zip' *
anyone can help me ?
{
"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"
}

Yep known error, wrong drivers, not much known of the issue. Do you have TWRP? Then type adb push zipfile /sdcard/ then you can manually flash it.

Puddi_Puddin said:
Yep known error, wrong drivers, not much known of the issue. Do you have TWRP? Then type adb push zipfile /sdcard/ then you can manually flash it.
Click to expand...
Click to collapse
1.I'm not sure cause of wrong driver because I just sideload oos Open beta 11 3 days ago, and it work well;
2. yep I've TWRP, but I want to find down why I got this bug

isibiki said:
1.I'm not sure cause of wrong driver because I just sideload oos Open beta 11 3 days ago, and it work well;
2. yep I've TWRP, but I want to find down why I got this bug
Click to expand...
Click to collapse
Oh ye even weirder.. have you tried "adb kill-server"? Maybe rebooting the PC while keeping the phone plugged in? Last one helped for me once.. But i still cant sideload either.

Puddi_Puddin said:
Oh ye even weirder.. have you tried "adb kill-server"? Maybe rebooting the PC while keeping the phone plugged in? Last one helped for me once.. But i still cant sideload either.
Click to expand...
Click to collapse
I tried everything like re-install driver, adb kill-server, larger address adware and more, but it didn't work. Luckily oos stock recovery can install from internal storage or flash twrp and install throught it

You are on a 32 bits windows computer. Which is unable to load the entire file in memory on default settings.
You should try this:
jstegeman said:
I will point out that adb.exe on Windows is not linked to be "large address aware" If you set the environment variable ADB_DEBUG=all and try to adb sideload a large file, you'll see that the call to malloc is failing to allocate enough memory for the file. The "obvious" fixes would be for adb not to try to read the entire file into memory or to be linked with the /LARGEADDRESSAWARE flag on Windows.
As a workaround, I've used https://www.techpowerup.com/forums/threads/large-address-aware.112556/ to make adb.exe large address aware, and it's now working for me.
Click to expand...
Click to collapse

JorgeManuelSilva91 said:
You are on a 32 bits windows computer. Which is unable to load the entire file in memory on default settings.
You should try this:
Click to expand...
Click to collapse
My computer running 64 bit windows 10 and I already tried this solution and it didn't help me resolve this bug

isibiki said:
My computer running 64 bit windows 10 and I already tried this solution and it didn't help me resolve this bug
Click to expand...
Click to collapse
Then, your computer may be out of RAM, check how much RAM your computer has and close programs you're not using.

JorgeManuelSilva91 said:
Then, your computer may be out of RAM, check how much RAM your computer has and close programs you're not using.
Click to expand...
Click to collapse
8gb ram with 56% free memory isn't enough ?, I think it because L Speed app I install in my phone, after install it, I cannot full unroot in super su app and this adb error happened after that.

isibiki said:
8gb ram with 56% free memory isn't enough ?, I think it because L Speed app I install in my phone, after install it, I cannot full unroot in super su app and this adb error happened after that.
Click to expand...
Click to collapse
Check this topic on OnePlus forums: https://forums.oneplus.net/posts/15306505
I had the cannot read 'update.zip' issue. Turned out it'd been installed as the wrong device in Windows 10 - it'd been recognized as a Marshall London Phone for some reason. To fix it, I removed it from device manager, and told it to delete the drivers. Then rescanned, and reinstalled it as a standard Android ADB Interface - it then accepted the file on the sideload. Drove me mad for a couple of days!
Click to expand...
Click to collapse

can someone help me with H815 misc partition img file

I have mistakenly erased misc partition and have no backup for it so my WIFI dosen't work for me
I've copied the way to make misc.img file from https://forum.xda-developers.com/tmobile-g4/help/request-h811-misc-partition-image-t3516353 and it's below
===============================================Misc.img=====================================================================
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
===============================================Misc.img=====================================================================

OriginLua said:
I have mistakenly erased misc partition and have no backup for it so my WIFI dosen't work for me
I've copied the way to make misc.img file from https://forum.xda-developers.com/tmobile-g4/help/request-h811-misc-partition-image-t3516353 and it's below
===============================================Misc.img=====================================================================
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
===============================================Misc.img=====================================================================
Click to expand...
Click to collapse
If you have a copy of your kdz for your model and software version for your specific carrier or can obtain one, you could use SALT to extract all your .image partition files yourself ... it could prove more handy doing it this way in the long run when issues arise.

sdembiske said:
If you have a copy of your kdz for your model and software version for your specific carrier or can obtain one, you could use SALT to extract all your .image partition files yourself ... it could prove more handy doing it this way in the long run when issues arise.
Click to expand...
Click to collapse
{
"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've tried what you said but kdz doesn't hold misc image

OriginLua said:
I've tried what you said but kdz doesn't hold misc image
Click to expand...
Click to collapse
Copy your post with the screen shot over to the SALT thread.

Q beta 5 is GREAT,but can not mount /system for now

I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)

seardna said:
I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)
Click to expand...
Click to collapse
Happened to me before. I believe I cleared the system partition and it worked.

TechNash said:
Happened to me before. I believe I cleared the system partition and it worked.
Click to expand...
Click to collapse
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .

seardna said:
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .
Click to expand...
Click to collapse
Latest TWRP from website, magisk stable

TechNash said:
Latest TWRP from website, magisk stable
Click to expand...
Click to collapse
Thanks. But can you mount system in the TWRP? While install Magisk , there are some errors failed to mount /system (Invalid argument )

Would this be why titanium backup doesn't open either ??

this happened with beta 4 also. don't know if it's twrp or magisk issue

Q5,same issue here, tried everything, factory reset, format partition, no luck
apart from this, everything works
in root explorer, you can't mount R/W

A latest magisk alpha version maybe solved this problem .
Here is the custom channel :backup up FIRST!
https://raw.githubusercontent.com/yzkpqv68745/magisk/master/alpha.json

solución
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.

ismael47 said:
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.
Click to expand...
Click to collapse
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this

{
"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"
}
[/IMG]
darkoj2007 said:
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this
Click to expand...
Click to collapse
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.

I'm on official release 10.0.0 (QP1A.190711.020, Sep 2019) flashed without "-w" over android 9. Pixel 2.
Flashed latest TWRP (3.3.0-0) and 19.3 Magisk, then latest canary. Nothing helps.
Did you manage to find solution? I would appreciate any help.

ismael47 said:
[/IMG]
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.
Click to expand...
Click to collapse
Dude that does seem to work at least for the magisk install. It doesnt help fix other issues like adaway and titanium backup from not being able to mount system though!
Appreciate your effort anyway

There's a setting in magisk that'll allow you to install adaway. Systemless hosts...tap it then reboot and adaway should install.
That worked for me.

I was able to get /system to mount by going to Advanced Wipe and selecting 'system' and choosing repair -> Change File System - EXT2 then go back and switch it back to EXT4.
I have not been able to get /vendor mounted and I believe it is because the syntax used has changed.
I read that AOS10 uses a form of EXT4 that preserves it as ready only, possibly by filling the used space of the drive preventing any writing.
This explains some of the new obstacles TWRP must compensate for in order to maintain compatibility w/ AOS10
https://source.android.com/devices/architecture/kernel/mounting-partitions-early
I have had luck installing Magisk by enabling USB Debug and typing in ADB shell:
cat /dev/block/sda19 > /sdcard/boot.img
Open Magisk and chose to install to file and select the boot.img.
Replace boot.img in the zip file that contains Android 10 factory firmware.
Current Marlin factory firmware [ https://dl.google.com/dl/android/aosp/marlin-qp1a.191005.007.a1-factory-c27241e0.zip ]
Inside marlin-qp1a.191005.007.a1-factory-c27241e0.zip is another archive: image-marlin-qp1a.191005.007.a1.zip ; inside this archive is boot.img.
Using 7zip you can open this archive and drag / drop boot.img replacing the stock image with the Magisk patched one.
Run Flash-all.bat, note it *WILL Wipe* your device but include a Magisk patched boot.img.
Once you finish initial setup of phone, download magisk manager and when you open it, it will automatically patch and reboot your phone enabling root. (make sure you have internet connection before opening magisk manager)
After you have root enabled phone you can customize /system to your liking and then cat /dev/block/sda33 > /sdcard/system.img to replace the firmware version.
(Still am not able to load /system as RW using FX, so have yet to be able to modify .props)
You can locate the various links and identify if you are using slot a/b by typing in TWRP terminal : ls -la /dev/block/by-name/
Side note:
The wizard himself has delicate and important matters of being a present father and managing the obstacles of keeping the brood happy-content and also providing nurturing support to the new addition and persistent validation for the wifey. [Congrats])
(apologies for improper formatting de-pretyfied by inotoxication)

fastboot.exe doesn't work

I want to flash a boot.img to Xiaomi 6, but fastboot does not work anymore.Device unlocked
fastboot.exe can recognize my device
{
"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"
}
When I type the command, it gets stuck here
Then i unplug the cable
I am using windows 10
help please...
fastboot.exe version
driver version

Does your "boot.img" inside the target folder? in your case inside "platform-tools" folder?
I recommend install ADB installer from this forum https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or just download it here;
ADB Installer : ADB Installer V1.4.3
After done installing
Create new folder in your Desktop
Copy and paste your boot.img inside the folder
Inside the new folder press and hold "Shift" in your keyboard, Right click and choose "Open command prompt windows here"
Reboot your Phone into the bootloader
Connect your phone
And flash your boot.img as you do it before :good:

Shimizux said:
Does your "boot.img" inside the target folder? in your case inside "platform-tools" folder?
I recommend install ADB installer from this forum https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or just download it here;
ADB Installer : ADB Installer V1.4.3
After done installing
Create new folder in your Desktop
Copy and paste your boot.img inside the folder
Inside the new folder press and hold "Shift" in your keyboard, Right click and choose "Open command prompt windows here"
Reboot your Phone into the bootloader
Connect your phone
And flash your boot.img as you do it before :good:
Click to expand...
Click to collapse
Thank you for your reply!
I used adb installer and uninstalled the original driver.
It's stuck here.I unplugged the cable and it did not respond.
I'm sure boot.img is in the current directory.

Tubby Custard said:
Thank you for your reply!
I used adb installer and uninstalled the original driver.
It's stuck here.I unplugged the cable and it did not respond.
I'm sure boot.img is in the current directory.
Click to expand...
Click to collapse
Sorry i dont understand, where do you stuck?
By the way, do you have custom recovery (TWRP) install on your phone?
You can flash boot.img with TWRP instead of using fastboot method

Also had this issue. At one PC worked well, but at another no. Changing USB ports or cables does no matter.
Try to use old pure USB2.0 Hub. In my case D-Link DUB-H7 (in metal case) completely solved the problem.