Related
As I understand it, the phone has the bands for at&t, does that mean it will work on at&t?
In stock form, the Verizon M is locked for US bands. You can flash the Australian radio to get it to work on AT&T, but you will only get EDGE speeds at the moment. P3Droid and cellzealot are the ones working on this, but they don't yet know why it only picks up EDGE speeds.
I believe this is what you are looking for. I been trying to figure it out also but for T-Mobile.
From my understanding I have to be on ICS ?
Then root the device with that exploit ?
Fire up RDS and then Fastboot Loader.
Flash ICS if not already on it.
Now i am confused on the part where they say flash the AU Radio bin file with command ?
http://forum.xda-developers.com/showthread.php?t=1984265&highlight=fast
Germanese said:
I believe this is what you are looking for. I been trying to figure it out also but for T-Mobile.
From my understanding I have to be on ICS ?
Then root the device with that exploit ?
Fire up RDS and then Fastboot Loader.
Flash ICS if not already on it.
Now i am confused on the part where they say flash the AU Radio bin file with command ?
http://forum.xda-developers.com/showthread.php?t=1984265&highlight=fast
Click to expand...
Click to collapse
No, you don't need to root it, you don't need to use RDS, you (probably) don't need to have ICS, although I haven't tried with JB yet. You don't even need to unlock the bootloader.
You just need to flash the radio image, the thread you linked has links to the radio image to download, and the commands you need to give from the command line to flash the radio (see post #4) ... I don't know if there are other (graphical) tools other than fastboot to do this, probably, I just don't know them (I'm fairly new too ... does RDS do the same as fastboot?). I got fastboot from the Android SDK.
aslomagic said:
No, you don't need to root it, you don't need to use RDS, you (probably) don't need to have ICS, although I haven't tried with JB yet. You don't even need to unlock the bootloader.
You just need to flash the radio image, the thread you linked has links to the radio image to download, and the commands you need to give from the command line to flash the radio (see post #4) ... I don't know if there are other (graphical) tools other than fastboot to do this, probably, I just don't know them (I'm fairly new too ... does RDS do the same as fastboot?). I got fastboot from the Android SDK.
Click to expand...
Click to collapse
Yeah ... coudln't figure it out. the commands didn't go through.
I guess i am doing something worng with the EXE and the DLLs to make it work.
I just grabbed that BIN file opened the Stock ICS FASTBOOT File 600+Meg one.
Opened it up with WinRar Pro and injected the AU Modem BIN into it and over wrote the Verizon BIN.
AU was 100mb vs Verizon 45mb
After reboot it gave me an amazon error but else everything seems to be working. I don't have Data on my plan so Edge will be just fine =)
First of all I have a 16gb n7 currently on 4.2.1 JOP40D. It's unlock/rooted on STOCK rom.
First off I have tried installing the OTA update and would get an error everytime.
Then I tried installing CWM and manually pushing the update nakasi update and it still threw an error:
Verifying current system..
assert failed: apply_patch_check ("/system/build.prop", 38f7593c2ff2fa85a147 etc...)
E: Error in /sdcard/0/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(status 7)
Installation abborted.
So from googling/searching that I have figured that there is something not "stock" about my build.prop. I had edited it to get rid of the NAV bar but after re-editing it back to stock, it would still throw the same error.
So first I tried reflashing 4.2.1 ... threw the same error
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about? Also when opening it there are just about 2 lines of chinese characters... Soooo this is where I'm stuck... I need to know how to extract a proper build prop from 4.2.1 or I need someone to post a stock 4.2.1 build prop.. thanks..
edit: before people suggest I have tried redownloading both the JOP40D and JPQ39 files
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
The checksum performed requires the file to be exactly identical to the original.
No extra spaces, identical line termination schemes et cetera - identical byte-for-byte. That means including characters you can not see in an editor.
You can certainly copy the original to a folder side-by with your hand-edited version and run any checksum on the both of them to see if you got it right, but it is probably easier to just copy the original into place.
Simply put, the only reason that check continues to fail is because the file you have there is NOT identical to the original.
good luck
canadianrider said:
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
Click to expand...
Click to collapse
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
canadianrider said:
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about?
Click to expand...
Click to collapse
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
bftb0 said:
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
Click to expand...
Click to collapse
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Pirateghost said:
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
Click to expand...
Click to collapse
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Pirateghost said:
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
Click to expand...
Click to collapse
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
canadianrider said:
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
Click to expand...
Click to collapse
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Pirateghost said:
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Click to expand...
Click to collapse
No no I know it does not require you to relock the bootloader.. I just assumed the method used in the one thread I was talking about would relock the bootloader.. I'm just talking out of my ass here though.. I'll start reading on how to use fastboot soon.
If anyone has any good idiot proof guides I'd appreciate it.
follow GOOGLE's directions for setting up fastboot and adb.
it is literally 2 commands
fastboot flash system nameofsystemimgfile.img
fastboot flash boot nameofbootimgfile.img
while the device is in fastboot mode....its not complicated. download the files you need and get started. in the amount of time you have waited on a reply, you could have already had it done. you dont have to learn every command, you just need to 'install' fastboot and adb and put the files in the proper place.
https://developers.google.com/android/nexus/images
http://bit.ly/158k5Wr
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
canadianrider said:
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
Click to expand...
Click to collapse
see? it wasnt really that complicated.
Pirateghost said:
see? it wasnt really that complicated.
Click to expand...
Click to collapse
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
canadianrider said:
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
Click to expand...
Click to collapse
i provided a lmgtfy link, that had many threads listed on setting it up on a mac.
all nexus devices are the same in respect to fastboot/adb
any thread you find for n7, galaxy nexus, nexus4....pretty much universal
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
canadianrider said:
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Click to expand...
Click to collapse
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
gavingt said:
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
Click to expand...
Click to collapse
Pirate posted a link of the full 4.2.2 ROM that can be installed with fastboot.
bftb0 said:
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.29
No pop up on the tablet
Ah nevermind.. I'm just reading on the ADB website that you need version 1.0.31 or higher with 4.2.2 .... thanks for the heads up!
So it has been reported that GE HTC One's are shipping. We would like to get all the paritions dumped so that we can use the images to fully convert our normal Ones into full fledged Google Edition Ones.
Before you do ANYTHING with it (before you root, before you flash a recovery etc...) Follow these directions courtesy of cschmitt Found Here This will ensure we get all the partitions
I have pasted the steps below. This will help the community out greatly!
cschmitt said:
I have a windows command script that uses adb to dump and pull every partition from a One, excluding cache (meaningless) and userdata (to large).
He would need adb and fastboot on his computer, no need for S-off, since we are only reading partitions.
Generally the process would be:
Enable USB Developer options and USB debugging on phone.
Connect phone to usb, install drivers from zip folder if prompted.
Copy SuperSU-v1.41.zip to sd card.
Reboot into bootloader. (Power off, hold power on an vol-down.)
Open command prompt into \htconedump folder.
Unlock bootloader, fastboot oem unlock should do it.
Reboot back into bootloader (via hboot menu.)
From command prompt:
fastboot erase cache
fastboot boot openrecovery-twrp-2.5.0.0-m7.img (Take note we are not flashing recovery, just booting into it so we can root. If you flash the recovery we will not be able to get the stock GE recovery pulled)
Once TWRP boots, flash SuperSU-v1.41.zip via TWRP to root device.
Reboot back into system.
Run pullmmc01-37.cmd command script from a windows command prompt.
Zip up the dump directory containing all of the mmcblk0p??.bin files.
I've packaged everything up into a zip file containing ADB, fastboot, HTC drivers, superuser.zip, TWRP image, and the pullmmc01-37.cmd command script.
htconedump.zip"
Click to expand...
Click to collapse
Also make sure to take note of your CID in the bootloader and also report that in this thread. You can get this by running fastboot getvar all while in the bootloader. The MID and the CID will be listed. Please make note of both.
I would advise anyone doing it that they do it without fully setting up the phone because once you unlock the bootloader it will wipe your data. So boot into android and just skip through the whole set up process because you'll just have to do it again after you unlock the bootloader
EDIT: Got this info from the Dump thread on Android Central. Just need to confirm it's correct with someone who has the device
ro.product.name=m7_google
cid=GOOGL001
mid=PN0712000
cidlist=GOOGL001
Reserving this space for conversion instructions.
http://forum.xda-developers.com/showthread.php?t=2356654 Using dump of released device??
bobsie41 said:
http://forum.xda-developers.com/showthread.php?t=2356654 Using dump of released device??
Click to expand...
Click to collapse
We have the system and the boot.img but for us to do a full conversation we need the bootloader, the recovery etc.. Sure, we can all run the rom now but if we get ALL the partitions dumped we can essentially convert our normal ones into full fledged google editions (I think if we had just the bootloader and the recovery we would be ok)
Have you asked Mike?
we would need the 4.3 system dump
bobsie41 said:
Have you asked Mike?
Click to expand...
Click to collapse
Mike used the same dump everyone has been using. It was only system and boot not the bootloader or recovery. The guy who did the dump flashed a custom recovery before he did the dump so we did not get the stock GE recovery which is needed if we want a full conversion and be able to get OTA's just like the GE One would get.
hello00 said:
we would need the 4.3 system dump
Click to expand...
Click to collapse
Yeah here is to wishing they ship with 4.3 lol
The idea here is not for us to be able to run the rom but to fully do a conversion. As of now we have the 4.2.2 rom and boot image. I have two ones and I want to fully convert one to a GE. I know others are interested in performing a full conversion as well. And if we do the full conversion when the 4.3 OTA drops we would get it as an OTA and not have to wait for other devs to package it all up for everyone
graffixnyc said:
Mike used the same dump everyone has been using. It was only system and boot not the bootloader or recovery. The guy who did the dump flashed a custom recovery before he did the dump so we did not get the stock GE recovery which is needed if we want a full conversion and be able to get OTA's just like the GE One would get.
Click to expand...
Click to collapse
Ok. I assumed that, due to the delay in Mike releasing his GE rom, that he had perhaps acquired his own information.
If anybody lives in the viscinity of Old York City, struggling to dump the required information, I could offer the same service as you have for those near New York City........Highly unlikely I guess.
I am very interested in trying this out.
RaptorMD said:
I am very interested in trying this out.
Click to expand...
Click to collapse
Hey! I remember you! Didn't you use one of my roms at one time(Either on the HTC View or GS3)? If I remember correctly you're also from NY?
This is a great idea. If not for the missing T-Mobile LTE band I would have bought the GE. I hope you get what you need. Would probably cure my Flashaholics disease too, if you're always up to date with the latest and greatest.
Sent from my One using Tapatalk 2
Yea i cant wait for the dump. I bought this phone specifically to make it a GE. Im on AT&T, running an unlocked Tmobile HTC One. The best of both worlds
graffixnyc said:
Hey! I remember you! Didn't you use one of my roms at one time(Either on the HTC View or GS3)? If I remember correctly you're also from NY?
Click to expand...
Click to collapse
I did on the HTC View and very likely the GS3 as well and I am from NY Its nice to run into you again. The HTC One is finally a phone worth KEEPING, finally. Now that I am off VZW and enjoying GSM and a Developer Edition H1 life is far more interesting.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
serialtoon said:
Yea i cant wait for the dump. I bought this phone specifically to make it a GE. Im on AT&T, running an unlocked Tmobile HTC One. The best of both worlds
Click to expand...
Click to collapse
I look forward to what the devs cook up in the ROM kitchen. I am very keen to try out the GE ROM's but I would also like HTC to just offer up the option for DE to get it now and to allow anyone to flash it if they want.
I am also interested in converting my s4 gt-9505 into a full google edition s4 with OTA.
slikr said:
I am also interested in converting my s4 gt-9505 into a full google edition s4 with OTA.
Click to expand...
Click to collapse
Wrong forum?
surely will try this out
Any news I'm anticipating fully converting to GE!!
Hopefully in the next few hours it will arrive! Cant wait to receive it
Aerys said:
Hopefully in the next few hours it will arrive! Cant wait to receive it
Click to expand...
Click to collapse
Are you going to try to dump the partitions? If so, I would advise anyone doing it that they do it without fully setting up the phone because once you unlock the bootloader it will wipe your data. So boot into android and just skip through the whole set up process because you'll just have to do it again after you unlock the bootloader
Hi guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
AS my comes from Brazil, i saw that fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz is avaliable. But my question is: how can i flash this kinda if files since they arent RSD lite type and are fastboot ones? Do i need unlocked bootloader?
If someone can help me, i appreciate a lot!
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
waiflih said:
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
Click to expand...
Click to collapse
Thanks my friend! But do uo have the steps for this? Cause i couldnt found any specific to Moto X.
As i unzip the tar file, i have these files as attached.
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
waiflih said:
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
Click to expand...
Click to collapse
Thanks again!
Any ideas?
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
xitake said:
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
Click to expand...
Click to collapse
No,but as the programa asks, i don have a JTAG flex?
xpc21 said:
No,but as the programa asks, i don have a JTAG flex?
Click to expand...
Click to collapse
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
xitake said:
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
Click to expand...
Click to collapse
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Flahing stock SBF
xpc21 said:
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Click to expand...
Click to collapse
Try this maybe it'll work
1. Connect your Moto x, make sure developer options is enabled and tick usb debugging.
2. open command window on the folder including the new extracted firmware.
3. Type adb devices to confirm that Moto X is detected by your computer.
4. Type adb reboot bootloader, Moto X will reboot in fastboot mode.
5. Run the batch file flasfall.
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
kkhadr said:
Try this maybe it'll work
...
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
Click to expand...
Click to collapse
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Anyone else?
[email protected]
xitake said:
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Click to expand...
Click to collapse
If this version includes the camera patch then it won't be rooted, but I flashed TMO 4.3 the test build it's working great but off course I lost root, and I'm sure in a few days it will be rooted again, so nothing to fear.
this is the OPs 3rd post about the same topic. One under q&a, one under dev that got moved to q&a, and now one under moto x general. Someone needs to teach him a lesson because he has gotten responses on all three threads. Really frustrating. Won't be getting anymore help from me...
Looks like fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz have the same camera app as in ATT, TMO, Sprint after OTA (with improved camera). Camera app in new Brazilian firmware have version 3.0.211 - the same as in TMO rom with OTA installed.
Kind of straight forward
You just need to unpack the tgz container. Inside the folder there is a bunch of files.
I'm my case since I'm using OSX I just ran flashall.sh and done. There is a flashall.bat that I believe is designed to work with windows.
Put your phone in bootloader mode, connect the cable, go to folder the files lies and run the command. In about 5 minutes it is done. :good:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
rodrigorox said:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
Click to expand...
Click to collapse
rodrigorox,
I have called motorola on friday and it seems we will be getting the update in the next week or so...
I'd hold on on flashing it if all you look for is the OTA that US got.
Hey guys, I'm looking into getting an axon7mini. Before I do, I want to verify that I can get into EDL mode and talk to the device. Is anyone willing to take one of the axon7 tools and see if it will talk to the axon7mini in EDL mode? You don't need to write anything, just read. For example, do a backup of the recovery image using one of the tools.
If that works, I'll snag one off ebay and get Lineage up and running in short order.
If you can provide some instructions, I'm happy to test this for you. Running the latest lollipop rom atm. Can update to nougat if required.
Thanks
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
dpgc213 said:
If you can provide some instructions, I'm happy to test this for you. Running the latest lollipop rom atm. Can update to nougat if required.
Thanks
Click to expand...
Click to collapse
tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
Cool, will give it a go tomorrow.
tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
Hi,
I can get it to communicate however when attempting "axon7tool -r gpt boot recovery" I'm getting an error which cause the tool to crash. it reads failed to read command.
Thanks
dpgc213 said:
Hi,
I can get it to communicate however when attempting "axon7tool -r gpt boot recovery" I'm getting an error which cause the tool to crash. it reads failed to read command.
Thanks
Click to expand...
Click to collapse
Thanks. That probably means it's incompatible. :/
tdm said:
Thanks. That probably means it's incompatible. :/
Click to expand...
Click to collapse
Yeah, this means incompatible, we need the programmer, firehose file 8952. But is only in a old firmware (NOT SD card upgrade). Anyone have this?
tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
tdm, you don't live far from me.
i'll try these out as well, but you have a local beta tester
Edit:
Same error even running in compatibility mode Windows 8
Code:
E:\Axon>axon7tool -r recovery
Connecting to device...
Sending programmer...
S: target error 0x00000014
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Code:
E:\Axon\axon7root>axon7root -d
Copyright @tenfar [email protected]
Version 1.10
Failed to say hello to device
device no response
!!!!!!!! Horse is dead!!!!!!!!!
rombdeta said:
Yeah, this means incompatible, we need the programmer, firehose file 8952. But is only in a old firmware (NOT SD card upgrade). Anyone have this?
Click to expand...
Click to collapse
I can probably find a 8952 firehose, but it will be from another manufacturer. So it won't be signed with the proper key. Which means it almost surely won't work.
Sent from my Find 5 using Tapatalk
Been trying to snag an axon7mini on ebay for about $120 but they keep going for $140-$150. @fallen00sniper if you want to trade me for another phone for a week, I can try my hand at unlock.
Well i have the programmer finally!
rombdeta said:
Well i have the programmer finally!
Click to expand...
Click to collapse
Which programmer? The official axon7mini one? Or for another device?
tdm said:
Which programmer? The official axon7mini one? Or for another device?
Click to expand...
Click to collapse
Axon 7 mini, 8952, but i will work with my device, i need info how to edit the bootloader bit
Currently, I added a file to remove patron / code, since some recovery does not bring the option of "wipe data", but I repeat is only a test, I do not take responsibility for damages, this is the door to unlock the boot and customs roms , recoverys and so on.
https://mega.nz/#!k1M2gKya!tjtjCD4Jp...xvYzx-wjeTrYvE
tdm said:
Been trying to snag an axon7mini on ebay for about $120 but they keep going for $140-$150. @fallen00sniper if you want to trade me for another phone for a week, I can try my hand at unlock.
Click to expand...
Click to collapse
We would have to speak about this further.
I'm on MetroPCS and they charge $15 Everytime I move the Sim to a different device, maybe on the website I can do it for free, not sure.
How do they do that? You should just be able to swap your sim over shouldn't you?
Hdale85 said:
How do they do that? You should just be able to swap your sim over shouldn't you?
Click to expand...
Click to collapse
I can swap the Sim over, but the IMEI change is where they get me, but it looks like I can do it free on the website, since I cannot go any further without a different IMEI I don't know if they charge and I am currently out of work :/
However if @tdm pm me we can talk about this trading for a week and try to get this ball rolling.
rombdeta said:
Axon 7 mini, 8952, but i will work with my device, i need info how to edit the bootloader bit
Click to expand...
Click to collapse
Nice! I'd love a copy of that. I can most likely make unlock tools with it.
Next question... does this device have a fbop partition?
tdm said:
Nice! I'd love a copy of that. I can most likely make unlock tools with it.
Next question... does this device have a fbop partition?
Click to expand...
Click to collapse
I think so, the link is in another post.
rombdeta said:
I think so, the link is in another post.
Click to expand...
Click to collapse
The link is bad, it says the provided key is invalid.