Develop Bugs

[ROM][4.3.1][December 3] Slim Bean jfltetmo [stable 2.2]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
Notification drawer & lockscreen Shortcuts
SlimPIE
Customizable NavBar
QuickSettings custom Shortcuts
Full hardware key rebinding!
SlimCenter
..and much more!
Need to find a feature? Want to see screenshots? Check out SlimBean's features!
Changelog
Find our latest Changelog go here
Chat with the slim team and other slim users
IRC: #slimusers @ freenode
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
Google+ [link]
Twitter [link]
Facebook [Link]
Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Download the latest build from [here]
Gapps ( if you don't have it already) from [here]
!Recommended! Full wipe, and manual format /system
Flash ROM and the gapps you want, reboot
FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!
To get root working go to Settings/Developer options/
Then change the option "root access" to "apps and adb".
Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.
Thanks!
You can find the full list of credits here
Source
Please visit here for the rom source code.
Kernel source can be found here
XDA:DevDB Information
Slim Bean jfltetmo [stable 2.2], a ROM for the T-Mobile Samsung Galaxy S 4
Contributors
blk_jack
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2013-12-03
Created 2013-08-18
Last Updated 2013-12-08

SlimBean 4.3 stable 2.2
Stable 2.2 is live! Please read the Changelog for more details including proper upgrade/installation methods, as well as notes on activating root and restoring with Titanium Backup.
Changes, Features & Fixes:
Changelog for stable 2.2
SuperUser security fixes
Several BT fixes
Selinux security ehancements
LID control fix
some translation upstrem
nearly all device got device and kernel updates

Please note these builds are under heavy development!
Known issues
Headset in-call mic uses phone
HDR Camera mode may need improvements, but should at least work
4.3 mini-FAQ
Q) I'm stuck at the boot logo and/or a boot loop!
A) Make sure you use TWRP 2.5.0.2. TWRP 2.6 and other recoveries can cause boot loops & hangups
Q) Root doesn't work!
A) From a clean build you need to enable root access for Superuser itself. This is different from 4.2.2 in which Superuser by default had root access on a new install. To do this, go to Settings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.
Q) Titanium Backup isn't restoring apps!
A) Change the backups folder to storage/emulated/legacy.
If you use Philz recovery 5.10.0 you must upgrade to 5.11.0 or you will lose radio!
Since the SGS4 is so new, development is happening very rapidly. This should be taken into consideration when flashing any 4.3 AOSP-based builds on the device. Known issues will be listed here.

I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.

quickquest88 said:
I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.
Click to expand...
Click to collapse
Something is definitely wrong on your end. You're gonna have to give me more info, like your recovery and what steps you did to install the ROM.
If it's stuck at the boot logo, try wiping dalvik cache.
Sent from my SGH-I337M using Tapatalk 4

I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.

quickquest88 said:
I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.
Click to expand...
Click to collapse
The lack of /data in recovery worries me the most. That's definitely not good and I'm not sure how that would be happening.
Are you doing all this w/ your device plugged in? Can you try not plugging it in if that's the case?
EDIT: I've had an issue where sometimes on reboot w/ my device plugged in I need to wipe dalvik to continue booting. I'm not sure why this is at the moment but it's always fixed if I reboot to recovery and wipe dalvik cache.

i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.

quickquest88 said:
i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.
Click to expand...
Click to collapse
From what I'm reading there are issues w/ TWRP 2.6. Downgrade to TWRP 2.5 and your issues should go away.

I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
I spoke too soon. now I'm getting an error when trying to format system that says cwm can't mount /data or /android.secure and /sdcard
now I seem to be soft bricked. I can't get it to go past the Samsung galaxy s4 screen. can't format.

quickquest88 said:
I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
Click to expand...
Click to collapse
You sure you don't have a bad build?? None of my testers are having these issues. Grab it here & flash it w/ goomanager or odin/hemidall http://goo.im/devs/OpenRecovery/jfltetmo

