Database Info

[CWM] Clockworkmod Recovery for the Samsung Blaze 4G

Shabbypenguin presents...
Clockworkmod Recovery 6.0.5.0 for Blaze 4G
Sponsored by Shabbypenguin.com. Have you tipped your devs today?
DO NOT CHECK REPARTITION! YOU HAVE BEEN WARNED!​
Why the big red warning? Far too many people have broken their devices by not following these instructions! Search the forums, or drop by IRC - you'll see plenty of examples.
So the T-Mobile CWM worked... well sorta you couldnt see anything, so i fixed it up and made sure it worked fine for yall enjoy
Instructions​
Download Odin 1.85 - see section below.
Download the Clockworkmod recovery TAR - see section below.
Extract the contents of odin-185.zip.
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR you downloaded.
Put your device into Download Mode:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down + Power.
You should now be at Download Mode.
Click Start in Odin.
If you are having issues getting into download mode check out these instructions
That's it! Your device will autoreboot, and your phone should be working properly again.
Downloads​
Download Odin 1.85
CWM Touch 6.0.5.0
​
Credits:​
​
DrTaru: stock device, remote access, lots of testing, screenshots, patience
k0nane: k0nane for being an awesome sauce kind of guy
JFigure/Watcher64: initial testing and pointers/proof of concept
UberPinguin: notes on building kernels for celox, which also apply to this device
SOURCE
If you feel as though my work is worth your money, you can click the link in my signature to donate to me ​

second'dddddd

P-O-S-T :: R-E-S-E-R-V-E-D
{
"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"
}
Original artwork by Pendulum via Gasolin3.
...for future use.
Follow me on Twitter @k0nane and @publik0!​

Okay.
Im having issues.
I have a T-Mobile Samsung Blaze4G
Followed every step to the T.
When I do Vol up+ Vol dwn+ PWR
i come to a recovery screen and at the bottom it says Manual mode.
I dont see anything that says "Download Mode"
From the top down this is what I see
Android Systems recovery <3e>
Reboot system now
apply update from sdcard
wipe data/ factory reset
wipe cache partition
Any ideas?
In Odin I had to download Keis Air because my computer was not installing drivers for the phone. once i downloaded Keis Air and plugged in the phone it recognized it and finished installing the drivers. I did a computer reboot and when I follow the steps I get a YELLOW highlighted box in ODIN under the ID:COM part that says 0:[COM3] in yellow.
I hit start but nothing happens.

Worked awesomely! Just need root now. ;-)
Thanks everyone for all the hard work!

avelasqu said:
Worked awesomely! Just need root now. ;-)
Thanks everyone for all the hard work!
Click to expand...
Click to collapse
I guess you missed this, which was posted at the exact same time.
http://forum.xda-developers.com/showthread.php?t=1591598

k0nane said:
I guess you missed this, which was posted at the exact same time.
http://forum.xda-developers.com/showthread.php?t=1591598
Click to expand...
Click to collapse
Ah shucks. I was able to use the SU files from the t989 and it worked for me.
Is there a difference in what I did and what the root kernel will do?

rooted kernel has a few perks to it that k0nane threw in . hopefully you guys can now attract some devs and start working on roms/cm . we aim to please, just remember us the next time you have a device that isnt getting much love ;P
SCossio from what i understand the key combo gets you into a quasi-downloadmode, need to hit vol up to confirm to enter download mode and then you can plug it in and begin to flash this
perhaps some nice blaze owner can make a how-to video? sorry if our instructions seem off or vague, myself or k0nane have never seen this phone let alone touched one, so we rely on you guys (blaze owners) to help with these kinds of things.

Here is a video on how to successfully enter download mode every time.

shabbypenguin said:
rooted kernel has a few perks to it that k0nane threw in . hopefully you guys can now attract some devs and start working on roms/cm . we aim to please, just remember us the next time you have a device that isnt getting much love ;P
Click to expand...
Click to collapse
This! We're here to help. Feel free to come join us on IRC.

i highly suggest you guys check out https://play.google.com/store/apps/details?id=com.s0up.goomanager to download all your roms etc, just the same as rom manager except you can use any recovery you wnat. same rules still apply... if your devs dont post roms/kernels to goo then they dont show up in teh app

