Related
This is a guide from a noob who spent a few hours today on my wifes phone trying to get it into Download mode after using Master Clear.....Worked fine before Master Clear but I wanted all the root apps IE Titanium) gone which the stock ROM update did not do. Being a total noob at Android and the Captivate being my first foray I though I would try to provide noob instructions to cover most bases. Most of the instructions here are scattered and not easy to find or are incomplete and make assumptions. This is specifically for those who cannot get into recovery or download mode.
Recovery/ Download modes are SEPARATE modes for for different uses.
I used recovery mode to "root' the phone AFTER putting the "update" file into the root directory using USB mass storage mode.
I use Download mode to install ROMS such as Stock and the 2.2 update.
My biggest issue was having a device that Would not GO INTO RECOVERY/DOWNLOAD MODE using any combination of button presses which it did before I Master cleared the phone. . Very frustrating. So I decided to bite the bullet and use the SDK mode. This first part will guide one on how to use the Android SDK and Command Prompt.
The assumption is all the drivers have been loaded for the Samsung Captivate.
First you need to have JAVA installed in your PC ( I did not)
The next you need to download the SDK package readily available
http://developer.android.com/sdk/index.html
This is what I did:
1. Created a folder called SDK on my C drive root directory.
2. Copied the android-sdk_r07-windows.zip SDK file to that directory
3. Extracted the ZIP into a newly created folder in that Directory
4. Deleted the Downloaded Zip package.
5. Moved all files from the new folder created by the extraction to the root SDK directory and deleted the now empty folder they came from. (This makes the path to the tools folder simple (as you will need to type that path out exactly in command Prompt)
My Path looked like this C:\SDK\Tools . Doesn't matter how you get there but tools folder must be in the path and the path must be exact
Next I started my Captivate normally and put my Captivate in USB debugging mode. Plugged in the USB.
I then opened the ODIN file I wanted to use whether original stock ROM or the new Froyo ROM
1. Opened command prompt on PC
2. Type CD\ to start at C root directory
3. from there I typed in CD \sdk\tools\
4. The next step involves the typing the command to open the screen you want the Phone to use...Recovery or download
4. Type in adb reboot recovery for the recovery screen (This gets you into the "three button screen" with no USB attached many cannot get into.
5. OR type in adb Reboot download to get the yellow download screen...
From there ODIN should indicate a com port..You hit start and the new ROM will be installed. There should be NO hangups on the indicated steps within ODIN. it happens pretty quickly.....YOu will see a filler bar at the top of ODIN and a blue line filler across the phone as the ROM is loaded.
I used Froyo..and discovered with Froyo I did not need to use the SDK method to get into recovery mode.....Froyo fixed that.
I have two Odin files. One for Jf6 Stock and the new 2.2.
I updated the JH7 FW using mini Kies in debugging mode. That was the only way I could load that FW which did not work OTA.
Bottomline is this is not a Hardware phone replacement issue if one cannot get into download mode. It is all about the FW in the phone. IF you can use the SDK you may likely not have to use it again.
OK ALL YOU EXPERTS Please correct or certify the steps.
Just trying to hep those who cannot read a 110 page thread that goes in many different directions.
Very nice instructions...
This type of detail is refreshing to see. Nice to see that assumptions aren't made. This type of detail can eliminate a lot of questions/posts.
I would just add - make sure you grab the right SDK - 1.5 ADB will not work with 2.1.
Thank You !
Followed your instructions but..
I tried to use sdk tools to reboot into download mode this is the specific comand I use:
adb reboot download
If I type this in the phone acts like i typed
adb reboot
The fact is that I searched help in the comand line and there is no reboot download only reboot recovery or reboot bootloader.
I cant get my kyocera torque into download mode and that is the problem I have also tried to boot with keys pressed nothing works. I want to get the phone to download mode so that I can install cwm recovery through odin
Maybe there is a esier way ?
U can make or buy a download mode jig. Quick search in the Captivate forums will show ya a thread of how to make one. Plus a lot of videos r on youtube as well.
Sent from my Nexus 5 using Tapatalk
First of all, many thanks for 4pda members.
It's time to post new thread for Lollipop.
This is for Kitkat me572c users.
(I can't make link so just copy the url)
● Lollipop firmware (UL-K007-WW-12.14.1.12) with root
Code:
mega.nz/#!LwJ3VBxK!4V4Ay-RzLS8x609zvyWL8IlcgI3xxfLcSqZ3gZkc52Q
● Install-Recovery.rar
Code:
mega.nz/#!C5ghzL6R!GR0WgLCumy6a429kB0ZjQOMxjPSylz07fVnHtKVm8ng
● ADB Driver
Code:
mega.nz/#!YAlxVbYS!7xfADRLuvcyO1GxRHtre3_e1TaVPmtIykqGbKCzUkkk
1) Can only be set on 4.4.2 (Kitkat). If you have already installed Lolipop, you must first revert to Kitkat. The computer should be installed ADB driver for the tablet and the tablet is turned on for the USB debugging. (no need to backup Internal memory. every data remain. but just in case, back up your data.)
2) Connect powered tablet to the computer. Download the firmware and rename it MOFD_SDUPDATE.zip, copy to the root of the memory card(MicroSd card) of the tablet. Download the archive Install-Recovery.rar and unpack it on your computer.
3) Run Install-Recovery.cmd, after the black command window turns up, volume buttons to select SD Download and power button for confirm. This will start the process of firmware.
Can anyone post instructions (in English hopefully because I'm lingual challenged) on how to revert back to KitKat if you've already upgraded to Lollipop? I didn't think that was possible...
Thanks so much!
I did a rough translation of the steps for downgrading in this thread. I haven't tried it myself, though, so I can't guarantee success.
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
does this work on ME176CX??
redhk886 said:
does this work on ME176CX??
Click to expand...
Click to collapse
I wouldn't try it. The process involves loading ROM images made specifically for the ME572C..
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
lexridge said:
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
gmaxjp said:
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
Click to expand...
Click to collapse
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
lexridge said:
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
Click to expand...
Click to collapse
Recovery is not CMW/TWRP, perhaps modified from stock.
Yep, What I did were execute series of command lines manually and crossing my fingers for several times
I'm expecting that will work in RPM based distros.
confirm, successful update using links/directions here.
kk stock rooted -> custom rooted 5.0 as above
yay!
significant speed increase in the ui animations, etc.
...google probably did a lot of support work for the moorefield
SacredMyths said:
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
Click to expand...
Click to collapse
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
gmaxjp said:
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
Click to expand...
Click to collapse
Good , no problem.
Now the only issue I'm having is a few emojis are black D:
where can i download the xposed apk for this model...
javcarbe said:
where can i download the xposed apk for this model...
Click to expand...
Click to collapse
Xposed Installer for Lollipop http://is.gd/jSVa1Q Use latest rev.
Since is a zip
How can I install a zip if I don't have a twrp recovery
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
i unzip run the bat but doesnt work i need an instructions to do it manually
C:\Temp\XposedForZenFoneLollipop_20150607>InstallXposedFramework.bat
'
'
' Connecting ZenFone ..
'
'
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
'
'
' Pushing files ..
'
'
error: device not found
error: device not found
'
'
' Installing Xposed Framework,
' please GRANT permission for this script on your phone !
'
'
error: device not found
error: device not found
error: device not found
'
'
' Done, rebooting ..
'
'
error: device not found
Instructions fail with the recovery not being able to mount the SDCard for some reason.
But the zip sideloaded just fine.
Thanks.
Also, any idea what recovery is compatible?
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
javcarbe said:
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
Click to expand...
Click to collapse
I guess you just have to turn on usb debugging, connect your device to your pc and execute InstallXposedFramework.bat and InstallXposedInstaller.bat
I did and nothing
Verified Downgraded from ZVA to ZV6 with full root access
LS991 Sprint Only.
QUICK GUIDE & TESTING
(Please read the entire guide before trying anything.)
I nor anyone at XDA is responsible for anything that may happen to your device.
Simply, by taking incentive to change the stock setup provided by the manufacturer for your device; you assume all responsibility for anything that happens.
download LGUP
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
(Thanks to shakeyabooti)
download LS991ZV6_00.zip and extract to get .tot file with winrar/7zip or any other unzipping program
http://downloads.codefi.re/autoprime/LG/LG_G4/LS991/LS991ZV6/LS991ZV6_00.zip (or google/xda search for mirrors) (Thanks to autoprime)
download LGROOT
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
(Thanks to Unjustified Dev)
download LG Drivers
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (or google)
(Thanks to Unjustified Dev)
download rootedsystem.ls991.zip and extract to get .img file with winrar/7zip or any other unzipping program
http://forum.xda-developers.com/sprint-g4/general/zv6-root-success-t3205963/page3
(scroll down to parin11's post. #29 and thank you to both parin11 and mswlogo)
-install drivers
-enable oem unlock in developer settings
-plug device in as charge only, switch to mtp to verify drivers are working correctly, then disconnect
--if on mtp then switch to charge only to verify drivers are working correctly, then disconnect
-enable usb debugging
-reconnect and drivers auto install
-disconnect after 2 minutes.
--while you wait;
-for LGUP extract and install _dll version then the second msi.
-for LGROOT extract to a folder to keep things organized
-remove the back cover of your device and leave it off for access to battery pulls.
-power off device
-hold volume up key and plug in your device and keep holding the volume down key until it passes the screen that says download mode.
-open LGUP
-make sure UPGRADE is checked/has a little circle/bullet point
-click in the empty space directly to the right of where it says BIN with the checkmark
-3 dots will appear to the right of the program in the same row that says BIN; which is your browse option
-navigate to LS991ZV6_00.tot and select
-reconfirm your UPGRADE option is checked
-press start and allow the device to fully complete the process.
-your device will boot to the loading screen right before showing the android desktop and "freeze"
-In most if not all new flash scenarios; your device will not boot up until a factory restore and clear cache is done.
-To do this you must simply remove the battery and usb cable from your device AFTER it has hung on the logo for about 3 minutes / 180 seconds.
(Most new devices average a first time boot of up to 150 seconds maximum to be considered fully "loaded")
-With the battery and cable removed; hold the power and volume DOWN button together at the same time.
-insert the battery while holding these buttons together and just wait while holding them and you will see it says booting into recovery.
-once your in the recovery you use the power key to select and the volume keys to navigate.
-navigate to factory restore/reset hit the power button, navigate to "yes" out of all the "no's" and hit the power button again
-it will say its complete and either ask you to go back reboot or return to menu. RETURN TO THE MENU, do not boot up yet.
-Once returned to the main menu you will see it says clear cache. Select and press yes and now you can select reboot; or return to menu then reboot.
Your device will be on ZV6 stock and fully booted after this.
Now this is where it gets kind of odd because my device never actually loaded the rootedsystemls991.img file nor did I run a root script
when attempting to flash it with the steps listed in the other root guides BUT i followed this guide from step one to step 9 (and outlined continuing through the guide)
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
this allowed all the necessary rooting files to be in the places necessary to execute the root but I did one extra step
I did an adb.exe push rootedsystem.ls991.img /data/local/tmp command as well while the device was on the home screen.
This was so I could basically emulate the command listed by |Unjustified Dev| as it also states to do in the ZV5 guide.
So this is what I did,
-After my device booted up and loaded to the home screen on stock zv6, I opened the LGROOT folder
-held shift and clicked "open command prompt here"
-when cmd opened I ran the following command
adb.exe devices
This allowed me to see that my device was connected to the PC with its generated serial number.
-then i ran the following command
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
-After this I applied the command to push the .img file to the same location. This was the "emulated command" I spoke of.
adb.exe push rootedsystem.LS991.ZV6.img /data/local/tmp
-I then added the .img file directly to the Internal Storage / Stock Phone MTP storage
-Afterwards I simply powered off my device, removed the usb cable, held the volume up button, then plugged it back in still holding the volume button until
the text download mode was gone again; and no this is not a timing thing im just saying that again incase anyone forgot how to get into download mode. lol.
-I then ran the ports.bat file included in LGROOT to find the COM port drivers.
-Followed up with this command
Send_Command.exe \\.\COM8 (<--Replace number here with the COM port listed for the "DIAG" portion of the device.)
-Now, still in download mode I executed this command about three times with no avail.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
(Which by the way I had the file in both the MTP side of root and in the data/local/tmp)
or you could change it to /data/local/tmp/ like
dd if=/data/local/tmp/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This would possibly solve the issue I was having. So you would have root now.
THIS PART REQUIRES TESTING.
BUT continue reading you'll be shocked.
sidenote:
They state that all you have to do is put the .img file into the root of your Internal Storage / Stock Phone MTP storage
and run the command in download mode but this failed when I tried to execute it.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
The command above was the command they listed to be able to restore the device from stock to stock with root access. Please note I tried this command while the phone was turned on in debugging with enable oem unlock on, while in download mode and while in recovery mode all with debugging and enable oem unlock checked with either no response / device detected, or attempts causing the command prompt to show the # symbol after a few seconds of executing the line above which shouldn't happen,
since the size of the file is 4GB... The ENTIRE SYSTEM PARITION. -_-. There is a considerable amount of hangtime here is what I'm saying.
If the dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0 command worked for you then great, boot up and enjoy root! BUT.
For those who didnt have luck doing so with the command that failed me above, for some odd reason after pushing both the SuperSU bundle and the entire .img file to /data/local/tmp/ with the files in the internal storage /data/media/0/ as well
trying to only execute the command for the .img (/media/0/ not /local/tmp/) | (not the "fixed" command") and NOT for the SuperSU
eg.
-This was for the image which was the only one I used. (USED)
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This was for root only which I did not touch. (NOT USED)
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
-This caused the device to simply show the # sign almost immediately as I spoke of above.
-I typed in LEAVE and the device booted back up.
-The odd thing I'm speaking about is when I turned the device back on it showed that SuperSU was installed and was requesting to be "updated".
-I chose normal and it asked for a reboot. Rebooted started back up and it asked for root access when I clicked on it.
-Granted and successful.
-Went to the playstore.
-It said update next to SuperSU which was even odder.
-Clicked it and updated it and it got the latest version, asked for one more reboot, started back up, then I opened the app. Everything was normal.
-Downloaded root checker basic, titanium backup, and greenify immediately.
All passed with flying colors.
-There is an error that pops up in titanium backup regarding adding underscores or slashes into modified file directories for backup purposes assumed but
opening greenify ended up picking up this issue and requesting to fix it.
Why not right?
-Heh. It worked.
I have never experienced this type of latency within programming so this is extremely odd and without executing the SuperSU script command or,
a sucessful flash of the .img it just seems too odd, but; there you have it! All of the mods / developers working on this device I would like to hear
your insight on this.
So you have two options. Follow what I did or test the command with /data/local/tmp/ and try your luck flashing stock with root again or just run the root script on stock instead of trying to flash from stock to stock rooted.
Thank you and enjoy your root!
P.S. I didn't end up experiencing this issue since it works perfectly but in the event that SuperSU does not install after trying to flash the .img and getting
the 2 second delay with the # sign appearing immediately and rebooting after 3 attempts I would have personally tested the original adb SuperSU script command recommended for the ZV5 users
which was listed above and is
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
And for the love of your device. Don't try to update your device from an older version using this method. Ayeeeyiyiy
I will re-test what I stated and make a completely organized guide and video for everyone.
I just wanted to let you all know now to assist the entire community in understanding this device's root process a little more.
Will this work with brand new phone?
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
wow, thanks!
Thanks for all your hard work. This phone has been one of my best and the only thing missing has been root, etc. Chewing over your instructions and thoughts. My confidence level is not quite there to pull the trigger, but i'm getting close. Hoping this is a promising method for those of us on Sprint ZVA. I will continue to do research and watch this thread. Thanks so much for your time, tips and expertise.
brpaaron said:
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
As long as its not been updated to zvb. Antirollback implemented on zvb
Still running zv6
I am still running zv6 and never updated. Do I need to update to downgrade to root or can I just skip to after the downgrade?
i am running zv9 i can not stock zv6
I have ZVC can i downgrade to ZV6?
LG G4 LS991.
LG G3 D850 ROM Fulmics 6.6
Recovery TWRP v2.8.7.0 bumped
LS991 ZVD
Hi there does anyone know whether or not it will work on the ls991 zvd update??? Sprint variant
Ls 991 ZVD
Will this method work on ls991 zvd i havent found anything on it
Expo6810 said:
Will this method work on ls991 zvd i havent found anything on it
Click to expand...
Click to collapse
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
TheMadScientist420 said:
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
Click to expand...
Click to collapse
Is there anything i can do for my zvd
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as far as i know. nothing
new root methods and tweaks come out everyday.
all the good devs as far as i know have stopped developing g4 and moved on due to the locked bootloader d other issues
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
a root method has been exposed on the g5
intime it may come for the g4 also but not adapted rite now
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
Right now i have ZVC software version can i downgrade zv6????
hawzsth said:
Right now i have ZVC software version can i downgrade zv6????
Click to expand...
Click to collapse
no u will brick
TheMadScientist420 said:
no u will brick
Click to expand...
Click to collapse
its already brick any solution...... now its show 9008 no power on ...
hawzsth said:
its already brick any solution...... now its show 9008 no power on ...
Click to expand...
Click to collapse
octoplus box with jtags the only fix
thats a hardbrick
---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as of rite now no
If I downgrade my zva will it allow me to sim unlock it
Somebody know if can downgrade ZVI to another version
Pls any update on locked bootloader?
Thank you!
Just learned here enough. Thank you!
I just head through UsU thread after reading this; Respectively thanks for the post again! ??
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
Any luck?
Thank you very much
Jayfreshh said:
Any luck?
Click to expand...
Click to collapse
Did you ever find anything for this device?
remarkablecow913 said:
Did you ever find anything for this device?
Click to expand...
Click to collapse
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?
Jayfreshh said:
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?
Click to expand...
Click to collapse
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
Click to expand...
Click to collapse
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying
remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying
Click to expand...
Click to collapse
Okay if anything works out when you try let me know
The bootloader can be opened in developer mode for this devise if I'm correct
You can unlock bootloader in developer options but from there. I'm stuck and really want to get root and see what "deleted" files I can recover from a factory reset. Anybody ever try twrp for same chipset like someone was talking about doing?
rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
[Update Anyone?]
I picked up a Coolpad 3632a yesterday and I've been trying to ROOT it for quite a while nowl; trying Kingroot v5.3.7 without PC, and KingRoot 3.5 on PC both failed to ROOT. I've been out of the loop for quite a while regarding Android devices and OS - the last Android Phone i owned was the LG G3 if i remember correctly. According to the available info I've found searching for Rooting Options for the coolpad 3632a it all seemed almost %100 easily rootable with or without PC mainly using Kingroot.
If anyone was successful in rooting this device (Coolpad 3632a / Android 7.1.1) - please let me know, my main goal is to find a good custom ROM and load it replacing the Bloat/Malware filled phone!
Thanks again to anyone who has taken the time to read and respond with any news (good or bad) on getting this device successfully rooted.
-=Mac3lite=-
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
EDIT: I just obtained temporary root.. seeing if it sticks.
Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.
phonecapone said:
Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.
Click to expand...
Click to collapse
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?
dwaipayan774 said:
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?
Click to expand...
Click to collapse
It gets detected just the commands fail. There is a white "Secure Phone" line of text across the bottom left. Im going to try loading an sdcard to see if it will auto update anything.
I can't even use Flash Programmer in QFIL or many other apps in QDLOADER 9008 mode. I know the firehose is the correct one yet it never wants to boot. I don't know why.
MTKLogger might have before unless i'm thinking of a different handset here. But as of the moment it doesn't.
No luck with the sdcard. I think it's about time to factory reset this device and put it up for sale. I'll post the firmware here shortly.
Here is the firmware - https://forum.xda-developers.com/android/general/rom-coolpad-defiant-3632a-stock-t3855692
Temporary Root
phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
What did you do? I've been trying for months now.
dwaipayan774 said:
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
Any chance on a repost of the file?
dwaipayan774 said:
Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
hey the link is dead. could you make a new link?
I'm trying to create an application to make flashing files on our pixel devices easier.
Features:
Install ADB
Unlock bootloader
Reboot to bootloader
Download and install factory images
Download and install TWRP
Download Magisk
Easy to use GUI
Enjoy! :good:
Credit to Dees_Troy and bigbiff for TWRP image.
Feel free to modify and hack away at the source.
WARNING: I am not responsible for anything that goes wrong using this tool, it works fine on my windows 10 machine, and tested on windows 7. However, make sure you know what these tools are doing beforehand.
New update!
Beta Release
What's New?:
All new base being built.
Better .exe support (requires installing the app)
Console interface for now.
Removed some features that were broken in the old app, will add them back one-by-one, but this time, not until they work 100%.
Usage:
Just follow the prompts on screen.
Allows picking the files for booting TWRP or pushing files via ADB.
Install:
Easy method (requires install): https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshAtchDB-2.3-win32.msi
Install the app with the provided .msi, choose where you want to install it. Open the folder where you installed it and run the crosshatchdbbeta.exe.
Build/Run from source:
Requires:
source .py file: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshatchbeta.py
cxfreeze config: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/setup.py
To run from source, just install Python on your PC, then from cmd window run : "pip install requests".
Then just double click on the crosshatchdbbeta.py file.
To build the .exe:
You need both files from above.
Install Python
python -m pip install cx_Freeze --upgrade
With setup.py and crosshatchdbbeta.py in the same directory, run "python setup.py build"
This is a very minimal release, I will continue to fix any bugs and add features once they are working better.
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
**Didn't want to waste thread space so I'm editing this to reply** - Thank you so much for the response below! Very helpful! I'm up and running and really appreciate the tool and the help!
NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
No problem, quick usage guide to make sure it goes smooth.
Enable OEM unlock in developer options, also enable ADB debugging.
Plug in your phone, run crosshatchdb.
Select option 9, this will auto download and extract adb to your c: drive.
Select option 1 to check for ADB devices, check the box on the dialog that pops up on your phone.
All set. You can download magisk directly to your phone or push it from your PC.
Reboot bootloader option 2, from here you can unlock the bootloader(formats your phone btw).
Setup your phone, enable ADB debugging again and your free to reboot bootloader and download/boot TWRP to flash magisk.(use TWRP img not zip)
Hopefully these instructions are not too confusing, it is pretty easy once you do it once, and the tool really does make the next time you do it faster.
Tested on a windows 7 virtual machine and my own personal windows 10 machine.
NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
The time to unlock a Google purchased Pixel isn't the issue. The factory reset just sucks if you run stock for any time before doing it.
Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Click to expand...
Click to collapse
Good idea, should be easy to pipe logcat output to a text file.
ADB sideload can be added as well, next update will probably be when TWRP ADB is fixed, or sooner depending how long that takes.
Already thinking of ways to make the current version of this script more automated, but I like to err on the side of explicit is better than implicit.
Thanks for the ideas.
Can this install TWRP ?
Zorachus said:
Can this install TWRP ?
Click to expand...
Click to collapse
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Click to expand...
Click to collapse
This.
It is a good option of you want an easy way to just boot TWRP in 1 button, if you don't want to install a custom recovery like TWRP.
New update coming soon, decided that command line didn't work very well for this purpose...
Also working on making all of the actions smoother.
New update released, let me know if you have any issues or feature requests, still waiting for TWRP to be fully functional before adding ADB sideload options.
CMD window still wants to hang out for now, you can minimize it though if needed.
can you add a (check for update)
Maty360414 said:
can you add a (check for update)
Click to expand...
Click to collapse
Yes, that is on the list for next update.
When TWRP is more reliable I will probably add options for copying TWRP backups to your PC as well.
Still need to get rid of the cmd window and cut down on having to open browser windows or file selection dialogs, just to get it feeling less clunky.
I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!
quinejh said:
I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!
Click to expand...
Click to collapse
Glad to hear it helped out, working on some new updates to make the UI even better.
Trying to make all of the download links update automatically too, just working on some web scraping again ?
It's a nice little tool if something gets messed up, also for new users to get up and running.
New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.
boostedduece said:
New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.
Click to expand...
Click to collapse
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?
frewys said:
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?
Click to expand...
Click to collapse
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.
boostedduece said:
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.
Click to expand...
Click to collapse
Right
So it doesn't automate the process the same as for xl?
frewys said:
Right
So it doesn't automate the process the same as for xl?
Click to expand...
Click to collapse
It will still install ADB and allow you to run reboot bootloader, boot TWRP, factory reset, ADB logcat, unlock bootloader.
But the only extra part that is manual would be extracting the factory image into the c:\crosshatch_stuff\platform-tools folder.