Related
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
omni_angel7 said:
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
Click to expand...
Click to collapse
If your on linux it's "./moto-fastboot" not just fastboot.
Windows 7 64 bit. sorry, should have specified.
Nobody with win 7 knowledge/advice?
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Diviance said:
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Click to expand...
Click to collapse
Thanks SO much for the quick response and all the effort I'd actually updating OTA from 1.26 because I flashed back, thinking no one was gonna help! Well, when I feel up to it another night. I'll give this another shot. Thanks for the custom fastboot, too!
i get < waiting for device >
did i do something wrong?
Me too. ^^^^^^^
I figured it out, i forgot to put it into fastboot mode!
did not work for me
when I do what you told the other guy it says system cant find the path specified couls you please help I have spent a couple of days trying different things and also when I try to erase the recovery installer file it want let me
Please help. I just want to reset to anything that will work. I have access to CWM. I have deleted all backups (I know...) I have WSG Rom and Wooky (which doesnt like CWM) on the internal SD card. I can't stop getting bootloader loops. I have made some mistakes trying to fix this. I just want anything (ADB or whatever) that will get me to a working tablet. I know this is vauge, please help. WHen I flash WSG it goes to the ASUS screen with the circle that keeps flashing as it rotate- not the image below. I have tried reading about fastboot, which I can enter, but I am unsure how to use it.
...
No this is an easy fix after you do a bit of reading! You need to fastboot flash TWRP and then WIPE and then push a rom to your device through adb.
You'll find TWRP in the development section, I'm guessing your on the stock bootloader (not androidroot), if so read back a couple of pages in the thread and you'll find a link to their older versions. On the first post you'll find a link to their website where you'll find instructions to fastboot flash their recovery.
Also in development section you'll find a thread called How To Un-Brick Your Prime. In there you'll find downloads and instructions for both ADB and Fastboot.
Reading a bit through these post you will learn alot and easily unbrick your device now, and the next time your in trouble.
Hope this helps....
I suggest you go here first http://forum.xda-developers.com/show....php?t=1426502 download and install naked drivers
Then go here http://forum.xda-developers.com/show....php?t=1774352 download and unzip nvflash
Then go here http://forum.xda-developers.com/show....php?t=1615990 download twrp and place it inside the nvflashpack directory where you see adb.exe
Then go here http://forum.xda-developers.com/show....php?t=1782413 download EOS 3
or
Go here http://rootzwiki.com/topic/32357-rom...ckbean-2-8-15/ and download bakedbean 3
Put either one in the nvflashpack directory where adb.exe is or if you have an external sdcard, load a rom onto it (preferred method)
I am not a fan of cm10 though it has some nice features I wouldn't start with it...
Now the hard part....
Go here and follow the instructions http://androidroot.mobi/t3_nvflash/
As per the instructions put your prime in fastboot mode...
to you start a command prompt, open the nvflashpack directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
Work your way all the way to the end until you see coming soon...
In the end you will have the modified bootloader required for the latest version of twrp (cwm doesn't work as well as twrp on the prime)
Now follow the instructions to install twrp this can be done through fastboot or through goo manager (download from market if you want to go the goo manager route)
Once that is complete with the prime still plugged into the pc, boot into twrp, now depending on if you have put the rom on an external sd card or not... if on sdcard, have it inserted before going into twrp, and install the rom from the card otherwise you can adb push the rom to the prime it will be adb push /name of rom.zip/ sdcard Note that the rom has to be in the same directory as adb.exe for this to work otherwise you need to type the path....for the name of the rom I suggest right clicking the file, go to properties and copy the name, then right click and paste in the command window... this eliminates mistakes.. and don't forget the.zip part.. the push will take about 5 minutes...
Then install the rom from twrp.....
My new phone received an OTA in the form of a 'dlpkgfile' file. Since I'd already rooted and installed CWM, it fails. BUT, I'd like to see what's inside, before I try the work-around found elsewhere on XDA.
I can't find anything through Google.
I have figured out the following chunks.
Code:
0x00000000 - 0x000000f4: Mystery header
Size
0x000000f5 - 0x0003f0b3: lge_fota executable (0x0003,EFC0 -> 257,984 bytes - matches)
0x0003f0b4 - 0x00362cf4: ??? (ends with "Y A F F S") (0x0032,3c40 -> 3,292,224 bytes, ~3.140 MB)
0x00362cf5 - 0x0038315a: fota_script.txt (0x0002,0465 -> 132,197 bytes)
But how do I disassemble/decompile/unpack/extract/view/dump this file????
same question . Anyone know the 'dlpkgfile' format???
It's a zip file.
You can use the linux unzip utility. (It comes with busybox... if you have rooted your device you likely will have it. )
Alternately, you can open with 7zip on a windows pc.
If your device is rooted but dosen't have busybox... google is your friend you will need the arm binary (may need to check your arm version)
I know this is an old post but I too found little out there... So might be helpful to those in the future.
Just FYI:
Inside you will find the updater-script file located at: META-INF/com/google/android/updater-script.
This is the main script used to check file sha1sums before applying patches to files on your device. If your files being patched have been modified then the script will abort the update. Unfortunate the entire package is signed and any changes made to any files there in will be detected and the update will not be permitted run. But it can be useful to see what files are being checked / patched and what there sha1sum is expected to be.
toy4x4xda said:
It's a zip file.
You can use the linux unzip utility. (It comes with busybox... if you have rooted your device you likely will have it. )
Alternately, you can open with 7zip on a windows pc.
If your device is rooted but dosen't have busybox... google is your friend you will need the arm binary (may need to check your arm version)
I know this is an old post but I too found little out there... So might be helpful to those in the future.
Just FYI:
Inside you will find the updater-script file located at: META-INF/com/google/android/updater-script.
This is the main script used to check file sha1sums before applying patches to files on your device. If your files being patched have been modified then the script will abort the update. Unfortunate the entire package is signed and any changes made to any files there in will be detected and the update will not be permitted run. But it can be useful to see what files are being checked / patched and what there sha1sum is expected to be.
Click to expand...
Click to collapse
Sorry but i cannot extract dlpkgfile, cannot open with 7zip
hoangnova said:
Sorry but i cannot extract dlpkgfile, cannot open with 7zip
Click to expand...
Click to collapse
It was explained to me that the LGE_FOTA file is the extractor for the dlpkgfile. I'm trying to open the file contents of a dlpkgfile as well.
Can you tell me how to?
---------- Post added at 05:10 PM ---------- Previous post was at 05:10 PM ----------
TekGadgt said:
It was explained to me that the LGE_FOTA file is the extractor for the dlpkgfile. I'm trying to open the file contents of a dlpkgfile as well.
Click to expand...
Click to collapse
Can you tell me how to extract?
hoangnova said:
Can you tell me how to?
---------- Post added at 05:10 PM ---------- Previous post was at 05:10 PM ----------
Can you tell me how to extract?
Click to expand...
Click to collapse
That is all I know. I have no idea how to use it. Sorry. If I did, I'd have extracted the contents of mine already.
It seems that flashing a modem on the GS5 can be real pain. Even using a pc w/odin the modem doesn't always stick.
I've been messing around with terminal emulator trying to figure it out. I pieced together a small script that is letting me flash a modem. Its easy and fast for me, so i thought I'd try to share it here.
It is working on my phone without fail, but that doesn't always mean it will work for others.
If anyone is up for trying this out on their phone there are instructions below. However, There is some risk.
DO NOT TRY THIS if you are not experienced with flashing modems. This could possibly soft brick your phone. It could possibly break, or erase your current modem.
If you don't know how to fix it, (i.e.
recover from softbrick, have the ability to flash modem with pc) YOU SHOULD NOT TRY THIS.
If you are comfortable with that then please go ahead and tell me if it works for you:
You will need the modem.bin file extracted from any of the stock .tar.md5s available.
Here is BNG4 if you need one.
https://docs.google.com/file/d/0B4OeXSTx8tgBWGlHWU1mVDZ0cDQ/edit?usp=docslist_api
Make sure the modem.bin is stored on your internal sd. Path: /storage/emulated/0/ -Not in the download folder.
Once you have the modem.bin on your internal sd, you will open terminal emulator. Make sure you are running as superuser.(type: su then hit enter)
Now, just copy and paste this exactly as it is below into terminal and run it(enter)
---------------------------------------------------------
#!/system/bin/sh
# variables
partition="/dev/block/platform/msm_sdcc.1/by-name/modem"
modem="/sdcard/modem.bin"
busybox="/system/xbin/busybox"
# main
$busybox dd if="${modem}" of="${partition}"
-----------------------------------------------------------
Once you hit run, it will take a second or up to 10 before it outputs a confirmation. It should show 100000ish+1 records in/out and copied modem.bin size MB and speed in MB/sec.
Reboot your phone and thats it.
The baseband version should now be updated in settings and anywhere else you might find it.
Ian the Great said:
It seems to be very difficult if not impossible for to flash modems on GS5 without using odin and pc.
I've been messing around with terminal emulator and peiced together a small script that will flash modems for me.
It is working on my phone without fail, but that doesn't always mean it will work for others.
I'm looking for a few volunteers to try this method and confirm if its working for them or not.
HOWEVER, DO NOT TRY THIS if you are not experienced in flashing modems. This could possibly soft brick your phone. It could possibly screw up, or erase your current modem. If you don't know how to fix it (i.e. recover from softbrick, have the ability to flash modem with pc) YOU SHOULD NOT TRY THIS.
If you are comfortable with that then go ahead:
You will need the modem.bin file extracted from any of the stock .tar.md5s available.
Here is BNG4 if you need one.
https://docs.google.com/file/d/0B4OeXSTx8tgBWGlHWU1mVDZ0cDQ/edit?usp=docslist_api
Make sure the modem.bin is stored on your internal sd. Path: /storage/emulated/0/ -not in downloads folder.
Now open terminal emulator and make sure you are running as superuser.(type: su then hit enter)
Then just copy and paste exactly as it is below into terminal and run it(enter)
---------------------------------------------------------
#!/system/bin/sh
# variables
partition="/dev/block/mmcblk0p2"
modem="/sdcard/modem.bin"
busybox="/system/xbin/busybox"
# main
$busybox dd if="${modem}" of="${partition}"
-----------------------------------------------------------
Once you hit run, it should take a second or up to 10 before it outputs a confirmation. It should show 100000ish+1 records in/out and copied modem.bin size MB and speed in MB/sec.
Reboot phone and thats it.
The baseband version should now be updated in settings and anywhere else you might find it.
Click to expand...
Click to collapse
I would change "partition=/dev/block/mmcblk0p2" to this: partition="/dev/block/platform/msm_sdcc.1/by-name/modem"
This will ensure the the correct block is written to no matter what S5 variant they are using. Hardcoding blocks can sometimes yet seldomly lead to bricked devices
elesbb said:
I would change "partition=/dev/block/mmcblk0p2" to this: partition="/dev/block/platform/msm_sdcc.1/by-name/modem"
This will ensure the the correct block is written to no matter what S5 variant they are using. Hardcoding blocks can sometimes yet seldomly lead to bricked devices
Click to expand...
Click to collapse
Yes, that is better. Thanks
First of all thanks for the Tool and instructions.
will it let me flash G900F modem on G900T ?
Ian the Great said:
It seems that flashing a modem on the GS5 can be real pain. Even using a pc w/odin the modem doesn't always stick.
$busybox dd if="${modem}" of="${partition}"
-----------------------------------------------------------
Once you hit run, it will take a second or up to 10 before it outputs a confirmation. It should show 100000ish+1 records in/out and copied modem.bin size MB and speed in MB/sec.
Reboot your phone and thats it.
The baseband version should now be updated in settings and anywhere else you might find it.
Click to expand...
Click to collapse
I have flashed modems via PC with odin and They stick everytime as long as I pull the battery first. I will give terminal a try .Thanks
---------- Post added at 11:44 AM ---------- Previous post was at 10:50 AM ----------
By the way I am trying this right now .. I will post back shortly
spirodave said:
I have flashed modems via PC with odin and They stick everytime as long as I pull the battery first. I will give terminal a try .Thanks
---------- Post added at 11:44 AM ---------- Previous post was at 10:50 AM ----------
By the way I am trying this right now .. I will post back shortly
Click to expand...
Click to collapse
Hey how did this workout for you bud. Thanks
xda23 said:
Hey how did this workout for you bud. Thanks
Click to expand...
Click to collapse
I found i faster to just convert the modem.bin to a tar.md5 . I put the NH5Modem up in the general section . After it wouldnt let me copy and paste the command from chrome to terminal emulator i just decided to convert it . I guess i could have just used ADB but didnt think about it at the time . I didnt want to risk typing the wrong command to terminal to install the modem .
Just tried this script a min ago with the NH5 modem.
It looked like it worked, but then after I rebooted and disabled airplane mode, it still says NF6.
I've done a similar method with my fiancee's Galaxy S T959V and it works fine, apparently not with this phone...
@Ian the Great.
In /dev/block/platform/msm_sdcc.1/by-name/ I have 3 devices: modem modemst1 modemst2
I did everything from an adb root shell.
I backed up all of them with dd.
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st1.ang2
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st2.ang2
-rw------- 1 root root 60227584 2016-11-29 11:59 modembak.ang2
But when I tried to overwrite modem with the new modem.bin I was blocked for some reason:
dd: /dev/block/platform/msm_sdcc.1/by-name/modem: Operation not permitted
I tried disabling selinux (and confirmed it was disabled) but it didn't help.
Lop3 said:
@Ian the Great.
In /dev/block/platform/msm_sdcc.1/by-name/ I have 3 devices: modem modemst1 modemst2
I did everything from an adb root shell.
I backed up all of them with dd.
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st1.ang2
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st2.ang2
-rw------- 1 root root 60227584 2016-11-29 11:59 modembak.ang2
But when I tried to overwrite modem with the new modem.bin I was blocked for some reason:
dd: /dev/block/platform/msm_sdcc.1/by-name/modem: Operation not permitted
I tried disabling selinux (and confirmed it was disabled) but it didn't help.
Click to expand...
Click to collapse
I'm not sure It was quite awhile back when I needed this. Sounds like your device is a little different than what I was using when I posted this.
In general from what i remember there number of things can block you from writing there. You may need to be on stock recovery and kernel. Having modified recovery like twrp or custom kernel can alert device so modem won't stick after reboot or it won't write at all .
Another idea to possibly try is, from the stock firmware, extract the file named NON-HLOS.bin and write that to apnhlos slot.
in other words instead of
dd if=/sdcard/modem.bin of=/dev/block/platform/msm_sdcc.1/by-name/modem
The command would be something like
dd if=/sdcard/NON-HLOS.bin of=/dev/block/platform/msm_sdcc.1/by-name/apnhlos
I'm pretty sure I was able update modem on newer samsung with just the NON-HLOS file, but can't remember exactly which phone I had and command used. Backing up apnhlos like you did with modem is probably smart.
Also If you are using adb from a pc why not just use Odin to flash it? Probably easier than dd method.
can this work for other brands ? specialy note 3 neo ?
hey guys, I got my new phone last night and I've rooted it, and just about got it modded to my liking. The last little piece of the puzzle is the damned bright orange Consumer Cellular splash screen when you turn on the phone.
I installed the stock oem rom, which supposedly had the "cust" partition, and it did install the stock boot animation which is a great improvement, but the initial splash screen when you first turn on the phone is unchanged. I tried following this thread here:
http://forum.xda-developers.com/ascend-mate2/development/custom-huawei-ascend-mate-2-splash-t2940864
However when I try to copy the new file into the "cust" folder, it says the location does not exist. The cust folder is a partition, so something screwy must be going on. I figured that the new rom I installed probably already replaced the file, so I just ran the command in terminal like it said, but it didn't seem to work either.
Has anyone successfully replaced the CC splash screen?
Thanks
You have to search the forum for it. I posted it in consumer cellular post
Sent from my MT2L03 using XDA Premium 4 mobile app
Yeah, enabling write permissions in root still didn't work. I did manage to get this working though. While it wouldn't allow me to copy any files to the cust folder, it was allowing me to create empty folders. The rom that I installed replaced the "cust/us/ConsumerCellular" folders with "cust/us/normal" folder.
So what I did was create the original file structure with the ConsumerCellular folder system, then I went to the TWRP recovery file explorer and copied the new splash screen In there where it originally would have went. Then booted back up and did the terminal command and it worked like a charm.
Thanks for your original tutorial.
Nice job, ArcAngel06. And thanks for sharing so others can do the same trick.
If you follow mtyler's post (thanks mtyler) you will be able to do it. You MUST enable read/write on all folders in the CUST folder down to where the image is (i.e Logo)
Using ES file I had to do each file property one by one, a PITA took couple hrs to figure this out.
Davinci50 said:
If you follow mtyler's post (thanks mtyler) you will be able to do it. You MUST enable read/write on all folders in the CUST folder down to where the image is (i.e Logo)
Using ES file I had to do each file property one by one, a PITA took couple hrs to figure this out.
Click to expand...
Click to collapse
Code:
su
chmod -R 777 "/path/to/cust"
su for root permissions when calling chmod
-R means recursive for all files and directories within the specified path.
777 means read, write, and executable for all groups. Feel free to use something other than 777.
---------- Post added at 04:22 PM ---------- Previous post was at 04:16 PM ----------
Just take note of the original permissions - they should all be the same and use chmod to fix the permissions after making your change.
SHM said:
Code:
su
chmod -R 777 "/path/to/cust"
su for root permissions when calling chmod
-R means recursive for all files and directories within the specified path.
777 means read, write, and executable for all groups. Feel free to use something other than 777.
---------- Post added at 04:22 PM ---------- Previous post was at 04:16 PM ----------
Just take note of the original permissions - they should all be the same and use chmod to fix the permissions after making your change.
Click to expand...
Click to collapse
Ok cool, but you still need to see what the permissions were to revert back to , so why not just edit them while you are there?:good:
Davinci50 said:
Ok cool, but you still need to see what the permissions were to revert back to , so why not just edit them while you are there?:good:
Click to expand...
Click to collapse
Because it is way faster than doing each folder and each file one by one.
For example, if you go to /system/bin and check that folders permissions you can assure yourself that everything else recursively will be the same also. So, there is no need to actually look at each ones permission. That would be crazy lol.
---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------
Could also unpack the TWRP recovery and grab the shell script for "fixing permissions". Modify the script to your liking for such cases as stated above, place the modified script to /system/bin, then give it executable permissions, and that will save LOADS of time. Now all you have to do is open the terminal and call on the script and voila, done.