Pre-reqs?
Use odin to install the rooted kernel first, then clockworkmod, correct?
This is my first time rooting. I just wanted to double check that the clockworkmod image didn't contain the rooted kernel already.
Dedridd

It doesn't although for the sake of only incrementing the flash counter once it probably could be consolidated.
However, if you flash CWM its a simple process of flashing the SU binary zip package from the sdcard with CWM, same end result.

I keep getting this message when I try and run odin on my Samsung Galaxy S Blaze 4g I know that I am doing everything right maybe it is my phone
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Someone help me plz

Total n00b here.. with a stupid question. (or twenty).
Let's say, if this "Clockworkmod Recovery for Blaze" was installed via Odin and then Rom Manager app flashed with Clockworkmod Recovery for Galaxy S 2, what happens to the previous files (loaded via Odin)? Do both recoveries co-exist? Or does one replace the other? and if so, can this process be repeated again?
I'm just trying to understand this process.
[Update]: I repeated the process described in this thread, figuring that having recovery for some other phone model would not be a good idea, probably not be a well functioning recovery... everything seemed to have worked great but how can I verify that I have the correct version of recovery now? (I apologize for another stupid question in advance).

SCossio said:
Okay.
Im having issues.
I have a T-Mobile Samsung Blaze4G
Followed every step to the T.
When I do Vol up+ Vol dwn+ PWR
i come to a recovery screen and at the bottom it says Manual mode.
I dont see anything that says "Download Mode"
From the top down this is what I see
Android Systems recovery <3e>
Reboot system now
apply update from sdcard
wipe data/ factory reset
wipe cache partition
Any ideas?
In Odin I had to download Keis Air because my computer was not installing drivers for the phone. once i downloaded Keis Air and plugged in the phone it recognized it and finished installing the drivers. I did a computer reboot and when I follow the steps I get a YELLOW highlighted box in ODIN under the ID:COM part that says 0:[COM3] in yellow.
I hit start but nothing happens.
Click to expand...
Click to collapse
Hey there. The phone must be plugged into the computer before you put the battery in.

You guys can also just turn off your phone hold down the volume up+volume down and plug the usb cable into the phone... Make sure the other end is plugged in to the computer first , Odin 100%
Sent from my SGH-T769 using xda premium

Done...now will wait for ROMs. Thank you to all involved in making this happen.
Sent from my SGH-T769 using XDA

De Odexed / Debloated rom should be coming tomorrow. possibly maybe.

Awesome! Can't wait. Thanks for all of the hard work!

[Q] Infuse stuck on boot screen

Background: Trying to update my stock infuse to Jelly Bean. Looked into what was needed via hours of research. Used SuperOneClick to root phone (Success), installed ESFile Manager to help install mod 3e recovery (success), used ROM Manager to flash CWM (Success).
Upon testing the CWM by booting into recovery, this boot screen issue started.
- I've tried hard resetting, (no success, won't go past the Samsung screen).
- I'm currently using Odin to restore stock firmware, but it's been about 25 minutes so it's probably not working.
- I can only get to Samsung screen and download mode, that's it!
I need my phone and I need to get some sleep. what am I missing? Much appreciated
thanks

here's a shot of Odin right now. It's stuck on "setup connection"
{
"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"
}

Here is what I used to Un-boot loop my phone worked like a charm, the instructions we're a little un-clear but if you read through it, a few times, it's really rather easy. You need to download Java (Jave Runtime Enviorment, also known as JRE I used OpenJDK Java 7) on your computer, download the Heimdall one click packages, put your phone in download mode:
-Pull the battery out and make sure the phone is NOT connected by a usb cable.
-Put the battery back in!
-Hold vol up+Vol down. DO NOT PRESS POWER.
-Plug in the USB cable.
Open the downloaded heimdall one click with java (in Ubuntu Context menu Windowz is likely the same) and it will return your phone back to stock which is where you want to start for I believe almost all the JB ROMs. If you search around Quickster made some other One click packages to get you rooted and CWM installed as well as Kernels and other stuff. These things work great and to me are a million times easier than every other method.Good luck and if there's any other help I can provide I'll do my best

