Thanks to simonsimons34 we now have a kernel compatible with Virgin Mobile's recent FOTAs (new radio and new hboot) AND supports overclocking!!
This kernel is for Sense-based ICS ROMs, however one for AOSP-based ICS ROMs (i.e. CM9) can be found in this post.
In fact, this is the exact same kernel - I just used the RAMDISK from Virgin's most recent FOTA to make it compatible with Sense-based ROMs.
So, if you use it, PLEASE give Simon a thanks in the post I linked.
What the FOTA?!?
Firmware Over-the-Air (FOTA) is used for upgrades to mobile phones and tablet computers. The feature goes by several names including Software Update, Firmware Update or Device Management. Originally, firmware updates to a device required visiting a specific service center, with every mobile brand having their own service center. Another method of receiving updates has been by connecting the device via a cable to a PC. Both of these methods were considered inconvenient by consumers and also relied on consumers actively seeking out updates. Therefore the majority of mobile device manufacturers and operators have now adopted FOTA technology for their handsets. If the mobile device has FOTA capability, firmware updates are issued directly "over the air" from the mobile phone service provider to the device. FOTA also allows manufacturers and operators to "push out" firmware upgrades to ensure that mobile consumers have the latest software improvements, which reduces potential customer support costs and increases consumer satisfaction.
From Wikipedia
Instructions for flashing (kernel only)
Download attached boot.img
Flash boot.img in fastboot "fastboot flash boot boot.img"
Instructions for flashing (ROM & kernel)
Follow the instructions of the Sense-based ICS ROM you want to install with the following amendment:
When flashing the boot.img in fastboot, use the one attached.
Credits and Thanks:
simonsimons34: for compiling the kernel and implementing the necessary changes to make it support VM's updates. (Basically all the heavy lifting) You ROCK!
russellvone: for testing and supplying the updated modules from the FOTA.
All the people developing for this device: You're why we're here.
Known Issues*
Bluetooth is spotty at best and won't always pair with devices.
Phone won't display "Charging" status when plugged in (though it will actually charge)
Changelog
5/07/2013: Rebuilt Kernel+Ramdisk so it no longer needs a flashable ZIP (thanks again to Simon for the instructions).
5/02/2013: First Release
*Important Notes
This Kernel is essentially provided "as-is".
Fixing the items under known issues would essentially require someone who possess the knowledge recompiling the kernel from source and I do not possess that knowledge.
This is simply a port of the AOSP kernel Simon made for this device to be usable on Sense ROMs and those issues could exist in both kernels or just simply be caused by "porting" the kernel.
@demoport has posted a work-around for the Bluetooth issue in this thread. It can be found here.
Haha.. just did a instructional reply on Curiousn00b's myOne thread. Thanks for doing this -Duir-
I've been running this kernel/modules combination since you first asked me to test and its absolutely been stable for all the hard usage i put my phone through.
Thanks a million simonsimons34 and
-Duir-
46 downloads on the flashable zip and no comments? I'm gonna take that as a good thing LOL :victory:
OP has been updated. Hopefully removed the need for a flashable zip, just fastboot flash the boot.img. If for some reason it's not working like it was/should let me know, I'll put the original flashable zip back.
The kernel works ok, the only issue I've noticed is a very slow charge rate. Even when plugged into AC, it charges at the slow USB rate.
riggerman0421 said:
The kernel works ok, the only issue I've noticed is a very slow charge rate. Even when plugged into AC, it charges at the slow USB rate.
Click to expand...
Click to collapse
I wouldn't be surprised if that's somehow tied into the charging status not showing.
Sent from my hTC One V.
Updated op fix the non charging display?
Sent from my HTC One V using Xparent BlueTapatalk 2
russellvone said:
Updated op fix the non charging display?
Sent from my HTC One V using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No. Just removed the need for flashable zip.
Sent from my hTC One V.
getting half the battery life i got on jmz ics:\
-Duir- said:
46 downloads on the flashable zip and no comments? I'm gonna take that as a good thing LOL :victory:
OP has been updated. Hopefully removed the need for a flashable zip, just fastboot flash the boot.img. If for some reason it's not working like it was/should let me know, I'll put the original flashable zip back.
Click to expand...
Click to collapse
Would you be able to put the .zip back up again? I think there might be some modules in the .zip that are needed to get bluetooth working correctly. With this kernel, I can get the head unit in my car to pair, but it will never connect. I've tried it with both the myOneV and x3reme Sense v5 ROMs.
Both of those ROMs do connect fine with bluetooth if I use the OTA kernel and modules from the x3reme Sense v5 ROM, but I prefer being able to overclock with this kernel, and choose a governor other than ondemand.
I'm doing some play testing right now with the kernel and different ROMs and running stock, once done I'll post full findings.
I just ran the RUU and flashed the kernel to see what happens.
I gotta say, was rather surprised by them.
Charging Status: Working
Bluetooth: Working
{
"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 after using myOneV for so long now it was nice to see that 3G icon again - oh how I've missed you. :laugh:
(Can't see it in the pic as I was testing to make sure Wi-Fi worked.)
MormegilND said:
Would you be able to put the .zip back up again? I think there might be some modules in the .zip that are needed to get bluetooth working correctly. With this kernel, I can get the head unit in my car to pair, but it will never connect. I've tried it with both the myOneV and x3reme Sense v5 ROMs.
Both of those ROMs do connect fine with bluetooth if I use the OTA kernel and modules from the x3reme Sense v5 ROM, but I prefer being able to overclock with this kernel, and choose a governor other than ondemand.
Click to expand...
Click to collapse
Attached to this post as requested, please let me know your results.
Well upgraded to new radio, Bluetooth is working and as expected the charging status is wonky. Only the notification LED changes to indicate a charging status, all the software-specific indicators (battery icon, power option in settings) think phone is discharging still. Gonna have a look at what files get changed by the FOTA.
-Duir- said:
Attached to this post as requested, please let me know your results.
Click to expand...
Click to collapse
Using the modules and kernel from the .zip didn't seem to help my bluetooth problem. I read in the other thread that clock speed (or lack thereof) can affect bluetooth pairing/connecting, so I tried all 6 of the following combinations with identical failing results: [245/1024,1024/1024,1200/1200] x [ondemand,smartassV2]
Changing back to the x3reme OTA kernel and modules, bluetooth connects immediately with clock speeds of 245/1024 and 1024/1024.
In case it helps, the bluetooth module is a Dual BTM60, and the vendor identifier portion of the bluetooth MAC is 00:13:7B
I'll be looking into the Bluetooth next, my attempts with charging status have determined it is something to with the kernel and the radio (or some other hidden nugget) in the FOTA. Every file the FOTA changed I flashed back the original versions off and it made no difference. The kernel displays charging status with the .0521_2 no problem but not with the .0928 and the stock kernel of course displays a charging status.
So yeah, given up on that and moving on to Bluetooth now, will report back if I find anything out.
-Duir- said:
I'll be looking into the Bluetooth next, my attempts with charging status have determined it is something to with the kernel and the radio (or some other hidden nugget) in the FOTA. Every file the FOTA changed I flashed back the original versions off and it made no difference. The kernel displays charging status with the .0521_2 no problem but not with the .0928 and the stock kernel of course displays a charging status.
So yeah, given up on that and moving on to Bluetooth now, will report back if I find anything out.
Click to expand...
Click to collapse
Hey, I just RUU'd and updated to the newest update... I'm still on whatever stock kernel it comes with after the RUU and everything is working fine.
My question is: Is there a way to get this stock boot.img so I can flash it later if I want to flash this kernel so I can overclock, but I may want to go back to this kernel someday.
Can I pull it from a nandroid backup through TWRP?
lilrob1213 said:
Hey, I just RUU'd and updated to the newest update... I'm still on whatever stock kernel it comes with after the RUU and everything is working fine.
My question is: Is there a way to get this stock boot.img so I can flash it later if I want to flash this kernel so I can overclock, but I may want to go back to this kernel someday.
Can I pull it from a nandroid backup through TWRP?
Click to expand...
Click to collapse
The easiest way is something you need to do in advance. Which is copy the FOTA zip file off your SD card before you run the update (because it gets erased afterwards) and then you can pull the stock boot.img from there.
For TWRP it will backup the boot.img if you instruct it to, but I'm unsure of what needs to be done to make into a fastboot flashable format (i.e. a simple rename).
That being said I have a copy of both FOTA zips and can supply it if needed, and they can also be found here
-Duir- said:
The easiest way is something you need to do in advance. Which is copy the FOTA zip file off your SD card before you run the update (because it gets erased afterwards) and then you can pull the stock boot.img from there.
For TWRP it will backup the boot.img if you instruct it to, but I'm unsure of what needs to be done to make into a fastboot flashable format (i.e. a simple rename).
That being said I have a copy of both FOTA zips and can supply it if needed, and they can also be found here
Click to expand...
Click to collapse
What FOTA zip was on my sdcard? I don't remember using one? why are there two fota zips?
lilrob1213 said:
What FOTA zip was on my sdcard? I don't remember using one? why are there two fota zips?
Click to expand...
Click to collapse
When your phone downloads the update it stores it on your SD card. There's two because the first one is the radio update, the second and most recent is the one that updates the hboot and makes using the RUU impossible.
-Duir- said:
When your phone downloads the update it stores it on your SD card. There's two because the first one is the radio update, the second and most recent is the one that updates the hboot and makes using the RUU impossible.
Click to expand...
Click to collapse
Oh... that makes sense... dang it! I wish I knew I could update the radio with the first update and skip on doing the second update so that I could still RUU if in trouble... now I'm screwed but yeah, can you PM me the FOTA zip for the second update so I can have the kernel?
lilrob1213 said:
Oh... that makes sense... dang it! I wish I knew I could update the radio with the first update and skip on doing the second update so that I could still RUU if in trouble... now I'm screwed but yeah, can you PM me the FOTA zip for the second update so I can have the kernel?
Click to expand...
Click to collapse
Done.
Ok so my attempts with Bluetooth haven't yielded any problems. I installed both the current versions of myONEv_RC9.5_FX+CDMA and x3remeSensev5_OTA and Bluetooth worked on first try with each. I'm streaming music to my BT speakers as I write this. I've only updated to the newest radio, not the newer hboot, but I can't imagine that update breaking Bluetooth somehow.
Related
WARNING: From koush' IRC channel it seems this version may be (permanently?) bricking devices.
At the time of this writing only a single working flash has been reported, and several (full?) bricks.
--Chainfire
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
{
"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"
}
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
932e5f7a9f09c9bc33b14a527f642933
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Wow!... Looks great!
Wanna try after going back home!
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Koush said:
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
Installation instructions:
Install Odin3
Start Odin3
Press PDU
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Click to expand...
Click to collapse
Can I assume this kernel wasn't compiled with ext3/4 support?
achio1115 said:
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Click to expand...
Click to collapse
I'm guessing, but considering this replaces the zImage that mimocan's fix provides anything you have on moved to ext3/ext4 will not be accessible.
To reverse reflash with the mimocan kernel.
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Chainfire said:
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Click to expand...
Click to collapse
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
damianarnold said:
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
Click to expand...
Click to collapse
I can confirm that, this mod won't work if you have mimocan's kernel applied.
Does it work if you "unapply" it ? Can you get your phone back functional again ?
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
raspdeep said:
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
Click to expand...
Click to collapse
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
damianarnold said:
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
Click to expand...
Click to collapse
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Chainfire said:
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Click to expand...
Click to collapse
Every single app. you've installed will need to be reinstalled, it's as if the device is completely cleared of any settings/config.
Basically you need to restore from backup.
If you see this screen
follow these commands while odin3 is opened.
"SIM+SD out, put the battery in. Plug in USB. Hold down both Volume keys, and then push power. Hold it. From the phone > pc screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power. " That should put you in download mode so you can install the recovery again.
Then flash this kernel to fix any slowness
http://android.eugenekay.com/Vibrant/LeshakKernel_9_01b9.tar
Eugenekay couldn't link because he only has 4 posts so I'm doing it for him
This might not apply to i9000 users but I posted it just encase.
Also any flashing done in odin formats everything. That is why recovery is needed in order to try and get zip updates. Zip updates wont allow a whole rom flash just modifications.
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
so are there gonna be roms in zip ?
or this recovery is gonna handle tars as well?
buddy01 said:
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
Click to expand...
Click to collapse
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
not working on JF7, keeping on rebooting
Chainfire said:
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
Click to expand...
Click to collapse
fair enough.
hkfriends said:
not working on JF7, keeping on rebooting
Click to expand...
Click to collapse
Does the same thing on JG5...
When I first applied it, it rebooted itself twice in a row and booted fine. It ran for a good few hours... restored apps. from titanium backup. Did a reboot again. (just to be safe.) At that point, it kept rebooting itself... and then I pretty much gave up and flashed the stock JG5. (couldn't head to work w/o a working phone, lol) Anyone got it to work so far?
Ladies and gentlemen, humans and androids, I present to you...
CLOCKWORK MOD RECOVERY 6.0.1.2
{
"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"
}
Install/Backup/Restore/InternalSD/ExternalSD all working!
For all you blob haters out there, you can switch the format from dup to tar in backup options!
Procedure is as usual:
1. Open Odin and ensure your phone is in DOWNLOAD mode.
2. Place the recovery.tar.md5 in the PDA slot.
3. Check auto-reboot and hit Start.
4. Wait for it to finish. Are you waiting? Wait until it finishes!
5. Enjoy an up-to-date CWMR6.
Recovery files are attached, along with Odin.
I've bumped into a few errors trying to get this working, so I'll post the symptoms and the solutions:
1. If the MD5 breaks validation, you changed the name of the recovery.tar.md5 -- it needs to stay the same!
2. If your transfer hangs, your cord may be bad. Mine kept getting stuck at 10% or so, and then I noticed my dog had bitten through the cord a little earlier. The cord is only good for charging, now.
If you have any questions or comments, I'll help as best as I can.
Aquethys' Recoveries are UNSUPPORTED by me.
Aquethys' old TOUCH recovery (Touch Recovery CM6) can be found at: http://aquethys.cu.cc/Glide/recovery.tar.md5
Special thanks to:
utkanos
KemoNine
Nice dude
MIRROR:
DOWNLOAD HERE
I hate to say this, but I get the same error message as I did flashing Aquethys version he was building!
write data size too big[14|sos] [Data:5213532(8) -> Part: 2550/2550(2k8)]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xffffffff]
Click to expand...
Click to collapse
can we have a flash cwmr of this? i know we can update cwmr this way as well - did that before on i9100 device.
dbrannon79 said:
I hate to say this, but I get the same error message as I did flashing Aquethys version he was building!
Click to expand...
Click to collapse
You shouldn't have any problems. Are you sure you downloaded and tried to use the right one? I have tested it, for sure, and it worked great on an I927R (mine, Rogers/International variant) and a I927 (girlfriend's/AT&T variant).
You'll get that error if your partition size is too small for recovery -- our recoveries *are* limited -- to about 5,200,000 bytes -- this is just under that and should work fine. You should not be screwing around with it.
Ensure you are using the recovery.tar.gz I included. Then attempt to do it again -- I have a feeling you may have flashed Aquethys' again.
And just noticed -- the recovery you used is larger than mine -- mine is 5,02x,xxx length in bytes -- so yours is not mine, since it went to 5,213,xxx.
taiber2000 said:
can we have a flash cwmr of this? i know we can update cwmr this way as well - did that before on i9100 device.
Click to expand...
Click to collapse
Well, I think I know how to do that -- but it's a little more risky. Involves manually using commands to write to the partition -- which is less stable/ideal than Odin. I was talking to some folks (when my cable was bad) and they said we could do that method as a LAST OPTION. They didn't seem to be too happy of the thought -- but it is something I could potentially research. It may have just been because I was potentially sacrificing my phone, when I didn't know for sure if it was correct/good.
Works well with i927 (AT&T) Version..
So, after playing around with this some more, this morning, I've discovered that the most important part -- being able to backup/restore -- is not working. Not sure if it is because it may be from an unstable branch of CM10 trying to integrate the newer Jellybean or what -- but I intend on fixing it and finding out what the problem is.
I didn't worry about testing the backup/restore, since I have no data/etc -- but I did test whether or not we could flash from internal or external SD cards, which does 100% work.
So, just a word of warning (I've included it in the topic) to be careful if you flash -- you may not be able to recover/backup as you would like to. I'll try to get this working within a week.
terinfire said:
So, after playing around with this some more, this morning, I've discovered that the most important part -- being able to backup/restore -- is not working. Not sure if it is because it may be from an unstable branch of CM10 trying to integrate the newer Jellybean or what -- but I intend on fixing it and finding out what the problem is.
I didn't worry about testing the backup/restore, since I have no data/etc -- but I did test whether or not we could flash from internal or external SD cards, which does 100% work.
So, just a word of warning (I've included it in the topic) to be careful if you flash -- you may not be able to recover/backup as you would like to. I'll try to get this working within a week.
Click to expand...
Click to collapse
Will be recovery type be Blob type ?
If it is CWM6, it will be. I may be able to see if there's a flag or two I can set to change it away from blob -- I know people seem to not like that.
thanks a million this will make development so much easier .. and it can even mount the external
terinfire said:
You shouldn't have any problems. Are you sure you downloaded and tried to use the right one? I have tested it, for sure, and it worked great on an I927R (mine, Rogers/International variant) and a I927 (girlfriend's/AT&T variant).
You'll get that error if your partition size is too small for recovery -- our recoveries *are* limited -- to about 5,200,000 bytes -- this is just under that and should work fine. You should not be screwing around with it.
Ensure you are using the recovery.tar.gz I included. Then attempt to do it again -- I have a feeling you may have flashed Aquethys' again.
And just noticed -- the recovery you used is larger than mine -- mine is 5,02x,xxx length in bytes -- so yours is not mine, since it went to 5,213,xxx.
Well, I think I know how to do that -- but it's a little more risky. Involves manually using commands to write to the partition -- which is less stable/ideal than Odin. I was talking to some folks (when my cable was bad) and they said we could do that method as a LAST OPTION. They didn't seem to be too happy of the thought -- but it is something I could potentially research. It may have just been because I was potentially sacrificing my phone, when I didn't know for sure if it was correct/good.
Click to expand...
Click to collapse
my apologies! after going back and looking at my download folder, realizing it's time to clean!! I reflashed your recovery and works!
Thanks,
I would like to see the recovery without the blobs that way single backups can be made and archived! also I do enjoy the "touch" version if there is a possibility putting all that together!
Thanks again and have a blessed thanksgiving!
I'll put the touch recovery back up. And...
I'm going to try to build TWRP in the next couple of weeks. Terinfire, you interested in helping me?
Aquethys said:
I'll put the touch recovery back up. And...
I'm going to try to build TWRP in the next couple of weeks. Terinfire, you interested in helping me?
Click to expand...
Click to collapse
TWRP! Wonderful! Million Thanks!
TWRP and physical keyboard is a great combo because you have a comfortable shell in recovery mode
Terin did you build in Ubuntu? ;/
I might have to cm sync again.. Takes forever xD like 2 hrs
Sent from my SGH-I747 using Tapatalk 2
Aquethys said:
Terin did you build in Ubuntu? ;/
I might have to cm sync again.. Takes forever xD like 2 hrs
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I setup a VM. Thankfully, my laptop is a monster so I have it virtualizing 8 cores without an issue. Don't ask the specifics, but to give you an idea -- it has two full-sized 5870's in it -- it's a monster.
Yeah, I have it working on Ubuntu. I'll see what I can do to help you out -- I can potentially build it if you help me find all of the details I need. I have a MUCH better understanding about how the entire systems work entirely, now.
So TWRP or whatever it is -- sure, I can see about helping you out with it. I'll probably finally need to get a github account or something, haha. Or get added to an existing TeamGlide one or something, hah.
Has anyone else tried to do a backup/restore with this? It didn't work for me -- but I'm curious if it worked for anyone else and maybe my SDCard's are formatted poorly?
I attempted to test the backup and restore! I found a setting for backup options, set it from "dump" to "tar" backed up to external sd. went well...
attempted to restore and got an error message "md5 mismatch"
opened the folder on my pc and saw where it made 2 .img files one boot and the other recovery. and a "system.ext4.tar" and "system.ext4.tar.a"
tried to open both if the archive files and both gave errors with archive manager in ubuntu, could not open! havn't tried the "dump" style backup yet!
Thanks.
terin,
Here's a permanent link for the touch recovery:
http://aquethys.cu.cc/Glide/recovery.tar.md5
Might want to add it to OP?
Aquethys -- done.
dbrannon79 -- Thanks for giving it a try and confirming. I have the same issues, regardless of dump-type on mine as well.
I'm wondering if it has something to do with CM's Jellybean source incorporating the latest and greatest from 4.2 Jellybean. It might not be an issue. Maybe it is. Regardless, I'm still trying to figure out the kinks with it. I'll be scheming with the good folks who helped me build it in the first place tomorrow -- and maybe I can at least get CWM5 working with an external card -- I haven't really seen much in terms of difference between 5/6, aside from organization structure... and we're kind of gimped (a little) on the size of our recovery partition, anyway...
terinfire said:
Aquethys -- done.
dbrannon79 -- Thanks for giving it a try and confirming. I have the same issues, regardless of dump-type on mine as well.
I'm wondering if it has something to do with CM's Jellybean source incorporating the latest and greatest from 4.2 Jellybean. It might not be an issue. Maybe it is. Regardless, I'm still trying to figure out the kinks with it. I'll be scheming with the good folks who helped me build it in the first place tomorrow -- and maybe I can at least get CWM5 working with an external card -- I haven't really seen much in terms of difference between 5/6, aside from organization structure... and we're kind of gimped (a little) on the size of our recovery partition, anyway...
Click to expand...
Click to collapse
sound good! I switched back to ver 5 mainly for the non bump backup! makes things easier to archive backups not to mention the ability to use them tweaking roms!!
I'll look forward to helping you test and any other way I can...
Thanks.
Hopefully going to be able to spit out a new version today for you folks. Will keep you posted!
EDIT:
And that was quick! Tested and working!
This is only what has worked for me i take no responsibility for anyones phone catching fire after following my guide/advice. Tested myself on a UK D802 16GB on Three Network! Confirmed working on 32GB devices now too!!
This needs formatting to make it easier to read. I will get around to it but here is the basic info needed!
Please READ this entire first post before asking questions that are already answered.
Today i have managed to flash the European Open Kitkat rom and root it and keep TWRP recovery. It worked for me but can't guarantee the same results for you.
Prerequisites. (Skip this if you already have rooted JB rom with custom recovery)
First i downgraded to Jellybean using this guide. I downgraded to "UK Open 16GB D80210B_00.kdz" i'm not sure if that's required though.
Then I rooted it using IORoot.
Then i installed TWRP using Freegee from the Play Store.
From here you are ready to flash or you can start from here if you already have root and recovery on Jellybean.
You need these three files.
1. My modded Stock rom zip.
Mirror 1 | Mirror 2
2. Savoca Modded Boot.img.
3. SuperSU ZIP.
Now to flash! (Take out your simcard first.)
1. Boot into TWRP and flash the modded stock rom DOWNLOAD 1. It will take a while and the screen may turn off during this, just press power button. Ignore the failed error!
2. Now go to main TWRP screen and select Reboot Recovery. (Wouldn't mount system otherwise!)
3. Now go to Mount and make sure System is ticked. (Not sure if required but do it anyway!)
4. Now flash Savoca's modified boot.img DOWNLOAD 2.
5. Again go to Mount and make sure System is selected.
6. Now flash SuperSU ZIP DOWNLOAD 3.
7. Now i wiped data here not sure if it's required as the rom wipes system but do it anyway!
8. Replace sim and reboot and all should be well!
If you have NO MOBILE NETWORK i got this error and that's why i recommended removing sim card. I had to repeatedly toggle wifi on and off, and airplane mode and restarted a few times. Not sure what fixed it but don't panic it DOES work.
Bugs and Fixes!
Audio Hissing/Crackling on Headphones.
This is present on all Kitkat roms currently. Some users don't get it most do. Type of headphones seems to be a factor. The following fix is temporary and will revert after a reboot. So needs to be repeated if your phones reboots for any reason.
Type in phone dial pad 3845#*802# and it will show Hidden Service Menu.
Click on "ELT Test", select "Manual Mode" and select "Test Start".
With headphones plugged in select "Audio Loopback" and than select "Test Start".
Blow gently into the microphone and keep on this test 20 seconds or more.
Once done back out and play music. Enjoy!
No LTE/4G anymore?
It seems to require a change of bands for some to get LTE working. There is a value to edit in build.prop. You can do this manually with a root explorer and setting correct permissions after changing, I've found the easiest way is to download JRummy Build.prop editor from market.
Open the Build Prop Editor app.
Find the value "ro.telephony.default_network" and select it.
Notice the property value will be set to "9". Change this to "11" and let the app reboot phone.
If you still don't have LTE try again but change the value to "13" and let the app reboot phone.
Bluetooth Battery Drain
This is NOT real battery drain so please don't worry about it. It is a falsely reported statistic. I get battery life on a par with 4.2.2. Around 8 hours screen on time which is fantastic! If you have battery drain please try a full wipe, don't restore apps from another rom do it manually. Take a look at your apps.
How is it done?!
The modded zip is stripped down to include only the System, Modem and Cust partitions. These are all that is required for Kitkat to play nice with Savocas modified boot.img. I edited the updater-script to remove the entries for all partitions except those listed above and repacked it up nicely to flash. So it is possible to do this with any future updates too. The Cust partition is necessary in case your partition has old carrier stuff still on there, this flashes a clean Cust partition.
Thanks to:
LenAsh for the flashable zip i modded.
Savoca for the modded Boot.img and modules.
Chainfire for SuperSU.
Jesus for blessing all the little children.
it would be great if you also make one for the 32gb version
anyways, great work, dude!
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
superbonto said:
it would be great if you also make one for the 32gb version
anyways, great work, dude!
Click to expand...
Click to collapse
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
paniczklos said:
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
Click to expand...
Click to collapse
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
ephumuris said:
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
Click to expand...
Click to collapse
I'm preparing a dead fish to throw it on your doormat ;p
I'm on 12th minute of booting - LG logo and led flashing green-to-blue.
And yes I'm 16GB
How to use the standard recovery ?
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated.
{
"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"
}
Sent from my LG-D802 using Tapatalk
SPBoss said:
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated. View attachment 2630159
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
What rom are you running? I get the option for gsm/wcdma/lte auto. Although no 4g for me on Three in Hull yet.
badchip said:
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Click to expand...
Click to collapse
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
ephumuris said:
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Click to expand...
Click to collapse
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
paniczklos said:
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
Click to expand...
Click to collapse
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
ephumuris said:
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
Click to expand...
Click to collapse
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
ephumuris said:
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
Click to expand...
Click to collapse
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
paniczklos said:
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
Click to expand...
Click to collapse
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
badchip said:
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
Click to expand...
Click to collapse
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
ephumuris said:
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
Click to expand...
Click to collapse
I'm downloading the UK open EUR and I'll start over.
ephumuris said:
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
Click to expand...
Click to collapse
I would very much appreciate that. I have used the tool to extract the kdz and dz. I have the files in screenshot now.
Whats the proper next step?
Thanks for your help
edit: The meta-inf folder is from the KK template provided in that thread, I suppose I don't need that.
Hi!
Firstly thanks for this!
and secondly i have to say that i already flashed to my LG G2 32gb and works like a charm... btw i also did it with another way:
1-Downgrade to 4.2.2.
2-when your in v.4.2.2 root and recovery.
3-i used lastest CWM version from Philz.
4-FLash your Rom.zip
5-reboot to recovery. (Dunno if this is really necessary but just in case i did it too)
6-Flash Savoca Patched
7-Flash Root
8-Reboot
9-ENjoy EUR 20b =)
Thanks!
Great to confirm working on 32gb too. Badchip you might have to wait til later unless you can use that existing meta inf folder. I've just left for work so not at laptop.
Try deleting every file but only keep.
Meta inf folder.
System.IMG
Modem.bin
Custom.bin
Zip those up and flash them. Should work if the update script is right in meta inf folder.
@iall5tar What base jellybean rom did you downgrade to?
And regarding custom recovery it should work with any cwm philz or twrp. I just referenced twrp as that's what I use.
Sent from my LG-D802 using Tapatalk
What you mean about folder meta-inf? im not a expert i just want to give a try and it worked xD
Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
BEFORE and AFTER:
{
"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"
}
ZIP ARCHIVE INCLUDES:
a) the rom itself (removed bunch of crapware)
b) SuperSU-2.49-BETA
c) Nuts Dual Recovery 2.8.15
d) DRM Function Restoration for UB
STEPS:
1) backup
2) wipe /system, /cache, /dalvik-cache
3) flash the main rom
4) flash google services removal.zip (optional)
5) boot up phone and go through setup
6) flash further debloat (optional)
DOWNLOADS:
Main
Google Services Removal
Further Debloat
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?
Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
zgomot said:
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?
Click to expand...
Click to collapse
I'm currently on a locked bootloader so I can't verify if it'll work without having to flash an ftf with TA beforehand. Best thing to do is try it yourself.
If x-reality is working, bionz is working.
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
facing problems...
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Its great to have a RAM free rom... but what the point of having so much ram when there's nothing else u can do with the phone. I did try installing Google Play Store apk but it just simply crashes...
Please dun be offended as I still feel this ROM is a well done rom, I might just missed out something.
kedirakevo said:
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Click to expand...
Click to collapse
The google debloat is only optional. If you don't flash it, you'll get to keep the play store.
I personally don't use the play store and download my apps from apkmirror or evozi
Okay, can share more what does further debloat do? I can do that without google debloat right?
kedirakevo said:
Okay, can share more what does further debloat do?
Click to expand...
Click to collapse
Further debloat removes some of the bloat that I forgot to remove from the main rom itself and also the setup wizards. So make sure to use it only after booting your device and going through the setup.
I can do that without google debloat right?
Click to expand...
Click to collapse
Yes.
I've tried flashing this twice and have ended up softbricking twice. I think the issue may be because of the wiping of system, which I have honestly never had to do before, so I'll try once again, and if it doesn't work I guess I'll just find something else.
EDIT: Yep, nothing I do seems to really be working, probably just getting bad downloads on my end though.
compatible with c6902?
Is this compatible with xperia z1 ,c6902?
Zerousen said:
I've tried flashing this twice and have ended up softbricking twice.
Click to expand...
Click to collapse
Do you have a c6903 and on latest kitkat(.108) or .242?
ravishmahur said:
Is this compatible with xperia z1 ,c6902?
Click to expand...
Click to collapse
Nope.
How to flash Xposed in this rom please? Thanks
Ahki767 said:
Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
edited
Click to expand...
Click to collapse
Flashed without issues coming from CM12.1 (the terrible, terrible photo-quality and some in-call sound issues recently always make me return to stock). I just took care to follow instructions and flash a pre-rooted .2.4.2 rom prior to flashing this.
The rom feels really really smooth, it's lovely so far.
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
I tried a couple of apps to change dpi values to default, but they wouldn't read current dpi and no new values could be applied. Maybe this is linked to the Play Store incompatibilities.
How must I install it? Always I installed it (from official .242 and .270 too with RockZ1 Kernel) I had many bugs on this ROM, please help me
HELP
dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance
busukusu said:
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance
Click to expand...
Click to collapse
I fond the solutions for my problems. I test Fastboot at It work. When Power Off, press Volume Up and connect the USB Cable, then I can detect my phone with command: fastboot devices
After that, using Flashtools and install any FTF source with Kitkat 108, then flash it using Flashtools at computer PC. Prepare downloaded FTF files about 1 GB size at the same computer drive, then run Flashtools and then connect Press Volume Down and connect with USB cable, after that Flashtools display will show that my phone detected / connected, and continue with flashing FTF files, the process about 10 minutes less, and after finish flashing, disconnect USB cable, press Power button and YES it work again.
After that I have to install again with TWRP and install any Stock preroot firmware.
dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
I had the exact same problem. Ended up going back to my nandroid backup.
I am on locked bootloader. Not sure if that is the problem.
@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.
zgomot said:
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
Click to expand...
Click to collapse
if you're still on this rom, you can change the dpi in /system/build.prop look for lcd_density and change it to 480 (original value). only thing i can think of for incompatibility is maybe an out of date play services
squashbuff said:
@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.
Click to expand...
Click to collapse
md5 check: 0406a4743310ee19209cfedcf0c728c9
make sure you're flashing at least from latest kit kat or lollipop
Root Method For S8+ U/U1/W Series Phones Rev8 Bootloader
New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation
Paypal email is [email protected]
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It. Do Not Come In Here And Post This Is Not Working Until You Have Tried It With The USB2 Mini Hub!
You Must Start From Stock U Firmware. IT Seems To Be The Less Likely To Brick Your Device As Explained In The Disclaimer!Disclaimer Please Read!!
This may brick your device there is a problem especially with s8 and note 8 models where the tz partition becomes corrupted and on some occasions after flashing combination firmware your phone will become bricked and as of now there is no way to fix it. There is no way to predict if it will happen. It doesn’t seem too happen very often on s8+ but it does occasionally happen on the other 2 models so do this at your own risk. I would say it probably happens 10 percent of the time on s8 and note 8 especially when on bit 6 or higher firmwares. S8+ it rarely happens too but it still may. If you take the risk and it happens do not pm me asking how to fix it as of time I posted this there is no way to fix it
Please Read Notes
OEM Toggle Does Nothing On US Model Phones
You will most likely need a USB 2 mini hub for Odin to work if using windows 8 or higher. I would temporarily disable windows defender or antivirus software while performing the procedure with your computer.
You cannot have root on any rom except a nougat rom also flashing custom boot images cannot be done or using systemless magisk. Hiding root or running modules cannot be done. There is no oem unlock and even if there is you cannot unlock your bootloaders or run any aosp based roms.
You can be on any firmware to achieve safestrap but to run a rooted rom you will be limited to using a special nougat android 7 rom. You can have safestrap on pie android 9 which gives you some ability to modify system files flash zips etc and have access too data and other partitions that are normally blocked but you can not run root on android 9 because root on android 9 requires a modified boot image
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Additional Help Can Be Found In The Telegram Channel
Telegram Channel For 8 Series Root
Downloads
Odin3_v3.14.1_3B_PatcheD.7z
SM-G955U_VZW_G955USQU8DUJ1.7z -- Stock U Firmware Flash First In Odin
SAFESTRAP_S8_PLUS_GUI_INSTALLER.7z - GUI 1 Click Method-Recommend!
Alt Method
Safestrap_S8_Plus_Cmd_Line.7z - Command Line 1 Click
Directions Once On Stock U Firmware
If using Safestrap_8_Series_Cmd_Line follow instructions on Cmd screen.
1. Download files and unzip SAFESTRAP_S8_PLUS_GUI_INSTALLER.7z
2. Plug phone into computer and allow access too phone data
3. Run the SAFESTRAP_8_SERIES.exe file. In program choose your model of phone in drop down box then click Root Button and select COMBINATION_FA70_G955USQU8ATG1.tar.md5 file too flash it is packed in the zip you downloaded from above. Everything else is automatically done for you just follow any pop up that come up.
{
"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"
}
4. Phone will reboot too download and flash combo firmware and then reboot. Click dialog stating that it has rebooted and it will inject safestrap all automatically
5. When done you will have a minimal system with safestrap recovery
Instructions For Installing Rom
System Images
system_g955_nougat.7z - Nougat Image That Can Be Rooted
Pie With Safestrap Stock Roms Un Rooted Found Here
Canadian Roms Found Here
1. From here you will either a nougat or pie system image to your phone which will be flashed in safestrap. Reboot to safestrap using the safestrap control app once in safestrap choose wipe then advanced wipe and wipe data. Then goto home screen of safestrap using install tab and the the flash image tab at bottom. Choose system image you copied to phone. System images get flashed too system partition.
2 My nougat system images are not pre rooted if you want for root you will also need too flash a root zip in safestrap.
Root Zips For Nougat Image
EFTSU_System-v20.4_12_28_22.zipSuperSU_System_12_28_22.zipPhhs_SuperSU_S8_S9_Series.zip3. You can enter safestrap anytime on nougat by simply rebooting to recovery which will enter safestrap or by using the safestrap control app
Fingerprint Fix For Nougat Roms
SM_G955U_FINGERPRINT_FIX.exe
4. If fingerprint not working reboot phone too download mode and run this SM_G955U_FINGERPRINT_FIX.exe
Pie With Safestrap Roms
Full Guide found Here
Video Tutorial
Thank You Liset Pedraza
Method In This Video To Obtain Safestrap Has Changed But The Process Of Using Safestrap Still Pertains
S8_Series_Install_Root.mp4
drive.google.com
Credits
klabit87 - Basically Everything
GSMCHEN - The root method
elliwigy -The root method
afaneh92 -Safestrap and too much too mention[/MEDIA]
oakieville - 1 click method
S8 SM_G950U/U1/W Can Be Found Below
2023 SM-G950U/U1/W Rev8 One Click Root/Safestrap Inject Method
Root Method For S8 U/U1/W Series Phones Rev8 Bootloader New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation Paypal email is [email protected].com Before Starting...
forum.xda-developers.com
N8 SM_N950U/U1/W Can Be Found Below
[NEW METHOD][ROOT] [Extreme Syndicate] [Snapdragon][N950U/U1][V8 Bootloaders]
Root Method For S8/S8+ And Note 8 Series U/U1/W Series Phones Rev8 Bootloader This may brick your device there is a problem especially with s8 and note 8 models where the tz partition becomes corrupted and on some occasions after flashing...
forum.xda-developers.com
so if i remain at nougat i should be able to flash custom roms? Also, i'm currently facing "no service" problem on my g995u. Any ideas if going back to nougat would rectify the issue?
jrkruse said:
Rooted Nougat Rom
This is last nougat rom made for S8 it is prerooted with flashfire and safestrap preinstalled. It has CSC stuff for all carriers added. Its debloated slightly with knox removed. Some stuff may not work but im not sure as I cannot test but this stuff may include fingerprint and or face recognition. If stuff doesnt work it probably related to using pie modems and non-hlos on a nougat rom which you have no choice.
Downloads
system_s8plus_brb1.7z
BL_G955_NOUGAT_V7.tar.7z
Includes Fingerprint and Face Unlock fix for above nougat rom. Just flash in BL slot in odin after everything else
Magisk_System-v20.4.zip This is system magisk not the normal systemless magisk so magisk hide and modules will not work!
SuperSU_System.zip
Safestrap-4.12-T01-DREAMQLTE_PIE.zip Will boot straight to safestrap only for pie roms
Safestrap-4.12-T01-DREAMQLTE_NOUGAT.zip Will Give you the safestrap splash screen on boot
Directions
Safestrap Method
1. Extract system.img from the system_s8plus_brb1.7z and copy to phone also copy either SuperSu_System.zip or Magisk_System-v20.4.zip reboot to safestarp and flash system image
2. Flash either SuperSu_System.zip or Magisk_System-v20.4.zip
3. Reboot to download and flash BL_G955_NOUGAT_V7.tar.md5 in odin
4. If you get constant rebooting to safestrap flash Nougat safestrap zip while in safestrap
Non Rooted Pie Rom With Safestrap Can Be Found Here
Click to expand...
Click to collapse
unfortunately i got myself a bricked device. no bootloader, no recovery, no charge, nothing...
kkins95 said:
unfortunately i got myself a bricked device. no bootloader, no recovery, no charge, nothing...
Click to expand...
Click to collapse
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
jrkruse said:
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
nope. no sign of life comming from the phone. just a flicker of white line when i hold volume down and power button. thanks for the response.
kkins95 said:
nope. no sign of life comming from the phone. just a flicker of white line when i hold volume down and power button. thanks for the response.
Click to expand...
Click to collapse
So what exactly happened?
Sent from my iPad using Tapatalk
jrkruse said:
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
jrkruse said:
So what exactly happened?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
i was on a g995u1 firwmare(bootloader v7) although i was having issues with "no signal". i thought maybe if i follow your guide to return the rom back to nougat my network would return to normal.
i only flashed this file "BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V7.tar.md5".
ps. i did tick the "nand erase" in odin.
the flash completed but my phone went black and did not reboot again.. i disconnected hoping to get it back to download mode again but nothing was working. i have tried using volume down and power keys but this only causes the a little part of the screen to flicker for less than a second.
my battery was 99%. I dont have qualcomm drivers installed. i am installing one as we speak, i have seen some threads with similar issues like mine but no solutions.. thanks for your response..:crying::crying::crying:
kkins95 said:
i was on a g995u1 firwmare(bootloader v7) although i was having issues with "no signal". i thought maybe if i follow your guide to return the rom back to nougat my network would return to normal.
i only flashed this file "BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V7.tar.md5".
ps. i did tick the "nand erase" in odin.
the flash completed but my phone went black and did not reboot again.. i disconnected hoping to get it back to download mode again but nothing was working. i have tried using volume down and power keys but this only causes the a little part of the screen to flicker for less than a second.
my battery was 99%. I dont have qualcomm drivers installed. i am installing one as we speak, i have seen some threads with similar issues like mine but no solutions.. thanks for your response..:crying::crying::crying:
Click to expand...
Click to collapse
It happens once in awhile for no reason. Nand erase may have had something too do with it. I never use nand erase except if going back too totally stock from a modified system. I responded too your pm. You’re phone can probably be fixed with edl files but you are going too have too take your phone apart and jump some test points to make phone enter edl mode
Sent from my iPhone using Tapatalk
jrkruse said:
It happens once in awhile for no reason. Nand erase may have had something too do with it. I never use nand erase except if going back too totally stock from a modified system. I responded too your pm. You’re phone can probably be fixed with edl files but you are going too have too take your phone apart and jump some test points to make phone enter edl mode
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
ive been searching for the edl points for the s955u but to no avail. ive taken apart my phone but cant find any reference online for the edl test points. i dont want to start testing randomly because something i have no idea about might happen..
kkins95 said:
ive been searching for the edl points for the s955u but to no avail. ive taken apart my phone but cant find any reference online for the edl test points. i dont want to start testing randomly because something i have no idea about might happen..
Click to expand...
Click to collapse
I use to have pics and stuff but I lost them on a hard drive that failed. I can tell you they are on the bottom side of the board and you have to pry back a metal heat shield to get too them
Sent from my iPhone using Tapatalk
jrkruse said:
I use to have pics and stuff but I lost them on a hard drive that failed. I can tell you they are on the bottom side of the board and you have to pry back a metal heat shield to get too them
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
kindly help identify them if visible or point out what i am to do next. thanks alot....
kkins95 said:
kindly help identify them if visible or point out what i am to do next. thanks alot....
Click to expand...
Click to collapse
You have to take board out and flip it over. The points are on the bottom side
Sent from my iPad using Tapatalk
jrkruse said:
You have to take board out and flip it over. The points are on the bottom side
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
OK, Thanks for the response. i see two large heat sinks with the larger one at the top and the smaller at the bottom. i assume the points would be hidden underneath the bottom sink. now i have to figure out a way to pry those metals off... so much work..lol..
Will this work on all V7 Bootloaders?
I am currently on DTF4 and noticed your on the Verizon page you posted for the DTB3 Bootloader. Thanks for your time and efforts.
jrkruse said:
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Click to expand...
Click to collapse
jrkruse said:
Rooted Nougat Rom
Click to expand...
Click to collapse
Thanks this worked for me! Is there a guide on how to reverse everything if I wanted to make the phone normal again? Like it would be factory out of the box?
lonewolf1738 said:
Thanks this worked for me! Is there a guide on how to reverse everything if I wanted to make the phone normal again? Like it would be factory out of the box?
Click to expand...
Click to collapse
Just flash stock firmware in odin
Sent from my iPhone using Tapatalk
I have version 8 files so will make stuff when I get a chance
Sent from my iPhone using Tapatalk
@NateNMad
yeah its on the same bootloader G955USQU7DTF4
[ROOT] [Extreme Syndicate] [Snapdragon][G955U/U1][V7 Bootloaders]
If anyone is thinking on updating phones now is the time. The method of unlocking bootloaders on US variants works one s10/s20 and n10/n20 phones. Read the whole article too get info and yes it works I have a bootloader unlocked sm-g975u s10+ with twrp and magisk installed.
https://www.xda-developers.com/samsung-galaxy-note-20-ultra-root-us-unlocked-snapdragon-865/
Sent from my iPhone using Tapatalk