Hi all,
I wan to shared my experience about download mode dead.
Case
- Can not enter download mode completely
- Can enter recovery (TWRP)
- Can not boot ,stuck lg logo
- Base rom D80220B Thailand
How to fix
step 1.
- boot G2 enter to TWRP and plug it into computer
- push .bin to /tmp and parted to /tmp
- chmod 777 /tmp/parted
- use ./parted /dev/block/mmcblk0 to show partition detail what is a block number of partition before use dd command
- I use dd command fix any partition as below via adb shell but it is a same problem.
Code:
dd if=/tmp/aboot.bin of=/dev/block/mmcblk0p5
dd if=/tmp/boot.bin of=/dev/block/mmcblk0p7
dd if=/tmp/laf.bin of=/dev/block/mmcblk0p23
dd if=/tmp/recovery.bin of=/dev/block/mmcblk0p15
dd if=/tmp/rpm.bin of=/dev/block/mmcblk0p6
dd if=/tmp/sbl1.bin of=/dev/block/mmcblk0p2
dd if=/tmp/tz.bin of=/dev/block/mmcblk0p8
dd if=/tmp/fota.img of=/dev/block/mmcblk0p24
dd if=/tmp/cust.bin of=/dev/block/mmcblk0p34
dd if=/tmp/persist.bin of=/dev/block/mmcblk0p14
dd if=/tmp/dbi.bin of=/dev/block/mmcblk0p3
dd if=/tmp/modem.bin of=/dev/block/mmcblk0p1
*** .bin file I extract from kdz
step 2.
- I'm adding dd command and partition as below then it can enter download mode and can flash firmware kdz
I don't know why ? but it can fix g2 of my friend 2 person
Code:
dd if=/tmp/DDR.img of=/dev/block/mmcblk0p4
dd if=/tmp/encrypt.img of=/dev/block/mmcblk0p20
dd if=/tmp/fsc.img of=/dev/block/mmcblk0p17
dd if=/tmp/fsg.img of=/dev/block/mmcblk0p16
dd if=/tmp/misc.img of=/dev/block/mmcblk0p13
dd if=/tmp/mpt.img of=/dev/block/mmcblk0p25
dd if=/tmp/rct.img of=/dev/block/mmcblk0p29
dd if=/tmp/sns.img of=/dev/block/mmcblk0p22
dd if=/tmp/spare.img of=/dev/block/mmcblk0p33
dd if=/tmp/ssd.img of=/dev/block/mmcblk0p18
*** .img I get from backupz that use flashable zip from this thread
http://forum.xda-developers.com/showthread.php?t=2451390
(LG_G2_Backup_All_Partitions.zip)
{
"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"
}
.....
Related
I'm on SGS 3 (I9300) with freshly installed I9300XXDLIH_I9300VFGDLJ1_VIP and rooted afterwards.
Since I upgraded my phone to Jelly Bean, I can't test/debug any development project on the phone.
The Eclipse APK build passes OK and this is what I get in the step afterwards -- when the APK is tried to be deployed on the phone:
Code:
Installation failed due to invalid APK file!
Please check logcat output for more details.
Launch canceled!
This is what I get when I try installing directly with ADB:
Code:
>adb install -r test.apk
3484 KB/s (1616779 bytes in 0.453s)
pkg: /data/local/tmp/test.apk
Failure [INSTALL_FAILED_INVALID_APK]
I've found some hints that the tmp folder may have invalid permissions, so I have done this:
Code:
chmod 777 /data /data/local /data/local/tmp
With the result:
Code:
[email protected]:/ # ls -ld data data/local data/local/tmp
ls -ld data data/local data/local/tmp
drwxrwxrwx system system 2012-10-23 15:40 data
drwxrwxrwx root root 2012-08-25 10:40 local
drwxrwxrwx shell shell 2012-10-23 16:36 tmp
Eclipse or ADB still refuse to install (any) APK.
If I copy the Eclipse-generated APK to the phone and initiate the install from there, it works OK.
What can I do to fix this? Please help.
FYI, I'm using 20.0.3 Android SDK (and Eclipse 4.2.1).
My system properties:
{
"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"
}
Update:
Installed SiyahKernel S3-v1.6.8 and w/o any tampering with the settings (e.g. through ExTweak) the problem is solved.
Root cause seems to be UMASK.
- on stock kernel I had 0077
- now on SiyahKernel I have 0000
Still, as can be seen from numerous other threads on the same issue out there, it's very wrong for the stock kernel to cause that problem.
Moved to Android Q&A.
Motorola Dashboard app extracted from Motorola Defy XT535 Gingerbread SBF. The Motorola Defy XT535 has the same resolution as the Motorola Defy/Defy+ and it should work for all Gingerbread ROMs and above. The zip file will flash the Dashboard app to the /system partition as it doesn't work if you flash it to the /data partition. The app WILL FC when you install it as a normal APK.
How to install the Motorola Dashboard app using the zip file:
1. Root your device and install Android Bootmenu if you haven't already done so. Custom ROMs already have bootmenu installed.
2. Download the zip file and put it in your SD Card.
3. Boot your device into CWM or TWRP.
4. Install the zip file.
5. Mount /system and /data partitions.
6. Install Compass and Music Now Services for Dashboard to work properly as I didn't include in the zip file (oops).
Type the following commands in cmd:
Code:
adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
Code:
adb push Compass_alldpi.apk /system/app/
Code:
adb shell chmod 644 /system/app/Compass_alldpi.apk
Code:
adb push MusicNowGlobal_tinboostplus_hdpi.apk /system/app/
Code:
adb shell chmod 644 /system/app/MusicNowGlobal_tinboostplus_hdpi.apk
7. Reboot your device and you should see the Dashboard and Compass in the app drawer.
How to install the Motorola Dashboard app manually:
1. Root your device and install Android Bootmenu if you haven't already done so. Custom ROMs already have bootmenu installed.
2. Download the APK and put it in the same path as adb.
3. Boot your device into CWM or TWRP.
4. Now mount /system and /data
5. Install Compass and Music Now Services for Dashboard to work properly.
Type the following commands in cmd:
Code:
adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
Code:
adb push DashBoard_tinboostplus_hdpi.apk /system/app/
Code:
adb shell chmod 644 /system/app/DashBoard_tinboostplus_hdpi.apk
Code:
adb push Compass_alldpi.apk /system/app/
Code:
adb shell chmod 644 /system/app/Compass_alldpi.apk
Code:
adb push MusicNowGlobal_tinboostplus_hdpi.apk /system/app/
Code:
adb shell chmod 644 /system/app/MusicNowGlobal_tinboostplus_hdpi.apk
6. Reboot your device and you should see the Dashboard and Compass in the app drawer.
Screenshots:
{
"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"
}
Hit the thanks button if I helped you
What exactly is Dashboard? Some kind of car mode?
TJKV said:
What exactly is Dashboard? Some kind of car mode?
Click to expand...
Click to collapse
It's a fitness app by Motorola that was made for the Motorola Defy Mini and Defy XT.
thank you
Hi,
I am trying to flash a new ROM to my Samsung Galaxy S5830i, but unfortunately, I can't use either Recovey Mode, or Download Mode.
When I try to access Download Mode, it simply boots in as nothing happened. (I tried to access Download Mode by pressing Vol Up + Vol Down + Power)
When I try to access Recovery Mode, I can't move with the volume buttons, but the home button does work (and it reboots the phone). It says, "Applying Multi-CSC", but nothing happens, I tried to leave it there for 1 hour, but nothing changed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried the following soultions, but none of them solved the problem:
I rooted the phone, and tried using Terminal to flash CWM as recovery.IMG, as this tutorial suggests:
Launch terminal emulator
Change user as superuser, type
$su
the $ symbol wil change to #
Mount and change the permission
# mount -o remount rw /system
Concatenate flash_image files and set the permission.
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
Install the CWM recovery
# flash_image recovery /sdcard/recovery.img
set back the permission for /system and reboot
# mount -o remount ro /system
# reboot recovery
Click to expand...
Click to collapse
It got stuck on installing the CWM recovery:
I tried to access Download Mode with ADB using the "reboot download", but the phone rebooted normally, not in Download Mode.
Any suggestions, on how to access Download Mode or fix the Recovery Mode, so I can flash a new ROM to the phone?
Hello,
I am trying create a disk image on my windows PC of the data on my phone to see if I can recover some lost files.
On my PC, can I just use:
~# adb shell dd if=/dev/block/datapartition > data.img
or just
~# adb pull /dev/block/datapartition data.img
or do I need to use netcat and busybox to send and receive the files?
Do all these methods work exactly the same?
Thanks
just type the following on ADB
Code:
adb devices
Code:
adb shell
Code:
ls -la /dev/block/bootdevice/by-name
^ this would list all partion of your devices it should look like 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"
}
based on the screenshot above we know boot.img is mmcblk0p59
now we just do dd command
Code:
dd if=/dev/block/mmcblk0p59 of=/sdcard/boot.img
Congratulation you now have boot.img backup of your device :fingers-crossed::fingers-crossed:
Thanks, but will that output to the phones sd card? I would like to output the img to my pc
kaotik123 said:
Thanks, but will that output to the phones sd card? I would like to output the img to my pc
Click to expand...
Click to collapse
you are most likely do the dd command from your pc just copy the img file from your device to your pc
also on my device even it say " of=/sdcard/ " files are being drop on Internal Memory ...
ineedroot69 said:
you are most likely do the dd command from your pc just copy the img file from your device to your pc
also on my device even it say " of=/sdcard/ " files are being drop on Internal Memory ...
Click to expand...
Click to collapse
Yeah I wanted to avoid writing to the phone's memory becuase I was trying to recover lost files from it. Plus the image would be too big to fit on the remaining memory anyway. Thanks for your help but I used netcat and busybox and successfully copied the image directly to my PC. Followed the tutorial here for anyone else reading this and was quite easy: https://dfir.science/2017/04/Imaging-Android-with-root-netcat-and-dd.html (second video for windows pc).
{
"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"
}
Droidian for Poco X3/NFC
ABOUT:
Droidian is a Gnu/Linux Distribution which uses Halium to have compatibility with android smartphones
Website: https://droidian.org
Telegram: Device Group | Global Group
Github: https://github.com/droidian
WHAT WORKS?
- Almost everything
WHAT DOESN'T WORK?
- Audio
- You tell me..
DOWNLOADS:
GSI rootfs
Adaptation package
boot-surya.img
boot-karna.img
dtbo-surya.img
dtbo-karna.img
vbmeta-surya.img
vbmeta-karna.img
Surya Installation:
Flash boot.img: fastboot flash boot boot-surya.img.
Flash dtbo.img: fastboot flash dtbo dtbo-surya.img.
Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-surya.img.
Flash your favorite recovery ( TWRP Recommended ).
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip
Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp
Get a shell into your device: adb shell
Change directory to /tmp and run the script: cd /tmp/adaptation-surya-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Karna Installation:
Flash boot.img: fastboot flash boot boot-karna.img.
Flash dtbo.img: fastboot flash dtbo dtbo-karna.img.
Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-karna.img.
Flash your favorite recovery ( TWRP Recommended ).
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip
Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp
Get a shell into your device: adb shell
Change directory to /tmp and run the script: cd /tmp/adaptation-surya-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while
Notes:
The default password is 1234.
If you see a black screen, don't worry it takes a long time to boot.
Droidian GSIs are experimental! Bugs and missing features are expected.
You need this miui build LINK
Thanks to: Barry, Javad and myself for making this rom possible
Does VOIP VoLTE work?
im not being sketchy... when you say audio doesnt work... is that global for the phone or glitchy... or because i so want to use a linux os for my phone but i do still need it to be a phone.... i was hoping you might say that phone calls work but the external speaker has a bug or something.... (praying)
nakedpwr said:
im not being sketchy... when you say audio doesnt work... is that global for the phone or glitchy... or because i so want to use a linux os for my phone but i do still need it to be a phone.... i was hoping you might say that phone calls work but the external speaker has a bug or something.... (praying)
Click to expand...
Click to collapse
Nope, they don't work, you can use something like telegram if your headphones have a microphone
Srilakshmidaran said:
Does VOIP VoLTE work?
Click to expand...
Click to collapse
Doesn't work with any Halium-based distro right now, but some people are working on it