Database Info

[Q] 2.3.4 update failure leads to whole crash..

Ok, so Was using my nexus s today and I kept getting the notification to perform a system update to the newest version of gingerbread (2.3.4). Prior to pressing update my phone was at 2.3.1 default with 2.5.### ClockworkRecovery and it was rooted. Everything worked on it perfect. So I proceeded to download and install the update, and CWR fails to install the update and I would have to take out the battery to restart the phone. I had been doing this multiple times and I wanted to get it updated. So I go into CWR and try installing it manually:
I look around and try to find the file and I couldn't, I reset user data to see if it would fix it and it didn't, then I go back and start formatting the following folders, /system, /cache, /data and one other but I did not format /boot, so Then (noob me) I restart to phone and of course the rom is gone. I get back to recovery and try to restore from update.zip but the console said the file could not be found, I look up my model and look for a full verison rom and the mount my usb storage and place the rom .zip on the storage and try to install from .zip on sd but it did not work so I end up grabbing this and installing it and now I'm stuck, when I do adb shell it doesn't pick up the phone any more, it can fast boot on the phone but it can't go into recovery and I have no idea what I should do to try to fix this problem.
NOTE: before I ened up installing and replacing the recovery, my /system folder would not mount due to "invalid arguments"
Model is i9020T
I don't have firmware version access
and if there is any other information I can provide please let me know
Update:
I got the device to be recognized by fastboot but not by "adb shell", when I type adb shell no device is found, so I guess my question now is do I need to just flash a new recovery and then try to flash a new rom?
Solution:
1. fastboot your phone, (volume up+lock/power button)
2. place the recovery image you want to install in the "Android SDK"/tools/ folder
3. in your cmd/terminal, while in "Android SDK"/tools/ execute:
Code:
fastboot flash recovery "NAME-OF-RECOVERY.img"
4. once that is installed and it should work, then restart your recovery mode
5.clear all your data/factory reset, including davlik cache
6.mount your sd to your computer so you can place the Rom you want on your phone's sd
7. In recovery choose zip from sdcard to install.
8. It should install, if it gives you problems try another rom, I had problems with rAv 1.2.2, keep restarting every minute. I used "NS-2.3.4-GRJ22-Stock-Deodexed-signed.zip" and it worked.
9. Restart the phone and be patient the phone will start up and you should be set.
Hope this helps someone!

[BUG][JB:4.1.2] PAC-man 18.0.0 [Paranoid] + [Aokp] + [Cm10]

Expected Result:
Steps tried to install mentioned by "marcomarinho9"
FIRST INSTALLATION OF THIS DUDE
Download the P.A.Cman
Download the GApps
Put both zips into the root directory of your SD Card
Perform a full wipe
"advanced" > "wipe battery stats"&"wipe dalvik cache"
"mounts and storage" > format everything except sdcard
"wipe cache partition"
Flash both zips with the Recovery with "install zip from sdcard" > "choose zip from sdcard"
Flash P.A.Cman rom
Reboot
Flash GApps
Reboot
Actual Result:
1. After reboot error pop up displaying "Unfortunately the process com.google.process.gapps has stopped" displays infinite number of times.
2. Another pop up "Unfortunately, Setup Wizard has stopped"
Hard Rebooted to Recovery and cleared cache and got below bugs
3. HOME hw button not working
Rebooted to recovery again and reinstalling only the ROM zip.
4. Home key working
Conclusion:
With gApps, LGP500 is bugged.
Device Details:
LG P500
sKantH

Nothing is bugged, its user error, you have to trim the Rom down so that the Rom and gapps can be happy together on your internal memory if you dont then there's not enough space and they start fighting one another and then some of the little files and codes get kicked outta there homes and thats why your having so many bugs

3ncrypt3d_Droid said:
Nothing is bugged, its user error, you have to trim the Rom down so that the Rom and gapps can be happy together on your internal memory if you dont then there's not enough space and they start fighting one another and then some of the little files and codes get kicked outta there homes and thats why your having so many bugs
Click to expand...
Click to collapse
Right now im trying the new ROM . Let see Wat's happening after testing it.
thanks for the reply

