Develop Bugs

Did I brick my SGS3 ? ^_^

All right, first thing first. Thanks to everybody for this amazing forum and all support.
Well. Here's my story:
1) Planned on installing CM10 nightly
2) Went to recovery (TWRP v2.2.0) and by mistake wiped everything :/ (Cache, Dalvik Cache, Factory Reset, System Internal Storage)
3) In effect i wiped everything including system.
4) Still have access to TWRP and download mode.
Does anybody have a clue how to fix that and install CM10 again?
PS.
1) internal storage does not mount under system (WIN7)
2) TWRP does not recognize microSDXC (32gbz) formated to either exFat or NTFS. (Tried 4 (four) of them)
Should i buy another micro sd like 2gb, format it to Fat32 and drop CM.zip there ? Or need i do something else?
Very respectfully.

That happened to me I just downloaded the rom to a sd card from my old phone put it in my s3 and installed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Hey thank you for quick answer. Do you know if there is any limitation for TWRP? It does not read my 32gb MicroSDXC.

Go into download mode and re flash then stock rooted rom.
Then install your twrp and try cm again.
Sent from my SGH-I747M using xda app-developers app

Personally, I would (try to?) use adb with the phone booted into TWRP to transfer the ROM you want to flash over to the phone's internal storage, and go from there.
If that's not a possibility for whatever reason, you'd be best off starting by reflashing a stock rooted image with Odin and going from there.

Well. First of all thank you all for all your help in support. Got it back to stock with root (Odin flash). However there is another small problem that i can't figure out. TWRP itself seem not to have access to anything. I mean it sees all / but after openning /sdcard or anything else all it sees is empty folders. It doesn't have an access to external sd either (when you check log it sees that it couldn't mount ext sd correctly [even if after boot to stock system it recognizes it witout any issues).
Any idea how to solve this problem? What has been tried:
1) Reflash recovery (TWRP 2.2 using ODIN)
2) moving all files to /
3) RootExplorer see files (cm.zip) after reboot TWRP doesn't
4) Installing GooManager (it crashes after granting supersu permissions)
Very Respectfully.

With all those problems, flash to stock rooted and start over. You will be better off in the long run. You may want to also format your external sd.
Don't flash twrp with Odin.
Rooted stock
Dl and use goo manager to get twrp

What about a stock kernel? Just my chime in
Sent from my SAMSUNG-SGH-I317 using xda premium

Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.

widofmaker said:
Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.
Click to expand...
Click to collapse
GJ take it sure and slow. Other than flashing stock/rooting form Odin I wouldn't flash anything form Odin. Once you have super user on your phone, leave Odin out and do everything from phone
That's the safest route and it gets easier from here. The countless hours you spent are much easier the more you do it. Shouldn't take more than 20 minute to backup and flash roms and new apps from now on

Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.

widofmaker said:
Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.
Click to expand...
Click to collapse
1. you are flashing a version of gapps that is out of touch with your rom or you did not flash it correctly/cleanly. I remember no matter how many times I flashed gapps I wouldn't get it to sync. Backed all user apps to Titanium backup. Did a clean install from scratch, and wallah it worked. Last sort.
Without doing that though there is usually one that is compatible that is listed on your rom page. Flash that one. For me that is 10/22 but I remember it giving that same error for a while so I ended up flashing the previously compatible version before that which was 7/26. Goo.im might help here, I haven't used it myself. Once you find a working gapps version etc. Store your 'safe' builds in one folder
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable

zetsui said:
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable
Click to expand...
Click to collapse
1) Ended up reflashing gapps with goomanger (script to TWRP)
2) What i mean is that under phone it recognizes them perfectly. Just when I connect phone through USB to PC, my PC tends to mix them up. Just shows ExSD as Internal and Internal as ExSD. No biggy, just tried to fix as many tiny issues as possible before I hit deployment.
Very respectfully.

That is a known, and stated, issue with cm 10.1

[Q] [HELP] Can't install .apk's from SD after unofficial Cyanogen Mod 10.1

I don't know if this is a known issue, nor if I'm in the right forum. Yesterday I flashed Unofficial Cyanogenmod 10.1. It was working pretty good. I then proceeded to install my .apk's. I installed only two, Temple Run & Temple Run 2. After those, I tried to install everything else, but it wouldn't let me. Every time I pressed "Install" the phone restarts. I tried to do it via a File Manager and Airdroid, still the same result; phone restarting. Aside from that, I installed App2SD and when I tried to move to SD it restarted.
I did the obvious things.
Remove SD and reinsert
Unmount and Mount SD Card
Swith phone off, switch it back on
Formatting the whole SD/Erasing the whole thing
I don't want to flash the rom again, since it would erase everything,
Is there possibly any other ways? Please help.

Isn't the ROM blocking you from installing with the "Security->Unknown sources" unticked? Might be a silly thought, but it is possible, that you haven't allowed the ROM to install from non-Market sources. I'm looking forward to your reply, if it fixed your problem or not. Try and tick it :silly:

Did you full wipe when flashing CM10.1? What ROM were you using before? You could try dirty-flashing (only wiping cache and dalvik) the same ROM and version again, but if that doesn't fix it I would do a full wipe and reflash. You can always back up apps with Titanium Backup or something similar and restore them.

