Please read this before you proceed:
1. The phone heats up a LOT
2. The battery consumption exceeds the charging speed, so using the device while it is charging will also drain battery (at idle state, it takes around 11 hours to charge)
3. You cannot install apps. You just can't. Don't be a smartass and say that you'll use ADB. That also won't work
4. It can get frustratingly sluggish
5. There isn't an RUU for the stable version out yet. I am trying to get one. Please refrain from trying this until I can upload a stable RUU file for you to fall back on (if a downgrade even works at all!)
6. This is a test version and logs a lot of stuff.
Once again, use it with caution! You have been warned.
So, after I read a few posts in the Lollipop update thread, I checked the ir-file.com website myself and found that they in fact do have an E8 lollipop leak (it is called M8 Ace by developers). Also, there's a bunch of other RUU on the website that isn't anywhere else. The OTA file that they are hosting seems to be the same one that I posted a few days ago to this forum.
What's the catch? It is paid. So, if anyone is a member on the website, would it be possible for you to try the RUU or at least mirror it?
The screenshot from the website is here: (LINK)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There's an Lollipop ROM out there guys. Let's go get it..
BTW.. Has anyone heard of or used this website? Its it possible that they could be fraud?
EDIT: Seems this thread is updated with the link: Thread | LINK to RUU
Even if I download this , how do I flash it, thru stock recovery ??
I'm as clueless.. In fact the first attempt I had at downloading this, I ended up with a corrupt archive. Now I'm downloading again.
Anyway the main thing here is that this is the first time we have seen indian RUUs for e8 or even m8 for that matter.
If not the lollipop I would definitely like to know if the other kit Kat Indian RUUs work or not.
If they do work, these are a real catch!!
Well, someone only posted the link to the Lollipop ones. And sadly, the archive posted seems to be corrupt.. :/
buggerman said:
Well, someone only posted the link to the Lollipop ones. And sadly, the archive posted seems to be corrupt.. :/
Click to expand...
Click to collapse
If I'm not mistaken HTC RUUs are encrypted so probably that archive is not corrupted at all.
Interesting.. In that case, how do you use it?
crystal_ball said:
If I'm not mistaken HTC RUUs are encrypted so probably that archive is not corrupted at all.
Click to expand...
Click to collapse
But those are .exe files. This is a zip, that just won't extract.. If there is some software to use these with, that would be an entirely different matter..
buggerman said:
But those are .exe files. This is a zip, that just won't extract.. If there is some software to use these with, that would be an entirely different matter..
Click to expand...
Click to collapse
Maybe these .zip are actually .exe files .
try renaming extensions and flash again, just guessing here.
BUT to flash any RUU, .zip or .exe, dont we need to be s-off ???
Ahh !! I remember these zip RUUs from the days when i had wildfire s. To flash this, u need to rename the zip file to OPAJIMG.zip and place in your sdcard. Then boot into boot loader, and it will automatically detect the zip file and start extracting it, and show you the status on top right (a coloured bar).
In the case of wildfire s, there was no internal memory. I'd suggest you place the zip file in both, internal and external sd.
And yeah, these files can't be extracted simply (AFAIK). Even you can't open boot.img or system.img, either by iso managers or winrar.
If the zip is really currupt, it would show in the bootloader. And even if it's a bogus file ( like made from another device's ruu or fake rubbish files), the extraction would stop!!
Hope I helped
Offtopic: I got a DOA for my E8 and got it replaced with one M8 EYE. You should be happy that there exists a page for E8 and a group of enthusiasts M8 eye is hopeless in terms of support
Kartik1807 said:
Ahh !! I remember these zip RUUs from the days when i had wildfire s. To flash this, u need to rename the zip file to OPAJIMG.zip and place in your sdcard. Then boot into boot loader, and it will automatically detect the zip file and start extracting it, and show you the status on top right (a coloured bar).
In the case of wildfire s, there was no internal memory. I'd suggest you place the zip file in both, internal and external sd.
And yeah, these files can't be extracted simply (AFAIK). Even you can't open boot.img or system.img, either by iso managers or winrar.
If the zip is really currupt, it would show in the bootloader. And even if it's a bogus file ( like made from another device's ruu or fake rubbish files), the extraction would stop!!
Hope I helped
Offtopic: I got a DOA for my E8 and got it replaced with one M8 EYE. You should be happy that there exists a page for E8 and a group of enthusiasts M8 eye is hopeless in terms of support
Click to expand...
Click to collapse
Thanks for the info dude.. Will check it out.
I thought the M8 Eye had decent support. It doesn't?
I can confirm that the image shared is legit. Just follow Kartik's instructions and you will have lollipop..
However, this is a test build, I think. I'd really like to shift back to KitKat..
buggerman said:
I can confirm that the image shared is legit. Just follow Kartik's instructions and you will have lollipop..
However, this is a test build, I think. I'd really like to shift back to KitKat..
Click to expand...
Click to collapse
is there's something wrong with it? or it's just unsuited to be daily driver?
I found out that after installing and configuring it you cannot install packages from Google play store... Others please confirm.
Please read the first post for details and warnings regarding this.
buggerman said:
Please read the first post for details and warnings regarding this.
Click to expand...
Click to collapse
Good warning and it does not look like a worthwhile test. Going to wait for the stable version, as HTC normally does a good job with these things
buggerman said:
Please read the first post for details and warnings regarding this.
Click to expand...
Click to collapse
thanks dude... This makes me wonder how long before we get an official update. hopefully in 2-3 weeks.
buggerman said:
Please read the first post for details and warnings regarding this.
Click to expand...
Click to collapse
The damage is already done ...
FYI, Your reply is after that ....
Well , I guess we have established that we just have to wait for the lollipop update from htc.
Meanwhile why dont we concentrate on getting the KK Indian ruu which is just above the loliipop ruu in ir-file.com .
I dont know how all the other e8 variants get RUUs but there are never for indian htc devices atleast for the m7 , m7 dual sim 802d, m8 etc.. , i'm talking about indian htc mobiles here.
We have FTFs for sony and tar.md5 for samsung so that when ever phone is soft bricked we can always use the corresponding stock fw to un-brick the device.
I googled with the below name but i could find the link only on ir-file which is possible to download only thru a paid account.
Code:
0pajimg_m8_ace_dwgl_k44_sense60_htc_asia_india_1.26.720.6_radio_1.12.30.0109_nv_nv_india_2.14_09b_release_420051_combined_signed.zip
So i would request indian users to find link for indian ruus.
iamsuperuser said:
Well , I guess we have established that we just have to wait for the lollipop update from htc.
Meanwhile why dont we concentrate on getting the KK Indian ruu which is just above the loliipop ruu in ir-file.com .
I dont know how all the other e8 variants get RUUs but there are never for indian htc devices atleast for the m7 , m7 dual sim 802d, m8 etc.. , i'm talking about indian htc mobiles here.
We have FTFs for sony and tar.md5 for samsung so that when ever phone is soft bricked we can always use the corresponding stock fw to un-brick the device.
I googled with the below name but i could find the link only on ir-file which is possible to download only thru a paid account.
Code:
0pajimg_m8_ace_dwgl_k44_sense60_htc_asia_india_1.26.720.6_radio_1.12.30.0109_nv_nv_india_2.14_09b_release_420051_combined_signed.zip
So i would request indian users to find link for indian ruus.
Click to expand...
Click to collapse
I am going to the service centre tomorrow.. Will try to get the file so that I can share it with you guys..
Related
First and foremost I take no responsibility to what this update package will do to your device. That being said I have tried this successfully on multiple rooted tablets running US 8.6.5.6.
Long story short if your rooted this will update you to 8.6.5.9 and update your CWM to 3.2.0.1 provided by Roach2010. Simply download to root of sdcard and flash through CWM.
All credit goes to Roach2010 and the package he provided for the 3.2 upgrade.
UPDATE: This is for Rooted stock firmware only, if you applied Netflix patch or any other mod's this will fail. Revert your changes and then give this a shot.
UPDATE2: Added the WW package but I can't test this. Please let me know how it goes.
Nice, waiting for WW version also
Sent from my Transformer TF101 using Tapatalk
Remember !!!!
If you already apply Netflix patch You cant update. (MD5 error) Using root explorer go to system/lib and rename
libnvomx.so file to libnvomx.so.tmp
and
original libnvomx.so.bak file to libnvomx.so.
After Update using CW mode ( Remember to mount all before)
*** [when you update nexflix patch last time this file replace to XOOM's libnvomx.so file. Thats why you need to do this.]***
rufik said:
Nice, waiting for WW version also
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
If someone can get me the WW package I can cobble something together. I won't be able to test however since I am on US.
Let me know.
Backing up now to try. I tried the unroot and update method but it kept failing, im betting some file I modified (like the Xoom SystemUI) or something I deleted is pissing it off. Hopefully this resolves it.
I never did the netflix patch so I should be good right? I should be able to run this, sideload netflix and party all the time?
I un-rooted, trying to get the update ... will this still work ?
nolf3 said:
I un-rooted, trying to get the update ... will this still work ?
Click to expand...
Click to collapse
If you unroot that why you did'n update original one. I saw some one upload in another thread. I think this is only for rooted one and this is modified version.
I was able to install this, it appears to have updated my build. I did run into some issues where it got mad because I had uninstalled the ASUS programs that it wanted to update but once I pasted those back in it ran fine (i of course then deleted them again).
Now I just need to clear this firmware thing. It keeps asking me to update
Ryan, did you install this while un-rooted ? since you mention you tried the unroot and update method - which is what i tried too
ryan stewart said:
I was able to install this, it appears to have updated my build. I did run into some issues where it got mad because I had uninstalled the ASUS programs that it wanted to update but once I pasted those back in it ran fine (i of course then deleted them again).
Now I just need to clear this firmware thing. It keeps asking me to update
Click to expand...
Click to collapse
Just run the firmware and it will fail. Reboot and the notice will go away. How I did it on mine.
Can I use this if I'm running Prime 1.7 ?
ajamils said:
Can I use this if I'm running Prime 1.7 ?
Click to expand...
Click to collapse
No. This is only for people with rooted stock ROM version 8.6.5.6 who want to update to stock rooted 8.5.6.9
nolf3 said:
Ryan, did you install this while un-rooted ? since you mention you tried the unroot and update method - which is what i tried too
Click to expand...
Click to collapse
Rooted and with clock workmod
A couple of bugs I see, not sure if its because of my Xoom systemUI but when I mount a disk it says its mounted as read only but I can modify it and when I click on the SD card icon the pop up says "mobiledock firmware updating" instead of "sd card inserted."
Also, the auto and slider look wierd under the brightness options, white icons that dont match.
chuy08 said:
If someone can get me the WW package I can cobble something together. I won't be able to test however since I am on US.
Let me know.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/39328504/dlpkgfile.zip
CrazyPeter said:
http://dl.dropbox.com/u/39328504/dlpkgfile.zip
Click to expand...
Click to collapse
Bump, give that a shot. Let me know.
chuy08 said:
Bump, give that a shot. Let me know.
Click to expand...
Click to collapse
No Go...
Failed on CRC Checking of ApplicationsProvidor.apk
(running HTJ85B.WW_epad-8.6.5.7-20110730)
CrazyPeter said:
No Go...
Failed on CRC Checking of ApplicationsProvidor.apk
(running HTJ85B.WW_epad-8.6.5.7-20110730)
Click to expand...
Click to collapse
I see what I did wrong try that. Sorry bout this I am new at this Android stuff.
chuy08 said:
I see what I did wrong try that. Sorry bout this I am new at this Android stuff.
Click to expand...
Click to collapse
Just did a BeyondCompare diff between the original dpkgzip and the modded one, so I can understand what you did. Most of it makes sense (the stuff in the script).
But why is the binary blob file half the size?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bump...
Anyone know what the blob file is, what it does and why it's smaller? I don't want to screw up my working tablet, but I do want to try this out.....
CrazyPeter said:
Bump...
Anyone know what the blob file is, what it does and why it's smaller? I don't want to screw up my working tablet, but I do want to try this out.....
Click to expand...
Click to collapse
The blob is half the size cause its CWM.
I've searched everywhere and can't find anything on the sprint SPH-P500.
Does anyone know of any guides out there? I don't want to risk bricking it with a root from another model number. Thanks for all your hard work guys.much appreciated!
Do you have your stock rom? If you do, try rom for GT-5100 but you will not have 4G capability...
And if it don't work, you go in download mode and then restore your old stock rom thank to odin!
I guess everyone has forgotten about our tablet
I've never done anything on the coding side. But if someone could give me some guidance, I'd be willing to attempt to port some of the greatness that all of the other tablets are getting.
Its a great undertaking. I do website development and have linux experience and would rater not touch rom development. I have been interested though.
As far as the gt builds, i can give that a try. I dont have 4g in my area anyways,. Ill just have to become comfortable with odin before i do anything. Thanks!
Has there been any update on this? Looked around and doesn't look like there is even a developer working on it.
I can't even find the stock firmware for the SPH-P500.05 to download. I'm about to see if a sprint store will give me the file so I can start experimenting. If someone has a link to the stock firmware for this device it would be great. Maybe I'll get my hands dirty and make a few attempts and maybe get a guide going.
FluffyMittens said:
Has there been any update on this? Looked around and doesn't look like there is even a developer working on it.
I can't even find the stock firmware for the SPH-P500.05 to download. I'm about to see if a sprint store will give me the file so I can start experimenting. If someone has a link to the stock firmware for this device it would be great. Maybe I'll get my hands dirty and make a few attempts and maybe get a guide going.
Click to expand...
Click to collapse
Any luck? I'm dying to root this thing.
FluffyMittens said:
Has there been any update on this? Looked around and doesn't look like there is even a developer working on it.
I can't even find the stock firmware for the SPH-P500.05 to download. I'm about to see if a sprint store will give me the file so I can start experimenting. If someone has a link to the stock firmware for this device it would be great. Maybe I'll get my hands dirty and make a few attempts and maybe get a guide going.
Click to expand...
Click to collapse
I understand that CVE-2013-2094 has been ported to work (escalate to r00t) on Android devices. I don't know if this model has "performance events" turned on but, if so, could this be an opportunity to get # on our tablets?
Also, I have a way to kick off processes as system. Could that help us?
buford said:
I understand that CVE-2013-2094 has been ported to work (escalate to r00t) on Android devices. I don't know if this model has "performance events" turned on but, if so, could this be an opportunity to get # on our tablets?
Also, I have a way to kick off processes as system. Could that help us?
Click to expand...
Click to collapse
I need to subscribe to this thread. Sorry about the delay. I have been playing with the idea of flashing the GT-5100 firmware, but there is no way back to stock if things go bad. I think I'm going to be more proactive and talk with the local Sprint store to see if I can get that firmware / bin from them. The fact that the development community for this device is so dead is a bit eerie.
FluffyMittens said:
I need to subscribe to this thread. Sorry about the delay. I have been playing with the idea of flashing the GT-5100 firmware, but there is no way back to stock if things go bad. I think I'm going to be more proactive and talk with the local Sprint store to see if I can get that firmware / bin from them. The fact that the development community for this device is so dead is a bit eerie.
Click to expand...
Click to collapse
I sent you a couple PMs with more information. Not sure if they actually got to you.
Long search but - Cydia Impactor will take care of root for that Tab 2! Just follow that up adding busybox and all of the other root goodness!
Thanks Jay!!!
Instructions: Just Run it!
MrDavis
MrDavis said:
Long search but - Cydia Impactor will take care of root for that Tab 2! Just follow that up adding busybox and all of the other root goodness!
Thanks Jay!!!
Instructions: Just Run it!
MrDavis
Click to expand...
Click to collapse
Great. Any more information on this? Links?
More info
Sure! Google search 'cydia impactor' and pick the first link. That is just about as technical has I can make it
MrDavis said:
Sure! Google search 'cydia impactor' and pick the first link. That is just about as technical has I can make it
Click to expand...
Click to collapse
Haha, sorry about that. I will test it tonight. Maybe write up a script to automate this. Thank you so much for sharing this information.
FluffyMittens said:
Haha, sorry about that. I will test it tonight. Maybe write up a script to automate this. Thank you so much for sharing this information.
Click to expand...
Click to collapse
Use cydia installer to root then use http://forum.xda-developers.com/showthread.php?t=2101044&highlight=sprint to get cwm
sph-p500 Rooted!
MrDavis said:
Sure! Google search 'cydia impactor' and pick the first link. That is just about as technical has I can make it
Click to expand...
Click to collapse
I can also confirm cydia impactor works and is really as easy as downloading to pc run impactor hit startband it installsnsuper su right to the root of the tablet after that I have been able to successfully install (titanium, busybox, , link2sd, rom manager) and they all have root access
I have also been able to download mobile terminal and at $ prompt put in (su) and # should show letting you know you now have root access
after that I have also been able to change the default storage to ext2 by using. pm set-install-location 2, from # prompt and using link2sd to move apps 2 extsdcard for those of you that have an 8 gigger like I do I hope this helps im still alittle new to android
Any custom roms found for this tablet? I googled and I could only find rooting method but no custom roms (e.g. kitkat) for this tablet. Can the P5100 ones be used instead? I don't need the 4G service.
cydia impactor isnt recognizing the device. usb drivers fully installed and all that... kinda weird
nevermind. it worked!!! now i just need to install recovery and find a darn ROM LoL
I just received my Sprint SPH-500, and wouldn't have known it's a nonstandard Galaxy Tab 2 variant without this thread. I rooted mine with Towelroot, so I still have a locked bootloader, but full root access. AFAIK, my flash counter hasn't been triggered.
Here;s a screen capture of my downloading screen. It shows I haven't done a custom binary download (what triggers the flash counter), and I'm not running a custom binary, as I'm running the Samsung Official binary. But it does show my system status is custom..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I should have progress to report on moving apps to my external sdcard and second partition soon.
After experimenting with Link2SD for more than a week, I gave up on it. It's just too unstable to be a daily driver. I only have the 8 GB model, and run several large data astronomy and birding apps, They left me with 800 MB free RAM on my internal SD storage, and I still had other apps to install.
Link2SD put apks, Dalvik-cache, and lib files on the second partition of my external SDCard, but lost the links a reboot or two later. It claimed to move 1.8 GB of files, but showed 14 GB of RAM used on my second partition. It lost user and system apps that were linked, unlinked, and lost, for instance, the Google Play Store Services.
I ended up using a symlinking app called Foldermount, similar to the old (unsupported) Directory Bind app. It stores data folders on my external SDCard, and symlinks them so my astronomy and birding apps think they're still stored on the internal SDCard. I've got all my apps installed, and still have nearly 3 GB internal SDCard RAM free.
Through a well executed chain of private messages I managed to get a hold of a shiny new leak for us S4 users, Don't know if it will help you AT&T users much, But I'd love it if it did. For now, this is for Canadian users only, and can be used (Confirmed with Bell, and Telus) with any carrier
Included in this package are a few things:
1) BL, AP, CP, and CSC files for Odin
2) Odin v3.09 to be used for flashing (Not confirmed to work with any other version, So why not have the latest? )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions for Flashing
Root: Latest version of CF Auto root HERE (Seriously, go buy that guy a beer. http://www.chainfire.eu/ )
As far as flashing the package goes, all files need to be put in their respective shots as per the screenshot, you may need to flash 2-3 times in odin to get the whole package in there, like with most custom -> stock transitions.
The updated bootloader is the only real bummer here, overall a very nice package, fully rootable, works with Wanam Xposed for any of those curious, with very little as far as incompatible modules I can see.
One key change I'm missing personally is the lack of adaptive auto brightness... Can no longer increment -5/+5 on your auto brightness setting
Anyway, enough about it for now, here is the package link. Screenshots will be posted in a few minutes.
https://mega.co.nz/#!h8pTnCZS!t2-PiSb5W9ZyNp7fct7WD_Pg_dnc-eZqtMvpsuKv_9Q <-- Now with 100% less pit file!
I know some people were doubting the legitimacy of this in the Canadian thread, but I just finally got permission to post the leak from my source, since it's not carrier specific, and doesn't tie back to any one specific person. Heh.
downloading right now, will install it asap.
Thanks a lot 0mega1
Interested in trying this out...wondering if anyone has noticed any bugs or general performance issues? Also is it responsive on the S4?
Thanks,
0mega1 said:
Through a well executed chain of private messages I managed to get a hold of a shiny new leak for us S4 users, Don't know if it will help you AT&T users much, But I'd love it if it did. For now, this is for Canadian users only, and can be used (Confirmed with Bell, and Telus) with any carrier
Included in this package are a few things:
1) BL, AP, CP, and CSC files for Odin
2) The appropriate PIT file for the Canadian 16gb model
3) CF Auto Root package for Odin(Latest version as of posting) -- HUGE Thank you to chainfire for all of his work. http://www.chainfire.eu/
4) Odin v3.09 to be used for flashing (Not confirmed to work with any other version, So why not have the latest? )
Instructions for Flashing
As far as flashing the package goes, all files need to be put in their respective shots as per the screenshot, you may need to flash 2-3 times in odin to get the whole package in there, like with most custom -> stock transitions.
The updated bootloader is the only real bummer here, overall a very nice package, fully rootable, works with Wanam Xposed for any of those curious, with very little as far as incompatible modules I can see.
One key change I'm missing personally is the lack of adaptive auto brightness... Can no longer increment -5/+5 on your auto brightness setting
Anyway, enough about it for now, here is the package link. Screenshots will be posted in a few minutes.
https://mega.co.nz/#!ghpAhaaK!eXjKiZvQy9aUvy54AhXXAl14DJGVrot1msb6XOUlhgw
I know some people were doubting the legitimacy of this in the Canadian thread, but I just finally got permission to post the leak from my source, since it's not carrier specific, and doesn't tie back to any one specific person. Heh.
Click to expand...
Click to collapse
dahlungril said:
Interested in trying this out...wondering if anyone has noticed any bugs or general performance issues? Also is it responsive on the S4?
Thanks,
Click to expand...
Click to collapse
Up until I hear otherwise it is literally running on two phones, aside from whatever there is internally.
I've had zero issues since I flashed it yesterday, and battery has been great.
Very nice. Thanks for uploading. Can someone please provide and upload a system dump of this ROM? Having trouble with my ext4.img extract tools since 4.3.
Thanks.
I noticed that the pit file isn't in the package anywhere!
dont use pit files unless you NEED a pit file.
quick way to bork your phone
always check the post count of the Uploader.
less than 200 ? I would not follow his instructions. And i would only flash his leak, if my post count was higher and I knew what to do without reading some "new guy's" instructions
TRusselo said:
dont use pit files unless you NEED a pit file.
quick way to bork your phone
always check the post count of the Uploader.
less than 200 ? I would not follow his instructions. And i would only flash his leak, if my post count was higher and I knew what to do without reading some "new guy's" instructions
Click to expand...
Click to collapse
OP probably took the files and infos from here: http://true-android.blogspot.ca/2014/03/i337mvlufnc1-android-442-kitkat.html
I don't care where he got it, my point is only experts should be flashing leaked firmware.
Or to put it simply if you need instructions, don't flash it.
Sent from my SGH-I337M using Tapatalk
I've installed this using Odin. Can't get the modem file to stick. I'm stuck on MK6 for baseband. Wifi doesn't work as a result.
Did a complete wipe of System, Cache, Dalvik and Data.
I've tried reflashing the modem file a few times but it's not sticking. I'm attempting a reflash of the entire ROM right now to see if that does the trick.
Edit: It stuck after a second flash. Wifi works now.
Relayers said:
OP probably took the files and infos from here: http://true-android.blogspot.ca/2014/03/i337mvlufnc1-android-442-kitkat.html
Click to expand...
Click to collapse
That's my ****ing screenshot. Are you for real? I can submit the full resolution one if you'd like.
I've leaked a full early release before...
http://forum.xda-developers.com/showthread.php?t=868829
That was the official went-to-public build for the Telus Fascinate... Same deal.
TRusselo said:
dont use pit files unless you NEED a pit file.
quick way to bork your phone
always check the post count of the Uploader.
less than 200 ? I would not follow his instructions. And i would only flash his leak, if my post count was higher and I knew what to do without reading some "new guy's" instructions
Click to expand...
Click to collapse
I fail to see how my post count indicated the quality of what the release. This isn't the first time I've posted a leak here, might be the last though... Apparently the content doesn't matter so much as who is doing the work nowadays.
Hey, I'm thankful for the leak.
So where is the .pit file in the package? Or can we flash this without the .pit?
Thanks!
aiton said:
So where is the .pit file in the package? Or can we flash this without the .pit?
Thanks!
Click to expand...
Click to collapse
You don't need the .pit file. The OP should remove that from the instructions. Otherwise it's running smoothly.
TLS2000 said:
You don't need the .pit file. The OP should remove that from the instructions. Otherwise it's running smoothly.
Click to expand...
Click to collapse
Oh, ok, thanks. And just another question, if we're not using the .pit file, we should also uncheck the repartition box? (because .pit files will only need to be used if a firmware update needs to change your partition layout). Or how did you do it?
Thanks for the info!
modem.bin
Is it possible to pull the modem.bin file from here? I am running another kitkat rom but with MK6 would like to try this one......
aiton said:
Oh, ok, thanks. And just another question, if we're not using the .pit file, we should also uncheck the repartition box? (because .pit files will only need to be used if a firmware update needs to change your partition layout). Or how did you do it?
Thanks for the info!
Click to expand...
Click to collapse
It fails for me Re-Partition checked or unchecked. Any suggestions?
thank you very much!
works great on I337M Telcel Mexico
ChantalCaron13 said:
It fails for me Re-Partition checked or unchecked. Any suggestions?
Click to expand...
Click to collapse
where does it fails ?
Hi guys
I know the creator of Newflasher has been removed, and so has his tutorial and useful information in the crossdevice section....
But does anyone have a good tutorial and also a confirmed working version of newflasher so that I can flash my XZP to a generic Australian version?
Really much appreciated!
Cheers
Hi!
I just flashed my XZP, read here
I used the tutorial here, except put all the *.sin files in the directory and flashed. This one kinda explains much more than yours Lorehaze
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16''
cheetah2k said:
I used the tutorial here, except put all the *.sin files in the directory and flashed. This one kinda explains much more than yours Lorehaze
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16''
Click to expand...
Click to collapse
not good to flash *.ta files sir
cheetah2k said:
Hi guys
I know the creator of Newflasher has been removed, and so has his tutorial and useful information in the crossdevice section....
But does anyone have a good tutorial and also a confirmed working version of newflasher so that I can flash my XZP to a generic Australian version?
Really much appreciated!
Cheers
Click to expand...
Click to collapse
I have both version stored on my mega account, linking below.
I recommend using the older version. I don't trust the most recent after he got banned.
Here's the older version.
Here's the most recent.
Thanks for your help guys. Flashing mine went smooth and easy
cheetah2k said:
Thanks for your help guys. Flashing mine went smooth and easy
Click to expand...
Click to collapse
did u exclude all .ta files??
Lorehaze said:
did u exclude all .ta files??
Click to expand...
Click to collapse
Yes
Do not use any of the *.ta files. Only copy the *sin files across (except for the userdata - but this made no difference anyways as my userdata was corrupt after the flash).
My aim was to change from Vodafone Australia, to Australian Generic (sony shop) firmware so that I would get all the latest updates quick, instead of waiting for carrier updates (which take ages).
I did not change countries.
So I used newflasher to do all the *.sin files from the Australian Generic firmware to the phone. After the first boot post flashing, I got the "your password is correct, but your user data is corrupt - Reset Phone" warning. I let it reset the phone, then before doing anything else, I powered it off and went to Sony Companion and then did a software recovery (full wipe and full 1.5gb flash) so that if there was anything I missed in the flashing, it would be picked up in the official Sony Companion flash.
Worked a charm. I used to do the a similar method with flashtool on the older Sony phones, especially where some user compiled FTF files had others userdata on them.
Cheers
cheetah2k said:
Yes
Do not use any of the *.ta files. Only copy the *sin files across (except for the userdata - but this made no difference anyways as my userdata was corrupt after the flash).
My aim was to change from Vodafone Australia, to Australian Generic (sony shop) firmware so that I would get all the latest updates quick, instead of waiting for carrier updates (which take ages).
I did not change countries.
So I used newflasher to do all the *.sin files from the Australian Generic firmware to the phone. After the first boot post flashing, I got the "your password is correct, but your user data is corrupt - Reset Phone" warning. I let it reset the phone, then before doing anything else, I powered it off and went to Sony Companion and then did a software recovery (full wipe and full 1.5gb flash) so that if there was anything I missed in the flashing, it would be picked up in the official Sony Companion flash.
Worked a charm. I used to do the a similar method with flashtool on the older Sony phones, especially where some user compiled FTF files had others userdata on them.
Cheers
Click to expand...
Click to collapse
Thanks for that dude, going to try that tonight to unbrand my Telstra XZP. Just a question though - Where you said to not use any of the *.ta files, and ONLY the *.sin files across - You mentioned you used all of the *.sin except userdata, but if I were to copy the userdata file over as well, would that matter or do anything bad?
Edit: Also - There's a *.ta file in the boot folder for the FW, do I exclude this also?
Guessing that excluding the *.ta files will ensure the TA partition will be left intact to not affect DRM, etc.
Thanks man.
laes443 said:
Thanks for that dude, going to try that tonight to unbrand my Telstra XZP. Just a question though - Where you said to not use any of the *.ta files, and ONLY the *.sin files across - You mentioned you used all of the *.sin except userdata, but if I were to copy the userdata file over as well, would that matter or do anything bad?
Edit: Also - There's a *.ta file in the boot folder for the FW, do I exclude this also?
Guessing that excluding the *.ta files will ensure the TA partition will be left intact to not affect DRM, etc.
Thanks man.
Click to expand...
Click to collapse
cheetah2k said:
Yes
Do not use any of the *.ta files. Only copy the *sin files across (except for the userdata - but this made no difference anyways as my userdata was corrupt after the flash).
My aim was to change from Vodafone Australia, to Australian Generic (sony shop) firmware so that I would get all the latest updates quick, instead of waiting for carrier updates (which take ages).
I did not change countries.
So I used newflasher to do all the *.sin files from the Australian Generic firmware to the phone. After the first boot post flashing, I got the "your password is correct, but your user data is corrupt - Reset Phone" warning. I let it reset the phone, then before doing anything else, I powered it off and went to Sony Companion and then did a software recovery (full wipe and full 1.5gb flash) so that if there was anything I missed in the flashing, it would be picked up in the official Sony Companion flash.
Worked a charm. I used to do the a similar method with flashtool on the older Sony phones, especially where some user compiled FTF files had others userdata on them.
Cheers
Click to expand...
Click to collapse
Hey I just followed your instructions, excluded all TA files including the one in the BOOT folde r- Worked perfectly as you said, just restored in Xperia Companion! Thanks mate!
laes443 said:
Hey I just followed your instructions, excluded all TA files including the one in the BOOT folde r- Worked perfectly as you said, just restored in Xperia Companion! Thanks mate!
Click to expand...
Click to collapse
Good news! enjoy
I'm currently developing a tool for XZP. I will integrate a working flasher and some other tools. What is still missing for me at the moment, is a working hack for the DRM. I've been biting my teeth for days. I am currently trying to understand the process better. I just look at the respective files in IDA and my head smokes. If someone finds a usable approach, let me know. I would integrate the whole thing into the tool.
What I can safely say is that previous versions of the DRM fix do not run, but still have an effect. Without DRM fix the Google camera runs almost without problems and the system camera makes green pictures. With the DRM fix the Google Camera makes green pictures. So the approach does not have to be wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sToRm// said:
I'm currently developing a tool for XZP.
Click to expand...
Click to collapse
You will make many people happy with your tool considering we desperately need a safe and reliable one!
I'm sure most would love to ditch NewFlasher as it's... not very safe considering who it comes from.
It would be amazing if you could release it asap when you feel it's stable.
I just picked up a new XZP Pink and I don't wanna use NewFlasher on it.
Keep up the good work :good::good:
This is android app, right?
Windows
Realy? Probably it will use new flasher? Or still newflasher?
This restore process is intended for the Tmob V60 (lmv600tm) model and you must WIPE your data so back it up if you want to keep it!
This process will restore the lmv600tm to the state directly after the ota upgrade to the a12 v30b build. I’ve dumped all the required partitions from a MY personal lmv600tm. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently unable to boot or who just can’t access Tmob ota services and wishes to upgrade their lmv600tm to the a12 build. I have only tried this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from a Android 10 rom but I haven’t tried it.
This process will not fix your erased or damage imei number problem.
Steps
Download “Lmv600tm v30b Restore Partitions.7z” file from ???? and unzip. Remember the unzipped restore directory path.
Download “DriverBootandFirehose.zip” file from here and unzip. Remember the unzipped location.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose from where you unzipped “DriverBootandFirehose.zip”.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.
When complete phone reboots as I recall.
Thanks for shareing
I have a LG V600AM , Can I use this backup file to upgrade my phone?
As per the op this is for the T-Mobile model. I haven’t tested on the AT&T model.
zhh said:
Thanks for shareing
I have a LG V600AM , Can I use this backup file to upgrade my phone?
Click to expand...
Click to collapse
We still need A12 Att modems in order to work or somebody on Att model that makes that same dump the full A12 system :/ sadly I don't know no one
krissrmx said:
We still need A12 Att modems in order to work or somebody on Att model that makes that same dump the full A12 system :/ sadly I don't know no one
Click to expand...
Click to collapse
The AT&T version has 30a as of now.I'll make a LUNS copy,and upload it some where if you want it?
surgemanx said:
The AT&T version has 30a as of now.I'll make a LUNS copy,and upload it some where if you want it?
Click to expand...
Click to collapse
Sure
I want backup imei and everything file partitions network need.
How to backup? And partition name ?
Userdata.bin is missing in the archive.
dprast said:
I want backup imei and everything file partitions network need.
How to backup? And partition name ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Partition Manager and backup those yellow ones and you should be good
krissrmx said:
View attachment 5627813
Download Partition Manager and backup those yellow ones and you should be good
Click to expand...
Click to collapse
Edit: Partition Backup
krissrmx said:
View attachment 5627813
Download Partition Manager and backup those yellow ones and you should be good
Click to expand...
Click to collapse
thanks your info.. i've subcribe unlocktool and backup all my ufs data for safety before unlocking and customized my phone but i've problem . my phone in android 12. May security path since ubl fingerprint not working how to fix them? and how to disable anti rollback?
very good , i updated it on verizon .thanks so much ...
thienton1689 said:
very good , i updated it on verizon .thanks so much ...
Click to expand...
Click to collapse
You're welcome
TheLoonyRebel said:
Userdata.bin is missing in the archive.
Click to expand...
Click to collapse
You won't need userdata on a reflash.
zhh said:
Thanks for shareing
I have a LG V600AM , Can I use this backup file to upgrade my phone?
Click to expand...
Click to collapse
Did you manage to do this?
I can confirm that a LGV600Am -> LGV600TM works*. It is possible to crossflash a ATT (A10) to T-Mobile (A12) LG v60!* Yay and TY. As stated elsewhere good luck with 5G. It is suspected T-Mo is blacklisting LG now? My FingerPrint reader is broken. I had to use a weird hidden menu trick on the stock Att A10 when bootloader unlocked. This guide worked perfect except the firehose! Someone is handing out the prog__ufs_firehose_sm8250_ddr.elf and not correct file named prog__ufs_firehose_sm8250_lge.elf! I kept getting QFIL errors! I attached the proper version. Its getting hard to find for free!
Still learning about treble generation. Thanks for the dump! Hopefully there is a newer june/july update.
PS: Welp unlocked bootloader causes failed update & lg switch key attestation/ key deleted error. I would appreciate any help w/ 5G would be nice but not needed.
*= Broken 5G and No Fingerprint registration.
Bug725 said:
I can confirm that a LGV600Am -> LGV600TM works*. It is possible to crossflash a ATT (A10) to T-Mobile (A12) LG v60!* Yay and TY. As stated elsewhere good luck with 5G. It is suspected T-Mo is blacklisting LG now? My FingerPrint reader is broken. I had to use a weird hidden menu trick on the stock Att A10 when bootloader unlocked. This guide worked perfect except the firehose! Someone is handing out the prog__ufs_firehose_sm8250_ddr.elf and not correct file named prog__ufs_firehose_sm8250_lge.elf! I kept getting QFIL errors! I attached the proper version. Its getting hard to find for free!
Still learning about treble generation. Thanks for the dump! Hopefully there is a newer june/july update.
PS: Welp unlocked bootloader causes failed update & lg switch key attestation/ key deleted error. I would appreciate any help w/ 5G would be nice but not needed.
*= Broken 5G and No Fingerprint registration.
Click to expand...
Click to collapse
I update my T-Mobile version from A11 to A12 and encounter the same problem.
Using the .elf file from https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ (probably the same as you provided because both files share the same name) and updated the system successfully.
The bootloader unlock state is perserved (unlocked). However, I also find that the fingerprinter is broken (Enrollment was not completed: Fingerprint enrollment time limit reached).
Edit:
Fingerprint can be fixed by following the guide in https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/
Thanks above for this and to OP for the original walkthrough this saved my bootlooped device! Took me a couple tries to get QFIL to start the process but it worked for me.
Also if you're a v60 neophyte like me you can follow the first 4 steps from the bootloader unlock thread to get QFIL setup to run the OP's restore process.
showgood163 said:
I update my T-Mobile version from A11 to A12 and encounter the same problem.
Using the .elf file from https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ (probably the same as you provided because both files share the same name) and updated the system successfully.
The bootloader unlock state is perserved (unlocked). However, I also find that the fingerprinter is broken (Enrollment was not completed: Fingerprint enrollment time limit reached).
Edit:
Fingerprint can be fixed by following the guide in https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/
Click to expand...
Click to collapse
Yeah the FP doesnt work period (or random) on custom roms. 4got that part. I was able to get it working prior with a different post about accessing testing/service menu on Stock ROM. Ty anyway. I cannot type on laptop anymore b/c touch phone. Seems hit & miss. Im going to do a full kdz restore. I will be able to download the latest update. I may link it when I do.
My thinking is the a/b schemes. So I am super grateful for the flash files. I did some minor prodding and the files were initially for EA series. I saw build props & stuff that said so. My thinking is there is a Vendor &or Product partition update thats needed. Most likely a full up to date Vendor from US carriers.
Unfortunately an unlocked boot-loader deletes Google Certs. This is because the (unlock magic) Engineering or Test BL thats around is not signed or more likely not matching the rest of the boot chain.
I dont really know of a better way to access 5G info other than the *#INFO or phone util app.
I choose NR/LTE, then menu select band. Now interesting things happen here. Selecting US gets LTE but if I select Auto then I get LTE+...
jeez all of this b/c my replacement Note10+ was locked and unlock dude died from COVID (or is being held by Samsung all Umbrella Corp style). Apparently nobody else has the keys or license.
lastly sorry about length & incompleteness of dialer codes. I said yeh lets update Corvus using updater. When it was done it said done & slot switched! My other partition was full stock! Now I got bootloops. Im experimenting w/ dualboot...
Bug725 said:
Yeah the FP doesnt work period (or random) on custom roms. 4got that part. I was able to get it working prior with a different post about accessing testing/service menu on Stock ROM. Ty anyway. I cannot type on laptop anymore b/c touch phone. Seems hit & miss. Im going to do a full kdz restore. I will be able to download the latest update. I may link it when I do.
My thinking is the a/b schemes. So I am super grateful for the flash files. I did some minor prodding and the files were initially for EA series. I saw build props & stuff that said so. My thinking is there is a Vendor &or Product partition update thats needed. Most likely a full up to date Vendor from US carriers.
Unfortunately an unlocked boot-loader deletes Google Certs. This is because the (unlock magic) Engineering or Test BL thats around is not signed or more likely not matching the rest of the boot chain.
I dont really know of a better way to access 5G info other than the *#INFO or phone util app.
I choose NR/LTE, then menu select band. Now interesting things happen here. Selecting US gets LTE but if I select Auto then I get LTE+...
jeez all of this b/c my replacement Note10+ was locked and unlock dude died from COVID (or is being held by Samsung all Umbrella Corp style). Apparently nobody else has the keys or license.
lastly sorry about length & incompleteness of dialer codes. I said yeh lets update Corvus using updater. When it was done it said done & slot switched! My other partition was full stock! Now I got bootloops. Im experimenting w/ dualboot...
Click to expand...
Click to collapse
I also found that OTA updates fails w/ unlocked bootloader (didn't test on locked bootloader). Because of that I even don't have the chance to change the slot. I thought that it was the R/O system partition that caused the problem.
'unlocked boot-loader deletes Google Certs', I don't know the consequence of deleted Google Certs, willing to explain more?
I currently don't have a 5G SIM so I can't have a test on 5G problem.