Ok, im am trying to re-compile a SMG file that i have unpacked with unyaffs.
this is what i am trying to do before everyone starts shouting that you can just use a update.zip
Where i work we are about to start reselling Verizon Wireless under a different name, we buy our phones from Verizon.
i am trying to "de-Verizon" the phone and put some of our own customizations on it ie: Carrier text, boot screen ect...
any way, i need to do this in the least intrusive way so that i can show the AE's how to do it before giving to customer, or can be done by some one else.
The RSD-lite method looks the best, i have already successfully changed the moto logo and go that working, but now i am trying to edit the Carrier Text "eri.xml" in the stock load WITH OUT rooting.
Once i unyaffs the file i can do what i need to do but what steps do i need to take to compile it back into a smg file?
does anyone have a better suggestions for what i am trying to do?
Thanks, this forum has been a GREAT help
Related
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
thanx
thanx its working
thank you.
singhshb said:
thanx its working
Click to expand...
Click to collapse
You're welcome!
daydream3r said:
thank you.
Click to expand...
Click to collapse
batinica said:
This no doubt a noob question but when you say "Just open up the firmware zip with 7zip, and extract the signed-aboot" how do I go about get the zip from my device?
Click to expand...
Click to collapse
You don't get the zip from your device. What you need to do is search for a firmware zip here on XDA and use it. You will probably find someone who has already made a no red text firmware zip and use the ABOOT from it, but where's the fun in that. You could make your own firmware zip, but that's not the purpose of this thread. Search for a thread on XDA to teach you how to make a firmware zip if you are interested in doing that as well.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
help please
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
Sorry my friend but looks like hard brick if it won't power on. there's nothing you can do but jtag.
This is a dangerous thing to do and could destroy your device. You are hex editing the a boot, which is cannot be compromised in any way or you will end up with a paperweight. You see, your bootloader is no longer operational. That's why your phone won't power on. In this case, allowing somebody to do it, that had no clue what they were doing, was extremely risky and foolhardy and looks to have destroyed your device.
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
I'm sorry to hear that your brother made a mistake editing the ABOOT. Like @Behold_this said you are now going to have to take your phone to a repair shop that has the professional tools to restore your phone to a working condition. If you are with T-Mobile and bought the phone through them you may be able to take it to them and get it replaced. Just don't mention that you modified the ABOOT. Also, if you are a US customer and you haven't used your Uh-Oh protection you can try that. I know that Mo Versi had said rooting your phone would not void the Uh Oh protection, but I don't know about modifying the ABOOT. They're all worth a try. I wish you the best with this. There's always a risk when you modify a device like we do here on XDA. The key is to always follow directions carefully, and if you're not a 100% sure of what you are doing don't do it.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
please help me
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
bakh1 said:
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
Click to expand...
Click to collapse
As far as I know that project was for the M7 and won't work on the M9. Besides that method required for the phone to boot to bootloader or fastboot I believe. Since your phone won't boot at all the only thing I can think to do is go through your carrier or HTC. HTC has repaired or replaced many bricked devices free, but I have heard of a few cases where they would charge. If you don't mind not telling them the complete truth about how it was bricked you could tell them it was in the process of updating when it happened. That has actually happened on the M7. This is the first time I have actually heard first hand of a M9 hard bricking. All of the other ones I have heard about were able to boot to download, htc ftm, or bootloader mode and could be recovered. You have tried to boot to htc ftm by holding the power and volume up buttons continuously?
Using XDA to unleash the power of Android in my S7 Edge, One M9, and S6 Edge Plus
jbfountain said:
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
Click to expand...
Click to collapse
I finally found your effort of writing this "recipe".
Thanky for sharing!
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
drfarmkid said:
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
Click to expand...
Click to collapse
The red text that appears on your phone after unlocking it doesn't have any functionallity. Some just do not want to see it. That's what this is all about. If you don't want to see it use this method. If it doesn't bother you don't do it.
Cheers
Sent from my HTC 10 using XDA Labs
I went and did it. I bricked my new phone. I'm in a pickle here and need help desperately. I know I messed up the carrier folder. I have a backup of it, but don't know how to go about restoring it.
The phone turns on and tells me "Unfortunately, the process com.android.phone has stopped" followed by many more apps force closing.
Wifi, data, and signal all do not work. The phone reboots itself before I can do anything.
If I placed the carrier folder inside the system.img that I have backed up and ran the dd command from download mode, would it restore it?
That's just an idea I had that probably won't work. I really freaking out over this.
I've tried using the dd command on my system image already but the problem is still there. Any help would be greatly appreciated.
Edit: Could maybe flashing someone's carrier image work? If anyone has one I would greatly appreciate it. Please help me, I know I can't be the only person whose had this problem.
Edit 2: My wifi is actually working, I somehow didn't see the icon. But no signal barks appear for the cellular connection.
Try doing the TOT method. Completely puts everything back the way it was. if you're on android M use the ZV9 file and if youre on lollipop use the ZV6 one.
Restore with the TOT... there is a thread with instructions in the forums dev section.
From my experiences with the carrier folder. Files in the carrier folder does not get modified/restored when restoring from a tot file. It stays the same from one rom to the next. I had an issue with activation and updating my prl after doing the sim unlock from http://forum.xda-developers.com/sprint-g4/general/guide-sim-unlock-t3229801 but I fixed that issue by changing the permission of node.db and node.db-journal to rwrwrwrw.
The Alcatel 5033T (Telstra) I have is Telstra-locked to the point that most online unlock-code providers can't get a code to free it up. The only places which say they can do it require you to bring it in (they're in other states) or they want you to install Teamviewer (!) and they'll do it remotely.
I'm sure this is a FAQ on other phone models, but I see nothing for the Alcatel 1 here yet. What are the chances someone with past experience on ADB can figure out how to get this working with a non-Telstra SIM?
Did you manage to sort this
How to mount sd card
saw someone posted this, any Guru can verify the steps? or make it clearer?
**********************************************************************************
On the 5033T fastboot will flash only the system.img not the boot or recovery
image,so Magisk or TWRP cannot be flashed via fastboot. Also to flash via SPflashtool for the MT6739 you now need a custom DA and Auth file for that phone.
The downloaded edited 5033D system image will give you root access but install
RootCheckerBasic app to check as sometimes the root access disappears.
The phone modem is in the vendor.img partition and so should be unaltered as you
have flashed the system.img partition only.Your bands should be unaltered. Install the MTK Engineering Mode apk and use the bandmode function to see the bands. (Phone Developer option must be on(Tap build number untill developer options appear)).
Now that you have root access you can now network unlock the phone. Using ES File Explorer or Root Explorer. In the phone /vendor/protect_f/md you will see a file ST33_004. This file determines whether the phone is network locked.
If you get this file from an unlocked phone and put it in place of the one
in the locked phone the phone will be then unlocked and vice versa.
Download the 5033A firmware from the Needrom site. From the download get the protect1.img (in another files). Download to your PC the Ext4Unpacker tool.
Use the tool to extract the ST33_004 file from the 5033A protect1.img .
This is the unlocked ST33_004.
Using ES or Root Exp rename the existing ST33_004 in the phone as ST33_004bac
and copy the new ST33_004 file into the directory. The phone will now accept
non Telstra/Boost SIMs .
Also download the Mobile Upgrade S Gotu2 v5.3.5 tool to your PC. This is the TCL(i.e.=Alcatel) official firmware upgrade tool. It replaces the firmware in
your phone with the latest version on their server for your phone. For a stock
phone it will upgrade to their latest stock version.
For the 5033T+5033D 'hybrid' ,when started the tool appears to be downloading
the 5033T firmware from the server, so it seems that the tool could be used
to return the phone to stock, but this not tried or tested yet.
bmscott said:
The Alcatel 5033T (Telstra) I have is Telstra-locked to the point that most online unlock-code providers can't get a code to free it up. The only places which say they can do it require you to bring it in (they're in other states) or they want you to install Teamviewer (!) and they'll do it remotely.
I'm sure this is a FAQ on other phone models, but I see nothing for the Alcatel 1 here yet. What are the chances someone with past experience on ADB can figure out how to get this working with a non-Telstra SIM?
Click to expand...
Click to collapse
saw someone posted this, any Guru can verify the steps? or make it clearer?
Click to expand...
Click to collapse
Where'd you find this? I'm willing to try 'cos it'll let me get my son off Telstra's overpriced plan and onto something affordable like Jeenee (which the rest of us are on). I've had this Telstra SIM for years so I was hoping they'd unlock the phone for me - after all, it was sent as a replacement for an older phone that'll be out of service when they retire some of the towers in our area - but when I call in to have them do that, they say they'll have to call me back and (of course) never do...
Found the post from ozbargain forum with this 5033D link
https://yadi.sk/d/_-dnrtKS499rww
The 5033A you need to get it from needrom
Any luck someone? I am unable to root it using kingroot
Yes
The Ozbargain thread now has a lot more info than it did a few months ago - I'm still working through it myself, but here's the link: https://www.ozbargain.com.au/node/446160
I ignored the warnings... I know, idiot.
But I went ahead and it completed.
But now the phone has a black screen and nothing else.
When plugged in, my computer recognises it as Qualcomm 9800 port 30.
Still nothing on screen though.
Anyway to get it back? Or get it to stock rom? Really don't want tmobile bloat all over it if possible.
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Double post.
What is it about the T-Mobile version that makes it so different to the others.
NGOwner said:
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Click to expand...
Click to collapse
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
shawnmos said:
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
Click to expand...
Click to collapse
It's not the modem partition, it's the ftm (and maybe some others too)
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
Why would you want to flash a T-Mobile stock ROM?
Ainz_Ooal_Gown said:
Why would you want to flash a T-Mobile stock ROM?
Click to expand...
Click to collapse
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
aw2a said:
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
Click to expand...
Click to collapse
Ahh I see well we do have Android 10 in the flavors of LOS 17.1 and Havoc OS 3.5..
No firehose loader for the T-Mobile one so you can't fix in 9008 mode. It is a paperweight. You need to replace the motherboard.
Bump? Any way to revive it?
slebeau1988 said:
Bump? Any way to revive it?
Click to expand...
Click to collapse
You could try asking tmobile for help and see how much they'll charge you. You may get lucky if the phone is still in warranty
aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
hey bro, how did you make a rawprogram.xml file, i've searched everywhere on the internet but no luck so far.
So i bought and installed this radio. it has been a great radio so far. their customer service also allows for you to customize the boot logo to a more factory look. so thoughts on if it is possible to include something like android auto through a third party setup. It looks to be android based but doesnt include it from the start. I am not gifted when it comes to coding and unsure of where to even begin. I will include the amazon link and i also have the update file they sent me with the pictures i uploaded to them. Also if someone might be able to guide me into incorporating more images without having to email them as i like to change things like the boot logo and maybe have a animation type logo if possible. the file they sent me was a .bin file and upon extracting it it just shows a blank file.
Amazon.com
this is the update file.