Related
I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
Wrong section...
fbihawk said:
I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
Click to expand...
Click to collapse
Ok, first step, it's very important...POST QUESTIONS IN THE G.D. Q&A SECTION!
Sorry, thought that since this was closely related to a few threads in the dev section that it would be more helpful to people here.
Re-submitted to the q&a section. Thanks.
Use this, it's helped me a lot.
fbihawk said:
I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
Click to expand...
Click to collapse
http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
fbihawk said:
Sorry, thought that since this was closely related to a few threads in the dev section that it would be more helpful to people here.
Re-submitted to the q&a section. Thanks.
Click to expand...
Click to collapse
Q&A's are in no way closely related to threads in a section where developers post their work... Questions, are not ROM's so next time read the ****ing rules!!!!!!!!!!!!!!!!!!!! Thread reported!!!!!!!!
EDIT: Let's keep this thread focused on how we can move past old methods, and make some progress towards modding. Thanks, and any relevant input is welcome.
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
lkrasner said:
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
Click to expand...
Click to collapse
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
scott14719 said:
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
Click to expand...
Click to collapse
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it. I am trying to learn quickly, and as you all know, devices are very different.
From what I understand, LOKI allows recovery to be overwritten, or is at least more permanent. What happens if you were to totally kill your system, could you still get into recovery with loki?
I understand that this is not motorola, and I am not trying to be stubborn here, but I fell like the same basic boot hijack that a ton of locked devices use should work.
lkrasner said:
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it.
Click to expand...
Click to collapse
http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html
and http://forum.xda-developers.com/showthread.php?t=2292157
lkrasner said:
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Click to expand...
Click to collapse
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
scott14719 said:
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
Click to expand...
Click to collapse
Thanks, It still looks to me like loki is a bit more advanced than what I am talking about, though the underlying principle is the same. LOKI allows the phone to actually boot a kernel (or recovery kernel) a boot hijack just loads some files on top of what is already running.
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
ashaton said:
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
Click to expand...
Click to collapse
Thanks, I am sure that will prove helpful.
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
The entire thread is very interesting. Starting around "Post# 115" and beyond there is talk about (what i believe) you are trying to do with the bootstrap idea. Maybe it will help you.
scott14719 said:
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
Click to expand...
Click to collapse
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
lkrasner said:
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
Click to expand...
Click to collapse
I edited my above post. I believe around post 115 and beyond of the above linked thread there is some information about the bootstrap idea you have.
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
scott14719 said:
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
Click to expand...
Click to collapse
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I'm just theorizing there from what I "think" I know. It still might be worth a try. The resulting TAR could:
1. Work, and if so we will have an ODIN flashable firmware for MF3. It doesn't matter if it is 'Frankenstein'd" or not...if it works it works!
2. Not work, but only fail in ODIN not causing anything to change or brick.
3. Not work and cause a soft or hard brick that can not be recovered from because it didn't work.
So, once again, finding someone to test the finished product out would be an issue. I'm guessing someone that is already hard bricked and already previously on MF3 could test because they already have nothing to lose (with JTAG not working for MF3).
I think Aou has deconstructed the MF3 OTA and pulled the bootloader(s) out of it. If someone can pull an MF3 image from their device and the bootloader can be added to it...and it can be made into a flashable TAR, maybe it would work. I don't think it will because of the reasons I listed in my last post...but it might.
Anyone willing to put it together and try it?
I think the problem is that it won't be signed. That is how it was with the a2. We just used fastboot but it would not flash an unsigned image
Sent from my Nexus 7 using xda premium
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
Click to expand...
Click to collapse
ashaton said:
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Click to expand...
Click to collapse
Yup, that's what I was saying. I can try to port a bootstrap cwm, but I really do not want to be the one to test it
Sent from my Nexus 7 using xda premium
I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.
bur2000 said:
I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.
Click to expand...
Click to collapse
You can find all the stock firmware images here:
http://sbf.droid-developers.org/phone.php?device=14
Flash either with RDS (http://forum.xda-developers.com/showthread.php?t=2637338) or fastboot (http://forum.xda-developers.com/showthread.php?t=2542219)
Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.
bur2000 said:
Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.
Click to expand...
Click to collapse
You can flash any firmware you want, except the ones for dual sim version (but if you want to be totally safe flash the retail de image). 4.4.4 images aren't available currently, you have simply to restore the stock 4.4.2, flash the stock recovery and take the OTA update.
The ROM you linked is for Moto G dual sim variant (XT1033), flashing it will probably cause a soft brick.
I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
2. How can I flash the rom if the phone keeps doing this?
Any help would be much appreciated. Thank you.
fertchen said:
I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
Click to expand...
Click to collapse
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
2. How can I flash the rom if the phone keeps doing this?
Click to expand...
Click to collapse
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.
bur2000 said:
After that no problems.
Click to expand...
Click to collapse
Thank you very much. I will try that when I get home next week. Will be a nice exercise in living without a phone for some time...
bur2000 said:
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.
Click to expand...
Click to collapse
Just did the same mistake with unlocked & rooted XT1032. I use TWRP and ended up there after every reboot. What I did is use the File Manager under "Advanced" to delete the .zip under /cache. Alternatively you could just wipe cache/ dalvik cache and the update zip should be gone, phone should reboot normally and after app optimization (if you wiped dalvik cache) everything should be back to normal. The first few seconds I got an error when checking for an update, but it went away after a minute.
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...
I was in the same situation, with bootloader active from cmd:
mfastboot erase cache
or whatever you use
Any improvement?
Hello everyone,
I had the same problem and had to restore a backup.
But can anyone tell us why this happens? Is Google aware of this and is a fix on the way?
I've seen that the update would fix the annoying incompatibility problem with the class 10 SDCards so I'd like to install this update.
I have seen that some of the improvements would also be :
- coloured tiles in the phone dialer
- ability to pause when you record a video
But I can already do that with my phone right now (I'm in 4.4.3 on a Moto G 4G), is this normal ?
Thank you.
suiller said:
I was in the same situation, with bootloader active from cmd:
Click to expand...
Click to collapse
Thank you very much, suiller. This:
fastboot erase cache
did it for me.
gnayug said:
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...
Click to expand...
Click to collapse
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?
fertchen said:
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?
Click to expand...
Click to collapse
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me. Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
...Help?
gnayug said:
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me.
Click to expand...
Click to collapse
My guess is that there are just too many versions of phones out there and too many different prerequisites (differences in how the phone was rooted, which apps might have been de-installed, which rom/recovery installed etc) that it is extremely hard and laborious to provide a truly foolproof way. That might be different if there was one standardized manual/tutorial on "Hot to root foolproof and OTA proof for the future" and everyone would follow that precisely.
gnayug said:
Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
Click to expand...
Click to collapse
There is a page that lists all the available stock Moto G Roms in different versions. It would be great if there was such a page for the recovery as well.
If there was a person that decided to take care of all these issues for the Moto G on this forum, he or she could maintain a page with direct links to all the tools, roms and recoveries as well as one general (foolproof) and possibly a handful of alternate ways and fixes.
That is a lot of work, particularly dealing with people who are not willing to read more than one sentence in order to get what they want. And certainly it must be frustrating for a "freak" or dev to encounter us newbies on a daily basis. A 101/primer on what boot/recovery/rom etc is would be helpful - and it does even exist in the wiki. It's that many of us don't find it. That could be changed by a very well thought-out and structured sticky post that provides all the necessary links and knowledge but not too much so that a beginner is frightened by 10 pages of instructions.
But I am certain that a person would be willing to do that if this forum allows it (which I assume is the case). Maybe this person has not been identified yet. Or maybe we have just missed it. I know I will not be this person simply because it would take me a lot of time to gather the necessary knowledge for such a position and right now I have other priorities and I usually use my phone once every 10 days or so.
I am aware that as a user I am not entitled to anyone providing this service. At the same time I am pretty sure that there is someone, maybe even within this great community, who would be willing to do it.
By the way, here is how I ultimately fixed the rooted-Moto G-OTA-update-problem: http://forum.xda-developers.com/moto-g/help/how-to-update-rooted-moto-g-t2828857/post54528345
Thank you for the link and everything you wrote! I was actually thinking the same the last few days... If only I was qualified enough or had the time to gather and polish all the information. I realize I shouldn't have written "Freaks". They're hard-working, skilled individuals that provide us with all this amazing software for us to use free of charge. I just wish they'd put some effort into explaining and laying out the basics etc. for all the "newbs" they encounter each day, because what good do their stuff do when nobody knows how to use it? All those devs that put out kernels and ROMs and then make a thread with changelogs and download links WITHOUT actually saying what they contain and why anyone should use them - I'm looking at you.
I'll go try to get my Moto G to 4.4.4 without losing my stuff using your link now, thanks again!:good:
So is it really so that the Xperia XZ does not have a recovery/bootloader menu?
I have unlocked the bootloader which needed the fastboot which works but now that I want to root the device and need TWRP I am getting nowhere since I can not get the device to go into recovery mode. this is annoying me badly, my phone is basically useless until I am done with this.
Any advice?
kane_1371 said:
So is it really so that the Xperia XZ does not have a recovery/bootloader menu?
I have unlocked the bootloader which needed the fastboot which works but now that I want to root the device and need TWRP I am getting nowhere since I can not get the device to go into recovery mode. this is annoying me badly, my phone is basically useless until I am done with this.
Any advice?
Click to expand...
Click to collapse
During the initial unlocking of the device of course it doesn't carry any recovery. Maybe ought to try powering down your device and press and hold the volume up key while connecting your device to the computer until the blue led is lit that's fastboot mode. Do this fastboot flash recovery recovery name.img then try accessing recovery after that. You now should have a working recovery.
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
You can find the available recovery.img on androplus website https://kernel.andro.plus/tone2.html for your corresponding firmware and androplus kernel fastboot flash boot boot.img.
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
The available instructions are posted on the website. Please make sure you have the perquisites.
Thanks.
Would you recommend running a custom rom or sticking to stock android and run xposed?
also, the first step it say boot into recovery bootloader, I don't understand how i am supposed to do that when there is none in the beginning.
I have tried everything any guide says and it just doesn't seem to work.
The adb says waiting for device as if the device is not there, the one click tool just doesn't do anything.
Idk anymore
kane_1371 said:
I have tried everything any guide says and it just doesn't seem to work.
The adb says waiting for device as if the device is not there, the one click tool just doesn't do anything.
Idk anymore
Click to expand...
Click to collapse
background (look at the date - some content is for Z3 xperias and older that do not have DM-Verity):
https://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
For the newer phones follow the instructions you find in the device-fora.
Here (after a full wipe) you get started following the instructions written by AndroPlus.
You need the right ROM and TWRP (recovery) for your ROM-version. Look at the changelog.
e.g.: I am on 39.2.A.0.374. There is no kernel for that right now -> I can not get into recovery -> no root for me ATM
fastboot boot TWRP_xy boots the recovery
You will become a "developer" on your device once you tapped seven times on the build number -> then you switch on adb debugging in the developer options
"When you unlock your bootloader you will lose all the DRM features on your device, this makes it valuable to have a backup of the unmodified version stowed away somewhere safe. You will need root level access to create that backup before unlocking. There is a tool called Backup TA which is widely used to create and restore backups of the TA partition. TWRP in XZDualRecovery can do the same. "
What the heck?
I need to backup TA, ok, but I need to have root to do this? ok, but to have root access I need to unlock my bootloader and flash a root boot which messes up with the TA?
It seems like every single one of these posts that I read just make things more confusing.
Why can't there just be a simple step by step that tells you what to do?
NVM, I actually flashed a recovery into the phone by using a combination of one click tool and Quickimage.
God this community need better tutorials and step by steps
Anyway now it is asking me for a password which is a surprise to me
OK past that too, did a backup and no I see that I have nothing but the recovery to boot to, hmmmm still figuring this thing out
It is amazing to imagine how **** is constantly hitting the fan.
The quick image thread has very little explanation and two screen shots which show that they are flashing the image to boot.
So I did exactly that and now I have no Boot but a recovery instead hhahahahahaha.
I am fairly depressed and desperate at this point
Well I somehow managed to install Xplayztation.
As mentioned before the only way possible for me to get a recovery installed was through flashing it on boot and loosing my access to the android at first and then installing a new rom through Twrp.
I have no idea what will the outcome for this be.
Any suggestions?
kane_1371 said:
God this community need better tutorials and step by steps
Click to expand...
Click to collapse
Go ahead!
You will find everything HERE and on
https://forum.xda-developers.com/crossdevice-dev/sony
There is more than plenty on the Z5 and Z3+ foro too...
In the Z5 forum you can really get to the technical beef if you want. The tutorial I quoted is gentle but written at a time when it was easier to root the devices.
The TA-Backup works via a vulnerability that raises the rights temporarily. This is not rooting per se since this does not survive a reboot.
Why can't there just be a simple step by step that tells you what to do?
Click to expand...
Click to collapse
Here on this forum (after a full wipe) you get started following the instructions written by AndroPlus.
or:
https://forum.xda-developers.com/showpost.php?p=70370065&postcount=7
DHGE said:
Go ahead!
You will find everything HERE and on
https://forum.xda-developers.com/crossdevice-dev/sony
There is more than plenty on the Z5 and Z3+ foro too...
In the Z5 forum you can really get to the technical beef if you want. The tutorial I quoted is gentle but written at a time when it was easier to root the devices.
The TA-Backup works via a vulnerability that raises the rights temporarily. This is not rooting per se since this does not survive a reboot.
Here on this forum (after a full wipe) you get started following the instructions written by AndroPlus.
or:
https://forum.xda-developers.com/showpost.php?p=70370065&postcount=7
Click to expand...
Click to collapse
Thanks for the links man.
Well I somehow managed to install Xplayztation.
As mentioned before the only way possible for me to get a recovery installed was through flashing it on boot and loosing my access to the android at first and then installing a new rom through Twrp.
I have no idea what will the outcome for this be.
Any suggestions?
Also I had already unlocked my bootloader when I learned about TA backup.
And then was confused that I am supposed to Root for it to work, so what are my options now?
Are the DRM keys reverseable through flashing my regions latest firmware via the flashtool?
kane_1371 said:
Thanks for the links man.
Also I had already unlocked my bootloader when I learned about TA backup.
Click to expand...
Click to collapse
You are welcome
Your TA-keys are gone. NO WAY to revover them. Do not even try - you will hardbrick your phone.
Follow the links I gave.
OK
Well I have the insurance on it, so if anything ever happens that is not reversible I will bust the phone and get a new one lol.
For now I will enjoy the stuff
It was a lot of trouble but I got what I wanted (moded Spotify app haha )
I want to root my xz too. Did you root it. If you did, how.? Plz reply
Im just gonna ask confirmation New to sony scene and never knew i had to backup the TA partion (Shouldve came here first normally would) but i assume theres no way to recovery DRM keys (i did install Androplus Kernel)
Well yes I did manage to do the work but I imagine the XZ is built in a manner that you can not root it without burning all the bridges behind you however I am basically the only person in this forum that I found to either have rooted their XZ or had to go through these many hassles.
As you can read in earlier posts I did have to backup the TA but by the time I knew about that I had already deleted the TA. The extended permission didn't work for me either so Idk if it was me doing something wrong or Sony going hard against rooters.
Also no TA is not reversible so once you do root and if you don't have the TA backed up don't even go for reinstalling the original rom because it will not work period.
I had to flash my boot and install recovery on that which is not the intended way of using recovery but I couldn't do it any other way, when you do that you basically are left with a paperweight the shape of a phone and then from there I would go to Boot instead of recover since recovery partition was empty and the recovery image was flashed on boot partition and use the recovery to install the rom.
But you should try to follow the step by steps posted in this forum by other people so maybe you won't have to endure the pain I did.
I have to say at this time I really feel like it wasn't even worth it because XZ is a pretty underwhelming phone even though I had a busted Z3 before this I never experienced such a slow phone with that.
XZ is just constantly out of ram and slows down and reboots the rom's shell which is pretty annoying.
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk