Database Info

[Q] HELP!!Problem with Nexus S

I have a very serious problem with my nexus S . I've installed an app on my nexus and after that... nothing works and when i say nothing i mean nothing!! when i try to open an app says ''unfortunately this app stopped '' always... i cant use my phone even to call or to send a sms. I tried to flash new rom but i cant save anything to my usb storage memory when i try to save something on the phone after the unplug from the usb disappear like never was there. Also its impossible to delete something from the phone if i delete something after one reboot itss back there (photos , music etc.). I tried to do factory reset but when makes reboot and try to open after a min. diplays a delta(warning) sing with an android and stays there and i need to pull out the battery. Also i locked and i tried again to unlock but on the cmd says fail to unlock... i really dont know what to do if anyone has any idea will help me sooooo much.
Thnax anyway

Have you tried to mount SD through recovery. In recovery, go to mounts and storage> mount SD. Transfer freshly downloaded rom from computer then unmount SD. While still in recovery perform a complete wipe.
Mounts and storage> wipe system> wipe data> wipe cache> wipe boot. Now try and flash rom and wipe dalvik cache. Hope this works for you.
Sent from my Nexus S using xda premium

d_phekt
nothing i tried many times through recovery but still nothing! when unplug the usb from my computer the rom dissapear ://

This happened to me once... I tried playing a movie and it froze and rebooted and everything force closed on my... even the launcher
I flashed a different rom to fix it.. and its also a good idea to change the kernel as well
Sent from my Nexus S using XDA

Oh right forgot about this. Unless you have a backup working rom, you can flash that first. If not try this first. go to CWM Recovery and fix permissions. Try that
If it is still not working, this is the solution if you dont need your data on your phone. First take out your mini sd card. Get a mini sd card reader from any tech shop (eg dicksmith, costco even has it, electronics store) use that to copy everything onto your SD Card. First make a copy of your current rom. (yes the one with nothing working. So if this stuffs up you can try another way)
Once you copied everything to your comp on your sd card. Plug your sd card back in. No go to recovery, and wipe ABSOLUTELY EVERYTHING. Including sd card. Now just flash the rom and kernel (optional) and it should all work.
When i mean everything (via CWM Recovery). Wipe: cache partition, dalvik cache, battery stats, format: /sdcard /system /cache /data /boot. Also wipe SD card and SD ext.

qaz2453
the problem is i cant save anything and that mean i cannt flash any rom or kernel because when i plug it with my computer and try to save (through mounts and storage) new rom or kernel to phone when i make unmount or to press go back the rom disappears

TigaTiger
My friend unfortunately the nexus s doesnt have sd card or mini sd card The phone has 16 GB so its impossible to follow your instructions! also i tried to make backup but nothing its shows that make backup but after the files dissappears the same when i try to save new rom and flash it again

nexuszac said:
qaz2453
the problem is i cant save anything and that mean i cannt flash any rom or kernel because when i plug it with my computer and try to save (through mounts and storage) new rom or kernel to phone when i make unmount or to press go back the rom disappears
Click to expand...
Click to collapse
If you got clockwork mod recovery.. than go into that and turn on mass storage from there
Sent from my Nexus S using XDA

qaz2453 said:
If you got clockwork mod recovery.. than go into that and turn on mass storage from there
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
You mean mounts and storage? and then mount USB storage?? yes i tried a 1000 times but nothing when i transfer the rom from my computer to phone when i press go back the rom dissappear i dont know why but its impossible to keep it ://

Can you see your device in fastboot devices? If yes download the Android 4.0.4 factory image from here https://developers.google.com/android/nexus/images
Unzip it in the tools folder of the Android SDK. Enter your device in booloader mode with volume up+power and insert the following order in the cmd window:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-crespo-i902XXXX.img (check the proper name according to your phone)
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i902XXXX.img (check the proper name according to your phone)
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip (check the proper name according to your phone)
Just make sure you download the correct version! This is important or you can end up with a bricked phone.

DeuXGod said:
Can you see your device in fastboot devices? If yes download the Android 4.0.4 factory image from here https://developers.google.com/android/nexus/images
Unzip it in the tools folder of the Android SDK. Enter your device in booloader mode with volume up+power and insert the following order in the cmd window:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-crespo-i902XXXX.img (check the proper name according to your phone)
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i902XXXX.img (check the proper name according to your phone)
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip (check the proper name according to your phone)
Just make sure you download the correct version! This is important or you can end up with a bricked phone.
Click to expand...
Click to collapse
Mate i followed all your instructions but! the problem now is the phone is locked because i locked it and now when i try to unlock it ALWAYS (when i press yes to unlock ) says on cmd FAILED to erase.... so i cant do anything because when i type ''fastboot flash bootloader bootloader-crespo-i902XXXX.img'' says ''failed because is lock type fastboot oem unlock''

