Related
Just order a new atrix 4G. I have looked at the possible ROM's to use and I want to try out the Neutrino ROM. I have rooted devices before but I am new to Motorola devices. Please help me find the CURRENT steps I need to take to get to be able to run the Neutrino ROM? I have used the search bar but a lot of the threads that I have found contain links that are no longer valid. Such as http://forum.xda-developers.com/showthread.php?t=1154600 Also I read a this link http://www.xda-developers.com/tag/motorola-atrix-4g/ which has me a worried that I may end up having an issue because all of the guides or seem to have been written before May 15th.
Thanks for taking a look and sorry if that was a little confusing I just didn't want to get flammed for being lazy. In the end I just want to know the most up to date way to get to the Neutrino ROM?? Below I will have included the specs. If I need to post anthing else please let me know
I recieved my phone last night and set it up on Striaght Talk.
System version: 45.31.0.MB860.AsiaRetail.en.03
Model Number: MB860
Android Version: 2.3.4
Your help is GREATLY APPRIECIATED!!
Also on the youTube videos they all seem to say "DO NOT DO TRY TO UNLOCK OR ROOT IF YOU HAVE 2.3.4 OR IT WILL BRICK YOUR PHONE!!"
Is this still the case or has there been a work around for it yet??
you have to unlock bootloader, but you can get FAIL with last step.
If you will get fail - don't worry, you can still unlock it via fastboot (tested on mine INTL Atrix, but every phone is a little bit different)
flash recovery, wipe data, wipe cache, wipe dalvik, flash rom, flash gapps. Done
Thanks ovitz. Can you point me to a thread describing how to unlock the bootloader on this phone?? I can do all the other stuff that you said I need to do after the bootloader is unlocked(clearing and flashing). Just really dont want to mess up my phone. I got 2 actually one for my girlfriend as well. I have java and all SDK/ADB and all programs that I may need. Just want a step by step for comfort.
Is the search not working for you?
http://cleanimport.xda/index.php?threads/1136261/
The thread is sticky even.
DISCLAIMER: I used this to unlock the BL on my Atrix, but mine is an older one, dating back to around Feb 2011. I do not know if this still works on brand new devices, however I am not aware of any other way to unlock (there probably isn't any other way really).
What is the other way (not using fastboot) to unlock this bootloader?? I tried fastboot oem unlock and got this message "INFOOEM unlock is not implemented"
Do I need to use an SBF with RSDlite or something to make this possible? If so please point me in the direction of that thread!?!
Thanks for anyone that can help
ravilov said:
Is the search not working for you?
http://cleanimport.xda/index.php?threads/1136261/
The thread is sticky even.
DISCLAIMER: I used this to unlock the BL on my Atrix, but mine is an older one, dating back to around Feb 2011. I do not know if this still works on brand new devices, however I am not aware of any other way to unlock (there probably isn't any other way really).
Click to expand...
Click to collapse
Sorry ravilov...Did not see your post as I had started a post and then ventured off to seach XDA and some other forums again as well. I have gotten to the link that you posted several times. I just saw that is was posted a long time ago and that there is a lot of things in that post that dont make too much sense to me.
First it says "All phones If you have unlocked then try to use 2.3.4 update zip from Motorola servers, then revert back to a "pre-unlock" version(1.8.3 or earlier on ATT) you will get bricked! Do not use the OTA via experimental servers and revert to older versions WITHOUT pudding preinstalled in your sbf. ATT ONLY Get your 1.8.3 with pudding from the pudding/unlocker section below."
Then shortly after is says "Disclaimer: Tested on 1.8.3 and 2.3.4 using sbf_flash and RSDLITE 5.3.1 or higher, usual warnings being responsible for your own actions yada yada"
So I dont really know if it works or not on the newer atrix's. I dont want to brick a brand new phone and I would just like to see that some one else has done it recently. So yes my eyes are open and search did work for me if you did not see the 2 other threads I mentioned. I just want something up to date, not from early 2011. If it can be confirmed that this works or If you know someone who has unlocked it recently, that would be great to hear from them.
Thanks for posting the link to that thread anyways though. Much apprieciated!
Can anyone tell me if the IHOP method to unlock bootloader will work with my phone?? I cant post in that thread because I do not have enough posts. Here are my specs so I could get some help with which patch to use with RSDlite.
System version: 45.31.0.MB860.AsiaRetail.en.03
Model number: MB860
Android version: 2.3.4
Baseband version: N_01.100.00R
Kernel version: 2.6.32.9
[email protected] #3
APflex version: GAS_ASIA_USAOLYGBSEART_P011
GAS_ASIA_USAOLYGBSEART_A003
GAS_ASIA_USAOLEMSEARET_M001
Build number: 4.5.2A-74_OLE-31
Something else I want to note is that it was bought on ebay as unlocked so I am assuming that is the radio. When I set up the APN for straight talk it did have the choices for AT&T US, AT&T US HSDPA, AT&T US Tether, AT&T US MMS. So this is why I am a little confused/scared as to which piece of pudding to use. It looks easy enough to unlock and clear the caches and flash the ROM I will want to use. Just would like to know which one to use.
Please, please somebody help!!:fingers-crossed:
Thanks you for taking a look to help. Much apprieciated!!!
For a phone with the Asia Retail firmware, you'll want to use RSD Lite to flash the IHOP SBF. Your phone will likely enter a soft brick as stated above, just proceed with the unlock commands in fastboot from the error screen.
Since its an international phone, if you don't load a new ROM soon after unlocking then you'll need to flash the "RAMfix" from the Development section here. Most ROMs have that built in to the kernel, though, so it's not needed if you're going directly to a ROM.
In case you need it in the future, you might want to locate your stock SBF for Asia Retail and keep it on hand. If you see the Atrix Firmware Superthread in the Dev section, find the later Page that has new links to updated download sites. It's a post with a link to all Gingerbread firmwares and a link to all Froyo firmwares. Yours will have "searet" in the name. Make sure it's the same version, 2.3.4. Flashing anything older will brick you.
Good luck!
Sent from my MB865 Atrix 2 via Tapatalk 2
das8nt said:
For a phone with the Asia Retail firmware, you'll want to use RSD Lite to flash the IHOP SBF. Your phone will likely enter a soft brick as stated above, just proceed with the unlock commands in fastboot from the error screen.
Since its an international phone, if you don't load a new ROM soon after unlocking then you'll need to flash the "RAMfix" from the Development section here. Most ROMs have that built in to the kernel, though, so it's not needed if you're going directly to a ROM.
In case you need it in the future, you might want to locate your stock SBF for Asia Retail and keep it on hand. If you see the Atrix Firmware Superthread in the Dev section, find the later Page that has new links to updated download sites. It's a post with a link to all Gingerbread firmwares and a link to all Froyo firmwares. Yours will have "searet" in the name. Make sure it's the same version, 2.3.4. Flashing anything older will brick you.
Good luck!
Sent from my MB865 Atrix 2 via Tapatalk 2
Click to expand...
Click to collapse
Awesome das8nt!! wish I could thank you more than once!!! I was just confused because it said asia in some spots but the APN's were for AT&T.
Oregon2 said:
Awesome das8nt!! wish I could thank you more than once!!! I was just confused because it said asia in some spots but the APN's were for AT&T.
Click to expand...
Click to collapse
Quite welcome.
APNs are usually set by your SIM, if it's provisioned properly and the phone supports it.
Sent from my MB865 Atrix 2 via Tapatalk 2
Good to know About the APNs. Just to let you know I unlocked, rooted, and flashed the ROM the day you first replied. So I've been running with a new ROM for 3 days and the battery life is great!!
If anyone out there has installed the Neutrino ROM, I have one more question. On the Neurino ROM page it say to do these 2 steps:
"Then, after booting, click on script manager, navigate to /system/etc and run NitroCharger.sh as ROOT and at BOOT!
It is also HIGHLY recommended to download the GPS Mod found in #2. Then you're done."
I tried flashing the GPS mod but I keep gettng an error. Then on my first boot I tried going to /system/etc and from there I do not know where to locate NitroCharger to run it for either. Any help on these two issues would be great!! Also another thanks for everyone for taking a look and helping.
I would post in that thread but I still dont have enought posts.
You really need to reread the original Neutrino thread, since all of this has been answered countless times.
YOU DO NOT FLASH THE GPS MOD DIRECTLY. Open the ZIP and read the instructions.
NitroCharger is only available as an OTA update, but you might reconsider if you really want it since it's been known to cause issues.
Again, I know the thread is very large, but whatever questions or issues you might have, it's very likely answered there already.
Thanks you for just answering, even though you think I should just reread the thread. That answered my questions very fast. I will just not run Nitrocharger, I thought it may casue problems if I could not get it to run, instead you said it is the opposite. As for the GPS mod I just did open up the .zip and read the readme. I pulled out the United_States.zip
Can I just use CWM recovery to flash the US.zip now or do I have to clear all my caches and the likes beforehand?
I know your very busy and I apprieciate the time you take to just look at it.
I have just started my own business and it is going great!! but I have been working 14+ hour days with usually 9 hours hour doing very hard physical labor 6 days a week!! I need to hire more employees soon, lol. I read the whole IHOP thread from front to back and the Neutrino thread but I was very exhasted and stayed up until 330 in the morning doing it!! So again I thank you for taking your time I appriciate it very MUCH that you are helping me to have a fun android experiance and also to learn something new to me!!
Yes, you can just go ahead and flash United_States.zip. No need to clear anything.
Awesome your the MAN!! Thanks again :laugh: :good:
I have a Samsung Exhibit 4G (the older model - I have a SGH-T759, NOT the SGH-T679). I have successfully rooted it via the old zergRush exploit (and have a working busybox & SuperSU installed), so now I'm looking for a stable ROM for this device.
So far I've been Googling around and I can't seem to find a copy of CWM or an Android ROM for this device; this is probably some combination of me not knowing where to look, as well as the fact that Samsung decided to create two incompatible phones with the same name not helping at all.
I don't particularly care about having CWM, other than it seems to be the easiest method for flashing ROMs - if there's some other method I don't mind going that route instead. I also don't care that much about having the very latest version of Android - ICS would be just fine, if a stable JB ROM doesn't exist for this device.
Thanks in advance for any advice!
AreaRom
CmdrMoozy said:
I have a Samsung Exhibit 4G (the older model - I have a SGH-T759, NOT the SGH-T679). I have successfully rooted it via the old zergRush exploit (and have a working busybox & SuperSU installed), so now I'm looking for a stable ROM for this device.
So far I've been Googling around and I can't seem to find a copy of CWM or an Android ROM for this device; this is probably some combination of me not knowing where to look, as well as the fact that Samsung decided to create two incompatible phones with the same name not helping at all.
I don't particularly care about having CWM, other than it seems to be the easiest method for flashing ROMs - if there's some other method I don't mind going that route instead. I also don't care that much about having the very latest version of Android - ICS would be just fine, if a stable JB ROM doesn't exist for this device.
Thanks in advance for any advice!
Click to expand...
Click to collapse
As far as I know there is no CWM for this phone. There is a "custom" GB rom (AreaRom V1) from another forum. Enough googleing and you can find it pretty easy. You will need to use Odin to "flash" rom to this device or hemdal (may be spelled wrong). I'm really sad there isn't a lot of development for this phone, it's pretty solid as far as phones go.
I just bout the 759 model, it will be here tomorrow! I didn't know that there were two models of the Exhibit! Does this mean I won't be able to successfully follow the upgrade procedures in the wiki since they are for the 679??
dax702 said:
I just bout the 759 model, it will be here tomorrow! I didn't know that there were two models of the Exhibit! Does this mean I won't be able to successfully follow the upgrade procedures in the wiki since they are for the 679??
Click to expand...
Click to collapse
Indeed. The Exhibit II is the Samsung Galaxy Exhibit 4G. It gets confusing as the original Exhibit seems to have just gotten skipped over, which is sad as it is pretty full featured as far as affordable smart phones go.
Well, when I discovered this, I immediately ordered the correct model off eBay and as soon as the old model arrived, I sent it right back to the seller. The new one should be here today. Now I'm trying to find detailed instructions for this ROM flashing procedure as I've never done it before and don't want to screw it up. Do you know of any detailed instructions available online that don't leave anything to guess? I'm good at following instructions if they're complete.
dax702 said:
Well, when I discovered this, I immediately ordered the correct model off eBay and as soon as the old model arrived, I sent it right back to the seller. The new one should be here today. Now I'm trying to find detailed instructions for this ROM flashing procedure as I've never done it before and don't want to screw it up. Do you know of any detailed instructions available online that don't leave anything to guess? I'm good at following instructions if they're complete.
Click to expand...
Click to collapse
Of the to of my head I don't as I don't have this phone. Usually it involves installing clockworkmod recovery via Samsung Kies. Then downloading the ROM you want and installing via CWM. Check in the "general" forum... There are usually a few guides to rooting, CWM, and custom ROM installation.
Thanks, I am reading about it now. When they say "flash clockworkmod" does that simply mean to install it?
dax702 said:
Thanks, I am reading about it now. When they say "flash clockworkmod" does that simply mean to install it?
Click to expand...
Click to collapse
Yes, flash = Install.
hi everyone !
I'm a noob here, at XDA
I'm in a trouble, please help me to get out of this =(
but before posting my real problem (may be I will resolve it my self after getting the answer), I want to know:
how can I select the correct ROM for my HTC Amaze 4G ?
actually my phone has no firmware right now, I wipe / format all, accidentally without any backup.
now I have no idea about ROM. There are many:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
[email protected] said:
hi everyone !
I'm a noob here, at XDA
I'm in a trouble, please help me to get out of this =(
but before posting my real problem (may be I will resolve it my self after getting the answer), I want to know:
how can I select the correct ROM for my HTC Amaze 4G ?
actually my phone has no firmware right now, I wipe / format all, accidentally without any backup.
now I have no idea about ROM. There are many:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
Click to expand...
Click to collapse
The Wiki article is a good place to start, however, it isn't up to date. Select any of the stock ICS based ROMs if you want full functionality as these are the only ROMs where everything works correctly. There are many ICS ROMs both themed and stock Sense available. If you can live without WiFi tethering and some Bluetooth functionality there are several JB based AOSP based ROMs that are otherwise stable and work well. So far all of the KitKat builds have camera exposure issues in addition to the same problems as the JB ROMs. They are more in flux and under heavy development.
It's against the rules of the board to recommend a specific ROM, so you'll have to try for yourself to see what fits your needs and tastes.
However before proceeding you should look over the various threads that are pinned to the top of the different forums. There you will find tons of useful information that will save you trouble later. Remember that if you're coming from any ROM before ICS that you need to first flash a stock ICS factory image so you can install the proper radio baseband otherwise it won't work. None of the after-market ROMs have radios in them. Once an ICS ROM has been flashed you can install other ROMs since all of the later ones use ICS radio basebands.
Edit: One more thing that will help guide you in making your decision. Look at the Dev threads for the ROMs that you're interested in. Usually somewhere in the first or second post the author of the ROM will list the known bugs and issues associated with their ROM, and in the case of ROMs undergoing heavy development they will also list what they know is working well.
Good luck and welcome to the board
Odysseus1962 said:
The Wiki article is a good place to start, however, it isn't up to date. Select any of the stock ICS based ROMs if you want full functionality as these are the only ROMs where everything works correctly. There are many ICS ROMs both themed and stock Sense available. If you can live without WiFi tethering and some Bluetooth functionality there are several JB based AOSP based ROMs that are otherwise stable and work well. So far all of the KitKat builds have camera exposure issues in addition to the same problems as the JB ROMs. They are more in flux and under heavy development.
It's against the rules of the board to recommend a specific ROM, so you'll have to try for yourself to see what fits your needs and tastes.
However before proceeding you should look over the various threads that are pinned to the top of the different forums. There you will find tons of useful information that will save you trouble later. Remember that if you're coming from any ROM before ICS that you need to first flash a stock ICS factory image so you can install the proper radio baseband otherwise it won't work. None of the after-market ROMs have radios in them. Once an ICS ROM has been flashed you can install other ROMs since all of the later ones use ICS radio basebands.
Good luck and welcome to the board.
Click to expand...
Click to collapse
Thank You very much
here is the abstract of what I understand:
I can select any of the stock ICS based ROMs
I'm coming from a ROM before ICS (it was GB) so I need to first flash a stock ICS factory image
Then I will be able to install the proper radio baseband
Once ICS ROM has been flashed I can install other ROMs
Now the new questions are popping up (respectively)
there are many vendors before selecting an ICS stock ROM (Mobilicity, Telus, T-Mobile etc.)
is it safe to select any of them ? (without knowing your phone's vendor)
what is 'stock ICS factory image' ? Can you please mention a link to download it or a guide to flash
what is 'proper' radio baseband ? (mine was 1.13.550L.13DC_30.69b.550L.101D)
How can I change / update to a proper baseband ? Can you please mention a link here too, (if necessary)
Thank You in Advance
[email protected] said:
Thank You very much
here is the abstract of what I understand:
I can select any of the stock ICS based ROMs
I'm coming from a ROM before ICS (it was GB) so I need to first flash a stock ICS factory image
Then I will be able to install the proper radio baseband
Once ICS ROM has been flashed I can install other ROMs
Now the new questions are popping up (respectively)
there are many vendors before selecting an ICS stock ROM (Mobilicity, Telus, T-Mobile etc.)
is it safe to select any of them ? (without knowing your phone's vendor)
what is 'stock ICS factory image' ? Can you please mention a link to download it or a guide to flash
what is 'proper' radio baseband ? (mine was 1.13.550L.13DC_30.69b.550L.101D)
How can I change / update to a proper baseband ? Can you please mention a link here too, (if necessary)
Thank You in Advance
Click to expand...
Click to collapse
Since you're coming from Gingerbread I assume you have an Asian or unbranded Amaze. You need to follow the directions for those models. It requires you to attain s-off prior to flashing an ICS ROM. There are posts explaining the hack you need to do to get s-off. Once s-off you next need to superCID. Once both s-off and superCID have been attained you can flash an ICS ROM. You need to go through this procedure because the stock ROMs have carrier identification codes (CID) which prevent ROMs from one carrier running on another carrier's device. These hacks get around it.
At this point most folks flash the T-Mobile ICS ROM since it's fairly recent and the basis for most of the ICS modified ROMs. Once you've got an ICS radio installed you can then flash any ROM you'd like.
Again read through the pinned threads and familiarize yourself with the procedure. Failure to follow the directions correctly can result in a bricked phone. Then your next post will be in the Amaze unbricking project thread asking for desperate help.
I'm s-on. I didn't need s-off since I'm a T-Mobile customer and already had ICS before I started flashing ROMs. So I'm not going to be much help with the s-off procedure. Like I said, read through the appropriate threads and familiarize yourself on the procedure so you can move forward. For now, until you get s-off it's best to flash back to whatever stock ROM you had because there isn't much you can do until you get s-off and I'm sure you still want to have use of your handset.
I hope this helps.
Good luck
I followed this method, yesterday and got my phone back (as it was before)
aj_2423 said:
If you have already made the mistake of unlocking and trying to flash an ICS rom while still on GB, you can do the following to get back to GB and have a working device.
ATTENTION - Before continuing past this point, You must first have 4ext installed as your recovery if the device is S-Off.(you can use hasoons AIO toolkit to do this.) Once you have 4ext flashed, boot into recovery and in the settings Enable Smartflash
1) Download this ruby_unsigned_021812_031444.zip GB rom
2) Next, Place the the downloaded file on your sd card.
3) Now Boot into 4ext recovery (battery pull, then start phone while holding down the power+VolumeDown buttons simultaneously).
4) Once in recovery, go to the Wipe/Format section and select "Format all partitions except SDcard"
5) Finally, after formating completes, verify that you have SmartFlash enabled & then flash the Rom you just downloaded from above..
Once this is complete, you should once again have a working device.
Please use this thread for any related questions/comments you may have so we can try and keep the forums a little more organized and clean. THANK YOU
*********************&*******************
Hopefully this will help reduce the duplicate threads
Click to expand...
Click to collapse
[email protected] said:
I followed this method, yesterday and got my phone back (as it was before)
Click to expand...
Click to collapse
Looks like @Odysseus1962 has things under control here, but I'll still add my two cents, if he doesn't mind
I read through this post and I must say, I'm glad that you got your phone working again, even though it's only GB still.
Having said that I could safely assume that you have rooted your phone and installed 4ext recovery, and I'm hoping that you've performed S-OFF and SuperCID your device.
If you have done that, then I highly recommend you to the T-Mobile stock RUU before you even attempt any custom roms. Personally, I enjoyed the T-Mobile stock experience (well, I debloated it myself using Titanium Backup, removing a lot of the useless T-Mobile stuff ie; T-mobile voicemail, assist, 411 etc)
I actually used that rom for a while. Battery life was nice, the rom itself was really well done, as expected.
But this is all up to you, many of the custom roms here have so much more features than the T-Mobile, with a much smoother experience too.
But like Odysseus said, there are some flaws with the roms. Some have WiFi tether issues, bluetooth, in call volume and codec issues.
It's really a personal decision where you can settle after experiencing the roms first hand. Everybody uses their device differently, so you'll have to test the roms to find which one suits your needs and standards.
Darin_Ram said:
Looks like @Odysseus1962 has things under control here, but I'll still add my two cents, if he doesn't mind
I read through this post and I must say, I'm glad that you got your phone working again, even though it's only GB still.
Having said that I could safely assume that you have rooted your phone and installed 4ext recovery, and I'm hoping that you've performed S-OFF and SuperCID your device.
If you have done that, then I highly recommend you to the T-Mobile stock RUU before you even attempt any custom roms. Personally, I enjoyed the T-Mobile stock experience (well, I debloated it myself using Titanium Backup, removing a lot of the useless T-Mobile stuff ie; T-mobile voicemail, assist, 411 etc)
I actually used that rom for a while. Battery life was nice, the rom itself was really well done, as expected.
But this is all up to you, many of the custom roms here have so much more features than the T-Mobile, with a much smoother experience too.
But like Odysseus said, there are some flaws with the roms. Some have WiFi tether issues, bluetooth, in call volume and codec issues.
It's really a personal decision where you can settle after experiencing the roms first hand. Everybody uses their device differently, so you'll have to test the roms to find which one suits your needs and standards.
Click to expand...
Click to collapse
Thank You @Odysseus1962 and @Darin_Ram
1. I followed @aj_2423
Thread : [GUIDE][GBtoICS]FOR INTERNATIONAL/ASIAN VERSION/UNBRANDED Amaze Owners-Read1st
2. 2nd Post of this Thread helped me to get back my phone in working state.
3. but as you know, this was not my aim. I had done this just to make sure that my phone is alive
4. to upgrade from GB to ICS, I carefully read and followed the 1st Post of same thread and last night I was successful to do so
Now I have perfectly working HTC Amaze 4G with ICS :victory:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Just to share my experience :
i - the 'Wire Trick' was the most annoying thing, I tried several times to do it accurate.
ii - Step 3 of this process was to 'Unlock bootloader', I had done that. But after S-OFF, during the next steps, I noticed that bootloader is LOCKED again. I don't know if it's normal. Anyhow it didn't cause any problem for me.
Happy Ending :highfive:
[email protected] said:
Thank You @Odysseus1962 and @Darin_Ram
1. I followed @aj_2423
Thread : [GUIDE][GBtoICS]FOR INTERNATIONAL/ASIAN VERSION/UNBRANDED Amaze Owners-Read1st
2. 2nd Post of this Thread helped me to get back my phone in working state.
3. but as you know, this was not my aim. I had done this just to make sure that my phone is alive
4. to upgrade from GB to ICS, I carefully read and followed the 1st Post of same thread and last night I was successful to do so
Now I have perfectly working HTC Amaze 4G with ICS :victory:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Just to share my experience :
i - the 'Wire Trick' was the most annoying thing, I tried several times to do it accurate.
ii - Step 3 of this process was to 'Unlock bootloader', I had done that. But after S-OFF, during the next steps, I noticed that bootloader is LOCKED again. I don't know if it's normal. Anyhow it didn't cause any problem for me.
Happy Ending :highfive:
Click to expand...
Click to collapse
Lol Glad to hear that your phone is up and running with ICS :highfive:
About your concerns.. I'm surprise the wire trick gave you some trouble. I don't know about anybody else but I'm assuming it was sort of easy since I got it on my second try.
And yes, the bootloader re-locks itself after you flash the ICS T-Mobile RUU. That's why you're supposed to keep the code saved in a notepad file on your computer
I have stock rom from nandroid backup that i've downloaded. android 4.4.2.
So the question goes like that, AT&T release the OTA 4.4.4 yet?
If so, why can't i see the OTA?
I have stock root does it a problem ? should i remove root? if so how i do that?
I need to make stock bootloader and all that stuff?
Last question, when AT&T will release the android lolipop 5 ?
ben33891471 said:
I have stock rom from nandroid backup that i've downloaded. android 4.4.2.
So the question goes like that, AT&T release the OTA 4.4.4 yet?
If so, why can't i see the OTA?
I have stock root does it a problem ? should i remove root? if so how i do that?
I need to make stock bootloader and all that stuff?
Last question, when AT&T will release the android lolipop 5 ?
Click to expand...
Click to collapse
I hesitate to answer this because so much is already in posts and threads....
1. AT&T has released the 4.4.4 OTA already
2. I don't know why you can't see it. Are you using an AT&T SIM card? Are you logged onto the AT&T network?
3. Root doesn't matter, but a stock recovery is required to actually install the update (but not to download it)
4. Stock bootloader isn't required. I don't know if it needs to be locked or not (probably not - just guessing).
5. Please contact AT&T for the answer to your version 5 update question.
DanGeorges said:
I hesitate to answer this because so much is already in posts and threads....
1. AT&T has released the 4.4.4 OTA already
2. I don't know why you can't see it. Are you using an AT&T SIM card? Are you logged onto the AT&T network?
3. Root doesn't matter, but a stock recovery is required to actually install the update (but not to download it)
4. Stock bootloader isn't required. I don't know if it needs to be locked or not (probably not - just guessing).
5. Please contact AT&T for the answer to your version 5 update question.
Click to expand...
Click to collapse
about 2, i dont think..
about 3, how i flash or whatever it called, the stock recovery?
ben33891471 said:
about 2, i dont think..
about 3, how i flash or whatever it called, the stock recovery?
Click to expand...
Click to collapse
If you're not using an AT&T SIM card or on the AT&T network, you will not be able to receive an update from AT&T. I'm not sure how you thought that might happen.
Please search this XDA forum on how to install a recovery (stock or otherwise). There are LOTS of threads on this. And if you don't know what it is, you probably shouldn't be mucking around with your phone yet. Read as much as possible first - If you don't, you'll be asking how to unbrick your phone.
DanGeorges said:
If you're not using an AT&T SIM card or on the AT&T network, you will not be able to receive an update from AT&T. I'm not sure how you thought that might happen.
Please search this XDA forum on how to install a recovery (stock or otherwise). There are LOTS of threads on this. And if you don't know what it is, you probably shouldn't be mucking around with your phone yet. Read as much as possible first - If you don't, you'll be asking how to unbrick your phone.
Click to expand...
Click to collapse
I'm from Israel so i dont think i connected to AT&T network.. My phone is from at&t but my carrer newtork is Orange(Israel)
So that means i can't update my phone ever?
kinda weird, my brother have m8 but T- Mobile and he is already have recived the OTA 4.44 a long time ago.
ben33891471 said:
I'm from Israel so i dont think i connected to AT&T network.. My phone is from at&t but my carrer newtork is Orange(Israel)
So that means i can't update my phone ever?
kinda weird, my brother have m8 but T- Mobile and he is already have recived the OTA 4.44 a long time ago.
Click to expand...
Click to collapse
OK - here's the scoop:
1. If you've put an Orange SIM card into your unlocked HTC One M8 (AT&T branded), it is an Orange device now. AT&T is just a label on the phone (logo on the lower back of the device).
2. If Orange Israel releases an update, you will most likely get it. Both T-Mobile and AT&T released updates about a month ago, which is why your brother got the update on T-Mobile.
3. You can still update your M8 to version 4.4.4 - but you'll need to ensure you have the proper firmware installed or you'll have problems. Version 4.4.4 has a different data structure than 4.4.2.
Again - read up on the general and Q/A threads on this forum. You can get your device updated to whatever version you want, it's just a matter of reading.
DanGeorges said:
OK - here's the scoop:
1. If you've put an Orange SIM card into your unlocked HTC One M8 (AT&T branded), it is an Orange device now. AT&T is just a label on the phone (logo on the lower back of the device).
2. If Orange Israel releases an update, you will most likely get it. Both T-Mobile and AT&T released updates about a month ago, which is why your brother got the update on T-Mobile.
3. You can still update your M8 to version 4.4.4 - but you'll need to ensure you have the proper firmware installed or you'll have problems. Version 4.4.4 has a different data structure than 4.4.2.
Again - read up on the general and Q/A threads on this forum. You can get your device updated to whatever version you want, it's just a matter of reading.
Click to expand...
Click to collapse
That's such a headache .. I'll just stay with the nandrid backup i guess.. i almost bricked my phone a month ago, but fixed it somehow..
This whole thing is complicated.. was so much easier on the galaxy 4 to flash roms and what not..
ben33891471 said:
That's such a headache .. I'll just stay with the nandrid backup i guess.. i almost bricked my phone a month ago, but fixed it somehow..
This whole thing is complicated.. was so much easier on the galaxy 4 to flash roms and what not..
Click to expand...
Click to collapse
Question - is the ROM on your phone from AT&T or from Orange, or was it flashed from some other source? The ROM is specific to a device, not a carrier, so you SHOULD be able to flash the ROM of your choice, as long as it works with the device (but keep in mind the fact that you will need a ROM for the GSM version of the M8, as opposed to, say, a Verizon or Sprint variant).
If it's from AT&T, you may be able to apply the updates from saved OTA file (not sure how to apply, but it can be done).
DanGeorges said:
Question - is the ROM on your phone from AT&T or from Orange, or was it flashed from some other source? The ROM is specific to a device, not a carrier, so you SHOULD be able to flash the ROM of your choice, as long as it works with the device (but keep in mind the fact that you will need a ROM for the GSM version of the M8, as opposed to, say, a Verizon or Sprint variant).
If it's from AT&T, you may be able to apply the updates from saved OTA file (not sure how to apply, but it can be done).
Click to expand...
Click to collapse
This is a nandroid backup and yes this one is AT&T rom.
I want to flash the ViperOne 3.2.1. i've been with 1.7.1 version but didn't really like it. a lot of bugs..
I want something with lollipop 5. and a STRONG battery , of course a smoothly rom with no bugs.
ben33891471 said:
This is a nandroid backup and yes this one is AT&T rom.
I want to flash the ViperOne 3.2.1. i've been with 1.7.1 version but didn't really like it. a lot of bugs..
I want something with lollipop 5. and a STRONG battery , of course a smoothly rom with no bugs.
Click to expand...
Click to collapse
I flashed Viper 3.2.1, and it worked nicely. Make sure to update your firmware before installing.
I also tried an L version 5 ROM, but didn't like the fact that it didn't work with Xposed modules, which I like and use.
DanGeorges said:
OK - here's the scoop:
1. If you've put an Orange SIM card into your unlocked HTC One M8 (AT&T branded), it is an Orange device now. AT&T is just a label on the phone (logo on the lower back of the device).
2. If Orange Israel releases an update, you will most likely get it. Both T-Mobile and AT&T released updates about a month ago, which is why your brother got the update on T-Mobile.
Click to expand...
Click to collapse
These points are not correct. Yes, the phone is being run on the OP's local network Orange (not AT&T). But the phone will only receive and be able to install an Orange OTA if its on Orange software and Orange CID/MID. If its running AT&T software, it will not receive OTA is most foreign countries. AT&T is the oddball here, as most other variants will still update on other networks. AT&T devices must be connected to the AT&T network to get official OTA.
The way to update the device by official means (when not on AT&T's network) would be the AT&T RUU.
---------- Post added at 10:33 AM ---------- Previous post was at 10:26 AM ----------
ben33891471 said:
That's such a headache ...
Click to expand...
Click to collapse
If you don't want such headaches, don't buy carrier branded US devices for use in other countries. I strongly believe this.
ben33891471 said:
I'll just stay with the nandrid backup i guess.. i almost bricked my phone a month ago, but fixed it somehow..
Click to expand...
Click to collapse
You didn't "almost brick" the device. A brick means that you phone is totally inoperable to the point the screen doesn't even power on; and the only way to recover is by opening the phone and JTAG or replacing the mainboard.
You probably just put the phone in a condition where it would not boot; which is a fairly common issue that crops up for just about anyone modding phones, at one time or another. And how to recover from such conditions is pretty basic info; and something anyone who is modding phones should now how to do.
I'm sorry if any of this seems harsh. But I believe the above to be more FACT than opinion, and for your own good. I agree with the former notions that you (and anyone who want to mod the hone) should always research thoroughly and understand before messing with the phone.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
ben33891471 said:
Last question, when AT&T will release the android lolipop 5 ?
Click to expand...
Click to collapse
God knows. There is never any firm release date for AT&T (one of the many reasons to avoid US carrier branded devices if you are in another country). They just released 4.4.4 a couple weeks ago. It was delayed for months due to issues implementing Voice Over LTE. Hopefully, the LP update won't suffer the same length of delay.
redpoint73 said:
These points are not correct. Yes, the phone is being run on the OP's local network Orange (not AT&T). But the phone will only receive and be able to install an Orange OTA if its on Orange software and Orange CID/MID. If its running AT&T software, it will not receive OTA is most foreign countries. AT&T is the oddball here, as most other variants will still update on other networks. AT&T devices must be connected to the AT&T network to get official OTA.
The way to update the device by official means (when not on AT&T's network) would be the AT&T RUU.
---------- Post added at 10:33 AM ---------- Previous post was at 10:26 AM ----------
If you don't want such headaches, don't buy carrier branded US devices for use in other countries. I strongly believe this.
You didn't "almost brick" the device. A brick means that you phone is totally inoperable to the point the screen doesn't even power on; and the only way to recover is by opening the phone and JTAG or replacing the mainboard.
You probably just put the phone in a condition where it would not boot; which is a fairly common issue that crops up for just about anyone modding phones, at one time or another. And how to recover from such conditions is pretty basic info; and something anyone who is modding phones should now how to do.
I'm sorry if any of this seems harsh. But I believe the above to be more FACT than opinion, and for your own good. I agree with the former notions that you (and anyone who want to mod the hone) should always research thoroughly and understand before messing with the phone.
Click to expand...
Click to collapse
Correct. I updated my responses - I thought that the OP had an Orange M8 ROM installed.
ben33891471 said:
I want something with lollipop 5. and a STRONG battery , of course a smoothly rom with no bugs.
Click to expand...
Click to collapse
Since there is no LP stock ROM or "official" firmware for AT&T, you won't be able to run Sense LP at this time unless you have s-off (and can then update the firmware by "unofficial" means).
You can however flash a Lollipop GPE or AOSP ROM, but you will still likely need to update to at least Android 4.4.4 to get a firmware and/or hboot that supports the specific ROM.
Battery and performance are always going to vary from one user to the next. Variables such as how one uses the phones; and especially your local reception will greatly impact battery life. There is never going to be one ROM that has "strong" battery for every user in every situation. Your best bet is to try the ROMs out, and see what works best for your situation.
DanGeorges said:
I flashed Viper 3.2.1, and it worked nicely. Make sure to update your firmware before installing.
I also tried an L version 5 ROM, but didn't like the fact that it didn't work with Xposed modules, which I like and use.
Click to expand...
Click to collapse
Alright , there is a nandroid backup 4.4.4? i think this is the only way i can update my phone, if this possible.
redpoint73 said:
These points are not correct. Yes, the phone is being run on the OP's local network Orange (not AT&T). But the phone will only receive and be able to install an Orange OTA if its on Orange software and Orange CID/MID. If its running AT&T software, it will not receive OTA is most foreign countries. AT&T is the oddball here, as most other variants will still update on other networks. AT&T devices must be connected to the AT&T network to get official OTA.
The way to update the device by official means (when not on AT&T's network) would be the AT&T RUU.
---------- Post added at 10:33 AM ---------- Previous post was at 10:26 AM ----------
If you don't want such headaches, don't buy carrier branded US devices for use in other countries. I strongly believe this.
You didn't "almost brick" the device. A brick means that you phone is totally inoperable to the point the screen doesn't even power on; and the only way to recover is by opening the phone and JTAG or replacing the mainboard.
You probably just put the phone in a condition where it would not boot; which is a fairly common issue that crops up for just about anyone modding phones, at one time or another. And how to recover from such conditions is pretty basic info; and something anyone who is modding phones should now how to do.
I'm sorry if any of this seems harsh. But I believe the above to be more FACT than opinion, and for your own good. I agree with the former notions that you (and anyone who want to mod the hone) should always research thoroughly and understand before messing with the phone.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
God knows. There is never any firm release date for AT&T (one of the many reasons to avoid US carrier branded devices if you are in another country). They just released 4.4.4 a couple weeks ago. It was delayed for months due to issues implementing Voice Over LTE. Hopefully, the LP update won't suffer the same length of delay.
Click to expand...
Click to collapse
I don't know what RUU means.. There is a simple way to update to 4.4.4 ?
redpoint73 said:
Since there is no LP stock ROM or "official" firmware for AT&T, you won't be able to run Sense LP at this time unless you have s-off (and can then update the firmware by "unofficial" means).
You can however flash a Lollipop GPE or AOSP ROM, but you will still likely need to update to at least Android 4.4.4 to get a firmware and/or hboot that supports the specific ROM.
Battery and performance are always going to vary from one user to the next. Variables such as how one uses the phones; and especially your local reception will greatly impact battery life. There is never going to be one ROM that has "strong" battery for every user in every situation. Your best bet is to try the ROMs out, and see what works best for your situation.
Click to expand...
Click to collapse
ben33891471 said:
I don't know what RUU means.. There is a simple way to update to 4.4.4 ?
Click to expand...
Click to collapse
RUU = ROM update utility. Its an official .exe (Windows PC required) that completely re-images the phone, including stock ROM, stock recovery and all firmware.
If this is the path you choose, its pretty simple:
Download the RUU to your PC.
Backup any personal data, as the phone will be wiped by RUU.
Connect the phone to PC in fastboot mode.
Relock the bootloader with command fastboot oem lock (not required with s-off).
Simply run the RUU .exe, and it will do the rest (you click a few confirmations dialogs, but that is it).
RUU and more detailed instructions at the following link, under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
As RUU installs stock recovery, you will need to unlock the bootloader again, and flash custom recovery again if you want to root or flash custom ROMs.
redpoint73 said:
RUU = ROM update utility. Its an official .exe (Windows PC required) that completely re-images the phone, including stock ROM, stock recovery and all firmware.
If this is the path you choose, its pretty simple:
Download the RUU to your PC.
Backup any personal data, as the phone will be wiped by RUU.
Connect the phone to PC in fastboot mode.
Relock the bootloader with command fastboot oem lock (not required with s-off).
Simply run the RUU .exe, and it will do the rest (you click a few confirmations dialogs, but that is it).
RUU and more detailed instructions at the following link, under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
As RUU installs stock recovery, you will need to unlock the bootloader again, and flash custom recovery again if you want to root or flash custom ROMs.
Click to expand...
Click to collapse
Which ROM do you think the best. I'm thinking about ViperOne 3.2.1 , Android Revolution hd 34.0 or CM 12 .
I really like the design of the CM12 but i heard that the boomsound ain't works, is that true? that's means the quality of the speakers will be very bad?
ben33891471 said:
Which ROM do you think the best. I'm thinking about ViperOne 3.2.1 , Android Revolution hd 34.0 or CM 12 .
I really like the design of the CM12 but i heard that the boomsound ain't works, is that true? that's means the quality of the speakers will be very bad?
Click to expand...
Click to collapse
I don't believe in recommending "best" ROMs. What's best for me, may no be the best for you. Especially since our network requirements are very different. And the choice of ROM is also largely a matter of personal preference and taste. In fact, until recently the XDA rules did not allow posting of "best ROM" threads as the discussions are largely irrelevant, and just resulted in fanboy pissing contests.
You really can't go wrong with any of the mentioned ROMs.
Although be aware that current ARHD is based on Android 5.0. So you need to update to Lollipop firmware or else suffer major bugs (broken WiFi is the most common). For the AT&T version of this phone, you can only update to LP firmware if you have s-off (until a LP is released by AT&T, for you by RUU).
Yes, any features that require Sense framework will not be present on CM12, including Boomsound and dual camera. Whether the sound is "bad" or not, I can't say. I'm not a CM12 user. But remember that Boomsound is just a software enhancement. The high quality of the speakers (for a smartphone) is largely a factor in the sound quality. If you like CM12 design, why not flash it (once on the proper hboot) and see for yourself what you think?
redpoint73 said:
I don't believe in recommending "best" ROMs. What's best for me, may no be the best for you. Especially since our network requirements are very different. And the choice of ROM is also largely a matter of personal preference and taste. In fact, until recently the XDA rules did not allow posting of "best ROM" threads as the discussions are largely irrelevant, and just resulted in fanboy pissing contests.
You really can't go wrong with any of the mentioned ROMs.
Although be aware that current ARHD is based on Android 5.0. So you need to update to Lollipop firmware or else suffer major bugs (broken WiFi is the most common). For the AT&T version of this phone, you can only update to LP firmware if you have s-off (until a LP is released by AT&T, for you by RUU).
Yes, any features that require Sense framework will not be present on CM12, including Boomsound and dual camera. Whether the sound is "bad" or not, I can't say. I'm not a CM12 user. But remember that Boomsound is just a software enhancement. The high quality of the speakers (for a smartphone) is largely a factor in the sound quality. If you like CM12 design, why not flash it (once on the proper hboot) and see for yourself what you think?
Click to expand...
Click to collapse
The RUU file isn't open. I boot into bootloader and type the command but then this says something failed and reboot my device. Then i boot into fastboot again and i saw its says relocked so i guess that's ok.
Fine, tried to plug into my PC while the phone is awake and open, the file can't seems to open, not even when i plug it while im in the bootloader.
did i do something wrong?
ben33891471 said:
The RUU file isn't open. I boot into bootloader and type the command but then this says something failed and reboot my device. Then i boot into fastboot again and i saw its says relocked so i guess that's ok.
Fine, tried to plug into my PC while the phone is awake and open, the file can't seems to open, not even when i plug it while im in the bootloader.
did i do something wrong?
Click to expand...
Click to collapse
Make sure you have HTC drivers installed on your PC. Phone should be connected in in fastboot mode.
If the RUU application doesn't even open, it doesn't sound like an issue with the phone. Even if there was an issue with the phone (wrong RUU , unlocked bootloader, etc.) the RUU would still open and start to run, but it would just give you an error message telling you what was wrong. Maybe just a bad download, try to download again.
redpoint73 said:
Make sure you have HTC drivers installed on your PC. Phone should be connected in in fastboot mode.
If the RUU application doesn't even open, it doesn't sound like an issue with the phone. Even if there was an issue with the phone (wrong RUU , unlocked bootloader, etc.) the RUU would still open and start to run, but it would just give you an error message telling you what was wrong. Maybe just a bad download, try to download again.
Click to expand...
Click to collapse
Bro, i managed to upgrade to 4.4.4 . I flashed ViperOne 3.2.1 at first, didn't like it, so i tried android revolution hd 34.0 and this ROM is amazing, love the design love it!
Have only 2 problems so far, first, the TV app , just got every 1-2 min a message: TV stopped .. so i kinda deleted this, but fine i can live without it.
But the problem that actually do me a troubles, is the screenshot, when i try to take a shot of my screen it's says. couldn't take a screenshot, not remaining space or program does not support..
Sorry about my English if you can't understand what i say..
Hi,
so I am having issues with the Wifi on my, recently acquired, LG V30.
I have got a strange model, L-01K, from Japanese provider DOCOMO.
I have unrooted / flashed .. currently running Havoc 3.11 on Android 10.
The wifi often loses connection/signal and in order to restore requires a complete device reboot.
Looking for some help.
Regards,
H.
haevaristo said:
Hi,
so I am having issues with the Wifi on my, recently acquired, LG V30.
I have got a strange model, L-01K, from Japanese provider DOCOMO.
I have unrooted / flashed .. currently running Havoc 3.11 on Android 10.
The wifi often loses connection/signal and in order to restore requires a complete device reboot.
Looking for some help.
Regards,
H.
Click to expand...
Click to collapse
Check your network stability? Don't use Havoc?
ldeveraux said:
Check your network stability? Don't use Havoc?
Click to expand...
Click to collapse
Is this a joke ?
Not really a joke... did the phone work fine on a stock ROM? You never told us what you came from.
How did you get to Havoc 10? As far as I've seen, Pie ROMs often have issues after install... I can't imagine 10-roms to be any better. Did you try any of the fixes mentioned in the ROM threads instead of just asking here? Sounds like it's probably ROM specific...
Well, is it my first custom, so I have no past experience and I don't know if this is specific to the ROM or the firmware drivers, or etc... hence I am asking around here for some support.
I assumed it was clear where I cam from, I came from stock. I only had the phone stock for a short period so I do not know if it was better or not before flashing. The phone was trully horrible with all the Japanese software crap on it.
I think I saw somewhere that this phone is known to have crappy drivers from LG.
haevaristo said:
Well, is it my first custom, so I have no past experience and I don't know if this is specific to the ROM or the firmware drivers, or etc... hence I am asking around here for some support.
I assumed it was clear where I cam from, I came from stock. I only had the phone stock for a short period so I do not know if it was better or not before flashing. The phone was trully horrible with all the Japanese software crap on it.
I think I saw somewhere that this phone is known to have crappy drivers from LG.
Click to expand...
Click to collapse
You also don't have a model number I've ever seen before, nor is it mentioned in the WTF thread. We have no clue what you installed here or how you did it, so I would suggest flashing one of the stock ROMs through TWRP if that's your bag. The Havoc ROM used in this forum is v3.9, again don't know how you got 3.11
Perhaps its not 3.11 ... I got it from the V30 Telegram group ... the zip file is "Havoc-OS-v3.11-20201128-joan-Unofficial.zip", I cannot seem to find the running software version, so I dont know how to check ... I am also trying to get some help there but I thought it wouldn't hurt to ask here as well.
are you rooted and or unlocked bootloader?
Also I've never heard of there being an issue with WIFI on this device.
Yes. TWRP installed as well
You say you came from stock, but WHAT stock? Oreo? Pie? US998? Something else? All this matters. You can't just slap a ROM on without having the rest of the stuff prepared on this phone.
As others mentioned, the model number doesn't make sense to us, so it could be some weird stock ROM that is not compatible with Havoc (or other custom ROMs). Even for many of these, you need to start with a known stock ROM, so that the proper blobs (binaries) are present as well as the partition layout in the phone. As you don't seem to know what it was (eg US998 is preferred) then I'd recommend you start there and then move forward. This means Frankensteining to US998, then moving forward.
Of course, given your weird model number, this may not be advised either... but if you want to try that's where I'd start.
OK.
So, phone came with stock Docomo android 8. Dont know too many details as I didnt kept it long.
Then I had some discussions on telegram group, where people advised me to unroot the phone, and install TWRP. It was mostly same as described in the thread for the LGv30 here in the forums.
I had to install a pre 2018 ROM version, using samsungs tools.
I don't recall anymore all the details order i did things from this on, I followed the steps as advised ... but I had to flash a V300 to H930 ROM. I also remember that an important step in the flashing process was not to flash modem, xbl and xbl2. So I did skip those.
Then initially I rooted Revolution Remix android 9.0, from stock android 10.0 ... by mistake, then I reverted back and I installed Havox android 10.0 instead.
The stock filename was "H93020d_00_OPEN_EU_OP_0326.kdz" and "V300_to_H93031a_converter.zip".
Edit: perhaps it wasnt Android 8 but rather 9 as someone corrected, this phone did not shipped with android 8. As mentioned, I did not keep the phone stock for long as it was literally unsuable with all the Japanese software, so I have not paid too much attention.
haevaristo said:
OK.
So, phone came with stock Docomo android 8. Dont know too many details as I didnt kept it long.
Then I had some discussions on telegram group, where people advised me to unroot the phone, and install TWRP. It was mostly same as described in the thread for the LGv30 here in the forums.
I had to install a pre 2018 ROM version, using samsungs tools.
I don't recall anymore all the details order i did things from this on, I followed the steps as advised ... but I had to flash a V300 to H930 ROM. I also remember that an important step in the flashing process was not to flash modem, xbl and xbl2. So I did skip those.
Then initially I rooted Revolution Remix android 9.0, from stock android 10.0 ... by mistake, then I reverted back and I installed Havox android 10.0 instead.
The stock filename was "H93020d_00_OPEN_EU_OP_0326.kdz" and "V300_to_H93031a_converter.zip".
Click to expand...
Click to collapse
You're ostensibly trying to combine 2 tutorials and forums to fix your problem. My guess is that flashing all those random ROMs, unrooting to install TWRP (?!?!), and using a Samsung tool definitely were not the right move. I'd advise against doing anything else unless @ChazzMatt gives his blessing, but he's away for a bit. Either that or ask for your Telegram friends to fix what they broke.
Also, wtf is docomo? The V30 did not come stock with Android 8.
ldeveraux said:
You're ostensibly trying to combine 2 tutorials and forums to fix your problem. My guess is that flashing all those random ROMs, unrooting to install TWRP (?!?!), and using a Samsung tool definitely were not the right move. I'd advise against doing anything else unless @ChazzMatt gives his blessing, but he's away for a bit. Either that or ask for your Telegram friends to fix what they broke.
Also, wtf is docomo? The V30 did not come stock with Android 8.
Click to expand...
Click to collapse
If you had read my earlier posts, I explain who is docomo and why I have such a weird model.
They are not my 'Telegram friends' but a community of people who use the LG V30. From what I gather it seems several of them are very active in ROMs, fixes and also part of the XDA forums here. They continue trying to help me however I though it would not hurt to also ask here in parallel ... it is also far easier for someone who later may face the same issues, to benefit from the solution if they can find this thread. Perhaps it was a mistake, this reminds me why I dont really miss much using forums ...
Using the LG tool was definitely the right move as written everywhere in the forums here and advised by anyone you ask to directly. As a first step, you need to break the encryption/security on the phone and you can only do that by reverting to an older version, preJuly 2018, where a known exploit exists. And guess what, until you root the phone, you can only do that by using a tool developed by LG.
And yes, I am definitely trying to combine several tutorials as there simply is no single tutorial or source of information.There are also no instructions, or even knowledge, for my model on the forums, and since the information is vague, outdated or incomplete on the different threads, you simply have no choice other than combining it. I followed the instructions as advised by my 'Telegram friends' considering it was clear I had to Frankenstein to something anyhow and the information they gave me, It all made sense, when compared to the forums information and according to the rationalle that they gave. So I took the risk. It worked without me bricking my phone, so I consider that a success.
It was definitely not 'random ROMs', if you go into the XDA section on LGv30 it is clearly explained why you need each of those and how. Its only the specifics, and versions, for my case that is not clear.
Seriously dude, you obviously have not enough knowledge nor interest in helping, .. so why don't you do me a favor, ignore this thread and go spend your time somewhere else and let others who can actually help reply... thanks, seriously!
Oh OK, no problem. Hope you and the other user who bothered replying twice can fix your cockup. With the 0 Likes and 2 weeks on XDA, I'm sure you'll solve it immediately.
... another really helpfull post, you really never disappoint ...
You really need to be far more clear in what you are doing or did. Don't blame the other users for your mistakes, nor should you complain to them when they're trying to help you with limited info. If you want help, you need to give a LOT more info. And you did, indeed, flash multiple different custom ROMs, which is a recipe for trouble.
Your terminology is also confusing, as you keep saying "unroot" and then install TWRP. You need to unlock the bootloader to install TWRP, maybe that's what you mean. Unrooting is a very different operation. You need to be precise in what you are asking for help with, otherwise you'll get bad info from anyone. Know the terms and use them properly, otherwise we can't help you... bad info will always lead to trouble.
Bottom line, as far as I know, there's only one way to do this right on the V30, which we can only assume you have. If you want to proceed, then you need to focus on one process and not try to mix with every other person's idea of what's right. Chazz has been great on this, and has provided detailed info... follow that.
Again, I won't tell you to do this because I don't want you to blame me if you brick the phone. So, if you want to proceed, you do so at your own risk. That said, I would start by getting to US998 stock ROM via KDZ. Follow the Frankenstein thread hereon XDA to see how to get there first. Once there, check to see that the phone operates properly - it should. If it doesn't then stop jumping around and fix that first.
Once all is good on that stock ROM, follow the WTF thread to install TWRP again (KDZ will remove it), with the version mentioned there (there may be newer versions, but you need to stick to what's detailed there to prevent problems, as those are the ones that are tested and known to work). Once you get that done, again, make sure the phone is working properly... then you can consider going to a custom ROM.
If you decide to move ahead, then you need to read the requirements of the custom ROM carefully. Most PIE ROMs, for example, require the PIE blobs, so you need to get to a stock PIE ROM as prescribed before going to a custom ROM. I don't know what the specifics are for 10-ROMs, so you'll have to see what's possible and how it's done based on that ROM's thread.
Well, I am not blaming anyone for my mistakes nor am I complaining to anyone trying to help me, you've been really helpful so far, not only giving ideas on what could be done but as well trying to teach and correct me, and I haven't complained about it.
However, the other guy is literally just patronizing.
Even for me who is new to this, I can clearly see by his comments that he doesn't know what he is talking about, this device in particular, and he even didn't bother to read Chad's thread to try and understand the typical, normal, process.
Just feel free to read again everything that I posted and everything that he posted, 'helping' me, its all registered above.
As for your points you are right, I am trying my best to understand all the details, but as you can notice I have literally just registered here in the forums and this is in fact my first attempt at customizing an android phone ROM.
I have initially, wrongly assumed, that the information I provided was enough and I expected this to be a more common issue that someone with experience could quickly point me to the problem or what I did wrong. And yes, my terminology is wrong, nothing I can do about that at the moment. The posts and information are literally full of jargon, abreviations, code names and sometimes spread over multiple replies or even different threads, this is not for the faint of heart and anyone new will always struggle to understand it all, no matter how smart they are, ... I am literally doing my best to try and catch up as quickly as possible.
So, wherever you read 'unroot' earlier, just replace with "unlock bootloader". As far as I understood it, and as I recall all the things that I have done, I have literally followed the process outlined in Chad's post here in XDA ... I have however frankensteined using the V300 to H930 patch, also according to instructions outlined here (I'm not sure at this moment, if that is also a post by Chad) as per the advice I received in the Telegram group. BTW, I have looked into the telegram group and Chad is also part of it, though he has not been active in the past days, so its not just a random group of people as pointed out earlier.
Anyway .. as far as I was explained, this device requires you to first flash A9 before going straight to A10, otherwise there are some 'blobs' issues with it, i dont really understand the details. During the process of discussion in the chat group, there was some miss understanding and I ended up going straight to A10 and then I installed LineageOS. Later when we noticed this, I tried to correct this by then going back again to A9 and then A10 and then finally I installed Havoc instead of going back to LOS.
So there was some mix up there, and I mentioned this not to blame anyone but just because I thought this could potentially be a source of the problems I am facing and a hint at the potential solution.
Thank you for your suggestion, I am literally half way in the process of sort of doing what you suggest. I am now back to stock A9 and see if the WiFi behaves better. I did flashed stock via TWRP, not KDZ. So I did not went all the back as you suggest. If this proves unsuccessful I might do that.
Not that he/she/they needs my defense, but ldeveraux is a senior member (more-so than me) and has tons of knowledge on this device, in my experience. That's all I want to say about that.
So it sounds like the problem was jumping to A10 from A9. Also, using instructions from one ROM to end up jumping to another. Each ROM has its needs/requirements, so you can't really do that. Also, at least on this phone, going between Android levels is somewhat tricky, so you can't just jump around from what I've read.
Yes, there can be some jargon and such. Chazz's thread (post 193) explains most, if not all, of that, but if you're missing something I strongly recommend reading MUCH more, rather than just moving forward. It is a very long thread, but it's very important you read through ALL of it, and understand it before moving forward. Then read it again. Don't read it on a phone/device - use a computer because browsers and apps have a bad habit of truncating the message. These are Chazz's recommendations as well, for good reason (and also at the top of this thread). I did a TON of reading before I did my phone unlocking/rooting, and with that thread alone, so I have read it MANY times myself (well, at least the older revision when I did my hacking) and I didn't have to ask questions... so I know the answers can be found.
US998 is the best "foundation" to start with for various reasons. Fact is, US998 should work on pretty much any carrier to start with, so it's a great foundation for that reason too. That's why I suggest starting there to be sure you have a good, working basis.
I have read that if you go to A9 or A10, going to another version may require going all the way back to Nougat first. You may need to do that now, if you want to get back to a stable US998 to begin with. The Pie/10 threads probably have info on this... I haven't read them up myself as I don't want to bother. I have stuck with Oreo because it does everything you need anyway... I see no advantage to Pie or 10. I believe Chazz has also stayed on Oreo for this reason.
Senior or no senior, he should just not patronize people. He has clearly the option to ignore if he doesn't feel like helping .. I have even politely asked him to do so ... but instead he decided to come back and patronize further ...
I rest my case...
OK. So, I am still in the process of finalizing everything, but I think it is safe to say that for the L-01K models, the US998 is the safe way to go.
Make a backup of your modem partition, then do the Frankenstein to US998 then once you are done, you can restore you original modem partition and everything should work fine!!