I flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my data connection is broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radio/prevent the constant restarting?
You should have backed up the ril files on your /system/lib/ first before flashing a different variant.
you should find a couple of files in /system/lib/ named libril* and ends with a .so extension... Now what you need is copy those from a stock sprint ROM and replace the ones on the custom ROMs.
Riyal said:
You should have backed up the ril files on your /system/lib/ first before flashing a different variant.
you should find a couple of files in /system/lib/ named libril* and ends with a .so extension... Now what you need is copy those from a stock sprint ROM and replace the ones on the custom ROMs.
Click to expand...
Click to collapse
I just flashed viperBoy's stock ROMS both odexed and deodexed and got the same thing (still not working). I don't think it is the libril* files. Out of curiosity, what are they for?
Originally Posted by Riyal
You should have backed up the ril files on your /system/lib/ first before flashing a different variant.
you should find a couple of files in /system/lib/ named libril* and ends with a .so extension... Now what you need is copy those from a stock sprint ROM and replace the ones on the custom ROMs.
Click to expand...
Click to collapse
I just flashed viperBoy's stock ROMS both odexed and deodexed and got the same thing (still not working). I don't think it is the libril* files. Out of curiosity, what are they for?
Click to expand...
Click to collapse
Have you had a look in here?
Sprint HTC One forums
(sorry, was going to post a link to the forums root but the c&p failed)
Sent from my HTC One using xda app-developers app
Related
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
thoughtlesskyle said:
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
Click to expand...
Click to collapse
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
unCoRrUpTeD said:
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
Click to expand...
Click to collapse
ah i deleted the meta-inf folder thats probably what cause the problem
also am i able to have a folder that keeps things in /data like i am on the vogue or does it all have to be in the system?
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks!
If you ever figuered this out please let me know too, i am having the same issue. I am using a Captive that I just restored with Odin. I unroot it and remove the applock on it. I get the same installation aborted issue. I then tried to install it with ClockWork recovery... that just crashed my phone and I had to reinstall again. So if anyone know what the problem is please chime in.
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
TheEscapist said:
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
Click to expand...
Click to collapse
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
ootz0rz said:
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
Click to expand...
Click to collapse
No problem. While on the topic, is that thanks button new, or am i just blind, and missed it all this time?
It's something about signatures, if I remember correctly, though, that may be 3e. I think part of it is that it's just typically done with CWM.
ootz0rz said:
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks![/QUO
Flash perception
Click to expand...
Click to collapse
dfuse06 said:
Flash perception
Click to expand...
Click to collapse
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
ootz0rz said:
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
Click to expand...
Click to collapse
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
TheEscapist said:
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
Click to expand...
Click to collapse
I'd love to have a set of concise instructions detailing all that...but everything is all over the place and difficult to find :/ Right now I'm just mostly reading up on things and trying to learn
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
TheEscapist said:
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
Click to expand...
Click to collapse
Heh I've been trying. It's certainly a bit of a learning curve
Hi everyone, I need help over here as I'm stuck in the process of rooting & upgrading my Xperia TX (LT29i).
I have successfully downgraded the firmware & rooted it. However, I can't seem to find a stock ROM for Xperia TX (LT29i) 7.0.A.3.197 firmware. I just gone through all the hard ways to create a stock ROM myself & successfully flashed it. Perhaps bcuz of the improper build, my WiFi can't be turned on & there might be other problems coming up later.
Now I am also worrying that would it cause any prob to my phone. I followed this guide to create the ROM.
http://forum.xda-developers.com/show....php?t=1931189
& I took the META-INF folder from this custom ROM.
http://forum.xda-developers.com/show....php?t=2040989
Plz kindly help that if there's any resource to the stock ROM or any way to fix this, as well as have a look if there is any side effect from flashing that ROM. Many thanks! ><
You could try the repair phone option in SUS, with will reflash the stock firmware on your phone
One way to fix your problem is to copy /system/lib/modules/prima/prima_wlan.ko to /system/lib/modules/wlan.ko. An issue that I found with this solution, though, is the MAC address I got after copying the .ko file is different from what it was in stock. I can't figure out why. But regardless, your wireless LAN should work after you copy the file.
Montoyatok said:
You could try the repair phone option in SUS, with will reflash the stock firmware on your phone
Click to expand...
Click to collapse
Thx, I'm aware of this option. It's just that I want to know if what I did would create any prob to my phone in future, as well as if there's any stock ROM available on the forum. =)
chibikit said:
One way to fix your problem is to copy /system/lib/modules/prima/prima_wlan.ko to /system/lib/modules/wlan.ko. An issue that I found with this solution, though, is the MAC address I got after copying the .ko file is different from what it was in stock. I can't figure out why. But regardless, your wireless LAN should work after you copy the file.
Click to expand...
Click to collapse
Alright, will try. Thx. =) Do I've to keep the original file at the original location? Btw, is the way I'm building a ROM a proper way to do it? Do u know is there any ready-built stock ROM available?
Look in the very first thread of this section to find an index of every ROM and ftf
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
SCC2002 said:
Thx, I'm aware of this option. It's just that I want to know if what I did would create any prob to my phone in future, as well as if there's any stock ROM available on the forum. =)
Click to expand...
Click to collapse
Links to stock ROM FTFs are available in gregbradley's FAQ here under FTFs. You will need Flashtool to flash these to your phone.
Available stock-based TX ROMs are gregbradley's Assaye and travis82's 240 DPI stock ROM. I haven't tried either since I'm just fiddling about on my own, so I can't tell you how well those work, but Assaye is a good reference if you're trying to build your own stock-based ROM.
Alright, will try. Thx. =) Do I've to keep the original file at the original location?
Click to expand...
Click to collapse
I didn't do anything else except copy the file, so the original prima_wlan.ko is where I found it on my ROM.
Also, I've been watching this thread on similar problems with the Xperia V and a solution has been found. I'm planning on trying it out on my TX some time this week to see if it will solve my MAC address woes.
Btw, is the way I'm building a ROM a proper way to do it?
Click to expand...
Click to collapse
The thread you linked to are instructions on building ROMs for older Xperia phones. Steps 1 - 4 don't need to change for our phones, but the TX uses a different partition scheme (or something), and this means step 5 needs to be different since our system.sin's contents are actually in ext4 format, not YAFFS. A typical Windows installation will not be able to handle the file contents. You can use mounting utilities to read the file and copy them over to your Windows hard drive, but all symbolic file links will basically be destroyed.
Currently, I'm using dsixda's Android Kitchen to build my own stock-based ROM. It's really just a collection of utilities that allows me to make all the necessary file changes and edits that I want before generating a ROM .zip file that can be flashed in CWM. This really needs Linux to work, which is a plus because the file system used by Linux is usually ext4 by default, making it easy to work with the contents of the decrypted system.sin.
If you're planning to build a simple custom ROM, I suggest you read up on how to use dsixda's Kitchen, but keep the following in mind:
- the Kitchen works with a system.img file, which is really just the system.ext4 you get from decrypting system.sin
- the Kitchen will complain about not having a boot.img to work with. Ignore it; I don't think you're building a ROM with a custom kernel, so you don't have to worry about it.
- the default contents of META-INF that the Kitchen generates does not work with CWM for locked bootloaders on the TX. I don't think it works with unlocked bootloaders either. The solution is to stea-... err, borrow the update binary and updater-script from a working ROM zip and edit it for use on yours.
Also, read gregbradley's Assaye ROM thread and TiMiN8R's stock and deodexed ROM thread. They are using dsixda's Kitchen as well, and you can learn a lot about fiddling with stock ROMs from reading about the problems they encountered and how they fixed them.
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
It may have been flashed to the 883 radio. I would do a complete SBF.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
I have sbf'ed the phone, but it hasn't fixed the problem. I have installed the 833 radio previously and made sure I have pushed the build.prop into the system folder still without luck of fixing the problem. After a little more research, could the EFS folder be corrupt/deleted causing the problem?
Skreelink said:
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
Click to expand...
Click to collapse
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
dinosaur swagg said:
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
Click to expand...
Click to collapse
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
htsebar meafure
Skreelink said:
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
Click to expand...
Click to collapse
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
dinosaur swagg said:
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
Click to expand...
Click to collapse
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Skreelink said:
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Click to expand...
Click to collapse
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
dinosaur swagg said:
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
Click to expand...
Click to collapse
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Skreelink said:
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Click to expand...
Click to collapse
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
dinosaur swagg said:
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
Click to expand...
Click to collapse
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Skreelink said:
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Click to expand...
Click to collapse
Okay so I have the 883 modified build.prop. Do you happen to have or know where/how I can get the stock build.prop?
Ok. I'm currently stock 4.4 (Sprint) rooted with the latest TWRP recovery. The stock ROM is, of course, odexed. I've never messed with odexed ROMs before, since I've always just stuck with AOSP type ROMs. I've found a few cool inverted 4.4 apps (i.e. MMS.apk) and I'm wondering if there is a way to flash a typical deodexed app onto an odexed ROM like this? Maybe by deleting both the MMS.apk and odex file before flashing? Thanks for any help.
sasokutenshin said:
Ok. I'm currently stock 4.4 (Sprint) rooted with the latest TWRP recovery. The stock ROM is, of course, odexed. I've never messed with odexed ROMs before, since I've always just stuck with AOSP type ROMs. I've found a few cool inverted 4.4 apps (i.e. MMS.apk) and I'm wondering if there is a way to flash a typical deodexed app onto an odexed ROM like this? Maybe by deleting both the MMS.apk and odex file before flashing? Thanks for any help.
Click to expand...
Click to collapse
You got it, just delete or rename both the apk and the odex file and manually install the apk, change permissions and reboot
Sent on my Moto X