I'm afraid you're pretty much out of luck mate... every thread i searched with FAILED (remote: Erase Fail) nobody could solve it... and without unlocked bootloader we can't do much i'm afraid...

Encrypted Device - NO keyboard

So, I encrypted my device last night, but on rebooting, the password screen has no keyboard, so I cannot enter my password... In TWRP, I cannot mount data (doesn't prompt for a password like it should), so I cannot wipe... Any attempts to wipe result in FAILED. I cannot access anything from a computer (nothing shows up).
I've seen a few scattered posts that relate, but none resolved. It would appear that I have a completely bricked phone now. Any suggestions?
HTC Droid DNA - Cyanogenmod (latest milestone) - TWRP 2.8

Did you encrypt /system?
You should normally be using LUKS and have an unencrypted partition on your SD card so you can access it via USB. Then getting to the other encrypted partitions is a lot easier.

dyczone said:
Did you encrypt /system?
You should normally be using LUKS and have an unencrypted partition on your SD card so you can access it via USB. Then getting to the other encrypted partitions is a lot easier.
Click to expand...
Click to collapse
I can access/mount system in TWRP, however I cannot see it over USB on my computer. Is there anything I can do from TWRP to get a keyboard, or at least wipe and start over.

Nagrom Nniuq said:
I can access/mount system in TWRP, however I cannot see it over USB on my computer. Is there anything I can do from TWRP to get a keyboard, or at least wipe and start over.
Click to expand...
Click to collapse
Can you try flashing a stock ROM via fastboot?

Well, incase anyone is interested. I was able to adb sideload CM11 onto my phone using TWRP and my computer. After that I was able to reboot and get a keyboard on the encryption screen. Unfortunately, after I entered my password, the screen looked like it was unlocking, however it then just went blank and stayed like that for over an hour before I gave up on that. Sadly, I was reduced to formatting data, losing everything, and starting over from scratch... Chalk that up to a massive fail for encryption. If that happens to people, no one is going to use it.

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]

Did you ever find a fix? I'm having a similar problem.

Try to use fastboot restore everything.

I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!

rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device

Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.

If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.

How I unbricked "Decryption unsuccessful" The password is correct but... (Apps2SD)

