Hey Guys,
So I was running the google experience rom v3 and I decided to head on over to another rom but forgot to wipe before hand and my phone got a little wonky. I eventually ended up doing a complete Odin factory flash which brought me right back to VRUAMDK, when I went to install the OTA update to VRUAME7 my phone would reboot but would not apply and changes and I would get a notification telling me I cant update. I used an Odin flash to the VRUAME7 stock rom and that worked but for some reason I cant flash any sort of recovery now. Booting into recovery just brings me to download mode. I've tried flashing a recovery with Odin with failures on the write. Did I seriously F&#$ up my Nand? I just want to be able to run a recovery and have my GE S4 back Any help would be majorly appreciated.
cj250mills said:
Hey Guys,
So I was running the google experience rom v3 and I decided to head on over to another rom but forgot to wipe before hand and my phone got a little wonky. I eventually ended up doing a complete Odin factory flash which brought me right back to VRUAMDK, when I went to install the OTA update to VRUAME7 my phone would reboot but would not apply and changes and I would get a notification telling me I cant update. I used an Odin flash to the VRUAME7 stock rom and that worked but for some reason I cant flash any sort of recovery now. Booting into recovery just brings me to download mode. I've tried flashing a recovery with Odin with failures on the write. Did I seriously F&#$ up my Nand? I just want to be able to run a recovery and have my GE S4 back Any help would be majorly appreciated.
Click to expand...
Click to collapse
The VRUAME7 firmware patched the Loki exploit and therefore you can not install a custom recovery. Right now all you can do is root the device also there is no way to go back to the VRUAMDK firmware.
Sent from my SCH-I545 using xda premium
ztkryan said:
The VRUAME7 firmware patched the Loki exploit and therefore you can not install a custom recovery. Right now all you can do is root the device also there is no way to go back to the VRUAMDK firmware.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Wow, am I really that oblivious? apparently.. any reason why this might not work on VRUAMDK either? pretty sure I tried flashing through goomanager on that and ran into the same issue..
Related
Hey guys just got a new Verizon S4 that has the bootloader unlocked. The guy I bought it from had CM 10.1 installed. I was wanting to go to the google edition rom or a TW rom. I flashed the google edition rom and it booted fine the first boot. Second boot, it got hung on the "Samsung Galaxy S4" screen. I have wiped caches, reflashed different roms and now everytime I try to boot the phone, it hangs at the same screen. I have no idea what to do. I know I can odin back to stock but I don't want to lose my root and unlocked bootloader (I am assuming I will?) Help?
Did you full wipe? Not just cache. You have to do a full wipe, system and everything. Basically factory reset.
If that doesn't work, you can flash back to stock and re root it, it's really easy.
Sent from my SCH-I545 using Tapatalk 4
JaeKay said:
Did you full wipe? Not just cache. You have to do a full wipe, system and everything. Basically factory reset.
If that doesn't work, you can flash back to stock and re root it, it's really easy.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I did a factory reset. If I flash back to stock I will lose my unlocked bootloarder correct?
I tried flashing another recovery and now I cant even get into recovery. I get the following in red at the top "secure fail: kernel" Then I get a yellow triangle below that that says "system software not authorized by verizon has been found on your phone, yada yada" Am I screwed? I tried flashing cwm advanced edition
I dont think u'll lock the bootloader as long as u dont take the me7 update... factory reset then reroot right after....
Sent from my SCH-I545 using xda premium
whitlecj said:
I tried flashing another recovery and now I cant even get into recovery. I get the following in red at the top "secure fail: kernel" Then I get a yellow triangle below that that says "system software not authorized by verizon has been found on your phone, yada yada" Am I screwed? I tried flashing cwm advanced edition
Click to expand...
Click to collapse
You can't flash a new recovery from inside the GPE port. Since you got the triangle of doom I'm guessing that's what you did. You need to ODIN back to the MDK stock Tar file. I don't know who has it but the download link is on here. Then you need to reroot using the MDK root method, which requires you to download the MD2 bootloader tar file and the MDK boatloader tar file and the motochopper root exploit tool. After you have root, update the binaries. Then power off and reflash back to the MDK (using the .tar file) Once back in MDK you can download a new custom recovery. TWRP or CWM. Boot into recovery and make a full nandroid backup. This way if crap hits the fans again you can reflash your backup. After your backup is done. Download the GPE zip file (I usually put it in my microsd card) then boot back into recovery and reflash the GPE ROM.
Important things to remember.
1.) Don't install the ME7 tar file in ODIN when reflashing
2.) Don't accept the update that OTA
3.) Don't reflash from inside the GPE ported ROM
4.) Don't forget to update the Root binaries from google play after installation
Ok, I'm at work so don't have a lot of time to get into details. Here it is in a nutshell:
I used Josh's MI5 tar to return to stock so that I can get that MJ5 update (if that's what it's called)
That went through w/o incident. However, in my haste I went to Odin and attempted to use Chainfire's root method to regain root on MJ5.
Needless to say that was a huge mistake. It froze during Odin and I was forced to disconnectand pull the battery.
I'm still able to get into Odin but it will not accept the MI3 or MI5 firmware. It gets an error after a few seconds. If I try to get into stock recovery I get FIRMWARE UPGRADE ENCOUNTERD AN ISSIE. PLEASE SELECT RECOVRRY MODE IN KIES AND TRY AGAIN.
Anyone have any advice other than attempting to return the phone?
I'm so pised at myself for making such a dumb mistake.
SantinoInc said:
Ok, I'm at work so don't have a lot of time to get into details. Here it is in a nutshell:
I used Josh's MI5 tar to return to stock so that I can get that MJ5 update (if that's what it's called)
That went through w/o incident. However, in my haste I went to Odin and attempted to use Chainfire's root method to regain root on MJ5.
Needless to say that was a huge mistake. It froze during Odin and I was forced to disconnectand pull the battery.
I'm still able to get into Odin but it will not accept the MI3 or MI5 firmware. It gets an error after a few seconds. If I try to get into stock recovery I get FIRMWARE UPGRADE ENCOUNTERD AN ISSIE. PLEASE SELECT RECOVRRY MODE IN KIES AND TRY AGAIN.
Anyone have any advice other than attempting to return the phone?
I'm so pised at myself for making such a dumb mistake.
Click to expand...
Click to collapse
Did you try Kies to see if it will let yup update the firmware?
mvansomeren said:
Did you try Kies to see if it will let yup update the firmware?
Click to expand...
Click to collapse
Not familiar with KIES but I guess I will have to try that when I get home.
Man, I'm super pissed
SantinoInc said:
Not familiar with KIES but I guess I will have to try that when I get home.
Man, I'm super pissed
Click to expand...
Click to collapse
Here's the website to download Kies from Samsung. Make sure you get Kies 3: www.samsung.com/kies
Good luck! I know how frustrating it can be. Please let us know how it turns out.
SantinoInc said:
Not familiar with KIES but I guess I will have to try that when I get home.
Man, I'm super pissed
Click to expand...
Click to collapse
I had the same problem and this is how I resolved it.
1) Odin CFautoroot
2) Odin TWRP
3) Boot into recovery and either restore a backup or install ROM of choice.
Don't sweat it bro. Simple fix:
1. Odin Twrp recovery
2. Boot into Recovery right after Odin passes you.
3. Flash a Nand or Rom.
4. Good to Go!
*Also, if you don't have a nand or backup or don't have a Rom downloaded, just download one and put it on you sdcard and then flash it. No need to wipe or factory reset. Rom of choice at this point should be Freeza's Mj4 or any mi5 rom will do!
*Stay away from Kies, waste of time...
Starting to look like the mj4 bootloader changed. Probably to try and prevent the knox safe root method by not allowing downgrading.
Sent from my SM-N900P using Tapatalk
bigmase23 said:
Don't sweat it bro. Simple fix:
1. Odin Twrp recovery
2. Boot into Recovery right after Odin passes you.
3. Flash a Nand or Rom.
4. Good to Go!
*Also, if you don't have a nand or backup or don't have a Rom downloaded, just download one and put it on you sdcard and then flash it. No need to wipe or factory reset. Rom of choice at this point should be Freeza's Mj4 or any mi5 rom will do!
*Stay away from Kies, waste of time...
Click to expand...
Click to collapse
OMG, thanks a million bro! I Odin TWRP and it immediately booted into my stock MJ4. I missed the opportunity to get into Recovery right after Odin TWRP. Now when I try to manually get into recovery it takes me to stock recovery.
I'm so afraid of doing anything at this point and am just happy to have a working phone. What would be the best way to go about restoring my nandroid? I'm assuming I should ODIN Twrp recovery again but this time don't allow it to reboot the rom? I'm so nervous I just need some more confirmation before I do anything!
I love you guys in this community...someone always comes through over here when I'm in utter despair!
Boot into twrp recovery and flash your back up. . Once you flash twrp recovery using Odin you won't have to do it again.
Sent from my SM-N900P using XDA Premium 4 mobile app
bigmase23 said:
Boot into twrp recovery and flash your back up. . Once you flash twrp recovery using Odin you won't have to do it again.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you saying that after TWRP is flashed via Odin you have to immediately go into recovery? Because after I flashed TWRP in recovery the phone automatically rebooted back into the rom. After this I turned off the phone and tried to manually boot into recovery but it took me to stock recovery despite having just Odin TWRP a few moments earlier. Hope that makes sense.
SantinoInc said:
Are you saying that after TWRP is flashed via Odin you have to immediately go into recovery? Because after I flashed TWRP in recovery the phone automatically rebooted back into the rom. After this I turned off the phone and tried to manually boot into recovery but it took me to stock recovery despite having just Odin TWRP a few moments earlier. Hope that makes sense.
Click to expand...
Click to collapse
Once you flash twrp via odin you have to go into twrp recovery before your phone reboots. I usually hold power up, power, and home button right after I hear my pc beep (like when you disconnect the usb). Once in twrp, flash away!
bigmase23 said:
Once you flash twrp via odin you have to go into twrp recovery before your phone reboots. I usually hold power up, power, and home button right after I hear my pc beep (like when you disconnect the usb). Once in twrp, flash away!
Click to expand...
Click to collapse
Thanks bro, that did it! I was w/o a phone the whole day at work and really thought my shiit was permi-bricked!
No problem!
Sent from my SM-N900P using XDA Premium 4 mobile app
When flashing twrp in odin it may help to uncheck auto reboot. Then when it finishes boot it into recovery manually. That way you don't miss the window.
Sent from my SM-N900P using Tapatalk
Can any one please share the stock recovery image for 4.3 MK2 baseband which i can update using Odin (and also the steps to odin the recovery image) ? I think i was trying to install custom recovery (later i came to know its not possible in MK2) and messed up the stock recovery.
I was able to recover the phone from "stuck download mode". But i wanted to make i have the stock recovery so that it will easy to install the OTA if verizon ( i know it will be in months ) releases 4.4.2 for S4.
(Note: I have already checked forums which has odin stock images, but i dont want to do that and lose all the apps and data)
rsadalarasu said:
Can any one please share the stock recovery image for 4.3 MK2 baseband which i can update using Odin (and also the steps to odin the recovery image) ? I think i was trying to install custom recovery (later i came to know its not possible in MK2) and messed up the stock recovery.
I was able to recover the phone from "stuck download mode". But i wanted to make i have the stock recovery so that it will easy to install the OTA if verizon ( i know it will be in months ) releases 4.4.2 for S4.
(Note: I have already checked forums which has odin stock images, but i dont want to do that and lose all the apps and data)
Click to expand...
Click to collapse
There's a no wipe image that doesn't touch any apps or their data.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
http://www.sammobile.com/firmwares
Sent from my SCH-I545 using xda premium 4 app
Phone: Verizon Galaxy S4
Tablet: Samsung Galaxy Tab2 10.1
When I first got my second GS4 (about 6 months ago) I rushed to root it and install a recovery (forgetting that the MK2 build has a locked bootloader) I attempted to flash CWM with ODIN and now if I boot to recovery it goes straight to the ODIN Downloading screen. The phone is still fully functional other than the recovery and it is rooted. Since screwing it up I've been looking for a way to fix this I know that i should have used the LOKI method to flash CWM. Is this something that i could fix by flashing stock firmware? or am I out of luck? Thanks.
Timinator01 said:
When I first got my second GS4 (about 6 months ago) I rushed to root it and install a recovery (forgetting that the MK2 build has a locked bootloader) I attempted to flash CWM with ODIN and now if I boot to recovery it goes straight to the ODIN Downloading screen. The phone is still fully functional other than the recovery and it is rooted. Since screwing it up I've been looking for a way to fix this I know that i should have used the LOKI method to flash CWM. Is this something that i could fix by flashing stock firmware? or am I out of luck? Thanks.
Click to expand...
Click to collapse
If your phone is NOT mdk base...you can not use loki or goo manager or rom manager or twrp. Safestrap only can be used. To clean up the mess mostly requires odin of the clean image of your firmware mk2.
sent by safestrap powered echo v26
Flash the stock recovery IMG in odin
Sent from my SCH-I545 using XDA Free mobile app
I suggest the full wipe method located here. Put in ap slot of odin.
http://forum.xda-developers.com/showthread.php?t=2578209
Thanks Tulsadiver I'll give that method a try ... and Thanks to decaturbob for the warning about LOKI, I must have missed that when I was reading over the thread ... I probably would have screwed up my phone again.
Timinator01 said:
Thanks Tulsadiver I'll give that method a try ... and Thanks to decaturbob for the warning about LOKI, I must have missed that when I was reading over the thread ... I probably would have screwed up my phone again.
Click to expand...
Click to collapse
Believe me are not the first...be patient.
sent by safestrap powered echo v26
i rooted my devce using cwm(n9005-cwm-recovery-6.0.4.7-kk(0125)) and gained super su access.
tried to put new rom on went through the process of backing up which i dont thinhk worked, and wiping the sustem
tried to put on new rom using cwm and got an error on startup
so i tried to go back and start the whole process over again
using odin i tried to flash the phone and FAIL
i am stuck in a loop everytime i start normal or start in cwm i get a message saying firmware upgrade encountered an issue. please select recovery mode in kies and try again
but i can still use ODIN
What can i do
Thanks
I'd use TWRP if I were you and save yourself some headaches. From my understanding, CWM is hit or miss on our beloved Note 3.
https://dl.twrp.me/hltespr/twrp-2.8.6.1-hltespr-4.4.img.tar.html
Sent from my SM-N900P using XDA Free mobile app
Shotty2015 said:
i rooted my devce using cwm(n9005-cwm-recovery-6.0.4.7-kk(0125)) and gained super su access.
tried to put new rom on went through the process of backing up which i dont thinhk worked, and wiping the sustem
tried to put on new rom using cwm and got an error on startup
so i tried to go back and start the whole process over again
using odin i tried to flash the phone and FAIL
i am stuck in a loop everytime i start normal or start in cwm i get a message saying firmware upgrade encountered an issue. please select recovery mode in kies and try again
but i can still use ODIN
What can i do
Thanks
Click to expand...
Click to collapse
First what version of KK where you on when you rooted your device ? Anyway pull battery then reinstall battery. Boot into download mode, then odin flash the version of KK you had before you rooted your phone.
Chances are the device won't boot. DON'T PANIC !!! Happenes all the time, just pull the battery again. Boot into download mode again, and odin flash the stock KK again it should boot the second time.
Once you get it to boot up, check and see what version of KK you are running and make the kernel , modem, and bootloader are the same.
At this point l would odin flash it again to make sure you have a clean install. Now you can root and install a custom recovery. I use TWRP.
IF you have any questions just click rom flashing basics in my signature.
Pull battery boot cold to download mode. From there attempt odin flash of factory tar image. Report back please.
Sent from my 0x1 Note 3...... I love tep
i was originally using the stock 5.0 lollipop i rooted using the method on galaxynote3root. tried re flashing but got a fail again i dont know if im using the right kernel
odin OC5 tar.
odin cfautoroot.
odin twrp.
done. easy peasy.
WOOOP WOOOOOOOP.
It worked. it took 10 tries, but it finally worked
now to root is this the right cfautoroot
CF-Root: 48 514 333
CF-Auto-Root: 29 510 246
This file: 106 225
i just dont want to mess it up again
thanks so much guys
every things good rooted and twrp installed.
Thanks again guys