dginsd said:
Here is what I used to Un-boot loop my phone worked like a charm, the instructions we're a little un-clear but if you read through it, a few times, it's really rather easy. You need to download Java (Jave Runtime Enviorment, also known as JRE I used OpenJDK Java 7) on your computer, download the Heimdall one click packages, put your phone in download mode:
-Pull the battery out and make sure the phone is NOT connected by a usb cable.
-Put the battery back in!
-Hold vol up+Vol down. DO NOT PRESS POWER.
-Plug in the USB cable.
Open the downloaded heimdall one click with java (in Ubuntu Context menu Windowz is likely the same) and it will return your phone back to stock which is where you want to start for I believe almost all the JB ROMs. If you search around Quickster made some other One click packages to get you rooted and CWM installed as well as Kernels and other stuff. These things work great and to me are a million times easier than every other method.Good luck and if there's any other help I can provide I'll do my best
Click to expand...
Click to collapse
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed

mendozer said:
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed
Click to expand...
Click to collapse
Perhaps try to use the Heimdall "back to stock" while in that Emergency mode. The Heimdall program will also tell you if it recognizes a phone attached in download mode, and if it will recognize the phone and flash you back to stock, you can also have it put you back on stock bootloaders which sounds like your problem (though flashing bootloaders is dangerious but in your case may be nessessary). Maybe PM Quickster see if he recommends trying to flash with Heimdall on that mode you've entered, I might also try using an alternate USB cable if you haven't already.

mendozer said:
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed
Click to expand...
Click to collapse
The computer icon with a yellow hazard triangle in between them is a form of download. Use Heimdall after making sure you have the correct JRE and drivers.
Sent from my SGH-I997 using xda premium

psal217050 said:
The computer icon with a yellow hazard triangle in between them is a form of download. Use Heimdall after making sure you have the correct JRE and drivers.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I have the stock firmware from Samsung. that includes the drivers I presume? the md5 file

holy smokes I'm so relieved it worked!
So, I used Heimdall's froyo Uck3 firmware or whatever since that's what was in the package. I still want Jelly bean. I have the JB folder with what I suppose I need (think it was from android geeks). However, since this was painless, is there a Heimdall one click for JB?

mendozer said:
holy smokes I'm so relieved it worked!
So, I used Heimdall's froyo Uck3 firmware or whatever since that's what was in the package. I still want Jelly bean. I have the JB folder with what I suppose I need (think it was from android geeks). However, since this was painless, is there a Heimdall one click for JB?
Click to expand...
Click to collapse
I haven't seen a Heimdall for JB, or any custom ROM I think because it requires a special PIT file to make. I used this ROM http://forum.xda-developers.com/showthread.php?t=1776129 To flash It though you have to be on the Gingerbread bootloaders, and the instructions for flashing it want you to even flash CM9 ICS, before you flash the final JB ROM. Basically follow the instructions thoroughly or you'll end up in a boot loop ( Not that that's a big deal, now that you have a quick easy way out)

meanhs sal
darn, I'll have to see if JB is really worth it to take the chance again. I also noticed that froyo version from the Heimdall is quirky with some apps. I turn the phone on and several apps just close on me. I get the buzz of death (the one and three) as i like to call it

I'm pretty sure there's Gingerbread version of the Heimdall one click, I'd flash that as almost all the newer Roms are going to require you at least have upgraded to the Gingerbread bootloaders.

[HELP] Verizon S3 won't go to Download Mode.

Hi, everyone.
I have a Galaxy S3 from Verizon and I cannot root the phone, it simply won't go into download mode.
I have tried formatting it, but still doesn't work.
I have Android 4.1.1 version in it, I have called Verizon and they didn't know how to do it either.
I have done the combo keys Volume Down, Home and Power, but it eventually just starts up normally.
I have tried the same thing on another S3 from Verizon and it didn't go into download mode either.
I did get an international version of the phone, so the problem must be verizon.
Please, help!
Thanks!

You're being unclear. You say you have a Verizon GSIII but also say you have an international GSIII, which is it?
For download mode, pull the battery then try again but hold it for like 15-30 seconds.
Sent from my SCH-I535 using xda app-developers app

Make sure you are not connected to your computer until after you get into D/L mode. I know if I am connected to the PC before I try to enter D/L mode it will not work.

ColdKill3r! said:
Hi, everyone.
I have a Galaxy S3 from Verizon and I cannot root the phone, it simply won't go into download mode.
I have tried formatting it, but still doesn't work.
I have Android 4.1.1 version in it, I have called Verizon and they didn't know how to do it either.
I have done the combo keys Volume Down, Home and Power, but it eventually just starts up normally.
I have tried the same thing on another S3 from Verizon and it didn't go into download mode either.
I did get an international version of the phone, so the problem must be verizon.
Please, help!
Thanks!
Click to expand...
Click to collapse
You have to make sure your USB cable isn't connected while trying to put into download mode. Also hold Power, Volume Down and home button until phone vibrates and then release. Hope this helps

Hey, guys.
Thanks for the replies.
Anyway... I have it disconnected from the USB and I also have already tried the battery thing, but none of those things worked.
I have 3 S3's, one of them is an international model, which I have rooted myself and everything worked (download mode), but the other 2 are the Verizon version (SCH-i535) of the phone isn't working - even though I've tried taking of battery, memory card, sim card, no USB cable connected. I have USB debbuging and everything that I need to have activate, but it won't go into download mode. I wonder if it's blocked (which I doubt, since I've seen people saying they rooted the Verizon S3).

Its actually a button sequence of the following:
While phone off and unplugged;
Hold Home Button (Just home)
Then hold Volume down while still holding home.
And finally, hold power while holding Home + Volume down
Let me know how that works out for you.
{
"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"
}
Team Kernelizers; Kernel tweaking at its finest.

It works now. I was just not holding it long enough. I'd let go of it as soon as the phone would vibrate when I should keep holding 'em.
luis86dr said:
Its actually a button sequence of the following:
While phone off and unplugged;
Hold Home Button (Just home)
Then hold Volume down while still holding home.
And finally, hold power while holding Home + Volume down
Let me know how that works out for you.
Click to expand...
Click to collapse

help mine doesn't go neither
i did the same key combination but i don't come into download mode.
i enter a screen with an android robot lying on the back, open belly with a warning sign..
can not root ( pls help

misstq said:
i did the same key combination but i don't come into download mode.
i enter a screen with an android robot lying on the back, open belly with a warning sign..
can not root ( pls help
Click to expand...
Click to collapse
I'm having the same problem as you. Except the difficult thing for me is that I can't see my screen because the lcd is broken. I have tried the buttons and it just wont go into download mode.
The next thing I tried to do was see if I could get it into download mode on a fully functioning SGS3. I tried it out, and even though I was using those buttons, it still wouldn't go. I tried again, but this time I held the three button combo for about 2-3 additional seconds AFTER I felt the vibrate and it worked!! Try that, and hopefully it will solve your problem.
However, I tried my same steps on the broken lcd phone and it didn't seem to work. (at least I can't tell if its in download mode or not)

Download mode
ColdKill3r! said:
It works now. I was just not holding it long enough. I'd let go of it as soon as the phone would vibrate when I should keep holding 'em.
Click to expand...
Click to collapse
Home...Volume Down...Power...vibrate...hold until warning message about using custom ROMs appears. Then press
volume UP and I get the green Android robot and this message "Downloading...Do not turn off target !!" Upper left
corner of screen reads in tiny red text "ODIN MODE"
followed by PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Does the above mean that I am in Download Mode? When I plug in the USB cable there is no response.
What does "Do not turn off target !!" mean?
If I AM in Download Mode at this point I should be able to use heimdall at the command line, but here are my responses
at the command line:
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ heimdall detect
heimdall: command not found
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ ./heimdall detect
Device detected
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ ./heimdall print-pit
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
As seen above it seems like there's an attempt to connect to my S3 but the libusb error: -3 sent me off searching about for a solution
and I found something about installing libusbx-1.0.17.
Followed the instructions in the INSTALL file
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
#1 seemed to work, #2 "make" returns the following:
[email protected] ~/Desktop/libusbx-1.0.17 $ make
make: *** No targets specified and no makefile found. Stop.
So, that's where I am stuck. Does #2 mean that I should type "make" and the specify a file as "target"
Anyone know where to go next?
The wiki says "Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary."
I don't object to rooting my phone, but if this heimdall method is the CM recommended method I'd like to get it to work. Suggestions???
Thx,
kb

What are you trying to do? Root? Install cm? I think there are much better ways to do what you're trying to do, but you need to be clearer.
Sent from my SCH-I535 using Tapatalk 2

No download mode.
I have a sprint SPH-L710 S3, and have previously gotten into download mode with no problems, but now, I get the Samsung logo, and then the Samsung galaxy SIII logo, and then a reboot to recovery, I can't get into download mode any longer to load via odin.
I am completely stuck. I've been working on this all morning trying to recover from my current soft brick state.
I've tried to restore from the backup, but can't be sure it's the correct backup. the filename is 1970-01-01.21.17.36/. I can't help but think that is not correct.
I'm currently running CWM recovery v6.0.3.1, and have been trying to update to 4.4.2 kitkat from stock 4.3 update.
Any assistance is greatly appreciated.
Thanks for any assistance you can provide.

utter madness said:
I have a sprint SPH-L710 S3, and have previously gotten into download mode with no problems, but now, I get the Samsung logo, and then the Samsung galaxy SIII logo, and then a reboot to recovery, I can't get into download mode any longer to load via odin.
I am completely stuck. I've been working on this all morning trying to recover from my current soft brick state.
I've tried to restore from the backup, but can't be sure it's the correct backup. the filename is 1970-01-01.21.17.36/. I can't help but think that is not correct.
I'm currently running CWM recovery v6.0.3.1, and have been trying to update to 4.4.2 kitkat from stock 4.3 update.
Any assistance is greatly appreciated.
Thanks for any assistance you can provide.
Click to expand...
Click to collapse
I'm going to direct you post your question in the Sprint S3 Q/A section as continuing here will cause confusion since our Verizon S3 has TW 4.3 and we are presently locked down to the point where we are unable to use a custom recovery.
CWM defaults to naming backups in the year 1970 so that looks right at a cursory glance. Last thing, your recovery is very out of date, given how KitKat works with our Verizon S3, you need a newer version of CWM to flash KitKat. Post in the Sprint section and be as specific as you can be as to what you want to accomplish.
Merry Christmas!

SS S3
skywalk3r89 said:
I'm having the same problem as you. Except the difficult thing for me is that I can't see my screen because the lcd is broken. I have tried the buttons and it just wont go into download mode.
The next thing I tried to do was see if I could get it into download mode on a fully functioning SGS3. I tried it out, and even though I was using those buttons, it still wouldn't go. I tried again, but this time I held the three button combo for about 2-3 additional seconds AFTER I felt the vibrate and it worked!! Try that, and hopefully it will solve your problem.
However, I tried my same steps on the broken lcd phone and it didn't seem to work. (at least I can't tell if its in download mode or not)
Click to expand...
Click to collapse
Thank you so much , I followed your way and succcessed