thanks fro the link. twrp 2502 got me out of the softbrick. with cwm, nothing seemed to work to get it past the samsung screen.
twrp got me to the point that i can at least get it running again, however, not even 2502 fixes the original issue of being unable to reboot. this time after getting 4.3 installed, i rebooted at the screen asking what language. it didnt get past the samsung screen. went back into recovery and wipe/format data/yes and then reboot. that got me back into the o.s.
this is really strange, i wish i knew more about developing. as long as i dont reboot, im ok. good thing this isnt windows, or id be in trouble, hah!!

I had no problems installing with the latest regular version of CWM from ROM Manager. Got root working just by tinkering around in superuser in settings... Not sure what I did but root works. Overall very very nice for a beta release!
I have one inane question(hope I didn't miss it somewhere): is the setting for lock screen rotation removed? It seemed to me to be buggy on cm10.2 anyway. Also can't remember if the phone app rotated to landscape in 4.2.2 build, but I think it did. Again, meaningless issues really, just wondering.
Thanks for the hard and awesome work!

Loving the beta build! It's almost fully stable! All convenient features are working as should!

I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.

Bowmanspeer said:
I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.
Click to expand...
Click to collapse
It'll be under Gallery2
Sent from my SGH-I337M using Tapatalk 4

Flashed 8/20/13 using TWRP 2.5.0.2. No problem, other than some freezing apps here and there. Cleared caches, fixed permissions, and all seem fine now.
Will now run it through my battery tests, etc.
Thank you blk_jack!

I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app

quickquest88 said:
I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This is a notice for others on TWRP 2.6. Please read the OP (post 3 specifically). It has been updated to contain a mini-FAQ for 4.3 that should solve 99% of the issues I'm seeing on XDA.

Any way to get stock DPI?
Sent from my Nexus 7 using Tapatalk 4

[Q] S3 using 20GB of System Memory! What is going on?

I have a 32GB S3 with only 5.73GB of available space. Looking in my storage settings the reason is System Memory is gigantic at 19.95GB.
How can system memory take up so much space? I mean most S3 phones are only 16GB total.
Something is obviously amiss but not sure how to get to the bottom of this. Any help or suggestions would be appreciated.
TIA

Superorb said:
How is that different from installing from a file manager?
Click to expand...
Click to collapse
Are you rooted?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
Are you rooted?
Yes but everything is fully stock.
Click to expand...
Click to collapse

bilgerryan said:
Are you rooted?
Click to expand...
Click to collapse
Yes but everything is fully stock.
Oops, sorry for double post.

That's definitely not right, if I was in that situation I would try to make a backup in recovery (if system is actually 20GB I doubt you'll have enough space) and then I would wipe everything (system, data, cache, and dalvik) thoroughly in recovery and reinstall the ROM to see if this issue persists.

If you go to Storage, in settings, and tap on the various categories shown there (Used Space, Miscellaneous files) you can dig down and maybe see what is taking up so much space. Give the phone a minute or so to calculate the space each time you go to a new page.

bilgerryan said:
That's definitely not right, if I was in that situation I would try to make a backup in recovery (if system is actually 20GB I doubt you'll have enough space) and then I would wipe everything (system, data, cache, and dalvik) thoroughly in recovery and reinstall the ROM to see if this issue persists.
Click to expand...
Click to collapse
I am fully stock so I can't make a backup in stock recovery. And I am stock ROM so there is nothing to reinstall.
meyerweb said:
If you go to Storage, in settings, and tap on the various categories shown there (Used Space, Miscellaneous files) you can dig down and maybe see what is taking up so much space. Give the phone a minute or so to calculate the space each time you go to a new page.
Click to expand...
Click to collapse
That's what I did, that is how I know the System Memory is taking 20GB. That is where I can see that. Clicking on the System Memory category does not give you any further breakdown.
See the attachment.

You might want to try an app like SD Maid. It has an option to find large files, and it can clean up all the cruft that collects over time.

