update:
i tried what you suggested, reflashing stock rom now. encountered same problem even in twrp, the phone reboots itself.
god help me i am trying to fix this for 2 days now.
=======
Here is the problem that i am encountering right now.
i am not sure what i am doing wrong, and this time whenever i flash something from recovery the phone reboots.
here are the things i did, using philz touch, i chose the install new rom (i do this everytime when flashing a new rom) then flash RR, was able to finish it but stuck in boot loop. so followed the same steps and flashed 2 other roms, infernus and halcycon (used these roms before) however before finishing the installation the phone reboots.
next step i flashed twrp via odin (success) and flashed the latest version via twrp recovery. guess what same problem, with RR it is stuck in boot loop while with other roms, it does not complete the installation. this thing never happened to me.
next step i used this adb thing and i believe it is successful, however same problem persists.
the only thing i can think of is to flash the original i9500 firmware which i am downloading right now and will flash it via odin. - did not work
Related
I'm not sure why i can't get it working but i was flashing back to stock rom. I have the correct rom and everything flashes fine on odin. I am unable to reboot to recovery. it says its loading and goes to black screen, and tries to boot to OS again. I tried flashing twrp with odin and same thing. I flashed the stock rom multiple times and it just won't boot. I even used Kies to flash it to stock rom and it was successful however stuck at boot logo again. The one thing i didnt do was wipe data/cache etc before flashing to stock rom but every tutorial i seen doesnt state to do it before the flash anyway. Has anyone ran into this problem before?
How are you able to get into download mode to flash rom but not be able to go into recovery? I had this issue once with my note 2 and went into recovery and wiped data and rebooted successfully....
Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....
I kind of messed up. I have had no issues up till now. I have flashed Baikal os and found there were problems with youtube. I figured it was just that rom then found that every other rom I tried had the same issue. I flashed the stock Nougat (on accident mind you) and thought I could just do the update to 8.1 oreo. The issue is that it restarted into twrp. From there, I can't boot into any rom. I haven't tried stock rom but everything I have tried does not work. When twrp is finished flashing both the rom and gapps, I clean (sometimes not) the cache and restart into system. It keeps rebooting into twrp instead of into the rom. What should I do? I have never had this issue before...
Update: I can only boot into my phone if I boot from the bootloader. I can't boot from recovery, like clicking on boot into system from recovery.
Update # 2: using the tool by drtechie, I flashed the Oreo stock firmware/rom. The issue is that even with the recovery wiped, something keeps making my phone try to boot into recovery. I got the screen for people who dont have a custom recovery installed. Still clueless. Getting desperate because I kind of want my g5 plus back...
Factory reset your phone from twrp
I don't understand exactly what you are trying to say but if your problem is "Twrp bootloop means no matter what you do you are not able to get out from twrp" than type this in twrp terminal
In twrp terminal :
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
And again reboot to recovery. Flash any rom now you will be able to boot into system
I recently picked up my old note 3 and wanted to use it as a gps for my car, but when i tried to start it i noticed it still had some weird rom form a few years back installed. So i went to sammobile to grab the newest official rom and flashed it with odin. That is when the trouble started.
Odin stated that the flashing proces was successful but when it automatically rebooted i was given an unpleasant surprise.
My good old phone kept rebooting to the samsung galaxy note3 logo with the text the top left which stated: "recovery booting....".
My first instinct was that i had to go to the recovery to format cache and data, but the problem was that the recovery wasn't reachable.
So installed twrp 3.1.1.0 which I've used before, but still no luck after doing a factory wipe.
After all of this i've never been able to enter the stock recovery, even after again re-flashing the stock rom.
does anyone have an idea how to fix this.
Search multiple identical posts.
Suggest older 2.8 TWRP.
I inded find some older posts, but none of them discribe this problem. I tried to use twrp 2.8.7 amd that will give me a recovery to work with. But it still won't boot afterwords.
I can flash the older 4.4.3 firmware and it will boot with no problems. But when i try to update it with a newer version, it gets stuck again
Its probably a bootloader problem .
Phone Info from playstore and post bootlader etc.