the walkingdead said:
Thank you so much , I followed your way and succcessed
Click to expand...
Click to collapse
Not trying to be mean but please do not revive 6 month old thread with a simple "Thanks" post. The moderators hate that. That's what the thanks button is for.
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
Not trying to be mean but please do not revive 6 month old thread with a simple "Thanks" post. The moderators hate that. That's what the thanks button is for.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Hey Sandman,
Thanks for the suggestion.
But since there are hundreds of S3s still being sold, and hundreds of buyers looking for support like this, shouldn't we supply this topic if someONE some where might need thsi?
Like I just did on my New bought a NEW a month ago
Huh?

Idol 3- Stuck In Bootloop After Flashing boot.img

Idol 3 Bootloop
I need your assistance
Hi, I have read through all of the posts and tried to find a solution with no luck.
I tend to always go one step too far with my hacking and playing/experimenting.
Alcatel One Touch Idol 3 5.5 6045K
It was booting into TWRP fine.
Then I wrote the non-functioning boot.img (which I thought was the backup of my pre-rooting version) on top of the working twrp recovery image.
So instead of installing the boot.img to the boot partition, I installed it to the recovery partition by mistake.
So now...
My phone just keeps booting and booting.
Alcatel Screen appears
The SuperSU installer starts
runs through its steps
Done!
Cleaning Up....
Will reboot in 10 seconds....
And starts all over again.
adb does not find any devices anymore
I am wondering if it possible at all to format the external sd card so that the phone will boot directly from there.
I have one single ray of hope ( maybe ) . The phone will boot into download mode. (Power off, hole power, volume up and volume down to activate)
The challenge I have now is the USB driver that was working now does not recognize the phone.
I have tried fastboot and I have also tried the OnDemand script. No luck.
I read that the download mode is used for flashing firmware and roms (most likely by the manufacturer)
Has anyone been able to install a rom using the download method successfully?
I am on Windows 10 All-in-One PC
Thanks in advance for any assistance you can provide.
N101BL

