Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
I tried to install cyanogenmod 12 onto my Moto G (2013 XT1031), and it was stuck in boot for 10 hours, so I put it into recovery, plugged it back into my computer, followed a forum on how to fix it, and now the drivers are gone. My computer can't communicate to my phone through USB. So now when I type "adb devices" it isn't listed, so I cannot push a stock img file to my phone to fix it. I've been looking forever for a fix... Could somebody here help me if you have any idea what to do. Thx.
Add me on Facebook. I'll help you. I had the same problem. www.Facebook.Com/mykehdoom
I will post here what I did to fix it, (if I do fix it) just in case anyone else comes here to fix their problem.
You should always keep a backup or stock ROM zip on SD card or USB otg. And you shouldn't have this problem as long as you can boot to recovery. I've found the quickest way to get any Lollipop ROM to boot since the first official CM12 nightly is to install Donkey Kang kernel. Most of the time they'll stay on boot animation forever until I do. I have an XT1031 too. A Leaf micro SD card reader or a Leaf bridge are well worth the cash. They've saved me from having to use my PC to get out of a jam every time, and I've flashed almost every build of every ROM that will flash on this phone.
Bellablue2 said:
I tried to install cyanogenmod 12 onto my Moto G (2013 XT1031), and it was stuck in boot for 10 hours, so I put it into recovery, plugged it back into my computer, followed a forum on how to fix it, and now the drivers are gone. My computer can't communicate to my phone through USB. So now when I type "adb devices" it isn't listed, so I cannot push a stock img file to my phone to fix it. I've been looking forever for a fix... Could somebody here help me if you have any idea what to do. Thx.
Click to expand...
Click to collapse
Have you tried restoring stock via fastboot? http://forum.xda-developers.com/showthread.php?t=2542219
If you wish to keep the contents of the internal storage, skip the erase userdata part. At least until you can backup what you want off it.
dominati said:
Have you tried restoring stock via fastboot? http://forum.xda-developers.com/showthread.php?t=2542219
If you wish to keep the contents of the internal storage, skip the erase userdata part. At least until you can backup what you want off it.
Click to expand...
Click to collapse
No, the problem was that my computer could not do anything to the phone, they would not interact at all. ADB couldn't sense the phone. I did fix it, however. Here is what I did:
1.Open Device Manager
2.Plug in phone
3.See if a new device pops up when device is plugged in.
4.Right click the device: Properties
5.Update Driver
6.Browse Computer
7.Pick from list of Drivers
8.Uncheck "Show compatible Hardware"
9.Manufacturer: Motorola
10.Motorola USB Composite Device
11.Next
12.Follow through and wait for it to set up your driver, then device.
13.After that, adb could find my phone.
So, here's the story: I wanted to root my d850 on LP version D85021R, Tried all methods posted here, including this, this, and this. None worked. So I decided to downgrade to KK using tot/kdz method by hyelton. Downloaded LGD850AT-01-V10d-310-410-JUN-19-2014+0.tot file and LG flash tool 1.8.x and flashed the tot file. Progress went above 85% and then phone rebooted, but never came back to life; super-bricked, no led, no boot screen, no download mode, no recovery mode, NOTHING! except that it identified as QHUSB_BULK in Win7, which upon installation of drivers turned to qhsusb_dload 9008. Tried all unbricking methods including Board Diag, Flashtool ,etc. none worked. So I took it to a repair guy, who probably used octopus box to copy image from another g3 (at least that's what I think, he would not let me see but i sort of glanced over). After copying that image to my g3, it turned back to life, i.e., boot screen appeared and download mode/recovery mode worked, but it was in a boot loop. however, that guy also tried flashing V10D using flashtool, and same thing happened, i.e., super-brick again. After a day of trying he gave up on it but was kind enough to give it back half alive. So now boot screen appears, download mode works, gets recognized as LGE Mobile USB Serial Port, and LGE Android MTP Device with a yellow triangle. I cannot access fastboot mode due to locked bootloader, or else I would have tried flashing partition images through fastboot, as bootloader and boot partitions are intact, so I would not touch them but could try flashing other partitions. LG Flashtool flashes the whole package so the boot sector also gets over written, which somehow is not compatible with stock rom. One thing which I have not mentioned is that I did not buy it new but refurb one, so may be some part was changed, but which one, no idea. I tried to get it recognized it in linux, but does not work; shows up as libmtp-1-1 in /dev, which is not mountable. However I was able to pullout one interesting fact, which might give some hint. dmesgs shows a serial number for this device which starts as LGD855xxxxxxx, whereas the serial number printed on the back is different, where it shows as d850 and serial number is also different, i.e., 406KPXVxxxxxx.
Now I am out of options. Can someone please suggest what else to do. Also, can someone confirm that the serial number shown in dmesgs when connected to USB port, starting with LGD855xxxxxx can be a d850?
Any help is welcome
First off when flashing almost every time it'll fail at 85%. That's normal. Anything after80% is just rebooting of the phone.
Now what your having is not normal. Maybe whatever the repair shop did changed the serial? And your issue usually means your bricked completely sadly.
Before your downgraded, was your phone booting normally or did the root do something to make it originally boot loop before trying to downgrade ?
Sent from my iPhone using Tapatalk
Thanks for replying hyelton. I fully understand that and also that rebooting should bring the phone to blue reset screen, but it didn't. Instead it died.
The serial number and IEMI fortunately are intact, and are read by firmware when present. Sadly I tried to flash the firmware again through Board DL option, but failed again, so back to QLoader 9800 mode. On WinXP, smart boot diagnostics recognized it and proceeded to flash boot/recovery, but sadly the accompanied AP_Chip file neither has D850 nor D855 Smart_Boot.bin files. So I flashed EUR xxxx.xxx version. Phone still dead, but no Qloader 9800 mode, instead Android Phone device started showing up, which had no supported drivers. After some effort, Windows 7 download drivers and it got recognized as AlCatel Android Phone, lol! No adb and fastboot in Windows, and no Serial communication was possible. I tried linux and there fastboot was showing a device without id, like ??????????, but it did allow me to flash individual mbn paritions extracted from D850 tot to their respective partition, but I discovered I cannot flash through fastboot files larger than 2GB, so no system and no userdata; those were erased only. Upon reboot and return to windows, phone is still dead (without any life) and back to Qloader 9800 mode.
So now I'm stuck due to lack of firmware files. I am afraid to flash a boot or recovery partition extracted from any other firmware, but can try D855 since it worked partially to bring download/recovery partitions and LG logo was also displayed upon turning on. I think it even booted basic kernel in download mode, because I was able to send reboot command through Send_Command.exe and it rebooted. So scripting was also a possible option, but not anymore.
Is the partition layout of D850 and D855 available somewhere? I tried to find but could only find for D851. If someone having these variants is willing to help, I'll post the commands to get partitions layout, or even partition images could be created using dd command if phone is rooted.
To your question, no, the rooting methods did nothing. It was working normal. But somehow I came across a lot of threads that suggested hassle-free downgrading to KK for rooting, and pointed to your guide which surely is hassle-free but not for a troubled phone like mine
BTW, I do have Flashtool log files for original downgrade and then reflashing yesterday. If someone wants to take a look...
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
unikorn74 said:
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
Click to expand...
Click to collapse
Flash it to D855 Lollipop version via octopus than write DUMP
It does work, indeed. We did it together, didn't we, aamszia?
To elaborate further, Aamir helped me out by writing D855 bootloader through octopus box. That was done before but flashing a KK rom again bricked it. Only this time, he flashed a d855 lollipop kdz rom (v20g, if I remember correctly). That made it functional; everything worked, except radio. Flashing a d850 LP radio would not work; flashing a KK radio would brick it. So I took a dump of mmcblk0 from a fully functioning, rooted, recovery flashed LP d850, via terminal using dd command (I chose to write only first 4gb or so due to smaller sdcard I had. That covered all partitions except cache and userdata, which were not needed anyway). Then I wrote back the dump on the bricked d850 using dd command from terminal. I tried flashing TWRP on it first, but somehow it did not work, and gave secure bootloader error. So I had to do it via terminal. I knew once it starts writing, the system would become unstable due to overwriting of partition table, kernel, system, and stuff, but I had to give it a try, and it worked! Screen went off immediately, but I touched it again after half an hour; pulled out and reinserted the battery; tried recovery and there it was. Rest was easy. Just formatted cache and data, and my phone was back to life.
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
ZiggyJapheth said:
How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
Click to expand...
Click to collapse
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
O
SubwayChamp said:
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
Click to expand...
Click to collapse
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
ZiggyJapheth said:
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
Click to expand...
Click to collapse
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
ZiggyJapheth said:
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
Click to expand...
Click to collapse
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
SubwayChamp said:
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
Click to expand...
Click to collapse
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files. That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin. So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
ZiggyJapheth said:
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files.
Click to expand...
Click to collapse
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
ZiggyJapheth said:
That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin.
Click to expand...
Click to collapse
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
ZiggyJapheth said:
So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
Click to expand...
Click to collapse
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
K
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse
Ok, thanks so much,I'm about to download mobile Odin first , altho i think i tried that and it needed SuperSU permissions which the moto E5 isn't rooted...so looks like I'm about to research your other suggestions. It gives me a direction to experiment in. Again,thanks so much. Oh one last thing.. but it is sending files to the phone in sideload form. Because before it aborts, the phone I'm sending files from goes through a percentage until 100% of any given file is sent. And on the galaxy i see it received because it says installing this or that zip file before saying...updates fron external sources disabled and aborting mission. I'll be back. Thanks for the time bro
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse