• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Please Help! Can't install ROM via ADB Push

B

BoiledFunn

Newbie
Hi folks,
I'd really appreciate some advice as I've been at this for almost a day straight and it's getting a bit ridiculous.

Device is Galaxy s5 Sprint Sm-G900P
The last working ROM was stock 5.0 VPU1ANK4 - No rom is installed at the moment, despite my best efforts
TWRP Recovery installed

ADB version is up to date (V 1.0.32)

I've tried installing loads of different drivers, including the 'universal naked' drivers as suggest elsewhere.
I've tried different USB cables (2.0 & 3.0) and different USB Ports

The furthest I can get is to get ADB to connect to the device in recovery, but none of my push commands get anywhere with no action once the command is executed, even when left for 10-20 minutes.
I've tried pushing simple .txt files with the same result.

When I try flashing with Odin it fails.

Anyone have any ideas? I feel like I've exhausted every possibility. I've been trying to solve this for more than 12 hours....

Given that I have agreed to sell this device to someone, if anyone can solve my issues I'd happily give a donation/reward
smile.gif


Thanks guys!
 
Are you trying to adb sideload via TWRP?

I recently did a staff survey of that feature and results were all over the place.

I've been in close contact with one of the TWRP devs but they can't fix what they can't reproduce.

I've seen it work and fail but I've concluded that a lot of it has to do with MTP timing on the pc - and thanks to the huge variations in how Windows responds to things depending on individual configurations, you're in a no-win game.

My advice - get a cheap OTG USB cable and usb stick, put your rom zip file on the usb stick - and use it as just another storage share in TWRP, install from there.

For a few bucks you can kiss the TWRP / adb headache goodbye.

Apologies if you're referring to some other aspect - tried my best to follow here. :embarrassed:
 
Hi there EarlyMon, thanks so much for your reply!

I wasn't using 'adb sideload' before. When in recovery, I was only unmounting system & cache, leaving only data mounted. It takes me a lot of ****ing around at this point (mounting, un-mounting, disable/enable MTP) in order to make ABD connect to the device in recovery.

However. I have just tried using the ADB Sideload function to no avail.

Here's the CMD commands:
E:\Users\Finn\Documents\ANDROID\platform-tools>adb devices
List of devices attached
9fac9b59 offline


E:\Users\Finn\Documents\ANDROID\platform-tools>adb devices
List of devices attached


E:\Users\Finn\Documents\ANDROID\platform-tools>adb devices
List of devices attached
9fac9b59 recovery


E:\Users\Finn\Documents\ANDROID\platform-tools>adb sideload ANK4.zip
loading: 'ANK4.zip'
error: device not found
 
What were your adb push commands looking like? I've had very spotty luck with adb sideload. I'd be going for...

adb push ANK4.zip /sdcard/

...noting the trailing backslash. How is the phone showing up in device manager when in recovery?
 
iowabowtech said:
What were your adb push commands looking like? I've had very spotty luck with adb sideload. I'd be going for...

adb push ANK4.zip /sdcard/

...noting the trailing backslash. How is the phone showing up in device manager when in recovery?
Click to expand...

Hi Iowabowtech,

When connected in recovery (confirmed in ADB CMD window) this is what the device manager looks like:
IaWPqap.png


The device is recognised asn android composite ADB Interface.
Also not that it shows up as MTP USB Device under Portable Devices.
 
EarlyMon said:
.

My advice - get a cheap OTG USB cable and usb stick, put your rom zip file on the usb stick - and use it as just another storage share in TWRP, install from there.

For a few bucks you can kiss the TWRP / adb headache goodbye.

Apologies if you're referring to some other aspect - tried my best to follow here. :embarrassed:
Click to expand...

I have just tried installing using a OTG + flashdrive and this is the terminal log on the phone:
Updating ppartition details...
Full SELinuz support is present.
MTP Enabled
installing '/usbstorage/g900PVPU1ANK4_G900PSPT1ANK4_SPR.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip'/usbstorage/g900PVPU1ANK4_G900PSPT1ANK4_SPR.zip'

So for some reason it doesn't recognise the .md5 in the zip?
I've tried another ROM zip with exactly the same result... :/
 
I think that the OTG USB stick failure means that using adb to push to the sd card won't be any better. If the pc is right, it may show if the phone is bad, as ibt said - but it's hard to ensure that the pc is right with a questionable phone.

In my experience, roms tend to not include an md5 file, you have to check the md5 yourself after downloading.

We provide a tool for that here -

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

Usually the download page or the development thread lists the correct value - if it doesn't match the md5sums value output, the download was bad.

Check your options in TWRP, make sure that you're not requiring an md5 to be present. I don't think that you do - it says that it's skipping the md5 check, that's normal.

Also make sure that the rom is OK with the Sprint version of the phone.

What version of TWRP are you using?

Does the TWRP file manager have any trouble seeing any of the files on the usb stick?

Same question for the sd card? Same question for internal storage?
 
Last edited:
EarlyMon said:
I think that the OTG USB stick failure means that using adb to push to the sd card won't be any better. If the pc is right, it may show if the phone is bad, as ibt said - but it's hard to ensure that the pc is right with a questionable phone.

In my experience, roms tend to not include an md5 file, you have to check the md5 yourself after downloading.

We provide a tool for that here -

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

Usually the download page or the development thread lists the correct value - if it doesn't match the md5sums value output, the download was bad.

Check your options in TWRP, make sure that you're not requiring an md5 to be present. I don't think that you do - it says that it's skipping the md5 check, that's normal.

Also make sure that the rom is OK with the Sprint version of the phone.

What version of TWRP are you using?

Does the TWRP file manager have any trouble seeing any of the files on the usb stick?

Same question for the sd card? Same question for internal storage?
Click to expand...

Oh shiiiiiit, have I been missing something very big and obvious here?
Am I right that ROM.tar.MD5 filesare only loadable through ODIN.
Do I need a .zip containing the ROM.tar to install via sd/otg?

In which case, how do I find that .tar file (in a zip?) OR how do I turn all of the .tar.md5 files I have (various stock roms) into installable .zip files?
 
Odin loads tar files.

TWRP uses purpose-built rom zips that have an embedded installation script that controls the placement of bits within the phone's protected storage partitions - they're not simple zip files.

Compatible rom zip files can be found here -

http://forum.xda-developers.com/sprint-galaxy-s5/development

Choose one that sounds appealing, download, check md5 checksum, and follow the installation instructions given in the chosen thread - details may vary by rom. You'll find some that need Odin and require firmware flashing - and you'll find some that you just use with TWRP, that's it.

Use your OTG-USB rig and you ought to be fine.
 
Last edited:
EarlyMon said:
Odin loads tar files.

TWRP uses purpose-built rom zips that have an embedded installation script that controls the placement of bits within the phone's protected storage partitions - they're not simple zip files.

Compatible rom zip files can be found here -

http://forum.xda-developers.com/sprint-galaxy-s5/development

Choose one that sounds appealing, download, check md5 checksum, and follow the installation instructions given in the chosen thread - details may vary by rom. You'll find some that need Odin and require firmware flashing - and you'll find some that you just use with TWRP, that's it.

Use your OTG-USB rig and you ought to be fine.
Click to expand...

Hi,
Sorry, I'm really confused by the whole md5 checksum thing. Could you explain a little more in depth?
What exactly would the file type be and what would it contain if I want to be able to install a Stock ROM from sd/OTG?

How exactly do I "Check md5 checksum"? I have downloaded the SDK-Tools that you linked me. I run the md5sums command on the .tar.md5 and once it's complete I'm given a string. What do I do with that to make this file usable without ODIN?

Your help is soooo appreciated. If I can't get this fixed by mid-day (2am now) then I'm going to have to cancel the deal with who I sold this too. I'd love give you something for your time :)

Cheers
 
BoiledFunn said:
Hi,
Sorry, I'm really confused by the whole md5 checksum thing. Could you explain a little more in depth?
What exactly would the file type be and what would it contain if I want to be able to install a Stock ROM from sd/OTG?

How exactly do I "Check md5 checksum"? I have downloaded the SDK-Tools that you linked me. I run the md5sums command on the .tar.md5 and once it's complete I'm given a string. What do I do with that to make this file usable without ODIN?
Click to expand...
You can't.

Let's try this -

http://forum.xda-developers.com/spr...ent/stock-rom-oa6-android-l-deodexed-t3023663

If you did not have Lollipop before (Android version 5) that post has links to a proper Odin (please try that one) and the firmware (please try theirs). Follow their instructions EXACTLY.

If you are ALREADY on the 5.0 bootloader just install the rom, you don't need Odin -

https://www.androidfilehost.com/?fid=95916177934525350

You'll see the md5 value for the zip file there. You check that zip with the md5sums tool, if you have a good download, it will say -

ea8622d30f6ec6a674c3a296513f5881

DON'T TRY IT ON AN OLD BOOTLOADER.

If you don't have the version 5 bootloader, and cannot get the above Odin and file to work, you can go a different way -

http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-adulterated-cm12-5-0-2-t2987665

You'll find two zip file downloads, install them in this order -

https://www.androidfilehost.com/?fid=95864024717072482

http://downloadandroidrom.com/file/gapps/5.0/gapps-lp-20141109-signed.zip

The second one you have to enter a capcha near the bottom of the page.

The md5 values you need are on each page.

Install one after another in TWRP, reboot, enjoy.

That's not stock but it is very good.
 
EarlyMon said:
You can't.

Let's try this -

