I had a couple of times before the problem with random format of partitions and last time with restarts after install any app on AOSP 5.0 by artas182x.
Last time partition /recovery /system and maybe /data was formatted so i flash cwm by fastboot then i flash other 5.0.x based cm by cwm and next day when i flash official gapps mini for android 5.0.x from xda, after restart...
Phone stuck on LG logo and i can't enter in fastboot or do anything... (i don't see security error or anything like that):crying:
vol- home power = not working
vol+ home power = not working
phone without batery is recognized as "Texas Instruments, Inc." (I'm working on ubuntu)
I tried to use this script but it does not work. (still scanning usb devices and waiting for phone response )
Can anyone here help me ?
"# simple menu script by wkpark at gmail.com (found in omapboot-for_optimus-v1.21)
# uses x.img and u.img from
#*********(i can't post links)
which fastboot || echo install fastbooot first, e.g. on ubuntu sudo apt-get install android-tools-fastboot
which fastboot || exit
echo 'Connect LG L9 *without battery* to PC using data cable'
sudo ./usbboot p940-aboot.2nd p940-u-boot_fastboot.bin && echo usbboot ok || exit
echo 'DO NOT disconnect usb cable. Insert battery, then press enter'
read x
sleep 10
echo fastboot devices:
sudo fastboot devices
echo flashing bootloader
sudo fastboot flash u-boot u.img && sudo fastboot flash x-loader x.img && sudo fastboot reboot && echo Everything OK, rebooting phone"
Related
Enable Developer Mode:
( on the watch )
tap clock, swipe up and go all the way down to “About”
tab build number several times. You’ll know
up one menu, “Developer Options” -> “ADB debugging”
your phone will ask you to allow debugging
dock it, plug usb to computer
in terminal:
adb usb
adb devices (check out your device’s serial #)
adb shell (woot! shell on your watch!)
Backup contents of system partition
mkdir system
adb pull /system ./system
Void the warranty (unlock bootloader)
adb reboot-bootloader
fastboot oem unlock
follow instructions on device
device will factory reset & reboot
Root ( needed to dump partition images, otherwise not particularly useful )
credit for this: androidpolice.com/2014/07/05/how-to-android-wear-enable-debugging-take-screenshots-unlock-the-bootloader-and-root-the-lg-g-watch/
get this: androidfilehost.com/?fid=23501681358558067
adb reboot-bootloader
Boot the image: fastboot boot LGGW-rootboot.img
DO NOT FLASH THE IMAGE!!!! FOR THE LOVE OF GOD DON’T FLASH IT!!!!!!!
intended to boot only once (installs su, etc)
adb shell
su
now what?
Dump some partitions: ( in a root shell on the watch )
partition layout
mmcblk0p15 - boot
mmcblk0p16 - recovery
mmcblk0p19 - system
mmcblk0p20 - cache
mmcblk0p21 - userdatadump some partitions. for example: ( jump into adb shell, as root )
dd if=/dev/block/mmcblk0p15 of=/sdcard/backup/boot.img
dd if=/dev/block/mmcblk0p16 of=/sdcard/backup/recovery.img
dd if=/dev/block/mmcblk0p19 of=/sdcard/backup/system.img
dd if=/dev/block/mmcblk0p20 of=/sdcard/backup/cache.imgDONT TRY TO BACKUP mmcblk0p21 to the sdcard!!! the “sdcard” is on that partition!!
pull the images. for example: ( on your computer )
adb pull /sdcard/backup/boot.img .
adb pull /sdcard/backup/recovery.img .
adb pull /sdcard/backup/system.img .
adb pull /sdcard/backup/cache.img .maybe delete those images from the device when you are done
Have Fun!
Restore images (flash via fastboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
The following may be tricky, might break stuff, and is generally not recommended unless you really know what you are doing
You have been warned!
Install a zip file using the stock recovery (might only work with signed updates, not roms)
In a terminal on your computer:
adb push whatever-new-rom.zip /sdcard/update.zip
adb shell
cp /sdcard/update.zip /cache/update.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/update.zip' >> /cache/recovery/commandreboot recovery
Enable Bluetooth debugging (really slow, kinda lame)
connect your phone over usb
on watch, in developer settings, Debug over Bluetooth
on phone, open wear app, in settings Debugging over bluetooth
on computer:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
adb shell
Install Debian chroot
on your phone (thats right, your phone) install Debian Kit from Play Store
open it, it the download button in top right corner
download debian-kit-1-6-testing.shar
open an adb shell to your phone ( i prefer usb)
su
cd /sdcard/Download
on my phone it always downloads it as a .jpeg rename it to .shar
mv debian-kit-1-6-testing.jpeg debian-kit-1-6-testing.shar
sh debian-kit-1-6-testing.sharAnswer Y to unpack
read the menu, then choose 0j (wheezy does not work in this script, don’t want it anyway)
it will now create /sdcard/debian.img (512mb) (will take a couple minutes)
next it will mount the image
next it will debootstrap a basic installation of jessie to the image (this takes a long time, ~30 minutes)
you might see an error “cannot create symlink…” that’s good, we don’t want to touch /system anyway
once its done. copy that debian.img from your phone to your computer
adb pull /sdcard/debian.img .we also need everything it unpacked to /data/local/deb
mkdir deb
adb pull /data/local/deb ./deb
unplug phone and plug in the watch, then push those to the watch
adb push debian.img /sdcard/
adb push deb /data/local/debian will not have internet access, the watch has no wifi. need to figure out how to forward over bluetooth
now what? check out this page: sven-ola.dyndns.org/repo/debian-kit-en.html
Also, the best Fastboot Doc ever: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Thanks for the Info
If I backup the files, would I be able to flash those same files back to recover the device ,kinda like a unbricking method. Coudlnt I do it though fastboot ?
Sent from my LG-D851 using XDA Premium 4 mobile app
Froz3nsolid said:
Thanks for the Info
If I backup the files, would I be able to flash those same files back to recover the device ,kinda like a unbricking method. Coudlnt I do it though fastboot ?
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The IMAGES (boot.img, etc) can be flashed from fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
However, there is no way (that i have found yet) do dump images using fastboot; dumping must be done on the device itself
updating op...
Thanks
Sent from my LG-D851 using XDA Premium 4 mobile app
hello, hope i post it in the right place, if not, please move it.
i bought the phone coolpad 7236, based on snapdragon 200 msm8212 chip.
i found out that i got the chinese version of the firmware, so the seller gave me a link for the multi language firmware: http://www.mediafire.com/folder/7g49chcyb7gdy/ROM_for_Coolpad_7236
there are some files there, offical flashtool, quallcom flash files (to be used with the flashtool), drivers, and an archive containg a script that should replace the entire system folder via adb.
i translated the .cmd file and here it is:
@echo off
%~d0
CD "%~d0%~p0"
set id=7236
taskkill /F /IM tadb.exe >nul 2>nul
taskkill /F /IM bdadb.exe >nul 2>nul
taskkill /F /IM sjk_daemon.exe >nul 2>nul
taskkill /F /IM romaster_daemon.exe >nul 2>nul
taskkill /F /IM AndroidInterface.exe >nul 2>nul
taskkill /F /IM adb.exe >nul 2>nul
adb.exe kill-server >nul 2>nul
echo .
echo The ROM for models£º%id%
echo .
echo Flash this ROM, please brush into the bottom of the package custom 7236
echo.
echo Brushing the bottom package, the phone is switched, the screen splash screen again after connecting USB
echo.
echo Note: During the brush machine, the phone screen is blank, do not operate the phone buttons until the phone automatically restart
echo.
title %id% ¹ú¼Ê°æ By Kyle
pause
:flash
color 1B
cls
adb -d push boot.img /tmp/.
echo Begin transmission system file, about 300M, wait. . . .
adb -d push system7236.tar.gz /tmp/.
adb -d shell mount /data
adb -d shell mount /system
adb -d shell rm -r /system/*
adb -d shell rm -r /data/*
adb -d shell tar -zxvf /tmp/system7236.tar.gz -C /
adb -d shell dd if=/tmp/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
adb -d shell reboot
echo Finished, the phone will automatically enter recovery, the recovery interface, you can directly select reboot system now
pause
exit
Click to expand...
Click to collapse
as you can see, it deletes the system folder and should put the contents of the archive as new system folder.
unfortunally this only made the first step, as soon as the script deleted the system folder, the phone stopped working.
i tried using adb shell to do it manually, but it didn't complied to simple commands as "dir" "ls" "cp" "pull" "push", the phone became a brick.
then i tried using the flashtool, the company says that in order to use it you should dial
#*20110606#
Click to expand...
Click to collapse
and then choose test mode or something in order to allow the flashtool put it in download mode, obiously i can't do that now. i figured that when i hold the power button the screen turns white, making the phone discoverable as quallcom hs-usb diagnostics or something like this, it doesn't work with the flashtool (it searches for qdloader device).
then i tried dumping system.img from other coolpad 7236 device, i used this tutorial: http://forum.xda-developers.com/showthread.php?t=2450045 and i got 800MB file, the fastboot refused to get it, then i used this fastboot: http://forum.xda-developers.com/moto-x/moto-x-qa/solved-img-vzw-xt1060-to-flash-fastboot-t2493814
waited for 30 minutes, but it was stuck on sending.
also, i couldn't get the fastboot to work, i tried to flash the boot.img that the seller gave me in the link, but the fastboot got stuck in "writing", the fastboot also ignored simple commands such as reboot.
the stocvk recovery is not helping either because i don't have signed update.zip for it.
is there anything else to do beside sending it back to china?
and, is there any GOOD WAY to replace the contents of the system folder (in case i get another chinese like this) without bricking the phone?
Figured it out, nevermind
kkffiirr said:
Figured it out, nevermind
Click to expand...
Click to collapse
Hi,
I'm new to all this. And I am having a Coolpad 7236 currently. It is also in Chinese and I do not know how to read that....Sigh...
Good phone with some flaws.
I'm interested in rooting it and flushing out the software to install a new one but I do not know how.
Can help?
Thanks
iandroid.co.il/forum/viewtopic.php?f=190&t=179082&hilit=7236
Use Google translate
Hi. I have the same problem. I am not able to follow the guide from the link you provided. Can you please put in simple terms how I can flash the multi language firmware in my coolpad. If yes, that would be a great help for me
Thanks.
wow, very old post...
here are the steps:
1. install adb drivers, get adb software, set the phone to enable usb debugging and root it with root genius.
2. download the system dump from: https://mega.co.nz/#!9JRTmYyD!MgZR1CITlfUMFM5FUtBlkVCg7u97djHYg8rkmudRbtc
3. download the kernel dump from: https://mega.co.nz/#!EBIH1TRZ!hfesnz3FkZXnaEHw6T5sA1DH98spXAGY594j-0HU-Hw
4. copy the files from 2 and 3 to the phone storage root.
5. start adb shell session by:
Code:
adb -d shell
6. enter the following commands:
Code:
su
dd if=/mnt/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/mnt/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
note: the first dd shouldn't take much time, while the second might be long, be patient and wait for it to finish, and then reboot
Thanks, kkffirr... The link for Kernel dump is not working.... It says the file has been removed! ?
The Imperium said:
Thanks, kkffirr... The link for Kernel dump is not working.... It says the file has been removed!
Click to expand...
Click to collapse
try this
https://mega.nz/#!IZpwgIJA!hfesnz3FkZXnaEHw6T5sA1DH98spXAGY594j-0HU-Hw
I have been trying for more than a week now, but not able to root the phone... This is so annoying...
The Imperium said:
I have been trying for more than a week now, but not able to root the phone... This is so annoying...
Click to expand...
Click to collapse
it worked for me with root genius back then
My device is a LG H440n. I did use adoptable storage aka external SD card as internal storage. I had quite a few games on my phone. Yesterday it has gone into boot loop, I can't rember what I did unfornuately.
After boot, when I see the graphical UI, it says that the process system has stopped working and restarts immediately almost every time. Yesterday I managed to get in the menu and do the factory reset and the device was ok again. Then I got cocky, put in SD card again and now it's in boot loop again. Today It won't let me.
I cant get to the factory reset through pushing buttons on boot, either Im doing it wrong, what I doubt or the buttons are not reacting.
I tried adb then:
Code:
#!/bin/bash
echo " "
echo "Wating for device..."
adb start-server
adb wait-for-device
echo "fu "
adb -d shell stop
adb get-state
adb status-window
Tried adb again:
Code:
#!/bin/bash
adb wait-for-device
echo $(adb shell getprop sys.boot_completed)
A=$(adb shell getprop sys.boot_completed | tr -d '\r')
while [ "$A" != "1" ]; do
sleep 1
A=$(adb shell getprop sys.boot_completed | tr -d '\r')
echo $(adb shell getprop sys.boot_completed)
done
echo "something"
I also used watch with adb devices
Code:
watch -n 2 "adb devices >> testt"
Nothing showed up anywhere.
What to do? Any help is greatly appreicated, I dont have the money for a new phone.
okaymoogle said:
My device is a LG H440n. I did use adoptable storage aka external SD card as internal storage. I had quite a few games on my phone. Yesterday it has gone into boot loop, I can't rember what I did unfornuately...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at the following, device specific, threads and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3108435
https://forum.xda-developers.com/showthread.php?t=3392128
https://forum.xda-developers.com/showthread.php?t=3111546
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hi I am having a problem trying to flash my g610f/DD phone. I tried removing the FRP lock with FRP Hijacker by Hagard and it totally messed up the phone where its boot looping. I've read and tried almost all the solutions on this website for that model phone. When I flashed the stock rom it is saying Re-Partition Failed in odin. Also on the phone it says in red "secure check fail". The current binary displays as Custom and the FRP lock is on.
I need some help since I tried a lot of solutions and none of them work.
Thanks,
A phone's NAND flash ( storage memory ) is divided into partitions, each of them is of fixed size. When you try to flash a ROM what contains partitions that exceed the size of already existing partitions then you will run in such a trouble. To get rid off of this you would have to completely clean / format the existing partitions ( except the EFS partition !!! ) before re-flashing a ROM. This can be achieved with ADB / Fastboot commands.
Generic Batch-file Example ( untested ! ) :
Code:
@echo off & setlocal
set "ROM=C:\stockrom.zip"
if NOT exist "%ROM%" ( goto :end )
set "PIT=%TEMP%\pit.txt"
adb devices
adb shell "cd /"
adb shell "ls -d" > %PIT%
if NOT exist "%PIT%" ( goto :end )
adb reboot bootloader
fastboot devices
for /f "tokens=9 delims= " %%a in ( "%PIT%" ) do (
if NOT [%%a]==[] (
echo %%a | findstr /I /C:"/EFS" > nul
if %ERRORLEVEL% NEQ 0 (
set "pn=%%a"
set "pn=%pn:~1,0%"
fastboot format %pn%
)
)
)
del /F /Q "%PIT%"
fastboot flashall %ROM%
fastboot reboot
:end
endlocal & @echo on & exit
Read also here: https://technastic.com/odin-nand-erase-samsung/
Hi Thanks for your reply. I can boot into the recovery mode now but when I tried to run the adb commands it gives me an error closed. Also try to install a stock rom it says custom rom block FRP lock.
itwayne said:
Hi Thanks for your reply. I can boot into the recovery mode now but when I tried to run the adb commands it gives me an error closed. Also try to install a stock rom it says custom rom block FRP lock.
Click to expand...
Click to collapse
In Recovery Mode you can't run most of ADB subcommands as for example "adb shell", this because Android OS isn't running.
jwoegerbauer said:
In Recovery Mode you can't run most of ADB subcommands as for example "adb shell", this because Android OS isn't running.
Click to expand...
Click to collapse
How can I format the partitions to get a stock rom on then if adb cant do it.
Thanks,
Hi guys, just a disclaimer here but I’m a newb when it comes to flashing ROM’s. I’m trying to flash Calyxos but I’m not having any luck. I get a very quick CMD window (using file flash-all.bat) that appears and then disappears and then… nothing. I’ve tried updating and installing adb drivers, downloading the latest adb fastboot (minimal_adb_fastboot_1.4.3_portable), re-downloading Calyxos (crosshatch-factory-2020.09.22.12) and setting the environment variables to reflect the location of the Caylxos files. I’ve already unlocked the phones bootloader and have USB debugging and OEM unlock enabled. When I run “adb devices” using cmd.exe, it’s able to detect the phone, but this is as far as I can get. If anyone has any advice for me, I’d really appreciated it!
Phone has also been updated to Android 11 and has the latest security patches installed
Anybody?
@jspicket1111
I guess you have heavily outdated ADB & Fastboot drivers installed. Use this tool to ensure the latest ones are installed.
I also guess the mentioned flash-all.bat is the one that comes with the Calyxos distribution you try to flash. Correct? If so then you can manually input each of the commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash bootloader <PATH_TO_BOOTLOADER_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio <PATH_TO_RADIO_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot erase avb_custom_key
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w --skip-reboot update <PATH_TO_CALYXOS_OS_ZIP_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
in a Windows CMD window ( not in a Powershell window ! ) and execute it to see whether an error occurs or not.
Awesome! I'll try it again this evening and report back. Thank you very much for the help
jwoegerbauer said:
@jspicket1111
I guess you have heavily outdated ADB & Fastboot drivers installed. Use this tool to ensure the latest ones are installed.
I also guess the mentioned flash-all.bat is the one that comes with the Calyxos distribution you try to flash. Correct? If so then you can manually input each of the commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash bootloader <PATH_TO_BOOTLOADER_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio <PATH_TO_RADIO_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot erase avb_custom_key
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w --skip-reboot update <PATH_TO_CALYXOS_OS_ZIP_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
in a Windows CMD window ( not in a Powershell window ! ) and execute it to see whether an error occurs or not.
Click to expand...
Click to collapse
So far I'm making progress. I've got to the part where I'm entering, "fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>" and I'm getting this error in CMD...
C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools>fastboot flash "C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin"
unknown partition 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
fastboot: error: cannot determine image filename for 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
I feel like I'm almost there! Not sure if it matters... but the "avb_pkmd.bin" file is only 1 KB in size. Anyhow, I'm not really sure how to fix this error. Would you be willing to help me out again?
jspicket1111 said:
So far I'm making progress. I've got to the part where I'm entering, "fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>" and I'm getting this error in CMD...
...
Unknown partition 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
Click to expand...
Click to collapse
Line
Code:
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
should read as
Code:
fastboot flash [color=red]avb_custom_key[/color] <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
Was a copy / paste error. Sorry for this.
jwoegerbauer said:
Line
Code:
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
should read as
Code:
fastboot flash [color=red]avb_custom_key[/color] <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
Was a copy / paste error. Sorry for this.
Click to expand...
Click to collapse
I finally got it! Thank you very much for the help!