This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
snovvman said:
This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
Click to expand...
Click to collapse
MAN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
...just... man.... i soft-bricked and my router was blocking sammobile for some reason. just finished restoring after kicking out bucks for a fast sammoblie download and playing Ethernet games
thanks though
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
dinaps86 said:
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
Click to expand...
Click to collapse
yeah, that's what happened to me. the boot loader was not having it. my system is still recovering. the boats are burned!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
There needs to be a real guide to rooting lollipop
Sent from my SM-N915P using XDA Premium HD app
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
i accepted the OTA. i should have not done that, now i'm trapped
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
cvaria said:
i accepted the OTA. i should have not done that, now i'm trapped
Click to expand...
Click to collapse
Not at all. I was waiting for lolly to drop for root.. I just did the chainfire method and you're done.
Rooty
jdidtht said:
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Click to expand...
Click to collapse
I'm saying that based on what I have read and experienced, you *generally* cannot revert to a previous major version. Aside from bootloader issues, you may not be able to flash over the modem. This was the case with the Note 2 and 3. I have not tried with the Edge. If you do, please do report.
dinaps86 said:
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
Click to expand...
Click to collapse
This is the Samsung stock image, so it is not a recovery flashable zip. It is a tar that must be flashed via odin. It contains bootloader, baseband, and system image.
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
snovvman said:
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
Click to expand...
Click to collapse
Ready to test maybe i get xposed back working
Well, here goes nothing....
http://forum.xda-developers.com/not.../rom-sprint-note-edge-915p-5-0-1-oc8-t3082802
For what it's worth, on the regular Sprint Note 4 you can go back to KK once you have taken the Lollipop ota or odin'd the Lollipop tar. The bootloader is backwards compatible on the regular Note 4. However you cannot run a Lollipop rom using the previous KK bootloader. That definitely causes big problems. Another thing you have to keep in mind is that the Lollipop tar writes carrier partitions and other important partitions so you MUST either odin flash the lollipop tar or have taken the lollipop ota BEFORE you flash ANY stock or custom Lollipop ROM via custom recovery. And before you odin the stock Lollipop rom tar you have to first reboot into custom recovery and do the factory reset several times and also wipe system, cache, dalvic etc several times.Then reboot into download mode and flash the Lollipop tar. Do this first or else you will odin the Lollipop tar and have left over data which I guarantee will cause issues. You would think the rom tar would completely wipe these partitions but apparently this isn't happening because there are reports of left over data from previous roms after flashing the stock Lollipop rom tar. I would assume this would apply to the Sprint Note Edge also. This is just a heads up.
Surf and talk
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
platniumrover said:
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
Click to expand...
Click to collapse
Sounds like you have some reading to do. Educate yourself before you get started.
primo523 said:
Sounds like you have some reading to do. Educate yourself before you get started.
Click to expand...
Click to collapse
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
platniumrover said:
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
Click to expand...
Click to collapse
You can usually find a stock version of any device's firmware. That'll bring it back to unrooted factory condition. HOWEVER, keep in mind that Samsung has included a piece of software called Knox on their newer devices. As soon as you modify the firmware (which you will have to do for root), you will trip a counter that lets Samsung know the device is modified. Basically, your warranty is literally void as soon as you root your phone. There are some apps I've seen that try to undo this, but I'm not sure if they work.
But it really sounds like you don't know enough about root to go messing with it. Do more research first.
Here's a link to a pretty good guide that'll give you an idea of what rooting is for.
http://www.androidauthority.com/root-android-277350/
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock AT&T Galaxy Note 3
Update Software for Samsung Galaxy Note 3 (SM-N900A)
FAST!! QUICK LINK--MEGA---------------------------------------------------------------->>>>>> ATT_Stock_KitKat_N900AATTCNL1_Rooted_Deodexed
FAST!! QUICK LINK--MEGA---------------------------------------------------------------------->>>>>> ATT_Stock_KitKat_N900AATTCNL1_Rooted_Odexed
QUICK MIRROR LINK--MEGA---------------------------------------------------------------------------->>>>>> ATT-NL1-FIRMWARE.zip 48.0 MB
AT&T [100% Stock] KitKat 4.4.4 (N900AUCUDNL1) Odin Tars download these for safekeeping Thanks to @Walter.White (don't forget to press thank's button)
ATT-KTU8P-N900AUCUDNL1 LIMITS
SafeStrap Recovery will not directly work on 4.4.4 Rom's
SafeStrap workaround is to Odin install NC2 kernel then Odin install Nl1 kernel to boot NL1 when done with Recovery
SafeStrap Recovery Installng Proceder of 4.4.4 NL1
1. If your new to Samsung, Coming from Iphone or Never installed a custom rom please go here and read and learn about your AT&T Note 3 and also search here for related information you need.
2. You must have safestrap recovery installed.
Coming from any Firmware newer than NC2 you need to go here and downgrade
3. Download and copy ATT_Stock_KitKat_N900AATTCNL1_Rooted_Deodexed.zip or ATT_Stock_KitKat_N900AATTCNL1_Rooted_Odexed.zip to you external or internal sdcard.
4. Boot into SafeStrap Recovery and do a Backup of your Current Rom. If you want and your currently running NC2 after your backup you can create a slot 1 and install your NC2 backup there so you can Use your current NC2 for what ever reason later.
5. Make sure your on stock slot (4.4.4 rom's will not run on the other slots because safestrap is not compatable with the newer 4.4.4 kernel) Do a factory reset. ( not doing a factory reset will mix UserData settings and cause FC of apps or cause bootlooping) also when restoring your app's some app's do not work well if you restore data info with them (so you may loose progress, like game levels and score's etc..)
6. Install your ATT_Stock_KitKat_N900AATTCNL1_Rooted_Deodexed.zip or ATT_Stock_KitKat_N900AATTCNL1_Rooted_Odexed.zip
7. When rom is finished installing DO NOT PRESS REBOOT, back out to main menu then press reboot so you get the download button. press download and use odin to install NL1 firmware (3 files BL bootloader,AP kernel and CP modem) skip the recovery you do not need to install that.
8. It is recomended to skip through any setup of accounts, let rom settle about 10 minutes.
9. Go to settings and turn wifi on, then Reboot and settup your phone.
Thanks to @muniz_ri for Modem install files and his root keep files and guides
Thanks to @Walter.White for learning skills, tricks and his firmware thread NL1 odin Firmware files
Thanks to @Hashcode for safestrap and other high tech help
Thanks to XDA for providing this these threads
Thanks to every one here who contributes all the stuff to get things working
ADD ON's
I gathered and also made some Quick guides that might help who need them.
AT&T Note3 Install Guide Documents.zip 9.7 MB
https://mega.co.nz/#!fR8HFA7T!3DiA0XwrmdSId43UK9whHnxXhL2UbTZ6EP4gujZFRss
Nice carl :thumbup::thumbup:
Other working ROMs on AT&T: http://forum.xda-developers.com/showthread.php?t=2938919
will it be possible to have init.d support on this stock rom
sinichi21 said:
will it be possible to have init.d support on this stock rom
Click to expand...
Click to collapse
Init.d support and busybox is already in rom
carl1961 said:
Init.d support and busybox is already in rom
Click to expand...
Click to collapse
Thanks carl just one last question I am currently on NL1 stock with root can't I just install safestrap and odin nc2 kernel then install your zip and odin back nl1 kernel to install this? or I really need to go back to stock root NC2?
sinichi21 said:
Thanks carl just one last question I am currently on NL1 stock with root can't I just install safestrap and odin nc2 kernel then install your zip and odin back nl1 kernel to install this? or I really need to go back to stock root NC2?
Click to expand...
Click to collapse
You don't have to install safestrap. Odin nc2 kernel ,boot into safestrap then dirty install so you do not loose your apps then back out to main menu hit reboot then download. Install with Odin NL1 kernel
The firmware link goes to a Media Fire error page instead of Mega. The roms work fine. Any ideas?
tcas55 said:
The firmware link goes to a Media Fire error page instead of Mega. The roms work fine. Any ideas?
Click to expand...
Click to collapse
thanks will check it out
Fixed
Quick question: does anyone know if I can install this rom on t-mobile note 3? Hardware seem similar and I am using it on at&t network
cnewsgrp said:
Quick question: does anyone know if I can install this rom on t-mobile note 3? Hardware seem similar and I am using it on at&t network
Click to expand...
Click to collapse
I see no problem but if you do just let me know we'll see what we can do
got 2 questions about the 4.4.4 rom. when the official first came out i installed it but had problems being able to install to the external sd or save downloaded files to it. i had tried the normal program called sdfix that had allways worked in 4.4.2 but never worked for me on the 4.4.4, maybe it was me and something i did wrong at the time but does save to external sd work in this? also i am on 4.4.2 and everything works great for me now but i like the newest and greatest is there anything that great that is in 4.4.4 over .2? i havent read any post about .4 and whats better. thanks for giving us this pre-rooted stock rom though.
peterson65 said:
got 2 questions about the 4.4.4 rom. when the official first came out i installed it but had problems being able to install to the external sd or save downloaded files to it. i had tried the normal program called sdfix that had allways worked in 4.4.2 but never worked for me on the 4.4.4, maybe it was me and something i did wrong at the time but does save to external sd work in this? also i am on 4.4.2 and everything works great for me now but i like the newest and greatest is there anything that great that is in 4.4.4 over .2? i havent read any post about .4 and whats better. thanks for giving us this pre-rooted stock rom though.
Click to expand...
Click to collapse
Really I see no visual different . The change log, I will add to op. I think 4.4.4 is maybe a step closer for android 5.0 , like NB4 was for kitkat.
carl1961 said:
I see no problem but if you do just let me know we'll see what we can do
Click to expand...
Click to collapse
Thanks for quick response ... I have TMobile Note 3 SM-N900T with 4.4.2 Bootloader and Modem and ROM with Phil CWM recovery.
I flashed the Deodex rooted file from OP. The flash was fine. After phone started I heard Att sound. I also saw menu and back keys light up like after we clear dalvik. However screen remained blank. I tested it for 5 minutes then rebooted to recovery and restored my nandroid backup
cnewsgrp said:
Thanks for quick response ... I have TMobile Note 3 SM-N900T with 4.4.2 Bootloader and Modem and ROM with Phil CWM recovery.
I flashed the Deodex rooted file from OP. The flash was fine. After phone started I heard Att sound. I also saw menu and back keys light up like after we clear dalvik. However screen remained blank. I tested it for 5 minutes then rebooted to recovery and restored my nandroid backup
Click to expand...
Click to collapse
Did you install a 4.4.4 kernel ?
you may also need the overlay lib files and the hw file hwcomposer.msm8974.so from a TMobile rom
carl1961 said:
Did you install a 4.4.4 kernel ?
you may also need the overlay lib files and the hw file hwcomposer.msm8974.so from a TMobile rom
Click to expand...
Click to collapse
No I did not install 4.4.4 kernel. Also I am on 4.4.2 bootloader and modem.
I am not sure I can overlay library files when screen is blank.
Looks like installation of att rom is not as easy as i thought
Safestrap
Hi, I followed your instruction to the T, but when I rebooted the ROM works great but I can't get back to Safestrap. Do I have to reinstall it? THx
gordec said:
Hi, I followed your instruction to the T, but when I rebooted the ROM works great but I can't get back to Safestrap. Do I have to reinstall it? THx
Click to expand...
Click to collapse
You have to install NC2 kernel to get back to recovery, safestrap will not run with 4.4.4 kernel.
carl1961 said:
You have to install NC2 kernel to get back to recovery, safestrap will not run with 4.4.4 kernel.
Click to expand...
Click to collapse
Great thank you. So all I have to do is flash NC2 kernel in Odin if I ever want safestrap back. I'm kind of enjoy not having to wait for Safestrap message right now, and it's booting super fast. THx
gordec said:
Great thank you. So all I have to do is flash NC2 kernel in Odin if I ever want safestrap back. I'm kind of enjoy not having to wait for Safestrap message right now, and it's booting super fast. THx
Click to expand...
Click to collapse
Yes a threads here just for that. http://forum.xda-developers.com/note-3-att/general/att-nj5-safestrap-t2957471
Since I rooted and installed successfully, several different ROMs, I am at a loss as to why vibration functionality is no longer working.
The only thing I did not do was restore to my original back up since a dev friend of mine wiped it out! Any insights are welcome and thanks in advance.
AT&T HTC One M8
Currently running 5.0.1 Lollipop on a version of 3.4.0 Kernel.
I am not a developer and am new to this whole thing. I figured the easiest thing to do it to share my ABOUT screen. Again, everything is working EXCEPT for the vibration.
If there is any other info which could help, please ask and I will do my best to get the info to you ASAP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bump
Sent from my HTC One_M8 using XDA Free mobile app
Maybe it's an actual hardware issue.
No, I don't think so. It was working fine until I raised and installed a new ROM. I had received 4.4.4 OTA and still it worked, but one I installed what appears to be GPE 5.0.1 I have not been able to get it working.
I am trying to troubleshoot, but the software methid I know for this will not work. I'm wondering if theme is a way to issue a command via adb which would ensure it should be working to verify if it is invest hard are related or not.
You should have an app called HTC guide (or if not can get it off the play store I believe). It has a hardware diagnose section that has vibration test.
GA_Android said:
Since I rooted and installed successfully, several different ROMs, I am at a loss as to why vibration functionality is no longer working.
The only thing I did not do was restore to my original back up since a dev friend of mine wiped it out! Any insights are welcome and thanks in ]
Click to expand...
Click to collapse
"The only thing" you did not do? Are you sure? Did you try to revert to stock 4.4.4? Did you RUU? Did you update the firmware?
Instead of saying what you "didn't" do, its much more helpful to fully describe what you did do. Just mentioning that you tried "several different ROMs" without specifying which ones, doesn't help us much to help you.
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
GA_Android said:
but one I installed what appears to be GPE 5.0.1 I have not been able to get it working.
Click to expand...
Click to collapse
Need to be specific on what ROM, or how you got to GPE. Otherwise, its hard to help.
S-off or s-on?
Did you do a RUU conversion to GPE?
ROM Lollipop 5.0.1 LRX22C
All I did was flash the boot.img and it does appears I'm on GPE but not sure how or why.
S on
I had been on stock 4.4.4 OTA and did a complete backup using TWRP but that got wiped out.
Ive tired to find a way back to 4.4.4 just to troubleshoot, but have been unsuccessful.
Sorry I can't be more helpful. This situation was handed to me.
GA_Android said:
ROM Lollipop 5.0.1 LRX22C
All I did was flash the boot.img and it does appears I'm on GPE but not sure how or why.
Click to expand...
Click to collapse
Its not clear whether that is a stock ROM, or custom, or where it came from.
You just flashed boot.img? How about the rest of the ROM?
GA_Android said:
Ive tired to find a way back to 4.4.4 just to troubleshoot, but have been unsuccessful.
Click to expand...
Click to collapse
Relock the bootloader with the command: fastboot oem lock
Then download and run the official 4.4.4 RUU (with phone connected to PC): http://dl3.htc.com/application/RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
RUU will wipe the phone. So backup any important personal data before RUU.
Sorry. I was trying to reply from my phone during a meeting. I should have known better
The goal was to get on a version of lollipop GPE.
I installed TWRP, created a backup.
Backed up all others details to my PC
Found what I thought was a compatible stock lollipop GPE ROM
Flashed the boot.img via adb
Then I used TWRP to wipe/factory reset
Then flashed the ROM from bootloader>recovery>TWRP.
The ROM came from this site.
After that install, I noticed the issue with no vibration. Looked all over for info or others with the same issue, but no luck.
A developer friend was helping troubleshoot that problem and he totally wiped the phone including my backup of stock 4.4.4 OTA, so restore was no longer possible. (Side note: The look on his face when I explained that he just wiped away the backups was PRICELESS. He was horrified!)
He then attempted to do some firmware flashes etc... soft bricked the phone so I took over from there.
Since then, I have been able to get back to the working stock Lollipop 5.0.1 GPE, (all working except vibration) and also tried 5.0.1 SkyDragon 39.0 WWE with the same no vibe issue, so currently I am restored back to the stock Lollipop 5.0.1 GPE
Anything older I have tried, I get no phone service or not SIM detected. I have tired various firmwares etc, to remedy from there, still no dice.
Barring any further insight, I'll try your suggestion. I really appreciate your input and the links. Thanks a bunch.
Regarding your suggestion, if I relock the bootloader, how would I unlock it again? Same process via HTCdev?
I suggest never asking that friend for help again! lol
In particular, wiping something from the phone without knowing what he was wiping is a n00b mistake, and not usually something someone with any experience would do.
GA_Android said:
Regarding your suggestion, if I relock the bootloader, how would I unlock it again? Same process via HTCdev?
Click to expand...
Click to collapse
Sometimes you can just fastboot the old token again. But if that doesn't work, then yes just go through the process again on HTCDev.com to request a new token.
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
GA_Android said:
The goal was to get on a version of lollipop GPE.
I installed TWRP, created a backup.
Backed up all others details to my PC
Found what I thought was a compatible stock lollipop GPE ROM
Flashed the boot.img via adb
Then I used TWRP to wipe/factory reset
Then flashed the ROM from bootloader>recovery>TWRP.
The ROM came from this site.
Click to expand...
Click to collapse
Its not normally required to flash boot.img separately on this device. In fact, when you flashed the ROM, you over-wrote the boot.img that you flashed manually, anyway.
Not sure what stock GPE LP ROM you are referring to (and I know you can't link yet with <10 posts). But at least for LP Sense ROMs like Skydragon 39, its required to have the LP firmware otherwise you are going to have some bugs. For GPE ROMs, you need to refer to the specific ROM thread to see what firmware is required.
redpoint73 said:
Its not clear whether that is a stock ROM, or custom, or where it came from.
You just flashed boot.img? How about the rest of the ROM?
Relock the bootloader with the command: fastboot oem lock
Then download and run the official 4.4.4 RUU (with phone connected to PC): http://dl3.htc.com/application/RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
RUU will wipe the phone. So backup any important personal data before RUU.
Click to expand...
Click to collapse
redpoint73 said:
I suggest never asking that friend for help again! lol
In particular, wiping something from the phone without knowing what he was wiping is a n00b mistake, and not usually something someone with any experience would do.
Sometimes you can just fastboot the old token again. But if that doesn't work, then yes just go through the process again on HTCDev.com to request a new token.
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
Its not normally required to flash boot.img separately on this device. In fact, when you flashed the ROM, you over-wrote the boot.img that you flashed manually, anyway.
Not sure what stock GPE LP ROM you are referring to (and I know you can't link yet with <10 posts). But at least for LP Sense ROMs like Skydragon 39, its required to have the LP firmware otherwise you are going to have some bugs. For GPE ROMs, you need to refer to the specific ROM thread to see what firmware is required.
Click to expand...
Click to collapse
Thanks for helping. I got it all back to stock and still, the problems persists so I called AT&T advanced support and they are replacing it. I will be back soon as I plan to root my new phone when I get it AND I plan play around with my Galaxy Tab 10.1!
GA_Android said:
I got it all back to stock and still, the problems persists
Click to expand...
Click to collapse
Meaning you used RUU?
redpoint73 said:
Meaning you used RUU?
Click to expand...
Click to collapse
Yes. I locked bootloader and used the RUU and vibration is still dead. So clearly it was no software issue. JUst very unhappy coincidence of timing with the ROM installs and a hardware failure.
Replacement on the way.
GA_Android said:
Yes. I locked bootloader and used the RUU and vibration is still dead.
Click to expand...
Click to collapse
Ok, thanks. Just curious and wanted to see some closure on what part of my posts worked for you.
I wanted to give you all an early set of instructions on properly moving to Lollipop. Being that I have already been through the trials & errors of this subject with the note 4, i wanted to give you all a head start to save you a bunch of time scratching your heads wondering why your stock ota/odin flash is buggy. It seems that the stock Lollipop tar's don't wipe everything especially data. So when you go to Odin the stock Lollipop tar without first wiping from your current custom recovery, you WILL have left over data which causes some issues. ALWAYS wipe everything per usual (including the factory reset option) BEFORE you odin the stock Lollipop tar. It's also been noticed that the Lollipop ota hasn't been nearly as stable as the official rom tar. So even if you took the official ota, I would recommend following these simple instructions for the best results. If you have never rooted your device then you can disregard otherwise keep reading. For the BEST trouble-free experience do the following.
***First you will need to download and copy to your sd-card the custom/stock rom zip*** (Custom/Stock ROMs are coming soon!)
1. Wipe everything several times in current custom recovery (including factory reset option) (TWRP recommended)
2. Odin the official lollipop tar.
3. Setup rom per usual. (At this point if you want to remain on the stock ROM you can stop here)
4. Enable usb debugging.
5. Reboot to download mode and odin the compatible cf-auto-root for your device.
6. Odin latest TWRP compatible with your device.
7. At this point you will be ready to flash a stock or custom Lollipop rom.]
Get ready. Roms will be coming soon... you will need to know this important info before you start flashing.
Thank you for the great information. May I ask that you please fix your font colors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tx_dbs_tx said:
Get ready. Roms will be coming soon... you will need to know this important info before you start flashing.
Click to expand...
Click to collapse
just to be clear, you're recommending that we Odin the stock tar, even if we're already rooted w/ custom recovery (on KK, as an example)?
and again, a sincere *thank you* for your attention to this device and its forum.
garyfunk said:
Thank you for the great information. May I ask that you please fix your font colors?
Click to expand...
Click to collapse
Looks ok here so....
Switch to a dark theme.
kingdazy said:
just to be clear, you're recommending that we Odin the stock tar, even if we're already rooted w/ custom recovery (on KK, as an example)?
and again, a sincere *thank you* for your attention to this device and its forum.
Click to expand...
Click to collapse
If you are going to flash a Lollipop based ROM, then yes Odin the OC5 update first. You will need to re-root and flash another custom recovery but it will be well worth it!
weavr said:
If you are going to flash a Lollipop based ROM, then yes Odin the OC5 update first. You will need to re-root and flash another custom recovery but it will be well worth it!
Click to expand...
Click to collapse
interesting! I have no issue doing it, if that's the req. easy enough to do. (you can see i've been here for a while)
But can you (or someone like @tx_dbs_tx ) explain why?
(my point being, if I haven't yet odin'd the stock tar or gone the route to receive the OTA already, it seems redundant to wait for tx_dbs_tx to put out his rom at this point. since being req'ed to odin and reroot will get me the same as what I would be about to flash... make sense? lol)
kingdazy said:
interesting! I have no issue doing it, if that's the req. easy enough to do. (you can see i've been here for a while)
But can you (or someone like @tx_dbs_tx ) explain why?
(my point being, if I haven't yet odin'd the stock tar or gone the route to receive the OTA already, it seems redundant to wait for tx_dbs_tx to put out his rom at this point. since being req'ed to odin and reroot will get me the same as what I would be about to flash... make sense? lol)
Click to expand...
Click to collapse
If you are currently on any version of KitKat you MUST either take the official Lollipop ota update OR wipe everything in your current recovery and Odin flash the official Lollipop rom tar. you MUST do one or the other before flashing any custom/stock rooted Lollipop rom or you WILL have a non booting phone. If you simply fash a Lollipop rom with a KK bootloader & carrier partitions, it will be a no go and you will have to start over by odin'ing the stock Lollipop rom tar. Lollipop brings a lot of new things and most importantly there afe partitions that must be written to your phone that are required. Simply flashing a custom or even a stock rooted Lollipop ROM WILL NOT write these important partitions. Only the official rom tar will do this as well as the regular ota. So no, the stock rooted rom i'm working on will not properly upgrade your phone to Lollipop. If you plan to move to Lollipop (which i highly recommend due to major system optimizations, features, etc) then go ahead and prep by flashing the official Lollipop rom tar using the wipe methods i explained above. Trust me it will save you a lot of grief. I hope this makes sense.
Edit: I need a couple of people to help me troubleshoot and test the stock rooted lollipop rom i'm trying to finish. I have one person helping me but his work schedule interferes. If you have some basic knowledge on how to flash, use root explorer and also know how to extract and zip a rom, please pm me and i'll give you the files and info you need. I'd like to help you all get a couple of stock rooted roms going so others can then have something to work with for future themes, roms, etc.
i would be happy to help
tx_dbs_tx said:
If you are currently on any version of KitKat you MUST either take the official Lollipop ota update OR wipe everything in your current recovery and Odin flash the official Lollipop rom tar. you MUST do one or the other before flashing any custom/stock rooted Lollipop rom or you WILL have a non booting phone. If you simply fash a Lollipop rom with a KK bootloader & carrier partitions, it will be a no go and you will have to start over by odin'ing the stock Lollipop rom tar. Lollipop brings a lot of new things and most importantly there afe partitions that must be written to your phone that are required. Simply flashing a custom or even a stock rooted Lollipop ROM WILL NOT write these important partitions. Only the official rom tar will do this as well as the regular ota. So no, the stock rooted rom i'm working on will not properly upgrade your phone to Lollipop. If you plan to move to Lollipop (which i highly recommend due to major system optimizations, features, etc) then go ahead and prep by flashing the official Lollipop rom tar using the wipe methods i explained above. Trust me it will save you a lot of grief. I hope this makes sense.
Edit: I need a couple of people to help me troubleshoot and test the stock rooted lollipop rom i'm trying to finish. I have one person helping me but his work schedule interferes. If you have some basic knowledge on how to flash, use root explorer and also know how to extract and zip a rom, please pm me and i'll give you the files and info you need. I'd like to help you all get a couple of stock rooted roms going so others can then have something to work with for future themes, roms, etc.
Click to expand...
Click to collapse
i did some testing for you on the note 4. i would be happy to test for you on the note 3 as well.
tx_dbs_tx said:
If you are currently on any version of KitKat you MUST either take the official Lollipop ota update OR wipe everything in your current recovery and Odin flash the official Lollipop rom tar. you MUST do one or the other before flashing any custom/stock rooted Lollipop rom or you WILL have a non booting phone. If you simply fash a Lollipop rom with a KK bootloader & carrier partitions, it will be a no go and you will have to start over by odin'ing the stock Lollipop rom tar. Lollipop brings a lot of new things and most importantly there afe partitions that must be written to your phone that are required. Simply flashing a custom or even a stock rooted Lollipop ROM WILL NOT write these important partitions. Only the official rom tar will do this as well as the regular ota. So no, the stock rooted rom i'm working on will not properly upgrade your phone to Lollipop. If you plan to move to Lollipop (which i highly recommend due to major system optimizations, features, etc) then go ahead and prep by flashing the official Lollipop rom tar using the wipe methods i explained above. Trust me it will save you a lot of grief. I hope this makes sense.
Edit: I need a couple of people to help me troubleshoot and test the stock rooted lollipop rom i'm trying to finish. I have one person helping me but his work schedule interferes. If you have some basic knowledge on how to flash, use root explorer and also know how to extract and zip a rom, please pm me and i'll give you the files and info you need. I'd like to help you all get a couple of stock rooted roms going so others can then have something to work with for future themes, roms, etc.
Click to expand...
Click to collapse
I xm test what ever you need. Its 305 ill be home and fully charged by 5 shoot me a pm. Cant test anything. Im fully updated via Odin. And Knox has been triple since day 1. So ill test lol
Sent from my 0x1 Note 3...... I love tep
I can test a rom. I am currently working on building my own and have been failing. I finally got everything deodexed, but building a rom that boots is another story. TWRP backup really messed things up. Have been using Odin to flash the official stock tar about 5 times now to try and get to a clean base. I found a DevBase in 9005 thread that I am testing now. Would love to get something going on this phone to help others (make a minimal devbase for others) since I haven't found a kitchen that works. ArchiKitchen does not work for our device, at least not without some editing
UPDATE: So I finally got it to flash, time to cut down on some of the extraneous files that won't be needed. I'll probably throw it together and post a thread for people to use as a base, just add their own stuff. I'm not looking at releasing a ROM just yet, just a base for people to build on.
I can still test yours and see how it goes. There was an issue with mine where it hung on first boot, booted into recovery and reboot system, all is fine.
tx_dbs_tx said:
Lollipop brings a lot of new things and most importantly there afe partitions that must be written to your phone that are required. Simply flashing a custom or even a stock rooted Lollipop ROM WILL NOT write these important partitions. Trust me it will save you a lot of grief. I hope this makes sense.
Edit: I need a couple of people to help me troubleshoot and test the stock rooted lollipop rom i'm trying to finish...
Click to expand...
Click to collapse
thank you for taking the time to explain. since I had a kid a little over a year ago, I've been out of the loop. (barely time to flash things, nonetheless read the tech details like I used to...) I knew LP had a lot of changes under the hood (art, etc), but was unaware of the partition changes.
I'd like to toss you a bit of a donation for your stockROMs when they come out. your time here is appreciated.
Hello everyone!
I'm new around here and it would be much appreciated if you guys can help me out a little.
As the title says i have a Verizon Samsung galaxy s4
SCH-I545
Android version: 5.0.1
Baseband: I545VRSGPL1
Build number: LRX22C.I545VRSGPL1
Knox version: 2.3
Can i install a custom recovery like TWRP and then install a custom ROM ?
I previously had a HTC One M7 International and i unlocked the bootloader and installed TWRP recovery along with several other ROMS through my usage of the phone. Is there a way to do the same thing with this Verizon S4 ?
Thanks for your help!!
Coincidentally, I just got an S4 yesterday. It has the same build number. I got it rooted with the Kingroot and SuperSU script mentioned here. I've looked on the forums for information about replacing the ROM, but they all mention different build numbers. I'd like to update the ROM in this phone as well.
After getting root, I flashed this ROM, using the OF1 instructions.
https://forum.xda-developers.com/galaxy-s4-verizon/development/stang5litre-ediition-5-0-t3132555
It installed correctly, but once I unlock and get to the home screen, I get a a constant "...gapps has stopped" popup error. It seems to be related to the Google search box on the home screen. Any ideas on how to correct this?
I fixed the gapps problem see "Readers' favorite comments" here:
https://www.androidpit.com/process-com-google-process-gapps-has-stopped-fix
---------- Post added at 07:17 PM ---------- Previous post was at 06:45 PM ----------
Now that I have the STANG5LITRE ROM installed and working, is there any way to flash an earlier ROM/bootloader, so I can install CWM or TWRP? I'd like to try installing other ROMs. Although I got this phone for free, and it is not my primary phone, I'd hate to brick it. If not, are there any other ROMs that I can flash, considering the locked bootloader?
No, there is no TWRP or CMW for this device as the bootloader is locked. Flashfire is the only option to flash ROMs. So make sure you have the latest tar to recover if you have a bootloop or something like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks. Where can I find the PL1 original ROM?
I can't get WiFi to turn on with either the STANG5LITRE ROM or this one: https://forum.xda-developers.com/ga...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009
I used the OC1 instructions. I also tried the OF1 WiFi fix. I'm about to try this: https://forum.xda-developers.com/showpost.php?p=67174300&postcount=424
Edit: Well, that FlashFire version doesn't run. It closes right away.
For PL1, what is the best performing, least bloated TW ROM (pre-rooted or rootable) without a bunch of bells and whistles added? It seems that all the really good ROMs need an unlocked bootloader. I won't be using this S4 as a phone (no SIM), but I would like the WiFi to work.
mojoehand said:
Thanks. Where can I find the PL1 original ROM?
I can't get WiFi to turn on with either the STANG5LITRE ROM or this one: https://forum.xda-developers.com/ga...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009
I used the OC1 instructions. I also tried the OF1 WiFi fix. I'm about to try this: https://forum.xda-developers.com/showpost.php?p=67174300&postcount=424
Edit: Well, that FlashFire version doesn't run. It closes right away.
For PL1, what is the best performing, least bloated TW ROM (pre-rooted or rootable) without a bunch of bells and whistles added? It seems that all the really good ROMs need an unlocked bootloader. I won't be using this S4 as a phone (no SIM), but I would like the WiFi to work.
Click to expand...
Click to collapse
You have to use v.53 or older of FF, the newer builds don't work on this device. Stanglitre's was the only one that everything worked for me for the short time I had this device. You can debloat whatever you don't use with ROM Toolbox or whatever app of your choosing.
All Odin flashable tars can be found at www.sammobile.com
bilgerryan said:
You have to use v.53 or older of FF, the newer builds don't work on this device. Stanglitre's was the only one that everything worked for me for the short time I had this device. You can debloat whatever you don't use with ROM Toolbox or whatever app of your choosing.
All Odin flashable tars can be found at www.sammobile.com
Click to expand...
Click to collapse
I did use FF v0.53 to flash both ROMs.. After playing around with it, I really like the S6 ROM. I just wish I could get the WiFi working. Bluetooth seems to work. I side loaded Titanium Backup to remove some apps.
mojoehand said:
I did use FF v0.53 to flash both ROMs.. After playing around with it, I really like the S6 ROM. I just wish I could get the WiFi working. Bluetooth seems to work. I side loaded Titanium Backup to remove some apps.
Click to expand...
Click to collapse
I never flashed with PL1, I would see if you could Odin back to OF1, I was able to switch between OF1 and OC1. That's probably the only way the WiFi fix will work for you.
Because of the locked bootloader, I was hesitant to downgrade. Based on your statement that you were able to go from OF1 to OC1, I took a chance.
I found a stock, rooted OF1 online and flashed with FF. This worked fine. I then used the OF1 instructions to install the S6 ROM. I am happy to say that WiFi is now working.
Thanks for all your help.
mojoehand said:
Because of the locked bootloader, I was hesitant to downgrade. Based on your statement that you were able to go from OF1 to OC1, I took a chance.
I found a stock, rooted OF1 online and flashed with FF. This worked fine. I then used the OF1 instructions to install the S6 ROM. I am happy to say that WiFi is now working.
Thanks for all your help.
Click to expand...
Click to collapse
I know this is an old thread and you've no doubt moved on but if you can recall the stock rooted rom you flashed?
It be greatly appreciated. I'm on pl1 bootloader and there's very little info out there. Thanks
KLit75 said:
I know this is an old thread and you've no doubt moved on but if you can recall the stock rooted rom you flashed?
It be greatly appreciated. I'm on pl1 bootloader and there's very little info out there. Thanks
Click to expand...
Click to collapse
I don't remember where I found it, but the file name is: I545_OF1_Stock_Rooted_ROM.zip
mojoehand said:
I don't remember where I found it, but the file name is: I545_OF1_Stock_Rooted_ROM.zip
Click to expand...
Click to collapse
Thanks man! That was just enough info...
https://androidfilehost.com/?fid=24052804347797371
KLit75 said:
Thanks man! That was just enough info...
https://androidfilehost.com/?fid=24052804347797371
Click to expand...
Click to collapse
I recommend Stanglitre's ROM for this device. Definitely has more options than stock.
mojoehand said:
I did use FF v0.53 to flash both ROMs.. After playing around with it, I really like the S6 ROM. I just wish I could get the WiFi working. Bluetooth seems to work. I side loaded Titanium Backup to remove some apps.
Click to expand...
Click to collapse
So again, this is a little old and you might not recall but figured you'd be my best chance at solving it.
I couldnt get any flashfire .53 or below to work (tried about 5 different versions, immediate FC or itd crash seconds later.) Strangely, the latest version right from play store worked.
I did a full wipe then flashed the stock rooted rom. It started the process, briefly showed the samsung logo then the code rolled down the screen (all seemed fine.) Then it went black and stayed black with the blue led light remaining solid. I let it remain with the black screen for 15 minutes then pulled the battery.
To my surprise, it booted into the previously installed rom, all the data remains.
Do you have any theories? Its almost as if the phone blocked the installation, which would make sense I guess but cant understand why it didn't so much as erase the cache partition...
Anyway, I just thought I'd ask in case you recall encountering or reading anything like this when you were trying to downgrade. Thanks again!
bilgerryan said:
I recommend Stanglitre's ROM for this device. Definitely has more options than stock.
Click to expand...
Click to collapse
How about You? Did u also have a pl1 and successfully downgrade with FF?
My last post details the problem I ran into using FF.
THANKS!
KLit75 said:
How about You? Did u also have a pl1 and successfully downgrade with FF?
My last post details the problem I ran into using FF.
THANKS!
Click to expand...
Click to collapse
No, PL1 wasn't out when I had this device. Flashfire is really touchy, I had to try a bunch of different versions before I found one that worked for this device (v.53 is what worked for me). Make sure you follow the ROM flashing instructions to the letter. I haven't had this device for over a year, so this is all from memory.
bilgerryan said:
I recommend Stanglitre's ROM for this device. Definitely has more options than stock.
Click to expand...
Click to collapse
bilgerryan said:
No, PL1 wasn't out when I had this device. Flashfire is really touchy, I had to try a bunch of different versions before I found one that worked for this device (v.53 is what worked for me). Make sure you follow the ROM flashing instructions to the letter. I haven't had this device for over a year, so this is all from memory.
Click to expand...
Click to collapse
Thanks. I might need to do some more digging. Maybe you can't flash a rom on pl1 (verizon). But on a few posts I did see people saying FF took a really long time (30+ MINS on black screen) but I can't see why it'd take 15 MINS before it even wiped data.
KLit75 said:
Thanks. I might need to do some more digging. Maybe you can't flash a rom on pl1 (verizon). But on a few posts I did see people saying FF took a really long time (30+ MINS on black screen) but I can't see why it'd take 15 MINS before it even wiped data.
Click to expand...
Click to collapse
As far as I know, PL1 is just a security update, I am 95% sure you will have to Odin back to OF1 or OC1 to get WiFi to work on any of the available ROMs. Check out this post also - https://forum.xda-developers.com/showthread.php?p=73513294. I would personally try that ROM first too, it's got the most complete instructions and most stable in my opinion. Also make sure you have SuperSU binary. I recommend using the free trial of a Windows program called Wondershare (Google "Wondershare root exe"). It's the easiest way to get SuperSU and root, the trial is only 5 days though, but that should be enough to get the job done.
bilgerryan said:
As far as I know, PL1 is just a security update, I am 95% sure you will have to Odin back to OF1 or OC1 to get WiFi to work on any of the available ROMs. Check out this post also - https://forum.xda-developers.com/showthread.php?p=73513294. I would personally try that ROM first too, it's got the most complete instructions and most stable in my opinion. Also make sure you have SuperSU binary. I recommend using the free trial of a Windows program called Wondershare (Google "Wondershare root exe"). It's the easiest way to get SuperSU and root, the trial is only 5 days though, but that should be enough to get the job done.
Click to expand...
Click to collapse
I really appreciate the help. So pl1 doesn't have an updated bootloader? And I can just flash any lollipop firmware?
I'm relatively new to Samsung but I do have an S7 EDGE. Ive used Odin before but my s7 is unlocked. However I know other s7 users are able to flash U firmware on carrier branded devices. Can I do that on the S4 Verizon?
And I read in multiple places, even if I downgrade, I have to flash a touchwiz based rom. Afaik there's 2 available (stang5litre & an s6 rom). Its my understanding that those are the only roms that'll boot.
Thanks again!
Hello everyone (Sorry I'm french from Benin so excuse my faults)
I tried to flash the TWRP recovery on my Verizon S4 from Terminal Emulator. But when i tried to reboot into recovery, the phone stucked in a Startup failed screen. But with some chances, i was able to boot my phone back and run my system.
Now i want the stock recovery of my VRUGOF1 firmware so that my Recovery partition table will be filled with the stock one. Please help me to deal with that...
And also there is something very weird about this phone. I bought a used S4 Verizon from someone. But in the phone, it is said that this is the s4 i9500 model but the bootloader version is I545VRUGOF1. So I'm pretty much sure this is an Verizon S4. Am confused. The phone is unlocked so that it support carriers other than Verizon. I was planning to flash the stock latest lollipop update I545VRSGPL1 and see if my phone will come back to his normal state. But the clue is that i'm afraid of losing the carrier unlocking.
Please, help me....
EsperaKing said:
Hello everyone (Sorry I'm french from Benin so excuse my faults). I tried to flash the TWRP recovery on my Verizon S4 from Terminal Emulator. But when i tried to reboot into recovery, the phone stucked in a Startup failed screen. But with some chances, i was able to boot my phone back and run my system. Now i want the stock recovery of my VRUGOF1 firmware so that my Recovery partition table will be filled with the stock one. Please help me to deal with that... And also there is something very weird about this phone. I bought a used S4 Verizon from someone. But in the phone, it is said that this is the s4 i9500 model but the bootloader version is I545VRUGOF1. So I'm pretty much sure this is an Verizon S4. Am confused. The phone is unlocked so that it support carriers other than Verizon. I was planning to flash the stock latest lollipop update I545VRSGPL1 and see if my phone will come back to his normal state. But the clue is that i'm afraid of losing the carrier unlocking. Please, help me....
Click to expand...
Click to collapse
First of all, you can't flash TWRP on an S4 with OF1 firmware because the bootloader is locked up.
If you require the Verizon S4 Stock OF1 firmware, i have them all on the my File Host Account here (just unzip the file):
https://www.androidfilehost.com/?w=files&flid=158750
Good Luck!
~~~~~~~~~~~~~~~
I Am The Egg Man,
They Are The Egg Men.
I Am The Walrus!
Coo Coo Cachoo!
Thanks you @Ibuprophen, I will download the ROM from your link. You're right about the TWRP recovery. But, what do you think I can do in order to flash a custom recovery on my phone so that I can install the S4 S8 WizCyan Rom on my phone? I thought there was an loki bypass method since 2013 that was used to bypass the bootloader lock.
Also, I was asking if flashing the stock rom of the phone won't re-lock the carrier.
Thanks you again. :
EsperaKing said:
Thanks you @Ibuprophen, I will download the ROM from your link. You're right about the TWRP recovery. But, what do you think I can do in order to flash a custom recovery on my phone so that I can install the S4 S8 WizCyan Rom on my phone? I thought there was an loki bypass method since 2013 that was used to bypass the bootloader lock.
Also, I was asking if flashing the stock rom of the phone won't re-lock the carrier.
Thanks you again. :
Click to expand...
Click to collapse
Root then flash ROM with Flashfire. Bootloader is locked, custom recovery cannot be installed. Yes, it probably will "re-lock carrier". Root methods are in the General Section of this forum.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Root then flash ROM with Flashfire. Bootloader is locked, custom recovery cannot be installed. Yes, it probably will "re-lock carrier". Root methods are in the General Section of this forum.
Click to expand...
Click to collapse
Thanks you bilgerryan for replying me.
So, I can flash the S4 S8 WizCyan ROM with FlashFire? That's good to know. I'm already rooted with Kingroot.
But, about the carrier lock, I learnt somewhere that it's most likely an hardware lock, so if it's unlocked once, it's means that it won't re-lock after flashing or anything. Because, before this phone, I bought an S4 AT&T i337 which was unlocked and I restored it's Stock rom with odin, afrer that, the carrier was still unlocked so it's worked with an non AT&T network. I was wondering if it'll be the same with this one too (S4 Verizon i545).
Thanks you again...
EsperaKing said:
Thanks you bilgerryan for replying me.
So, I can flash the S4 S8 WizCyan ROM with FlashFire? That's good to know. I'm already rooted with Kingroot.
But, about the carrier lock, I learnt somewhere that it's most likely an hardware lock, so if it's unlocked once, it's means that it won't re-lock after flashing or anything. Because, before this phone, I bought an S4 AT&T i337 which was unlocked and I restored it's Stock rom with odin, afrer that, the carrier was still unlocked so it's worked with an non AT&T network. I was wondering if it'll be the same with this one too (S4 Verizon i545).
Thanks you again...
Click to expand...
Click to collapse
You'll need SuperSU instead of KingRoot to use Flashfire, there's also a guide for that in the General section of this forum.
@bilgerryan @Ibuprophen
Okay, thanks you.
So what are you saying about the carrier. Should I restore? Or not?
EsperaKing said:
@bilgerryan @Ibuprophen
Okay, thanks you.
So what are you saying about the carrier. Should I restore? Or not?
Click to expand...
Click to collapse
You really don't need stock recovery, I wouldn't if I were you. Anything that can be done in stock recovery can be done through Flashfire.
Okay @bilgerryan
1- The system sometimes restarts bt itself and after restart it's stuck on com.android.system has stopped, so I thought that restoring it would fix those problems. Also the phone show model i9500 and bootloader i545, I will attach the screen shot.
2- I tried to replace king root with supersu with SuperSume app, no sucess. I also tried with terminal emulator, it shows failed and it uninstall king root. And permanently pop-up com.android.kinguser has stopped until I restart the phone. After restarting root is gone.
So I want to restore in other to restart all this from fresh stock firmware. But if you have any other ideas, please let me know how to just get root with supersu and use flashfire...
Thanks for replying. ...
EsperaKing said:
Okay @bilgerryan
1- The system sometimes restarts bt itself and after restart it's stuck on com.android.system has stopped, so I thought that restoring it would fix those problems. Also the phone show model i9500 and bootloader i545, I will attach the screen shot.
2- I tried to replace king root with supersu with SuperSume app, no sucess. I also tried with terminal emulator, it shows failed and it uninstall king root. And permanently pop-up com.android.kinguser has stopped until I restart the phone. After restarting root is gone.
So I want to restore in other to restart all this from fresh stock firmware. But if you have any other ideas, please let me know how to just get root with supersu and use flashfire...
Thanks for replying. ...
Click to expand...
Click to collapse
In that case, you'll probably have to restore stock with Odin and start over.
bilgerryan said:
In that case, you'll probably have to restore stock with Odin and start over.
Click to expand...
Click to collapse
Okay, I will restore in a few minutes and let you know.
bilgerryan said:
In that case, you'll probably have to restore stock with Odin and start over.
Click to expand...
Click to collapse
Hi @bilgerryan and all xda members.
I restored the stock rom with Odin and everything goes fine. I rooted then replaced kingroot with supersu succesfully.
The problem now is that after installing supersu, I installed FlashFire and tried a backup of my system. The screen goes black with some blank text. After that, there is nothing else that happens. My phone will stay stucked on a black screen with a blue led on on top. But nothing happens, I have to pull battery and reinsert in other to power on my phone. I can't use Flashfire.
Hope you reply me....Thanks.
EsperaKing said:
Hi @bilgerryan and all xda members.
I restored the stock rom with Odin and everything goes fine. I rooted then replaced kingroot with supersu succesfully.
The problem now is that after installing supersu, I installed FlashFire and tried a backup of my system. The screen goes black with some blank text. After that, there is nothing else that happens. My phone will stay stucked on a black screen with a blue led on on top. But nothing happens, I have to pull battery and reinsert in other to power on my phone. I can't use Flashfire.
Hope you reply me....Thanks.
Click to expand...
Click to collapse
You have to use v.53 of Flashfire. The newer versions don't play nice, also a backup with Flashfire is useless, if you have a bootloop you wouldn't be able to use it anyways. You just Odin stock again if you have any problems.
bilgerryan said:
You have to use v.53 of Flashfire. The newer versions don't play nice, also a backup with Flashfire is useless, if you have a bootloop you wouldn't be able to use it anyways. You just Odin stock again if you have any problems.
Click to expand...
Click to collapse
I'm installing Flashfire v53 right now, so I will make you know if it's working or not. Thanks for responding.
EsperaKing said:
I'm installing Flashfire v53 right now, so I will make you know if it's working or not. Thanks for responding.
Click to expand...
Click to collapse
It has worked like a charm. Thanks you very much. This is the last step of setting my phone. I'm going to install the S8 S4 WizCyan Rom to my phone and let you know. It should work cause I have an Snapdragon S4. I will let you know. Thanks you again
EsperaKing said:
I'm installing Flashfire v53 right now, so I will make you know if it's working or not. Thanks for responding.
Click to expand...
Click to collapse
@bilgerryan @bilgerryan
I flashed the WizCyan Rom and it's finished succesfully I also managed to install add-ons from aroma file.
After reboot it's failed to load with software update failed. Kernel error. I don't why it's not working. The installation goes succesfully. Is it the aroma add-ons that I have installed? Or it's just that the ROM is not compatible with the S4 Verizon.
I don't know how to get that ROM work for me. I'm restoring stock with odin right now. I don't know if I should try again because I learnt on a youtube video that for some people, it might failled with a soft break the first time when we use Flashfire to attempt installing a ROM so we should just restore odin, wipe data and cache from recovery and restart the process and then it'll work.
Thanks you...
EsperaKing said:
@bilgerryan @bilgerryan
I flashed the WizCyan Rom and it's finished succesfully I also managed to install add-ons from aroma file.
After reboot it's failed to load with software update failed. Kernel error. I don't why it's not working. The installation goes succesfully. Is it the aroma add-ons that I have installed? Or it's just that the ROM is not compatible with the S4 Verizon.
I don't know how to get that ROM work for me. I'm restoring stock with odin right now. I don't know if I should try again because I learnt on a youtube video that for some people, it might failled with a soft break the first time when we use Flashfire to attempt installing a ROM so we should just restore odin, wipe data and cache from recovery and restart the process and then it'll work.
Thanks you...
Click to expand...
Click to collapse
That means you didn't follow the directions.
Go into flashfire and select the ROM you're gonna flash.
Select the of1 kernel tar.
Select the of1 WiFi fix.
Select a full wipe. (System, cache, data) and hold down on the wipe so you can swipe it to the top of your list.
Don't flash the addons.