Related
This is my first tutorial for installing Cyanogen Mod 7.2.0 on Live With Walkman WT19i. All credit goes to the developers who made all the following and related tools. I simply put together info from various sources. Admins/moderators are welcome to make any changes.
WARNING: Proceed at your own risk! I am not responsible for bricked phones! You might want to do some more research if you're unsure or don't fully understand anything from below
Requirements: ADB drivers:
http://www.mediafire.com/?6u1zl54w3jnvvax
Fastboot drivers:
win_usb.inf file from http://unlockbootloader.sonymobile.com/instructions
Android SDK(unlocking bootloader):
http://developer.android.com/sdk/
Flashtool(flashing kernel):
http://forum.xda-developers.com/showthread.php?t=1351309
Zergrush(for rooting):
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Clockworkmod Recovery(flashing ROM):
http://www.mediafire.com/?73xv18tht0e8zt4
WT19i_4.0.2.A.0.58 firmware:
NOTE:Enable "USB DEBUGGING" from Menu -> Settings -> Applications -> Development
>Enable "UNKNOWN SOURCES" from Menu -> Settings -> Applications
1) If you're already on official ICS, downgrade to Gingerbread, root Gingerbread and then install other custom ROMs as follows:
2) Flash any Android 2.3.4 firmware (I've tried this method only with the WT19i_4.0.2.A.0.58 firmware though) using Flashtool
->Select Flashmode, Wipe data, Wipe cache
3) Use Zergrush v3 by DoomLord. Works well with 0.58 version
If Superuser app has been installed, rooting is successful.
4) Install ClockWorkMod Recovery 5.0.2.7-nAa-r2(Ported by [email protected])
5) Make a backup in recovery mode. (see below for howto)
6) Install Android SDK Manager
If Google USB Driver is not visible, install Android SDK Tools Rev 20 first, reopen SDK Manager.
Replace android_winusb.inf-file in extras\google\usb_driver folder with the new one on http://unlockbootloader.sonymobile.com/instructions
7) Unlock bootloader officially from: http://unlockbootloader.sonymobile.com/instructions
Instructions on that page are pretty clear.
NOTE: Unlocking the bootloader the official way will void your phone's warranty and DRM keys will be lost. You may want to use the testpoint method as mentioned here:
http://forum.xda-developers.com/showthread.php?t=1285285
8) Download Cyanogenmod 7.2 for WT19i (=coconut version) and place it on your SD card.
9) Ensure that the fastboot drivers are installed.
10) Replace stock kernel : Extract boot.img from the Cyanogenmmod 7.2 ZIP file that you downloaded. Now, in Flashtool, select Flash button > Fastboot mode > Select kernel to Flash > Point it to the boot.img file you extracted. Check log in background window for success.
11) Restart the phone into Recovery. Select Wipe data/factory reset followed by Wipe cache partition followed by Advanced>Wipe Dalvik cache.
Then, install zip from sdcard. Select the coconut 7.2.0. ZIP file you placed here earlier.
Wait for about 5-10 minutes. If you're worried, open Command Prompt, navigate to the fastboot folder and run adb logcat to see what's happening!.
And that's it, you're done!
(If the logging process looks like it's repeating itself for more than 10 minutes, remove battery restart phone, and see if Cyanogenmod now boots up(again, will take ~5 minutes). If it does not still boot(rare case), repeat step 10. Make sure you download the CM ZIP package from your computer)
If you get an 'assert' error (Status 7 error) then, edit the file updater-script in your cm7.2.0 ZIP file\META-INF\com\google\android\. Remove only the first line (ending with a . Now repeat step 10 again.
Extra: To use Google services, you need to flash the gapps.zip similar to the way you did CM 7.2. However, do NOT wipe cache do NOT wipe data or anything! To install, simply boot into recovery, install zip from sd card and choose the gapps ZIP file. Later, Restart phone
How to enter recovery mode on the WT19i:
Turn off phone. Turn it on again. As soon as you see Sony Ericsson logo, keep tapping Volume Down button repeatedly. (Once you are familiar, you'll realize that even 1-2 presses can do the trick)
You do not need to root and install Recovery in the first place, I mean skip steps 3, 4 and 5.
Backup can also be made in the same recovery, which is included with kernel, right before wiping and installing the ROM.
I would just install any Android 2.3.4 firmware, then unlock bootloader, install custom kernel, backup, then wipe, then install.
And if you unlock bootloader officially, then do not forget your phone's warranty will be void and DRM keys lost.
If you succeed with official bootloader unlock, then fastboot drivers are already installed, no need to worry about that
And before ppl go crazy - First boot does take a while, as all the caches need to be recreated.
This tutorial can also work for other custom ROMs aswell, because the process is the same, the only different thing is the kernel and the .zip file.
You do not need to root and install Recovery in the first place, I mean skip steps 3, 4 and 5.
Click to expand...
Click to collapse
Right I meant that to install CWM!
I would just install any Android 2.3.4 firmware, then unlock bootloader, install custom kernel, backup, then wipe, then install.
Click to expand...
Click to collapse
Right except that I had problems with using Zergrush v2 and v4. That's why I thought I'd mention.
If you succeed with official bootloader unlock, then fastboot drivers are already installed, no need to worry about that
Click to expand...
Click to collapse
Yes, but that would entail downloading the android_winusb.inf-file from the mentioned official site, wouldn't it?
And before ppl go crazy - First boot does take a while, as all the caches need to be recreated.
Click to expand...
Click to collapse
Oh, but how common is it for a WT19i to take more than 10 minutes at boot? I did this on two other friends' WT19is; both of them took around 3 minutes. (Obviously i did something wrong the first time on my phone)
Anyhow,thanks for the constructive comments!Editing it accordingly!
blackstallion1234 said:
Right I meant that to install CWM!
Click to expand...
Click to collapse
You do not need CWM in the first place. You can make the full Nandroid backup AFTER flashing custom kernel and BEFORE wiping and installing the ROM.
blackstallion1234 said:
Right except that I had problems with using Zergrush v2 and v4. That's why I thought I'd mention.
Click to expand...
Click to collapse
You don't need root to be honest.
blackstallion1234 said:
Yes, but that would entail downloading the android_winusb.inf-file from the mentioned official site, wouldn't it?
Click to expand...
Click to collapse
What's your point? If you unlock the bootloader official way and it succeeds, you do not have to deal with the drivers anymore, as they have been installed properly and they're working
blackstallion1234 said:
Oh, but how common is it for a WT19i to take more than 10 minutes at boot? I did this on two other friends' WT19is; both of them took around 3 minutes. (Obviously i did something wrong the first time on my phone)
Click to expand...
Click to collapse
I didn't mention about minutes. Some ppl are not aware of that, so it was just a small note for them.
You do not need CWM in the first place. You can make the full Nandroid backup AFTER flashing custom kernel and BEFORE wiping and installing the ROM.
Click to expand...
Click to collapse
Right! The custom kernel would provide a recovery (which isn't present on a stock kernel for our phone), right?
You don't need root to be honest.
Click to expand...
Click to collapse
I shall edit the title to something like 'Root and install CM...' where I express the opinion that rooting does have advantages too!
blackstallion1234 said:
Right! The custom kernel would provide a recovery (which isn't present on a stock kernel for our phone), right?
Click to expand...
Click to collapse
Custom kernels already include recovery and stuff needed for root.
blackstallion1234 said:
I shall edit the title to something like 'Root and install CM...' where I express the opinion that rooting does have advantages too!
Click to expand...
Click to collapse
Rooting is already included in custom ROMs, if not then custom kernel does the job and roots it automatically. You don't need to root it by yourself
didn anyone tried latest nightly
There is a stable rom for LWW listed on the cyanogen mod downloads page. Is it really stable? I'm asking this because when you select 'all' and 'stable' on left panel on that site, there is no stable rom listed for lww! This is very confusing.
hsrbnr said:
There is a stable rom for LWW listed on the cyanogen mod downloads page. Is it really stable? I'm asking this because when you select 'all' and 'stable' on left panel on that site, there is no stable rom listed for lww! This is very confusing.
Click to expand...
Click to collapse
Yes the version of CyanogenMod 7.2.0 listed on their site is stable and indeed the one used in this thread for reference. Click coconut in the left hand pane(that's the codename for LWW) and then selecting stable. (Alternately just go to http://get.cm/?device=coconut&type=stable)
I just installed Cyanogenmod today and it's fantastic!
Do i need to unlock my bootloader?
Hi,
I've rooted my phone (Sony Ericssion Live With Walkman-WT19i) and right now running stock ICS ROM from sony (build: 4.1.B.0.431). Even Clockworld Mod is installed. I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Could You please mail me the steps even to my persoanl mail id [email protected]
sauravsagar said:
Hi,
I've rooted my phone (Sony Ericssion Live With Walkman-WT19i) and right now running stock ICS ROM from sony (build: 4.1.B.0.431). Even Clockworld Mod is installed. I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Could You please mail me the steps even to my persoanl mail id [email protected]
Click to expand...
Click to collapse
You can't install CM with locked bootloader it requires different kernel.
Yes you need to, for CM!
sauravsagar said:
I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Click to expand...
Click to collapse
Yes, most custom ROMs need the bootloader to be unlocked(including CyanogenMod). There are two methods to unlock your bootloader - the test point method and the official method. If you're concerned with your warranty(which may already have been voided), use the Test point method described in the FAQ by Someguyfromhell.
And what ^ said.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Click to expand...
Click to collapse
If only people read FAQs on forums...
thanx a million
thanks a million for the tutorial
this thing rocks
i do love this rom
and most nice thing it dose support ad-hoc
wathbiknight said:
thanks a million for the tutorial
this thing rocks
i do love this rom
and most nice thing it dose support ad-hoc
Click to expand...
Click to collapse
Glad it worked for you! Not to be a thanks-whore, but it's just a click away if I really helped ya!
Cheers!
Might be a foolish question but I flashed some custom firmware on my Samsung Star (not Android) back in the days and only had the English language available instead of the Dutch I wanted.
If I root and install the ROM will everything also be available in English only or will I still be able to use Dutch. Will I lose something?
Another question: If I upgrade to ICS official by Sony trough Sony Bridge on my Mac and ICS is installed on my phone, will I lose data and the root and ROM?
Thanks in advance
zeromusx said:
If I root and install the ROM will everything also be available in English only or will I still be able to use Dutch. Will I lose something?
Click to expand...
Click to collapse
That depends on whether the new ROM you're flashing contains a Dutch language pack. Rooting per se will not modify your data or your language. Also note that flashing can erase your internal memory data.(I have no experience with the Star, however I had a Nokia 3500c. Using the official Nokia app, I upgraded my firmware without any data loss. If you will be using the official Samsung app, you should be safe). That said, make it a point to backup your SMSes, contacts, calendars, notes etc.
Another question: If I upgrade to ICS official by Sony trough Sony Bridge on my Mac and ICS is installed on my phone, will I lose data and the root and ROM?
Click to expand...
Click to collapse
Will I lose root? Yes, you will most likely lose existing root permissions if you already are rooted.
Will I lose data? Unlikely, using Sony Bridge.
Will I lose ROM? Of course, that's the reason you're upgrading to ICS in the first place, isn't it?
Have a look at the following resources and any other places you'll stumble across.
http://forum.xda-developers.com/showthread.php?t=1253127,
http://www.techcredo.com/android/android-rom-and-rooting-dictionary-all-the-funny-words-explained
Good luck!
Installed Cyanogen Mod 9 in my Live with walkman. So far So good!
rolo143 said:
I just installed Cyanogenmod today and it's fantastic!
Click to expand...
Click to collapse
Sir can you show us some screenshots?
thanks again
blackstallion1234 said:
Glad it worked for you! Not to be a thanks-whore, but it's just a click away if I really helped ya!
Cheers!
Click to expand...
Click to collapse
my bad
i thought i did click it earlier , but did today
i'll come back for ROM review later
Just got my sony version - can say this phone is beast mode. There is a pending update to .257 and someone told me that if I update to this, i will be locked out of any ROMs, including any google edition ROM. Can anyone verify this or comment? I have NOT updated to .257 yet.
Thanks in advance.
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
LordManhattan said:
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
Click to expand...
Click to collapse
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
LxMxFxD said:
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
Click to expand...
Click to collapse
Correct. There are currently no way to root 257, so we have to root 532 and update through OTA to keep root on 257.
- Use this tool to root
- Install OTA Root Keeper from the Play Store
- Since you've already received the OTA, you don't need to change the CDA in build.prop (to force the OTA), so...
- Update to 257
- The root app (i'm not sure what app it installs) may be gone, so just install SuperSU from the Play Store if it's not in your app drawer.
And you're done...
... unless you also want to unlock the bootloader:
But let's not get ahead of ourselves. You really want to take a backup of your TA partition. It holds all your unique DRM keys, and X-Reality won't work without it. Once you lose it, you can't get it back, so back it up and upload it to your Dropbox or something. So how do you backup your TA partition?
- Download this tiny tool on your computer and run it.
Are you done? Great! Let's move on to the bootloader:
- Go to Sony's dev site
- Request the unlock key and check your mail.
- Install Flashtool on your computer (follow the guide)
- Click the "lightning" icon
- Follow the steps and enter your unlock key
This may wipe your phone, so backup your stuff
And you're done...
... unless you want to install Recovery and TWRP!
Installing Recovery and TWRP is easy. Just run this tool on your computer.
Now you're all set to flash custom ROMs and all that stuff
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Actually... You only need ADB and Fastboot. You can install this Windows installer which will do all the work for you. I'm sorry if you installed the entire SDK I should have included it in the guide.
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my C6833 using Tapatalk
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
techpal said:
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
Click to expand...
Click to collapse
Thank you very much.
I'm new to Sony flashing. Recently bought a XZU (6833) after learning about GPe release. I havent gotten it as yet but i've spent the last few days reading up on preparing for flashing AOSP roms. I'm still not 100% solid on the steps as information is all over the XZU section, not really organised too well. A lot of the information is out of date and there are many gaps that left me scratching my head...
As far as I can gather, these are the steps a new XZU non GPe edition owner should undergo if they would like to flash GPe roms(or any other)...please correct me if I am wrong.
1) Use flashtool 0.9 to flash older 532 firmware ftf file. (does not require root and can be done on a bone stock device non GPe device regardless of installed firmware version). Link here http://forum.xda-developers.com/showthread.php?t=2463701. Now I know Hong Kong version is ok. 532 is older than 257. 257 cannot be rooted directly hence the need to downgrade first.
2) Root using the Japanese rootkitZ Link: http://forum.xda-developers.com/showthread.php?t=2559009 (I assume this installs Superuser as there is a Superuser APK in the folder)
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
5) Unlock bootloader using Sony method. Link:http://unlockbootloader.sonymobile.com/
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Please can someone edit and/or add details where necessary.
---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------
LxMxFxD said:
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Click to expand...
Click to collapse
To what scripts are you referring? Can you help me by fleshing out my above post?
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
Click to expand...
Click to collapse
If you're not planning on keeping the stock ROM, and you want to jump straight to a custom ROM, then no, it's not necessary to install OTA Root Keeper.
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
Click to expand...
Click to collapse
You don't need to back it up, but it's recommended even if you're going to use custom ROMs. What if you're having some issues with your ZU, and you have to send it in for repairs? Sony will notice if the DRM keys aren't there and they'll then know that you've unlocked the bootloader.
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
Click to expand...
Click to collapse
No, this part isn't necessary if you don't want to.
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
Click to expand...
Click to collapse
Yes, run the bat-file and choose SuperSU in the terminal.
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Click to expand...
Click to collapse
Before you start flashing custom ROMs, make a NAND backup of the stock ROM. This way, if you want to go back, all you have to do is to flash a boot.img and restore it, and you'll end up exactly where you left off (with root).
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
1) How does one know when it is necessary to do any of the above.
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
3) How do you flash the boot.img files? Through cwm or the flashtool?
4) Some gapps come with recovery? Why is that necessary?
A million thanks.
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
LxMxFxD said:
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
Click to expand...
Click to collapse
I see you're being taken care of welcome dude, good choice of phone, it's a screamer!
Sent from my C6833 using XDA Premium 4 mobile app
CptAwesomeTT said:
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Click to expand...
Click to collapse
No problem. I quite enjoy this (yes, i'm weird)
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Click to expand...
Click to collapse
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
Click to expand...
Click to collapse
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
Click to expand...
Click to collapse
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
3) How do you flash the boot.img files? Through cwm or the flashtool?
Click to expand...
Click to collapse
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
4) Some gapps come with recovery? Why is that necessary?
Click to expand...
Click to collapse
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
LordManhattan said:
No problem. I quite enjoy this (yes, i'm weird)
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
Click to expand...
Click to collapse
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
CptAwesomeTT said:
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
Click to expand...
Click to collapse
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
LordManhattan said:
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
Click to expand...
Click to collapse
You've been so helpful. I think that's all my questions until I actually get the device in hand and start working on it. Thanks a mill.
atm the jap root method is the one I'd use. kingo might be safe and vroot might not be...
Use the one in the zip or download the v4 or v5 boot.img
v4 http://forum.xda-developers.com/showthread.php?t=2426739
v5 http://forum.xda-developers.com/showthread.php?t=2426736
if going to omni i would flash the revolution kernel http://forum.xda-developers.com/showthread.php?t=2548092
No problem!
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
Link to .532 is gone. Is there another?
Thanks!
Hi,
Today I purchased a new LS990 which was rooted by stump method. Since SuperSU was not installed I installed it and while updating SU binaries it failed and I lost root. When I open StumpRoot it shows rooted but non of the apps have root access.
I am on LS990ZV4. Even did factory reset and then installed Stump root again but still the same problem.
Is there any method by which I can get the root back. The stock tot file is 2.8 GB and I do not have that much data left.
and since I did factory reset I also lost apn settings and to use data I need shortcut master to work which requires root.
Please help.
Make sure the SuperSU you're flashing is at least 2.40. There's a link in the BarRin thread post #2.
If that doesn't work, then you'll need the tot. Stump only works one time.
But if you have recovery, flashing the correct SuperSU should work.
engine95 said:
Make sure the SuperSU you're flashing is at least 2.40. There's a link in the BarRin thread post #2.
If that doesn't work, then you'll need the tot. Stump only works one time.
But if you have recovery, flashing the correct SuperSU should work.
Click to expand...
Click to collapse
Nope I don't have recovery installed.
Sent from my Nexus 7 using XDA Free mobile app
Well, There is a few things you can do for starters though the root files get installed in the /system/ folder of the phone (the part that a factory reset will not touch). One thing you could do is 100% factory reset here are the steps:
https://www.youtube.com/watch?v=x-cTpsDLNF8
or this one
https://www.youtube.com/watch?v=5zezqSE-uTE
One or the other will work now since you do not have a recovery it will factory reset/hard reset the phone.
If that didn't work you are going to need to use the flash tool and manuly reflash EVERYTHING this should knock out the root. The other method is a little hard please note that I am not responsible if anything happens to the phone by you doing this good luck!!
Heres the link to the other method http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
if you need ANY help just PM me i'll get back to asap also if any of these methods work please donate (as a thank you)
1619415 said:
Well, There is a few things you can do for starters though the root files get installed in the /system/ folder of the phone (the part that a factory reset will not touch). One thing you could do is 100% factory reset here are the steps:
https://www.youtube.com/watch?v=x-cTpsDLNF8
or this one
https://www.youtube.com/watch?v=5zezqSE-uTE
One or the other will work now since you do not have a recovery it will factory reset/hard reset the phone.
If that didn't work you are going to need to use the flash tool and manuly reflash EVERYTHING this should knock out the root. The other method is a little hard please note that I am not responsible if anything happens to the phone by you doing this good luck!!
Heres the link to the other method http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
if you need ANY help just PM me i'll get back to asap also if any of these methods work please donate (as a thank you)
Click to expand...
Click to collapse
Thanks for the reply. The first method didn't worked. Will flash the stock rom now.
Just a few questions (since I am new to G3):
1. After installing stump root and rooting the device. How can I flash recovery? I mean should I use bump method or directly flash the twrp from flashify?
2. Whats the difference between bump twrp and normal twrp?
3. Are there any special roms for bumped twrp or I can flash any rom for LS990?
4. Any other suggestion.
Thanks a lot.!!
Well, for starters DO NOT UPDATE TO ZV6 VIA OTA IT BREAKS ROOT
You can watch/do everything from this video (the info is a little outdated the root takes less then 10 mins now). Heres the link for the video:http://youtu.be/nmeER5btwDo you can download stump root from here:http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Next you will need to install a recovery basicly twrp is probaly the best due to its advanced features so you could dowload that from here: http://techerrata.com/file/twrp2/ls990/openrecovery-twrp-2.8.4.0-ls990.img wait 10 seconds and save it to you phone some where (I recommend the downloads folder)
Next follow this video to install twrp: http://youtu.be/k7a5hnefnnM (you can get flashify for free from the playstore)
----------------------------------------------------------------------------------------------------------------
Well flashing a rom isn't that hard but yes it can ONLY BE FOR THE LS990(SPRINT). You can find a number of roms for this phone under the android develoment and original android develomet pages. You can find the links for these and more here: http://forum.xda-developers.com/sprint-lg-g3
See all roms are pre bumped due to the fact our bootloader is locked so don't rebump. Make sure when you get to flashing roms you download it for only the sprint lg g3. Make sure that the kernels you flash are only for the type of rom your on and make sure you install gapps when need to.
HAPPY FLASHING!
There is a difference between bumped and non bumped for starter since our bootloader is locked we need to "Bump" the recovery image so that way it doesn't need the bootloader. The link I provided has a pre bumped twrp image so you just need to flash with flashify.
All problems solved. Can someone delete this thread?
To get a cm rom booting on vzw firmware heres what you must do.first you must flash us unlocked firmware.look for the thread to do this with.boot the phone.go back and flash dottat 1.85 ruu.let the rom boot.go into twrp do a full wipe format data flash cm rom gapps and your good to.how or why this works i have no idea but with helping my friend @andybones we discovered this is the method for it to work.happy Flashing!!!
Possible to make this in bullet or number/step format and a little more clear and detailed? Pretty sure I get it, but... Thanks!
Detailed Guide
UPDATE: please read this posthttps://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
With thanks to @The Fer-Shiz-Nizzle it was figured out that the key to getting LOS/AOSP ROMs booted was rfg_3.img. Verizon and Sprint don't have one. Instead of having to flash the entire US Unlocked RUU (which flashes the firmware, thus flashing the rfg_3.img) you can now simply 'flash' just the 1 .img
This post has a .zip I made and instructions to flash rfg_3.img
https://forum.xda-developers.com/showpost.php?p=71362727&postcount=32
---UPDATED 6/02/17---
OUTDATED - I SUGGEST FOLLOWING THE ABOVE INSTEAD
Here is a more clear, step-by-step guide.
1) Flash the US Unlocked firmware, modified for Verizon.
1a) Here is the one I personally used, that is already modified.
1b) CAUTION - Flashing this did wipe my internal, so back up everything! Back up everything either way.. even if you're just reading this.
1c) How to flash?
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 1.96.617.20_Modified4VZW.zip
fastboot reboot
2) After you issue the 'fastboot reboot' command you will most likely get stuck on the hTC splash screen as the modified firmware wiped everything, including your system (ROM). If it didn't, not a problem - reboot the device to download mode and continue onto step 3.
2a) Hold Vol+ Vol- and Power buttons until the phone reboots. Keep holding Vol- while letting go of the other buttons. This will bring you to download mode.
3) Now flash the Official Verizon 1.85.605.8 RUU from dottat. Putting you back to a full Verizon variant device. Thread found here.
3a) Let the RUU boot fully up to the stock ROM after the installation finishes.
3b) Make sure to have the AOSP ROM of your choice either on SD-Card or move it now onto the Internal storage.
4) Set your device back to your liking. Splash screen, etc.. but also now you flash TWRP.
4a) If you use multirom, I would still first finish these steps, then you can flash the multirom TWRP and zip. (I am using multirom successfully with both Stock Verizon 1.85.605.8 ROM as primary and CM, AOKP and Resurrection Remix AOSP ROMs as secondaries while being fully Verizon variant device, thanks to this process)
5) Boot to TWRP. Do a full wipe and flash your AOSP ROM.
5a) Note - Most the AOSP ROMs (possibly all that are out?) will boot to the boot animation and then go to a black screen for a minute or so, don't freak. This is normal behavior and will resume back to the boot animation.
6) Enjoy! Hit thanks button if this helped you.
andybones said:
Here is a more clear, step-by-step guide.
1) Flash the US Unlocked firmware, modified for Verizon.
1a) Here is the one I personally used, that is already modified.
1b) CAUTION - Flashing this did wipe my internal, so back up everything! Back up everything either way.. even if you're just reading this.
1c) How to flash?
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 1.96.617.20_Modified4VZW.zip
fastboot reboot
2) After you issue the 'fastboot reboot' command you will most likely get stuck on the hTC splash screen as the modified firmware wiped everything, including your system (ROM). If it didn't, not a problem - reboot the device to download mode and continue onto step 3.
2a) Hold Vol+ Vol- and Power buttons until the phone reboots. Keep holding Vol- while letting go of the other buttons. This will bring you to download mode.
3) Now flash the Official Verizon 1.85.605.8 RUU from dottat. Putting you back to a full Verizon variant device. Thread found here.
3a) Let the RUU boot fully up to the stock ROM after the installation finishes.
3b) Make sure to have the AOSP ROM of your choice either on SD-Card or move it now onto the Internal storage.
4) Set your device back to your liking. Splash screen, etc.. but also now you flash TWRP.
4a) If you use multirom, I would still first finish these steps, then you can flash the multirom TWRP and zip. (I am using multirom successfully with both Stock Verizon 1.85.605.8 ROM as primary and CM, AOKP and Resurrection Remix AOSP ROMs as secondaries while being fully Verizon variant device, thanks to this process)
5) Boot to TWRP. Do a full wipe and flash your AOSP ROM.
5a) Note - Most the AOSP ROMs (possibly all that are out?) will boot to the boot animation and then go to a black screen for a minute or so, don't freak. This is normal behavior and will resume back to the boot animation.
6) Enjoy! Be baffled like myself as to why this worked. Also hit thanks button if this helped you.
Click to expand...
Click to collapse
Thanks man was just about to write it up.you saved me the trouble lol.
hovercraftdriver said:
Possible to make this in bullet or number/step format and a little more clear and detailed? Pretty sure I get it, but... Thanks!
Click to expand...
Click to collapse
Made a more clear guide, if you haven't already got it.
This will serve as a thread for those needing help as well. :good:
gillim74 said:
Thanks man was just about to write it up.you saved me the trouble lol.
Click to expand...
Click to collapse
- team effort. :highfive:
andybones said:
Made a more clear guide, if you haven't already got it.
This will serve as a thread for those needing help as well. :good:
- team effort. :highfive:
Click to expand...
Click to collapse
Indeed
HELP HELP! Guys I'm STUCKED
andybones said:
Here is a more clear, step-by-step guide.
1) Flash the US Unlocked firmware, modified for Verizon.
1a) Here is the one I personally used, that is already modified.
1b) CAUTION - Flashing this did wipe my internal, so back up everything! Back up everything either way.. even if you're just reading this.
1c) How to flash?
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 1.96.617.20_Modified4VZW.zip
fastboot reboot
2) After you issue the 'fastboot reboot' command you will most likely get stuck on the hTC splash screen as the modified firmware wiped everything, including your system (ROM). If it didn't, not a problem - reboot the device to download mode and continue onto step 3.
2a) Hold Vol+ Vol- and Power buttons until the phone reboots. Keep holding Vol- while letting go of the other buttons. This will bring you to download mode.
3) Now flash the Official Verizon 1.85.605.8 RUU from dottat. Putting you back to a full Verizon variant device. Thread found here.
3a) Let the RUU boot fully up to the stock ROM after the installation finishes.
3b) Make sure to have the AOSP ROM of your choice either on SD-Card or move it now onto the Internal storage.
4) Set your device back to your liking. Splash screen, etc.. but also now you flash TWRP.
4a) If you use multirom, I would still first finish these steps, then you can flash the multirom TWRP and zip. (I am using multirom successfully with both Stock Verizon 1.85.605.8 ROM as primary and CM, AOKP and Resurrection Remix AOSP ROMs as secondaries while being fully Verizon variant device, thanks to this process)
5) Boot to TWRP. Do a full wipe and flash your AOSP ROM.
5a) Note - Most the AOSP ROMs (possibly all that are out?) will boot to the boot animation and then go to a black screen for a minute or so, don't freak. This is normal behavior and will resume back to the boot animation.
6) Enjoy! Be baffled like myself as to why this worked. Also hit thanks button if this helped you.
Click to expand...
Click to collapse
Guys I really need help with this thread.
What I expected this was like I will be able to flash the custom rom and change from Verizon variant to run viper, but I ended up with the same stock rom from Verizon.
My verizon htc 10 is still S-ON and Locked Bootloader and according to what I've read threads and forums I found out that I can't unlock the bootloader unless I pay 25$ to use SunShine App. So I was so interested with this thread and I've followed the procedures from step 1 until step 3 when everything back to stock and I realized that I was in the same stock rom as I used to be nothing change or make it worth it after I flashed the RUU.exe something like that.
Then through step 4 I stucked there! I have no idea what to do next maybe I'm just dumb and can't get rid of the problems? Please let me know what to do next :\
sorry for my bad english cuz I'm so hesitating!!!!:crying:
cheakimpor said:
Guys I really need help with this thread.
What I expected this was like I will be able to flash the custom rom and change from Verizon variant to run viper, but I ended up with the same stock rom from Verizon.
My verizon htc 10 is still S-ON and Locked Bootloader and according to what I've read threads and forums I found out that I can't unlock the bootloader unless I pay 25$ to use SunShine App. So I was so interested with this thread and I've followed the procedures from step 1 until step 3 when everything back to stock and I realized that I was in the same stock rom as I used to be nothing change or make it worth it after I flashed the RUU.exe something like that.
Then through step 4 I stucked there! I have no idea what to do next maybe I'm just dumb and can't get rid of the problems? Please let me know what to do next :\
sorry for my bad english cuz I'm so hesitating!!!!:crying:
Click to expand...
Click to collapse
What..?
please read the thread title again. And did you even read my steps outlined before doing them? You're lucky you didn't brick your device being S-ON...
andybones said:
Here is a more clear, step-by-step guide.
1) Flash the US Unlocked firmware, modified for Verizon.
1a) Here is the one I personally used, that is already modified.
1b) CAUTION - Flashing this did wipe my internal, so back up everything! Back up everything either way.. even if you're just reading this.
1c) How to flash?
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 1.96.617.20_Modified4VZW.zip
fastboot reboot
2) After you issue the 'fastboot reboot' command you will most likely get stuck on the hTC splash screen as the modified firmware wiped everything, including your system (ROM). If it didn't, not a problem - reboot the device to download mode and continue onto step 3.
2a) Hold Vol+ Vol- and Power buttons until the phone reboots. Keep holding Vol- while letting go of the other buttons. This will bring you to download mode.
3) Now flash the Official Verizon 1.85.605.8 RUU from dottat. Putting you back to a full Verizon variant device. Thread found here.
3a) Let the RUU boot fully up to the stock ROM after the installation finishes.
3b) Make sure to have the AOSP ROM of your choice either on SD-Card or move it now onto the Internal storage.
4) Set your device back to your liking. Splash screen, etc.. but also now you flash TWRP.
4a) If you use multirom, I would still first finish these steps, then you can flash the multirom TWRP and zip. (I am using multirom successfully with both Stock Verizon 1.85.605.8 ROM as primary and CM, AOKP and Resurrection Remix AOSP ROMs as secondaries while being fully Verizon variant device, thanks to this process)
5) Boot to TWRP. Do a full wipe and flash your AOSP ROM.
5a) Note - Most the AOSP ROMs (possibly all that are out?) will boot to the boot animation and then go to a black screen for a minute or so, don't freak. This is normal behavior and will resume back to the boot animation.
6) Enjoy! Be baffled like myself as to why this worked. Also hit thanks button if this helped you.
Click to expand...
Click to collapse
Hi, thanks for this post. I've flashed this custom unlocked firmware, then flashed the stock Verizon one over-top of it. Now, since I'm a noob, will this leave the radio working? Because before I've had many issues with custom roms and the radio not working on this phone. I have S-Off and an Unlocked bootloader. (Im VERY new if you cannot tell.)
I had the stock rom rooted, and then switched to Viper10.
All went to **** when I switched to ICE. Signal was GONE.
kiwigramme said:
Hi, thanks for this post. I've flashed this custom unlocked firmware, then flashed the stock Verizon one over-top of it. Now, since I'm a noob, will this leave the radio working? Because before I've had many issues with custom roms and the radio not working on this phone. I have S-Off and an Unlocked bootloader. (Im VERY new if you cannot tell.)
I had the stock rom rooted, and then switched to Viper10.
All went to **** when I switched to ICE. Signal was GONE.
Click to expand...
Click to collapse
Flashing the Verizon RUU indeed does flash the Verizon radio. Google what an RUU is for better understanding.
andybones said:
Flashing the Verizon RUU indeed does flash the Verizon radio. Google what an RUU is for better understanding.
Click to expand...
Click to collapse
Thank you, I'm more asking for a better understanding of how this decryption thing works with disabling the radio. There is very very little information online. Am I selecting the wrong options in TWRP or simply flashing the wrong roms?
kiwigramme said:
Thank you, I'm more asking for a better understanding of how this decryption thing works with disabling the radio. There is very very little information online. Am I selecting the wrong options in TWRP or simply flashing the wrong roms?
Click to expand...
Click to collapse
I'm not sure what you're doing wrong as I don't know what you did....
You are on MM firmware. You are a Verizon user. There is no benefit to flash any other firmware like the Android N US Unlocked firmware. No benefit.
The ONLY reason I flashed it, and this thread was made because of this discovery, that for some reason, the simple steps of
1) flash us unlocked firmware
2) flash vzw ruu
3) flash twrp
4) flash cm rom
5) profit
That's it. That's what this thread is for. I am not sure about radio, and decryption stuff, you are better off asking in a thread dedicated to that, or even creating one.. if you have these questions -- so do others.
For some info that I can give (which will be short as on phone)..
step 2, you flash the vzw ruu, which means you are back to 100% stock VZW MM ROM. You CAN flash N ROMs, but again this thread is not for that. When you flash the ROM, like Leedroid N, ICE N, Viper N, for ex. they have option in aroma for MM or N, you choose MM. As for radio, read the ROM threads instructions, I think Viper has them on their site, in-fact here.
http://venomroms.com/viper10-downloads/?refresh=true
read. ask questions. learn. repeat.
Hope this was of some help. :good:
P.S. When they say format data, it is not WIPE data. it is FORMAT data. you need to actually type YES in TWRP. You may need to do this. Personally... since I am using multirom, I am on Verizon MM RUU, I did these steps so I can run CM. As long as I have my stock deodexed MM ROM as my primary I can run N ROMs no issue as secondary (if you are familiar with multirom) I have the stock rom as primary, Leedroid N, ICE N and CM 14.1 ROMs all as secondary ROMs running great.
andybones said:
Flash the US Unlocked firmware, modified for Verizon.
Click to expand...
Click to collapse
What do I do to "modify it for Sprint"?
mcwups1 said:
What do I do to "modify it for Sprint"?
Click to expand...
Click to collapse
Please sit tight.
mcwups1 said:
What do I do to "modify it for Sprint"?
Click to expand...
Click to collapse
Been very busy, wasn't ignoring you.
Edit the android-info.txt with the CID and MID for Sprint. If you need help with that let me know. Follow the rest of the instructions, but flash the Sprint RUU rather Verizon, and the rest should be the same.
Merry Christmas
andybones said:
Been very busy, wasn't ignoring you.
Edit the android-info.txt with the CID and MID for Sprint. If you need help with that let me know. Follow the rest of the instructions, but flash the Sprint RUU rather Verizon, and the rest should be the same.
Merry Christmas
Click to expand...
Click to collapse
Beautiful!
I will try this very soon!
Sorry, I didn't see this, or get a notification.
---------- Post added at 04:21 PM ---------- Previous post was at 04:16 PM ----------
andybones said:
Been very busy, wasn't ignoring you.
Edit the android-info.txt with the CID and MID for Sprint. If you need help with that let me know. Follow the rest of the instructions, but flash the Sprint RUU rather Verizon, and the rest should be the same.
Merry Christmas
Click to expand...
Click to collapse
Also, if I have Super CID, I change to 11111111?
mcwups1 said:
Beautiful!
I will try this very soon!
Sorry, I didn't see this, or get a notification.
---------- Post added at 04:21 PM ---------- Previous post was at 04:16 PM ----------
Also, if I have Super CID, I change to 11111111?
Click to expand...
Click to collapse
If your device is SuperCID you can actually leave it as VZW_001, or change it to Sprints (being SuperCID though allows you to flash basically anything, so continue to be careful). I am not 100% sure if it matter about MID, that was one thing I was unsure about, but if you open up a Sprint firmware and look at the android.info.txt, change modelid: 2PS650000 to whatever it is for Sprint (it may be the same?). but other than that you are good to go!
Sorry it took me so long, I didn't foresee anything bad happening but I wanted to be sure first.
andybones said:
If your device is SuperCID you can actually leave it as VZW_001, or change it to Sprints (being SuperCID though allows you to flash basically anything, so continue to be careful). I am not 100% sure if it matter about MID, that was one thing I was unsure about, but if you open up a Sprint firmware and look at the android.info.txt, change modelid: 2PS650000 to whatever it is for Sprint (it may be the same?). but other than that you are good to go!
Sorry it took me so long, I don't foresee anything bad happening but I wanted to be sure first.
Click to expand...
Click to collapse
2PS640000 for Sprint.
Now, I'm just worried about it working!
Sprint has had several MM RUU's.
I might be the first to try this with Sprint's latest update.
mcwups1 said:
2PS640000 for Sprint.
Now, I'm just worried about it working!
Sprint has had several MM RUU's.
I might be the first to try this with Sprint's latest update.
Click to expand...
Click to collapse
RUU is an RUU, I wouldn't worry. And if are flash older RUU, then the new firmware, but that's going outside the guide and can't say that the AOSP ROMs will boot after the firmware, but I don't see why not.
Or do you mean flashing the US unlocked firmware on Sprints new firmware? If so you can flash an older RUU/firmware, then the edited US unlocked firmware, then Sprint newest RUU.
figured id just flash this and get it out of the way in case I wanted to run some of these asop builds popping up along the way.
from my understanding from reading this is that its kinda a permament fix, meaning id never have to flash the modified firmware pack again even if I reflash a ruu a second time down the road, or even the Verizon N update say? or is it needed again after doing that?
Please read the whole post and answer all (if possible) of my questions, I don't mind if you give me links, I'll read myself. Just don't answer with 2 words that don't mean anything to me.
I want to get into rooting, custom kernals, etc but I really don't know where to start reading from. Anything I came across seems not detailed enough. My end goals are:
- To get enough info so I don't brick my phone or even if I do, I want to know how to fix it.
- Install a custoim kernel, so I can get battery life simillar to this guy.
- Get magisk working, so I can get AUX lenses on gcam working too.
In the past I have installed custom roms on my old LG G2 and everything was so simple, rooting was 1 click and installed TWRP too. Then just flashing roms, gapps, etc, but at the moment I feel my knowledge/experience is like I've never seen a computer or phone in my life.
1. First, where do I start from? Here? It doesn't say if I should have an unlocked bootloader, but other guides require that. I'm kinda confused.
2. If I need to unlock it, I read that it wipes everything, how do I backup without TWRP? Speaking of which, do I need it since there is no official one. Can I do a pre-root backup with OP switch and then restore from it after I've rooted and/or unlocked bootloader?
3. What's the deal with patched boot images, in what situation would I need one?
4. I've just updated to OOS 10.0.8.HD01BA. Does that make me unable to root with method from 1 because its so new or it doesn't matter? I've read somewhere that with OTA you lose magisk/twrp, is there a way to prevent that or I'll just have to do 1 again. Do OTAs return me back to stock kernel?
5. The guy above is using this kernel. It's supposed to be working on 7T Pro too. Has anytone tried it? If so how is it?
6. What about blu_spark kernel, is it good? Also I don't really get what the warning message mean :
"Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark."
How do I reflash stock rom? Also there is no official TWRP, so I guess it's better to not use this one or there is another way to install?
7. Speaking of which, what's the deal with FKM? What should I know about it?
8. If I root with 1, can I then install arter97's kernel with FKM?
9. How do I go back to stock kernel/rom/etc/lock bootloader in case I need warranty?
10. Is there anything that's recommended to read/know?
UndeadG2 said:
Please read the whole post and answer all (if possible) of my questions, I don't mind if you give me links, I'll read myself. Just don't answer with 2 words that don't mean anything to me.
I want to get into rooting, custom kernals, etc but I really don't know where to start reading from. Anything I came across seems not detailed enough. My end goals are:
- To get enough info so I don't brick my phone or even if I do, I want to know how to fix it.
- Install a custoim kernel, so I can get battery life simillar to this guy.
- Get magisk working, so I can get AUX lenses on gcam working too.
In the past I have installed custom roms on my old LG G2 and everything was so simple, rooting was 1 click and installed TWRP too. Then just flashing roms, gapps, etc, but at the moment I feel my knowledge/experience is like I've never seen a computer or phone in my life.
1. First, where do I start from? Here? It doesn't say if I should have an unlocked bootloader, but other guides require that. I'm kinda confused.
2. If I need to unlock it, I read that it wipes everything, how do I backup without TWRP? Speaking of which, do I need it since there is no official one. Can I do a pre-root backup with OP switch and then restore from it after I've rooted and/or unlocked bootloader?
3. What's the deal with patched boot images, in what situation would I need one?
4. I've just updated to OOS 10.0.8.HD01BA. Does that make me unable to root with method from 1 because its so new or it doesn't matter? I've read somewhere that with OTA you lose magisk/twrp, is there a way to prevent that or I'll just have to do 1 again. Do OTAs return me back to stock kernel?
5. The guy above is using this kernel. It's supposed to be working on 7T Pro too. Has anytone tried it? If so how is it?
6. What about blu_spark kernel, is it good? Also I don't really get what the warning message mean :
"Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark."
How do I reflash stock rom? Also there is no official TWRP, so I guess it's better to not use this one or there is another way to install?
7. Speaking of which, what's the deal with FKM? What should I know about it?
8. If I root with 1, can I then install arter97's kernel with FKM?
9. How do I go back to stock kernel/rom/etc/lock bootloader in case I need warranty?
10. Is there anything that's recommended to read/know?
Click to expand...
Click to collapse
1. Unlocked Bootloader is always required.
2. Yes it wipes everything, OnePlus switch works fine for backup and restore
3. Since there is no TWRP you'll need one to root.
4. Not necessarily. You can just grab whatever patched boot image (preferably for BA), fastboot boot it to see if it works, if it does then do direct install in Magisk Manager. You can maintain root after an update following this
https://topjohnwu.github.io/Magisk/ota.html , and yes, it'll bring you back to stock kernel.
5. ?
6 &7. You can do ahead and try different kernels however I recommend arter97.
Since there is no TWRP you'll need FKM to flash the kernel.
8. Yes.
9. Rooting doesn't really void warranty, but I'd use MSMTOOL to get back to 100% stock.
For stock kernel you can flash stock (or patched) boot image depending wether you want stock or stock root.
To get back to stock ROM, either use MSMTOOL or fastboot ROM, you can find both in guides section.
10. Guides section for fastboot ROM and msmtool.
For AUX module.
https://www.celsoazevedo.com/files/android/p/gcam-oneplus-7-t-pro/
Since there is no TWRP it can be tricky to get out of bootloop if you install a rogue module.
Use this then;
https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677