Database Info

[Q] Bricked SGS4G

Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have 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"
}

What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide

Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.

Major kudos to diego930 for such a nicely detailed description of his problem!

Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.

Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!

When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.

ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.

Having issues with OPO adb

Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!

minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"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"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK

[solved] adb not recognising phone in fastboot(download) mode

Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.

Adb is adb.
Fastboot is fastboot.
For adb, you need adb binaries.
For fastboot, you need fastboot binaries.

I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?

kiwigi said:
I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?
Click to expand...
Click to collapse
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool

d
VD171 said:
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Click to expand...
Click to collapse
Thanks
Done that. PC is not recognising phone in download mode(fastboot)

kiwigi said:
d
Thanks
Done that. PC is not recognising phone in download mode(fastboot)
Click to expand...
Click to collapse
Probably because you didn't have drivers installed.
You need to find the specific drivers for your device model and install it.
Good luck.

VD171 said:
....
You need to find the specific drivers for your device model and install it.
..
Click to expand...
Click to collapse
I have searched for hours and all I have found seems not to be compatible with S7 sm-g930f. I have also followed this https://androidadbdriver.com/ specific to my mobile.
{
"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"
}

Did you really try to find ?
Here is the download for samsung usb drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Install it and reboot.
If it doesn't work, probably you have any problem in your device manager.
I'm an user linux and I hate windows.
Good luck google'ing it.

Im having the same problem. i don't want to use the adb setup thing becuase its a virus so yeah.

kiwigi said:
Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.
Click to expand...
Click to collapse
THANK YOU!!! From a fellow Kiwi. I followed a tutorial for my Nokia G20 and they left this part out! Faaaaar out. You're my hero

Bootloop Ulefone armor 6

Hello everyone, I have a big problem with my device, it happens that the system started to fail and after that it turned off, when I turned on it stayed in a bootloop and I can only access the fastboot, the question is that my device does not have the OEM and I never did any modifications so it doesn't have recovery either.
So far I have tried to install for fastboot the boot.img and system.img from the original firmware but I get the error "remote: not allowed in locked state" because the bootloader is locked
Any recommendation?

Reflash original Stock ROM by means of ADB Sideload method

jwoegerbauer said:
Reflash original Stock ROM by means of ADB Sideload method
Click to expand...
Click to collapse
but I can't use recovery and it doesn't have TWRP installed either.
The truth is that I am quite new to this subject but it would help me a lot if you guide me through that process.
In addition, the stock rom offered by ulefone is in .tar.gz format

Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...

jwoegerbauer said:
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
Click to expand...
Click to collapse
How about, I was trying to access with ADB, however when I put adb devices, the device does not appear, perhaps because I did not have the USB debugging before the bootloop, I was trying with different commands and nothing happens, but it does appear in the device manager. I'm sure I have the correct drivers because I tried another device with USB debugging enabled and it works fine.
Attached image
{
"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 should be obvious to you that ADB can't work as expected if USB debug option isn't got enabled on Android.

how can the bootloop be solved if only fastboot is available?
And the manufacturer flashing tool doesn't recognize the phone?
I cannot reflash the phone.

Question Made A Mess - ROG 5 CN Fastboot Loop

Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?

Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery 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"
}

Device is now back in a fastboot loop with no access to any options but power off & restart.

Your phone is broken
Buy a new phone and don't try to mess with it next time

Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.

yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.