poit said:
You might want to try an app like SD Maid. It has an option to find large files, and it can clean up all the cruft that collects over time.
Click to expand...
Click to collapse
I'll give it a go but this phone isn't even two weeks old.
I'm totally baffled here.

poit said:
You might want to try an app like SD Maid. It has an option to find large files, and it can clean up all the cruft that collects over time.
Click to expand...
Click to collapse
That was quick and easy. I just ran it and there are no egregious offenders, as I expected.
This 20GB of system memory usage on a new & stock phone is ridiculous...

Before I installed a new rom and kernel, I was showing like 13gigs of memory use. What I did was formatted my system, data, and storage, and I ended up with 9 gigs of available storage after installing everything. Of course everything is backed up so I had nothing to worry about.
sent from my Wicked GS3

schlepprock said:
Before I installed a new rom and kernel, I was showing like 13gigs of memory use. What I did was formatted my system, data, and storage, and I ended up with 9 gigs of available storage after installing everything. Of course everything is backed up so I had nothing to worry about.
sent from my Wicked GS3
Click to expand...
Click to collapse
That's what I suggested

This is ridiculous.
First I tried a factory reset. After rebooting I skipped everything end went right into my phone settings. Didn't even associate a Google account with the phone (so no data was automatically restored). Still 19.95GB used for system memory.
Then I went into stock recovery to wipe everything. (Remember my phone is bone stock except it is rooted.)
First I get a "no command" message. Then it says "error" and then it goes back to "no command." Then I have the android guy with a red exclamation sign coming out of his body along with all the stock recovery options.
I then wiped the cache partition and wipe data/factory reset.
When I select the option to reboot I get "error" one more time and it reboots.
Same problem. I go into the Android OS with no associated Google account and it still shows 19.95GB of system memory being used.
Any other suggestions?

After every type of reset and wipe failed I tried reinstalling the stock unrooted 4.3 ROM. No joy. Phone still shows 19.95BG used for System Memory.
And when I boot into stock recovery I still get the android guy with the red exclamation mark sign coming out of his body.
Anybody have any ideas as to what in the world is going on here? I've done everything I can possibly think of and none of it helps.

uscpsycho said:
After every type of reset and wipe failed I tried reinstalling the stock unrooted 4.3 ROM. No joy. Phone still shows 19.95BG used for System Memory.
And when I boot into stock recovery I still get the android guy with the red exclamation mark sign coming out of his body.
Anybody have any ideas as to what in the world is going on here? I've done everything I can possibly think of and none of it helps.
Click to expand...
Click to collapse
Odin MK3 unrooted. If that doesn't fix your problem I don't know what will.

bilgerryan said:
Odin MK3 unrooted. If that doesn't fix your problem I don't know what will.
Click to expand...
Click to collapse
That's what I did. I used the tar file from this thread - http://forum.xda-developers.com/showthread.php?t=2565972 and still 19.95GB system memory used without even associating the phone with a Google account.
Is their any significance to having the android guy laying on his back with the red exclamation mark and the message "no command" when I am in recovery? What is the meaning of this?

uscpsycho said:
That's what I did. I used the tar file from this thread - http://forum.xda-developers.com/showthread.php?t=2565972 and still 19.95GB system memory used without even associating the phone with a Google account.
Is their any significance to having the android guy laying on his back with the red exclamation mark and the message "no command" when I am in recovery? What is the meaning of this?
Click to expand...
Click to collapse
That is stock recovery

bilgerryan said:
Odin MK3 unrooted. If that doesn't fix your problem I don't know what will.
Click to expand...
Click to collapse
bilgerryan said:
That is stock recovery
Click to expand...
Click to collapse
That's not stock recovery. I've never changed recovery. Per the thread that is "MK3 FULL stock tar extracted from Kies." And after I flashed it I was back to virgin unrooted state.
If this isn't what you are suggesting I use, what exactly are you suggesting I flash? I'll try just about anything at this point.