More Info
No ideas anyone?
Here is some more info. Hopefully it helps.
So this is what my screen looks like when the phone is turned on. I can only turn it off if it is not plugged in to usb or power.
{
"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"
}
This is the Download Mode. (Power off - then hold power button, volume up, and volume down. Let go when splash screen starts)
Download mode makes a connection sound on my PC so I know something is being recognized.
The phone stops bootloop and waits for something?
This is what appears in Devices and Printers Windows
These are the USB Properties for the USB Driver.
I am thinking that maybe there is a secret usb driver that Telus uses or Alcatel uses to push the firmware or rom onto the phone. Not just the default Alcatel usb driver. (not sure)
Even if I could somehow push a ne SuperSu.zip or my original backup files, everything would be good.
Any ideas would be amazing. I know the trials and tribulations of working with a new product. Hopefully you experts can decode this one.
Thank you.
N101BL (Kevin)

CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.

No Recovery Mode
DallasCZ said:
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
Click to expand...
Click to collapse
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)

You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.

what about off warranty repair by alcatel service in your country?

N101BL said:
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
Click to expand...
Click to collapse
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
petrov.0 said:
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
Click to expand...
Click to collapse
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.

famewolf said:
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Probably but the files must be released in the wild first. I do searches in baidu from time time in case that something interesting pops up. I also must to admit that the translation of these sites is awful in most cases

Update
Well I sent my phone back.. Fortunately it was under warranty!
But now another hopefully minor issue with the replacement phone.
Please see this thread and post if you know what I am missing. I really appreciate your time and efforts!
http://forum.xda-developers.com/idol-3/help/valid-backup-file-t3199797
famewolf said:
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse

I Need Help to Recover my Phone Please

Hello,
I'd like to say I was told about this site, and I hope someone can help. I find the forum very difficult to navigate.
I have a moto G 2015 that I tried to root, but I fear that I made some mistake or downloaded a bad rom or something because I can only access the root loader, or w/e it's called. The new rom or recovery image or w/e (yes i'm sorry i don't know all the terms) never loaded, and even the backup (which installed successfully) won't load.
Can I factory reset my phone with the original android rom? I really like this phone and it's just a brick now. I'm using my old phone which i don't like as much. I hope someone can help.

You'll have to flash the stock firmware using fastboot, here is the guide. Refer first 2-3 posts by lost101 for the instructions.
Also, the guide has a link for the firmware index where you can download the latest firmware for your particular model (mine is XT1550, for example).
You should already have ADB and fastboot set-up on your PC as you have tried to root. Assuming that you're using Windows, Extract the firmware into the folder where adb.exe and fastboot.exe are located.
Now, boot the phone into bootloader mode by pressing and holding power+volume down button for about 7-10 seconds. You can release the keys once you see an Android robot lying on its back. The screen should read 'fastboot mode'. Connect the phone to your PC, the screen should now day 'USB connected'. Now open a command prompt from the location where you placed the firmware files. You're now ready to flash the stock firmware.
Follow the guide linked above for the required commands. Make sure to do the recovery flash first, factory reset, then reboot to bootloader again to continue rest of the procedure.
BTW, what was the backup you mentioned that restored successfully? Can you describe it more?
Broadcasted from Zeta Reticuli

