Related
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
jimmydafish said:
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
Click to expand...
Click to collapse
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
minitele said:
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
Click to expand...
Click to collapse
you should join the G+ community for much better and more pointed help. The forums get cluttered.
1) download correct 4.2.2 (57-1) FXZ file
2) extract boot, system, recovery from the file
3) fastboot flash each of the partitions to your phone
(fastboot flash boot boot.img)
(fastboot flash recovery recovery.img)
(fastboot flash system system.img)
Doing this will put your phone in a state where it is ready to update.
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
jayboyyyy said:
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
Click to expand...
Click to collapse
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
jimmydafish said:
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
Click to expand...
Click to collapse
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
jayboyyyy said:
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
Click to expand...
Click to collapse
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
minitele said:
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
Click to expand...
Click to collapse
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
jayboyyyy said:
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
Click to expand...
Click to collapse
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
minitele said:
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
Click to expand...
Click to collapse
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
jayboyyyy said:
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
Click to expand...
Click to collapse
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
minitele said:
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
Click to expand...
Click to collapse
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
tracyde said:
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
Click to expand...
Click to collapse
To all,
The forums and people in our arena never fail, fastboot erase cache worked perfect. I have recovered all my data and now I will definitely continue to performing a full recovery with stock image.
Thank you again all for all of your help, I am glad to see at least this corner in the internet still is alive and kicking!
I just successfully downgraded from COD6 back to NK4 in order to alleviate concerns that downgrading back to Kit-Kat was going to be an issue. Reference post found: HERE. I am outlining the method I used to downgrade below, but this can also be a guide on how to upgrade to later firmwares.
I don't recommend trying to downgrade past NK4 and only downgrade if your dev says you need to! downgrading is risky and can brick your device! You've been warned!
Downgrade to NK4 or Upgrade to COD6
1.) Download Odin v3.09
2.) Download full Odin NK4 (Found HERE) or COD6 found, almost everywhere
3.) Unzip the file and there should be a file called "N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5" or your COD6 tar called, "N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5"
4.) Open Odin v3.09 and click the button labeled "AP" and locate the tar file you unzipped
5.) Let it load, it will freeze for some time while checking the MD5 and then be ready to go
6.) Turn off your phone completely; after it is powered off hold vol down+ home + power until you see a warning message
7.) Hit Volume up to continue
8.) Plug in your device and and the it should light up blue under "ID:COM" and say something like "COM:1"
9.) Check to make sure your tar is loaded into the AP slot.
10.) Ensure that they only two boxes that are checked are: "Auto Reboot" and "F. Reset Time"
SHOULD LOOK LIKE THIS PHOTO: http://cdn.droidviews.com/wp-content/uploads/2013/05/galaxy-s4-odin-flash.jpg
11.) If you've verified that your Odin looks like the picture then click "Start" and be patient
*****************************************************************************************************************************
***If Downgrading You MUST wipe USER DATA following the steps below or your phone will boot loop on restart!***
***If Upgrading I Strongly Suggest wiping USER DATA to avoid potential issues from upgrading!***
*****************************************************************************************************************************
12.) Wipe User Data as outlined below by booting into recovery as soon as the download completes by holding power + volume up + home until it says, "Recovery booting" in blue in the upper left corner.
13.) After doing the factory reset and rebooting it will you can setup your phone like normal
These are the same steps if you want to upgrade with Odin, you just use the full tar of the upgraded firmware (COD6 in our case)
To Wipe User Data
1.) After you've clicked start and the file completely loads on your phone it will reboot and immediately enter recovery
2.) It will show and Android and a blue bar scrolling across setting up your system. It will reboot again after this
3.) As soon as the screen turns black hold vol up+ home + power to enter recovery again
4.) It will boot to the Android again and you should see THIS before the menu loads
5.) Scroll down to "factory reset/data wipe" with the Vol Down button and then hit the power button to select it
6.) Scroll down again and hit "Yes" so that it completes
7.) After it is done reboot and allow your phone to boot normally
8.) Setup your phone like normal
Done!
I vote for this to be a "Sticky".
Good job :good:
Thank you, I've been with 5.0.1 for the day and the battery was better on 4.4 and it looked better. I was going to try as soon as I got home but now I know.
I was googling how to downgrade and ran in to this. A lot of report saying it worked. I'm surprised this is possible with Odin. Thanks for the additional confirmation.
Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.
aznmode said:
Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.
Click to expand...
Click to collapse
I know it was a long time ago when you posted this, but it just now sank in that boot loop = bad
I will update the OP, thanks for pointing this out :good:
Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...
CtJackHarkness said:
Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...
Click to expand...
Click to collapse
Because doing an Odin upgrade or downgrade on your device does not wipe the data partition which is necessary when changing a letter versions of Android. For example, let's say you are going from Kit-Kat to Lollipop or perhaps Lollipop to Kit-Kat in a way similar to that presented in this "How to".
However, I get that new members need help sometimes so let me help you research your criticism.
Welcome to XDA.
Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.
KingBeef said:
Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.
Click to expand...
Click to collapse
The reason OTA and Kies don't do the reset themselves is because they aren't capable of backing up the data you've accumulated on your phone since you've owned it. The average user only get an icon in the upper left-hand corner that tells them to update and they do it because T-Mobile says so. Imagine that same user installed the update and then they were looking at the Lollipop welcome screen like they had just taken the device out of the box. It would lead to an outcry from consumers because they lost months of data from the upgrade. However, we here on XDA are not average users and some of us know exactly what happens during these updates. You probably don't remember this, but there was a time when Odin wiped your phone automatically even on incremental updates. Because just like flashing a ROM, clean is the only way to truly ensure that residual files are not causing problems. But they eventually removed this behavior in later releases of Android. I don't know why this was done, I am only able to tell you the history of Odin as I know it. However, because Android changes have been so drastic lately (locked SD cards, addition of preload partition, removal of preload partition, SELinux policy updates, institution of Knox and protected files, etc etc etc.) not starting with a clean slate led to a myriad of problems for users. If you need specific examples just look at the Galaxy S5 Wi-Fi issues from taking the Lollipop OTA without doing a factory reset. If you format your hard drive before installing a new version of Windows then you should be capable of understanding why clean partitions for an OS upgrade makes sense. But you don't have to take my word for it, click the link I left with CtSomethingOrAnother up there. People almost unanimously support a factory reset for major upgrades. So you can take my advice or follow your own, but I promise that I'm going to get plenty of sleep tonight regardless of what you decide to do with your phone. You have to realize that I am giving advice as a senior member of a respected development community where new members come for answers. I make sure that I am giving them the best advice that I could possibly give them with my experience on these forums and with Samsung devices. If users decide to cut corners after knowing the proper way to do it, that is on them.
tl;dr -- I wrote this Howto so that I could help people; not waste their time. You don't have to believe anything I wrote above. In fact I encourage you to research this information yourself and come to your own conclusions about why factory resets are necessary. Until Google goes on record saying, "No more factory resets for upgrades" I'm going to keep my advice just the way it is written.
I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.
I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)
KingBeef said:
I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.
Click to expand...
Click to collapse
To me, the why is always the most important part. When someone posts a flashable file to fix a problem I open it up to see what it is doing. It took a lot of reading and some prior experience with Linux to be able to grasp a lot of what Android developers are doing when they change the files
CtJackHarkness said:
I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)
Click to expand...
Click to collapse
I truly don't understand how you could acknowledge that skipping the factory resetting could lead to problems for people but that you don't recommend it because people should just use it until they have a problem and then wipe all their data at that point. And as far as "everywhere online this is the case", I literally Googled for you tons of links with people saying to factory reset for Android upgrades and you're choosing to ignore the information. That's on you. As far as CDMA phones having to be re-activated? It's been years since I used a device on Sprint and doing a factory reset on Android led to the device activating itself. It isn't an issue, it's just part of the setup process. It's no different than updating the PRL and Profile on Sprint (CDMA) once a month to ensure roaming capabilities are working at peak efficiency. Verizon customers used to have to dial a number to update the PRL but now on Android it happens in the background just like it would during setup.
However, changing your mind isn't my job nor is it how I intend to spend my time on here. You can do whatever you wish with your phone and what I wrote is exactly how I handle my phone. I'm leaving your criticism and my responses in this thread for people who want to hear both sides and hopefully that will accomplish what you set out to do by posting here in the first place. If you still aren't satisfied, please take it to PM.
EDIT: Nevermind, I went back and edited the post to clarify that boot loop happens on downgrading and encouraged people to wipe user data while upgrading.
This method worked for me..
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html
hacker904 said:
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html
Click to expand...
Click to collapse
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/
Internal data
v2.2v said:
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/
Click to expand...
Click to collapse
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?
hacker904 said:
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?
Click to expand...
Click to collapse
Hey bud. and this by no means is trying discredit you, but the OP works just fine. Just did it. Odin 4.4.4 and wipe data after.
@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one
Santos89 said:
@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one
Click to expand...
Click to collapse
I guess tmobile changed some security policy that blocks phone users from downgrading.
Source:
http://forum.xda-developers.com/showpost.php?p=64548030&postcount=5
downgrading from cod6
Has anyone confirmed that you cant downgrade from Cog6? I am on one of the 5.1.1 ROMs I tried downgrading to 4.4.4 using ODIN but it keeps failing. Has anybody had any success with this?
Hello, I'm new here.
I have a problem.
I forgot the PIN lock of my SM-G360F LTE (with Android 4.4.4), and I would like to keep all my files & documents inside it.
I don't have USB Debug enabled and I don't have a Samsung Account, so there's no easy way I can connect the phone to a computer.
What can I do to save my datas?
I've already tried flashing a Custom Recovery with Odin, but I haven't found a compatible one.
Please, give me an advice on what I should do.
Not sure if this will work for your version but it can't hurt to try. It worked for my stock unrooted SM-G360T1
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page4
Let me know if this works for you
hatchet13rydin69 said:
Not sure if this will work for your version but it can't hurt to try. It worked for my stock unrooted SM-G360T1
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page4
Let me know if this works for you
Click to expand...
Click to collapse
It doesn't work (or I'm missing something) just because I can't unlock my screen lock to install the APK.
If I'm missing something, please tell me.
What I'm looking for is a way to enable USB Debug mode without unlocking the screen (something like a Custom Recovery mode).
Read the entire post including he comments cuz that link I posted is a step by step guide to unlocking the phone. If the phone has not been factory reset yet then do that first so it causes the phone to go to the Google email verification page then follow the in the link step by step and you will have the phone unlocked. What you are doing with this guide is making a custom path to the settings menu for the phone enabling you to do a factory reset from the backup/reset setting. By doing so you will remove the link to any and all accounts that have been uses on the phone this making the device start just as it would had you bought it from the store and was doing the initial setup. Let me know if you get stick anywhere or need help
hatchet13rydin69 said:
Read the entire post including he comments cuz that link I posted is a step by step guide to unlocking the phone. If the phone has not been factory reset yet then do that first so it causes the phone to go to the Google email verification page then follow the in the link step by step and you will have the phone unlocked. What you are doing with this guide is making a custom path to the settings menu for the phone enabling you to do a factory reset from the backup/reset setting. By doing so you will remove the link to any and all accounts that have been uses on the phone this making the device start just as it would had you bought it from the store and was doing the initial setup. Let me know if you get stick anywhere or need help
Click to expand...
Click to collapse
But if I factory reset my phone, I will lose all my data, which I don't want to. Or via this "Backup/Reset" setting am I keeping my data?
Sorry for all this questions, but I'm pretty confused...
You will lose your data as this is the master factory reset but you can back up everything while in this menu to your Google account. After you factory reset go through the initial setup and come back to this menu and restore from your Google account
Can I backup my photos, music, documents etc. on my Google account? And how do I do it before resetting the phone?
sfn1701 said:
Can I backup my photos, music, documents etc. on my Google account? And how do I do it before resetting the phone?
Click to expand...
Click to collapse
Check out this guide here on lifehacker...
https://lifehacker.com/5976036/simp...droid-phone-from-the-desktop-no-root-required
Works great and doesn't require root to get it done. I know it is a lil different from what I mentioned earlier but I totally spaced this method until earlier today. Hope this helps you.
Man, my main problem is I can't enable USB debugging, having the screen locked! So I can't use any ADB method.
As far as I know there is no other way to backup your data without using adb methods without a custom recovery. Have you tried flashing twrp for your device and doing a full nandroid that way? I know that twrp has a compatible version for your device. Just search the forums here for you specific device model and flash using Odin 3.10
Here is the link to the twrp website go here to make sure you model is supported then download the tar.md5 file for tour device and flash using odin. Make sure to Uninstaller lies from your pc to avoid any issues with odin
http://twrp.me/
I had already tried flashing twrp, but when I tried to boot in recovery I did get a Bootloop and the "Recovery is not seandroid enforced" error.
sfn1701 said:
I had already tried flashing twrp, but when I tried to boot in recovery I did get a Bootloop and the "Recovery is not seandroid enforced" error.
Click to expand...
Click to collapse
Are you using the hardware keys to boot to recovery (volume up+home+Power buttons)? If you try to boot to recovery from any other method it will cause a recovery loop. It's a known issue with all variants of this divice. It's gonna show the "Recovery is not seandroid enforcing" but it will go into recovery.
Of course, I'm using Home+VolUp+Power.
Im out of ideas outside of trying to flash twrp again through Odin
sfn1701 said:
I forgot the PIN lock of my SM-G360F LTE (with Android 4.4.4), and I would like to keep all my files & documents inside it.
Click to expand...
Click to collapse
You can just try reflashing the stock firmware for your region in the AP slot of Odin from here.
http://sammobile.com/firmwares/database/SM-G360F/
It should keep all your data while it resets everything else like new.
bogarty said:
You can just try reflashing the stock firmware for your region in the AP slot of Odin from here.
http://sammobile.com/firmwares/database/SM-G360F/
It should keep all your data while it resets everything else like new.
Click to expand...
Click to collapse
But will flashing stock firmware remove the frp lock? Sorry still a lil new to all this and just trying to gain knowledge of everything I can.
hatchet13rydin69 said:
But will flashing stock firmware remove the frp lock? Sorry still a lil new to all this and just trying to gain knowledge of everything I can.
Click to expand...
Click to collapse
Yes. In fact, if you've tripped factory reset protection (FRP), it is the only way to fix it. Here's an example of where this worked for someone else. Read my comment here:
http://forum.xda-developers.com/showthread.php?p=65016084
Then also read the response that follows. Use the correct firmware for your device though at the link i gave above.
bogarty said:
Yes. In fact, if you've tripped factory reset protection (FRP), it is the only way to fix it. Here's an example of where this worked for someone else. Read my comment here:
http://forum.xda-developers.com/showthread.php?p=65016084
Then also read the response that follows. Use the correct firmware for your device though at the link i gave above.
Click to expand...
Click to collapse
I followed this guide here earlier his year and it worked without any problems
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page1
I'm still using the device that I used this guide for. Have recently rooted and installed twrp. Going to flash slimpickens rom later tonight
hatchet13rydin69 said:
I followed this guide here earlier his year and it worked without any problems
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page1
Click to expand...
Click to collapse
I understand that that guide has helped people and that's a good thing for sure. It's just that it's really the absolute most difficult way to fix a device that's under an FRP lock, as it's many steps rather than just the one step of flashing the stock firmware.
bogarty said:
I understand that that guide has helped people and that's a good thing for sure. It's just that it's really the absolute most difficult way to fix a device that's under an FRP lock, as it's many steps rather than just the one step of flashing the stock firmware.
Click to expand...
Click to collapse
I appreciate the help and insight. Will definitely keep this in mind in case I ever run into this problem again.
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Did you verify the checksum of the image prior to executing the flash-all script?
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
I don't use flash all script. I flashed each img individually like it's posted in the guide
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
Yes the checksum was verified
XMayhem2099 said:
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Click to expand...
Click to collapse
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
v12xke said:
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
Click to expand...
Click to collapse
Did both still the same bootloop
XMayhem2099 said:
Did both still the same bootloop
Click to expand...
Click to collapse
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
v12xke said:
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
Click to expand...
Click to collapse
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
XMayhem2099 said:
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
Click to expand...
Click to collapse
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
v12xke said:
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
Click to expand...
Click to collapse
I did the flash all command it ran successfully. Looks like im still getting a bootloop. I'll let it sit for an hour or so. If it doesn't run ill flash an older factory image. Thanks for the help, Ill let you know what happens.
Mine started doing the same thing last night, so far nothing I have tried has worked. Wireless provider is no help maybe Huawei will replace.
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Sent from my Nexus 6 using XDA-Developers mobile app
CyberpodS2 said:
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Click to expand...
Click to collapse
Huawei seems to have done a crappy job manufacturing them. Mine bootloops every time I update to a new ROM build, every time I switch ROMs and every time I try to restore a backup. Thankfully I've been able to get out of it every time so far but I've owned a lot of phones and none went into bootloops as often as the 6P. I've resigned myself to the fact that this phone is a time bomb and that it likely won't have a very long life. Would never buy another phone made by Huawei.
Problem google and hawuei (hardware) RMA
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
fapste said:
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
Click to expand...
Click to collapse
1. In general or when it happened? Averaged 4 hours SOT in 14-16 hours total.
2. 128 Toshiba
3. 3-29-2016
4. No
5. No
Same issue on a buddies 6p.. Fastboot commands go through the script with no errors but no results.. Still stuck in this bootloop. Has to be hardware causing this bootloop.
I'm having the same issue
Sent the device to Huawei and they say they'll repair it but I'm not sure if that's possible
My question is when they replace them, is the defect still waiting to pop up again??
Sent from my Nexus 6 using XDA-Developers Legacy app
Bought 2nd hand phone, managed to coax original sales receipt from Google store out of seller. Sent it in for an RMA and they swapped out my motherboard. Was also out of warranty by 2 months
My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.
Lare2 said:
My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.
Click to expand...
Click to collapse
Call the hotline support phone number at the bottom of the page you bookmarked. If your phone has boot loop of death Huawei likely can't tell what you did in terms of rooting. If the phone still works well enough that you can flash the full factory image then you should. My understanding is that unlocking the bootloader doesn't void the warranty on Nexus devices.
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Depending on where you are located Huawei might point you to a local service center rather than have you mail in the device. Huawei contracts with some phone repair chains.
The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.
Lare2 said:
The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.
Click to expand...
Click to collapse
Did you try flashing the full factory image with fastboot?
jhs39 said:
Did you try flashing the full factory image with fastboot?
Click to expand...
Click to collapse
Yes I did, using the flash-all.bat as per instructions and it succeeds without issues. But as soon as you restart the device and gets to the Google logo, it restarts again and again and again up to the Google logo and never past from there
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
I downloaded the Unified Android Toolkit.
I tried following this instructions
FLASH A STOCK IMAGE BACK TO YOUR DEVICE [FIXES NEARLY ALL PROBLEMS]:
1. Unplug the usb cable
2. Reboot manually to Fastboot Mode [see above for button combination]
3. Plug the usb cable back in
4. From the Toolkit Main Menu select option 9,1 to download/flash a stock firmware
image back to your device. Choose to format userdata and is should fix everything.
Mentioned on this Url
But I can't see and option for 9. When I initially open it it asks me to select the device and then asks me to choose the Android version to go but never see that option 9 mentioned above.
Can you guide me to the steps you followed to fix yours
TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2
v12xke said:
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2
Click to expand...
Click to collapse
Well, for anyone scrolling through here. This is how my device semi-hard bricked (after not booting)
I was flashing PureNexus (I've been using it since I got my 6P in April, it was a standard update to me). I was going from November build to January build, and I thought nothing of it. Next thing I know my phone isn't booting, so I try flashing again. I realize I'm stuck so I backup all the stuff that isn't already backed up, and I wipe everything. Flash stock from my computer. Welp looks like that didn't work. So I go through and format everything before trying again, still. No luck. Vendor refused to flash at that point, so vendor had gotten corrupted in the process ( I kept on getting invalid directory for /vendor - weird right?). Or a string of complex errors in fastboot. I saw something earlier while I was helping someone, about the took. I usually like doing things myself, but I used it as a last resort. I flashed back to stock and everything worked. Then I flashed PureNexus again, and had to do the toolkit all over again. Because my phone absolutely refused to boot on December PureNexus for the angler.
TL;DR : I would not recommend flashing the December update of PureNexus at ALL
I have been trying to get it to work with all the suggestions mentioned here sin my last post. No luck at all. I'm in the process to call the warranty support number and will se how it goes.
Even though I have been unable to get it working this has been an amazing learning experience. I got to try several solutions that made me gain more knowledge that I know will be useful in the future.
I'll report back to see how it went with the warranty guys.
Thank you all