PAC-man 18.0.0 [Paranoid] + [Aokp] + [Cm10] not suitable for LG O1
Nothin offensive atall.
I just loved the UI, but as LG O1 has gt tiny scree, this doesn't suit well. Settings screen is too tiny. Tried diff paranoid settings, but nt Gud
sKanth
CM10
LG O1 P500
skanth said:
Expected Result:
Steps tried to install mentioned by "marcomarinho9"
FIRST INSTALLATION OF THIS DUDE
Download the P.A.Cman
Download the GApps
Put both zips into the root directory of your SD Card
Perform a full wipe
"advanced" > "wipe battery stats"&"wipe dalvik cache"
"mounts and storage" > format everything except sdcard
"wipe cache partition"
Flash both zips with the Recovery with "install zip from sdcard" > "choose zip from sdcard"
Flash P.A.Cman rom
Reboot
Flash GApps
Reboot
Actual Result:
1. After reboot error pop up displaying "Unfortunately the process com.google.process.gapps has stopped" displays infinite number of times.
2. Another pop up "Unfortunately, Setup Wizard has stopped"
Hard Rebooted to Recovery and cleared cache and got below bugs
3. HOME hw button not working
Rebooted to recovery again and reinstalling only the ROM zip.
4. Home key working
Conclusion:
With gApps, LGP500 is bugged.
Device Details:
LG P500
sKantH
Click to expand...
Click to collapse

[Completed] Pioneer XDP-100R stuck on android logo

Hi,
I have a Pioneer XDP-100R (hi-res music player) running android 5.1. I tried to root with SuperSU. At the end it asked to reboot my device. Now it's stuck on the android boot logo.
I can access the recovery menu (next track + power). A message is displayed: "E:Can't open /dev/block/platform/msm_sdcc.1/by_name/misc (permission denied)".
If I choose Wipe Data/factory reset, I get:
-- Wiping data...
Formatting /data...
Formatting /cache...
Data wipe complete.
"E:Can't open /dev/block/platform/msm_sdcc.1/by_name/misc (permission denied)".
I get pretty much the same when I try to "wipe cache partition".
None of the two actually make a difference.
Previous track + power is supposed to get me to the fastboot menu but it's stuck on the linux logo.
I had made a backup with adb beforehands but I can't restore it. adb won't see my device unless I select the option "apply updates from adb", but in that case, the only command it accepts is adb sideload.
I have not installed a custom recovery as my device is too rare. I never managed to find a stock rom or custom rom for my device so I can't even flash another one.
Has anyone any clue?
Thanks heaps

Hello,
please ask here:
http://forum.xda-developers.com/android/help

Samsung GT-S7580 (Galazy Trend Plus) cant mount data, wont boot after stock rom flash

