I have a realy serious problem with flashing lpx13d flashable pack. each time I try to flash it via twrp recpvery says that everything was flashed succesfully but then when I try to reboot the system it stops on google logo and after a reboot comes back to recovery mode. Do you have any ideas about wht am I doing wrong? Thank you in advance
First things first, the easy things.
Is it a clean install, or are you installing on top of a different version.
Did you clear the caches, if you didn't that's the first thing to try.
I have actually installed custom ROMs many times. and I have solved the problem. I havven't thought that instalation of the multirom is neccesary. When I installed it - everything works fine so as I can see - instalation fromthe stock KTU84 kernel was the issue.
To moderator- please, close the thread.
Related
Hi I got a solution to endless bootloops (at least working for me ) every time I flash new ROM I got stuck with bootloops so I experimented little bit and this solution seems to be working ...
I am using CM10 with Semaphore JB
You will need fixrecovery.tar and Odin (I used v1.83) you can download them in attachments.
For those who don't have flashable kernel on Internal SDCard can skip step 5 and second half of step 3.
1. So first of all you have to remove SIM and SDCard.
2. Flash fixrecovery.tar with Odin and uncheck Auto Reboot
3. Get into recovery and wipe only cache and flash kernel you want
4. Flash normal kernel with Odin and again uncheck Auto Reboot
5. Get into recovery and again flash kernel of your choice
6. Now you should be ready to switch your phone on
Maybe this excessive flashing of kernel is not necessary but I did it this way
Did you make this fix by yourself? There is already a fix for bootloop from stratosk!
Yes I did... can you post stratosk's fix please ?
Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sorry, my mistake, it's probably made by someone else. Search the thread.
Anyway, thanks for the fix...
No problem I hope someone will find this fix useful
Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sure you did ... [Q] Cannot boot or enter recovery (CM9 20120425)
Didn't see that post earlier, but it's not working for me anyway ... I had to clear cache additionally
Thats big development time... Clear cache ftw!
Sent from my XT910 using xda premium
Hello there,
Thanks for the guide. This hasn't worked for me?
I was upgrading versions of aways ROM (from ICS to Jellybean) and once I had flashed the ROM and GAPPS the phone rebooted. The link for the GAPPS was broken on the ROM website but it found me a replacement that I used. The phone does boot but FC on setup and no longer boots into recovery and is stuck in bootloop.
I thought this would fix the issue as I could still enter download mode but I still have the same problem? Phone won't boot into recovery and just loops...
Any thoughts?
Thanks in advance : )
I have a device that is experiencing bootloop just stop at the logo, I think this is the kind of Mtk, rooted, Kitkat. I do not know exactly what causes it bootloop, Before bootloop I edit files and install Tweaks build.prop through the application My pimp and when I restart the device bootloop ensued, do you think this is file damage build.prop or else. So that my device bootloop
Hi all,
I have problem with Android Revolution HD by mike1986 ROM. Everything working well expect restarting. If I restarted, phone didnt start rom but only clockworkmod and only one way how to correctly start phone is connect via cable to computer and over fastboot boot boot.img push boot.img into phone.. And second issue - in clockworkomod I cant make backup - everytime it ends with error message..
Any idea how to fix it? Thanks
I have this exact problem too. I'm ENG S-OFF and ARHD 9.2 installer is fine until the very last step when it goes "assert failed" and something about extracting the boot.img to /tmp/boot.img.
I tried going about it the same way I read before with CyanogenMod where I'd manually flash the boot.img in fastboot to make sure it was flashed properly or I'd just get bootloop into recovery, but it's a no-go. It flashes fine, of course, but it doesn't help one bit. I'll be damned if I'm giving up and moving to CyanogenMod again after going through all the guides and reading page up and page down of things that basically didn't help me.
Does anyone have a solution or an idea why ARHD 9.2 fails when extracting the boot.img to /tmp?
EDIT: Same issue with ARHD 7.3 btw.
EDIT2: I gave up and went to CyanogenMod 10.2. Worked the first time...
did you already tried using another custom recovery..like 4ext or TWRP..?
JJeamy said:
did you already tried using another custom recovery..like 4ext or TWRP..?
Click to expand...
Click to collapse
Hi, I have same problem, I tryed install 2 custom rom, but device started only to ClockworkMod Recovery ...
I tryed hard reset - wipe all data, not help
just tried installing TWRP recovery..look in here..
I've been using TWRP2 all along. It works very well on my HTC One and Nexus 7 both. I gave it another try today, but it's still a no-go. I think I've tried most every combination of things now. No matter. I'm giving the nightly CM11 a try now. :fingers-crossed:
Aha! Turns out I had a faulty SD-card. I could write to it and all, but I couldn't delete any files off it. No format worked. Nothing. It couldn't readily be identified, but at least I found the cause and now it's working perfectly. Smooth and fast. Very, very nice. :good: I'm a happy camper.
Hello, I've been looking in the forums and in Google for a few days to see if I can fix this particular issue and I still haven't had any luck. I hope that some developers out there that have crossed with this issue can help me out.
Lately all the ROMs I've tried to install via recovery in my Flo device haven't been installing completely, they've been all installing only the system partition in recovery and nothing else, not presenting any errors on the flashing process. By doing this, most of the ROMs run on my device, but they only run barebones, meaning that they miss out on those particular features that identifies each ROM.
I've tried flashing several stock images via fastboot to see if this resolves the issue and no luck, and recently tryed installing Multirom seeing that it seemed to resolve the issues in This Thread but still no luck, the ROMs all install with the same problem if I try to flash them via recovery.
I've only had luck with ROMs flashed via fastboot, like a stock image or Cyanogenmod via the installer app that flashes trough fastboot. I should also mention that I've tried using all the available recoveries out there (CWM, TWRP, Phil's, Modified TWRP) but still no luck. Also I should point out that I noticed the issues starting since I accidentally installed 5.1.1 OTA.
Any thoughts?
ejrm13 said:
Hello, I've been looking in the forums and in Google for a few days to see if I can fix this particular issue and I still haven't had any luck. I hope that some developers out there that have crossed with this issue can help me out.
Lately all the ROMs I've tried to install via recovery in my Flo device haven't been installing completely, they've been all installing only the system partition in recovery and nothing else, not presenting any errors on the flashing process. By doing this, most of the ROMs run on my device, but they only run barebones, meaning that they miss out on those particular features that identifies each ROM.
I've tried flashing several stock images via fastboot to see if this resolves the issue and no luck, and recently tryed installing Multirom seeing that it seemed to resolve the issues in This Thread but still no luck, the ROMs all install with the same problem if I try to flash them via recovery.
I've only had luck with ROMs flashed via fastboot, like a stock image or Cyanogenmod via the installer app that flashes trough fastboot. I should also mention that I've tried using all the available recoveries out there (CWM, TWRP, Phil's, Modified TWRP) but still no luck. Also I should point out that I noticed the issues starting since I accidentally installed 5.1.1 OTA.
Any thoughts?
Click to expand...
Click to collapse
Well, firstly give me more details. Are you on unlocked bootloader.
Can you provide me with a screenshot of how the flashing looks like ? Do you have the latest recovery ?
Have you tried repairing your device with WUGFRESH TOOL kit or manually downloaded Nexus Image and flashing it ?
Quote me in case you expect a reply!
Good Luck
I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices
Hey guys. I'm going crazy for days. I tried to root my T805 and something went wrong. After rooting and after the reboot there appeared many many error massages like "Google service stopped" or "android..... stopped". You can't really skip them because they are coming over and over and over. After some time it rebootes by itself and voila same issue... makes it unuseable. So right here nothing special I thought. Just flash the stock rom over it with odin and you will be fine. But whatever kind of rom or firmware I tried to flash I'm getting the same issues. Plus after every flash I got stuck at the Samsung logo incl. some vibrations in intervals. So when I get stucked (over 20 min) I have to force shutdown it and yeah it starts and hello error messages.
I rooted and flashed so many smartphones and tabs and I've never seen a problem like that. Please oh please try to help me. Probably I'll donate you some dollars for the perfect hint or solution, I'm really desperate.
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
mihailrusia said:
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
Click to expand...
Click to collapse
Yes. Every time I'm flashing I wipe befor and after it. And after I tried LineageOS the same happend with the error messages . But now after flashed stock ROM again it seems now that I'm totaly stuck at the Samsung logo. Even when I try to reboot and reflash I get stucked at the logo with these vibrations.
Thanks for your reply.
Ok now I'm not stucked at the logo but get the error messages again...
Are you flashing the last firmware and system and data are on ext4?
mihailrusia said:
Are you flashing the last firmware and system and data are on ext4?
Click to expand...
Click to collapse
Yes I'm flashing the latest. About the filesystem... I'm not sure. Where can I look at the filesystem? In Recovery? What I reached in the last houres: I flashed LineageOS again WITHOUT Opengapps. And boom ist startet pretty well but yea now I have no google playstore and such stuff. Now I'll try to flash the opengapps stock over the ROM using the TWPR.
Edit: I looked at the filesystem, it's ext4
You can view the partitions with DiskInfo
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=es
Install the pico gapps
So now I flashed opengapps stock again and I'm now stucked again in at the Samsung logo. I have to hard reboot now and yeah I think there will be the error messages. But I'll try the Pico version of opengapps like you said.
Edit: I didn't have to hard reboot it. It booted by itself after some minutes but yea with the errors. After some errors it shutsdown and reboot... and so on.
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
mihailrusia said:
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
Click to expand...
Click to collapse
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Metero said:
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Click to expand...
Click to collapse
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
Thanks for searching. I'll try this next. (Give me some minutes )
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Metero said:
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Click to expand...
Click to collapse
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
thejase said:
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
Click to expand...
Click to collapse
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Metero said:
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Click to expand...
Click to collapse
Try using https://forum.xda-developers.com/ga...olkit-unified-android-toolkit-galaxy-t2998205
This should take you back to stock as if the tab was new. It has many many features, including rooting the tablet for you. It runs in windows ( hopefully you have). Habben Sie einen guten Tag! (is this right? I love German but I am just learning)