Related
alright i have this problem and i am quite panicking now.
i will set everything straight , i hope someone reading the forums can help me asap !
- have a sgs2 unbranded (hk)
- has ICS 4.0.3 stock rom, rooted.
- i don't remember if usb debug mode was enabled
- i messed up in some way with the file /system/build.prop but there is a backup in /system/ called build.prop.bak
- phone doesn't boot anymore as it's stuck at the logo
- recovery and download modes work however
#need a way to delete the build.prop and replace the bloody file with the one backupped. I would like to avoid having to format the phone as i do not remember when was my last kies backup...
what i tried:
-adb shell: it doesn't work. for some stupid reasons the drivers won't be recognized (i have download android sdk and usb drivers), but when i plug the phone in recovery windows just says Device Unknown and even if i update drivers manually it would say that current ones are functioning so no need to update.
if i connect the phone to usb while it's stuck at boot logo, it would recognize the device through samsung drivers (except MTP of course, that would give error).
in both cases adb shell doesn't list any connected device: even if i kill-server and start-server it still doesn't list anything.
-tried using droid explorer in both frozenboot mode and recovery mode, doesn't see anything.
-tried using that other program called SuperOneClick or something like that, that has a "check drivers" button in advanced: if the phone is in recovery pressing the button doesn't do anyhing; if the phone is in frozenboot it asks to download and install some drivers but when i press yes a message appears with " no more data is available " !
i tried this procedure on both win7x64 and winXPx86: same results. reading around , someone says that adb shell will never work if usb debug is de-actived, like i said i cannot remember if that's the case.
-zip package: i created a package to try and overwrite the file with a custom working one i got. i put the package in the root of the micro sd , put the sd in the phone and booted in recovery.
but when i am in recovery the bloody CWM 5.0.2.7 says error to mount /sdcard, or E: could not mount /sdcard , same if i try to mount/unmount /sdcard. if i go to mount external usb card or whatever it says that a file or a lib (cant remember the exact message) was not found.
i have no more ideas of how to solve this, please be patient :<
edit: is there a way to soft format the system folder so that i don't have to properly wipe all my user data and it only affects the system without other contents?
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
bala_gamer said:
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
can you expand on this?
give any suggestion/example?
isn't there a soft temp rom for emergencies like this that you can just start, make modifies to fix and reboot (similar to the process to boot ubuntu on windows, fix issues and then restart normal windows? )
i would so like to make adb work.. but how.!!!
probebly will not work but try backing up of your ROM from CWM working or not..then just back up current one...
you can restore apps & data lateron from nandroid backup with some application like titanium backup donated version.
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
-marco- said:
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
Click to expand...
Click to collapse
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
zaheedahmed said:
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Click to expand...
Click to collapse
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
mljjlm said:
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
Click to expand...
Click to collapse
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
-marco- said:
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
Click to expand...
Click to collapse
you try to reflash once more CF-Root (.TAR)only from odin
then check "E: cant mout...error" is rectified or not.... also check booting or not,
still no hope...you flash the same firmware again and Cf-root, your SD card data will be there for sure as far as our expereicne till now..
first part of your comment: i tried reflashing the kernel; no changes. same errors
second part: shall i try using the same firmware from my previous post then?? not other roms? after that i will put the root and check if internal memory is still there. if it is i will copy it on my hd and restore.
if it is not there anymore..............
so the end of the story.
thanks to anyone who helped.
the resolution was much easier than everything else.
opened odin, pda loaded my same firmware which was the HK stock update to ICS and reflashed.
what it did was apparently and overhaul of the system folder, that's it.
any data was still there, as well as the backup that i did and all my apps etc etc etc.
however especially at first it looked a bit unstable, with processes failing randomly. now it seems it has stabilized a bit, but still when i try to run a Kies backup, the phone kies process dies and the backup gets stopped.
i still don't know how to fix this, but i'll be looking into it.
so, the morale out of this was at least for me: if there is some **** up within the system folder just reflash the same rom installed. i feel so stupid now for having made such a fuss when the solution was so easy and straightforward
NICE that you finaly came across and able to boot , now you make the Titanium back of your all apps and data transfer to PC....forget the system data.
and move to a nice stable ROM
"Unfortunately, wssyncmlnps has stopped"
anybody knows about this?
Hi all.
I've just installed some app that broke down my S3 stock OS.
The OS was rooted, and I gave the crappy app superuser access...
It was supposed to change the DPI setting, but now it's boot-looping over the Samsung logo.
Now I'd like to recover my data, photos and stuff...
CWM Recovery 5.5.0.4 is installed.
I can start a backup, but it won't complete since I don't have a large enough SD card at hand (it's a 32 GB SGS3 with a bunch of large videos...).
I don't care about the movies, just the photos, but there's no option for a selective backup...
I also tried updating CWM to a more recent release with Odin (downloaded .img and tar'ed it...), but it won't go further than SetupConnection.
I've not tried a factory reset of anything else yet...
Is there a way I can still recover my data, or should I just get over it and try to flash the whole thing back with Odin?
Thanks for your help.
Adb backup?
maybe reinstalling the ROM can fix it ?
The other thing you can try is adb pull /build prop, edit LCD density back to 320 and adb push it back
Thanks for your answers.
adb looks like the way to go, but I never managed to get it working on my computers.
"adb devices" won't list any, "adb shell" returns "error: device not found".
USB debugging was enabled in the OS.
Is the phone supposed to be in recovery mode or download mode? None works... (Also tried with the OS running before it started crashing)
Is there a setup guide somewhere?
Actually, working with Android on Windows (XP x64) has been a total nightmare so far.
On my main computer, Device Manager loops forever on device detection / driver installation, and successive driver installation/uninstallation/reinstallation mangled WMP10 completely (and since it's tied to Windows, I can't reinstall it).
On other computers, driver installation went fine, I hardly managed to copy movies to the phone through MTP / WMP, and never managed to copy anything back.
I only ever managed to move files over wifi, but that's at wifi speed, not USB2 speed...
And now that I gave Kies a try (stayed away from it so far), it keeps eating 100% CPU whenever I run it.
I had that adb problem then I installed android command centre, and bam, it worked! Will try and find link for you....brb
Finally managed to run adb on the computer with Kies installed.
I'll look into this.
Here go
http://forum.xda-developers.com/showthread.php?p=36671130
Can't use adb pull/push anymore: in a previous attempt to reduce the nandroid backup size, I formated the system and cache partitions.
Then I managed to run a full backup with CWM Recovery, but can't find my files in there.
The backup files only contains application data, but the sdcard folder is totally missing.
Well, it appears the problem indeed was in build.prop.
My backup has 2 files: build.prop.bak and buid.prop.temp.
.bak has the old density, .temp has the new value.
Somehow the app failed to rename build.prop.temp to build.prop, and made the system unbootable.
adb backup won't work either: it's waiting for a confirmation on the phone, and doesn't seem to work in recovery mode.
Now browsing /data/media with adb shell !
I had to mount /data manually (in recovery), I guess the same is true for a recovery backup, and that's why I couldn't find my files.
Think I'll manage to get it all back now.
Thanks a lot slaphead20.
I was just about to wipe away all these family pictures!
Nico57m said:
Now browsing /data/media with adb shell !
I had to mount /data manually (in recovery), I guess the same is true for a recovery backup, and that's why I couldn't find my files.
Think I'll manage to get it all back now.
Thanks a lot slaphead20.
I was just about to wipe away all these family pictures!
Click to expand...
Click to collapse
FYI TWRP will not wipe ur sd when u do factory reset
but ur problem not with data its with system and u can fix it simply by reflashing the u r using without any wipe
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
Hi,
I'm new to this forum and a beginner to learn about android devices. I have a Gionee E3 android device (Asian version - English) with Android 4.2.1 on it. Unfortunately I have forgot the pattern lock and to make matter worse the following problems are also included -
1) No root - the device is not rooted
2) No USB Debugging
3) No custom recovery (I guess, only (stock recovery), Android system Recovery is displayed when tried pressing volume + and power key combination )
4) No wi-fi or mobile data could be enabled as the lock won't allow even to slide the screen from the top to get quick access to these things.
5) Windows Xp on my pc
I have tried the following -
1) ADB method to delete the gesture.key, but as the device is not rooted, failed with this attempt with several errors.
2) Tried from Cygwin, but the SU command gave error - -bash: su: command not found
3) Tried Aroma file manager zip file from Android system recovery ----> apply update from SD card, returned error - Installation aborted. Tried to resolve by fixing the updater script file through Notepad++ with different versions of Aromafm but nothing works.
4) Tried with several pattern cracking software .zip files through Android system recovery ----> apply update from SD card, still getting error - Installation aborted.
Kindly help me to recover my data intact.
Don't want to root the device and there may be the risk of wiping the data off.
I have also tried to backup from Android system recovery ----> backup user data and 300 MB of data has been backup on SD card. Does this include SMS and phone contacts too with whatsapp data also?
Thanks in advance and sorry for long description, just wanted to make sure you guys know all the things I have tried. Your help will be greatly appreciated.
Sam
This phone is really starting to piss me off. I lost all of my data two days ago when a TWRP backup didn't save my lock screen pattern, and now I can't even properly get into TWRP.
What do I do?
So I did some searching. I bypassed the password (losing all of my data again) and did a Format Data. Got through the initial setup (I skipped everything I could skip) to get to the Launcher. Then I copied 'LE_X2_X820-OS-OP-FGXOSOP5801910121S-5.8.019S.zip' (stock 19s rom) to Internal Storage through Windows. I promptly reboot to recovery and *bam* I'm hit with Decrypt Data again leaving me unable to flash the example rom. FFS, I never set a password.
Also 'default_password' doesn't work.
decrypt
What I did when I was on the stock ROM was to just keep hitting cancel and booting back into TWRP through the recovery and using hardware buttons to boot back in a couple times until the decrypt data screen didn't show when booting into TWRP.
Found a work around that might work on all phones having this issue
I too had the same password issue and I tried a lot, and I really mean, A LOT of ways to get it working. I tried setting password and then applying the same in TWRP, I tried evein trying to connect my phone to pc so that it showed me my phone on pc through which I could be able to transfer files to phone after doing a clean wipe everytime it asked for password and that too did not work out.
So I got another idea, if I wipe the data folder and clear cache once it asks for password, and then go to bootloader and connect through ADB, then I might get to copy the files by command line ADB and that might work and it did not too.
So another thing I tried, downloaded various versions of TWRP and finally got hitched with the latest 3.1.x version. There after doing all wipe I mounted the USB Drive and connected my phone to pc and opened ADB, and that did the work.
So follow these steps and let me know if it works but the key here is PATIENCE; if you have not got it, give up the process (I kept on trying continuously for more than 12 hours and finally got it done.):
Step 1: When prompted for password, Click Cancel and Swipe the slider to modify partition details.
Step 2: Do a wipe by formatting data (type in yes to do so), factory reset and then clear the cache and data folder again.
Step 3: Goback to Mount and click Mount USB Drive/Device ( Has the option in TWRP 3.1.x versions )
Step 4: Connect your phone to your PC and open up the ADB ( Its a whole different ball game ***Also phone wont detect in ADB unless drivers are installed )
Step 5: Type "adb devices" withoput the "" and press Enter. If it shows your phone then you are good to go OR go back to the mount and try mounting the USB again ( try with different variations: sometimes reconnecting your USB cable before or after doing so might work, sometimes re-wiping and re-formatting might work ). Keep entering the command until phone gets detected.
Step 6: When connected, type in "adb push <path/to/rom-or-flash files/with/file-name> </data>"
Obviously without the "" or the <>s. Repeat for all the files.
Step 7: Now go to Install and the "data" folder and then install the files one by one.
Thank me later
Can someone explain what I encountered for "twrp decrypt password" command as given below?
Most of the time I use PC adb shell commands for wipe, sideload, etc. I tried twrp decrypt command as below:
Assume my Le Eco account password as "abc1de2f" and google account password as "XYZ".
~ # twrp decrypt XYZ -
Attempting to decrypt data partition via command line.
Failed to decrypt data.
Next I used Le Eco account password:
~ # twrp decrypt abc1de2f
Attempting to decrypt data partition via command line.
Failed to decrypt data.
Assuming I might have inserted a special character "&" in the Le Eco password at the time of account creation I entered as below:
~ # twrp decrypt abc1&de2f
/sbin/sh: de2f: not found
~ # Attempting to decrypt data partition via command line.
Failed to decrypt data.
On seeing de2f "not found" I tried:
~ # twrp decrypt abc1
Attempting to decrypt data partition via command line.
Failed to decrypt data.
[1]+ Done twrp decrypt abc1
~ # exit
Now I wonder what " [1]+ Done twrp decrypt abc1" means. I could recreate the same again too.
pbassjunk said:
This phone is really starting to piss me off. I lost all of my data two days ago when a TWRP backup didn't save my lock screen pattern, and now I can't even properly get into TWRP.
What do I do?
Click to expand...
Click to collapse
Heyyo, for future reference restoring a TWRP backup never seems to be able to keep lockscreen settings. It's been a longtime standing bug. I think the way Android saves it prevents tampering via backup and restore...
Just follow this guide to remove the lock after restore
https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Hey! So i had the same encryption problem. I somehow worked around it, and i know how but i dont know if you can replicate it?
So i had the TWRP 3.0.2-2x installed, and got the decryption thingie. I pressed cancel, went to install and browsed to the /sdcard folder, which obviously was empty.
After that i rebooted to bootloader and installed TWRP 3.1.0-0 (https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-1-0-0-t3593942)
When i booted into that TWRP i pressed cancel again on the decryption thingie, and when i pressed install it showed me my internal storage!
Don't know how this works, but hope it helps
Good luck!
If you use EUI 5.6, yo can wipe data partition as ext4 instead of emmc at TWRP and reboot. EUI will initialize sytem as non encrypted. But this method don't work for EUI 5.8 and EUI 5.9. If some one know a good way to keep data partition as ext4 instead of emmc, we will solve the problem.
susobhan.dash said:
Found a work around that might work on all phones having this issue
I too had the same password issue and I tried a lot, and I really mean, A LOT of ways to get it working. I tried setting password and then applying the same in TWRP, I tried evein trying to connect my phone to pc so that it showed me my phone on pc through which I could be able to transfer files to phone after doing a clean wipe everytime it asked for password and that too did not work out.
So I got another idea, if I wipe the data folder and clear cache once it asks for password, and then go to bootloader and connect through ADB, then I might get to copy the files by command line ADB and that might work and it did not too.
So another thing I tried, downloaded various versions of TWRP and finally got hitched with the latest 3.1.x version. There after doing all wipe I mounted the USB Drive and connected my phone to pc and opened ADB, and that did the work.
So follow these steps and let me know if it works but the key here is PATIENCE; if you have not got it, give up the process (I kept on trying continuously for more than 12 hours and finally got it done.):
Step 1: When prompted for password, Click Cancel and Swipe the slider to modify partition details.
Step 2: Do a wipe by formatting data (type in yes to do so), factory reset and then clear the cache and data folder again.
Step 3: Goback to Mount and click Mount USB Drive/Device ( Has the option in TWRP 3.1.x versions )
Step 4: Connect your phone to your PC and open up the ADB ( Its a whole different ball game ***Also phone wont detect in ADB unless drivers are installed )
Step 5: Type "adb devices" withoput the "" and press Enter. If it shows your phone then you are good to go OR go back to the mount and try mounting the USB again ( try with different variations: sometimes reconnecting your USB cable before or after doing so might work, sometimes re-wiping and re-formatting might work ). Keep entering the command until phone gets detected.
Step 6: When connected, type in "adb push <path/to/rom-or-flash files/with/file-name> </data>"
Obviously without the "" or the <>s. Repeat for all the files.
Step 7: Now go to Install and the "data" folder and then install the files one by one.
Thank me later
Click to expand...
Click to collapse
thanks i successful access twrp through your method
Sebastien Dove said:
thanks i successful access twrp through your method
Click to expand...
Click to collapse
now with my nexus 5x how do i proceed?
susobhan.dash said:
Found a work around that might work on all phones having this issue
I too had the same password issue and I tried a lot, and I really mean, A LOT of ways to get it working. I tried setting password and then applying the same in TWRP, I tried evein trying to connect my phone to pc so that it showed me my phone on pc through which I could be able to transfer files to phone after doing a clean wipe everytime it asked for password and that too did not work out.
So I got another idea, if I wipe the data folder and clear cache once it asks for password, and then go to bootloader and connect through ADB, then I might get to copy the files by command line ADB and that might work and it did not too.
So another thing I tried, downloaded various versions of TWRP and finally got hitched with the latest 3.1.x version. There after doing all wipe I mounted the USB Drive and connected my phone to pc and opened ADB, and that did the work.
So follow these steps and let me know if it works but the key here is PATIENCE; if you have not got it, give up the process (I kept on trying continuously for more than 12 hours and finally got it done.):
Step 1: When prompted for password, Click Cancel and Swipe the slider to modify partition details.
Step 2: Do a wipe by formatting data (type in yes to do so), factory reset and then clear the cache and data folder again.
Step 3: Goback to Mount and click Mount USB Drive/Device ( Has the option in TWRP 3.1.x versions )
Step 4: Connect your phone to your PC and open up the ADB ( Its a whole different ball game ***Also phone wont detect in ADB unless drivers are installed )
Step 5: Type "adb devices" withoput the "" and press Enter. If it shows your phone then you are good to go OR go back to the mount and try mounting the USB again ( try with different variations: sometimes reconnecting your USB cable before or after doing so might work, sometimes re-wiping and re-formatting might work ). Keep entering the command until phone gets detected.
Step 6: When connected, type in "adb push <path/to/rom-or-flash files/with/file-name> </data>"
Obviously without the "" or the <>s. Repeat for all the files.
Step 7: Now go to Install and the "data" folder and then install the files one by one.
Thank me later
Click to expand...
Click to collapse
best answer
thank you so much for this solution