Related
I just got this in the mail today. Does anyone have any insights on how to unlock the bootloader and inject root? I had assumed 'fastboot' would work, but this has ODIN. I'm sure I could follow the steps on the original S4, but I don't know what the downstream effects will be.
Thanks!
----------------------------------------------------------------------------------
Edit: Please see this post: http://forum.xda-developers.com/showpost.php?p=44322019&postcount=70
Ok, just got done rooting my gs4 vzw dev edition. It was really pretty simple.
Steps from my win8 laptop were...
Install samsung drivers,
get adb working (android sdk doesn't seem to work on win8.. but just the adb files are all you need, google adb platform-tools or just use win7)
dl and push your superuser zip to the sdcard or external sdcard
dl odin 3.07 and extract to pc
dl and make tar.md5 of your favorite recovery. ( i personally like cwm )
Then all I did was... reboot phone in to odin mode... while phone is powered off, hold vol down + power
Start odin.exe
uncheck auto-reboot
click pda button, select the recovery file.md5
press start and let it finish, only takes a few secs...
once done.. reboot in to recovery, and flash the superuser.zip u pushed over to it.
Vol up + power to boot in to recovery. for me i just booted the phone normally... used "adb reboot recovery" then flashed superuser.zip.
reboot your phone and done.
good idea to make a backup while ur in recovery
If someone has hosting, i can send the files needed.
-r4ph
Click to expand...
Click to collapse
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
equake said:
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
It became available yesterday, and I got overnight shipping.
tithefug said:
It became available yesterday, and I got overnight shipping.
Click to expand...
Click to collapse
Is it full of VW blot ware?
rcb929 said:
Is it full of VW blot ware?
Click to expand...
Click to collapse
Yes. The only difference is that this has an unlocked bootloader by default.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
markwebb said:
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
Click to expand...
Click to collapse
Probably. But, I knew that would work.
tithefug said:
Probably. But, I knew that would work.
Click to expand...
Click to collapse
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
markwebb said:
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
The boot message you see when you power on your device means your device is rooted. I have the same exact thing when I rooted mine. I got mine from a Verizon store.
Sent from my SCH-I545 using xda app-developers app
tithefug said:
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
Click to expand...
Click to collapse
What backup method are you using: CWM or TWRP?
cmmelton2 said:
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
Click to expand...
Click to collapse
Search for the phrase used in the notification. It had to so with SEAndroid. You have to delete/rename KNOXAgent.apk, KNOXAgent.odex from /system and com.sec.knox.seandroid from /data/data
Have fun!
markwebb said:
What backup method are you using: CWM or TWRP?
Click to expand...
Click to collapse
TWRP. I installed it using the GooManager app.
tithefug said:
TWRP. I installed it using the GooManager app.
Click to expand...
Click to collapse
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
markwebb said:
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
Click to expand...
Click to collapse
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
tithefug said:
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
Click to expand...
Click to collapse
Was just wondering if you tried CM yet?
markwebb said:
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
I would also like to see the best/correct way to root the Developer Edition.
markwebb said:
Was just wondering if you tried CM yet?
Click to expand...
Click to collapse
Not yet. It's going to have to wait until tomorrow. Sorry.
is it gay to taste your own semen?
what about drinking it?
vipercode said:
Long story short I deleted and wiped my entire system rom and partition in safestrap and didn't install a new OS before rebooting
Now my phone will not enter safestrap to allow me to install a new rom
I cannot flash stock rom through odin as I get a Fail: Auth error
I cannot find a serial number that works with kies to do a firmware upgrade
And using ADB to sideload gives me an error: "Could not read sideload"
So what options do I have left to fix this mess?
Click to expand...
Click to collapse
I will say that is a laundry list of issues.. I learn to fix things as tbey come and I have not yet had to odin my s4... I would recommend reading through the safestrap in both general and development and pm someone who states they have used odin successfully for help.. if by chance and heaven forbid I need to utilize odin I will respond again.. I am sorry I couldnt be helpful, good luck.
vipercode said:
Long story short I deleted and wiped my entire system rom and partition in safestrap and didn't install a new OS before rebooting
Now my phone will not enter safestrap to allow me to install a new rom
I cannot flash stock rom through odin as I get a Fail: Auth error
I cannot find a serial number that works with kies to do a firmware upgrade
And using ADB to sideload gives me an error: "Could not read sideload"
So what options do I have left to fix this mess?
Click to expand...
Click to collapse
Just double checking. You weren't clear on this point. You are trying to odin a me7 stock image correct?
Sent from my SCH-I545 using xda app-developers app
shut the **** up its not gay ITS NOT GAY
vipercode said:
Yea, I gave it to my rooting expert friend and he fixed after like 6 hours. Said that I had write protection enabled and therefore I couldn't flash anything that wasnt digitally signed by verizon so he fixed that then flashed the stock rom again. Its running again and thats all I care about thanks guys
Click to expand...
Click to collapse
Can you ask your friend how he bypassed the digital signature?
And this might be a huge favor but, can you ask him if he can bypass the MF3 signature?
Odischeese said:
Can you ask your friend how he bypassed the digital signature?
And this might be a huge favor but, can you ask him if he can bypass the MF3 signature?
Click to expand...
Click to collapse
He didn't bypass the signature, he just installed the proper stock ROM. Or that's the most likely thing to have done.
If he's able to bypass the signature, he could collect the bootloader bounty.
k1mu said:
He didn't bypass the signature, he just installed the proper stock ROM. Or that's the most likely thing to have done.
If he's able to bypass the signature, he could collect the bootloader bounty.
Click to expand...
Click to collapse
Lol doesn't matter anymore. 4.3 is able to be flashed if you have MF3, Which was my problem. Doesn't matter anymore! i got my phone fixed anyways! :good:
Odischeese said:
Lol doesn't matter anymore. 4.3 is able to be flashed if you have MF3, Which was my problem. Doesn't matter anymore! i got my phone fixed anyways! :good:
Click to expand...
Click to collapse
I'm confused. What is "MF3"?
Edit: I see. You're talking about an AT&T GS4, apparently.
k1mu said:
I'm confused. What is "MF3"?
Click to expand...
Click to collapse
I think it's AT&T.
riker147 said:
I think it's AT&T.
Click to expand...
Click to collapse
Yeah he's right.
The god forbidding baseband version ATT released.
No one could flash the stock rom with odin.
Untill today...:good:
I want to cut it to the chase, but I am going to attach a video too because this may help!
I had safe strap installed on my i545 Verizon Galaxy S4 on Me7 and I installed several different roms with no problem. Today, I was rocking the eclipse rom, but decided that I wanted to return to the hyperdrive rom that I had yesterday.
I know the Rom works because i had the exact ZIP file flashed and working yesterday...
But now I flashed it and then the module files and when I reboot it stays on the samsung boot logo and will not show safetrap... its just stuck there...
I don't care what it is I need to do, even if I lose safe trap or root, I want my phone fixed. But I'd love to keep it if possible
Im freaking out but I can go into download mode and some weird blue recovery mode if I hit Volume down + power or Volume up + power.
What are my options?
Thank you so much!
Have you tried a battery pull?
lazer9 said:
Have you tried a battery pull?
Click to expand...
Click to collapse
Yes of course, that does nothing Can I just reinstall the stock firmware with odin?
dannyboy42670 said:
Yes of course, that does nothing Can I just reinstall the stock firmware with odin?
Click to expand...
Click to collapse
Yes, I would try this --->> http://forum.xda-developers.com/showthread.php?t=2301259
Pick your appropriate build.
Then if all goes well, you can re-install safestrap and see if your ROM slots are still viable.
lazer9 said:
Yes, I would try this --->> http://forum.xda-developers.com/showthread.php?t=2301259
Pick your appropriate build.
Then if all goes well, you can re-install safestrap and see if your ROM slots are still viable.
Click to expand...
Click to collapse
Thanks for the quick replies! I will try that now I really hope I didnt do any permanent damage. I thought that safe trap does not touch anything that will harm the device?
dannyboy42670 said:
Thanks for the quick replies! I will try that now I really hope I didnt do any permanent damage. I thought that safe trap does not touch anything that will harm the device?
Click to expand...
Click to collapse
It shouldn't have. Unless you may have accidentally tried to install a rom to the SAFE (Stock) side and something went wrong.
lazer9 said:
It shouldn't have. Unless you may have accidentally tried to install a rom to the SAFE (Stock) side and something went wrong.
Click to expand...
Click to collapse
If that is the case, will I still be able to fix with odin? I'm downloading the firmware file now
dannyboy42670 said:
If that is the case, will I still be able to fix with odin? I'm downloading the firmware file now
Click to expand...
Click to collapse
If you can get into download mode then Odin should fix you up.
You are on mdk? hence the "blue recovery" .
Sent from my SCH-I545 using Tapatalk
Addiso said:
You are on mdk? hence the "blue recovery" .
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I learn something new every day!
UPDATE: I have successful fixed my issue by going into download mode and re-flashing stock ME7.
I have no idea what my issue was but currently have HyperDrive running again! All is well thank you so much everyone! :fingers-crossed:
Cheers from Boston!
dannyboy42670 said:
I learn something new every day!
UPDATE: I have successful fixed my issue by going into download mode and re-flashing stock ME7.
I have no idea what my issue was but currently have HyperDrive running again! All is well thank you so much everyone! :fingers-crossed:
Cheers from Boston!
Click to expand...
Click to collapse
Glad to here you got it sorted! :highfive:
xxx
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"
Hi There,
I'm running a rooted version of KitKat 4.4.4 on my Z2 (23.0.1.A.0.167) and I was just wondering about the process of upgrading to a rooted version of Lollipop. Can I just upgrade using the standard method (from the settings menu) and retain root access? Or will I have to flash an entirely new Lollipop ROM onto the device and then root that separately?
I'm in no rush for Lollipop so I'm happy to wait for the official upgrade, but if it won't be possible or will mess up my device then I'd rather just do whatever it takes to get it flashed.
BottleGreen said:
Hi There,
I'm running a rooted version of KitKat 4.4.4 on my Z2 (23.0.1.A.0.167) and I was just wondering about the process of upgrading to a rooted version of Lollipop. Can I just upgrade using the standard method (from the settings menu) and retain root access? Or will I have to flash an entirely new Lollipop ROM onto the device and then root that separately?
I'm in no rush for Lollipop so I'm happy to wait for the official upgrade, but if it won't be possible or will mess up my device then I'd rather just do whatever it takes to get it flashed.
Click to expand...
Click to collapse
I guess your bootloader is still intact, if so you're good to go. You will will only lose root when you update to lollipop through OTA.
On the other hand, if you've unlocked your bootloader and probably have a custom kernel, then I'm afraid ota will not work.
Hope this helps.
BottleGreen said:
Hi There,
... and I was just wondering about the process of upgrading to a rooted version of Lollipop.
Click to expand...
Click to collapse
sublinker said:
I guess your bootloader is still intact, if so you're good to go. You will will only lose root when you update to lollipop through OTA.
On the other hand, if you've unlocked your bootloader and probably have a custom kernel, then I'm afraid ota will not work.
Hope this helps.
Click to expand...
Click to collapse
If the desired outcome is root on lollipop, don't do ota.
Install recovery (if you don't have one) and flash a rooted lollipop zip through recovery.
@o0 Matt 0o, you've made your point but I guess quoting me wasn't necessary.
Thanks for the replies, a couple of questions still though:
o0 Matt 0o said:
If the desired outcome is root on lollipop, don't do ota.
Install recovery (if you don't have one) and flash a rooted lollipop zip through recovery.
Click to expand...
Click to collapse
I think I have recovery, though I can't remember to be honest. I followed a guide here when I rooted my Z2.
If I flash a rooted L zip does this mean I'll lose all my apps/data? I remember that I did when I rooted 4.4.4 but the process was such a headache that I can't remember which parts required wiping everything from my phone.
Also, is there a ROM version you'd recommend? Is the current one stable or should I wait a little while longer for a better one?
Google recovery and Xperia to see videos of how to get into recovery to find out if you have it.
You don't 'need' to wipe, but it's always advised. Before I flash I do a nandroid backup and wipe and recovery specific app data with nandroid manager.
Have a look at the dev section, there is a rooted stock lollipop room there. lollipop is stable and awesome.
If.I helped don't forget to hit thanks [emoji14]
o0 Matt 0o said:
Google recovery and Xperia to see videos of how to get into recovery to find out if you have it.
You don't 'need' to wipe, but it's always advised. Before I flash I do a nandroid backup and wipe and recovery specific app data with nandroid manager.
Have a look at the dev section, there is a rooted stock lollipop room there. lollipop is stable and awesome.
If.I helped don't forget to hit thanks [emoji14]
Click to expand...
Click to collapse
Is it worth waiting for a Lollipop 5.1 ROM or would this ROM update to 5.1 without needing to be flashed? http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150/ (I presume this is the ROM you were talking about?)
Thanks, turns out I do have recovery. I followed this guide all the way through: http://forum.xda-developers.com/xperia-z2/general/how-to-root-23-0-1-0-167-fw-sony-xperia-t2928591/
So seeing as I have CWM recovery on there. Does this mean I can just use flashtool to put the lollipop ROM onto CWM Recovery and then do 'install from zip' and all should be good?
What would happen if I flashed without wiping the data? I'm more inclined to wipe too, but I wondered if it's possible to do it without wiping.
BottleGreen said:
Is it worth waiting for a Lollipop 5.1 ROM or would this ROM update to 5.1 without needing to be flashed? http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150/ (I presume this is the ROM you were talking about?).
Click to expand...
Click to collapse
Yea that's what I was referring to. Once 5.1 comes out you'll need to do the same thing to keep root so it's up to you if you do it once or twice.
BottleGreen said:
Thanks, turns out I do have recovery. I followed this guide all the way through: http://forum.xda-developers.com/xperia-z2/general/how-to-root-23-0-1-0-167-fw-sony-xperia-t2928591/
Click to expand...
Click to collapse
Good
BottleGreen said:
So seeing as I have CWM recovery on there. Does this mean I can just use flashtool to put the lollipop ROM onto CWM Recovery and then do 'install from zip' and all should be good?
Click to expand...
Click to collapse
No. No flashtool needed just get the zip into the phone (either download it on the phone or use a usb cable to copy it over) then go to install zip.
BottleGreen said:
What would happen if I flashed without wiping the data? I'm more inclined to wipe too, but I wondered if it's possible to do it without wiping.
Click to expand...
Click to collapse
What would happen depends on what you've done:
Best case nothing happens
Medium case apps misbehave
Worst case bootloop
It is possible and give it a go. Make sure you do a backup first and copy the backup to your computer just in case. If bad things happen, recovery the backup and try again another way.
o0 Matt 0o said:
Yea that's what I was referring to. Once 5.1 comes out you'll need to do the same thing to keep root so it's up to you if you do it once or twice.
Good
No. No flashtool needed just get the zip into the phone (either download it on the phone or use a usb cable to copy it over) then go to install zip.
What would happen depends on what you've done:
Best case nothing happens
Medium case apps misbehave
Worst case bootloop
It is possible and give it a go. Make sure you do a backup first and copy the backup to your computer just in case. If bad things happen, recovery the backup and try again another way.
Click to expand...
Click to collapse
Okay perfect, thanks for that. One last question though, in that thread with the Lollipop ROM someone mentioned that you could lose your recovery if you install it (I guess because of a bug or something). Will this affect me if I want to install 5.1 later on?
Not really. You'll just need to get back to a ROM with recovery for locked bootloader or wait until they get recovery working on locked bootloader on 5.0
o0 Matt 0o said:
Not really. You'll just need to get back to a ROM with recovery for locked bootloader or wait until they get recovery working on locked bootloader on 5.0
Click to expand...
Click to collapse
Okay, so my bootloader has been unlocked. Does that mean I won't be affected at all?
BottleGreen said:
Okay, so my bootloader has been unlocked. Does that mean I won't be affected at all?
Click to expand...
Click to collapse
Is that first sentence a statement or a question?
Bootloader unlocked means freedom. Life is a lot easier, just flash a kernel with recovery and upgrade
o0 Matt 0o said:
Is that first sentence a statement or a question?
Bootloader unlocked means freedom. Life is a lot easier, just flash a kernel with recovery and upgrade
Click to expand...
Click to collapse
Yes my bootloader is unlocked, I used the Sony method. I didn't think I could flash a rooted ROM without it to be honest.
Hmm, I think I'm confusing recovery with Bootloader though here. I thought Recovery was part of the bootloader unlocking process and was separate from the ROM. Kind of like a small management interface to flash new ROMs and manage the device from the boot partition.
Does anyone have an answer to the above? I'm just trying to make sense of the process here.
What do you want to know? What the bootloader is?
http://forum.xda-developers.com/wiki/Bootloader
o0 Matt 0o said:
What do you want to know? What the bootloader is?
http://forum.xda-developers.com/wiki/Bootloader
Click to expand...
Click to collapse
I'd really like to know what 'recovery' is exactly and how it differs from either a ROM or a bootloader. I understand the Xperia Z2 stock rooted Lollipop ROM has no recovery, so I want to know what exactly that means and what the implications are in the event I choose to upgrade to 5.1 in the future.