Related
hmm I've been searching around a bit bit I couldn't find anything about fastboot for galaxy S (epic 4G).
Please let me know if its out there
Thanks
You mean the thing HTC has in their new Sense builds?
Frankly I don't understand if its only for HTC or a generic tool
but basically I wanted to use
$ fastboot flash boot boot.img
$ fastboot flash system system.img
Click to expand...
Click to collapse
fastboot commands which seems to be available for HTC devices.
My concern is if we have something similar for Galaxy S devices and specifically epic 4g
Thanks
Fastboot is an executable in your android tools platform whatever folder...it should be in same folder as adb. You push .img files from your computer to the phone by fastboot.
Fastboot is the same throughout android regardless of phone (for most part I reckon
Its the best and cleanest way to erase and flash your partitions.
Look in the stickies.
Yes I've known about fastboot terminal utility
However I read people referring to fastboot boot loader separately than recovery mode (CWM3) in phone itself.
I didn't try just going with it, as I wanted to confirm if I'm thinking something wrong here
Thanks
you are on the right track.
To make things worse -- fastboot is also a feature in Sense development settings -- it literally means "fast-boot" as in it boots faster than normal. People get confused over that as well.
everything go ok?
So it is safe to assume that Galaxy S doesn't have anything similar to fastboot?
I don't think so.
Sent From My Evo Killer!
Sorry I'm bit confused now
Can you please elaborate a bit more or even just a link with explanation would be good
If your talking about the speed the device boots up..we already have that from day one..takes me 15 seconds to boot...an Evo for example without HTC's fast boot takes like 2 minutes I hear :/
Thats good,
however I wanted a way to flash img files to my epic before making flashable zip and for that purpose I need support (on phone) from fastboot PC utility.
http://wiki.cyanogenmod.com/index.php?title=Fastboot
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=517874
In that order...there are no better tutorials. Read away.
bier
Call me a n00b, whatever. I am interested in testing a different radio on my Nexus S i9020a. I have recently noticed terrible download and upload speeds over 3G on my device since upgrading to Android 2.3.4.
My device is not rooted, and if this is a requirement to flash the new radio, then I will not do it. But my question is, can somebody guide me through the process step by step?
get fastboot (and adb while you're at it) working, then power of an boot into fastboot (or "adb reboot bootloader"), then:
"fastboot flash radio radio.img"
either "fastboot reboot" or just scroll down to reboot in the fastboot menu.
irishrally said:
get fastboot (and adb while you're at it) working, then power of an boot into fastboot (or "adb reboot bootloader"), then:
"fastboot flash radio radio.img"
either "fastboot reboot" or just scroll down to reboot in the fastboot menu.
Click to expand...
Click to collapse
This doesn't exactly help me because I don't know what any of that is...
http://forum.xda-developers.com/showthread.php?t=619153
irishrally said:
http://forum.xda-developers.com/showthread.php?t=619153
Click to expand...
Click to collapse
Hey, good to have you back here. Do you still have the ns or have you shifted?
Sent from my Nexus S using Tapatalk
You need to set up adb, you will also need to have Java jdk in order to set up adb. You will also need to have to have the correct drivers installed on your computer in order for it to communicate with your phone. IMO you might as well root your phone if your going to set up adb lol its the hardest part. Good luck. Btw Google is your friend, read read and read so you wont end up bricking your device.
Sent from my Sexy Nexy 4 GIZZLE!
deeren said:
Hey, good to have you back here. Do you still have the ns or have you shifted?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey, thanks man. My NS took a turn for the worst. I think I corrupted the memory as I could no longer write to the internal memory and the phone wouldn't get past the google splash screen. I spent a while thinking I could fix it (ODIN etc.) but finally gave up and sent it back to Samsung. They replaced the PBA (Printed Board Assembly), free of charge. I should be getting it back in the mail any day now. Can't wait, I've been stuck with my g1 for weeks now.
My 3g/mobile data is also guffed since the 2.3.4 upgrade and I'm going to revert the radio back.
I dunno if I'm being stupid but I can't seem to find any radio images anywhere...can someone point me to them please?
Thanks,
irishrally said:
http://forum.xda-developers.com/showthread.php?t=619153
Click to expand...
Click to collapse
Thank for the helpful link. And to reference "Google is my friend", I have searchec high and low for some kind of step by step guide on how to do this. Somebody want to point me in the direction of a guide or write up quickly here in this thread?
I just re-read your first post and I don't think you can flash a different radio if you are not rooted (could be wrong though). Honestly, flashing a radio has much higher risk than rooting your phone (but still low risk as long as you check the md5 on the radio image you download and you don't pull the battery during a radio flash).
If you choose to root, this is a good guide: http://forum.xda-developers.com/showthread.php?t=895545
irishrally said:
I just re-read your first post and I don't think you can flash a different radio if you are not rooted (could be wrong though). Honestly, flashing a radio has much higher risk than rooting your phone (but still low risk as long as you check the md5 on the radio image you download and you don't pull the battery during a radio flash).
If you choose to root, this is a good guide: http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
I found a thread on Modaco where Paul posted radios.
http://android.modaco.com/content/google-nexus-s-nexuss-modaco-com/333482/01-mar-xxkb3-gri54-basedband-radio-only-updates/
Not tried it yet...
Deeko1 said:
I found a thread on Modaco where Paul posted radios.
http://android.modaco.com/content/google-nexus-s-nexuss-modaco-com/333482/01-mar-xxkb3-gri54-basedband-radio-only-updates/
Not tried it yet...
Click to expand...
Click to collapse
I have the radio image I want to apply I just need to have some sort of guide on howvto apply. All this talk of fastboot and adb is in reference it seems to the Android SDK. I have the SDK installed and what not. But where do I go from there. Is there a way to root with stock recovery? Or just applyt the radio image without rooting in recovery mode with unlocking bootloader?
EvilSpants said:
I have the radio image I want to apply I just need to have some sort of guide on howvto apply. All this talk of fastboot and adb is in reference it seems to the Android SDK. I have the SDK installed and what not. But where do I go from there. Is there a way to root with stock recovery? Or just applyt the radio image without rooting in recovery mode with unlocking bootloader?
Click to expand...
Click to collapse
Fastboot or Clockwork Recovery is mandatory.
If you want to use stock + a radio. You can try renaming the .zip to update.zip and applying update.zip from stock Recovery but I'm not 100% sure if that would work.
best bet is to use fastboot or clockwork recovery.
Btw if you flash clockwork only once than it will not stick, than you can flash a new radio while still having stock recovery if that's you're jive.
Sent from my Sexy Nexy 4 GIZZLE!
Deeko1 said:
My 3g/mobile data is also guffed since the 2.3.4 upgrade and I'm going to revert the radio back.
I dunno if I'm being stupid but I can't seem to find any radio images anywhere...can someone point me to them please?
Thanks,
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showthread.php?p=14564429#post14564429
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Stop using one click crap. If you don't know what you're then you should not be messing with your device.
Sent from my DROIDX using XDA App
I can. Just won't.
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for
The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.
csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process
After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.
@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?
Just wondering if anyone has looked into this, and what it could possibly mean for our device if we could be merged. Apparently there's no need for special kernel modules, bootloader edits, or KEXEC, and I think it would be pretty cool to be able to use multi ROM to boot back and forth between stock and AOSP.
Why don't you explain what this is and provide a few links?
lafester said:
Why don't you explain what this is and provide a few links?
Click to expand...
Click to collapse
https://www.xda-developers.com/efidroid-is-a-second-stage-bootloader/
This article was the first I'd heard of it. But it does seem like it might be something easy to implement. It's basically multi ROM, but without all the requirements.
Looks interesting.
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
gecko702 said:
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
Click to expand...
Click to collapse
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
This is very, very interesting. I love the thought of just using LineageOS or RR for everyday things and then just switching to stock when I want to use media and enjoy the fantastic sound.
I'm not a developer, but I'd like to help/contribute in any way possible if someone's working on bringing unofficial support to the Axon 7.
jimbo77 said:
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
Click to expand...
Click to collapse
Very true. However, it makes ROMs easier to port and for more people to test, as then people can try them out without wiping their phone each time they want to try.
I was able to port and build right up until the last step where you generate lk.img and fastboot it to the phone. I'm running Linux inside a virtual machine and it doesn't seem to want to communicate, though adb does work.
I might try on the weekend to boot linux off a hard drive and see if it will work..
In the mean time, if someone else wants to try to build, it's really simple just follow these two guides:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Getting-Started
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
twoi said:
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
Click to expand...
Click to collapse
Did you try this fix for arm64 devices?
https://github.com/efidroid/projectmanagement/issues/89
Seems you need to dump aboot to check what's the correct address for LK to boot.
Edit: also did you try using freeza Beastmode boot.img? Probably that's better
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
Yeah that's he creator of Efidroid... Why don't you reply to that issue tracker and add the Axon 7 to the list of devices that don't boot because of the arm64 arch
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
yes you are on right track
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Druboo666 said:
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Click to expand...
Click to collapse
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
twoi said:
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
Click to expand...
Click to collapse
you should contact with the dev he may help you OP3 and A7 got same chipset so yeah it will help
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
twoi said:
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
Click to expand...
Click to collapse
you can contact @npjohnson or @m1cha with your compiled LK or boot maybe they can help
as they have fix Nexus 6P LK with no uefi boot
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.