Related
Hello folks,
My phone is currently rooted, running Android 4.4.2. The bootloader is 1747MVLUFNH2. It is the Telus, i747M variant of the S3.
I am using ClockworkMod Recovery, Version 6.0.4.7 and trying to flash Cyanogenmod 10.2.1 (the latest stable release for this phone).
When I flash the Zip in CWM, the installation aborts and I get a Status 7 error. I have tried earlier releases of CyanogenMod, but they have resulted in the same error. Presumably, this is because my bootloader is not listed among those in the asserts of the ROM.
I have found old threads where folks have noted that, when running bootloaders from the ICS era, you can't flash any Cyanogenmod roms past 10.1. I figured that maybe my bootloader is one of these old ones, but from my research "FNH2" appears to be the newest. In most of the lists featured online, mine doesn't even show up. I understand that reverting your bootloader back to an old one is a huge "no no", and would likely result in my phone being bricked.
I suppose all of this leaves me wondering whether I am caught in some sort of limbo, where my bootloader is in fact too "new" for a relatively old version of Cynanogenmod (10.2.). The phone was recently given to me by my brother, and I am not sure how he updated the bootloader/firmware, but it was likely through Kies.
My end goal is just to have some stable version of Cyanogenmod running, and I've run out of ideas as to how I can make it work. I have tried using Cyanogenmod's "One Click Installer", and that seemed to work well until the phone rebooted to the stock ROM that had been running before; leaving me with effectively no change at all. I have verified root access, and gapps zips seem to extract and install just fine.
Any ideas or pointers would be greatly appreciated.
Thanks.
Why not run the latest cm11 for the d2lte? CM10.2 is only JB.
audit13 said:
Why not run the latest cm11 for the d2lte? CM10.2 is only JB.
Click to expand...
Click to collapse
I've actually tried that, but I still get the Status 7 error, even with a CM-11 nightly.
I flashed back to the stock ROM, with the most current bootloader, etc. It still won't flash any CM zip from CWM, and the Installer doesn't seem to work either. It will install CWM, and say that everything went ok, but when the phone reboots, it's still the stock ROM.
p.s. the CAPTCHAs on this forum are damn near impossible.
"It will install CWM, and say that everything went ok, but when the phone reboots, it's still the stock ROM."
If you're having trouble installing CWM, try this: re-flash CWM or Philz in Odin and do not check anything except r.reset.time, flash recovery, remove the USB cable when you see reset in the status window, remove the battery, replace battery, boot into recovery.
If the latest version of CWM is working properly and you get the status 7 error, try to pull a logcat.
Managed to instal AT&T v20 stock kitkat and sb told me to:
use towelroot to root the device then install gpro rec.apk and flash rec but do not reboot to rec then install busybox and freegee-i DID THAT-was easy I quess
NOW I DON'T GET THIS:and perform cwm action after this reboot to rec and flash phillz rec and reboot again to rec and full wipe then flash any rom u want.
Help?
kamolinkaaa said:
Managed to instal AT&T v20 stock kitkat and sb told me to:
use towelroot to root the device then install gpro rec.apk and flash rec but do not reboot to rec then install busybox and freegee-i DID THAT-was easy I quess
NOW I DON'T GET THIS:and perform cwm action after this reboot to rec and flash phillz rec and reboot again to rec and full wipe then flash any rom u want.
Help?
Click to expand...
Click to collapse
Okay, first, you may want to try flash the v10g version of the stock ROM because it's the best starting point for flashing the custom ROM on lg ogp device. Follow the instructions in the link below and you should be good. I don't know why someone would tell you to use the towel root with the stock v20 rom because a lot of time it doesn't root properly. The instructions you were originally gave were to root with the towel root and then install the busy box so you can use the freegee. With the freegee you can install either cwm or twrp custom recovery. Once you have the custom recovery, reboot into the recovery and then flash philz custom recovery because it's better than the freegee's. Philz recovery is optional if you don't feel like you need it, it just has more bell and whistle, that is all. You can flash the custom ROM with either custom recovery, philz or freegee. However, I'm more concern with you trying to root with the v20 stock ROM, because you will likely run into many issues. So be sure to read the guide I give you first.
[http://forum.xda-developers.com/showthread.php?t=285432
x
Hey! thanks for the replay! I just got one helper because the rom guy didn;t want to help me so the others.Only 1 guy wanted to give me hints and I managed to install this stock rom.
So you're saying that I have wrong rom installed?
Do I have to really instal other rom or can I do it on mine but in other way to root it and process it so as to install http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779 or not?
I'm all confused,just wanted to install http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779
but whole day passed and nothing was done U.Ux
Read the guide I give you.
Managed to root my phone by iRoot.
Now I tried install busybox but after I hit install: "it looks like the instalation of busy box was not successful try installing to different location that may resolve the issue"....
any tips?
If you can't install the busy box, that usually has something to do with the root. That's the reason I said not to use the v20 stock ROM as the starting point. The only reason you need the busy box is the freegee, you can install the recovery without using freegee, but you have to search around XDA first because freegee opens up the boot loader, which is also the reason you can't just flash the recovery with the lg flash tool. You may have to flash v10g version of the stock ROM.
Ok I'm in philz menu.Someone said that all I need is to install(ANY) rom and kernel-how I do it? I want http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779
Have you used a custom recovery before? Down load both rom and kernel installing files to a directory that you prefer, usually some where on your external sd disk. Once you get the files, go to philz recovery and press install zip, find the directory where the installing files are located, press on them, and it should install the rom. If you have never done this before, remember to factory or clean install the rom. On philz recovery, there is a function call installing a new rom under factory reset section, use that every time you're installing a new rom.
hawkwind212 said:
Have you used a custom recovery before? Down load both rom and kernel installing files to a directory that you prefer, usually some where on your external sd disk. Once you get the files, go to philz recovery and press install zip, find the directory where the installing files are located, press on them, and it should install the rom. If you have never done this before, remember to factory or clean install the rom. On philz recovery, there is a function call installing a new rom under factory reset section, use that every time you're installing a new rom.
Click to expand...
Click to collapse
PLEASE HELP!
Installed CM12.1 on my e980. And now the wifi isn't working at all. Have searched and tried some fixes but to no end. Any suggestions?
D Sami said:
PLEASE HELP!
Installed CM12.1 on my e980. And now the wifi isn't working at all. Have searched and tried some fixes but to no end. Any suggestions?
Click to expand...
Click to collapse
Have you tried clearing Cache from Recovery?
khan.orak said:
Have you tried clearing Cache from Recovery?
Click to expand...
Click to collapse
Yup, I advanced wiped my phone (TWRP) and cleared cache, dalvik and system
What's Wi-Fi doing? I notice there are issue with the modem on cm12.1 based custom rom. During the boot up, it would spent long time searching for the signal, but I never have problem with the Wi-Fi though, then again, I'm not using cm12.1 but vanir instead. However, somewhere I remember reading that someone else is having a issue with the Wi-Fi on cm12.1, and he fix it temporarily by setting up the Wi-Fi each time.
Looked at ALL the referenced similar threads, and none applied to my device. So, with your permission, I would like to ask for information.
I bought a used, off-contract T-Mobile variant of Galaxy S3, SGH-T999. It IS SIM-unlocked, as I am using a Straight Talk-provided AT&T SIM without any problems. Also, it is rooted, as confirmed by Root Checker and running Terminal--I get the "#" prompt. SuperSU is installed and appears functional. However, neither CWM nor TWRP recovery programs are on the device.
How can I tell if my bootloader is unlocked? If it is not, what would you suggest to use to accomplish unlocking? I would like to be able to flash a custom ROM such as CyanogenMod.
Thank you for your help and patience.
Its not locked
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
stahlwird said:
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
Click to expand...
Click to collapse
You can flash CWM through Odin, but it'll take some repackaging (.img to .tar.md5) or you can search for one to download since CWM comes in .img form. Again, you could use ADB on a computer to install CWM in its .img form since your phone is already rooted. You could also just download TWRP or some other recovery that comes in .tar or .tar.md5 form, which will already be ready to flash in Odin. I haven't used Flashify, but some of the screenshots on the app listing show some kind of recovery install feature. I can't personally recommend it since I've never used it before.
stahlwird said:
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
Click to expand...
Click to collapse
The latest software version causes some weird things indirectly. I haven't noticed any issues with the latest CM12.1 nightlies, but you may run into issues when trying to flash a custom ROM in recovery. It seems the updater_script (a part of custom ROM zip files that tells the phone what to do when flashing in recovery) doesn't include the latest version in the line that determines if the ROM will work with the phone or not (a simple software version text comparison to make sure you won't brick your phone). This can be easily fixed since it's just a text file inside a custom ROM that can be easily modified. The software itself doesn't cause issues with system modification other than some interference with root (which, since you've told me your phone is already rooted, I assume you've figured it out). Keep in mind that the stock ROM could replace your custom recovery upon reboot (I think), which could be fixed by deleting the files 'install-recovery.sh' and 'recovery-from-boot.p' located in /system/etc/. If you're installing a custom ROM, you won't need to worry about that. Also, your Knox Warranty Bit will be tripped (your phone now definitely has a void warranty) but I'm sure you know since you're rooting and stuff. Sorry about the late response, let me know if you have any questions on anything I missed, I'm kind of jumping around with things that come to mind.
I have used flashify and do recommend it. Very easy to use and can select from different recoveries. MJC is not a problem as far as flashing recoveries or roms. Probably one of the only problem is as the poster above stated, but it may be fixed by now by developers
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Hope you two guys (Serio22 and tonytien) don't mind if I pick your brains a bit more. Flashing via phone download mode and Odin doesn't look too bad, but I keep reading all these posts about guys bricking their phones. I CAN'T do that--- this is my PHONE, not a PC I can play around with! Seems you have to have a version of Odin that matches your installed OS AND your particular phone variant, then the CWM version must match both of those. If anything doesn't match, it's brick city! I did finally find a site that lists the current version of Odin (3.07) for the T-Mobile SGH-T999 running the MJC version of 4.3 JellyBean, and it lists the matching version of CWM (6.0.1.2). So, using that site as a guide, I think I might get brave and try to flash CWM that way rather than use Flashify. But, thanks for your comments on it as well.
Far cry from flashing the next nightly on CM using CWM! There was usually a natural path of progression---CM 9.1 to 9.2, then to 10.0, 10.1, etc. There was never a need to jump around and risk bricking. AND, going into Recovery for CWM was a simple option in the Reboot menu, not having to hold down 3 keys and release one at just the right time. I lived thru two phones with CyanogenMod and ClockworkMod, and only went backwards once: I flashed a nightly that I didn't really like. It was a simple matter to go into CWM and restore from the previous Nandroid backup.
Anyway, thanks for your suggestions, help, encouragement, and your ears (eyes?).
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
stahlwird said:
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
Click to expand...
Click to collapse
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
serio22 said:
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
Click to expand...
Click to collapse
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
stahlwird said:
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
Click to expand...
Click to collapse
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
serio22 said:
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
Click to expand...
Click to collapse
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
stahlwird said:
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
Click to expand...
Click to collapse
Not sure, I use twrp. Haven't used cwm in ages
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.
Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues
and if I'm on note 5 moar rom with patch.... no issue flashing right?
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.
MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/
yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?
bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.
Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.