Fix Galaxy Nexus bootloop after flashing CM nightly.

Hey guys!
I have flashed my Samsung Galaxy Nexus (i9350) with CM-12.1-20160117-NIGHTLY. I first installed the new CM recovery (with the same build date) via Fastboot, wiped Cache (but not Dalvik Cache, since the new Recovery had no option for this).
My device was then stuck in some sort of "bootloop". It gets to the "Android is updating ..." screen, where it says it compiles "app X of Y", then reboots and starts over again.
So I booted the device back into the bootloader, flashed back the old CM recovery (with build date 2016-11-17) via Fastboot, formatted System, Cache and wiped Dalvik Cache, then installed the old ROM only to find it being stuck in a bootloop too with the AMOLED display increasing and decreasing in brightness, but the ROM's not getting anywhere (not even to the point where it says "Android is updating ..." - it's just showing the boot animation and the screen "goes mad").
So I went back to the "old" CM recovery, formatted System, Cache, wiped Dalvik Cache, rebooted to bootloader, flashed the "new" CM recovery via Fastboot, flashed the "new" ROM again, wiped Cache again with the "new" Recovery ("new" recovery does not offer to format System or wipe Dalvik Cache, which is why I did it with the "old"), again "Android is updating ..." loops.
Now since System, Cache and Dalvik-Cache are basically "clean", I'm afraid that Data might be corrupt and thus my data on the phone might indeed be lost. (I have backups, but they are four months old.) Formatting Data might make the device bootable again, but I'd really like to do some sort of "data recovery". I mean "normally" flashing a ROM doesn't corrupt your data partition, right?
I don't know how to access the data partition though, since the device won't boot. The recoveries I have unfortunately don't allow ADB access either. Any chance? Or should I hit "wipe data / factory reset" and kiss the data goodbye? (Like I said, it's not "much" that will be lost, though I'd really like to keep it if it's "somehow" possible.)
Thanks a lot for your advice!
EDIT: I managed to gain MTP and ADB (root) access by booting into TWRP via Fastboot.
I now backed up the entire MTP storage, as well as the following:
- "/data/data/com.threema.app"
- "/data/data/com.android.providers.telephony"
- "/data/data/com.android.providers.contacts"
- "/data/data/com.android.providers.userdictionary"
Will this be sufficient to get my SMS, contacts (stored on phone), custom dictionary (for swipe recognition) and Threema messages back?

TWRP has a mount as MTP functionality that will allow you to access data.
You can also use adb while you're in fastboot adb pull allows you to pull anything as long as you have the path so adb pull /data should be able to pull those contents.
For me TWRP mount as MTP is a much easier and reliable option.

Thanks! I managed to pull off "/data" using TWRP, wipe "/data", restore files selectively. Works, even on the new nightly, which now runs like a charm.
Do you have an idea, why CWM does not support ADB access? I remember that it used to support it some years ago.

TWRP - Unable to copy files to a totally wiped phone &weird folders on my wiped phone

TWRP - Unable to copy files to a totally wiped phone &weird folders on my wiped phone
I'm trying to install a custom rom on my HTC One M8. I unlocked bootloader, flashed TWRP, did an advanced wipe of everything, but now I'm unable to copy the rom image to the phone.
When I boot in recovery mode, TWRP shows up and the phone appears on my computer. But when I browse it, it has 4 folders:
-TWRP
-_nero_sync
- albums
- mobile
This looks weird to me, as I remember TWRP should be the only folder right there. Also, windows wont let me copy files into any of the folders for some reason.
I actually managed to fix this probably by repeatadly wiping the phone yesterday, but now I did it for at least 15 times and it's always the same.
What can that be?

Storage may be corrupted. You can try the "format data" button on the main TWRP "wipe" screen, which often fixes such corruptions issues. Somewhat obvious, you'll lose data when you format; but if you are wiping everything, this shouldn't matter to you.

Dysfunctional LOS SONY Xperia Z5 Compact suzuran after ENCRYPTION

After heavy reading and trying to sort things out by myself and before giving up on the device, just to give it a chance:
after upgrading to the latest build of Lineage OS for MicroG (lineage-14.1-20190215-microG-suzuran) i encrypted the phone, simple-hearted.
result:
starts into TWRP 3.1.1 but can't decrypt data
No more cell service, which i couldn't solve
After repeated wipe - advanced wipe - Format data followed by reinstallation each i can boot into Lineage, with adb and cell service working but the install is unstable:
-larger uploads like my TWRP backup (~2GB) result in ads connection loss, 'system read only' which can be solved by restarting into recovery, but backup upload is not possible although more than 20GB free space seem to be available (can it be that memory space encrypted before is still not usable, despite formatting all partitions?).
-Trebuchet app crashes
-Phone won't reboot, hangs with startup animation
Last two issues can be solved by wiping the phone and reinstallation, until reoccurring.
Do i have to trash the device or is there something else i could try?
Update:
SOLVED: TWRP Wipe - Advanced Wipe - select Data - Repair Or Change File System - Repair File System (Mount Point /data) (Many thanks: https://android.stackexchange.com/a/176124)
As far as i understand (as stated here https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952) i need a different kernel and a different TWRP build for Encryption and OTA Updates working on the same system, but which ones and how to install is a different thread.