Hi,
I have a Samsung GT-S7580 from my girlfriend sitting on my desk for few months without battery (the original got fat and we recycled it).
Today I bought a new battery and while trying to boot the phone, it got stuck on the boot screen "Samsung GALAXY Trend Plus GT-S7580" with a little red exclamation mark on the top left of the screen.
I googled a bit and i found out that we could flash it again with the stock ROM. I followed that guide online:
1) I went to samsung-firmware.org and got the correct ROM (same country, same phone company): PRT-S7580XXUBOA1-20150520110018.zip
2) I got Odin3 v3.07 and the Samsung drivers as well as the CWM (CWM_6.0.3.7_notouch_GalaxyTrendPlus_s7580_bdc_v0.2.zip, including "recovery.tar.md5" inside)
3) I rebooted the phone in download mode (VOLDOWN+HOME+POWER) and via Odin I tried to first flash CWM (recovery.tar.md5), all went fine and i managed to boot into CWM recovery, tried to clean data/cache/etc but the phone would still not boot.
4) I then went back to Odin and flashed the firmware (extracted the zip to: S7580XXUBOA1_S7580PRTBOB1_S7580XXUBOA1_HOME.tar.md5), all went fine and the phone booted into Android! Weee!!!
Great! But then I decided to install Cyanogenmod as the stock was a bit old:
5) I downloaded TWRP for the phone: TWRP.S7580.tar.md5 and I downloaded CM13.0 for Kylepro (the correct one): cm-13.0-20160910-UNOFFICIAL-kylepro.zip and Open Gapps zip file
6) Because the CM13.0 is a ZIP file, I added it to the Downloads folder while the Android was booted and plugged to my PC.
7) I then rebooted the phone into Download mode again and flashed TWRP via Odin
8) I restarted the phone into TWRP mode and i again deleted data/cache/etc, then I went to install the CM13.0 zip file
9) All went file and CM13.0 was installed and booted
10) I went through the normal first-time-config and then I decided to reboot into TWRP again to install "open_gapps-arm64-6.0-nano-20181107.zip"
11) But oops, i tried but apparently i got the arm64 instead of the arm (32bit) which obviously did not install. So I decided to get the arm version and boot the phone normally into CM13.0 as before so I can just copy-paste the new Open Gapps zip file there.
12) Damn! The phone got stuck again on the boot screen "Samsung GALAXY Trend Plus GT-S7580" with the little red exclamation mark on the top left of the screen... Again?....
13) I then tried to get to TWRP and clean cache/data, but it says "Failed to mount /system (invalid argument)", same for /data, /cache and /efs and then "Unable to mount storage"
14) I tried to repair the /data, gave me: Present: No, Size: 0MB, Free: 0MB, Removable: No, Used: 0MB, type: ext4 and then "/sbin/e2fsck -pf process ended with ERROR: 16 Unnable to repair Data"
15) If I go to install I see the linux/android tree but most major folder is empty (sd_card, data, external_sd, recovery, etc)
16) if I go to mount, i cant select any option, and selecting "Select Storage" will give me "Internal storage: 0MB"
17) I also cant change the partition type back to ext4, nothing happens.
18) I tried to format data but i also get an error "Unable to open ' ' to wipe crypto key"
19) I tried to flash the original ROM again via Odin, all went ok, same issues happened from point 12.
20) I tried to flash the original CWM via Odin, all went ok, but when I reboot it insists on rebooting into TWRP and the same happens from point 13.
21) I tried to flash the latest TWRP for this device (twrp-3.2.3-0-kylepro.img.tar),all went fine, but after rebooting im still with TWRP v3.0.2-0...
Any help?

vascotech88 said:
Hi, I have a Samsung GT-S7580 from my girlfriend sitting on my desk.........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is also specific to your device too (Galaxy S Duos 2).
https://forum.xda-developers.com/s7582
With that guidance...
You may be able to locate what you are looking for on the following thread that's specific to your device too.
https://forum.xda-developers.com/showthread.php?t=3648165
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.

Qualcomm CrashDump Mode Attempted to kill init! exitcode=0x0000000b do_exit

Hello,
I'm having issues installing Nethunter.
I have the last Android version 11.0.8.1
Oneplus 7 Pro GM1913
I did:
- Msm tool to go back to stock.
- I unlocked the bootloader (fastboot oem unlock, phone wiped)
- Enabled USB debugging mode again.
- fastboot boot twrp-3.6.2_11-0-guacamole.img
- adb sideload twrp-3.6.2_11-0-guacamole.zip
- rebooted to system and then to recovery to check everything was ok.
- Tutorial said to format data ( Wipe -> format data -> yes ) doing this i got this message in the middle of the logs:
"TWRP will not recreate /data/media on an FBE device. Please reboot into your rom to recreate /data/media"
- Rebooted to system as the message request and it recreated the folders and i could copy files to the internal storage once again.
- Rebooted to Recovery TWRP and installed Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v19.3.zip.
- At this point the guide said to reboot to system to finish the setup but never got into the system, instead i get this message:
"Qualcomm CrashDump Mode
Attempted to kill init! exitcode=0x0000000b
do_exit"
Is anyone able to help me ? I can't find information about this message that could relate to my situation specifically.
With thanks and regards,