Since lot of peoples are complaining about their phones going suddenly slow and lagging after some days of flashing a new ROM, so there is a guide how to fix this issue
Importants notes:
-This solution will provid you to format system partition , it means you will lost all custom mods you have installed on it (Xposed, Fonts), but don't worry you will be able to re-install them after.
-I suggest you to do a backup before anything.
-This fix only lags/slowness due to eMMCs, so if your phone still lagging after blame your ROM or the Kernel you use or maybe the 1000 apps you have installed on it.
What's eMMCs and why this lag is happening ?
I suggest to read full thread about it here : https://goo.gl/FchzSN (Thanks @doesntexits)
How to know if my device is affected by this issue?
Use this app https://goo.gl/gpY8tq
After install test your Internel Memory writing speed(Hold Internel Memory then select Quick), in the end it sould be at least 20mb/s.
If not so you have some lags on your phone.
How to fix it?
-Download and flash this version of TWRP: https://goo.gl/2znyCx (Flash it using your old TWRP )
-Reboot the phone to recovery again (You should see TWRP version is 3.0.1 now)
-Go to Settings , make sure (Use rm-rf instead of formatting) is unthicked
-Now go back and go to Wipe ,then Advanced Wipe, select only System and Swipe to Wipe
-Wait until it finishe , it could take lot of time (About 20 Minutes), have a cup of tea while you wait .
-Repeat the System Wipe for at least 20 times (More or less depend on users, but to be safe do it 20 or more ).
-Then It's done you can install any ROM you want, after installing the new ROM go check your Write Speed again with same app to see diffrences, if it still under 20mb/s do more System Wipes .
-After your lags are defently fixed you can Use rm-rf instead of formatting to flash ROMs or anything you like faster.
After this you should have your phone at good writing speed.
If you have any kind of question be free to ask me.
Credits:
- @doesntexits for original guide and solution.
- @Nikit for TWRP version.
- @mv2007 for advices and help.
Hope i didn't forget anyone.
Or you could just do 'fstrim -v /system' Optionally run the same command on /data and /cache. Works for me but YMMV. At least better than waiting six hours of repeated wiping arrrrgggggghhhhh.
my Galaxy core prime has the same problem. my phone now lagging stucking. how to fix this? will this mod help me?
rms112 said:
Or you could just do 'fstrim -v /system' Optionally run the same command on /data and /cache. Works for me but YMMV. At least better than waiting six hours of repeated wiping arrrrgggggghhhhh.
Click to expand...
Click to collapse
Sir can you explain this procedure step by step
Also is this helpful ???
---------- Post added at 01:33 PM ---------- Previous post was at 01:27 PM ----------
Sir I have one question what is the reason of using 3.0.1 version of TWRP when we have 3.0.0 version too?
Also are you or anyone else getting writing speed of 20 mbps or more......
Have anybody tried it?
I get 20 normally. Idk I haven't experienced lags so far. Screenshots show fstrim too.
rms112 said:
I get 20 normally. Idk I haven't experienced lags so far. Screenshots show fstrim too.
Click to expand...
Click to collapse
Followed your commands via TWRP recovery. Entered those commands successfully on system, data and cache.
Getting writing speed of 22.25 mbps on internal storage
It's really working for me!! i recommending
Everyone facing slow device problem, just follow these steps:
Make sure you're running @dreamstar's old TWRP version without formatting fixes (VERY IMPORTANT) (DOWNLOAD LINK BELOW)
Untick "Use rm -rf instead of formatting" in TWRP settings (again, VERY IMPORTANT)
Do a full wipe (format data, system, cache) (why don't we need to wipe data, dalvik cache in advanced wipe? because we have already done those steps when format data)
Reflash stock ROM (any versions)
And... enjoy flashing other ROMs
OLD TWRP LINK
Original Post
https://forum.xda-developers.com/showpost.php?p=67824939&postcount=383
iamkani said:
It's really working for me!! i recommending
Everyone facing slow device problem, just follow these steps:
Make sure you're running @dreamstar's old TWRP version without formatting fixes (VERY IMPORTANT) (DOWNLOAD LINK BELOW)
Untick "Use rm -rf instead of formatting" in TWRP settings (again, VERY IMPORTANT)
Do a full wipe (format data, system, cache) (why don't we need to wipe data, dalvik cache in advanced wipe? because we have already done those steps when format data)
Reflash stock ROM (any versions)
And... enjoy flashing other ROMs
OLD TWRP LINK
Original Post
https://forum.xda-developers.com/showpost.php?p=67824939&postcount=383
Click to expand...
Click to collapse
This guide is same as I wrote with just more details
:fingers-crossed:
rms112 said:
I get 20 normally. Idk I haven't experienced lags so far. Screenshots show fstrim too.
Click to expand...
Click to collapse
Me too. Havent expirienced it.
i did this command 'fstrim -v /system' alot of times and flashed stock system and i get write speed on internal 3.99 mbps
if i flashed custom rom like linage or python the system not boot up
i have lots o lags and slowness on stock
i formatted 22 times the system but still have slowness any idea? to fix my cp
muhammed Palestinian said:
i did this command 'fstrim -v /system' alot of times and flashed stock system and i get write speed on internal 3.99 mbps
if i flashed custom rom like linage or python the system not boot up
i have lots o lags and slowness on stock
i formatted 22 times the system but still have slowness any idea? to fix my cp
Click to expand...
Click to collapse
You can try this.
https://play.google.com/store/apps/details?id=com.paget96.lspeed&hl=en
Should I flash stock rom through odin? Or just flash the custom rom I was using?
QuinzyJb said:
Should I flash stock rom through odin? Or just flash the custom rom I was using?
Click to expand...
Click to collapse
Cause Im a little confused with the last part
Related
This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire GSM (cdma version here)
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 6 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. Update your radio if needed (720p require 5.x radio)
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://mirror.teamdouche.net/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
thank's to gatsu_1981 and imfloflo for inspiration
Rooting Guide
http://forum.xda-developers.com/showthread.php?t=788044
Google Addon: latest HDPI-20101114
Other release http://goo-inside.me/google-apps/
Radio Firmware: 5.x radio required (GSM ONLY)
Desire GSM radio thread
Read/Write Access System Partition (S-OFF)?
Thank's to AlphaRev [site] [xda]
Low storage for apps?
Flash the AlphaRev HBOOT Bravo N1Table (Require S-OFF)
Follow this instrunction for update without data lost (aka no data wipe)
Still low storage for apps?
Install an A2SD solution: Firerat or Darktremor
i recommend the Firerat solution: CM specific, less space usage 25kb vs 6mb, bind mount, no boot loop, auto restore after cm rom update (from 1.35b)
Fantastic, thanks Kali!
bemymonkey said:
Fantastic, thanks Kali!
Click to expand...
Click to collapse
+1
And don't post questions before reading the 300+ pages of this thread: http://forum.xda-developers.com/showthread.php?t=719544
Just kidding. But I thought a reference to the old thread could be useful.
yuo should add a link to alpharevs s-off and modified partition table
deleted .
the developt is in 6.1 cyanomod nightly updated right?
Latest nigthlies have been rock solid for me. My only complaint is the annoying credential storage password, which I must enter every time I reboot the phone if I want to connect to 802.1x wifi networks. Other than that, 16x have been flawless.
*cheers kali on*
Finally an up to date thread. Reading your post I learned something. I didn't know firerat a2sd now works with cyanogen.
Anyone got experience migrating from dta2sd to firerat?
Swyped with my S-OFF'd brain using teh internetz
Is there a patched Amon Ra recovery image that allows you to use the N1 partition table ?
why woud you patch it?? just use n1 table and default amon ra
madman_cro said:
why woud you patch it?? just use n1 table and default amon ra
Click to expand...
Click to collapse
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.
ganjamu said:
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.
Click to expand...
Click to collapse
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom
madman_cro said:
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom
Click to expand...
Click to collapse
Thanks! I will give it a shot tonight and let you know how it goes.
Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore
stingerpl said:
Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore
Click to expand...
Click to collapse
Yes! Absolutely no problem... (but if you already have recovery, then there is no need to flash a new one)
Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.
dipje said:
Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.
Click to expand...
Click to collapse
Have you tried diasabling signature verification?
vnvman said:
Have you tried diasabling signature verification?
Click to expand...
Click to collapse
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
EDIT: Solved it. Apparently there is a bug in my recovery. If I use the recovery the mount my sdcard over USB, afterwards /sdcard can get unmounted. So it couldn't find the .zip file I was choosing because /sdcard was not mounted. Why it was still possible to list the contents on the sdcard is a mystery to me. That must mean the recovery mounts /sdcard, lists the contents and then unmounts it again, and _then_ tries to start the update?!?
Anyway, going into the 'mounts and storage' menu and choosing 'mount /sdcard' suddenly made sure things worked again.
Really stumped how this happened.
dipje said:
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
Click to expand...
Click to collapse
What recovery image are you using? If you have amonRA you might try to fix this launching clockworkmod via fake flash and using that one to install the update. Otherwise if you already have clockwork you might try flashing amonRA via hboot and use that one...at times i can't perform something with one of the two recoveries, and using the other one often solves every issue for me
Hey guys,
I'm trying to install this rom on my Skyrocket but I'm getting a Status 7 installation aborted when I try to install the .zip after wiping Data / cache / dalvik and formatting system (as explain in the instructions).
I tried searching that thread, I found one instance of a status 7 installation aborted comment but it was basically answered with "OMFG WHY DOES NO ONE READ THE INSTRUCTIONS" which is useless because the instructions simply state:
-put on your internal sdcard
-boot into cwm and do a Nandroid back-up
-wipe/format system, wipe/format data, wipe cache and wipe dalvik-cache.
-flash ROM, then the SU files--http://d-h.st/fOD
-flash JB_Gapps...-- gapps-jb-0811[marketFIX].zip - 78.59 MB
-reboot and enjoy-
I fail to see anything I've done wrong.
I have tried redownloading / re-copying to my phone several times incase it was a corrupt file but I don't think so. Do I need anything installed BEFORE I install this hybrid? I would assume that instructions would mention that if it was required but as you can see, it doesn't.
Sorry for being a noob and what not, I generally don't have trouble following instructions so I think a step is missing or I'm misinterpreting something.
Thanks for any help!
Some ROM install scripts check ro.product.device or ro.build.product to verify that the device is compatible with the ROM being flashed.
Long story short, you need to update CWM to a more recent version. Personally, I like this one: ClockworkMod v6.0.1.5 Touch v14
Be sure to thank sk8.
cschmitt said:
Some ROM install scripts check ro.product.device or ro.build.product to verify that the device is compatible with the ROM being flashed.
Long story short, you need to update CWM to a more recent version. Personally, I like this one: ClockworkMod v6.0.1.5 Touch v14
Be sure to thank sk8.
Click to expand...
Click to collapse
I remember seeing "ro.something" as the text flowed after selecting the zip but was too fast to check. I will try this when I get home, thank you very much!
Hi all,
I want to install Andromadus ROM Build 13 on my DS and currently have stock 2.3.3 installed.
As this will be my first custom ROM and also I couldn't find any how-to to install Andromadus on an HTC Desire S so, I am posting it here.
I have 4EXT touch recovery, S-OFF'ed and the HBoot is downgraded to 0.98.2000 (PG8810000).
So, where do I start? I am making backups using 4EXT recovery and downloading "flinnycm101_saga_13.zip" & "gapps-jb-20121212-signed.zip" from http://andromadus.flinny.org/?q=node/24
but as posted on the same page..I have a doubt of whether to flash the MDDI kernel too? Is that required to be flashed on an HTC Desire S ?
Any full length how-to's will be appreciated.
General guide to flash any rom can be found here
No need to flash kernel. Just flash the rom and gapps.
You might also want to use Titanium Backup to backup any apps from your stock rom and restore to the new rom.
oddoneout said:
General guide to flash any rom can be found here
No need to flash kernel. Just flash the rom and gapps.
You might also want to use Titanium Backup to backup any apps from your stock rom and restore to the new rom.
Click to expand...
Click to collapse
So, Can I use 4ext's recovery app to boot into recovery mode >> then format System
>> Format Data
>>Format Cache
>> then Format Boot
>> Wipe Data/Factory reset (1st option in wipe/format menu)
>> Wipe Dalvik Cache
>> n then finally install zip (ROM) from sd card and flash the rom..
>> then flash then gapps zip?
Also, isn't 4ext's backup option backs up my apps, app's data and the contacts too? :| um..what about the draft message(s) ? will that be backed up too using 4ext recov.?
But I guess I won't be able to restore them on an individual basis when I am done flashing the new ROM? As 4ext's created backup can only restore the full backed-up data which includes the old ROM itself!
Update: backing up apps+data using Titanium backup pro..so that will backup my contacts+ sms+draft sms too..right?
Any advice?
Guys..I did the following:
went to 4ext's recovery app in recovery mode
>> then formated System
>> Formated Data
>> wiped* Cache (as there was no option for: "format" cache)
>> then Formated Boot
>> Wiped Data/Factory reset (1st option in wipe/format menu)
>> Wiped Dalvik Cache
>> n then finally installed zip (ROM) from sd card and flashed the rom..
>> then flashed then gapps zip
Now after 1st reboot from recovery..I am stuck at white background saying HTC..its been quite a few mins around 3-4mins
Shall I re-flash the ROM ?
Please help :s
sky770 said:
Guys..I did the following:
went to 4ext's recovery app in recovery mode
>> then formated System
>> Formated Data
>> wiped* Cache (as there was no option for: "format" cache)
>> then Formated Boot
>> Wiped Data/Factory reset (1st option in wipe/format menu)
>> Wiped Dalvik Cache
>> n then finally installed zip (ROM) from sd card and flashed the rom..
>> then flashed then gapps zip
Now after 1st reboot from recovery..I am stuck at white background saying HTC..its been quite a few mins around 3-4mins
Shall I re-flash the ROM ?
Please help :s
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1943524 read this!!!
acultr said:
http://forum.xda-developers.com/showthread.php?t=1943524 read this!!!
Click to expand...
Click to collapse
h ****..I just pulled it out :'(
well..it again got stuck into the same boot screen..
funny thing is I din't even pressed the power button it straightaway booted up? :s
ok...wrote the command "adb reboot recovery"
I am back into the 4ext recovery menu
now what's next?
sky770 said:
h ****..I just pulled it out :'(
well..it again got stuck into the same boot screen..
funny thing is I din't even pressed the power button it straightaway booted up? :s
ok...wrote the command "adb reboot recovery"
I am back into the 4ext recovery menu
now what's next?
Click to expand...
Click to collapse
read the previous post
acultr said:
read the previous post
Click to expand...
Click to collapse
Is there a way I can determine which screen do I have..now that I have already flashed my device and cannot access es explorer and stuff?
I do have access to 4ext recovery and adb console :|
Is it possible to navigate to / or /sys using adb console?
Also, suppose even if I do have the MDDI type of screen and I flash the MDDI kernel img but will that mean that I won't be able to adjust screen brightness and stuff?
Just flashed the MDDI kernel..waiting for reboot proc to complete...
I hope this doesn't fail this time.. :|
Re: [Q] How to start Flashing Andromadus ROM (Build 13) Android 4.2 on HTC Desire S?
As a suggestion, flash the mddi panel if it boots then you can be fairly certain your on the right path. At the moment there is no brightness control for mddi panel but there are some alternatives in the thread i directed you to
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom
jugg1es said:
As a suggestion, flash the mddi panel if it boots then you can be fairly certain your on the right path. At the moment there is no brightness control for mddi panel but there are some alternatives in the thread i directed you to
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom
Click to expand...
Click to collapse
now its been ~2-3mins still stuck on the HTC screen :| (even after flashing the MDDI kernel)
Do I have to re-clear/wipe the cache..after flashing the ROM? or re-flash the ROM itself? (as I have read in some posts that it usually works after clearing the dalvik/cache and/or reflashing the same ROM again)
Can you provide me with the command I can use on adb console to find out the brand of my screen's manufacturer ?
Update:
I had flashed the ROM and then flashed the google apps pkg and then after a reboot now again flashed the MDDI kernel.
Is it the correct sequence to install the MDDI kernel?
Need help guys..its been more than 5 mins since I am stuck on the screen..what should I do now?
Pull out the battery..to give it a hard reset?
Please help :'(
I have shifted my issue to this thread: http://forum.xda-developers.com/showthread.php?p=37933379
Re: [Q] How to start Flashing Andromadus ROM (Build 13) Android 4.2 on HTC Desire S?
sky770 said:
Need help guys..its been more than 5 mins since I am stuck on the screen..what should I do now?
Pull out the battery..to give it a hard reset?
Please help :'(
Click to expand...
Click to collapse
Best thing to do is not panic, you can still access recovery. What i would do in this situation is start again from the beginning with fresh downloads checking you have correct gapps package for the rom(check md5 of all files) using 4ext format all except sd card and reflash new downloads. Reboot into recovery using adb, try not to pull the battery unless you really have to then if you do wait a couple of seconds before replacing it
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom
jugg1es said:
Best thing to do is not panic, you can still access recovery. What i would do in this situation is start again from the beginning with fresh downloads checking you have correct gapps package for the rom(check md5 of all files) using 4ext format all except sd card and reflash new downlosd
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom
Click to expand...
Click to collapse
Thanks for replying..
um..can you please..follow with me in this thread here: http://forum.xda-developers.com/showthread.php?t=2146151
Thanks a lot :|
PS: Sorry..I am all on fire..as this is the only phone I have :| (except my sucko Nokia )
sky770 said:
Need help guys..its been more than 5 mins since I am stuck on the screen..what should I do now?
Pull out the battery..to give it a hard reset?
Please help :'(
Click to expand...
Click to collapse
go to recovery restore your prev. ROM and check the panel
Step 1. Find out which screen panel your device has:
1) Download and install Android Terminal Emulator from Google Play Market
2) Open the application and type in these commands:
(WARNING: to use these commands - you must be rooted with either Superuser or SuperSU AND have BusyBox installed on your phone)
su
dmesg|grep -i panel
If the app shows you any text with word "sony" in it - then your device has a screen panel made by Sony (obviously). If that's the case - you can just close this thread at once and don't worry that your device might freeze at "HTC Quietly Brilliant" screen after flashing a ROM. Otherwise, proceed forward.
OR
1) Open up a file manager that has an ability of browsing any partition above the default SD-card directory and can access the system partition
You can use either ES File Manager or Root Explorer
2) Navigate to /sys/android_display
If there is a file called "sony ****** wvga" - then you have a Sony panel. Otherwise - you device has a panel by Hitachi.
Step 2. Download a MDDI kernel developed by Andromadus:
For Android 4.0.x & 4.1.x, use this link --> http://goo.im/devs/Super/andromadus/...kernel_82n.zip
For Android 4.2.x, use this link --> http://andromadus.flinny.org/sites/a...212.zip&nid=16
Step 3. Flash the MDDI kernel:
If you are S-OFF --> just flash the .zip file with the kernel after flashing the ROM and GAPPS package through "install zip from sdcard"
If you are S-ON --> use the following instruction:
Thanks for Fatal1ty 18 RUS:good:
Re: [Q] How to start Flashing Andromadus ROM (Build 13) Android 4.2 on HTC Desire S?
sky770 said:
Thanks for replying..
um..can you please..follow with me in this thread here: http://forum.xda-developers.com/showthread.php?t=2146151
Thanks a lot :|
PS: Sorry..I am all on fire..as this is the only phone I have :| (except my sucko Nokia )
Click to expand...
Click to collapse
Stop opening fresh threads, people tend to ignore you More if you constantly open threads. I had a couple of panicky moments when i first did mine. Just take a deep breath and start again
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom
The MD5 was not same ! The MDDI kernel I flashed it did not had the same MD5 as I the one I redownloaded..
And now..I cannot reboot into recovery by using adb.. :'(
I tried "adb reboot recovery" command
And it gave me an error saying: error: device not found
How can I reset the adb?
PS: sorry MODs but I wanted to present my problem clearly so had to open a thread with a clear description.
sky770 said:
The MD5 was not same ! The MDDI kernel I flashed it did not had the same MD5 as I the one I redownloaded..
And now..I cannot reboot into recovery by using adb.. :'(
I tried "adb reboot recovery" command
And it gave me an error saying: error: device not found
How can I reset the adb?
PS: sorry MODs but I wanted to present my problem clearly so had to open a thread with a clear description.
Click to expand...
Click to collapse
command:adb devices
acultr said:
command:adb devices
Click to expand...
Click to collapse
prints:
List of Devices attached
it is showing nothing :'(
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS
dima234 said:
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS
Click to expand...
Click to collapse
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?
meriox said:
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?
Click to expand...
Click to collapse
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.
dima234 said:
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.
Click to expand...
Click to collapse
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.
meriox said:
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.
Click to expand...
Click to collapse
yea getting the same problem here.
cant mount system
cant mount cache
and most of all when install custom ROM. cannot continue since non of those partitions cannot mount properly.
and other errors are flooding the recovery, we have tried Philz, CWM, TWRP. same annoying problems.
Hello,
On another website I found this:
"All worked fine but that like of command in terminal you put there isn't right, i did this
$ su [and then enter]
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32 [and then enter]
# reboot recovery [and then enter]
PS: the $ comes automatically when you start the terminal emulator app; the # comes automatically after you allow the super user [in $ su]
Do consider all the "Spaces" between symbols and paths!"
Has anyone used this method?
syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
Thanks worked for me :good:
bricked
I've got these errors on my htc desire x, I made a backup, after that, I try to flash a new rom, with the steps written in the first post. The result was: after the htc logo, it showed a black screen! I try to restore the backup, but I cant restore!!!!! I've got soft brick, so I take it a service. I hope, they can fix it
Samsung Galaxy Tab 2
AOSP - Project
This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)
[#DONATETOME]
FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.
Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.
Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.
Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.
Q: I found a bug.
A: Nice finding my friend Please provide needed logs - ADB will be your best friend, if you are replying in a development thread
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.
I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here
Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen
(... forgot about the releases between ...)
2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P51xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2017-04-30
Thank you Andi! I've been hoping for this! Up and running, really really smooth.
Sent from my GT-P5110 using Tapatalk
Thank you Sir.. Can't wait to try it out.
Sent from my Nexus 6 using XDA Premium HD app
stuck at samsung galaxy tab page
Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there
luckywang95 said:
Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there
Click to expand...
Click to collapse
No. Data or cache on f2fs? If yes format them back to ext 4.
Also make sure you did a clean install.
Try without gapps maybe, if it boots you can flash gapps after that.
Hello
p5110
installed no problem
thanks
regards
Android-Andi said:
No. Data or cache on f2fs? If yes format them back to ext 4.
Also make sure you did a clean install.
Try without gapps maybe, if it boots you can flash gapps after that.
Click to expand...
Click to collapse
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:
luckywang95 said:
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:
Click to expand...
Click to collapse
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.
If it boots, boot back into recovery and flash gapps.
If still not work, start clean flash again and get a recovery.log directly after flashing.
Android-Andi said:
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.
If it boots, boot back into recovery and flash gapps.
If still not work, start clean flash again and get a recovery.log directly after flashing.
Click to expand...
Click to collapse
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:
luckywang95 said:
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:
Click to expand...
Click to collapse
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Android-Andi said:
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Click to expand...
Click to collapse
yes. i chose allow changes. my device is p5100. installation failed. i will get recovery.log now and upload to u soon.
---------- Post added at 10:45 AM ---------- Previous post was at 10:31 AM ----------
Android-Andi said:
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Click to expand...
Click to collapse
I have a new problem. Im still a new member so im not allow to pots a link or attach any file to here. how am i able to send the log file to you?
luckywang95 said:
I have a new problem. Im still a new member so im not allow to pots a link or attach any file to here. how am i able to send the log file to you?
Click to expand...
Click to collapse
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send
Android-Andi said:
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send
Click to expand...
Click to collapse
i have sent it to you through private message. i will do it again here.
drive.google.com/file/d/0B3WN3t7uFUZvcFh1cTRlVzdacEU/view?usp=sharing
its google drive.
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:
luckywang95 said:
and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:
Click to expand...
Click to collapse
Good to know... Mh... Could you get me a logcat and dmesg?
I had a similar issue on p3110, but i am sure i fixed it on p5100 before compiling... Maybe something else is wrong then...
Android-Andi said:
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
Click to expand...
Click to collapse
but i have the same directory when i flash the cm12?
---------- Post added at 11:58 AM ---------- Previous post was at 11:12 AM ----------
Android-Andi said:
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
Click to expand...
Click to collapse
well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...
luckywang95 said:
but i have the same directory when i flash the cm12?
.
Click to expand...
Click to collapse
ok, then it's not the cause
well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...
Click to expand...
Click to collapse
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Android-Andi said:
ok, then it's not the cause
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Click to expand...
Click to collapse
its not connected to computer... i cant use adb.... i tried installing all driver... but still cannot... adb devices shows nothing..:crying:
---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------
Android-Andi said:
ok, then it's not the cause
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Click to expand...
Click to collapse
sorry, just now is my usb hub not working. not the device. dmesg and logcat i uploaded to google drive. in this folder. it included the recovery.log just now.
https://drive.google.com/open?id=0B...9Ydkw3T0VfZUhWS0ticHdtYnhOQ1hWTFhhRkVtSEh3QVE
logcat is empty. but it is still in the folder.
Hello AndroidAndi
First, thank you for this rom and I have not had any problems during installation.
Full wipe (data, cache, dalvik, format system) and installation of Gapps tk_gapps micro-modular-5.1.1.
If you want sreens? :
Sorry for my English
Dirk