i want to flash my phone with jf's roms but i want to know if he already has a rom that has root and wont need to be activated because i dont have a data plan
The ADP1 updates (incl the JFMod version) have an option on the initial setup wizard to bypass activation. However, running ADP1 means you won't be able to buy apps from the Market. Alternately, install the JFMod version of RC33 and follow the instructions in the "How to register the G1 without a sim or dataplan" thread.
ruffrider5956 said:
i want to flash my phone with jf's roms but i want to know if he already has a rom that has root and wont need to be activated because i dont have a data plan
Click to expand...
Click to collapse
just to let you know your going to get flamed for this. There is a sticky thread on this exact subject that you just asked a question on. Which is NO MORE than 10 topics to read to find what your looking for. Please read before posting and you will enjoy your stay here a little more.
inpherno3 said:
just to let you know your going to get flamed for this. .
Click to expand...
Click to collapse
Easy now don't be so silly ....
jshields said:
Easy now don't be so silly ....
Click to expand...
Click to collapse
lol silly is the new angry you didn't know?
jashsu said:
The ADP1 updates (incl the JFMod version) have an option on the initial setup wizard to bypass activation. However, running ADP1 means you won't be able to buy apps from the Market. Alternately, install the JFMod version of RC33 and follow the instructions in the "How to register the G1 without a sim or dataplan" thread.
Click to expand...
Click to collapse
wrong.
you can download and buy apps from the market.
what you can't do with an ADP is buying protected apps only and they are very few.
inpherno3 said:
just to let you know your going to get flamed for this. There is a sticky thread on this exact subject that you just asked a question on. Which is NO MORE than 10 topics to read to find what your looking for. Please read before posting and you will enjoy your stay here a little more.
Click to expand...
Click to collapse
i read the sticky but it said rc30 i reread it and it was for rc30 up so i got that down so anyway if i flashed with a modded rc33 i can unlock using the method posted in the sticky right and can someone give me a link to the modded rc33 i think i found it but im not sure and i dont want to brick my phone so thank you guys for the help
so this how you flash the phone with a different rom
1. Format your phone's SD card to FAT32 mode:
* Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
* Click the notification, and then click "Mount".
* A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
2. Download and unzip the RC29 or RC7 image file. Copy the DREAMIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
3. Turn the device power off.
4. Hold Camera button, and press Power button to entry bootloader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
5. As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
6. After it is finished, perform the restart your phone.
but instead of using rc29 i want to use the modded rc33 so i would be going from stock rc33 to modded rc33 because i read it was already rooted if anyone can tell me thats right ill appreciate it
ruffrider5956 said:
so this how you flash the phone with a ut instead of using rc29 i want to use the modded rc33 so i would be going from stock rc33 to modded rc33 because i read it was already rooted if anyone can tell me thats right ill appreciate it
Click to expand...
Click to collapse
Nope.
Gotta go RC33 > RC29 > Rootit >RC33 JF Edition.
ruffrider5956 said:
but instead of using rc29 i want to use the modded rc33 so i would be going from stock rc33 to modded rc33 because i read it was already rooted if anyone can tell me thats right ill appreciate it
Click to expand...
Click to collapse
That would be nice. I wouldn't call it "wrong" like the other guy did, because wanting something isn't wrong. It just won't work since there is no mod-RC33 image available *in the required format*. Problem is that in order to write a system image to a stock consumer device, that system image needs to be digitally signed with a private key that we simply don't have available.
So the procedure becomes... write the older system image that has a known exploit available, and use that exploit to root the device, allowing you to write the engineering bootloader, which allows the installation of your desired system image.
ok so if i go from rc33 to rc29 and root it how do i got to jf's rc33 wont i loose the root
ruffrider5956 said:
ok so if i go from rc33 to rc29 and root it how do i got to jf's rc33 wont i loose the root
Click to expand...
Click to collapse
AAAAHhhhhhhhhhhhh lol
No you wont cause JF roms are modded so we wont.
Don't ask how lol
Mikey1022 said:
AAAAHhhhhhhhhhhhh lol
No you wont cause JF roms are modded so we wont.
Don't ask how lol
Click to expand...
Click to collapse
lol bro then why cant i just go from rc29 to the modded rc33 why do i have to first root rc29 then go to modded rc33 and also do i flash the modded rc33 just how i did the rc29 or is it going to be different
Read,Read, and Read some more.
ruffrider5956 said:
lol bro then why cant i just go from rc29 to the modded rc33 why do i have to first root rc29 then go to modded rc33 and also do i flash the modded rc33 just how i did the rc29 or is it going to be different
Click to expand...
Click to collapse
I'll just ask this.....Why does the sun rise from the East and not the West.
There are just some things you dont ask why to. It just is.
ruffrider5956 said:
also do i flash the modded rc33 just how i did the rc29 or is it going to be different
Click to expand...
Click to collapse
rc33 has to be renamed update, place it on your cards root, reboot *home+menu+power key* let go of menu and power key when your phone restarts booting up. HOLD THE HOME KEY STILL, till you enter recovery mode.
Click Alt+l
Click Alt+s
when update is one installing,
Click Home+back key.
Cross your fingers that your phone won't blow, if it doesn't, you did it
your best solution
get the Haykuro Sapphire port...the latest 4.9 is working awesome, you can just click the SKIP button on the registration, but if you are going to use the market later on, you need to connect on wifi and login with you gmail account. plus, you will have many other features on your phone like auto-rotate, camcorder, stereo BT (Still buggy) and many more.. Hope this helps you. good luck.
Related
I was trying to manually install RC29 and for some reason when it goes to install it says that there are "No Signature" and that it cant update. Anyone have a way to fix this or had this issue?
Even when I tried to manually update to that it gave me the same No Signature error and wouldnt update it. Basically I cant get passed the Google log in because something must have happened to the phone because when I restored my phone and went to set it up with my new gmail account it wont get passed that screen and wont connect to the servers. So basically I wanted to update it again with a full install of RC29 in hopes of it fixing the problem.
ballaholyk84 said:
I was trying to manually install RC29 and for some reason when it goes to install it says that there are "No Signature" and that it cant update. Anyone have a way to fix this or had this issue?
Even when I tried to manually update to that it gave me the same No Signature error and wouldnt update it. Basically I cant get passed the Google log in because something must have happened to the phone because when I restored my phone and went to set it up with my new gmail account it wont get passed that screen and wont connect to the servers. So basically I wanted to update it again with a full install of RC29 in hopes of it fixing the problem.
Click to expand...
Click to collapse
Have you edited anything on the phone? Have you touched the OTAcerts.zip file?
neoobs said:
Have you edited anything on the phone? Have you touched the OTAcerts.zip file?
Click to expand...
Click to collapse
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
ballaholyk84 said:
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
Click to expand...
Click to collapse
That is why you get the no signature file error. OTAcerts.zip is the signature file.
neoobs said:
That is why you get the no signature file error. OTAcerts.zip is the signature file.
Click to expand...
Click to collapse
So is there a way that I can get those back on the phone?
ballaholyk84 said:
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
Click to expand...
Click to collapse
to reverse look in that AndroidMod.zip JesusFreke posted look for update - Restore Orginial RC29 Boot Image.zip. hope i helped
"Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition.."-JesusFreke
humble said:
to reverse look in that AndroidMod.zip JesusFreke posted look for update - Restore Orginial RC29 Boot Image.zip. hope i helped
"Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition.."-JesusFreke
Click to expand...
Click to collapse
I see that but How do I apply it since I cant get into the phone?
ballaholyk84 said:
I see that but How do I apply it since I cant get into the phone?
Click to expand...
Click to collapse
try naming it update.zip and updating it from the sdcard.
neoobs said:
try naming it update.zip and updating it from the sdcard.
Click to expand...
Click to collapse
Got that to work thanks! Now if only I can transfer this damn RC29 to my card without some part being corrupt. I Have tried about 5 times with something being corrupt
Help i need to restore the recovery.img for the G1 RC29
I mest up my G1 it no longer could take my RC33 update, i get an error
E:Failure at line 5 assert getprop("ro.build.fingerprint")== "tmobile/kila/dream/trout:1.0/TC4-RC30/116143:users/ota-rel-keys,release-keys" l l getprop("robuild.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys.release-keysInsta
i was going to do the multitouch on my G1 but when i started to follow this link
http://hehe2.net/gadgets/howto-multitouch-tethering-task-manager-for-android-g1/
i got stuck on the telnet command for the
rm -f /system/recovery.img
it would not accept it, andy my Dumass decided to skip that step and enter the
flash_image recovery /sdcard/recovery_testkeys.img
since i knew that i had the recovery_testkeys.img in my sdcard
(to be honest, i dont know squad about telnet with the G1, i am familiar with the linux terminal but its not the same)
so i stop there because i started to get nervous about my G1 getting **** up, i figure that i would just do a factory reset and wala ill be back in business but nah, after the factory rest i obiously was going to be in the RC29, so i tried doing the manual update to the RC33 but now it will not take it, i keep on getting the message that is in the beginning of this post, i know the update file i am using is not corrupt or incorrect, i had my girls G1 that i just purchase for her and i decided to test out the update in hers, since its still on the RC30, and it work fine.
Please Someone help, i know i should had tough my firmware.....
My G1, which has been converted to a JF ADP1.1, gave me the following popup message just now:
! A system update is available
-----------------------------
Holiday phone update 2 of 2: This is
a full system update. Your data and
settings will be preserved.
Update now Update later
I'm going to click "Update later" since I don't know exactly what this is.
I searched the XDA Dream forums for "Holiday phone" without finding anything, but if this is something previously discussed I'm sorry for the double post.
I have tried to attach a picture of the screen as well.
~Christopher
I went to Device Info, and clicked "Check for upgrade".
The result was:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Check-in status:
CHECKIN_SUCCESS
grenness said:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Click to expand...
Click to collapse
Does anyone know where in the phone file system these files go?
If I can find it, I can probably copy it to the SD card and then attach it to this thread.
~Christopher
so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
i imagine it will just be RC33 for ADP, with Latitude etc.
only one way to find out
Meltus said:
so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
Click to expand...
Click to collapse
I'm guessing this is for ADP only, since my phone (as far as Google knows) is an ADP (converted from a G1 using JesusFreke's ADP image) and the name of the .zip contains *devphone*.
No, I haven't proceeeded with the upgrade, I would like some other inputs from the forum first.
~Christopher
hrm, mine is saying its up to date when I hit the update checker. Guess i'll keep checking, as I would much rather stay on adp code and not run the tmobile.
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
So it has the update for "Check for updates". Looks like it probably is the ADP1's answer to the RC33...
kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
I appreciate the link, but JF-ADP1.1 is based off the images you linked to. Whatever the holiday update is is different.
Can you look in /cache and see if you see an update file? I'd love to get a copy. (Also, run 'logcat' and look for urls.)
I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher
grenness said:
I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher
Click to expand...
Click to collapse
RC33 takes -forever- to do it's first boot. On the order of 10 mins for some people.
Does 'adb logcat' show anything?
I left it on the table in front of me, I swear it took around 10 minutes before it proceeded with the boot-up, and now it seems to work fine. Has Google voice search and Latitute.
Don't know what's missing - looks like Sansdroid auto-rotate no longer works.
~Christopher
the download url is similar to rc OTA updates , just need to replace filename:
Code:
https://android.clients.google.com/updates/signed-holiday_devphone-ota-130444-debug.55489994.zip
I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.
Is it possible to use this update directly on a ADP 1 with 1.0 image?
A friend of mine has not updated his ADP to 1.1 yet.
jcdekoning said:
I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.
Click to expand...
Click to collapse
It is, it just might not be released yet.
cannot upgrade from JF1.41 RC33
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?
endolin said:
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?
Click to expand...
Click to collapse
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.
thanks for your quick reply.
i'm not familiar with the signing process, therefore I'd be glad to see a modified
release from you.
Disconn3ct said:
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.
Click to expand...
Click to collapse
http://andblogs.net/2009/02/new-adp1-update-official-with-google-voice-and-more/ has the download that does no system checks. So anyone should be able to apply it as update.zip
Tomorrow i send in my g1. and it is rc33 rooted, on the phone the htc person told me that they will inspect it to make sure there is not any 3rd part software on it for warranty void purpases. please help me! i need to get this done!
re-flash to RC29
Done!
You might consider using the search function. This subject has been considered many, many times before.
flash the Dreaming.nbh file from the original files you downloaded when you were rooting your phone and that will take you back to rc29 and it will automaticlly update its self back to rc33 and u wont have anything to worry about
dang you beat me to it...lol
only by a second!
idragbody said:
flash the Dreaming.nbh file from the original files you downloaded when you were rooting your phone and that will take you back to rc29 and it will automaticlly update its self back to rc33 and u wont have anything to worry about
Click to expand...
Click to collapse
what is the name of the file sopossed to be on the memory card
dreaming.nbh.zip or dreaming.zip dreaming.nbh errrr what
jbettt said:
what is the name of the file sopossed to be on the memory card
dreaming.nbh.zip or dreaming.zip dreaming.nbh errrr what
Click to expand...
Click to collapse
DREAIMG.nbh (DREAm + IMaGe)
Look at the spelling very carefully, it must have the correct spelling to work.
http://forum.xda-developers.com/showthread.php?p=3690555&highlight=dreaimg.nbh
Question answered and has been asked before.
Closed
Dave
I AM NOT RESPONSIBLE FOR THE "BRICKING" OF YOUR DEVICE. FLASHING A RADIO IS DANGEROUS, DO NOT PULL THE BATTERY OR STOP THE UPDATE AT ANY TIME. FOLLOW ON SCREEN INSTRUCTIONS AND BE PATIENT.
That said... let the fun begin!!!
Anyhow this is the latest radio from:
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
INSTRUCTIONS FOR FLASHING:
- Download the EVO-1.39.00.05.31-radio-signed.zip from below
- Put it on the root of your sdcard (top level)
- Reboot to recovery and run .sh or .bat file to gain custom recovery
- Select "Flash zip from sdcard" in recovery
- Select "EVO-1.39.00.05.31-radio-signed.zip" and confirm the flash
- Ath the bottom it will say "Reboot via menu to complete installation" do as it says and select reboot in the menu
- it will then say "writing image" then reboot to a screen with a phone and a green arrow
- then it will reboot again showing the same screen with the arrow but have a little status bar.
- after that it will reboot into android and prompt u with a congrats on flashing the new radio. press ok ansd cancel the firmware update (its useless )
- navigate to settings>About phone>Software information
- under Baseband u will see "1.39.00.05.31"
- your done now. enjoy the awesome new radio <~~~ congrats its not a brick!!!
DOWNLOAD LINK
Thanks toast!
Sweet thanks
Wait where's the link lol
Download Link
Download Link PLZ
is this the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
change log? any idea what it updates/fixes/improves?
thanks!!
toast your a monster
Man what a good job your doing toast I can hardly keep up I am loving my rooted Evo I/O Phone tho thanks to you I am even sending someone my Incredible to see about root cuz I sill never use it again lol
joeykrim said:
is this the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
change log? any idea what it updates/fixes/improves?
Click to expand...
Click to collapse
htc doesnt do chage logs in their ruus anymore. ur guess is as good as mine as to whats changed. they obviously want u to use this radio for a reasion or else they wouldve just left the old one.
What is the md5sum of EVO-1.39.00.05.31-radio-signed.zip?
could this be a fix for the weak Wifi radio?
which radio is this?
toastcfh said:
htc doesnt do chage logs in their ruus anymore. ur guess is as good as mine as to whats changed. they obviously want u to use this radio for a reasion or else they wouldve just left the old one.
Click to expand...
Click to collapse
didnt see an answer to this previously?
is EVO-1.39.00.05.31-radio-signed.zip the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
is there a simple way to determine this? compare radios? what partition are they kept in? mtd2?
sorry bunch of questions as my thoughts flow
ChrisDos said:
What is the md5sum of EVO-1.39.00.05.31-radio-signed.zip?
Click to expand...
Click to collapse
4d9404ebc30c32b20a7b8fa304225680
joeykrim said:
didnt see an answer to this previously?
is EVO-1.39.00.05.31-radio-signed.zip the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
is there a way to find this out?
Click to expand...
Click to collapse
Anyhow this is the latest radio from:
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rele ase_171253_signed
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
pingpongboss said:
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
Click to expand...
Click to collapse
this will not replace the ota. this will only replace the radio.img and yes u must be root and have access to a custom recovery
pingpongboss said:
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
Click to expand...
Click to collapse
somebody can correct me if im wrong, this is just what ive gathered from reading.
yes, apply this radio udpate.zip after rooting using's toasts method and running his recovery. when the recovery UI pops up, then load this radio update.zip file posted in the OP. that way you'll still be able to keep root and have the latest radio.
this does not replace the OTA update, this update only patches the radio, it does not patch the software.
Call me stupid, but what are the benefits of flashing the radio?
Thanks for the quick response guys. So are we free to apply the OTA ourselves after we root and use this radio upgrade? I keep remembering toast saying not to apply any RUU's (not sure if the OTA update counts as an RUU)
jigglywiggly said:
Call me stupid, but what are the benefits of flashing the radio?
Click to expand...
Click to collapse
Since they don't release the changelogs, we don't know what has changed. But as toast said, there must be a reason they updated the radio.
jigglywiggly said:
Call me stupid, but what are the benefits of flashing the radio?
Click to expand...
Click to collapse
You must not be the only stupid one, Im stupid too, what does this new radio do?
arkshel said:
You must not be the only stupid one, Im stupid too, what does this new radio do?
Click to expand...
Click to collapse
could increase signal or optimize hardware. the radio controls a lot of function of the device.
thanks. Everything went well.
ADDED INSTRUCTIONS AT END OF POST*****
Got it.... Rooted, twrp, the whole deal. On 6.0. I'll post instructions in the middle of the week for everybody.
Unfortunately if you already did the other method, you are screwed for now. Because the method I used required me to flash a stock 5.1.1.
Standby
_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|
So there I am sitting on my computer last night, when a notification pops up on my V10 .... The old "congratulations, you've won first prize in an update contest!"
Lo and behold, the MM update had downloaded (at record speeds I might add).
Without wasting a minute, I navigated to the cache partition and copied it to my internal folder (see attachment), then backed it up on drive.
So... We'll just skip to the good part...
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
I'll save you all the curiosity and let you know that I am going to look into this option to flash the OTA this weekend. I'm going to assemble a compatibility analysis and if everything checks out, I'll flash it.
Standby for carnage.
****INSTRUCTIONS
OK... I really owe everybody here an apology for taking so long to get an official instruction up. Work has been crazy this week. But I wanted to be able to take some time to do this. So here we go...
But wait... Before we even start, please for the love of God do your homework here. Please go read through chains thread about his app, how it works, etc. The interface is straight forward enough, but there are other things to understand. Please just understand what you are doing, and please verify checksums of anything you download. This is very important.
And thank chainfire, not me.
PRE-FLASH REQUIREMENTS:
1. First and foremost, you MUST be on the latest version of MM TWRP. There is a thread in the development section for this, with instruction on how to flash it, find that thread. Get it installed. This is a must. You must also verify adb and fastboot are working fully on your device.
2. You must be 100% Stock (but rooted) on the latest TMO V10 5.1 1 firmware and ROM, no custom kernels, nothing. Stock, with the exception of working root, and the latest 3.0.2.0 Marshmallow TWRP. When I say stock I mean no deodex, no system apps removed, this is an absolute requirement. The reason for this is mostly to avoid the update.zip from aborting as it does checks for presence of apps within system, etc. If you have to flash a stock ROM before doing this, don't do it as an "in line" queue before you flash the OTA in flashfire. Do it separate.
3. You must have the official OTA downloaded and on your internal SD card. Also, put the latest superSU version 2.67 on an external card, and remove the SD card from the device. The md5 for the OTA is 280ad51eb96457df097df5a088a535af9
Once you have checked those 3 boxes. You are ready to proceed.
4. Install flashfire. I was on version 32.
5. Open flashfire, grant it root
6. Go into the setting of the app, check the "Flash boot loaders" and "Freeload" box.
7. Find the OTA package, queue it up with "flash zip or ota" (small + sign at the bottom right of the screen)
It is important to note that after the flashing process completes, you will want to power off the device, and boot it into fastboot mode to unlock the boot loader.
8. Execute the update.
9. After it finishes, power off the device.
10. Boot into fastboot by holding down the volume down button, and with the button held down, plug the USB cable into your computer.
11. Once in fastboot, type the following command and hit enter:
Code:
fastboot oem unlock
Let it run for a bit, it is going to wipe your data.
12. After it completes (your terminal should give you a time displayed for the operation).... Unplug the phone, and yank the battery.
13. Pop in your Micro SD card (with superSU 2.67 flashable on it) then manually boot the phone into recovery mode. You are going to flash superSU again as a sanity check. I did this because if for some reason FF didn't flash superSU, and then the system wrote over your recovery during your first boot... You'd be absolutely dicked stuck on stock MM with no way of getting root back for now. I like verification...
To boot the v10 into recovery mode manually, simply have the device powered off, then hold the volume down and power button at the same time. AS SOON as you see the boot screen (not to be confused by the boot animation) released the power button for just a little less than a second then press and hold it again (keep the volume down button pressed the whole time). It may or may not be absolutely critical that you don't screw this part up. You need to get into recovery at this point to validate root being installed.
This should take you into 2 sequential screens, both asking about clearing data, select yes for both (don't worry, it won't, it will take you into TWRP.
Once in twrp... Mount your SD card in the twrp settings, and flash superSU.
Reboot afterwards. Done.
After you do this, you will be in 100% stock, rooted MM.
You might need to flash twrp again (do it the normal way, you are done with flash fire now), but root, you will have, and full functionality, you will also have, with everything working.
Dont do it. No root for MM at the moment.
Double0EK said:
Dont do it. No root for MM at the moment.
Click to expand...
Click to collapse
Unless you use Eliminator74's rooted rom which is the official MM update from T-Mobile.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.
markbencze said:
what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.
Click to expand...
Click to collapse
I'm debating that myself
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Standing by!
Sent from my pretty nifty brand new LG V10
Ok. Im actually interested in the outcome.
I think a lot of us are curious to see if it works. For all we know this is the solution that we've had the entire time. the question is, is anyone brave/crazy/foolish enough to try it? It might work great, but then again it could brick your phone given LG devices are untested trying this. there are several devices that were also untested that it did work on so who knows. But the app does have the capabilities to flash a stock update.zip and maintain boot root and recovery. I would think you'd have to reunlock your bootloader after flashing though in order to boot.
anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache
In for results
dimm0k said:
anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache
Click to expand...
Click to collapse
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
A think tank.
If the update is zip, can the flash be done with TWRP plus superSU?!
truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip
truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
so is mine
dimm0k said:
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip
Click to expand...
Click to collapse
That's weird. Wonder why your's went there?
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
See OP... got it.
warBeard_actual said:
See OP... got it.
Click to expand...
Click to collapse
Got what? Is in you used Flashfire and updated via ota and were able to retain root and TWRP? Sorry, I"m running g on almost no sleep cause my truck broke down and is in the shop and it's hard to sleep in the customer lounge of a Freightliner dealership.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.
crashnova said:
Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.
Click to expand...
Click to collapse
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
truckerdewd said:
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
I woke up to the OTA this morning. I find it odd tho because i thought OTAs were disabled on siraltus rom. I would try FF but don't eant to risk bricking until OP shares the steps he took.