Hey!
With the new root / unlock that I managed to get on my F800L, I was wondering if anyone thinks it would be possible to get the US996 ("unlocked") ROM working on my phone? (note: it's a spare that i got for free, so I'm happy to try, even if it means I might brick it)
I'll be honest, I have no idea what I'm doing, but I've already started trying, and I thought I'd managed to do it, until the phone started rebooting on me.
To start, I downloaded the US996 deODEXd ROM from here, and installed it, via TWRP. After that, I wiped data, and advance wiped dalvik/data/cache, before installing SuperSU. I then re-wiped dalvik & cache (I was basically re-doing step 4 onwards in the twrp+ section of me2151's Dirtysanta unlock and root guide, from what I could remember...) After that, I rebooted to bootloader, flashed the boot2.img from that guide, and rebooted.
...and it started up fine, and I got to the setup wizard (where it now tells me that it's a US996, instead of F800L).
The problem starts here. If I rush through the wizard, I can complete it and get into the operating system, and I can see what the problem is (if not, it reboots and I have to start the wizard again). There's an "android is upgrading" progress bar in the notification menu. Once that completes, the phone reboots. Apart from that, it seems like everything else works............... as far as I can tell, because the phone reboots after 15 seconds or so, and it gets quicker each time I reboot... although if I go into fastboot, and wipe userdata, I can start from the wizard, again.
I've managed to get a 4G (LTE) Signal, made a short call to check it worked & wifi seems to be working. I managed to turn developer options, and adb debugging on, too, so I can reboot into recovery. (I tried re-flashing supersu, like in the guide, to see if it did anyhting, but no (I don't know if it should, but like i said, I have no idea what I'm doing)).
Anyone have any ideas that I could try? Or is it likely not going to work, and I'm an idiot for trying? (it's cool, I know, I embrace it)
I'm assuming that if there's a way to stop it from trying to upgrade, permanently, then it might stop rebooting? but, obviously... I have no idea what I'm doing, so if there's a way to do that, I don't know how.
Thanks!
Update: Managed to install stock H918 onto my F800L and it works perfectly. Same method as above.
Screenshot:
{
"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"
}
Hi, Is it working perfectly yet?
I want to try also on my F800L..
Dear ad,
How to root/unlocked the F800L variant?
I want to try also on my F800L.
Thanks!
I'm wondering if this will work on my Sprint 997
Could someone post detailed steps on how to do this? I have the F800L version and would like to flash a US rom on it. Mainly because my vaoicemail doesn't work, some of LG's apps ignore the system language and still show Korean, etc..
any news???? can i install a custom rom based on h918 variant on my f800l????
is it fully functional?, can u make a tutorial step by step please, there was so very few topic about F800l variant, it would be awesome if u could help.
Does this work on a f800k?
Sent from my LG-F800K using Tapatalk
I have do step by step in the instrustion dirty santa to unlock/root my f800l but i stuck at the step type id in terminal on phone, nothing to show, i repeat from step 1 for many times but it too, please help me. Sorry for my bad English
JvvB126 said:
Update: Managed to install stock H918 onto my F800L and it works perfectly. Same method as above.
Screenshot:
Click to expand...
Click to collapse
Please help me how to do it
Is F800K possible?
Related
I can find several how-to's about moving from rooted 4.4.2 to 4.4.4 and stay rooted. But none of them work. Either I can get 4.4.4 to run, but can't root it (towel root won't do 4.4.4, I know that), or I can root 4.4.2, but applying an NI2 kernel leaves me staring at the Sammy S5 splash screen. No Sammy animation, no VZW red screen of boredom, nothing. I tried wiping cache and doing an FDR. No change. What am I doing wrong???
Tried CF Auto Root?
It'll trip KNOX, but if you're not bothered, it should work
The certainly is an option. Noway this S5 will ever see the inside of a VZW store.
I am, however, baffled as to why following the how-to's utterly fails. I have an extensive collection of flashable files, thanks to how-to's that say "use these files from Sammobile", and the ones that have them coming androidfilehost, and on and on. Worse, I have no idea if, for example, all of the NCG files are really the same thing with a different name or not. Meaning I'm really doing the same series of steps with only the names changed. Odin never says FAIL!, finds the device, it validates the md5 checksum, does its magic, and says PASS!. NTL, the phone either bootloops or otherwise doesn't do what it should. At the moment, wiping cache and doing a reset doesn't clear the problem (the S5 stops at the power-up splash and doesn't do so much as the Samsung animation).
Either all of the how-to's are bogus, which seems unlikely, the files listed below are all somehow defective but have good MD5 checksums (also unlikely), or there is something really odd about my phone. The only thing I can think of is I'm doing all of this without an SD installed. I can't see how that would be a problem. I can't imagine the SIM is a bad actor (I do get the right phone number after doing an FDR, BTW). So what's up?
Because things are so wonky, I'm a little uncomfortable with trying CF Auto Root, only to find I managed to brick the phone because of whatever weirdness seems to lurk somewhere in this project.
For laughs and grins, here's the collection to date:
{
"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"
}
Ahh, your S5 is on Verizon ?
Bootloaders are locked on those phones, so you won't be able to root or custom recovery using ODIN
Towelroot for 4.4.2 ROMs prior to June 2014 will work
This is, indeed, an SM-G900V from VZW. The how-to's (links follow) are for the same device. Odin works, to the point where 4.4.4 and 5.0 are functional. Even the WiFI problem, discussed earlier, takes "only" an FDR to put it right. Towelroot works for 4.4.2. What doesn't work is carrying rooting forward to 4.4.4 or, ideally, 5.0 (sure would be nice to extend to 5.1).
http://forum.xda-developers.com/showpost.php?p=55495211&postcount=1
http://www.droidviews.com/update-verizon-galaxy-s5-android-5-0-lollipop-retain-root/
http://androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/
http://forum.xda-developers.com/ver.../safely-upgrade-root-4-4-4-nha-volte-t2879348 [ADDED]
Again, either all of these items are bogus, I'm doing something wrong, or the phone is not 100% healthy.
Success! I've at least left 4.4.2 behind for rooted 4.4.4. This is the how-to I followed:
http://forum.xda-developers.com/showpost.php?p=55495211&postcount=1
As best I can tell, the moment of actually rooting has the phone thinking it's running 4.4.2, thanks to the kernel, but it's somewhat in the 4.4.4 world, too. At least that's my ill-informed guess about how/why this hack works.
Of course, now it's on to trying to retain root under 5.0. At least, should 5.0 tank, I now know how to get back to a rooted 4.4.4.
I tried looking everywhere but I have a Galaxy S6 Edge+ which took an OTA and got into a boot loop, nothing helps at all. I tried to ODIN Pl1 version I found but it won't get past the application optimization part with the gears before it shuts off and restarts again. I also found the PC2 version, but it won't even flash for me, that version fails, maybe because it's older than Pl1?
I just need to locate the latest file and associated PIT that I can flash on the Verizon device. I think the partitions are possibly jacked up.
I also don't want to pay an arm and a leg for the firmware.
Any help is appreciated!
I have been able to get a PF2 firmware as well, I place it in the AP area (PDA) and once connected, hit Start and the thing keeps failing, just like it did with PC2. When I do the Pl1 version though it actually goes all the way through, what gives?
{
"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"
}
Any help would be great.
ssconceptz said:
I have been able to get a PF2 firmware as well, I place it in the AP area (PDA) and once connected, hit Start and the thing keeps failing, just like it did with PC2. When I do the Pl1 version though it actually goes all the way through, what gives?
View attachment 3969966
Any help would be great.
Click to expand...
Click to collapse
Did you try emergency recovery with smart switch?
ssconceptz said:
I tried looking everywhere but I have a Galaxy S6 Edge+ which took an OTA and got into a boot loop, nothing helps at all. I tried to ODIN Pl1 version I found but it won't get past the application optimization part with the gears before it shuts off and restarts again. I also found the PC2 version, but it won't even flash for me, that version fails, maybe because it's older than Pl1?
I just need to locate the latest file and associated PIT that I can flash on the Verizon device. I think the partitions are possibly jacked up.
I also don't want to pay an arm and a leg for the firmware.
Any help is appreciated!
Click to expand...
Click to collapse
What's the version that you've got by ota? Just flash that version(must be latest in case), try to boot if it doesnt; boot into stock recovery; wipe cache/dalvik, factory reset(I dont remember which options were there). The fact is; bootloaders of latest firmwares are lock up which means you can't downgrade even previous one you've been using. Custom roms would helpful to get rid of that bootloop but don't know if its available for Verizon devices. Good luck.
Please bear with me as this may be a biblical post
Around 3 weeks ago I bought a nice shiney new Huawei P9 Lite from CPW in the UK. Out of the box the phone was listed as VNS-L31C432B131 with EMUI 4.0 . The first thing I did was read all the various bits and bats on different threads about updating and custom roms. Then I unlocked the bootloader, installed TWRP and also rooted my phone.
I was then reading about one version of nougart so installed Meticulus TWRP in preperation to install that rom, however due to working 14 hrs a day I didnt get chance to do it being so tired.
A little while later I saw a thread on updating to B160 which would then give me the HiCare update to B370 through OS early update.
So the other day I fired up Firmware Finder and pushed the update ( via FF proxy ) to the official update app and moved from B131 to B160 with out any issue. During the " upgrade " I saw no errors or warning messages and nothing exploded so I thought all was good.
The next evening I went into HiCare and saw I could update from B160 to B370, so I did and again everything seemed to go fine. Although at the end I had no root so my Viper4Android mod wouldnt work. No biggy I though....Ill just root it again and go from there.
I then noticed I was on build version : NRD90M test-keys and I had some missing apps ie themes etc
{
"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"
}
Also on my app drawer the settings Icon has a red 1 on it.
Most of my phone seems to work ok but as I am missing various apps and some functions are not working I have tried to fix it. I downloaded update_data_full_VNS-L31_hw_eu.zip but I can't flash it as I have lost TWRP.
If I boot with all three buttons held I get the standard software installation failed screen, even though I have placed the above file into the root of my phone, in to a folder called " dload " and into a separate " dload " folder on my external SD card.
If I press Vol up and power, I can get my standard recovery screen with the three opions reboot, wipe data/factory reset or wipe data partition
Pressing Vol down and power achieves nothing.
No matter what I do I cant get into TWRP to try and flash the above update file to get all my apps and functionality back.
I have even tried to go back into Firmware Finder to see if there is an update package available for me but I can't get that to work either as I get a cant reach the server error.
When I try to set up the proxy it is asking me to sign into my internet connection(??)
It seems I have somehow ballsed things up in an epic way while still keeping a semi working phone. So my only option is to take the phone back to CPW and exchange it for a new phone ( hopefully already on nougart or at least B160 ) however while ever I get the warning message about my device being locked I doubt they will take it back.....
So is there a way to be able to lock the bootloader again so I can take it back?
Or could someone please help me get out of NRD90M test-keys and get everything working again with root so I can install Viper4Android again.
You should've tried searching. You can rollback to MM B160 using official Huawei guide. Make sure your update package has 3GB size, as it's the complete MM with all the apps. Then you'll be able to update to B370 through firmware finder.
you need to plugin your cable in some cases .. e.g. to enter fastboot mode.
I have tried to relock the bootloader with ADB etc however I get remote access denied errors.
I see things are still fairly alive for this phone. I have a quick question about updating. I just powered my phone back on tonight after it being off for several years due to upgrades and what not. Long story short, my intent was to only use it as a means to port a Magic Jack number to Google Voice via a pay-as-you-go service.
Currently, I have a Net10 Wireless sim in the phone, and my MJ# has been ported successfully to this provider and the phone works. Of course I brain-farted and checked for software updates, and the phone successfully connected to the AT&T servers and downloaded an update (I haven't installed it though). As far as I can remember, all I did to this phone back in the day was to root it, I don't think I installed any CFW. Here's a photo of the about screen, anyone have any insight? From what I've gathered it's factory ATT firmware.
I guess my question is, do I allow the firmware update to continue? Will it even succeed if my phone is rooted? Is it even worth it to update? I may keep the phone on Net10, at least for a bit, but I may still just finish porting the number to GV and be done with it...fewer phones to carry around and all.
Thanks guys!
{
"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"
}
Raven2k360 said:
I see things are still fairly alive for this phone. I have a quick question about updating. I just powered my phone back on tonight after it being off for several years due to upgrades and what not. Long story short, my intent was to only use it as a means to port a Magic Jack number to Google Voice via a pay-as-you-go service.
Currently, I have a Net10 Wireless sim in the phone, and my MJ# has been ported successfully to this provider and the phone works. Of course I brain-farted and checked for software updates, and the phone successfully connected to the AT&T servers and downloaded an update (I haven't installed it though). As far as I can remember, all I did to this phone back in the day was to root it, I don't think I installed any CFW. Here's a photo of the about screen, anyone have any insight? From what I've gathered it's factory ATT firmware.
I guess my question is, do I allow the firmware update to continue? Will it even succeed if my phone is rooted? Is it even worth it to update? I may keep the phone on Net10, at least for a bit, but I may still just finish porting the number to GV and be done with it...fewer phones to carry around and all.
Thanks guys!
View attachment 4778717
Click to expand...
Click to collapse
Do NOT update! You are on the MDB bootloader which can take advantage of the loki exploit and allow you to run TWRP custom recovery and ROMs once rooted. If you update the exploit gets patched and you are stuck with root and safe strap recovery which can boot only touch wiz ROMs. Use the towel root app to root, then follow my guide to get a custom recovery here: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
I know it says MDL bootloader, but MDB and MDL are pretty much the same. Both can use loki. If you want, you can update to MDL but don't update past that or else you'll lose the magic that is loki doki.
Hello. I installed CleanPie from this forum, and the instalation went Ok. I then noticed that I have no SIM, no IMEI, nothing regarding the carrier network.
I already tried creating a IMEIRepair.zip like some tutorials say, to flash on TWRP, but no change. I decided to revert back to Stock ROM, but when I run Odin with the Stock ROM files, it runs in 2 seconds, says Ok, and makes absolutely no change.
{
"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"
}
Can anyone help me with this? Any alternative way to restore to Stock ROM?
Soubesses said:
Hello. I installed CleanPie from this forum, and the instalation went Ok. I then noticed that I have no SIM, no IMEI, nothing regarding the carrier network.
I already tried creating a IMEIRepair.zip like some tutorials say, to flash on TWRP, but no change. I decided to revert back to Stock ROM, but when I run Odin with the Stock ROM files, it runs in 2 seconds, says Ok, and makes absolutely no change.
Can anyone help me with this? Any alternative way to restore to Stock ROM?
Click to expand...
Click to collapse
Some feedback on this thread. I know this is stupid, and I can't be sure if this was the problem, but I ran Odin as administrator, and I'm getting another error, the device 6 binary 5, which means I don't have the latest stock rom to flash on Odin. So if anyone has this problem of it loading too fast, and finishing in 2 seconds, try running it on Administrator.
Download the latest firmware for your model. There is a newer version for you. Flash it with odin..then reboot. After that flash twrp.go to twrp without rebooting, now back up boot,modem and efs,cpfs files. Flash clean pie. Reboot..there will not be any signal or imei. If so reboot in to twrp and restore the boot modem efs and cpfs now reboot..now it should show imei and signal..
Other option is change helios kernel with the rom to any other kernel like cronos or kraken..it is so easy..done