Hello...
I flashed this version 2.8.6.0 of TWRP for my RN2 but it takes long temps to load around one minute and one minute an a half. Is it normal or there is something wrong...?? I don't have any problem to flash anything besides this annoyance.
I already tried the "Materialized" version TWRP v2.8.7.0. but have changed because I read some where that it was buggy... was a little faster to load tho.... Also because I got used to v2.8.6.0. it has the same interface of the TWRP flashed on my Nexus 4.
I think it's normal, I never had problem with it except long time to load. Currently i'm using the materialized v2.8.7.0 and so far no problem wiping/installing/backup/restore.
cml.snc said:
Hello...
I flashed this version 2.8.6.0 of TWRP for my RN2 but it takes long temps to load around one minute and one minute an a half. Is it normal or there is something wrong...?? I don't have any problem to flash anything besides this annoyance.
I already tried the "Materialized" version TWRP v2.8.7.0. but have changed because I read some where that it was buggy... was a little faster to load tho.... Also because I got used to v2.8.6.0. it has the same interface of the TWRP flashed on my Nexus 4.
Click to expand...
Click to collapse
I also used 2.8.6, it booted to recovery a bit slow but very reliable.
Sent from my 2014817 using Tapatalk
OK... I was worried because on my nexus 4 it boot really fast.
Thanks both of you for your feedback.
Waiting for another member feedback to be sure tho....
Related
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
NOTE: Most, if not all of these ROMs are designed for ATT.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
I had the same problem and switched to Philz Touch instead of TWRP, I like TWRP a lot more and most people say its more stable, but that's what fixed it for me.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Umm... Don't reboot
Sent from my SCH-I545 using xda app-developers app
I have read, on CM's site somewhere I believe, they recommend using CWM for a recovery. I use 6.0.4.4 and have no issues with getting stuck at the boot logo. There was an issue with that but CM addressed it in one of the nightlies about two weeks ago.
I had that issue when I had a newer twrp recovery I have the .2 whatever one and I havnt had it since.
Hi guys,
A while back I rooted my Galaxy S3 gt-i9300 international and loaded the S4 Revolutionairy ROM onto it which worked perfectly.
This weekend I decided to flash a new ROM since I have a new phone now and I want to give this one to my girlfriend to replace her old S2.
First I had to upgrade CWM to flash a 4.4 ROM and so I did via Odin. No problems here.
If I perform a wipe data/factory reset it says it can't mount the data partition. A manual mount also gives back an error. If I do load a ZIP file from the external SD card it gives back an error that it can't access data partition, error 7
Looking around I find dozens of people with similar problems but not exactly the same. So I'm a little afraid I make the wrong decision here. The phone keeps booting fine in the S4 Revolutionary ROM but of course the factory reset part did work so every time I have to log into my Google account.
I think I have to flash a factory ROM via Odin first, so basically revert it back to stock completely. Anyone out there who can point me in the right direction or has a better idea?? Thanks!
Did you tried to flash TWRP recovery 2.7.x and then try to install a new rom.Download the latest version of recovery directly from TWRP website
Sent from my GT-I9300 powered by ArchiDroid+ArchiKernel
No. Since the galaxy s1 I use cwm.
But it's worth a shot. I'll keep you posted.will try this later on.
Verstuurd vanaf mijn GT-I8190 met Tapatalk
vinz3nt said:
No. Since the galaxy s1 I use cwm.
But it's worth a shot. I'll keep you posted.will try this later on.
Verstuurd vanaf mijn GT-I8190 met Tapatalk
Click to expand...
Click to collapse
Flash latest Cwm but i am afraid that Odin and stock rom will only work. More work but not that much
Sent from my GT-I9300 using XDA Free mobile app
I don't like to flash with CWM. There's no way to flash with Philz Touch? Use it, way better. When people ask me to flash a custom ROM, I use Philz. It's prepared make a factory reset and prepare your phone to a new ROM without problems.
But if you're going through with CWM, I suggest to get the lastest version and try again.
It worked fine with TWRP 2.7.1.0
I really love it, looks very good, lots of options and just really working fine!
I just flashed the Liquid Smooth ROM with Android 4.4.4. My phone is really really fast now!
Thanks a lot
Hi,
I flashed Carbon ROM 4.4.4 you can find it here
Or dowload directly from here.
The Google Apps can be download from here, I used the Nano version, only the Google base, Google services and Google search are incorporated so byebye Google+ and al unwanted stuff, Google Now is in there though but the complete package comes in at only 57 MB which saves a lot of space, Gmail and YouTube can be downloaded from the Play store.
I'm really impressed by this ROM, it's really fast, everything works including both camera's, bluetooth in my car works flawlessly (connects faster then ever), battery life is also really good so far, took it from the charger 7.30 this morning and used it quite a bit till now (15:00) and still at 77%. Wifi is working fine and GPS connection is really fast (had to figure out first they use another icon for GPS now and it's on the right on the taskbar now).
A lot can be customized as well but I also installed Xposed now for even more freedom.
I can really recommend it, I like it more than CM (which I also really like) but that's personal.
PS I'm a big fan of the TWRP recovery now. It's really so much better than CWM and much much more intuitive.
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
I suggest you to flash the latest version of MIUI latest china dev, then from fastboot flash twrp, then clean flash rom + kernel. It takes about 30 minutes if you know what you're doing.
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
ginohabibi said:
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
Click to expand...
Click to collapse
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
ufoshop said:
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
Click to expand...
Click to collapse
Try method in my signature.. it should work for you
khajiit said:
Try method in my signature.. it should work for you
Click to expand...
Click to collapse
Where do i find that method?
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Alright, im going to try that method and i will report my results here.
Followed all the steps within your guide, but that guide didnt work and has nothing to do with our slowboot issue.
Hardware related then
ginohabibi said:
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
Click to expand...
Click to collapse
Didnt you change recently some parts of the phone? Like display/baterry and so...?
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
So you say there is no solution to run the official rom without waiting 4-5 mins on boot, I have the phone from fastcardtech and maybe is a refurbished unit because they have very low prices compared to other resellers...the phone came in sealed box...
Dwnld links plzz..
Hay anybody here ...is there any other kernal for andriold n ROMs...
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
Mine to, it 2 time I had to replace screen. I'll give a test right now and report back.
Im not using the device anymore, but i think i had to replace the screen like 3-4 times, its very fragile, even a drop from small height makes it crack. Also without case its very slippy device, but none of that matters. From the 4 displays i used, which all have been touchscreen + lcd + the frame (as i dont like to glue the display, i pay 10 dollars more and its better) had that exact same problem, which is very long waiting for the device to boot. The custom kernel solved it, but another (probably better quality) display does solve it too.
So, I flashed the beta firmware 9.2.18 and it actually went well. I didn't wipe anything after the flash and I am currently using the Nitrogen OS ROM. Anyway, after I flashed the firmware, it encrypted my device. Is this normal behavior? I did check my TWRP to see that it still works, but the loading time is increased dramatically (like before, it loaded within 10 seconds. After the flash, it needs to load twice the amount of time).
To reiterate:
1. Is it normal behavior that the phone "encrypts" after flashing new beta firmware?
2. What does this encryption do exactly?
3. Is it normal for TWRP to load slower?
P.S. I also believe that I flashed the TWRP version with the working encryption or something. I can't really remember. -_-
BenParz said:
So, I flashed the beta firmware 9.2.18 and it actually went well. I didn't wipe anything after the flash and I am currently using the Nitrogen OS ROM. Anyway, after I flashed the firmware, it encrypted my device. Is this normal behavior? I did check my TWRP to see that it still works, but the loading time is increased dramatically (like before, it loaded within 10 seconds. After the flash, it needs to load twice the amount of time).
To reiterate:
1. Is it normal behavior that the phone "encrypts" after flashing new beta firmware?
2. What does this encryption do exactly?
3. Is it normal for TWRP to load slower?
P.S. I also believe that I flashed the TWRP version with the working encryption or something. I can't really remember. -_-
Click to expand...
Click to collapse
If you came from a custom ROM to the stock, whether beta or stable, it will encrypt your phone. It is normal.
Encryption relates to security and your phone is now more secure than before.
Because of the encryption, TWRP will load slower. This is also normal.
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
try twrp 3.3.1 unofficial from
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
also then flash vendor image https://mirror.akhilnarang.me/MIUI/beryllium/ (9.6.27 is the popular)
flash LINAGE OS
flash DFE Treble https://drive.google.com/file/d/1As6z5v7NEIfOk67jXHBX34cbnFZdEjy9/view ,
later install magisk 19.4
now try one by one all three version of Twisted kernels ( the developer maintains 3 versions based on touch drivers (nvt)
https://forum.xda-developers.com/poco-f1/development/kernel-twisted-kernel-v4-0-beryllium-t3902838
i am hopful you will fix it
zyhpex said:
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
Click to expand...
Click to collapse
Worked for me! Thanks!
zyhpex said:
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
Click to expand...
Click to collapse
I had an experience as bad as yours. After flashing the last miui.eu, I went to boot and the phone does not leave the boot right away. I tried to enter TWRP and the touch just didn't work. I ended up flashing the official TWRP, also none of the touch works. I started getting desperate and settling for formatting for ROM stock and losing my 2 year old data, because I went to fastboot and flashed stock 11.0.8.0 and guess what? the touch didn't work, even in stock, I started to go crazy. So I had the stupid idea of putting the stock and blocking the bootloader, I ended up ****ting even more because even after the flash and blocking the bootloader the touch was dead. I was already giving up and thinking about paying someone as access to EDL mode to restore the phone. I ended up seeing your post and had the idea of plugging a mouse into the cell phone's type c input, and believe me the mouse cursor worked. Then I managed to unlock the bootloader again and flashed the stock that you recommended, and voiala the touch went back to work. I ended up going back to miui.eu and I'm ready for new flashes. It seems that we like to suffer LoL. I think this topic should be fixed at the top in case anyone else falls into this insane problem.
Reflash firmware n try ones.. only firmware
dorfohm2 said:
Worked for me! Thanks!
Click to expand...
Click to collapse
Im having the same issue.What should I do??My touch was working totally well before flashing TWRP.
solved by plugging in a mous in TWRP and navigating the UI to restore my "full" backup of all partitions! if you have done a backup! cheers and thanks for the idea of the mous! not expected it to work in TWRP though!!!