Related
Hi Folks,
I have experienced the sadly famous boot loop issue (the one that keeps the device on the boot screen forever), not in one, but in two different devices (same model and build, 4.0.2 GSM - ICL53F).
I fixed the first one by flashing the latest stock rom (4.0.4), but of course it lost all the data, including camera pictures.
So for this one, I would like to save as much as I can. The problem is, that I can't access the device with adb since it wont boot, I just can access it with fastboot.
I have managed to enter the ClockWorkMod Recovery and perform a backup, but it saves it into the sdcard, so if I flash the phone to fix it, it will lose the backup
So, the question is: How can I either access the filesystem trough fastboot or just performing a backup that won't be lost if I have to flash it.
Thanks in advance
You said you can access ADB...but I assume you meant can't?
If you can...
http://forum.xda-developers.com/showpost.php?p=24910351&postcount=21
And pull your sd card as well.
If not...
I assume you've tried booting into bootloader and odin?
Jubakuba said:
You said you can access ADB...but I assume you meant can't?
If you can...
http://forum.xda-developers.com/showpost.php?p=24910351&postcount=21
And pull your sd card as well.
If not...
I assume you've tried booting into bootloader and odin?
Click to expand...
Click to collapse
Your assumption is right, I can't.
And yes, I tried booting trough odin and bootloader, many times, but I have read about many people experiencing this issue, most of them solved it by wiping data (and some also flashing). I know how to solve the booting issue, I just want to save as much data as I can.
mdelolmo said:
Your assumption is right, I can't.
And yes, I tried booting trough odin and bootloader, many times, but I have read about many people experiencing this issue, most of them solved it by wiping data (and some also flashing). I know how to solve the booting issue, I just want to save as much data as I can.
Click to expand...
Click to collapse
No I understand man.
The link I gave would back up your apps at least...
And your SD if you changed -noshared to -shared but I haven't had much success.
But you'd need ADB access.
Wait for another opinion if you wish.
But I'd assume you need a factory reset if you can't get ADB...
And simply flashing a rom doesn't work, right?
mdelolmo said:
Hi Folks,
I have experienced the sadly famous boot loop issue (the one that keeps the device on the boot screen forever), not in one, but in two different devices (same model and build, 4.0.2 GSM - ICL53F).
I fixed the first one by flashing the latest stock rom (4.0.4), but of course it lost all the data, including camera pictures.
So for this one, I would like to save as much as I can. The problem is, that I can't access the device with adb since it wont boot, I just can access it with fastboot.
I have managed to enter the ClockWorkMod Recovery and perform a backup, but it saves it into the sdcard, so if I flash the phone to fix it, it will lose the backup
So, the question is: How can I either access the filesystem trough fastboot or just performing a backup that won't be lost if I have to flash it.
Thanks in advance
Click to expand...
Click to collapse
You cannot backup through fastboot with a shipping bootloader, but you can access /sdcard via adb when booted in CWM, despite not being able to connect when booted normally.
1) Boot into CWM.
2) Connect to a PC.
3) Open a command prompt in the same directory where you have your adb.exe file.
4) Type: adb pull /sdcard/
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
Hello,
I am a happy owner of OnePlus 3 and at the beginning when I got this Smartphone and run it, I had to set-up a Pin which was also used for Encryption,
due to the decision that I wanted to change it, I have tried numerous things to do this, either via System -> Security, System -> Lock Screen or TWRP Recovery.
Then I have stumbled upon a wiping feature in TWRP. (TWRP Menu -> Wipe) where there was a couple of options like Advanced Wipe, Format Data and Swipe to Factory Reset. So I have
decided to see what Format Data does which showed me the following statement before I continued with it "Format Data will wipe all of your apps, backups, pictures, videos, media and
removes encryption on internal storage". Well when it said it removes the encryption I have proceeded because at this point where all of the methods failed I wanted to remove and
re-encrypt my OnePlus 3 again in order to change my encrypting pin. Ok, cool this worked perfectly except that now I can't restore my original rom or encrypt my OnePlus 3 again ....
Then I have flashed CyanogenMod 13 Nightly from August (The latest one on the CyanogenMod website) and when I went into System -> Security there was Encrypt button instead of saying
Encrypted at the top of the menu then I have played around with setting up a new Pin/Password and when I went throug all the process at the end the following happens within a few
seconds: a green dissasembled android shows then screen turns black and returns to lock screen. I checked if OnePlus 3 is encrypted and is not. This is not the normal as usually
encrypting takes some time.
Also, I have tried to restore my original rom which came with my smartphone and was encrypted, when I restored it, OnePlus 3 stucks on the first screen showing OnePlus logo on the
middle of the screen and text "Powered by Android" on the bottom of the screen.
I presume that CyanogenMod 13 encryption is broken or that I shouldn't have format Data ?
Is there any way that I can encrypt my smartphone again ?
P.S I know that OnePlus 3 encryption is handled by Hardware.
You can try downloading the official OxygenOS ROM, flashing it and trying to encrypt again. Last I tried doing it on Sultan's CM13, it didn't work, so it might be a CM problem.
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
abhibnl said:
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
Click to expand...
Click to collapse
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
formating data with TWRP -28 will decrypt your phone, it's madethis way so it can work on beta 9 and f2fs ...
that said i had encrypted device before on CM
so if you're not using beta 9 and your data partition is not f2fs, you can have an ecrypted device, the easiest way is to sideload official rom 3.2.8 (make sure you're on stock recovery and start adb sideload from there) , after the sideload the phone will be encrypted, if you're staying at MM, fastboot TWRP .22 or 23 or just the official in case .28 decrypts the phone.
Gliop022 said:
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
Click to expand...
Click to collapse
Well man i want you be on as much safe side as possible. When you perform factory data reset on stock recovery, it will wipe and reformat your internal memory as well. TWRP only wipes data partition, and you need to format whole internal memory manually. But stock is recommended for full compatibility.
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Gliop022 said:
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Click to expand...
Click to collapse
Hello Gliop022,
Do you know if flashing OxygenOs stock from TWRP 3.1.0 encrypts the phone or do I have to be on stock recovery?
Then once the phone is encrypted, are you able to flash an OOS based ROM (e.g. FreedomOs) and keep the encryption?
Hey everyone,
I recently installed a new ROM, but now my phone and TWRP is asking me for a password. I never set one, I did recently setup a pattern but I'm not able to input a pattern in TWRP or after Google logo goes away and I'm asked for a password.
I did create a nandriod but cannot get to it. If I ADB to the TWRP location I get access denied. If I use TWRP to to restore the backup I get access denied.
Any idea how to pull the nanriod backup from my phone or bypass this encryption on TWRP? ANy help would be great.
I already installed factory system, boot, recovery but that made things worse. I don;t even get past the GOOGLE logo anymore. I know I need to format userdata at this point but I really need to pull that nandriod off of it.
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Simone98RC said:
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Click to expand...
Click to collapse
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
nikexv2 said:
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
Click to expand...
Click to collapse
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Xceeder said:
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Click to expand...
Click to collapse
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Come on, do not vent on XDA, do not make useless quarrels ?
@nikexv2 sorry, but technically speaking, I don't know the reason of problematic encryption on custom roms.
Just enable encryption with official firmware and there's no other compatibility issue.
Encryption still remains when you full wipe device via recovery.
Have a good day.
nikexv2 said:
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Click to expand...
Click to collapse
It works like this - you ask for help and if someone gives you good advice or helps you out in any way then a quick thumbs up is appreciated , it's just courtesy but anyway I hope you get your phone sorted out ...
nikexv2 said:
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
Click to expand...
Click to collapse
Not sure what's wrong with your set up but I came from OOS OB19 to DU, wiped userdata to switch data to ext4, flashed DU + beans gapps (recommended for DU) then booted up, encrypted my phone via Settings > Security and set ask pin on booting device, same pin has worked on all ROMs, even tried some OOS based ones like Freedom OS CE, now on Omni + open gapps, I'm using blu spark latest recovery.