1. Are you ready for the Galaxy S20? Here is everything we know so far!
Thread Status:
Not open for further replies.

[Test]NoT WoRkInG![Back to Stock!] Restore Phone via Calibration mode.

Discussion in 'Android Devices' started by zimlokks, Mar 22, 2013.

  1. zimlokks

    zimlokks Android Expert
    Thread Starter

    So guys this is My first Guide, so dont shoot me.
    first of im doing wrong by blind development here but knowing what i know ill do my best to help!
    So u soft bricked your phone, now what? its not the end of the world!!! im here to help! :D
    First this method should work on all platforms as long as android sdk is installed properly and adb is working and the correct drivers are installed! i can only supply the link to download the sdk(plz read how to install it properly). link to download Android sdk http://developer.android.com/sdk/installing/index.html
    ok after u install android sdk and the correct drivers, now to test adb.
    To test adb open command prompt. (Window users do this by pressing the start menu clicking run and typing cmd) (press enter) now u have to change directory to platform-tools located where android sdk was installed. did u make it?
    ok now if u did it type adb
    some gibber blaber is gonna come out thats good :D
    now(with your phone plugged in and in calibration mode power+volume down)
    type adb devices(press enter)
    your phone serial should appear)
    now that is outta the way u have to download the backup images from herehttp://androidforums.com/showthread.php?t=696265
    give him a thanks plz!
    after thats done extract all the images to a safe location yu will remember most likely the desktop in a folder called images
    now that thats done the fun starts
    start the command prompt and cd to platform-tools again. again do adb devices see yur serial good!
    so to flash the boot yu will do:
    adb shell flash_image boot /path/to/boot.img(drag and drop will do as well this image will be located where u extracted) if all went well yur good to go!
    now to restore system:
    adb shell flash_image system /path/to/system.img
    if all went well the system portion is gonna be back to stock and should boot fine!
    now for stock recovery do:
    adb shell flash_image recovery /path/to/recovery.img
    all went well you'll have stock recovery
    thats all for now plz if u deserve credit plz pm me im new to this side of the world and this is my first Guide lol hope this will help ppl stuck with soft bricks! ask for help if needed!
    thanks for this crucial info!
    Credit to Killcmd for the images!
    ***Standard Disclaimer goes here! Androidforums.com nor I are responsible for what you do yu to yur devices, im not holding a gun to yur head so dont say i made yu do it! if u mess up kindly ask for help, but if u decide to blame me i will laugh and enjoy my root bear!***


    this thread shall be closed(hopefully any questions please contact me asap meanwhile a mpre complete thread here http://androidforums.com/showthread.php?t=704451
     

    Advertisement

    El Presidente and andriodadmirer like this.
  2. andriodadmirer

    andriodadmirer Android Enthusiast

    Thanks for this i know people needed it!
     
  3. zimlokks

    zimlokks Android Expert
    Thread Starter

    i will be improving the op...how shall i improve this? im using Tapatalk so i cant really edit this as much but ill do my best with yur guys help :d
     
  4. Kaiser17

    Kaiser17 Android Enthusiast

    Thanks im gonna try this when I get home from work, in on Tapatalk too.

    My pad has been bricked for a month and I've been using my admire since which is a good phone but I spent so much on the coolpad and only used it for a month before I bricked it :(
     
  5. keefer2k4

    keefer2k4 Member

    It would be great if this worked!! Please let us know
     
    zimlokks likes this.
  6. zimlokks

    zimlokks Android Expert
    Thread Starter

    remember guys i dont own the device so plz do this at yur own risk! its more than likely gonna work but one cant b 100% sure! so plz post yur results! :D
     
  7. Kaiser17

    Kaiser17 Android Enthusiast

    If it doesn't work, no harm done.. because mine is bricked anyway lol
     
  8. zimlokks

    zimlokks Android Expert
    Thread Starter

    hmm u mean doesnt turn at all? o_O
     
  9. Kaiser17

    Kaiser17 Android Enthusiast

    Soft bricked
     
  10. zimlokks

    zimlokks Android Expert
    Thread Starter

    yea i saw brick im like nooooo lol well try this if that doesnt work ill look into scripting so its a one click thing but since im a noob at scripting i cant and wont promise anything other than help(post a how to)
     
  11. ahdunno

    ahdunno Newbie

    Used this:
    adb shell flash_image recovery /sdcard/recovery.img

    returns
    error opening /sdcard/recovery.img: Permission denied

    I checked the file in Linux and it's Read, Write and Execute for Owner, Group and World.

    I also have recovery.img in the sdk tools benedictory, I've tried:
    adb shell flash_image recovery /recovery.img
    adb shell flash_image recovery ./recovery.img
    adb shell flash_image recovery recovery.img

    all return
    error opening recovery.img: No such file or directory

    Please, any input? Thanks

    Edit: Here's what I get...
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>cd c:\sdk

    c:\sdk>adb devices
    List of devices attached
    Coolpad_5860E device


    c:\sdk>adb shell flash_image recovery recovery.img
    error opening recovery.img: No such file or directory

    c:\sdk>adb shell flash_image recovery /recovery.img
    error opening /recovery.img: No such file or directory

    c:\sdk>adb shell flash_image recovery ./recovery.img
    error opening ./recovery.img: No such file or directory

    c:\sdk>adb shell flash_image recovery /sdcard/recovery.img
    error opening /sdcard/recovery.img: Permission denied

    c:\sdk>

    Also: adb root
    returns
    c:\sdk>adb root
    adbd cannot run as root in production builds

    Also, when trying to access sdcard, returns:

    c:\sdk>adb shell
    $ su
    su
    # cd /sdcard
    cd /sdcard
    # ls
    ls
    # ^C
    c:\sdk>
     
  12. zimlokks

    zimlokks Android Expert
    Thread Starter

    try
    adb shell mount -o rw,remount -t auto /
    adb shell mkdir /tmp
    adb shell chmod 777 /tmp
    adb shell cd /sdcard/recovery.img /tmp/recovery.img
    adb shell chmod 777 /tmp/recovery.img
    now i believe that sdk includes a flash_image binary plz double check for me if not then do
    adb shell flash_image recovery /tmp/recovery.img
    that should work...if not i will try to figure out why and take the guide down temporally until i find out why...also if anyone has a spare device i may BARROW(not have i will return it asap side note i kno not alot of ppl will think about this but plz consider letting me borrow this phone to make a basic unbrick guide :D)
     
  13. ahdunno

    ahdunno Newbie

    Not working.....
    c:\sdk>adb shell mount -o rw,remount -t auto /
    returns...
    Usage: mount [-r] [-w] [-o options] [-t type] device directory


    Tried...
    adb shell mount -o rw,remount -t auto Coolpad_5860e /
    returns...
    mount: Operation not permitted
     
  14. zimlokks

    zimlokks Android Expert
    Thread Starter

    alright ull have to hold on until i get somethings straight, my apologies.
     
  15. zimlokks

    zimlokks Android Expert
    Thread Starter

    can u get adb shell to work?
     
  16. ahdunno

    ahdunno Newbie

    Yes, shell works. I used su and was able to ls and see the phones directories.
     
  17. zimlokks

    zimlokks Android Expert
    Thread Starter

    hmm....i wonder, do;
    chmod 777 /system/xbin/flash_image
    it may be also be located in bin. ill keep on trying sorry guys.
     
  18. ahdunno

    ahdunno Newbie

    Its in bin. Returns unable to change... read only.

    That's running cmd normal and as admin. Tried shell normal and su.
     
  19. zimlokks

    zimlokks Android Expert
    Thread Starter

    wtf....hmm ill make a script guys it should make things easier...just give me a day or two(life, work, and parents keep me busy)
     
    ahdunno likes this.
  20. zimlokks

    zimlokks Android Expert
    Thread Starter

    mount system
    do:
    adb shell
    su
    mount -o rw,remount -t auto /system
     
    ahdunno likes this.
  21. ahdunno

    ahdunno Newbie

    Here's what I get:

    c:\sdk>adb shell
    $ su
    su
    # mount -o rw,remount -t auto /system
    mount -o rw,remount -t auto /system
    Usage: mount [-r] [-w] [-o options] [-t type] device directory
    # chmod 777 /system/bin/flash_image
    chmod 777 /system/bin/flash_image
    Unable to chmod /system/bin/flash_image: Read-only file system

    I think syntax is wrong on the mount command because it returns the "Usage" message but I'm not really sure. Just recalling some of my really old dos days.

    2nd attempt: Added Device = No errors

    Start 2nd attempt -->

    # ^C
    c:\sdk>adb shell
    $ su
    su
    # mount -o rw,remount -t auto Coolpad_5860E /system
    mount -o rw,remount -t auto Coolpad_5860E /system
    # chmod 777 /system/bin/flash_image
    chmod 777 /system/bin/flash_image
    #

    :) Now we're getting somewhere.

    Also, I had some progress with a GUI called Android Control. I replaced adb.exe and fastboot.exe with current sdk tools version.

    When I flash the recovery.img, it reboots the phone but I'm still hanging in Recovery mode even after battery pull and normal start. It just displays "Recovery mode..." and is stuck there.
     
  22. ahdunno

    ahdunno Newbie

    Gave this a quick try:

    c:\sdk>adb shell
    $ su
    su
    # mount -o rw,remount -t auto Coolpad_5860E /system
    mount -o rw,remount -t auto Coolpad_5860E /system
    # chmod 777 /system/bin/flash_image
    chmod 777 /system/bin/flash_image
    # adb shell flash_image recovery c:\recovery.img
    adb shell flash_image recovery c:\recovery.img
    adb: not found
    # flash_image recovery c:\recovery.img
    flash_image recovery c:\recovery.img
    error opening c:recovery.img: No such file or directory
    # mount -o rw,remount -t auto Coolpad_5860E /sdcard
    mount -o rw,remount -t auto Coolpad_5860E /sdcard
    mount: Invalid argument
    # flash_image recovery /sdcard/recovery.img
    flash_image recovery /sdcard/recovery.img
    error opening /sdcard/recovery.img: No such file or directory

    Just want to say thanks to zimlokks for his help as well!
     
  23. zimlokks

    zimlokks Android Expert
    Thread Starter

    u mounted system u pushed the recovery.img to the sdcard but its either flash_image is flaky or the recovery image isnt the right one....i gotta get this fone!...
     
  24. zimlokks

    zimlokks Android Expert
    Thread Starter

    do this plz: adb shell mount

    just copy and paste the output plz may help
     
  25. ahdunno

    ahdunno Newbie

    The recovery is stock from the dload link you posted. As far as fl-img goes, I believe I may have placed the file there myself. Recovery Flasher app always would install its own when flashing and I thought that may have been an issue to trying to flash a custom recovery.
    I'llpost the mount output later. Out for dinner with the family now. Thanks
     
Loading...

Share This Page

Loading...