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.
Related
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/
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.
Today, I got this new System Alert showing that there's a new DELL System Update available...
{
"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"
}
Since the 7840 has been wide open for Stagefright attacks, I decided to apply this update asap.
OTA download worked smoothly, the initiated reboot sequence does take a bit longer (as advertised), then the system update cycle starts, the Android Toolbox Droid appears - and then breaks down with the usual red excamation mark protruding from its metal body, accompanied by a nondescript "Error"-message....
Only thing I can do then is to do a hard power-off (10 seconds power button-method) and then start the thing up again....
Then the Dell/Intel bootup sequence begins and after a thorough startup period, I'm back at where I started from - no harm done to the system, but no update either.... and the Dell System icon again displays the "new update available"...
Was wondering if any of you had the same problem/experience? And if so, did you find a workaround?
I had the same problem as you. I thought it was just me. Was rooted and the OTA didn't work. Then I unrooted, still same result.
Mine downloads, seems to install, reboots and when back in Lollipop, the update is proposed again.
thebreezer said:
Mine downloads, seems to install, reboots and when back in Lollipop, the update is proposed again.
Click to expand...
Click to collapse
I just got my tablet off eBay and today I got the update message. 3 times it downloaded and nothing happened. A fourth download triggered by checking for system updates via About menu went smoothly (if you consider 30 mins for a 1.8gb download smooth) and it installed correctly. The android version is now 5.1 instead of 5.0.1.
We are not talking about the 5.1 update.
Worked fine on my unrooted tablet, although it seems to have installed a bunch of rubbish such as Evernote, Camcard Free, Google Keyboard (with Pinny and Indic languages, huh?), etc, etc, etc.
if we could get the update.zip, it would most likely be possible to flash it via custom recovery. But after downloading, the file is moved from /sdcard/update.zip to somewhere else just before you can copy it to any other location. So if someone managed to keep the file, i'd be happy if it would be shared here.
I have it, will upload when I get home. The file is saved in data/data/dell ota update *or something similar under data/data.* I copied it to my sd before rebooting.
Sent from my LGLS990 using XDA Free mobile app
Here is the zip file. https://drive.google.com/file/d/0B8MfsJT1QP9NY0ZXblJyLWt0Wnc/view?usp=docslist_api Mine is only ~230mb and I have not attempted to flash it so don't blame me if it doesn't turn our like you hope.
Well it was 5.0.1 before and the Stagefright fix brought it to 5.1.
awesome, thanks. I'll try it out today in the evening and report back. Current plan is go install old 5.0 boot-img, launch tethered TWRP, install the fix and patch 5.1 boot-img back. It's about time to get permanent recovery for this shiny piece....
same for me
---------- Post added at 02:52 PM ---------- Previous post was at 02:09 PM ----------
toxic_garden said:
awesome, thanks. I'll try it out today in the evening and report back. Current plan is go install old 5.0 boot-img, launch tethered TWRP, install the fix and patch 5.1 boot-img back. It's about time to get permanent recovery for this shiny piece....
Click to expand...
Click to collapse
Wont work, will give status 7 error, tried on TWRP and CWM
olvrick said:
same for me
---------- Post added at 02:52 PM ---------- Previous post was at 02:09 PM ----------
Wont work, will give status 7 error, tried on TWRP and CWM
Click to expand...
Click to collapse
even when trying it from SD? Meh....
I'll google around if there's some way of getting the original recovery back. Since first root, it only boots back into bootloader when trying to access stock recovery. I guess it's in some way needed for this update.
I certainly hope Marshmallow arrives soon as the current situation is really a pain in the a$$
will be fun, if rooted devices wont be able to install MM6.0 update
so i gave it a try. Looks like the update checks the fingerprint of some build.prop string (most likely ro.build.fingerprint). I guess this could easily be changed, but chances are good that we mess up the whole system when being on 5.01 droidboot and applying a fix that's suited for 5.1. As i messed up my system anyways while experimenting with this whole stuff, i just started from scratch, which means putting the phone to factory state using the flash_DDO_BB.xml, dd'ing the system.img back to it's place and downloading the 5.1 update right now. After that, i'll try downloading and installing the stagefright-patch before rooting.
toxic_garden said:
so i gave it a try. Looks like the update checks the fingerprint of some build.prop string (most likely ro.build.fingerprint). I guess this could easily be changed, but chances are good that we mess up the whole system when being on 5.01 droidboot and applying a fix that's suited for 5.1. As i messed up my system anyways while experimenting with this whole stuff, i just started from scratch, which means putting the phone to factory state using the flash_DDO_BB.xml, dd'ing the system.img back to it's place and downloading the 5.1 update right now. After that, i'll try downloading and installing the stagefright-patch before rooting.
Click to expand...
Click to collapse
system.img provided here is already rooted
olvrick said:
system.img provided here is already rooted
Click to expand...
Click to collapse
well at least i wasn't able to gain root before explicitly installing the SuperSU-Package via CWM.
Back to topic: i tried nearly everything yesterday, but after 4 hours of experiments, i rest my case. For me, there's no option on installing this update without having a proper working custom recovery on 5.1.
Did anyone try going back to stock, yano like real stock, install the update via OTA and root as known?
Illux said:
Did anyone try going back to stock, yano like real stock, install the update via OTA and root as known?
Click to expand...
Click to collapse
we'd need an unrooted stock image for that. At least i don't know if there's one flying around already. Also, we'd need to create a 5.1 boot.img and droidboot.img after the stagefright patch.
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!
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
87lwrdr said:
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
Click to expand...
Click to collapse
1) This phone has a locked bootloader and has to remain on Touchwiz. Rooting methods are posted in the General section. You're stuck on Lollipop with this device, however you can flash other ROMs with Flashfire.
2. That would be software. Hardware is things such as the speaker, Home button, or the device itself.
{
"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"
}
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
87lwrdr said:
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
Click to expand...
Click to collapse
Pretty much, after 18-24 months companies just stop putting out new software (to get you to buy a new phone), that's part of the reason for using custom ROMs. This device is much older than that and has a locked bootloader, keeping you from doing a lot of things, like using a ROM with an unofficial kernel, so the latest software is not possible. The Sprint and TMo versions of this phone do not have locked bootloaders and are able to use Marshmallow and Nougat, etc. So root the phone using the one methods outlined in the General section (you need to use one that uses SuperSU to use Flashfire) of this forum and then use Flashfire to flash a custom ROM in the Android Development. New features and better functionality. I also recommend removing apps you don't use to decrease RAM consumption and increase performance.
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
87lwrdr said:
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
Click to expand...
Click to collapse
SuperSU is required to use Flashfire, but yes. I would Odin OF1 first or WiFi won't work, I would suggest Stanglitre's ROM it was the most stable I tried for the short time I had this device.
What do I use on build LRX22C.I545VRSGPL1?
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
87lwrdr said:
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
Click to expand...
Click to collapse
Yes they are for specific builds. You really picked one of the worst phones to start with. Do you have a PC?
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
87lwrdr said:
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
Click to expand...
Click to collapse
This device is more than a couple years old... But I would recommend downloading the OF1 firmware from wwe.sammobile.com and using the Odin program to flash it. Then you can use a few of the ROMs on here.
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
87lwrdr said:
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
Click to expand...
Click to collapse
You can now root it and flash a ROM. Just follow the rupturing instructions in the General section of the forum.
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
87lwrdr said:
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
Click to expand...
Click to collapse
Reflash OF1 with Odin and start over. I told you SuperSU was needed for Flashfire to work right. You need to use a root method that uses SuperSU. There is a couple guides in the General section of this forum.
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
87lwrdr said:
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
Click to expand...
Click to collapse
Try OC1 tar instead.
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
87lwrdr said:
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
Click to expand...
Click to collapse
Yes
Hi tell us how it was please...I am with the same trouble can not pass from lollipop don't have any rom mod nothing