http://forum.xda-developers.com/spr...ent/stock-rom-oa6-android-l-deodexed-t3023663

If you did not have Lollipop before (Android version 5) that post has links to a proper Odin (please try that one) and the firmware (please try theirs). Follow their instructions EXACTLY.

If you are ALREADY on the 5.0 bootloader just install the rom, you don't need Odin -

https://www.androidfilehost.com/?fid=95916177934525350

You'll see the md5 value for the zip file there. You check that zip with the md5sums tool, if you have a good download, it will say -

ea8622d30f6ec6a674c3a296513f5881

DON'T TRY IT ON AN OLD BOOTLOADER.

If you don't have the version 5 bootloader, and cannot get the above Odin and file to work, you can go a different way -

http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-adulterated-cm12-5-0-2-t2987665

You'll find two zip file downloads, install them in this order -

https://www.androidfilehost.com/?fid=95864024717072482

http://downloadandroidrom.com/file/gapps/5.0/gapps-lp-20141109-signed.zip

The second one you have to enter a capcha near the bottom of the page.

The md5 values you need are on each page.

Install one after another in TWRP, reboot, enjoy.

That's not stock but it is very good.
Click to expand...

Heya! Thank you so much EarlyMon. Thanks for putting up with my ineptitude :D

I've managed to flash some Rom's via recovery but still no luck with Odin. Odin is able to flash modems, recovery and PIT but no ROM's sadly.

I would really like to get this stock so that the buyer of this device doesn't have to manually update but that doesn't look like it's going to happen due to the bootloader for 5.0 not being available (yet) without Odin.

I'm about to install the version of CM that you linked. Due to that being a 5.0 Rom, will that load a lollipop bootloader that I might be able to install the Ao6 (5.0) stock firmware?
 
Roms consist of just a boot image (contains the kernel and startup code) and the /system partition.

Never any kind of firmware. No bootloader, modems or anything like that.

And you cannot install the tar with Odin that you got here?

http://forum.xda-developers.com/spr...in-sm-g900p-oa6-official-restore-rom-t3022826

(Notice that's a self-extracting exe, you don't need to worry about download errors, the exe will fail if it's wrong. No md5sums checking - it's not a rom zip.)

And you're using the Odin 3.09 from here?

https://www.androidfilehost.com/?w=files&flid=15340
 
Ah ok, thanks for clearing that up. I thought firmware and rom were interchangeable haha.

No luck with that tar :/
I've tried using Odin 3.09 & 3.10

Odin log:

<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SM-G900P_OA6_Stock_Nodata.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


Device Download Mode Log:

ODIN MODE
Product Name: S<-G900P
Current Binary Custom
System Status: Custom
Reactivation Lock(kk): off
Knox Warranty Void: 0x1 (4)
Qualcomm secureboot: Enable (csb)
RW SWREV: S1, T2, R1, A2, P1
Secure Download : Enable
UDC Start
SW REV CHECK FAIL : [aboot]Fused 2> Binary 1
 
BoiledFunn said:
I've tried using Odin 3.09 & 3.10

Odin log:

<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SM-G900P_OA6_Stock_Nodata.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...

We've been seeing the same basic nand write fail on the S6 as well. You mentioned using Odin 3.10 - is that 3.10.6? If not, you might give that a shot as that specific version allowed several of us S6 types to proceed when previous versions failed:

http://forum.xda-developers.com/showthread.php?t=2711451

I misunderstood your original intent. I first thought you were simply having issues with device recognition for adb push.
 
iowabowtech said:
We've been seeing the same basic nand write fail on the S6 as well. You mentioned using Odin 3.10 - is that 3.10.6? If not, you might give that a shot as that specific version allowed several of us S6 types to proceed when previous versions failed:

http://forum.xda-developers.com/showthread.php?t=2711451

I misunderstood your original intent. I first thought you were simply having issues with device recognition for adb push.
Click to expand...
No more luck with that version sadly, although I do find it slightly snappier than previous versions.
Thanks for your advice :) I thought ADB was the way to go at one point. I've tried everything! hahaha, ready to resign myself to non-stock until something new is released.

EarlyMon said:
Can you Odin flash this firmware?

https://www.androidfilehost.com/?fid=95916177934524239

If so, you will probably end up with the new bootloader and be able to do the rom install via TWRP.
Click to expand...

Negative.
How can I find out my bootloader? A quick google said to hold volume down + power? that doesn't get me anywhere. It just gives the standard rooted/custom kernel message in the top left and boots as normal :/
 
EarlyMon said:
Try the CM rom + gapps (linked earlier), let's see if we can at least install those two and make sure that the phone works.
Click to expand...
Sorry, I should have said earlier. Yes, i've got those installed fine. I seem to be able to install any rom apart from stock... haha, exactly the opposite of what I'm after!
 
You must log in or register to reply here.
Back
Top Bottom