How I unbricked "Decryption unsuccessful" The password is correct but... (Apps2SD)
Hello, I don't usually post in tech forums, I usually the guy that only reads,
but this is the time when i could not find the straight answer to my problem and had to google the solution out of similar posts, so I decided to glue everything together and write my solution to this particular situation,
so I might save a lot of time to someone who got in exact or similar situation.
Sorry for my crappy English, but here we go.
What this post trying to solve:
You stuck at boot loop: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt.
and how to make it work Apps2SD with Huawei P9 SD card with enabled password protection.
Basically my Huawei P9 (EVA L-19) with Android 7.0 Nougat got running out of internal space, and i am really a heavy user on apps. Kirin 955 handles just fine as long as it has at least 10Gb of internal free space.
I have SD card 64Gb, but huawei stopped support, native move apps to SD, long time ago. My device is rooted, so I was searching for a solution. There is few apps that can transfer your internal memory apps to SD by using root, but the one that actually worked for me is Apps2SD. The thing is, my SD card is password protected (Huawei native function) I want to keep this function in case of device getting stolen.
Problem is, many third party apps that move your apps to SD, does not know anything about Huaweis SD card password feature. In fact (as far as i tested) only Huawei phone allows you to enter password and show contents of SD card, no PC, or for example Samsung phone will recognize this SD card.
So i was messing with Apps2SD, partitioned my SD card in to 2 primary partitions, 1- exfat, 2- Ext3. It works kinda fine, but after reboot, there is delay, Huawei unlocks SD card after main boot part, and Apps2SD does not understand this and show that it failed to mount second partition.
In this case, Apps2SD starts giving you solutions, one of them is this ADVANCED mounting option. It does not tells u about any dangers, nothing really.
I chose that option to see if it will be able to see second partition contents faster, rebooted - boom bricked.
You see the message: "Decryption unsuccessful" and asks you for decryption password. It might be SD card password, not sure, it does not matter, because you can type ANYTHING and it always say:
"The password that you entered is correct but unfortunately your data is corrupt". And gives you only option: fully data factory reset. Now hold your horses, dont press that. I just knew that this is bull**** and no way
my personal data is corrupted, its just some hadshake issue. (I was right i fully recovered everything up n running)
Assuming you got in this mess, your device must be rooted and you probably have TWRP recovery, cause Apps2SD work only with rooted devices.
To recover from "Decryption unsuccessful" boot message and restore all data and settings:
Got to TWRP recovery by holding power button and volume UP (after phone vibrates, hold both buttons 2sec more and then release power button, and then after 2sec more release volume up, cause if
you do this too fast, u will end up in wifi recovery by Huawei, and it wont work anyway cause your device rooted).
Then go to advanced and file manager, locate sdcard folder (this will be internal memory, not external), you should be able to see all of your personal files! Copy them to flash drive by connecting with OTG.
What we gonna do now is: do a full nandroid backup: TWRP, backup, check: BOOT, SYSTEM, DATA. and do a backup to flash drive connected with OTG or hard drive if it works for u.
After backup is done, go to WIPE, select format data, select DATA partition and see what original file system it uses. Now format in any other system, then reformat again to your original file system.
DATA partition somehow lost its encryption handshake key and this caused the problem, reformatting fixes it.
Now do a full wipe as if you would install new rom, wipe: system, data, storage, cache, dalvic cache.
Restore your previous nandroid backup, reboot to system,now your phone should boot with all the apps and settings just as you left.
You might be missing some pictures and other media in main storage, just connect your P9 with usb cable to pc, and restore previously backed up media from flash drive manually in pc interface (copy paste, replace all),
some small minority files might wont copy, don't worry about it, Im not sure but they are mostly indexing files, all ur media will be back in place.
Now, how to make Apps2SD work with this configuration?
Don't use that advanced method to find SD cards second partition, use any of first 3, the 3rd one worked for me just fine, cause its SU library based one.
Don't move your apps fully to SD, or they will "disappear", move everything except APK, ODEX, DEX (Lib is optional, you usually can move this one just fine). SO basically app core will stay in main storage but cache and app data will be on second SD card. This way, after you reboot your phone, you will have to wait like 3mins and App2SD will link your files to apps itself just fine. It might will show some errors right after reboot, but after Huawei unlocks its card, files will be linked, and apps wont be "gone" cause app core still stays in main storage.
This way i managed to save a lot of space and move most of app storage to SD card, P9 became very responsive, even in 2018 this is a really fast smartphone.
Sorry for a messy post, I'm not a writer, but I hope this helps to someone!

Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.

dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
So glad this helped someone

dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919

zgfg said:
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919
Click to expand...
Click to collapse
I'm not entirely sure what caused it, but I suspect Apps2SD just like in the original post (I installed/tried to use it shortly before the problem occured).

Issue with Havoc ROM installation

Guys, having a lot of trouble getting the Havoc ROM on my device. I am new to this slot A/B thing so please bear with me. I am coming from OOS 9.5.13 with unofficial twrp 3.3.1-70. Active slot is B. I rebooted to recovery, it asked me for my password, entered password, wipe data, flash rom, flash twrp installer, and when I reboot recovery I can't access my sd storage!! I see a 0 folder with random folders inside. So I figured TWRP is unable to decrypt the other slot. I start from scratch, i.e, format data and let it boot, strangely OOS boots with again like a fresh install To prevent encryption again, I don't go throught the setup, reboot to bootloader, then select recovery, inside twrp again (note: wasn't asked for password this time; I assumed because I didn't go through the OOS initial setup (no PIN etc) the storage in currently decrypted), connect to PC for transferring ROM back onto the phone again, disconnect from PC, wipe data, flash rom, flash installer, revoot recovery, reboots to slot A, and AGAIN no access to the SD card contents (folder 0 with random folders inside again). So my questions are:
1) Can someone please explain to me what's going on...?
2) Is there a way to permanently disable encryption on the device? (no-verity, etc)
3) Can I read something to get up to speed with this two slot thing and how things are supposed to work with OnePlus devices (was a long time Samsung user)
I am terribly frustrated with this; I have gone through this process a ridiculous number of times. I have fastboot flashed stock OOS several times. Even did the MSMTool to get back to as-stock-as-possible (somehow frying my SIM in the process, which I also suspect has something to do with Magisk modules). I am absolutely loosing my marbles over this.. Someone please help me!!
My device is retail Indian unlocked OP7P.

Why are you so hellbent on disabling encryption?
Format data, install rom over adb sideload, boot the rom, profit?