Let me provide some images I took with my other phone. It might help.
OK I have osprey xt1540 and i used something called Team Win Recovery Project v2.8.7.0. I can still get into the TWRP thing, and there's a bunch of options i'm sure you're aware of. The backup of my phone that I made doesn't seem to work. It will load say that it loaded properly. Maybe I can provide some photos to show you what I've done.
The backup was simply a backup of my phone before attempting to flash it the first time. It was meant as a way to recover the phone I think..
edit: OK so I'm not allowed to post pictures because I have fewer than 10 posts. That's going to make it harder to get help.
edit 2: BTW In the list for stock firmware I'm not sure which one to take. I found the version of my phone, but it seems newer than any of those listed. 24.71.2 where the newest there is 24.65.33 ?
I found a more recent firmware, but it still doesn't exactly match my phone (I think?) I'll post them
My phone: 24.72.2.osprey_retca.retca.en.ca
Most recent found: MotoG3_XT1540_OSPREY_RETCA_5.1.1_LPI23.72-16.3_cid14_subsidy-DEFAULT_CFC.xml.zip
And I found it from this thread: https://forum.xda-developers.com/showthread.php?t=2537119
Also I wonder if my phone will work if I can just relock the bootloader somehow. I get stuck on that screen that warns about the bootloader unlocked (white screen with motorola warning.) I can get on that screen, the bootloader, and then the team win recovery thing. I hope this helps

First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.

KrisM22 said:
First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.
Click to expand...
Click to collapse
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.

mobile.frank said:
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.
Click to expand...
Click to collapse
I would need to see a copy of your terminal output.

Try what you were doing again in TWRP, this time after the error, use the third button on nav bar (right to the home button, 4 horizontal lines) to switch to terminal output window; then press and hold down power+volume down to take a screenshot and then upload it here, it might help us understand the situation better.
And if you are aiming for a stock firmware install, probably 'XT1540_OSPREY_RETCA_6.0_MPI24.65-33.1-2-2_cid14' is what you want. Got from the firmware index thread here.
BTW, you can try some threads on the off-topic section to increase your post count.
Broadcasted from Zeta Reticuli

KrisM22 said:
I would need to see a copy of your terminal output.
Click to expand...
Click to collapse
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything.) I imagine i have to update the TWRP from this screen, but the instructions in the links you sent me don't correspond with the files that I downloaded. If I type in what I downloaded it doesn't work.
{
"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"
}
This is the program and screen and instructions. The codes there don't work because the filenames are different:
This is an example trying to use the recovery img which tbh I'm not even sure what image that is.
I attempted to root my motorola a long time ago, that's why i can't remember how i managed to do any of it. I think I deleted all the links to the instructions I was using.

mobile.frank said:
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything)
This is the program and screen and instructions. The codes there don't work because the filenames are different:
Click to expand...
Click to collapse
fastboot devices shows the devices that are in fastboot mode (same as bootloader mode in our case) connected to the PC. So, connect the phone via USB and try running that command, it'll show up your device's serial no. and 'fastboot' written on the right side.
Now, rename your recovery image to twrp.img. Or you n modify the command itself. Make sure that the recovery is in the same folder as these 4 files. For example, if your recovery is named twrp-3.1.0.0-osprey.img, then type in-
Code:
fastboot flash recovery twrp-3.1.0.0-osprey.img
after you get a [DONE], scroll down and select recovery in phone.
If you already have a twrp version installed now, then copy the new twrp.img file to your sdcard. In TWRP>Install>install image. Select the file, select recovery in next step and swipe to flash.
Broadcasted from Zeta Reticuli

from the lying down android in the first picture, it shows you have stock recovery.

KrisM22 said:
from the lying down android in the first picture, it shows you have stock recovery.
Click to expand...
Click to collapse
That's the bootloader screen, not recovery.
Sent from my MotoG3 using Tapatalk

OK I managed to update the TWRP and am trying to restore the phone backup from the SD card. I made the backup before making any changes when I tried to root my phone.
I don't know if anything works because every time the phone reboots I get the "Warning bootloader unlocked" screen; so maybe it even worked when i tried to root it, but is just always stuck on this screen. I only get that screen, or the bootloader screen if I go to it.
OK so I tried to follow these directions with the factory image for my phone, and it didn't work. I get a nice motorola boot screen, and then nothing:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#

I strongly suggest you look at this:
https://forum.xda-developers.com/20...gin-how-to-t3599251/post72111431#post72111431
That will also tell you how to get rid of the nasty bootloader screen.
Also make sure you WIPE dalvik/art,data,system,cache before you restore. Anything.