Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.5
for your Verizon Samsung Galaxy S 4
Read this whole post before doing anything
I use nandroid manager to edit/alter my nandroids made by this recovery, you can find the app here : https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore&hl=en Enjoy
CWM Flashable - OUDHS CWM-based Recovery 1.0.3.5 (need to already have a recovery for this)
Loki flashable - OUDHS CWM-based Recovery 1.0.3.5
Loki Flashing Utility
Drivers
Directions:
1) Download the above files
2) using a root file manager remove /system/etc/install-recovery.sh
3) extract the zip
4) use the following adb shell/terminal commands:
Code:
adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
-------------------------------------------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now.
-------------------------------------------------------------------------------------------------------------------------------------------------
Keep in mind as of 1.0.3.4 it auto loki's kernels for ya, so its even easier to customize your device read more here - http://forum.xda-developers.com/showthread.php?p=41803523#post41803523
Source for jfltevzw
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) for being the best we can for those whom need us
garwynn for helping with setting up jflte-common stuff
howtomen & RehpotsirhC for helping test 1.0.3.4's autoloki on teh jflteatt
bhp090808 & an21281 & MR H3LLMAN for helping test
So this will work on my s4 verizion correct?
Sent from my SCH-I545 using xda premium
shabbypenguin said:
Hey guys, now obviously you cant flash this yet, but i didnt want yall to know you werent going to be left out . if you decide to be lazy and flash twrp via goo manager i made a flashable zip so you can just flash it and go
Click to expand...
Click to collapse
after the install completed i still can't get to cwm recovery. i completed odin, the recovery installed after odin, now im still getting the stock recovery screen
iTechWNC said:
So this will work on my s4 verizion correct?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
once teh bootloader is unlocked
p-slim said:
after the install completed i still can't get to cwm recovery. i completed odin, the recovery installed after odin, now im still getting the stock recovery screen
Click to expand...
Click to collapse
im terribly confused, you installed this recovery? on your verizon sgs4? did you read steps 10 and on?
shabbypenguin said:
once teh bootloader is unlocked
im terribly confused, you installed this recovery? on your verizon sgs4? did you read steps 10 and on?
Click to expand...
Click to collapse
i did but i read it backwards. i thought i had to let it install. damn im so angry with myself
shabbypenguin said:
once teh bootloader is unlocked
im terribly confused, you installed this recovery? on your verizon sgs4? did you read steps 10 and on?
Click to expand...
Click to collapse
Thanks im a noob once again I have been out of the android seen for two years
Sent from my SCH-I545 using xda premium
already have OUDHS installed.
p-slim said:
after the install completed i still can't get to cwm recovery. i completed odin, the recovery installed after odin, now im still getting the stock recovery screen
Click to expand...
Click to collapse
Without an unlocked bootloader? I am confused....
---------- Post added at 10:56 AM ---------- Previous post was at 10:28 AM ----------
slackwaresupport said:
already have OUDHS installed.
Click to expand...
Click to collapse
Without an unlocked bootloader? Or do you know something we don't?
mikebuck69 said:
Without an unlocked bootloader? I am confused....
Click to expand...
Click to collapse
So was I, smh
Sent from my SCH-I545 using Tapatalk 4 Beta
was a tester for Dan.
updated op, enjoy guys
nice.. loki was way more easier.
install-recovery.sh doesn't seem to be present in /system/etc for me. Any other locations it might be in?
mikebuck69 said:
install-recovery.sh doesn't seem to be present in /system/etc for me. Any other locations it might be in?
Click to expand...
Click to collapse
if its not there, then you are good
updated op with a bigger text recovery, and zipped up the files to prevent corruptions when downloading
have recovery already? just use teh cwm flashable in recovery and youll be set
Edit: Nevermind, it didn't work the first time but I tried it again and it booted into recovery. Thanks for the hack!
I followed the instructions and it said it successfully flashed the recovery, but when I tried to boot into it, it said it was booting recovery but didn't actually go anywhere. The screen blacked out for a second then rebooted normally. Any ideas? I'm not running the stock kernel, but the one used in one of the other root methods. Do I need to have stock kernel for this to work?
getting Loki aboot version does not match device (plus my adb keeps timing out for some reason and flipping back to usb mode)...
justreboot said:
getting Loki aboot version does not match device (plus my adb keeps timing out for some reason and flipping back to usb mode)...
Click to expand...
Click to collapse
I got the same error
I am rooted with the MK kernel, if that matters
Good news I guess.. even though in no way this is an unlocked bootloader but it will do the trick for now, any chance b of making twrp cuz cwm sucks lol
Sent from my SCH-I545 using Tapatalk 2
justreboot said:
getting Loki aboot version does not match device (plus my adb keeps timing out for some reason and flipping back to usb mode)...
Click to expand...
Click to collapse
mikebuck69 said:
I got the same error
I am rooted with the MK kernel, if that matters
Click to expand...
Click to collapse
should be fixed now, sorry
beanstown106 said:
Good news I guess.. even though in no way this is an unlocked bootloader but it will do the trick for now, any chance b of making twrp cuz cwm sucks lol
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
no intentions to port twrp, others will do that id rather port my teams recovery.
if you only guess that this is good news then you shouldnt really be using it
Related
is there any way to flash a zip with a locked bootloader? its not a rom zip but a zip whic contaings some mods like beats audio and stuff like that. it just takes tooo long to copy and set permissions manually. i was thinking rom manager but im not sure if you have to be unlocked or if it will even work. maybe theres another app or something. or maybe some one knows a way to do it using adb. i am rooted by the way.
You must be unlocked, rooted, and have a custom recovery (TWRP, CWM) installed to flash any zip of any nature. I use TWRP, it was easy enough to install, has a nice UI, and has less ware on the volume buttons. Happy rooting
AnnonymousFalcon said:
You must be unlocked, rooted, and have a custom recovery (TWRP, CWM) installed to flash any zip of any nature. I use TWRP, it was easy enough to install, has a nice UI, and has less ware on the volume buttons. Happy rooting
Click to expand...
Click to collapse
Untrue, you don't need to be rooted.
Unlocking is mandatory, the only way to install a custom recovery. Once unlocked you flash the recovery with fastboot, then you can flash ROMs.
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
fcortes626 said:
is there any way to flash a zip with a locked bootloader? its not a rom zip but a zip whic contaings some mods like beats audio and stuff like that. it just takes tooo long to copy and set permissions manually. i was thinking rom manager but im not sure if you have to be unlocked or if it will even work. maybe theres another app or something. or maybe some one knows a way to do it using adb. i am rooted by the way.
Click to expand...
Click to collapse
Whatever the content of the zip you need a recovery. ROM Manager don't do that at all. ADB sure, unzip the file on your computer, then 'adb remount' first to mount r/w sytem, and 'adb push <your file path> <destination path>'.
Striatum_bdr said:
Untrue, you don't need to be rooted.
Unlocking is mandatory, the only way to install a custom recovery. Once unlocked you flash the recovery with fastboot, then you can flash roms'.
Click to expand...
Click to collapse
Sorry, thats correct, I've just always rooted first.. I apologize :/
well i found an app that installs cwm on the system partition but it only works for the xperia and i emailed the developer and he said the belives he can make it work but wouldnt know where to start
fcortes626 said:
well i found an app that installs cwm on the system partition but it only works for the xperia and i emailed the developer and he said the belives he can make it work but wouldnt know where to start
Click to expand...
Click to collapse
???
Mind linking that?
I've never heard of a recovery installed on /system. The only way i know to install CWM without unlocking is by a bootstrap hijack (Moto devices).
My suggestion is to just unlock your tablet, perform the unbrickable mod, and flash at will.
Sent from my DROID RAZR using Tapatalk 2
joshw0000 said:
???
Mind linking that?
I've never heard of a recovery installed on /system. The only way i know to install CWM without unlocking is by a bootstrap hijack (Moto devices).
My suggestion is to just unlock your tablet, perform the unbrickable mod, and flash at will.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
here is the app https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
if i was to unlock i would probably need to send it to asus first because i am having the wifi drop issue. but i have read that some people cant unlock their prime after getting it back from asus
fcortes626 said:
here is the app https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
if i was to unlock i would probably need to send it to asus first because i am having the wifi drop issue. but i have read that some people cant unlock their prime after getting it back from asus
Click to expand...
Click to collapse
That's pretty badass. Never had a Sony phone so I'd never heard of this.
Sent from my DROID RAZR using Tapatalk 2
joshw0000 said:
That's pretty badass. Never had a Sony phone so I'd never heard of this.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
yea and if it worked for our device it would be really big. i think you can install cwm on external sdcard too but dont know how that works either.
Warning: Total Noob here.
Just rooted my VZW S4 following the instructions for the ME7 build on the forums here with no problems. Installed "ROM Manager" via Play store and went thru the steps of flashing CWM. The app reports, under "Recovery Setup" that my current recovery is ClockworkMod 6.0.3.2.
BUT, when I "Reboot into Recovery" ... it always go to the default "Android System Recovery <3e>"
How can I get CWM running instead?
Thanks
You can't install a custom recovery on ME7 yet. It's been well covered here on XDA.
Sent from my SCH-I545 using xda app-developers app
AliceBToklas said:
You can't install a custom recovery on ME7 yet. It's been well covered here on XDA.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks. As someone new to Android and the rooting community, is there an explanation on the whys and hows of CWM (e.g. what is required for it to work, why it requires more than rooted phone, how it should best be used, etc...)?
Just trying to figure out how everything plays together and what I should and shouldn't do.
-wg
wgpubs said:
Thanks. As someone new to Android and the rooting community, is there an explanation on the whys and hows of CWM (e.g. what is required for it to work, why it requires more than rooted phone, how it should best be used, etc...)?
Just trying to figure out how everything plays together and what I should and shouldn't do.
-wg
Click to expand...
Click to collapse
The bootloader on this phone is locked, meaning you will need an exploit to bypass it in order to install a custom recovery. The loki method that was previously working has been patched by the most recent update, eliminating the only publicly known hole to install custom recovery. Without an exploit to bypass or an unlocking method we have no way to install a custom recovery like CWM or TWRP, without these it makes it nigh on impossible to install a custom ROM.
Anyone else please correct me if I am wrong but this was my understanding of the current state of things.
Your 100% correct sir...
Sent from my SCH-I545 using xda premium
I tried to run the root but when putting the commands in the emulator I get file not found. SD card is exfat
Hope someone makes a bootstrap like we had for the old droids.
goherd said:
I tried to run the root but when putting the commands in the emulator I get file not found. SD card is exfat
Click to expand...
Click to collapse
Make sure you are very specific on letters that need to be caps.
For example; when you type cd /mnt/extSdCard......make sure the S and C are caps or it will not work.
First time I did it I put in extSdcard and not extSdCard and I got the file not found error.
That should do the trick.
MikeyFid said:
Make sure you are very specific on letters that need to be caps.
For example; when you type cd /mnt/extSdCard......make sure the S and C are caps or it will not work.
First time I did it I put in extSdcard and not extSdCard and I got the file not found error.
That should do the trick.
Click to expand...
Click to collapse
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
ballsagna said:
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
Click to expand...
Click to collapse
Um, Linux command line is often case sensitive. The question above wasn't about custom recoveries, it was simply referring to rooting ME7 which has long been possible.
Sent from my SCH-I545 using Tapatalk 2
ballsagna said:
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
Click to expand...
Click to collapse
That command line is in fact case sensitive. So you're wrong. The previous post was about using the root exploit method which has been done already, not unlocking the bootloader.
So I rooted my phone with a locked bootloader using this method http://forum.xda-developers.com/showthread.php?t=2173465 and went ahead and installed CWM recovery, and then tried to flash this rom http://forum.xda-developers.com/showthread.php?t=2428306
After my phone rebooted, I keep on getting this LG Security Error and cannot boot into the phone. I've tried to use the fastboot method to try and flash a new kdz, however I keep on getting stuck at the waiting for device part.. would appreciate it if anyone could help me to just restore my phone to factory settings?
cosmictrips said:
So I rooted my phone with a locked bootloader using this method http://forum.xda-developers.com/showthread.php?t=2173465 and went ahead and installed CWM recovery, and then tried to flash this rom http://forum.xda-developers.com/showthread.php?t=2428306
After my phone rebooted, I keep on getting this LG Security Error and cannot boot into the phone. I've tried to use the fastboot method to try and flash a new kdz, however I keep on getting stuck at the waiting for device part.. would appreciate it if anyone could help me to just restore my phone to factory settings?
Click to expand...
Click to collapse
Sounds like you made a serious error and didn't do any research before proceeding. Did you install the LG drivers prior to doing anything with the phone? If not, you have just bricked your device. L9RecoveryInstaller.apk is the ONLY way at the moment to successfully install CWM on the P769 if the bootloader is locked. I don't have all the answers myself as I'm fairly new to this device, P769, myself. There may be someone here with a little more insight as to how to fix your issue, but if you didn't install LGs drivers beforehand, I'd say your device is bricked. Sorry.
You'll need to use fastboot to flash ICS u and x. Then go into upgrade mode by holding volume up and plugging the phone to the computer. Upgrade mode should pop up and you're ready to flash any kdz using the offline flash method.
Sent from my LG-P769 using XDA Premium 4 mobile app
Or simply unbrick using the lgupdate tool. Why not go the easy way?
Sent from my LG-P760 using xda app-developers app
cosmictrips said:
So I rooted my phone with a locked bootloader using this method http://forum.xda-developers.com/showthread.php?t=2173465 and went ahead and installed CWM recovery, and then tried to flash this rom http://forum.xda-developers.com/showthread.php?t=2428306
After my phone rebooted, I keep on getting this LG Security Error and cannot boot into the phone. I've tried to use the fastboot method to try and flash a new kdz, however I keep on getting stuck at the waiting for device part.. would appreciate it if anyone could help me to just restore my phone to factory settings?
Click to expand...
Click to collapse
security error should appear when some system mod was been wrong (sorry bad english)
you should re-flash the firmware with kdz(this time flash a firmware with cwm and root included)
AXD96 said:
security error should appear when some system mod was been wrong (sorry bad english)
you should re-flash the firmware with kdz(this time flash a firmware with cwm and root included)
Click to expand...
Click to collapse
L9 P769 is a much different creature than the other P76X variants. CWM CANNOT be installed on the recovery partition unless the bootloader is unlocked. There are very few people here who have managed to unlock the bootloader on this device ( P769 ). Any attempt to modify the bootloader, boot partition, or recovery ends in "LG Security Error". As per my previous post, the only way to get CWM on this device with a locked bootloader is with the L9RecoveryInstaller.apk.
shinobisoft said:
L9 P769 is a much different creature than the other P76X variants.
Click to expand...
Click to collapse
Creature is right! What a nightmare this thing is!
Sent from my LG-P769 using XDA Premium 4 mobile app
N00BY0815 said:
Or simply unbrick using the lgupdate tool. Why not go the easy way?
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
This will not work until u use fastboot to flash ICS xand u. It will not reconize the phone until this is done.
Sent from my LGMS769 using XDA Premium 4 mobile app
Where is L9RecoveryInstaller.apk?
seshsud said:
Where is L9RecoveryInstaller.apk?
Click to expand...
Click to collapse
This post
shinobisoft said:
This post
Click to expand...
Click to collapse
Thanks although CWM installed fine with this apk, however on boot up (with vol - pressed) it doesnt go into recovery mode
seshsud said:
Thanks although CWM installed fine with this apk, however on boot up (with vol - pressed) it doesnt go into recovery mode
Click to expand...
Click to collapse
Do you have busybox installed and or do you have multiple copies of busybox installed?
If you don't have busybox, install it from the Play Store. Make sure it installs to /system/xbin.
If you have multiple copies, which I did when I had this error, use the busybox installer to uninstall all copies of busybox and then use the installer to reinstall busybox to /system/xbin.
You may need to run L9RecoveryInstaller again. It will say there is a recovery installed just reinstall anyway.
Reboot and try again.
shinobisoft said:
Do you have busybox installed and or do you have multiple copies of busybox installed?
If you don't have busybox, install it from the Play Store. Make sure it installs to /system/xbin.
If you have multiple copies, which I did when I had this error, use the busybox installer to uninstall all copies of busybox and then use the installer to reinstall busybox to /system/xbin.
You may need to run L9RecoveryInstaller again. It will say there is a recovery installed just reinstall anyway.
Reboot and try again.
Click to expand...
Click to collapse
Yes that worked!! Thanks! Looks like we can't get CM11 onto this phone yet...currently on 20h...can the bootloader be unlocked at all...?How to get rid of all tmobile bloatware?
seshsud said:
Yes that worked!! Thanks! Looks like we can't get CM11 onto this phone yet...currently on 20h...can the bootloader be unlocked at all...?How to get rid of all tmobile bloatware?
Click to expand...
Click to collapse
Cm11 is available, yes some people can unlock the bootloader. Theres a few threads about removing tmobile bloatware, along with solutions to the other questions I answered. Simply search your question and you'll find a solution. THEN if you can't find the solution by searching make a thread to ask about it. Goodluck if you try unlocking the bootloader, its quite a journey!! If you can't unlock it or the process scares you out of trying search Kuma ROM. Goodluck!
Sent from my LGMS769 using XDA Premium 4 mobile app
lwg45714 said:
This will not work until u use fastboot to flash ICS xand u. It will not reconize the phone until this is done.
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, I'm in a similar boat as the OP, successfully rooted the device but didn't realise I needed an unlocked bootloader to flash a recovery. Now I get Security Error.
Now, I keep seeing "ICS x and u" on this forum, and have no idea what it is. Yet people keep saying it like it's obvious.
Is this it? http://forum.xda-developers.com/showpost.php?p=44144663
If so, obviously I can't follow the steps because my phone won't boot up past the splash screen. And said phone isn't recognized by ADB at the moment, because I can only figure out how to boot it into S/W update mode.
Currently I can't even use the L9RecoveryInstaller.apk, because, again, can't boot up. Help?
Alucai Vivorvel said:
Hi, I'm in a similar boat as the OP, successfully rooted the device but didn't realise I needed an unlocked bootloader to flash a recovery. Now I get Security Error.
Now, I keep seeing "ICS x and u" on this forum, and have no idea what it is. Yet people keep saying it like it's obvious.
Is this it? http://forum.xda-developers.com/showpost.php?p=44144663
If so, obviously I can't follow the steps because my phone won't boot up past the splash screen. And said phone isn't recognized by ADB at the moment, because I can only figure out how to boot it into S/W update mode.
Currently I can't even use the L9RecoveryInstaller.apk, because, again, can't boot up. Help?
Click to expand...
Click to collapse
You'll need to use fastboot to flash the x and u images. They are included with the tools. Search the General section.
Sent from my LG-P769 using Tapatalk
N00BY0815 said:
Or simply unbrick using the lgupdate tool. Why not go the easy way?
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
C this doesn't work. It gets stuck at 4 percent during the sw upgrade process.:crying:
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
jay876 said:
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
Click to expand...
Click to collapse
How the hell did you downgrade? As far as this community is concerned, there is no way to downgrade.
Sent from my SCH-I545 using xda app-developers app
jay876 said:
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
Click to expand...
Click to collapse
MANY others have tried, and have checked the code that checks the qfuses... So you are either mistaken, lying, or your phone is some amazing anomaly...
Nothing other then odin and a stock image? have a link to where you downloaded the image from?
Screen shot of about phone screen?
scryan said:
MANY others have tried, and have checked the code that checks the qfuses... So you are either mistaken, lying, or your phone is some amazing anomaly...
Nothing other then odin and a stock image? have a link to where you downloaded the image from?
Screen shot of about phone screen?
Click to expand...
Click to collapse
I'm not lying. It was ODIN/download mode with the green android logo with some red text saying the phone was unable to boot. I tried to flash the mdk tar in that state and it failed so I rebooted into download mode holding down the 3 buttons and it was flashed successfully.
I used this stock image - http://downloadandroidfiles.org/download-sch-i545_mdk_562219_stock_restore-zip/
requested screenshot -http://imgur.com/1IJEBB6
jay876 said:
I'm not lying. It was ODIN/download mode with the green android logo with some red text saying the phone was unable to boot. I tried to flash the mdk tar in that state and it failed so I rebooted into download mode holding down the 3 buttons and it was flashed successfully.
I used this stock image - http://downloadandroidfiles.org/download-sch-i545_mdk_562219_stock_restore-zip/
requested screenshot -http://imgur.com/1IJEBB6
Click to expand...
Click to collapse
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Would be my second guess. I have seen people think their phone was downgraded after flashing an MDK radio.
Could this be the opposite, where the phone already had custom recovery I could see it having a stock Mi1 rom and showing Mi1 in the about phone while its still MDK base.
I'd love for this to be true, and don't mean to offend the OP... but this has been tried a ton of times and does not work, and its just so much more likely there is some confusion here rather then his phone simply not checking qfuses... Well, hopefully someone smarter than me will pick this apart tonight.
scryan said:
Would be my second guess. I have seen people think their phone was downgraded after flashing an MDK radio.
Could this be the opposite, where the phone already had custom recovery I could see it having a stock Mi1 rom and showing Mi1 in the about phone while its still MDK base.
I'd love for this to be true, and don't mean to offend the OP... but this has been tried a ton of times and does not work, and its just so much more likely there is some confusion here rather then his phone simply not checking qfuses... Well, hopefully someone smarter than me will pick this apart tonight.
Click to expand...
Click to collapse
Yeah but the scary thing is I don't recall ever seeing a MI1 stock build for mdk users.
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea it was slightly used. When I checked it out it had the mi1 firmware and I think someone tried to root it because it had terminal emulator and superuser installed. I ran root checker and it did not have root access so it was a failed attempt.
I factory reset everything at that point though then that's where my story began. Rooted, rom manager > goo manager > soft brick (odin/download mode) > flashed mdk stock > root > loki bypass bootloader for cwm > aosp rom issues with receiving and ending calls > stock with custom recovery
When I downloaded rom manager, I didn't know at the time that mi1 firmware was unable to get a custom recovery installed.
Could he have purchased used developers s4?
jamesd1085 said:
Could he have purchased used developers s4?
Click to expand...
Click to collapse
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
k1mu said:
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
Click to expand...
Click to collapse
It was previously a vrudmi1 bootloader. I don't think that's a dev unit. If it was a dev unit wouldn't I have been able to install the custom recovery successfully before right after rooting? Blah I guess it was a stroke of luck somewhere.
k1mu said:
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
Click to expand...
Click to collapse
Yeah...but seems like once surge gets the rest of the missing parts for his dev mdk tar he should be able to flash it back to dev
jay876 said:
It was previously a vrudmi1 bootloader. I don't think that's a dev unit. If it was a dev unit wouldn't I have been able to install the custom recovery successfully before right after rooting? Blah I guess it was a stroke of luck somewhere.
Click to expand...
Click to collapse
No, it was previously a MI1 build That's not the same as a MI1 bootloader.
You can have a MDK phone running a MK2 ROM. The build will show MK2 even though it's an older bootloader.
k1mu said:
No, it was previously a MI1 build That's not the same as a MI1 bootloader.
You can have a MDK phone running a MK2 ROM. The build will show MK2 even though it's an older bootloader.
Click to expand...
Click to collapse
Oh ok. Thanks. I didn't know that could be the case.
jay876 said:
Oh ok. Thanks. I didn't know that could be the case.
Click to expand...
Click to collapse
Well lets just make sure. Open terminal and type the following:
Code:
su
mount -o remount, rw /system
echo ON >/efs/carrier/HiddenMenu
Then dial *#1234# and post back with a screenshot of that screen
Surge1223 said:
Well lets just make sure. Open terminal and type the following:
Code:
su
mount -o remount, rw /system
echo ON >/efs/carrier/HiddenMenu
Then dial *#1234# and post back with a screenshot of that screen
Click to expand...
Click to collapse
http://imgur.com/uPmLbok
jay876 said:
http://imgur.com/uPmLbok
Click to expand...
Click to collapse
Hmm...looks like good ole run of the mill MDK...keep it...hard to get anymore
jay876 said:
http://imgur.com/uPmLbok
Click to expand...
Click to collapse
Okay, that was unexpected. Tell me how do you know for sure you were on VRUDMI1? Do you have a back up from then?
Open terminal post the output of the following commands:
Code:
su
cat /proc/version
cd /dev/block/platform/msm_sdcc.1/by-name
hexdump -C aboot|grep SW_ID
And since this has already caught surge's attention... He may be able to verify that flashing MDK modem +hlos bin may fix your aosp issues...
Surge1223 said:
Okay, that was unexpected. Tell me how do you know for sure you were on VRUDMI1? Do you have a back up from then?
Open terminal post the output of the following commands:
Code:
su
cat /proc/version
cd /dev/block/platform/msm_sdcc.1/by-name
hexdump -C aboot|grep SW_ID
Click to expand...
Click to collapse
Can't really figure out whats going on here..
First of all if you tried to flash MDK via odin on a MI1 BL you should have gotten an error "SW REV. CHECK FAIL: FUSED: 4, Binary: 1"
Guys I am in dire need of some help. I have a VZW GS4 i545 and I flashed the new 'merged' version of PHilz touch for the GS4 only to find out it is non-Loki'd so now I am getting the error message "Software not authorized by Verizon".
I know I need to use Odin to get back but I don't know how to use it to replace the boot loader.
Can someone please tell me or point me to a step-by-step?
I've Googled this many different ways but I can't seem to find what I need.
Please help.
ktraub said:
Guys I am in dire need of some help. I have a VZW GS4 i545 and I flashed the new 'merged' version of PHilz touch for the GS4 only to find out it is non-Loki'd so now I am getting the error message "Software not authorized by Verizon".
I know I need to use Odin to get back but I don't know how to use it to replace the boot loader.
Can someone please tell me or point me to a step-by-step?
I've Googled this many different ways but I can't seem to find what I need.
Please help.
Click to expand...
Click to collapse
Just flash the no wipe mdk tar...you don't just flash bootloaders... It will replace recovery image which is what you need...you will have to re-flash a loki'd image after
jamesd1085 said:
Just flash the no wipe mdk tar...you don't just flash bootloaders... It will replace recovery image which is what you need...you will have to re-flash a loki'd image after
Click to expand...
Click to collapse
Jamesd1085, thanks for the reply.
But, how do I flash with the " Software not authorized by Verizon" message up?
I don't know how to get the phone back into download mode with that message up.
Your help is greatly appreciated.
ktraub said:
Jamesd1085, thanks for the reply.
But, how do I flash with the " Software not authorized by Verizon" message up?
I don't know how to get the phone back into download mode with that message up.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Pull the battery then try to get into download mode again. Here's a thread with a guide. Make sure you get the mdk file and not another one as you'd end locking your phone up.
http://forum.xda-developers.com/showthread.php?t=2301259
Sent From My Verizon S4
ktraub said:
Jamesd1085, thanks for the reply.
But, how do I flash with the " Software not authorized by Verizon" message up?
I don't know how to get the phone back into download mode with that message up.
Your help is greatly appreciated.
Click to expand...
Click to collapse
To turn it off pull battery... After that you can boot into download mode by holding volume down and power button...after that you can flash via odin
Mistertac said:
Pull the battery then try to get into download mode again. Here's a thread with a guide. Make sure you get the mdk file and not another one as you'd end locking your phone up.
http://forum.xda-developers.com/showthread.php?t=2301259
Sent From My Verizon S4
Click to expand...
Click to collapse
Mistertac, thanks for the response. I pulled the battery and the phone booted into my custom ROM HyperDrive RLS 14, and I still have root.
I think I may have just hosed my recovery. While I'm waiting for the no wipe mdk to download (another 2 hours), is there nay way to just flash the recovery?
Your help is greatly appreciated.
ktraub said:
Mistertac, thanks for the response. I pulled the battery and the phone booted into my custom ROM HyperDrive RLS 14, and I still have root.
I think I may have just hosed my recovery. While I'm waiting for the no wipe mdk to download (another 2 hours), is there nay way to just flash the recovery?
Your help is greatly appreciated.
Click to expand...
Click to collapse
Well you can easily re install your recovery of choice still. Either with goo or rom manager.
Sent From My Verizon S4
Mistertac said:
Well you can easily re install your recovery of choice still. Either with goo or rom manager.
Sent From My Verizon S4
Click to expand...
Click to collapse
Mistertac, thank you very much!
I installed Goo manager and then used it to install TWRP.
The I rebooted to recovery and flashed the correct (loki'd) version of Philztouch.
Thank you again. I really appreciate it.
-Kev
ktraub said:
Mistertac, thank you very much!
I installed Goo manager and then used it to install TWRP.
The I rebooted to recovery and flashed the correct (loki'd) version of Philztouch.
Thank you again. I really appreciate it.
-Kev
Click to expand...
Click to collapse
Glad we could help. And even better that you flashed the Loki'd version of Philz or you'd be using Odin after all lol
Sent From My Verizon S4
Mistertac are you familiar with philz touch?...jw because last week I installed it and loved the ui and extra features but it wouldn't allow me to flash anything...I ended up having to use ROM toolbox to flash cwm touch 6.0.4.4...any Ideas...everybody seems to swear by Philz touch and I would rather use it...I tried toggling Loki support on and off it wouldn't flash regardless of settings
jamesd1085 said:
Mistertac are you familiar with philz touch?...jw because last week I installed it and loved the ui and extra features but it wouldn't allow me to flash anything...I ended up having to use ROM toolbox to flash cwm touch 6.0.4.4...any Ideas...everybody seems to swear by Philz touch and I would rather use it...I tried toggling Loki support on and off it wouldn't flash regardless of settings
Click to expand...
Click to collapse
Yes I use Philz. Are you flashing our device specific Philz zip or the unified jflte zip? Because some were having problems with the unified one
Sent From My Verizon S4
Mistertac said:
Yes I use Philz. Are you flashing our device specific Philz zip or the unified jflte zip? Because some were having problems with the unified one
Sent From My Verizon S4
Click to expand...
Click to collapse
Dunno...lol...I downloaded it from the philz touch op for jfltevzw...but I will have to look again...it was most recent version but I didn't see anything about a unified version...thanks for the heads up
jamesd1085 said:
Dunno...lol...I downloaded it from the philz touch op for jfltevzw...but I will have to look again...it was most recent version but I didn't see anything about a unified version...thanks for the heads up
Click to expand...
Click to collapse
Yea I'd grab the latest one from here..
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw
Sent From My Verizon S4
Mistertac said:
Yea I'd grab the latest one from here..
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw
Sent From My Verizon S4
Click to expand...
Click to collapse
Yeah I had the previous build from here...maybe just a fluke...Lil...I will try the new version...thanks