uscpsycho said:
That's not stock recovery. I've never changed recovery. Per the thread that is "MK3 FULL stock tar extracted from Kies." And after I flashed it I was back to virgin unrooted state.
If this isn't what you are suggesting I use, what exactly are you suggesting I flash? I'll try just about anything at this point.
Click to expand...
Click to collapse
Yeah, FULL STOCK includes recovery. I suggest you flash a custom recovery and a custom ROM. Stock is obviously causing you problems.

bilgerryan said:
Yeah, FULL STOCK includes recovery. I suggest you flash a custom recovery and a custom ROM. Stock is obviously causing you problems.
Click to expand...
Click to collapse
Is flashing a custom ROM going to trip knox if I keep stock recovery?
If a hard reset and flashing stock ROM doesn't clear this problem up I'm not convinced that flashing a different ROM is going to fix this. As strange as it sounds it seems to me like I have a hardware problem.
I'm happy enough with the stock ROM and don't feel like spending hours researching all the ROM options. Can anyone recommend the most stable alternate ROM for the S3? And I don't just mean stable as in it doesn't crash, I mean stable as in everything works as it should - camera, GPS, screen rotation, wifi, bluetooth, etc.
When I'm in stock recovery why do I have the android guy laying on his back with a red exclamation mark and the message "no command?" Is this normal for a stock rooted phone?

How to install cyanogenmod on HTC One M8?

Hi,
I searched online for 2 hours but I see a lot of mixed, outdated articles, videos. For example Hasoon's app link doesn't work, or the cyanogenmod installer link for your phone is giving me 404.
I don't want to do something stupid so can someone tell me or show me a guide on how to install this?
My phone is from Rogers (contract ended). I just want a fast and light weight android without bloatware and nice features.
Will I have to find a cyanogenmod release from someone who use Rogers, or can you use the same build on that's built for M8 regardless of your phone company?
Thanks a lot.

Have you done anything to the phone yet (unlock bootloader, s-off, root, etc.) or still just fully stock?
Is the phone currently on Lollipop? You'll want updated hboot to run current CM12.1.
Don't bother with toolkits and the like. The toolkits haven't been updated in over a year, contain obsolete files, and that will cause you more problems than anything. The steps are not that hard to do "manually", and that is a much better learning process. The toolkits shortcut that learning process; putting you in a position to get into a jam, with no knowledge of how to get out of it.

Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
I downloaded these to my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Thanks again

lachdanan said:
Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
Click to expand...
Click to collapse
No need to flash SuperSU to root after flashing CM.
Go into Developer's Options in phone's settings (may need to tap version number 7 times to make Dev Options appear) then turn on root there.
lachdanan said:
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
Click to expand...
Click to collapse
Before doing anything, make a TWRP backup of your current (presumably stock Sense) ROM.
Then backup any user data you want to keep, by method of your choice (Titanium Backup, cloud, copy to PC, etc).
Then do a wipe. I would only recommend the default Wipe option (user data, cache and Dalvik) in TWRP. Right in TWRP, it says "most of the time, this is the only wipe you will need" (or words close to that effect) and it says that for good reason.
You certainly don't want to wipe "everything". If you wipe internal storage, you will lose the TWRP backup I just told you to make. Plus you will wipe the ROM and gapps zips you are going to flash, if you put them on internal storage.
Some folks swear by wiping system when flashing ROMs. I don't like this, since if for some reason the ROM fails to flash, you are then stuck with no OS (although you will have a TWRP backup, that I just told you to make). If you run into problems, you can always wipe system later and flash again. But honestly, after many ROM flashes on several different devices, and I've never once had to wipe system, that I recall. Unless of course the ROM instructions require to wipe system. If that is the case, follow the instructions.
After default wipe, flash the ROM, and flash gapps. Then reboot.
lachdanan said:
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Click to expand...
Click to collapse
I don't follow what the problem is. It looks like you have the files on a PC. Just connect your phone by USB, then copy and past the files to the phone's internal storage.
Don't know why you want to store the files "outside the phone" (and not on the PC) unless you are talking about wiping internal storage. Again, it isn't necessary to do that.
lachdanan said:
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Click to expand...
Click to collapse
It usually takes a bit of time for a new Android version to be ported over to a respective device. Than a bit more time, for it to be fairly stable. So its up to you, but I say why wait. You can always flash again when CM13 (or whatever its going to be called) is released on the M8.
One of the things about flashing ROMs, is it can be addictive. So if you have the urge and time to do it now, just do it!
lachdanan said:
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Click to expand...
Click to collapse
I actually don't use CM on the M8, so check the CM thread for any discussion on this.
Even if OTA updates aren't functional (no idea if they are or not), you can often download and "dirty flash" new updates (like nightlies). Dirty flash, means you just wipe cache and Dalvik and flash the ROM, keeping user data. Its very fast, since you don't need to setup the phone again.
Although, sometimes a dirty flash won't work, and you need to do a full flash. When CM13 comes out, you will probably need to do a full wipe before flashing it. And likewise, you probably won't want to do an OTA update to CM13 either.

