I recently bricked my Atrix 2, and since I don't have easy access to a Windows machine, I attempted to flash it back to stock using fastboot from the android dev tools. I noticed that the XML file in the FXZ looked like a set of fastboot commands, so that's what I tried to do. However, no matter which zip I started from, it always failed to flash system.img, saying that verification failed. After giving up on that approach, I used a friend's windows machine to flash the exact same zip using RSDLite, and it succeeded just fine. This leads me to conclude that RSDLite must be doing something special when flashing the system.img. Does anyone know what it is, and is there a way to do the same thing using the standard Android development tools (fastboot, etc)?
Thanks!
bemjb said:
I recently bricked my Atrix 2, and since I don't have easy access to a Windows machine, I attempted to flash it back to stock using fastboot from the android dev tools. I noticed that the XML file in the FXZ looked like a set of fastboot commands, so that's what I tried to do. However, no matter which zip I started from, it always failed to flash system.img, saying that verification failed. After giving up on that approach, I used a friend's windows machine to flash the exact same zip using RSDLite, and it succeeded just fine. This leads me to conclude that RSDLite must be doing something special when flashing the system.img. Does anyone know what it is, and is there a way to do the same thing using the standard Android development tools (fastboot, etc)?
Thanks!
Click to expand...
Click to collapse
Fastboot is basically doing what RSD Lite does manually. If you keep on getting a flash system.img error mkake sure that you have the proper drivers. You can download Android-SDK for your platform and then open the manager. There should be an option to install a drivers package.
I am pretty sure RSD Lite does nothing special. I have flashed just the system.img multiple times to quickly get my phone back up and running.
.
farshad525hou said:
Fastboot is basically doing what RSD Lite does manually. If you keep on getting a flash system.img error mkake sure that you have the proper drivers. You can download Android-SDK for your platform and then open the manager. There should be an option to install a drivers package.
I am pretty sure RSD Lite does nothing special. I have flashed just the system.img multiple times to quickly get my phone back up and running.
.
Click to expand...
Click to collapse
Thanks, but there are no USB drivers available for Mac OS X: the Android SDK says that they are unavailable for this platform. Maybe if I get the chance, I'll see if doing the flash with fastboot on Windows gives different results.
Are you using moto-fastboot?
Oh there's a Mac version here (from here)
There's a size limit on flash operations with normal fastboot.
moofree said:
Are you using moto-fastboot?
Oh there's a Mac version here (from here)
There's a size limit on flash operations with normal fastboot.
Click to expand...
Click to collapse
I've been using normal fastboot, I didn't realize there was a difference there. Thanks a ton, I'm sure that will solve my issue!
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
jimbridgman said:
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
do you really have to erase before flashing? I always try to avoid formatting system, but I have not done this manually, so you may have to.
lkrasner said:
do you really have to erase before flashing? I always try to avoid formatting system, but I have not done this manually, so you may have to.
Click to expand...
Click to collapse
Yes if you don't you will most likely get an error when you try to flash system.img, over a different system version.
jimbridgman said:
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Sorry I missed your other explanations. I did see a lot of posts with random fastboot commands, but pretty much none with any sort of explanation or rationale. Most of them seemed to be on the order of "Use these commands because I said so" or "I used these and they seem to work, I don't know why".
Do you have a writeup where you explain why should I flash with fastboot in a different order than is given in the fxz? And can you explain why you are skipping flashing most of the partitions? None of the instructions for using RSD Lite suggested removing nearly that many of the entries in the xml file, so I would like to know why I wouldn't want to flash the same things that RSD Lite would be flashing.
If you do have a canonical post explaining what needs to be done and why, I can ask the maintainer of the newbie information post to add a link to that post, so that it is easy to find and hopefully make it so that you don't have to post about it again. If that post doesn't exist, if you would like to give me enough information to write it, I am more than happy to write it up (crediting you for the info, of course), and then see about getting it added to the newbie post.
bemjb said:
Sorry I missed your other explanations. I did see a lot of posts with random fastboot commands, but pretty much none with any sort of explanation or rationale. Most of them seemed to be on the order of "Use these commands because I said so" or "I used these and they seem to work, I don't know why".
Do you have a writeup where you explain why should I flash with fastboot in a different order than is given in the fxz? And can you explain why you are skipping flashing most of the partitions? None of the instructions for using RSD Lite suggested removing nearly that many of the entries in the xml file, so I would like to know why I wouldn't want to flash the same things that RSD Lite would be flashing.
If you do have a canonical post explaining what needs to be done and why, I can ask the maintainer of the newbie information post to add a link to that post, so that it is easy to find and hopefully make it so that you don't have to post about it again. If that post doesn't exist, if you would like to give me enough information to write it, I am more than happy to write it up (crediting you for the info, of course), and then see about getting it added to the newbie post.
Click to expand...
Click to collapse
The reason is there are other files, and some are binary files that run commands and make changes to the bootloader, and other things, you do not need any of that to have a working phone. Some of them also open the bootloader to allow flashing, which is not needed if you erase the boot partition first. Any of those files like mbmloader, and anything with .bin after it will not work correctly unless you use RSDlite, it sends the signatures and such to the files that require it.
For getting your phone back up in a quick and dirty fashion we don't care about the signatures, we are assuming you got the fxz from a known source, by doing it this way.
You should do other research besides this site, pull apart a few roms, the fxz, and figure out how they work. Do some android research as to the boot process, etc. That how this kind of information is learned. The why in this case is less important. I would have to explain android and linux and how they boot as well in more detail here, but those are best left to the google and linux explanation sites.
This is not a process for a beginner, that is why it is not in the beginner thread. It has the possibility of hard bricking your phone if a mistype happens.
I am going to be 100% honest here, if you don't know any of the information I am referring to in this post, just use RSDlite, it has checks and safeguards that this process does not.
If you really want to learn about this, and not just asking questions because you don't understand, then jump in with us devs and start to learn, pull apart some ROMs flash a few ROMs, build a few ROMs, those things will teach you more than you will ever need to know about what files are and are not needed for a working phone. Also google is a good resource.
Also your boot.img and your recovery.img could be left out, since they are never touched by you or a ROM flash. I leave them in for a slight safeguard that your phone will actually be wiped clean.
P.S. I am a linux and OS X user myself, hence why I learned all of this a long time ago... I have been using and working on android since the G1 firat came out.
I also use bootcamp with win7 just to use RSDlite, when the need arises... that is not often, if you follow my process. It skips all the checking, processing that RSDlite does with using fastboot.
jimbridgman said:
The reason is there are other files, and some are binary files that run commands and make changes to the bootloader, and other things, you do not need any of that to have a working phone. Some of them also open the bootloader to allow flashing, which is not needed if you erase the boot partition first. Any of those files like mbmloader, and anything with .bin after it will not work correctly unless you use RSDlite, it sends the signatures and such to the files that require it.
For getting your phone back up in a quick and dirty fashion we don't care about the signatures, we are assuming you got the fxz from a known source, by doing it this way.
You should do other research besides this site, pull apart a few roms, the fxz, and figure out how they work. Do some android research as to the boot process, etc. That how this kind of information is learned. The why in this case is less important. I would have to explain android and linux and how they boot as well in more detail here, but those are best left to the google and linux explanation sites.
This is not a process for a beginner, that is why it is not in the beginner thread. It has the possibility of hard bricking your phone if a mistype happens.
I am going to be 100% honest here, if you don't know any of the information I am referring to in this post, just use RSDlite, it has checks and safeguards that this process does not.
If you really want to learn about this, and not just asking questions because you don't understand, then jump in with us devs and start to learn, pull apart some ROMs flash a few ROMs, build a few ROMs, those things will teach you more than you will ever need to know about what files are and are not needed for a working phone. Also google is a good resource.
Also your boot.img and your recovery.img could be left out, since they are never touched by you or a ROM flash. I leave them in for a slight safeguard that your phone will actually be wiped clean.
P.S. I am a linux and OS X user myself, hence why I learned all of this a long time ago... I have been using and working on android since the G1 firat came out.
I also use bootcamp with win7 just to use RSDlite, when the need arises... that is not often, if you follow my process. It skips all the checking, processing that RSDlite does with using fastboot.
Click to expand...
Click to collapse
Thanks for the rather comprehensive reply. Sadly, I do not have the time or inclination to build ROMs, in fact, I may not have dug into this at all if I had a Windows license, but I do not. So it is true that I didn't know all of the information that you mentioned in the post, but I had guessed a lot of it given the format of the xml file in the fxz and the names of the partitions. I just like to verify that my guesses are not incorrect, thus the questions. I do have plans to spend some time reading Google's official Android documentation, I just hadn't gotten there yet.
Anyways, while I am not interested in building ROMs, given the format of the xml file, it looks like it would be a fairly easy task to build a Java application that would read the XML file, check the MD5 sums, and then do the flashing just like RSD Lite. If I was to do something to contribute to the development effort, I'd probably start there. Don't know if I'll have time, but that's much more of a problem to me than a custom ROM. You mention signature checking: does RSD Lite actually check cryptographic signatures on the images themselves, or is it only checking the MD5s? (Feel free to ignore that question if you think I should spend some time Googling, if you don't answer, I'll get around to looking it up eventually)
P.S. I am an experienced Linux and OS X user. I only happen to be new to the Android world. (I was using webOS before this)
bemjb said:
Thanks for the rather comprehensive reply. Sadly, I do not have the time or inclination to build ROMs, in fact, I may not have dug into this at all if I had a Windows license, but I do not. So it is true that I didn't know all of the information that you mentioned in the post, but I had guessed a lot of it given the format of the xml file in the fxz and the names of the partitions. I just like to verify that my guesses are not incorrect, thus the questions. I do have plans to spend some time reading Google's official Android documentation, I just hadn't gotten there yet.
Anyways, while I am not interested in building ROMs, given the format of the xml file, it looks like it would be a fairly easy task to build a Java application that would read the XML file, check the MD5 sums, and then do the flashing just like RSD Lite. If I was to do something to contribute to the development effort, I'd probably start there. Don't know if I'll have time, but that's much more of a problem to me than a custom ROM. You mention signature checking: does RSD Lite actually check cryptographic signatures on the images themselves, or is it only checking the MD5s? (Feel free to ignore that question if you think I should spend some time Googling, if you don't answer, I'll get around to looking it up eventually)
P.S. I am an experienced Linux and OS X user. I only happen to be new to the Android world. (I was using webOS before this)
Click to expand...
Click to collapse
No worries.... I am and have been a unix linux architect for 20 years (yes I got a job as a sysadmin at 17), been using macs since the 80s, I don't own a machine with a fulltime windows install. I only recently installed win 7 on my bootcamp partition on my macbook just for rdslite, only used it twice....
I have a shell script that will flash the phone using the commands I posted, if you would like I can upload it and post a link tomorrow. My shell script works on both os x and linux.
If you you try to do EXACTLY what rsdlite does line by line it will FAIL, even with a java app. The bin files and the mbm files can only be utilized with RSDlite. RSDlite has SEVERAL checks that only it can do after each step.... If you want to restore the fxz using the mac or linux the shell script is the easiest, no real need for all the fluff, of rsdlite or an app. I have done it about 20 times now without issue, so have others on here.
Again, just let me know if you want my script and I will post it here.
And no it does not check the cryptographic signature of the bootloader, but the mbm program that rdslite runs, does check the signature of the boot image and the bootloader.
I was not implying that you actually jump into rom dev work.... just that, by doing some pulling apart and attempting it will teach you more than reading the android docs.
If you are a linux guy then hopefully you know what sec linux is, and how it uses signatures with the bootloader. That is similar to what motorola has done with their bootloader on their android phones.
Jim
Sent from my MB865 using xda premium
jimbridgman said:
No worries.... I am and have been a unix linux architect for 20 years (yes I got a job as a sysadmin at 17), been using macs since the 80s, I don't own a machine with a fulltime windows install. I only recently installed win 7 on my bootcamp partition on my macbook just for rdslite, only used it twice....
I have a shell script that will flash the phone using the commands I posted, if you would like I can upload it and post a link tomorrow. My shell script works on both os x and linux.
If you you try to do EXACTLY what rsdlite does line by line it will FAIL, even with a java app. The bin files and the mbm files can only be utilized with RSDlite. RSDlite has SEVERAL checks that only it can do after each step.... If you want to restore the fxz using the mac or linux the shell script is the easiest, no real need for all the fluff, of rsdlite or an app. I have done it about 20 times now without issue, so have others on here.
Again, just let me know if you want my script and I will post it here.
And no it does not check the cryptographic signature of the bootloader, but the mbm program that rdslite runs, does check the signature of the boot image and the bootloader.
I was not implying that you actually jump into rom dev work.... just that, by doing some pulling apart and attempting it will teach you more than reading the android docs.
If you are a linux guy then hopefully you know what sec linux is, and how it uses signatures with the bootloader. That is similar to what motorola has done with their bootloader on their android phones.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You do have a couple of years on me on Linux use, and definitely lots more years of Mac use, I didn't use Macs until OS X. But I think we've established geek cred quite effectively at this point. ;-)
Thanks for offering the script, but if it literally just runs the commands that you gave earlier, it would be simple for me to just toss one together myself. (Now, if you want to elaborate on the secret sauce in RSDLite, I'd be all ears.
I do know what SELinux is. I haven't looked into the specifics of how they use signatures with the bootloader, but I have a pretty good idea of ways that it could be implemented. It does make a lot of sense that Moto would do something similar to SELinux. Actually, I'm a little bit surprised that they're doing something similar and not just doing the same thing, but perhaps the bootloaders are different enough that they needed to roll their own signing. (Or they just did what a lot of people do and fell into NIH syndrome.)
Thanks,
Bem
jimbridgman said:
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Hm. My bootloader and I are not on very good terms atm :\
-It tells me "command restricted" when erasing system, recovery, or boot with fastboot. RSD Lite just says "FAIL."
-Also, it tells me "preflash validation failure" when flashing boot or recovery. RSD Lite again just says "FAIL"
-It also gives me the "preflash validation failure" when flashing system with fastboot. Moto-fastboot and RSD Lite both work. Maybe fastboot would work if we could erase system?
-Finally, we don't have a userdata.img
cogeary said:
Hm. My bootloader and I are not on very good terms atm :\
-It tells me "command restricted" when erasing system, recovery, or boot with fastboot. RSD Lite just says "FAIL."
-Also, it tells me "preflash validation failure" when flashing boot or recovery. RSD Lite again just says "FAIL"
-It also gives me the "preflash validation failure" when flashing system with fastboot. Moto-fastboot and RSD Lite both work. Maybe fastboot would work if we could erase system?
-Finally, we don't have a userdata.img
Click to expand...
Click to collapse
In the first line the fastboot command I referenced and that Farshad mentioned and linked to is the moto-fastboot command. You are supposed to rename the binary to fastboot, there was a readme at one time that explained that and was included with the download of moto-fastboot.
Also, yes we don't have a Userdata.img, but I pulled this from my own personal script, that I have been using since the G1 days, that was my first android phone. My script is not customized for just our phone, so the userdata.img line will fail, but since we don't need it, it is no big deal.
Jim
jimbridgman said:
In the first line the fastboot command I referenced and that Farshad mentioned and linked to is the moto-fastboot command. You are supposed to rename the binary to fastboot, there was a readme at one time that explained that and was included with the download of moto-fastboot.
Also, yes we don't have a Userdata.img, but I pulled this from my own personal script, that I have been using since the G1 days, that was my first android phone. My script is not customized for just our phone, so the userdata.img line will fail, but since we don't need it, it is no big deal.
Jim
Click to expand...
Click to collapse
Oh I see now . I typically use moto-fastboot but I never renamed it. Thanks for the clarification.
cogeary said:
Oh I see now . I typically use moto-fastboot but I never renamed it. Thanks for the clarification.
Click to expand...
Click to collapse
Yeah the reason to rename the binary/exe, was for compatibility with other scripts and programs in old days, when there was no odin or RSDlite, etc. I still do it, so that if someone does come up with some bad-assed way to do something via a script or other means for another phone, then I don't have to edit their script to reference the "moto-fastboot" binary/exe. I just rename the fastboot to fastboot-orig, or fastboot-google. If I ever change phones, and I will, I can rename the binary/exe again real easy.
Just one of those things I have learned over the years with both android and linux and well even in the old DOS and windows NT 3.51 and 4.0 command line days.
I've looked all over, but cannot find anything on the problem I am having.
I go through the steps to load the current factory image onto my nexus s 4g through terminal on my mac, but for some reason it doesn't load everything. Here's what it says in terminal about the items that can't load:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
And here's what my folder looks like where I'm loading everything from:
I guess I can't post a picture from an outside source, so I'll just type in what my folder looks like:
boot.img
bootloader-crespo4g-d720spric1.img
flash-all.bat
flash-all.sh
flash-base.sh
image-sojus-jro03r
image-sojus-jro03r.zip
radio-crespo4g-d720sprilf2.img
there are files in the unzipped folder (image-sojus-jro03r) named:
android-info.txt
recovery.img
system.img
userdata.img
These seem to be some of the files that are missing, but even when i drag them over to the main folder, they still don't load. maybe something to do with the fact that they are .sig's?
I drag the flash-all.sh file into terminal and it loads and writes everything except for these .sig's, which I truthfully don't know what they are. Now I can't get into the correct recovery mode, it just shows some weird blue-lettered options that are different then the normal recovery options. That is why I think the fact that these .sig files are not loading is the problem.
I also booted up the new operating system and signed on, but for some reason none of my apps can download.
Sorry for my noobness, but I'm sure I'm missing one easy step that will fix my problems.
Does anyone know what I'm going through?
Any help is much appreciated.
Alright. I've searched the web and found a few different things. It seems that it's common for those .sig files to not load. Also, i loaded the factory image again and was able to download my apps.
I also now foolishly realize that to get a good version of recovery, I need to root my phone. I'm in terminal now, and for some reason adb is not showing my phone in adb devices. This wasn't a problem when I loaded the factory image, but now it's a problem when I'm trying to do this: http://forum.xda-developers.com/showthread.php?t=1129759
step 5 is a problem, but hey, I can turn off the phone and go into fastboot mode myself. I guess step 7 is the next problem I'm dealing with. Here's what I get in terminal when I do step 7 manually (I put a *#* where my name is just so everyone knows):
MacBook:~ *#*$ /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img
-bash: /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img: Permission denied
Does anyone know what I'm dealing with this time around?
You probably need to enable adb in Settings --> Developer Options. If it's an issue with adb while in recovery, i'm pretty sure the stock recovery (which will be overwritten on every boot from a stock ROM) doesn't allow it. What you need to do is flash a new recovery in fastboot (not in recovery).
Commands (while in fastboot mode):
/path/to/fastboot devices <-- this will tell you if your phone is connected properly
/path/to/fastboot flash recovery /path/to/recovery.img <-- this will flash the new recovery
You'll need to type in the path to fastboot unless you have it in somewhere like /bin or a more convenient environmentally recognised location. The command you typed there is the same as trying to open the .img file as a script, you want to tell fastboot to flash the file to the phone and not open it with the computer.
Edit: Also, once you root, you probably want to delete /system/etc/install-recovery.sh. That file replaces any custom recovery with stock each time you boot.
Thanks Harbb.
That's what I ended up doing, using fastboot. it worked perfectly. I did try to find the /system/etc/install-recovery.sh file in root explorer, but could not find it. don't know where it is.
Everything is rooted and restored on my custom rom to where I was previously using titanium backup.
Here's the tutorial I was using: http://forum.xda-developers.com/showthread.php?t=1129759
with this video being a walkthrough of the previous tutorial: http://www.youtube.com/watch?v=sP9ZDWmbLVM
I was actually using the recovery img in the android folder that I downloaded from the tutorial, and not the one he told me to download, which was my problem in the end. Here's the link to the download page where I should have downloaded it from: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+4.0.0.2
Thanks again Harbb, much appreciated.
No worries buddy, glad you got it sorted.
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
p011i3 said:
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
Click to expand...
Click to collapse
You mention cwm.
Don't you have a backup?
Try google translating this thread: http://www.phonandroid.com/forum/carliv-recovery-cwm-6-0-4-4-pop-c5-et-x-pop-t81752.html
Lgrootnoob;50489116]You mention cwm.
Don't you have a backup?
Try google translating this thread: *link removed due restrictions*
Click to expand...
Click to collapse
I thank you for your kind answer.
No, I do not have a backup prior to my problem.
I have one now though, before things get worse.
I actually made some progress - I managed to correctly install and boot CWM.
I already stumbled upon and downloaded the files mentioned in your link.
The teXt translates as:
-put mobileuncle tools and recovery on your SD
mobileuncle-install and granted him the rights superSU
-click recovery update
-then recovery.img
clicked OK
-then it will ask to restart a recovery click OK
I downloaded the file called ' recovery.img' but I am unsure how to transfer it to my device and implement it.
Also, how do I install and run mobileuncle without being able to boot?
Regards,
EDIT:
Code:
C:\Users\Maya\Desktop>fastboot flash recovery recovery.img
sending 'recovery' (5522 KB)...
OKAY [ 0.217s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.242s
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
DeathNotice said:
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
Click to expand...
Click to collapse
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Lgrootnoob said:
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Search it on www.SamMobile.com......U may get ur stock rom and firmware on it
Lgrootnoob said:
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
DeathNotice said:
Search it on SamMobile.com......U may get ur stock rom and firmware on it
Click to expand...
Click to collapse
I searched for ' 5036x' : " No entries found."
p011i3 said:
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
I searched for ' 5036x' : " No entries found."
Click to expand...
Click to collapse
I did look at it and it is the part of the source code for the kernel and that's it
Bat cave One
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
The kernel should be good enough though. (With modules)
---------- Post added at 10:41 AM ---------- Previous post was at 10:36 AM ----------
@p011i3 Hey, what version of android do you have.
YOu might be able to make a flashable zip if you have a working system img.
Or we could make a false cwm backup and just restore system only from that.
I managed to fully recover my Alcatel One Touch POP C5 5036X without having a backup for my own. I did this by formatting the entire device using Flash Tool and downloading the files from the French Website discussed earlier in this thread.
I'll post a 5036X recovery topic including all files later this weekend.
Again, I thank everyone for their kind help.
hello all,
just intalled the latest update 10.0.0 (QQ3A.200605.002, Jun 2020) with my usual process and that goes fine.
trying to get root again, extracted boot.img, transferred to phone, patched with magisk manager 7.1.2 in beta mode, transferred back to pc, fastboot flash boot magisk_patched.img (success)
when phone reboots, i land on a screen that says system corrupt options are:
try again
factory wipe
try again gives same result
need to back up some data so flashed back stock boot image from 10.0.0 (QQ3A.200605.002, Jun 2020) and phone boots fine.
tried whole process again (i do this once a month and i am familiar with it)
double checked i'd uninstalled magisk before starting
reinstalled magisk manager and set to beta channel
re-downloaded 10.0.0 (QQ3A.200605.002, Jun 2020) factory image, verified sha
flash-all.bat (success)
repatched fresh copy of boot.img to magisk_patched.img
fastboot flash boot magisk_patched.img (success)
same error, system data corrupt try again/factory wipe
anyone else? im wondering if something has changed in the 10.0.0 (QQ3A.200605.002, Jun 2020) boot.img that prevents rooting by this method?
Solved
solved.
downloaded platform-tools_r30.0.1
a bit daft of me missing that but hey-ho
Some further Info
Just in case this solves someone having to do a lot of work.
Been re-setting-up my phone today after a full clean install of factory image without removing - w from flash-all.bat. Didn't restore my apps, started right from the beginning.
Turns out the culprit is a clock mod from another poster on here I was using to move my clock back to the right side. I'm not knocking their work, I've used it since I got my pixel; simply pointing out that the June factory image doesn't like it the op who made it does say to remove it before updating and I didn't so that's my bad. I re-added it today (spent aaaaall day rebuilding phone from scratch) and boom! Same issue.
Luckily, this time I was able to avoid having to reflash by using:
adb wait-for-device shell magisk --remove-modules
And rebooting (took a few goes, I think I was holding vol- when it did boot)
Again, I like and use the mod but if you use it with the June update, it will deffo bork.
Lost a day but learned some stuff so fair trade
I just did this last night.
Okay for starters I'm going to explain my system. I'm running a dual boot laptop all linux. Debian on one drive Ubuntu on another. Over the course of downgrading, rooting, and updating I came across a few problems. The failures during flashing themselves were in my case due to the fact that the process simple will not complete if your using USB-C - USB-C that is the factory charging cable. As soon as I got out a USB-A - USB-C my flashing worked. Second I edited my flash-all script. This is going to be the same thing whether your using windows (flash-all.bat) or linux (flash-all.sh). So you could copy and paste and give my flash-all script a try should you like. In short I simply added
Code:
fastboot set_active a
at the beginning and before the pixel would try to move into fastbootd. Also a simple reboot at the end.
For the stuff, you need to double-check. Get the latest ADB/FASTBOOT drivers, the flash-all scripts can be temperamental unless you edit out the version check which I did. So keep in mind if you don't update your fastboot/adb drivers and you copy my script you could be using outdated adb and the part of the script that checks is simply gone. You'll want to downgrade to Android 9 (you can see the exact firmware I used in the script). Once you have a solid OS installed. Take the boot.img from that firmware and do exactly like you did before. (patch with magisk move, flash, move, reboot ect.) When attempting to patch the boot.img on Android 10 my touch screen fails, and that can be bad news if you don't know your way around an adb shell. Once you got root and magisk confirming installed your there.
Having just finished the process a few hours ago this is all very fresh and feel free to contact me i'd be happy to work it out with you. Also you should know that in my sargo-1 flashing folder I've downloaded and decompressed the Driver Binaries from Google. These are essentially your .img files that the firmware may be missing. Also I unzipped the "image-sargo-<version>.zip" which contains the rest of the .img files.
My Flashall Script
Code:
./fastboot set_active a
./fastboot flash bootloader ~/sargo-1/bootloader-sargo-b4s4-0.1-5653622.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio ~/sargo-1/radio-sargo-g670-00011-190411-b-5457439.img
./fastboot reboot-fastboot
sleep 5
./fastboot set_active a
./fastboot -w update ~/sargo-1/image-sargo-pq3b.190801.002.zip
./fastboot reboot
Phone Info:
T-Mobile Carrier
SARGO
System Info:
Dell G5 15 Gaming
Intel I7-8750H 6 Core
Nvidia GTX 1060 6GB
16GB Ram
Samsung 860Pro SSD 1TB (Debian Linux)
Samsung 860Pro M.2 SSD 500GB (Ubuntu Linux)
Intel AX-200 Ethernet
EDIT: YES I ALSO INSTALLED THE PLATFORM-TOOLS AND USED ADB/FASTBOOT OUT OF THAT, TOOK CARE OF THE COMPAT. PROBLEMS ON THAT END. BUT FOR ME IT WAS THE DUAL USB-C CORD, I COULDN'T GET PASSED FLASHING VENDOR_A 2/2.
Edit: Nvm, problem solved.