Related
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex,
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Solved it!
Mistertac said:
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
markctco said:
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
Click to expand...
Click to collapse
I'm not sure why you had to get a paid version of su. I had the SU zip and installed it as part of the upgrade/downgrade method
sent by baja kitkat S4
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
You should have plenty of time. I've flashed back to stock so many times and never had that update pop up before I could freeze SDM
I have an MDK phone so I'm not 100% up to speed on what you should do... @decaturbob has done it all and I'm sure would help send you down the right path
Sent from my SCH-I545 using Tapatalk
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
decaturbob said:
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
Click to expand...
Click to collapse
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
markctco said:
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
Click to expand...
Click to collapse
have you looked at any youtube videos concerning S4 and safestrap?
decaturbob said:
have you looked at any youtube videos concerning S4 and safestrap?
Click to expand...
Click to collapse
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
markctco said:
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
Click to expand...
Click to collapse
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
decaturbob said:
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
Click to expand...
Click to collapse
Yup! As a matter of fact this is the video I watched that shows Hyperdrive RSL12 on the exact same phone as mine with 4.3 MK2 build.I think this is also the one that suggests flashing the module at the end. I've watched so many videos I can't remember which ones say what.
Am I missing something? I've made sure that I have USB debugging checked as well as unknown sources before flashing, I've tried flashing both zips at the same time and individually, even tried again without selecting any music players besides the Samsung one and not picking any audio mods when setting up the rom as per someones post on some blog somewhere. I've changed boot image, keyboards...I'm just about over this ROM. It can clearly be used with 4.3 but just not for me I quess? I've even considered backing up my stock rom and doing a factory reset on my phone and then starting from scratch. I'm just hoping I don't have to update to KitKat, which by the way is what Hyperdrive's website states you have to do, but this video contradicts that. UGHHH AGAIN!
http://www.youtube.com/watch?v=pA8cV3-r3oU
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
markctco said:
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
Click to expand...
Click to collapse
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for responding! And yes I'm using that version of Safestrap and did everything you mentioned as per this video:
http://www.youtube.com/watch?v=l4F5UYDcQ5A
The only thing I can think of comes from something someone else mentioned about updating superuser binaries which made me realize that SuperSu, which is what I have doesn't appear to have that option. I checked the Play Store and there is the original Super User apk that I've used before to root other versions before all this bootloader crap started. I remember updating binaries in that version...I think. It may have been an option in CWM which I've also used. Could that be the issue? SuperSu acts just like Super User, asking for permissions and whatnot, but maybe Safestrap needs the other version. I think I'm going to uninstall or freeze (better idea) SuperSu and install the regular SuperUser. What gets me thought is that they are both developed by Chainfire, so I'm not sure what the difference would be. I do know that something is not right because I'm confident I'm doing everything as instructed.
HOT DAMN! I got it! It was a SuperSu issue, just took me a bit to figure out how to update binaries. It doesn't just have a button for that, had to uninstall and reinstall newest version.
Wow, what a trip that was! And I love the ROM.Gotta go and play now though
Thanks for everyones help and patience!
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
Edited
---------- Post added at 10:01 PM ---------- Previous post was at 09:57 PM ----------
Install Terminal Emulator. Type su and press enter. Then type setenforce 0 with a space after setenforce. Then press enter and reopen SafeStrap and all is well. The reboot recovery button will not be greyed out no more.
James- tech for a site dealing with Android day and night!
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
i have this model but i updated it before I knew it would prevent me from rooting it... any way you could upload a backup of your firmware that I can use to downgrade to?
How can you beat a $9 phone
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
Just picked this phone up too, any luck on getting a ROM for it?
I picked one up....couldn't resist for just $9.82. I didn't let it update, so I was able to root it with Kingroot 4.6. Quite snappy after all the bloatware was removed. Have about 1.5gb of internal memory left, but added an 8gb microSD. I haven't been able to findy any recovery, doubt one exists. Nice little emergency phone to have in the car or backpack.
Just picked this phone up as well, and KingoRoot doesn't work. I wasn't prompted for a firmware update when I first cranked it up so I guess I'm on some version that isn't supported? Can anybody clarify what the status of this device is currently? I've got the Tracfone version.
I just rooted my LG L15G tracphone with KingRoot and it worked immediately. Great!
Next step is to get this 10 dollar phone unlocked.
By the way, my firmware version is: Android 4.4.2
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (http://www.imei-unlocker.com) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
anuraj1 said:
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: **Link removed**
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (**Linked Removed***) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: **link removed **]
Click to expand...
Click to collapse
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Root with Root Genius
I have root my LG L15G (Android 4.4.2, kernel 3.4.0+, software version LGL15G10f) with Root Genius for PC v3.0.85.
Of cource, before rooting "Developer options" must be unlocked (5-8 taps on Settings>About Phone>Software information>Build number) and turned on; in "Developer options" must be selected "USB debugging".
After this connect phone to PC. All phone drivers must be installed.
Run Root Genius. When program will ready and say about connect with LG L15G - press one button. After 2-3 minutes root is enabled.
Titanium Backup works. But I have no ideas for unlock the phone to make a possibility work in other GSM-networks, except TracFone's.
Hmm, I had tried Root Genius and that didn't work for me (and yeah I did enable USB debugging. I apparently was using an older build of Root Genius. But I found and used the build you used and still get the unsupported model error. ). My software version is as follows:
Android Version: 4.4.2
Baseband version: M8610B-AAAANAZM-1.0.6060
Kernel version: 3.4.0+
Build number: KOT49I.LGL15G11a
Software version: LGL15G11a
There does appear to be some differences in the software version of mine vs the post above me. I'm guessing they changed something. But that's odd as my phone was brand new just like yours assuming you got it around the same time as me.
EDIT. Ok some bad news. Looks like there was a newer software update (that my phone apparently came with) that blocks root and even prevents download mode from working. (I had attempted to boot into download mode but none of the button combinations work and even the root scripts I've tried can't get it to reboot into download mode)
Seems I'm stuck with a phone I probably can't ever root.
It seems it can still be forced into download mode by using a "56k/130k/910k cable" cable (special cable with resistor on one of the data lines). But they are running for $18 on ebay and way to damn expensive for a simple cable with a resistor installed. Resistors are probably only worth pennies each, so they are way too expensive to be charging that much for it.
If I had a such a cable, the root script I had tried awhile back might have worked as it needs to get the phone into download mode to finish the process.
There seems that there's little hope for your phone but I may have a solution. My LG Sunrise got updated as well and got root access with the update. You can use King Root but not Kingo.
Look it up on Google. So far I've had no success on getting to the recovery mode.
I've tried rooting with KingRoot. It will just say it failed after 20% (sometimes it goes higher, but always end with it saying this).
Note that unlike your phone, mine already had the latest update out of the box.
Apache Thunder said:
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Click to expand...
Click to collapse
If you still haven't got root yet,for me it was McAfee that's been blocking Kingroot every since Nov.
Even though I never set up an account,it was the culprit..I opened the McAfee app created the account and Disabled.
Went to settings,ALL apps,then opened McAfee..Scrolled down to ''manage space'' and deactivated and hit force stop.
Then I ran KingRoot version 4.8.0 from this site.My device rebooted at around 30%,went back to KingRoot and it finished rooting.
THANK YOU!
It took a few tries, but after disabling McAfee's root protection (It completely skipped my mind that this stupid app would have a feature that would interfere. ) KingRoot definitely did it's thing. (I had to re-attempt twice because once it rebooted and failed. So I had to kill the app again and try again. That time it rooted without restarting).
I've already uninstalled McAfee and a few other system apps I need to get rid of. (McAfee on a $10 phone? Yeah..... No.... I'll take my chances. )
I also replaced KingRoot with SuperSU and uninstalled Purify and the KingRoot app that installed the root. After cleaning out unneeded bloatware, this phone is pretty responsive now! It used to lag a little and not register touches some times. But after cleaning out the bloatware (McAfee was probably the main source of the lag) it runs pretty well now!
EDIT:
Ok minor issue. I can't seem to uninstall Chrome (since it's a system app on this phone). It keeps reinstalling it self. It won't stay gone. What would be causing that? I wanted to move Chrome to SD so it doesn't take up space. But this particular phone won't let me.
Seems to happen with Polaris Office as well. Not a big deal at the moment. I can just freeze this app so it won't take up any CPU time/ram. Freezing it seems to work fine. Uninstalling it just results in it mysteriously reinstalling it self....
Does yours lose root after rebooting? I tried to run 'adb reboot recovery' for giggles and SuperSU no longer had root when it failed to start the local and booted normally.
---------- Post added at 04:27 AM ---------- Previous post was at 04:19 AM ----------
anuraj1 said:
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
Click to expand...
Click to collapse
I have the Android SDK installed on my desktop but the TWRP porting guide by Dees_Troy is a little bit too vague for a first timer. I was able to extract the stock recovery using dd this afternoon.
I haven't tried to reboot mine into recovery mode. But root sticks when doing normal reboots.
recovery/rom LG-L15G
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
DroidHost said:
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
Click to expand...
Click to collapse
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
anuraj1 said:
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
Click to expand...
Click to collapse
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
DroidHost said:
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
Click to expand...
Click to collapse
That's fantastic. If it would help, I have one of those variable resistor cables that some LG phone requires for supporting baseband or entering the bootloader.
This is the cable I have: http://m.ebay.com/itm/131321398015
It is described here as well: http://forum.xda-developers.com/showthread.php?t=2069564
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
SamFail presents...
PartCyborgRom
BQL1
A Rooted Custom Rom
For G950U/W, Bootloader Revisions 1 or 2 only any higher are not currently rootable or vulnerable to this exploit
Updates
New Release and a new OP that I hope is easier to read.
Send feedback or suggestions on improvements to me via pm here or on telegram.
Heads Up
You may notice that the BL version of this release is different than the system rom part.
The rom version is in fact BQL1, but the BL is a new version of AQK2. The reason for this is because
the latest combination, ARA1, has a number of sensors not working. I figured out a fix but it requires splicing
stuff in from other versions, and it didnt feel like the battery lasted as well. I am still testing though and
the next release if its ready will come with ARA1. This is not the same BL as the previous
release though, so if you upgrade also flash this new BL!
Thanks!
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should keep working as long as nougat
(is that a haiku?)
Xposed Preinstalled
PCR now comes out of the flasher with xposed pre-installed!
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Boot Animation
Another great one from @Ryan-refoua.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have made me a fan and a regular user. Among other things, it has a better convolver (IRS processing) implementation, and its bass boost is significantly better than v4a. If there are things you like about V4A you can use both at the same time.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by @laura almeida, @Razerman and @ZaneZam. It features some cool additions like native adblocking (no more xposed module), overriding your max youtube resolution (you can watch 4k videos on your phone, but not 4k hdr). I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
Found better stuff to delete. Added back some stuff I took out before that some of you asked for.
If you find something missing that you want back, pull it from the stock rom and install it in /system/app or /system/priv-app, wherever you got it from.
Improved Battery Life
Thanks to some battery sleuthing by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due some personally tested build.prop tweaks. Another part is some data optimisation scripts that now run at boot. You wont notice those, but they are there doing their thing.
Other Features
New for first time flashers
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8.1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager.
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. It has neer happened to me, but I have a backup of my sdcard so I can be a little more risky. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. Lets use this rom as our example. The full build number is as follows: G950USQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. But we are not flashing the BQL1 firmware (or Baseband), We are using an older version because it works better. The version we are flashing is: G950UEU2AQK2. Can you tell which revision it is?
Is my Phone Compatible?
Is it a G950U? Is it a G950W? If you answered "yes" to one of those questions, then the answer is "yes". That being said, flashing this rom if you are on bootloader revision 1 will upgrade your bootloader revision to 2, which means that any previous rom you were running wont work, so be prepared by having a copy of stock for bootloader version 2. If you don't want to move to version 2, you can still run the latest PartCyborgRom though, just use the G950UEU1AQk1 BL_ tar under Old Downloads in place of the one that came with this one. It will work just fine. However if you are unsure I suggest you go ahead and upgrade, there are not really any benefits to staying on 1 at this point.
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode and connect it to your pc
4) Open Comsy Odin and only add the AP Part1.tar.md5 file. Select only the following options:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back. If your computer is old this will take even longer.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while too.
ATTENTION
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of usb ports as you have suffered from the usb3 corruption.
When you see the upload mode page, do the 3 button salute to reboot into download mode again.
WARNING: When you reboot from upload mode, it wont look like download mode. You will see an error.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar. Just continue the process. It is safe to do so and that error will go away after the next step.
6) Close and re-open Comsy Odin or hit the reset button, and add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Leave the default checkboxes for "F Reset Time" and "Auto Reboot" checked. Uncheck "Nand erase all". Click "Start" and flash the BL (part 2) to your device.
Note: If you forgot to uncheck nand erase all, don't worry. You are just wasting time doing something again that you already did, the outcome is the same. "All" in "Nand Erase All" means "all userdata", which means cache and, well, userdata. Nothing else is deleted.
8) Wait for the flash to finish . It won't take very long at all as the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
From this point forther the scary download error message will be gone for good (or until next flash). Don't go looking yet though, you have more work to do to get root.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata and cache partitions that are valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
11) Boot the device as normal. Wait for it to come up. Its deodexed so it will take longer than even your average odexed rom.
All done!
FlashFire Instructions
- Get the ROM on your phone and unzip it
- Open up FlashFire
- Add a Wipe task, select the top 3 items only
- Select Flash Firmware and load up the AP_PartCyborgRom-BootLoopEdition-<version>.Part1.tar.md5 file to flash your new system
- Select Reboot to Recovery
- Make sure "Inject Root" is NOT checked
- Press go. Wait for the rom to flash and your device to reboot into recovery
- From recovery do a factory reset
- Then select reboot to Download Mode
- When device reboots into Download mode, flash BL_PartCyborgRom-BootLoopEdition-<version>.Part2.tar.md5
You have to use odin for the BL file because flashing bootloaders in FlashFire is a bad idea.
Dirty Flashers
Yes, you can dirty flash this rom to upgrade, however it is problematic and can cause issues. I did it for a long time, but my install was a mess by the time I gave up and reset.
To dirty flash, follow your preferred method of flashing above, but skip the Wipe step.
Odin
Skip "Nand Erase All" during the Part 1 flash. Do everything else the same
FlashFire
For the first Wipe task, instead of selecting the top 3, select only Dalvik like the second wipe task.
NOTE: This procedure is ONLY for people upgrading from an earlier PartCyborgRom version. If you are coming from stock you can not dirty flash because you userdata is encrypted which is not supported by the Factory firmware. If you are coming from other rom, or stock, I have no idea man but don't look at me if it blows up.
ANOTHER NOTE: This method of flashing is unsupported! If you do this and you have issues, you are on your own. If you think they are the rom, then back up your entire rom, wipe and reproduce them.
Help! I Got a Boot loop!
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode. If this doesnt help, or you can't get to recovery because you cant press the buttons right, proceed to the next step.
2) Try flashing just Part 2 (the BL) again. not only will this get you back in recovery, it will also format your cache again. Its worth a shot and doesnt take long.
Kernel Panic, Invalid Argument
Start Over
Go back to the beginning and do everything again. If it fails again, even in a slightly different way this time, bad interaction between the s8 and your USB port/controller/cable/etc are causing the image to be corrupted as its being written to disk. Try the following:
1) New USB Ports. If you have them, use a different set of usb ports (not the one next to it, but one further away). Its possible that that will be your "good" port, and that will be enough. Lots of machines also have some USB3 ports and some USB2.
2) New Cable. Its less likely, but maybe a new cable will help. Do the whole thing over with a new cable.
3) Try a few times. It sounds silly, but people who have had this issue have reported that eventually it just works. Try a few times until you get sick of trying. If you try like 10 times it probably wont work on the 11th though.
I Dont Have Another USB Port!
Try to borrow your partner/spouse/roommate/friends computer for a quick flash. Ask about the USB ports though, because another 3.0 port may not help you.
If you can't get someones computer, you can purchase a USB2.0 Hub online or at your friendly neighborhood electronics store. They arent very expensive, and I have heard positive reports from people saying it did the trick.
None of that Worked! I'm Screwed!
No you probably arent. I can count on one hand the number of people who someone couldnt get this working eventually. Some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Its right here!.
And they all rooted happily ever after.
The End.
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10
Downloads
BQL1 (G950U and G950W)
AP_PartCyborgRom_G950U_BQL1.Part1.zip
[Alternate Mirror]
BL_PartCyborgRom_G950U_BQL1.Part2.zip
[Alternate Mirror]
Other Downloads
Remove OTA apps, downloads and debug messages
Remove RCS and VoLTE Icons Zip (Flash in FlashFire)
Odin3-v3.12-PrinceComsy-.zip
[/SIZE]
Previous Versions
G950USQU2BQK5
Bootloader Version 2
AP_PartCyborgRom-G950USQU2BQK5_Part1.zip
BL_PartCyborgRom-G950USQU2BQK5_Part2.zip
Alternate Download Links
Bootloader Version 1
AP_PartCyborgRom-BootLoopEdition-G950USQU1AQK3.Part1.zip
BL_PartCyborgRom-BootLoopEdition-G950USQU1AQK3b.Part2.zip
SM-G950W
AP_PartCyborgRom_G950WVLU1AQJ4.Part1.tar.md5.zip
BL_PartCyborgRom_G950WVLU1AQJ4.Part2.tar.md5.zip
SM-G950U AQI6v2
AP_PartCyborgRom-AQI6_Part1.tar.md5.zip
[This was updated from the original Part2]
Download BL_PartCyborgRom-AQI6_Part2r3.tar.md5
Flashed fine through flashfire(AP only) was a bit worried because after I flashed the bootloader I got a kernel panic upload mode, but I reflashed the bootloader and it worked out fine. Running it for a few hours now and I noticed right away the difference in battery drain, as in, amazing job at extending the battery life. Thanks for your work, look forward to Future updates :good:
Update: only bug I've found is auto rotate doesn't really work, and internet connection issues(might be my network)
I'm new to SIM unlocked and haven't rooted since s4 so possible newb question but
Can I use this rom to root unrooted AQH3?
I'm on sim-unlocked G950U.
Thanks for any help.
Sent from my SM-G950U1 using Tapatalk
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
I will test this with my unlocked g950u1 on tmobile
OMEGAHORSE said:
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
Click to expand...
Click to collapse
Same here.
I tried the first method (fully stock) and it failed badly to where download mode did not work, had to use Smart Switch emergency recovery
First attempt without flashing CSC on TMo resulted in Kernel Panic after reboot from Download mode. I ended up flashing the CSC and now the Tmobile boot splash is showing up and seems to be working, will update to confirm in a few minutes.
Update: booted just fine now into Setup Wizard...
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
TimelessPWN said:
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
Click to expand...
Click to collapse
Sorry about that! I'm taking care of it now
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
TimelessPWN said:
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
Click to expand...
Click to collapse
The links work again. Sorry for the temp issue!
thejackalsmark said:
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
Click to expand...
Click to collapse
This is about all we have as far as ROMs go. We don't have a custom recovery because our bootloader is locked and it's not looking like it's going to be unlocked ever. You can flash this on any G950U phone, carrier doesn't matter.
thejackalsmark said:
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
Click to expand...
Click to collapse
I'm happy enough with the battery. Bonus is that you won't wear it out charging to 80% only apparently.
It's a multi CSC so you should be fine on boost. I can't test it though I only have VZW. Worst case flash the CSC but only do that if it fails to boot.
adj998 said:
This is about all we have as far as ROMs go. We don't have a custom recovery because our bootloader is locked and it's not looking like it's going to be unlocked ever. You can flash this on any G950U phone, carrier doesn't matter.
Click to expand...
Click to collapse
Yeah, Bootloader's a major buzzkill.
Root and decent custom ROM would be a nice consolation prize.
What's your take on the battery afterwards? I practically live on my phone and with not being able to swap batteries, a major hit to battery life is pretty much a deal breaker. BTW, thx for the quick reply!
- TheJackalsMARK
Sent from my Samsung SM-G950U using XDA Labs
reggie cheeks said:
I'm new to SIM unlocked and haven't rooted since s4 so possible newb question but
Can I use this rom to root unrooted AQH3?
I'm on sim-unlocked G950U.
Thanks for any help.
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
No but you can install rooted aqi6 with it. This literally flashes /system and replaces what you have installed. I find aqi6 much improved TBH
OMEGAHORSE said:
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
Click to expand...
Click to collapse
Factory reset. Sorry I should have mentioned that in the op. I will update
partcyborg said:
I'm happy enough with the battery. Bonus is that you won't wear it out charging to 80% only apparently.
It's a multi CSC so you should be fine on boost. I can't test it though I only have VZW. Worst case flash the CSC but only do that if it fails to boot.
Click to expand...
Click to collapse
Thx, man!
And Great Work, again, on this!
- TheJackalsMARK
Sent from my Samsung SM-G950U using XDA Labs