I've run into a huge problem that I hope someone here can help me with. I currently have a USA model XZ that is on Nougat 7.0. Completely stock, bootloader locked and everything. I've been reading and researching all the necessary steps to flash a custom rom on the XZ and am prepared. Have all the files I need, am following the steps in order and making sure I don't skip or overlook anything, but my problem is at the first few steps.
I am trying to backup my TA partition, but the problem is when I flash a 6.0 FTF. I flashed a European FTF, flashtool said successful, but when my phone booted, I reached a screen that said "To start Android, enter Password". I did not have a password on my phone to unlock, a pin, nor a pattern. I had it at swipe to unlock and made sure of it before I flashed the .FTF file. I googled, tried reading some threads here, but no luck. I entered my Google account password that was associated with my phone, nothing. It gave me 20 tries and if I got it wrong 20 times, it would factory reset I believe. Out of fear an panic, I flashed the newest USA FTF from Xperifirm and everything worked like normal. All my files, apps, and settings were there as if nothing ever happened.
Has anyone ever seen that screen? I wished I would've taken a picture, but I was completely afraid that I softbricked or did something wrong with my phone. I would love to try out a custom rom, but would prefer that I still have all my DRM keys intact. Could anyone help out? Thanks in advanced for reading and helping!
Related
Hey,
Does anyone has by chance the official OTA package .zip of ASA-14? I'm still on ASA-10 since I'm proceeding with updates very carefully, especially when I see no fixes that address my problems I've been trying to force update whole day today both from phone settings and from PC, and PC software tells me my software is up to date, and on the phone, it tells me I have to setup my MotoService account first, but pressing "Setup" gives never-ending "Communicating with server. Please wait...". I tried changing servers in shared_prefs of com.motorola.blur.service app, but it gave no difference. Also I discovered Skrillax zip packages aren't suitable for stock recovery (wrong signature), so no luck.
Anyone could help me? I need to update to ASA-14 because of JB coming, and I have locked bootloader
Have you tried using RSDLite to apply the FXZ files from Skrilax_CZ?
I've flashed ASA-14 using this, works great.
I've thought about RSDLite but I couldn't find consistent info about need of unlocked bootloader to use it... So I could use it without unlocking bootloader? It wipes all data from internal storage?
Thanks for help
micx_pl said:
I've thought about RSDLite but I couldn't find consistent info about need of unlocked bootloader to use it... So I could use it without unlocking bootloader? It wipes all data from internal storage?
Thanks for help
Click to expand...
Click to collapse
It basically sets your phone completely back to factory defaults. Wipes everything, every partition, recovery & all.
It does not matter if you are locked or unlocked on the bootloader. It is basically a tool which is supposed to only be used by providers, to restore phones in the repair facilities.
In the end, I backed up everything, did a factory reset, and the OTA update came right away
So, while I was messing around with my phone, I accidentally screwed stuff up. Unfortunately, I decided to get extra stupid and lock my bootloader. So now whenever i try to unlock my bootloader, boot into recovery or basically do anything beyond using CM11s, I get this youtu.be/tuWRHJA50hA. If any of you have any solutions, please help. If you need any extra details, I will be glad to answer. Thanks in advance for the help.
kurroption said:
So, while I was messing around with my phone, I accidentally screwed stuff up. Unfortunately, I decided to get extra stupid and lock my bootloader. So now whenever i try to unlock my bootloader, boot into recovery or basically do anything beyond using CM11s, I get this youtu.be/tuWRHJA50hA. If any of you have any solutions, please help. If you need any extra details, I will be glad to answer. Thanks in advance for the help.
Click to expand...
Click to collapse
You need to provide more information, like a detailed description of exactly what steps lead to this situation.
Heisenberg said:
You need to provide more information, like a detailed description of exactly what steps lead to this situation.
Click to expand...
Click to collapse
I wrote a detailed explanation on the OnePlus forums so here is it copy pasted.
TL;DR: Recovery won't boot, this happens
I've posted this on multiple sites to get as much help as possible. Check /u/braden26 for my posts on reddit about my issue. What I'm having trouble with is a strange issue when entering a recovery. . I'm guessing my recovery is corrupted or nonexistent, due to a few dumb mistakes I made. I first flashed the wrong rom and soft bricked my phone. At this time it was rooted, running cm 12.1 nightlies and using twrp. After this soft brick, I restored to cm11s, unlocked the bootloader and rooted. I installed sultan's cm12.1, but got another weird issue, so I decided to go back to cm12.1. Here's where my issue begins. When I tried to enter recovery, twrp was gone despite developer option for overwriting recoveries was off. So I downgraded to cm11s and tried again. Then it wouldn't install twrp at all. So I erased my recovery and accidentally hit oem lock instead of unlock. When I tried oem unlock after wards, it would reboot then do this which I already showed . The device runs fine, but I can't update cm11s to 12s or I stall custom recoveries. So I'm in a little bit of a problem here. I'm familiar with how to use fastboot, not all the commands, so don't be afraid to give them to me. Thank you for any help and if you need any more details please let me know.
kurroption said:
I wrote a detailed explanation on the OnePlus forums so here is it copy pasted.
TL;DR: Recovery won't boot, this happens
I've posted this on multiple sites to get as much help as possible. Check /u/braden26 for my posts on reddit about my issue. What I'm having trouble with is a strange issue when entering a recovery. . I'm guessing my recovery is corrupted or nonexistent, due to a few dumb mistakes I made. I first flashed the wrong rom and soft bricked my phone. At this time it was rooted, running cm 12.1 nightlies and using twrp. After this soft brick, I restored to cm11s, unlocked the bootloader and rooted. I installed sultan's cm12.1, but got another weird issue, so I decided to go back to cm12.1. Here's where my issue begins. When I tried to enter recovery, twrp was gone despite developer option for overwriting recoveries was off. So I downgraded to cm11s and tried again. Then it wouldn't install twrp at all. So I erased my recovery and accidentally hit oem lock instead of unlock. When I tried oem unlock after wards, it would reboot then do this which I already showed . The device runs fine, but I can't update cm11s to 12s or I stall custom recoveries. So I'm in a little bit of a problem here. I'm familiar with how to use fastboot, not all the commands, so don't be afraid to give them to me. Thank you for any help and if you need any more details please let me know.
Click to expand...
Click to collapse
You were using a toolkit?
Ok, so TWRP didn't initially stick and that's normal since Lollipop came out. It's in the FAQ thread, so doing some research most likely would have saved you from this whole situation. Right now though you're kinda screwed. With no recovery and a bootloader that won't unlock there's pretty much nothing you can do.
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
yahboyvictorr said:
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
Click to expand...
Click to collapse
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Jkay7 said:
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Click to expand...
Click to collapse
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
yahboyvictorr said:
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
Click to expand...
Click to collapse
Yes it is definitely a reason. Follow the steps from the guide I linked you step by step, it works 100%
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
Hello,
the long and short of it is that I tried to root my phone and then install Lineage, but ended up with no OS and now I can't use my phone. I simply want any OS so that I can use my phone. Any help would be greatly appreciated. I am a bit new to this kind of stuff, so I apologize in advance if I don't know some of the technical terms.
I am using a Samsung Galaxy S7 SM-930W8.
A bit more in detail:
I used two videos on youtube. 1 to teach my how to root, which got me into an OS. Then I used a video to teach me how to install Lineage, and that's when it all failed. After this, my phone was stuck in a never-ending loop of a circle going across a line and it never recovered.
I still have access to the TWRP when I hold down Vol-Up, Power and Home but when I try to reboot, it tells me there is no OS installed. I can't even use the recovery option, since I believe I deleted all the previously installed recoveries.
I feel silly for being in this predicament, but I would be so grateful for any help, folks!
-New2S7
New2S7 said:
Hello,
the long and short of it is that I tried to root my phone and then install Lineage, but ended up with no OS and now I can't use my phone. I simply want any OS so that I can use my phone. Any help would be greatly appreciated. I am a bit new to this kind of stuff, so I apologize in advance if I don't know some of the technical terms.
I am using a Samsung Galaxy S7 SM-930W8.
A bit more in detail:
I used two videos on youtube. 1 to teach my how to root, which got me into an OS. Then I used a video to teach me how to install Lineage, and that's when it all failed. After this, my phone was stuck in a never-ending loop of a circle going across a line and it never recovered.
I still have access to the TWRP when I hold down Vol-Up, Power and Home but when I try to reboot, it tells me there is no OS installed. I can't even use the recovery option, since I believe I deleted all the previously installed recoveries.
I feel silly for being in this predicament, but I would be so grateful for any help, folks!
-New2S7
Click to expand...
Click to collapse
Hello, no need to panic, the blue circle over the line was Lineage first boot up, it can take 10-15 mniutes on the first time. If you waited longer than this then maybe there was a problem.
If the Lineage ROM is on your SD card you can try to flash it again and see if it boots this time, sometimes it needs to be flashed twice to work. You must make sure it's the right one for your device.
If it still doesnt work then you will need to flash the stock firmware back to your device with ODIN. This is the firmware for your device >>>>HERE<<< Pick your network provider or an "unknown" version which is unbranded stock firmware. The download is a little slow but it's free.
There's lots of guides how to flash firmware with Odin, it's very easy.
I forgot to mention TWRP is a much better Recovery Option so yes when you instal TWRP the stock recovery won't boot.
cooltt said:
Hello, no need to panic, the blue circle over the line was Lineage first boot up, it can take 10-15 mniutes on the first time. If you waited longer than this then maybe there was a problem.
If the Lineage ROM is on your SD card you can try to flash it again and see if it boots this time, sometimes it needs to be flashed twice to work. You must make sure it's the right one for your device.
If it still doesnt work then you will need to flash the stock firmware back to your device with ODIN. This is the firmware for your device. Pick your network provider or an "unknown" version which is unbranded stock firmware. The download is a little slow but it's free.
There's lots of guides how to flash firmware with Odin, it's very easy.
I forgot to mention TWRP is a much better Recovery Option so yes when you instal TWRP the stock recovery won't boot.
Click to expand...
Click to collapse
Hello cooltt,
I was able to fix my problem an hour or so ago, but thank you for your calming post anyway.
For future threads, here is what I did:
1. I downloaded a stock OS and then extracted all the md5 files. (There is an md5 file for the "BL", "AP", "CP" and "CSC" fields in Odin.)
2. I then used Odin and after it detected my device, I plugged the 4 files in the appropriate fields.
3. I then hit start and it restored my phone back to a functional state.
Though I spent the last 20ish hours in a panic, I actually managed to achieve the goals that prompted me to try and install a custom rom: fewer stock apps and no Samsun Account bothering me all the time.
Thank you all for your concern.
-New2S7
(P.S. I do not know how to mark this as solved. If an admin comes across this, please mark this as solved!)