Okay so for starters you can switch out a T999 motherboard for a T999L and get LTE. So I did this and I rooted and ROM'd the new mobo and I put on the T999 TWRP (DocHoliday77 said it would be fine in his Galaxy s3 LTE thread) and it shows absolutely nothing. I can see folders in the root of the device but if I look and any of the folders nothing is inside them. And when I reboot it says no OS installed. CWM touch works fine but I prefer TWRP. Any ideas?
You probably need to flash a rom or firmware.
To see files in /system in recovery you first hsve to mount system.
I'm already running the latest snapshot of CM11 right now. And I can't mount anything. If I go to the mount menu of TWRP and press anything, it just freezes and I have to go back to the main menu. If I try to fix permissions it says "unable to mount (everything)." Why does CWM work and TWRP doesn't? And why can't I get TWRP to mount?
What version of TWRP are you trying? What version of CWM?
2.7.1.0 for TWRP and 6.0.4.5 for CWM
Not sure then. Usually its none, or both thst have that problem. It has to do with the devices hardware revision if im not mistaken. They solved this problem in the Sprint forums and I am hoping to use their info to do the same here. Just gotta find the time!
I prefer TWRP as well, but my best advice is to just stick with cwm gor now until we can figure this all out.
Were you able to flash a rom or firmware and get it to boot?
Now that I think of it, you might want to Odin flash the stock or root66 firmware and try TWRP again after that. You never know....
CyanogenMod 11 is running fine right now with no problems (no major bugs at least). As for Odining back to stock that would take hours for me. It takes well over an hour and a half just do d/l the CM ROM. I'll just stick to CWM for now i guess. Maybe i'll find a fix or somthing that will make it work. Thanks Doc :good:
If you decide to give it a try, download from my firmware thread. itll be faster than sammobile or other firmware sites.
So I went back to stock with the root66 fw and I did it all over again and its still not working. The CWM version works and I'm back on CyanogenMod, but TWRP is still not working. Could it be because I have BOOTLOADER RP SWREV 1 or Qualcomm secureboot enabled?
I dont believe so. My best guess is its the hw version of your device. Like I mentioned before, they ran into similar problems in the Sprint forums. CWM may have already incorporated the fix and TWRP may not have.
If thats not the case then im really not sure what else it could ben
I guess I'll take a look at the Sprint forums and see any contacting the TWRP team.
Just thought I'd post and say that TWRP 2.8.0.0 did not fix the issue. *sad face*
There's another recovery I think I forgot about before. Look for Philz cwm recovery. Its a modified cwm, but a lot of people who had trouble with cwm or twrp found philz worked fine.
Sorry youre having so much trouble still...
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Related
Been a while since i updated my device so i wanted to try out the new 4.4. I see that i needed CWM 6.0.4.3 and i only have 6.0.3.0. I downloaded Rom manager and installed the update that way and Rom manager says its is running the 6.0.4.3 but when i go to the recovery it says the old version is still running and gives me the expected error when i try to flash the 4.4 ROM. I also tried to download the the update file and flash that in recovery and it didn't work either.
Any help would be greatly appreciated. It probably something simple and i will feel like an idiot when someone chimes in........
guttus said:
Been a while since i updated my device so i wanted to try out the new 4.4. I see that i needed CWM 6.0.4.3 and i only have 6.0.3.0. I downloaded Rom manager and installed the update that way and Rom manager says its is running the 6.0.4.3 but when i go to the recovery it says the old version is still running and gives me the expected error when i try to flash the 4.4 ROM. I also tried to download the the update file and flash that in recovery and it didn't work either.
Any help would be greatly appreciated. It probably something simple and i will feel like an idiot when someone chimes in........
Click to expand...
Click to collapse
I updated mine yesterday from the rom mananger and had no problems.
1 thing you should know before you go and try the 4.4 kitkat is that sd card isnt showing. I love the rom but cant get to anything on my sd card.
Good luck.
@guttus
Just a Rule of Thumb. It is advisable to flash Recoveries with ODIN. I am very well aware you can use Rom Manager or Goo Manager, but this is just a thumb rule for flashing the Recovery Partition.
Also note, flashing wrong Recovery can cause hard brick.
recoveries in my sig.
odin and recovery flashable versions
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Hi all. I'm on the i9305 and want to flash latest recovery for kitkat. I'm on philz recovery and wondered if there was one of his I could use. I searched xda but I couldn't find anything. Also I couldn't find an Odin (tar) file for normal cwm. Omni and cm only have the zip and IMG files.
Perseus71 said:
@guttus
Just a Rule of Thumb. It is advisable to flash Recoveries with ODIN. I am very well aware you can use Rom Manager or Goo Manager, but this is just a thumb rule for flashing the Recovery Partition.
Also note, flashing wrong Recovery can cause hard brick.
Click to expand...
Click to collapse
I did do this update via oden. Also flashed Phil's recovery from there. This is where i tried to flash the 4.4 gapps to fix the issue with no luck.
Please post a log of the error when you tried to flash CM Kitkat. If you can't pull the log file, take a photo.
Ok guys I am a noob (also new to these forums) and I'm having a lot of trouble with my phone. The other day, I rooted my phone using towelroot and confirmed it using root checker. then, I downloaded ROM manager as advised by a friend. i followed the instructions and installed Clockworkmod Recovery onto my AT&T Galaxy S3. Feeling I was finally ready to install a ROM, i tried to download Cyanogenmod 10.3.1 only to have it be "downloading" for over 14 hours without it completing. From there, i did some research and decided to utilize the Cyanogenmod Installer. it seemed to work perfectly, even showing the cyanogenmod logo under when my devicec turned on, until it told me to reboot my device. i entered clockworkmod recovery mode to officially reboot it. when i selected "reboot system now" it said "Root access possibly lost. Fix?". i was given the options to say "No" and "Yes - Fix root (/system/xbin/su). no matter which one i try, my phone boots to the stock touchwiz OS. I have installed and reinstalled both superuser, superSU, and ROM manager to no success. What am i doing wrong?
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
audit13 said:
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
Click to expand...
Click to collapse
CM is already rooted? What does that mean? I have a feeling that I will be unable to flash any ROMs due to my "possible loss of root access." Thank you for your patience as I am a noob and am very stressed out as this is my only phone.
I see two areas that are potential problems for flashing that rom. If it took 14 hours to download, its highly likely a corrupted download. But also, you may be on too new firmware. Cm uses asserts in the updater-script to check that you have the right base firmware/bootloader build. They dont update this so when newer firmware is released it will no longer flash because the script doesn't see it as allowed.
Anytime you have issues flashing something in recovery, you should copy the recovery log to sd. This will tell you what happened. I suspect it simply didn't flash, but without the log, theres no way we can tell what happened.
Also, you do not need to be rooted to flash anything from recovery. Just flash the recovery, then flash a rom from there. Nearly all roms you will ever see are already rooted. Non rooted roms are very rare and are generally only used as an alternate way to revert to stock.
I dont use cwm, but if im not mistaken, it seems to always ask to fix root. I dont know why, but I see people ask about it frequently.
I use TWRP, so try that, or philz as suggested by audit13. Just watch the flash progress for any errors and copy the log.
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.