Galaxy S5 Downgrade Failed (Verizon Screen) - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Hey guys,
I updated to Marshmellow from NI2, under the assumption that if I manually flashed, I'd be able to downgrade.
I then tried to downgrade, anndd am stuck on the red Verizon screen. I then tried to re-flash back up to Marshmellow (using the same rom that I flashed to upgrade) and am still stuck on the red Verizon screen.
I don't have safestrap or anything (I did, but apparently flashing Marshmellow removed any and all backup/restore software I had, which I also didn't know).
I did a lot of googling around and this looks like a common issue, but there is no "accepted" solution and almost all links to download what people recommend trying are removed/deleted. Is there any way to get this device functional again? I don't care about what version, I just would like the device to be functional again.
Thanks for any help!

Velero said:
Is there any way to get this device functional again? I don't care about what version, I just would like the device to be functional again.
Click to expand...
Click to collapse
1. After flashing MM you still can downgrade but you're limited to BOK3 and above.
2. If you've downgraded the firmware with Odin, you need to boot recovery and perform a factory reset. It will erase all user data but the older firmware may not boot with data from a newer firmware.
3. The first boot after factory reset usually takes 12-15 min. so you need to look at the Verizon Screen patiently. But it never takes more than 20 min.

bbsc said:
1. After flashing MM you still can downgrade but you're limited to BOK3 and above.
2. If you've downgraded the firmware with Odin, you need to boot recovery and perform a factory reset. It will erase all user data but the older firmware may not boot with data from a newer firmware.
3. The first boot after factory reset usually takes 12-15 min. so you need to look at the Verizon Screen patiently. But it never takes more than 20 min.
Click to expand...
Click to collapse
EDIT: I managed to factory reset. We'll see if it'll boot properly now.
EDIT2: Okay, the phone is back to functional, but still on 6.0.1
So is there any way for me to root at this point? If I downgrade to BOK3 is there a root method available? Or am I stuck with a non-rootable phone now?

Velero said:
So is there any way for me to root at this point? If I downgrade to BOK3 is there a root method available? Or am I stuck with a non-rootable phone now?
Click to expand...
Click to collapse
1. No. Not at this point, at least.
2. Yes, BOK3 and BPB1 are LP and they are rootable.
It's said many times already.
Here is a good thread with many things explained about G900V.

Related

5.1 OTA failed

I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .
1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update
sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.
There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM
neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.
Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.

Need help flashing stock S5 G900R4

Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e
*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.
nice one
*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc
I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely

Questions on unbricking my S5

Last night my battery got down to 5% or so and out of the blue my phone restarted and ended up in basically a boot loop (It would let me use it for about 1 minute before rebooting). I tried everything I could think of and eventually gave up and did a hard reset. Now I can't get it to go past the Verizon logo.
I guess the next step is to re-load the software via Odin, but wanted to double check before I broke something because I am on OE1 rooted via Munoz's thread.
Best I can tell I need to load the NCG complete and then use flashfire to upgrade to OG5. Correct?
Thanks for the help.
jonnio said:
Last night my battery got down to 5% or so and out of the blue my phone restarted and ended up in basically a boot loop (It would let me use it for about 1 minute before rebooting). I tried everything I could think of and eventually gave up and did a hard reset. Now I can't get it to go past the Verizon logo.
I guess the next step is to re-load the software via Odin, but wanted to double check before I broke something because I am on OE1 rooted via Munoz's thread.
Best I can tell I need to load the NCG complete and then use flashfire to upgrade to OG5. Correct?
Thanks for the help.
Click to expand...
Click to collapse
u can downgrade 4.4.4 NK2 stock firmware then install NCG kernel for root by towelroot offline version by geo hotz after root reflash NK2 kernel
or u can flash stock 5.0 OG5 directly if u want
make sure repartition is uncheck in odin
I went ahead and flashed the older Firmware, re-ran towel root and upgraded. Seems to have fixed the phone, thankfully.

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.

Back to Stock with Oreo possible?

Hello my friends.
I bought my U Ultra in December 2017.
Now I decided to flash LeeDroid Oreo on my phone.
It works great.
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Now my question.
Is it possible to go for going to stock when I recover it all?
Can I lock the bootloader after that?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
My System Version was 2.21.401.1 and my region is Europe/Germany.
Regards
inFiniTyz_Z said:
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Is it possible to go for going to stock when I recover it all?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
Click to expand...
Click to collapse
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
inFiniTyz_Z said:
Can I lock the bootloader after that?
Click to expand...
Click to collapse
Kind of. You can make OEM lock but it won't be the factory lock. It will be relock. And if you have a custom ROM at that point the phone may not let you boot up.
QDT said:
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
Click to expand...
Click to collapse
In case when I flash the stock recovery too?
inFiniTyz_Z said:
In case when I flash the stock recovery too?
Click to expand...
Click to collapse
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).
QDT said:
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).
Click to expand...
Click to collapse
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?
inFiniTyz_Z said:
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?
Click to expand...
Click to collapse
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.
QDT said:
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.
Click to expand...
Click to collapse
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.
inFiniTyz_Z said:
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.
Click to expand...
Click to collapse
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.
QDT said:
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.
Click to expand...
Click to collapse
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?
inFiniTyz_Z said:
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?
Click to expand...
Click to collapse
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.
QDT said:
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.
Click to expand...
Click to collapse
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.
QDT said:
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.
Click to expand...
Click to collapse
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?
inFiniTyz_Z said:
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?
Click to expand...
Click to collapse
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".
QDT said:
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".
Click to expand...
Click to collapse
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"
inFiniTyz_Z said:
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"
Click to expand...
Click to collapse
And to my knowledge it will be like that. You have flashed unlocked (from HTC but always) bootloader and this has to be noted. It is not that drastical as KNOX for Samsung, doesn't influence the phone functioning.
inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
When you say you followed the procedure, which exactly do you mean? Can you please help me by giving me a quick summary of the steps?
I would like to know the procedure as well.
Hi! I've installed a custom ROM, now I would like to go back to the stock ROM, I don't have a nandroid backup, what can I do?

Categories

Resources