Thanks a lot man, you cleared many of my questions. Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
But since you said don't delete system, then this is not an issue?
Also by system, does it mean actual stock android system files? Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Thanks again

lachdanan said:
Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
Click to expand...
Click to collapse
Nope, the storage is actually partitioned into something like 41 separate partitions: system, hboot, recovery, radio, data, boot, and (of course) many more.
So when you say you want to wipe "everything" I said you don't want to do this, and I really mean it.
Plus, one of the Advanced wipe options in TWRP is the removable SD, which most folks will not want wiped, most of the time.
So again, use the default wipe option in TWRP. Only pick the Advanced options, if you know exactly what you are doing, and fully understand the result of wiping that selection.
The "default" TWRP wipe just wipes user data, cache and Dalvik. Internal storage (which is data/media) is actually not touched, and that is most likely where you placed the ROM and gapps files (plus its the default location for TWRP backups, Titanium Backup and some other things).
lachdanan said:
But since you said don't delete system, then this is not an issue?
Click to expand...
Click to collapse
Correct.
lachdanan said:
Also by system, does it mean actual stock android system files?
Click to expand...
Click to collapse
If you are still on the stock ROM (haven't flashed any ROM yet, was I assume is the case) then YES, system partition is where the actual stock ROM (stock Android system files) are currently located.
lachdanan said:
Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Click to expand...
Click to collapse
Nope, when a ROM is successfully flashed, it will wipe system, then install the new ROM on the system partition.
This is another reason why I say its not necessary to manually wipe system in TWRP. It will happen anyway when you flash the ROM. But if for some reason the ROM fails to flash (not unheard of, for various reasons), you will still have have a working phone if you didn't wipe system.

Thanks. I made a stupid mistake before reading your last post, now it seems like my phone's data storage is completely empty I restarted into bootloader and added TWRP to it again using Windows. But then I chose restart on that bootloader menu and now the phone screen is stuck in HTC android boot screen. I couldn't turn the phone off or restart. Do you know how to fix this?

I managed to fix it and now I am in cyan Looks really good, I will be customizing it now but it feels snappy
Thanks again man

phone says its full?

Hey guys Im running stock rooted and for some reason my phone SD is saying im full. I have literally nothing on it. Any ideas?
I tried once to install a ROM but it borked so I went back to a backup I had and it was fine.
Via windows it says my SD only has around 8 gigs used but android is saying 24?!?!?!?
WTF MATE?

Try wiping userdata in twrp.

Illogi.xbone said:
Try wiping userdata in twrp.
Click to expand...
Click to collapse
thanks, I was about to try and just redo the device with a ROM. Clear cahces and such.
I was actually wrong, every time I go into the phone in windows its giving me different storage use #'s. One time its 8 then 17 then 23 then 9. its weird. I think when I tried dirty flashing it just screwed it all up. I have nothing on the SD I care about really so maybe Ill just back up what I want (TWRP backup and titanium apps) and start from scratch if I Cant solve this.

That might be the best. Try backing up to an OTG then completely wiping and installing a fresh ROM. After backing up apps and such.

ugh IM having trouble using any roms on my 5x. No matter the way I install the phone always boots to "internal problem with device"
Ive tried installing different roms (I only like stock style ones) and the vendor.zip and it just doesnt work for me. Ive gone back to my backup for the moment until I figure this out. Never had these issues with my nexus 5

this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!

tevil said:
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
Click to expand...
Click to collapse
Try 1st: Completely wipe device, System, data etc. Including Internal Storage and flash a new rom. If that does not fix the issue try flashing stock firmware and start from scratch. Use THIS guide to flash the stock images.

Flash vendor.img that matches your rom base. MMB29Q is the February OTA base. February AOSP roms are based on MMB29U master code but MMB29Q vendor file works fine.
For password issues after TWRP restore, do this: http://forum.xda-developers.com/showthread.php?t=3245070
Sent from my Nexus 5X using Tapatalk

SERIOUS ISSUE!
Bricked the phone!
CRAP, this whole thing went downhill. Can get into TWRP, and get the android crash logo (triangle) was trying to restore back to stock to start fresh and it bombed completely!
Any tips!!!
Been a while since I used ADB or fast etc, but man if I have to relearn I will

Question Stock F3 Global (No system modifications) stuck in a bootloop

Dear community,
An old XDA member here, who forgot everything about flashing or fixing a broken phone system.
My Poco F3 just went into an infinite bootloop, and I have no idea why is that since I didn't perform any custom modifications to the system, absolutely none!
I can access the recovery menu, which was useless as Safe Mode or any other mode didn't help, the phone can't boot.
Connecting with MIAssistant doesn't work as well, I can see the phone is connected in hidden USB devices on the PC as an Android ADB interface, but the MI software can't see it.
I can also access FASTBOOT, but I have no idea what to do with it. MIAssistant detected it but it asked to connect in normal mode?
A strange artifact is showing on the bootscreen every time, some random colors on the logo, something corrupted? I have no idea...
Is there anything I can do without wiping the phone? It's my daily driver and I need the data saved on it.
I will be monitoring this thread for the next few hours, please don't hesitate to suggest potential fixes or ask questions.
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Update:
The phone finally made it into Safe Mode, I am backing up my data, can't reboot it yet until the 125GB are on the PC.

Is the bootloader locked? Has the phone suffered any physical damage?
The logo looks as if either the screen, its connector or the motherboard were broken. I hope to be wrong.
Maybe try the steps from here except I wouldn't wipe data nor do a factory reset (yet). I hope someone more knowledgeable and experienced than me can advice something better.

heybaybee said:
Is the bootloader locked? Has the phone suffered any physical damage?
The logo looks as if either the screen, its connector or the motherboard were broken. I hope to be wrong.
Maybe try the steps from here except I wouldn't wipe data nor do a factory reset (yet). I hope someone more knowledgeable and experienced than me can advice something better.
Click to expand...
Click to collapse
Thank you for the effort,
No, the phone didn't suffer any physical damage, I also have no idea about the bootloader as I haven't flashed or try to flash anything on it.
I managed to copy some of my important data when it decided to boot up, then it went into bootloop again.
I wiped it, as I had no other way to confirm that the phone is broken at the hardware level. After the wipe and reinstallation, it went into bootloop again.
I will have to throw it somewhere and buy a Samsung.

sos_sifou said:
Thank you for the effort,
No, the phone didn't suffer any physical damage, I also have no idea about the bootloader as I haven't flashed or try to flash anything on it.
I managed to copy some of my important data when it decided to boot up, then it went into bootloop again.
I wiped it, as I had no other way to confirm that the phone is broken at the hardware level. After the wipe and reinstallation, it went into bootloop again.
I will have to throw it somewhere and buy a Samsung.
Click to expand...
Click to collapse
Hi,
Samsung's are Yuk, expanding batteries and the dreaded KNOX,
my F3 was brought from the UK and came with 2 Years Warranty,
As mentioned above, have you unlocked your bootloader, if not why not, if your not fussed about your F3 then you have nothing to loose, you could try installing a new rom, i use EVO-X and its amazing,
I love the F3

johnr64 said:
Hi,
Samsung's are Yuk, expanding batteries and the dreaded KNOX,
my F3 was brought from the UK and came with 2 Years Warranty,
As mentioned above, have you unlocked your bootloader, if not why not, if your not fussed about your F3 then you have nothing to loose, you could try installing a new rom, i use EVO-X and its amazing,
I love the F3
Click to expand...
Click to collapse
You're right, I was a bit angry, all phones can break, including iPhones and Samsungs.
Claiming warranty is a bit tricky for me, as I purchased the phone during my short stay in the UAE, and I won't be going back until next year.
Now I think there is a part of the system files that has been corrupted, because when the phone reboots, it will go into bootloop, but if it boots after some 30 to 40 minutes of bootlooping, it will stay running for a certain period of time.
If system files are corrupted, I don't think a wipe can fix it, as it deletes user data and apps, but I don't think it fixes system files used to boot the device.
Do you have a link to a step-by-step tutorial to unlock the bootloader and flash a stock ROM. I don't really need any special features from custom ROMs, other than the phone to work for the next 3 to 4 months without problems.

Hi,
You can try fastboot update.
First download and decompresse the latest fastboot ROM for your device you can find here.
Then download latest android platform tools copy all it's content into the ROM folder.
Finaly run flash_all_except_storage.bat (this will preserve your data), if no sucses you can try flash_all.bat, but this will erase all your personal data.

Dear all,
After more testing, it seems the phone doesn't have corrupted boot files, but it just can't run when the CPU is under load.
I have made several tests, when the phone is relaxed, battery saver option is ON, it doesn't reboot, but once battery saver is OFF, and I push the CPU a little using a benchmarking software or a CPU stress test, it reboots.
Thus, the problem is with the hardware, I wonder how many people are suffering from such an issue or is it isolated and only a handful devices are affected by this?

The broken boot logo makes it look like a hardware problem as well. Did you buy it new? Did you game on it or keep it at or above 40-50 degrees C for prolonged periods of time?
I've had Poco X3 Pro that would freeze when using navigation in the summer once in a while. Happened few other times as well.
Trying to flash the (newest) stock ROM may be worth trying. Maybe selling it for parts is an option.

ferreol-fr said:
Hi,
You can try fastboot update.
First download and decompresse the latest fastboot ROM for your device you can find here.
Then download latest android platform tools copy all it's content into the ROM folder.
Finaly run flash_all_except_storage.bat (this will preserve your data), if no sucses you can try flash_all.bat, but this will erase all your personal data.
Click to expand...
Click to collapse
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!

zalm_98 said:
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!
Click to expand...
Click to collapse
Hi,
I struggled a bit in the early days moving away from my LG G7,
you could try my post on the Evo-X thread,
[A13]Evolution X for POCO F3/Mi 11x[alioth][OFFICIAL]
Evolution X 7.0 for the POCO F3 [alioth] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
following parts 1 to 1b,
you could also try Temporary Recovery using part 6.
None of this will work unless you have a unlocked bootloader and FASTBOOT working on your PC.
You could also try Miflash to install the correct drivers and see if your device is detected in FASTBOOT,
A word of warning never choose "clean all and lock" in miflash unless you are running the correct stock firmware for your device as you could end up with a BRICKED device.

zalm_98 said:
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!
Click to expand...
Click to collapse
Hi,
Are your device drivers correctly installed on the computer?
After plugging your phone into fastboot mode on your PC, look in the Windows manager if the device is installed correctly. Otherwise, go to Windows Settings-> Windows Update-> Optional Update. And see if there is any driver update that can help you.