Related
For anyone that is building their own kernels, I highly recommend grabbing this patch:
https://github.com/invisiblek/andro...mmit/f745249b52cab9feb5b7821b54d47176ae093617
Details in the commit comments.
You know what I've been hacking phones for awhile and I forgot about fastboot booting a boot.img
Haven't tried it, but sounds like nice work!
I had another idea for adding some safety - early in the boot process set the bootlloader message to tell the bootloader to boot into recovery mode (but don't actually reboot), then later when the boot is complete, reset the message. That way if the user reboots anywhere in between, they will boot into recovery.
Hope that makes sense, I brainstormed over the idea in another thread: http://forum.xda-developers.com/showpost.php?p=44030783&postcount=8
Feel free to implement any of my ideas you like - I don't have as much time for Android development as I would like.
~Troop
Trooper_Max said:
Haven't tried it, but sounds like nice work!
I had another idea for adding some safety - early in the boot process set the bootlloader message to tell the bootloader to boot into recovery mode (but don't actually reboot), then later when the boot is complete, reset the message. That way if the user reboots anywhere in between, they will boot into recovery.
Hope that makes sense, I brainstormed over the idea in another thread: http://forum.xda-developers.com/showpost.php?p=44030783&postcount=8
Feel free to implement any of my ideas you like - I don't have as much time for Android development as I would like.
~Troop
Click to expand...
Click to collapse
Yea, you could probably make the kernel write to scratch right away, in the case that it panics, dump it into recovery or bootloader, then clear it upon a full, successful boot. But that sounds like a lot more work and in the end, you really don't get anything more than this. This patch will save you from anything except a kernel panic that happens way early. (or of course blatantly flashing crap to the wrong partitions )
invisiblek said:
Yea, you could probably make the kernel write to scratch right away, in the case that it panics, dump it into recovery or bootloader, then clear it upon a full, successful boot. But that sounds like a lot more work and in the end, you really don't get anything more than this. This patch will save you from anything except a kernel panic that happens way early. (or of course blatantly flashing crap to the wrong partitions )
Click to expand...
Click to collapse
Ah, I was just thinking maybe it would be possible to write to scratch earlier than the sysrq method becomes available and thus be a little bit safer. It also wouldn't require a keyboard though that point would be a bit moot as you'd need a keyboard once you reboot into recovery. So you're right, it probably doesn't make much difference.
Have you ever done anything with kexec? That was the next thing I wanted to look into once we got something like this for booting more safely. I know people use it for multi-boot methods and someone even came up with a way to hardboot a Nexus 7 with kexec:
http://forum.xda-developers.com/showthread.php?t=2104706
Eventually, I'd like to develop something like that into a boot image that could be stored on the boot or recovery partitions and function as an extra bootloader to allow booting images stored elsewhere.
Anyway, thanks again for sharing your work, and I don't mean to hijack your thread - if you want to discuss ideas I had hoped more people would join in on brainstorming in my thread: http://forum.xda-developers.com/showthread.php?t=2380314
~Troop
Trooper_Max said:
Ah, I was just thinking maybe it would be possible to write to scratch earlier than the sysrq method becomes available and thus be a little bit safer. It also wouldn't require a keyboard though that point would be a bit moot as you'd need a keyboard once you reboot into recovery. So you're right, it probably doesn't make much difference.
Have you ever done anything with kexec? That was the next thing I wanted to look into once we got something like this for booting more safely. I know people use it for multi-boot methods and someone even came up with a way to hardboot a Nexus 7 with kexec:
http://forum.xda-developers.com/showthread.php?t=2104706
Eventually, I'd like to develop something like that into a boot image that could be stored on the boot or recovery partitions and function as an extra bootloader to allow booting images stored elsewhere.
Anyway, thanks again for sharing your work, and I don't mean to hijack your thread - if you want to discuss ideas I had hoped more people would join in on brainstorming in my thread: http://forum.xda-developers.com/showthread.php?t=2380314
~Troop
Click to expand...
Click to collapse
We used kexec on the vzw sgs3. It may be useful here but really probably isn't too necessary
Sent from my HTC6435LVW using Tapatalk 4
where can i find motorola custom fastboot commands?
i'm stuck on 4.4.3 with CWM.
i want to install stock 4.4.4 but i can't because of CWM.
and i can't remove CWM because motorola only provides 4.4.2 which can't be flashed over 4.4.3
I'm figuring that if RDS-lite or whatever out-of-nowhere program can do that, it does so using fastboot commands. and that list of commands may be available somewhere.
anyone have any idea?
thanks.
there are no "custom motorola fastboot commands".
RSDLite doesn't use mfastboot
What model X do you have?
Have you tried looking at both -> http://sbf.droid-developers.org/phone.php?device=0 and http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 for the SBF you need?
You can use mfastboot to flash an older recovery.img. It SHOULD work, however future OTA may fail due to an incorrect version of recovery.
KidJoe said:
there are no "custom motorola fastboot commands".
RSDLite doesn't use mfastboot
What model X do you have?
Have you tried looking at both -> http://sbf.droid-developers.org/phone.php?device=0 and http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 for the SBF you need?
You can use mfastboot to flash an older recovery.img. It SHOULD work, however future OTA may fail due to an incorrect version of recovery.
Click to expand...
Click to collapse
What does RDSlite uses?
gcbxda said:
What does RDSlite uses?
Click to expand...
Click to collapse
Install RSD-Lite. Download zip file from above link and unzip it. Boot your device to Bootloader and connect to PC via USB. Open Rsd-Lite and Select XML file from unzipped folder. Click "Start". RSD-Lite will automatically install for you.
kenosis said:
Install RSD-Lite. Download zip file from above link and unzip it. Boot your device to Bootloader and connect to PC via USB. Open Rsd-Lite and Select XML file from unzipped folder. Click "Start". RSD-Lite will automatically install for you.
Click to expand...
Click to collapse
I'm more interested in what RDSlite uses to talk to the phone. Any idea about that? thanks.
gcbxda said:
I'm more interested in what RDSlite uses to talk to the phone. Any idea about that? thanks.
Click to expand...
Click to collapse
routines built into the exe and dll's of the app.
Seriously, its not a "front end" or "gui" to mFastboot or other tool. Its its own tool. Just like the software updater that is part of the Motorola Device Manager package is its own tool.
RSDLite is basically Moto's equivalent to Samsungs Odin.
KJ said:
RSDLite is basically Moto's equivalent to Samsungs Odin.
Click to expand...
Click to collapse
which i also failed to find any info about.
how do they talk with the phone?
a binary protocol? is there anyone trying to decode that?
i have a windows VM with RDSlite now... one of the advantages of those two companies releasing a rogue program like that, they don't have to give support if it burns down your house and kill your cat, but i also do not have to agree to not reverse engineer it ...if it was released by those companies and not some chinese gov spy agencie
Dunno... I use them and they work. Good enough for me. ?
Not a conspiracy theorist here. ?
KJ said:
Dunno... I use them and they work. Good enough for me. ?
Not a conspiracy theorist here. ?
Click to expand...
Click to collapse
lol. just because i'm paranoid, it does not mean they aren't after me!
i was sure i wrote more to that reply than just the joke... sigh, either i'm getting more retarded by the hour or the CIA did it!
anyway, joke aside, think about it:
if there is a secret protocol that the manufacturer implements on their fastboot to do things like downgrade without any hassle and probably much more, like flashing modem and other parts that we don't have access normally, why the heck should we not investigate it?!
my curiosity is less about paranoia (even though i'm 99% sure odin and rdslite are the work of a joint china-us spy effort that patches images on the fly to include backdoors) and more about unlocking more from our hardware.
i think in the end i'm still pissed off that i carry a computer more powerful than my desktop but that can only run a silly UI because i have access to nothing.
gcbxda said:
anyway, joke aside, think about it:
if there is a secret protocol that the manufacturer implements on their fastboot to do things like downgrade without any hassle and probably much more, like flashing modem and other parts that we don't have access normally, why the heck should we not investigate it?!
Click to expand...
Click to collapse
Well, first off, the only difference between fastboot.exe from the Android SDK and moto's patched version (aka mFastboot) is the ability to flash larger files. The system partitions on Moto phones have been bigger and therefore the mFastboot was created. Standard fastboot will tell you the file size is too great when flashing system.img to Moto phones and that is why mFastboot is needed.
Using fastboot or mfastboot you can downgrade SOME PARTS "without any hassle." However, there are security measures on the phones which prevent downgrading certain parts (think S-ON vs S-OFF on HTC). Moto doesn't allow you to downgrade the GPT.BIN or the contents of Motoboot.img. But you could flash older logo.bin, recovery.img, boot.img, system.img, and modem/radio files. that being said, there are compatibility and other issues that pose other problems when you downgrade.
Fastboot and mFastboot does allow flashing the modems and other parts. The moto X does have a /persistent partition which is not contained in the SBF. But if unlocked & rooted, we can modify it (add/remove files).
gcbxda said:
my curiosity is less about paranoia (even though i'm 99% sure odin and rdslite are the work of a joint china-us spy effort that patches images on the fly to include backdoors) and more about unlocking more from our hardware.
Click to expand...
Click to collapse
Well, RSDlite is a moto tool, and Odin is a Samsung tool.
as for "China-US Spy effort" I'm not even going to go there, other than saying that IS paranoia.
Feel free to sit down, decompile them, analyze them. If you find PROOF anything, post it.
gcbxda said:
i think in the end i'm still pissed off that i carry a computer more powerful than my desktop but that can only run a silly UI because i have access to nothing.
Click to expand...
Click to collapse
Feel free to sit down and create your own port of Android... or take the time to program your own OS. But these are not meant to be "totally open" devices that the user can do anything they want on it. There are some proprietary components. There are some limits.
KidJoe said:
Well, first off, the only difference between fastboot.exe from the Android SDK and moto's patched version (aka mFastboot) is the ability to flash larger files. The system partitions on Moto phones have been bigger and therefore the mFastboot was created. Standard fastboot will tell you the file size is too great when flashing system.img to Moto phones and that is why mFastboot is needed.
Using fastboot or mfastboot you can downgrade SOME PARTS "without any hassle." However, there are security measures on the phones which prevent downgrading certain parts (think S-ON vs S-OFF on HTC). Moto doesn't allow you to downgrade the GPT.BIN or the contents of Motoboot.img. But you could flash older logo.bin, recovery.img, boot.img, system.img, and modem/radio files. that being said, there are compatibility and other issues that pose other problems when you downgrade.
Fastboot and mFastboot does allow flashing the modems and other parts. The moto X does have a /persistent partition which is not contained in the SBF. But if unlocked & rooted, we can modify it (add/remove files).
Well, RSDlite is a moto tool, and Odin is a Samsung tool.
as for "China-US Spy effort" I'm not even going to go there, other than saying that IS paranoia.
Feel free to sit down, decompile them, analyze them. If you find PROOF anything, post it.
Feel free to sit down and create your own port of Android... or take the time to program your own OS. But these are not meant to be "totally open" devices that the user can do anything they want on it. There are some proprietary components. There are some limits.
Click to expand...
Click to collapse
lol, stop paying attention to the joke man
and not talking about mfastboot, talking about how RDSlite talks to the phone. if that does MORE than fastboot/mfastboot, why shouldn't we found out how? that's basic curiosity, despite paranoia.
and i did try to install the 4.4.2 they provided over 4.4.3, but there is no point in allowing to install recovery or whatever if you need a new partition layout everytime. so allowing downgrading something but not gpt is the same as nothing.
I'm working on a (100% legit legal and 100% ORIGINAL works) way to flash to our /system partition for kitkat.
I've put my turbo through physical abuse. And it finally croaked weeks after "the drop".
I would need someone who has flashed a /system img via mofo to run USBlyzer on the correct port during the flashing process and then save and upload the log file. I will guide as needed. Remote desktop would allow me to quickly setup and start the process.
No longer having a phone that even turns on, I've resorted to using as USBlyzer as my debugging info by comparing my output to the known correct output. However, I have only logged the beginning of an upload. I need a complete, in order log.
I can help in about 12 hours
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
5.1:
How it works: Nobody has a clue because the 4.4 loophole is patched.
4.4
How it works: (I'm just making an example don't pick apart my math or partition sizes)
system.img = 3.5gb
cache partition = 1.5gb
So with a modified fastboot, you will write to the cache partition, but send more than 1.5gb of data, since the /system partition is next in order anything you send now will actually write to /system and not the /cache partition.
There are a few quirks I've seen, fastboot sends the "download" command 2x back to back, while the first "download" command hardly sends anything. This has something I assume to be "fake writing" Not quite sure. Its like it writes a tiny amount of data to /cache, sends the second "download" command to now write to /system. I've noticed that the data sent to /cache is actually a clone of a portion of the data sent to /system. Also there is 3gb of ram on the device, so after that gets filled up, the flash command is sent, then it goes back to download commands.
At the end it erases /cache because its full of garbage.
koftheworld said:
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Click to expand...
Click to collapse
SaschaElble said:
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
Click to expand...
Click to collapse
Fair enough that is exactly why I stayed on kk.
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Does anyone have any info on the lolipop .img s
SaschaElble said:
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Click to expand...
Click to collapse
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
just use a vm...
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
Good idea. I'd be willing to do that.
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
That log data contains your device serial and UID for your turbo... Thanks for helping the turbo community!
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
That should work
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
SaschaElble said:
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
Enjoy uploading 5-8gb of log data since you don't trust me being on your computer. Oh and since we are talking trust, that log data contains your device serial and UID for your turbo... SO actually you might not even want to do that either. Thanks for helping the turbo community!
Click to expand...
Click to collapse
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
TheSt33v said:
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
Click to expand...
Click to collapse
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
SaschaElble said:
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
Click to expand...
Click to collapse
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
TheSt33v said:
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
Click to expand...
Click to collapse
lol. I will for sure! But I won't get banned again. Not if everyone plays by the same rules they expect me to.
Anyone is free to contact me at (Edit: I was such an idiot. 5 years later... wow. ) If you want an easy two click way to get onto my channel on IRC follow the link in my signature.
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Michaelmansour1997 said:
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Click to expand...
Click to collapse
I would buy the bricked one, or you can let me see if I can fix it remotely.
NEW:
My vouching thread for those who I request access to their device remotely or gain knowledge of sensitive information:
http://forum.xda-developers.com/general/off-topic/saschaelble-vouching-thread-want-help-t3150299
Do you have a hangouts
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
rp201 said:
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
Click to expand...
Click to collapse
Howdy! Sorry it's taken three months for your question to get any attention. Bionic forum's pretty dead, eh? I'm amazed it's still an officially supported Lineage device. Go team!
Sadly, the no one ever found a bootloader unlock, as a fellow informed me here two years ago. Unless some clever hacker happens upon a Bionic and decides to crack it for kicks, it's not likely to happen. But at least we have SafeStrap and Lineage!
You may know this already, but you didn't mention it in your post, so I'll go ahead and say: when installing a ROM like Lineage on the Bionic with SafeStrap, you need to install it on ROM Slot 1, not the Stock ROM Slot. I imagine that might be why you bricked your phone (I've done it myself a few times too ).
Now that I've given you the skinny on the Bionic's limitations, let's see if we can't get you back afloat. Whenever I bricked mine, I never used RDS Lite—I found a utility called House of Moto. You can find the home page here, but you'll need to create an account to see the important stuff and the downloads (you'll also need to install Java). But if you're more familiar with RDS Lite, feel free to use that instead
System images for the Bionic are hard to find nowadays. I seem to have found one link to an article with a direct download link to an update file at the bottom, which I'll link to here. Whether the update file is the same as an FXZ file RDS Lite/House of Moto requires, I'm not sure. Give it a try and see how it goes! If not, I may have a copy of the file on my old computer at my parents' house. If the linked update file doesn't work, I'll see if I can't get ahold of my image file.
Finally, if you do happen to get things up and running happily, I've got a list of optimizations that help Lineage run more smoothly.
Best of luck! :good:
Can someone please with ATT android Q build 30E send me both A and B boot.img
nikothebarber said:
Can someone please with ATT android Q build 30E send me both A and B boot.img
Click to expand...
Click to collapse
Niko, yer asking everywhere for this, but u already have it right? Your phone is att updated to 30e right?
So, just like anyone else would have to do, use qfil and get it? I mean, if you're going to root and get twrp on the device, you're going to have to install and learn to use, qfil.
As I mentioned in another thread, if you post your boot_a image, I'll twrp patch it for u and post it back.
Do you need help using / installing qfil?
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
nikothebarber said:
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
Click to expand...
Click to collapse
Okay, since you did an OTA update (right?) then the other boot image would be the previous version OS for att. Maybe to get the newest one u can do the update again? (I don't know, I"m asking, I don't have a carrier specific phone so no way to test that).
Also, that NT error code is usually only going to occur when u 'cross flash'. Which makes me wonder... what boot partition are u really using? It sounds like it **may** not even be an att one?
I better understand your situation now, sure does make it obvious why you want to do a backup before any modifications right? sorry, I'm sure you've learned that lesson now, but maybe others can benefit from your tough lesson.
Here's the first thing I'd do if u; Make A COPY OF EA boot partition, as they are now. At least you'll have a backup of ea one from here (whatever they happen to be).
One of the easiest ways to do that would be (assuming you have twrp injected), would be to boot recovery, connect to pc with usb cable, and type in 'adb shell'.
Then use the following dd commands (modify for your directory structure on sd card);
dd if=/dev/block/bootdevice/by-name/boot_b of=/external_sd/backup/current_att_boot_b.img
this assumes you have a directory on your sd card called 'backup'. Replace it with whichever you may have. Do the same for boot_a also (change boot_b to boot_a), and change the output name to reflect what you're backing up.
So with these backups, you **could** decide to copy your boot_b backup tot he boot_a partition and see what happens? I mean it sounds like you're not sure what is on either one of your boot partitions, so trying that may be the only way to have some idea of what's there.
*If** it turns out that the device boots okay with boot_b copied over, then at least you'll have a boot partition that could be twrp injected and not have the nt_error code?
good luck
I mixed up the active side and replaced one with the other already . I never did OTA and unfortunately it does not work. I have back ups now of boot a and b with qfil, my firmware is 30e and boot img is 30b. I need boot.img 30E
I've got 30e boot.bin can.you add twrp to it
nikothebarber said:
I've got 30e boot.bin can.you add twrp to it
Click to expand...
Click to collapse
Well I have no way of knowing which one is 30e and which is att prior version. But I can tell you the 30e_a u posted here is identical to the 30e_a posted in this thread.
cheers