Related
I just recently rooted my Verizon Galaxy S4 and swiftly installed Rom Manager. I have used ROM manager in the past before I owned an iPhone when the Moto Droids were popular. Upon installing I flashed the recovery over to CWM - However, when I reboot into recovery I still receive the default stock options. I even purchased the CWM Touch recovery to see if that would work, sadly it did not.
I am stuck as to what to do here, I have googled the problem and cannot seem to find a cure. I can not do anything with CWM - When I click backup current ROM it simply reboots into the stock recovery.
If anyone can help me with this issue I would be extremely appreciated
Thanks,
Christopher
Reneg4d3 said:
I just recently rooted my Verizon Galaxy S4 and swiftly installed Rom Manager. I have used ROM manager in the past before I owned an iPhone when the Moto Droids were popular. Upon installing I flashed the recovery over to CWM - However, when I reboot into recovery I still receive the default stock options. I even purchased the CWM Touch recovery to see if that would work, sadly it did not.
I am stuck as to what to do here, I have googled the problem and cannot seem to find a cure. I can not do anything with CWM - When I click backup current ROM it simply reboots into the stock recovery.
If anyone can help me with this issue I would be extremely appreciated
Thanks,
Christopher
Click to expand...
Click to collapse
Did you remember to go to Rom Manager > Recovery Setup > Click ClockworkMod Recovery (Under INSTALL OR UPDATE RECOVERY) > Then click on the Samsung Galaxy S4 (Verizon).
Yes, since that is the only way to download and install the recovery that is what I did...
You might want to email the developer or get a mod to move this thread to the Q&A forum.
DarkMenace said:
You might want to email the developer or get a mod to move this thread to the Q&A forum.
Click to expand...
Click to collapse
I will email the developer the link to this thread.
Surely I am not the only one with this problem...
Reneg4d3 said:
I will email the developer the link to this thread.
Surely I am not the only one with this problem...
Click to expand...
Click to collapse
I was able to flash it with no issues.
Do you mind telling me exactly what you did (even rooting wise) - I used some compiled package that was on droid life I believe. It had all the tools compiled and was the closest thing to a one click without being one click. I think it even attempted to flash the recovery. However, that is how I rooted my device. I didn't flash another rom. Still on the stock rom.
I just rooted the device. Switched to SuperSU, restored all my programs via Titanium Backup. Then I flashed CWM.
DarkMenace said:
I just rooted the device. Switched to SuperSU, restored all my programs via Titanium Backup. Then I flashed CWM.
Click to expand...
Click to collapse
I have read conflicting posts about this but is your bootloader unlocked? I read that the bootloader was unlocked before the phone was even released - Then I read somewhere else that the Verizon bootloader was super locked down and not cracked yet. Obviously, you would need some bootstrap or the bootloader unlocked before the device would even be able to use a custom ROM. Did you flash the phone to get root, or did you use all kinds of different tools to do so?
EDIT:
this is the method I used - http://forum.xda-developers.com/showthread.php?p=41718543
Reneg4d3 said:
I have read conflicting posts about this but is your bootloader unlocked? I read that the bootloader was unlocked before the phone was even released - Then I read somewhere else that the Verizon bootloader was super locked down and not cracked yet. Obviously, you would need some bootstrap or the bootloader unlocked before the device would even be able to use a custom ROM. Did you flash the phone to get root, or did you use all kinds of different tools to do so?
EDIT:
this is the method I used - http://forum.xda-developers.com/showthread.php?p=41718543
Click to expand...
Click to collapse
That's the same method I used but I didn't unlock the bootloader. I just did the root them installed the recovery from the Play Store.
Reneg4d3 said:
I have read conflicting posts about this but is your bootloader unlocked? I read that the bootloader was unlocked before the phone was even released - Then I read somewhere else that the Verizon bootloader was super locked down and not cracked yet. Obviously, you would need some bootstrap or the bootloader unlocked before the device would even be able to use a custom ROM. Did you flash the phone to get root, or did you use all kinds of different tools to do so?
EDIT:
this is the method I used - http://forum.xda-developers.com/showthread.php?p=41718543
Click to expand...
Click to collapse
Please read about loki in the development forum. The bootloader is not unlocked and unlock is not needed to flash roms or recoveries.
http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I545 using Tapatalk 4 Beta
I will read about loki - maybe when I read about loki this will be explained, however I was always under the impression that in order to install custom ROMs you have to unlock the bootloader. I know that a bootloader or bootstrap is what tells your device what operating system to boot to and if it is locked this prevents you from loading a custom ROM. If I have this all wrong, would someone care to explain? You can use technical explanations as I will most likely be able to understand what you mean.
EDIT:
reading about loki clears this up. It's simply (yet sophisticatedly) tricks the aboot into thinking the rom passes the checksum that is physically embedded into the phone and proceeds to boot the custom rom. The boot loader itself is still locked, but is bypassed.
The only problem with this is they can release an update to patch the sequence in which the checksum is done so that it cannot be loaded over itself.
My problem still remains - Clockwork Manager is not working.
Does anyone have any suggestions?
Questions and help issues go in Q&A and help section
Thread moved
FNM
Sorry I posted it in the wrong section. If anyone knows what is wrong please let me know, I am thoroughly confused as to why this is happening. Maybe I should restore stock and reroot the device, although I don't know what that would do.
Am I supposed to install Loki? Because I never did that, I was under the impression that rom manager would do that.
Reneg4d3 said:
Sorry I posted it in the wrong section. If anyone knows what is wrong please let me know, I am thoroughly confused as to why this is happening. Maybe I should restore stock and reroot the device, although I don't know what that would do.
Am I supposed to install Loki? Because I never did that, I was under the impression that rom manager would do that.
Click to expand...
Click to collapse
Do a stock restore. Then root again. Start over.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
I cleared the Clockwork Mod data and also uninstalled and reinstalled the app and now it is working Guess it was just a fluke!
Hey XDA, can we talk? cause im about to cry man tears.
First off you are much better at android then I am, this isn't me trying to sound humble, I suck and the threat of bricking my toys scares me.
Today I found a way to get root access without unlocking my bootloader and I was thrilled, it was easy and it worked! I had root access and then decided I was going to try to install CyanogenMod 10 (latest nightly) and so I installed ROM Manager and downloaded CyanogenMod, when I tried to boot to recovery mode (hold down volume and power, then up volume) I would get the dead android with an exclamation point, every time.
So I decided to unlock my bootloader, I went searching and came across the ASUS official bootloader unlocker and it said the unlocker was for ICS and I have already upgraded the ASUS rom to jellybean, I decided to try the unlock device app anyway and now when I restart the words "this device is unlocked" show in the top left corner, I thought that meant the bootloader is unlocked but when I restart into recovery mode I still get the dead android.
I cant find any information anywhere about how to unlock an ASUS jellybean bootloader and I am only guessing that why I keep getting the dead android.
Anyway, if you can help thats awesome, I am usually the kind of guy that can read and find the answers but **** me if I cant find them anywhere, I was never good at the world of bootloaders, whether PC or Android and I am hoping to find a hand and learn something more here
Thanks
I know its my first time here to post but I have read loads of stuff off this site.
78 people read this already, one of you must be able to point my dumbass in the right direction?
bueller, bueller ...:crying:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
ArghMonkey said:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
Click to expand...
Click to collapse
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
flumpster said:
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
Click to expand...
Click to collapse
Sweet, im on it right now
Wow, there are TWRP threads everywhere, several downloads, I even did a search within the transformer prime subthread and cant find one version mentioned for the JB bootloader.
Ill keep looking ...
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
1: Can anyone tell me how I find exactly which bootloader I am running? I have JB installed (4.1.1)
2: So what version of TWRP do I need to download?
3: How would I install TWRP?
and yes, I am unlocked and rooted, help!
Download TWRP 2.5.0.0 for JB blob from here: http://teamw.in/project/twrp2/93
Rename to twrp.blob
Use command prompt on your computer to flash recovery to tablet using this command: fastboot -i 0x0b05 flash recovery twrp.blob
....................
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2038464
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
ArghMonkey said:
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
Click to expand...
Click to collapse
You can't use NVFlash because you are on the JB bootloader. You can't downgrade to ICS.
Great links!
Thanks for your help, I will report back once I try this
ArghMonkey said:
Great links!
Thanks for your help, I will report back once I try this
Click to expand...
Click to collapse
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
Click to expand...
Click to collapse
Ok, so I followed your link, I downloaded the Android SDK and when I opened it I see a million things, the Google USB Driver was highlighted so I installed it, are there other drivers im supposed to install before I go to the next step?!
Lavman72 said:
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Click to expand...
Click to collapse
Working on it right now, flashed twrp over, prime is starting up right now *fingers crossed*
and yes! it booted to stock, now to transfer over supersu ...
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
ArghMonkey said:
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
Click to expand...
Click to collapse
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Lavman72 said:
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Click to expand...
Click to collapse
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
ArghMonkey said:
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
Click to expand...
Click to collapse
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Lavman72 said:
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Click to expand...
Click to collapse
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
ArghMonkey said:
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
Click to expand...
Click to collapse
Rooted: Check
Unlocked bootloader: Check
Tired though, and it's late. So I'm going to hold off on the final steps.
i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root
Hello everyone,
tl;dr version
What's the best way to install a custom rom on the Redmi Note 3 out of the box with a locked bootloader. What is the best rom to use for maximum functionality.
I have been following these forums for a while, but haven't got around to creating an account and posting. I'm new to flashing roms, and my experience goes as far as following guides to flash a Samsung S4, and a Samsung S2. The Samsung phones were really easy to flash, and I just followed guides in a robotic way without ever actually learning anything. For the record, CM12 on the Samsung S2, which I'm using because I smashed my S4, is absolutely unbelievable in regards to the increase of performance.
One of my work friends was telling me that he has a mate who bought a Chinese phone really cheap and flashed it. Getting excited, knowing exactly where I need to look to flash a phone, I impulsively researched these phones and bought a Redmi Note 3 for $173 AUD. It's on the way in the mail. Having looked at the hardware specs, this price is absolutely ridiculous. I was more swayed to buy the Redmi Note 3, because multiple sites reported that the second sim slot can hold a micro SD card. The only downside I can see to this phone is the bloatware and stock rom that it comes with, and the reason for this post is to discuss the best way in which to flash a new rom. If you have managed to read this far, thanks for reading my life story!
Having limited experience in the phone flashing world, from researching it looks like the flashing process is something like:
Unlock the bootloader
Flash a recovery program
Use the recovery to flash rom/app
My understanding of the bootloader and why it needs to be unlocked is limited. I've done some research around it, and this is what I have found. The bootloader is the first thing that runs when the phone starts up, loads the kernel and the rom, and verifies that you have a legit recovery program. It needs to be unlocked so you can put a custom recovery on to your phone. Once you have that sorted, flashing roms from the recovery is a pretty straight forward process. If I'm wrong, please correct me, because this is what I have understood from looking around and I'm not confident about my understanding.
Unlocking the Bootloader On The Redmi Note 3
Having read on multiple sites, this looks like the biggest constraint when trying to flash a custom rom on the Redmi Note 3. This is because Xiaomi have locked the bootloader for this device, when most other phones do not have this problem. Most flashing guides for the Redmi Note 3 assume that the boodloader is unlocked or list it as a pre-requisite, so I'm unsure what path to take here. From research, it looks like there are 3 possible ways to move forward from here:
Official Bootloader Unlock
Unofficial Bootloader Unlock
Bypassing The Bootloader Unlock
Because my account is new, the following links aren't hyperlinked and in a good format due to permissions. Sorry! It'd be sweet if a mod could edit it.
1. Official Bootloader Unlock
This seems like the most legit way to unlock the bootloader. Apparently you just go to: endotmiuidotcom/unlock/ and apply for an unlock by using google translate and creating an account. People have reported response times taking over a month, not getting a successful application, or the unlocking process getting stuck at 50%. To me this doesn't sound appealing and I'm not too keen on waiting a month to find I'm unsuccessful in applying.
2. Unofficial Bootloader Unlock
This process is found here: endotmiuidotcom/thread-253680-1-1.html and looks to be a bit tedious. Apparently there is a high chance for a brick using this method, and some custom recoveries don't work well with it. My other concern is that if the brickrate is high, and this method was released around april, it could be possible that Xiaomi has made some further updates, further increasing the chance for a brick.
3. Bypassing The Bootloader Unlock
I found this process on a post from these forums, which then sourced a reddit post. The reddit post is pretty straight forward and can be found here: wwwdotredditdotcom/r/Xiaomi/comments/5611tg/psa_you_can_flash_twrp_and_subsequently_cm13/ .This process works by flashing a legit miui rom, but by flashing it with a modified recovery image, in particular, a custom recovery like TWRP. Having considered the three methods, this looks like the easiest way of getting it done.
My questions are: has anyone done any of these three methods successfully? What method do you recommend? Have I missed anything? Are there any other methods?
My understanding is once the bootloader is unlocked, you install TWRP. Then once that is installed you flash whatever rom you want, which leads into my next question. What is the best ROM to use?
It looks like the most viable roms are the CM roms. I've seen CM 13 and CM 14, are people running CM 13 instead of 14. Why? Is it more stable? Ideally I'm after the most functionality possible. Are there any other roms that you'd recommend flashing? When flashing roms are you supposed to do all the standard things that you would on other phones, factory wipe/cache wipe/davlik cache wipe, flash rom, flash gapps? I've also seen that CM needs firmware flashed before the rom, will this mess anything up and can it brick? Can you do all this stuff from TWRP with a locked bootlader (method 3)? I really like having notification badges too, what will I need to do for this to happen?
If you have read all of this, I really appreciate you taking the time. I hope I haven't broken any forum rules in the process.
dude,it's too much to read for people. I can't believe i read it,anyway.
about unlocking the bootloader process(I'm telling you about my experience):
---step 1 : you sign up for a mi account,choose your country and verify your phone number>login to your mi account on your device(remember to enable every feature on your mi account on your device,you can disable backup)> go to https://i.mi.com and check your device,it should be there> go to http://en.miui.com/unlock/ , write for example dear sir or madam, I'm an austrailian developer and I want to try and work on projects like cyanogen mods and other custom roms. sincerely,JaFranchise - alright,after finishing the writing go to translate.google.com and translate it to chinese,then paste on the form,then apply,you will confirm your request by entering the code that was sent to you via mi message --- for me it took about 3 to 4 hours to receive my confirmation.
---step 2 : first try this,if you stuck on 50% error,you will try step 3,so here is the instruction,
sign in to your mi account on your device(enable find device),also on i.mi.com(to check your device). enable developer options,OEM unlocking and USB debugging. > download the latest version of MIFlashUnlock tool and log into your account link : http://bigota.d.miui.com/miflashunlock/MiFlashUnlock_1.1.0317.1_en.zip> turn off your device and go to fastboot (press and hold volume - and power button at the same time), connect your device to your PC, click unlock(on MIFlashUnlock tool), after your bootloader successfully unlocked, click on reboot.
---step 3 : this is for kenzo devices(redmi note 3 pro - snapdragon650) - if you're using redmi note 3(mediatekX10), you should download the roms(stable and developer) according to your device
you need to switch from global stable to global developer rom, download the latest global developer rom on android lollipop(5.1). link : http://bigota.d.miui.com/6.8.18/miui_HMNote3ProGlobal_6.8.18_d0da79d09e_5.1.zip> after downloading the rom,rename the file name to Update.zip then copy to internal storage(in downloaded_rom folder).> open updater app, select choose update package, go to downloaded_rom folder and select Update.zip. It will verify your rom and install it. > download the latest global developer rom from en.miui.com/download-301.html , repeat the instruction or just simply download via updater > then follow step 2
I think,It's better you first unlock bootloader,then mention me in the comments to go through that(about cm and aosp roms and flashing instructions) process.
goodluck.
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
JaFranchise said:
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
Click to expand...
Click to collapse
It's alot easier than it sounds. The hardest part is probably getting the drivers on your computer installed properly to unlock bootloader/miflash. The good thing about this device is if you brick it, it's fairly simple to unbrick via the edl method but yea, official unlock bootloader - flash zcx twrp - make a backup - flash away
Hemphiz said:
It's alot easier than it sounds. The hardest part is probably getting the drivers on your computer installed properly to unlock bootloader/miflash. The good thing about this device is if you brick it, it's fairly simple to unbrick via the edl method but yea, official unlock bootloader - flash zcx twrp - make a backup - flash away
Click to expand...
Click to collapse
So it looks like official unlock is the way to go about things. Why ZCX version of TWRP?
ZCX is essentially the official TWRP, but with some extra stuff in it to allow it to support F2FS, if I'm not mistaken. Since you've decided to unlock your bootloader the official way, both ZCX and the official twrp are fine.
JaFranchise said:
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
Click to expand...
Click to collapse
you're welcome,yes if you officially unlock the bootloader,everytime you face an issue,for example got your bootloader locked again,you can use miflashunlock with ease.about the version of the twrp,i should say ZCX_TWRP_0917 is the way to go,it got everything you'll ever needed except for encryption you need lazyflasher-I don't want to go into details to make you confused-for more info about twrp and other roms check these links :
1- ⋆⋆ NEWBIE GUIDE ⋆⋆ [UPDATED] Available TWRPs, Add-On Zips, Root, Flash, Restore, FAQ
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
2-step by step instructions for zcx twrp
http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
3- comprehensive guide for unlocking bootloader process
http://en.miui.com/thread-246705-1-1.html
Samsung Galaxy S4 (SGH-I337) locked at AT&T bootup screen, then I "tried" to fix it..
Well, as the title suggests, I f***ed (Not sure if swearing is allowed...) up my device. I did the upgrade to 5.0.1 and keep root method by another user a while back, then yesterday, Super SU asked if I wanted to disable KNOX, which forgetting that I had a locked device I accepted. The phone died and I saw the issue on bootup. I went to Odin to try to flash the stock firmware back onto it, and that is to no avail. Now I am willing to redo the "keep root" method, but I need to backup my files! I opened Kies 3 with the device set in download mode, and it isn't detecting the device. I've tried both versions of Kies (2.6 & 3) & another 3rd party program.
TL;DR:
I basically need someone to tell me a way to backup my files, or a way to fix this without any data loss!
Thanks
- HyperFirez
Are you able to get into TWRP recovery and make a data backup to your SDcard?
Akti88 said:
Are you able to get into TWRP recovery and make a data backup to your SDcard?
Click to expand...
Click to collapse
Ya see, when they pushed the lollipop update to the phones, AT&T took the opportunity to lock the bootloader as well... So TWRP is a no go. Before the lollipop update, the bootloader was open, and I rooted the device before. I used this method (I'm sure this is on the forums here somewhere, I just can't find it): https://www.sammobile.com/forum/showthread.php?t=26464
This might help you if you can find a way to get into ADB you could do a backup from there http://forums.androidcentral.com/ge...n-can-t-access-recovery-mode.html#post3698554
If you can't get into ADB because of locked bootloader, try: http://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
Akti88 said:
This might help you if you can find a way to get into ADB you could do a backup from there http://forums.androidcentral.com/ge...n-can-t-access-recovery-mode.html#post3698554
If you can't get into ADB because of locked bootloader, try: http://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
Click to expand...
Click to collapse
I've used that exact guide before, and it doesn't work. AT&T are assholes.
HyperFirez said:
I've used that exact guide before, and it doesn't work. AT&T are assholes.
Click to expand...
Click to collapse
Man I'm sorry to hear that. Hopefully someone with some expertise jumps in this thread to help you out, as I can only suggest things you seem to already be aware of
I'll try to post some more threads that may help, maybe the thread bump will get an expert in here for you.
"Bootloader unlock Galaxy s4 sgh-i337 4.4.2 kitkat" https://forum.xda-developers.com/showthread.php?t=2785166
[Youtube] Install Safestrap Recovery & Custom ROMs on Your Bootloader-Locked Samsung Galaxy S4 [How-To] https://www.youtube.com/watch?v=GqmV8JwO7iY
Akti88 said:
Man I'm sorry to hear that. Hopefully someone with some expertise jumps in this thread to help you out, as I can only suggest things you seem to already be aware of
I'll try to post some more threads that may help, maybe the thread bump will get an expert in here for you.
"Bootloader unlock Galaxy s4 sgh-i337 4.4.2 kitkat" https://forum.xda-developers.com/showthread.php?t=2785166
[Youtube] Install Safestrap Recovery & Custom ROMs on Your Bootloader-Locked Samsung Galaxy S4 [How-To] https://www.youtube.com/watch?v=GqmV8JwO7iY
Click to expand...
Click to collapse
I already re-did the keep root method once more. I just hate that I lost my files...