Develop Bugs

Problem with dirty flash older version of a custom rom

Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?

Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.

i get bootloops on flashing any rom except fastboot rom on Redmi 1s

i used twrp 2..8.7.0 to flash various mokee roms, htc sense rom, resurrection remix and many more but facing bootloops on each.
i wiped everything formatted external and internal storage still last time i flashed mokee rom i was able to get into initial setup of the phone then after a minute still bootloop happened.
glad i took the backup so i was able to restore and i was able to run resurrection remix rom for a month
lastly i tried fastboot method to install stable 4.3 older version and it worked
after i tried flashing twrp and tried various new roms still bootloop.
i am tired of this i cant find any solution online.
EDIT- case still unresolved
my friend said that you messed up phones paritions thats why custom roms fail to boot well so when flash custom rom
it flashes data to some other parition and formats real parition so phone cant boot will go to boot loop maybe some recovery or some rom you installed over writtern your phone parition id's so now when install rom phone mistakes system folder for boot.img folder so when trying to boot up kernerl tries to find system files and its not inside system parition
i dont get much of it can someone help?

Have you flashed latest firmware file? You can find it in cm13 thread, post #3.

cvele992 said:
Have you flashed latest firmware file? You can find it in cm13 thread, post #3.
Click to expand...
Click to collapse
yes i tried that too still bootloop i dont know why i have flashed various roms in past never faced a bootloop

geek.shivam said:
yes i tried that too still bootloop i dont know why i have flashed various roms in past never faced a bootloop
Click to expand...
Click to collapse
flash latest miui 7 fastboot rom.
If it does not help then maybe its a problem with recovery.
Did u remember anything doing to recovery before getting bootloops

[email protected] said:
flash latest miui 7 fastboot rom.
If it does not help then maybe its a problem with recovery.
Did u remember anything doing to recovery before getting bootloops
Click to expand...
Click to collapse
nothing odd i can remember, i flashed twrp many times still facing this issue.
i am sure if i will flash the latest fastboot rom it will work its downloading but i cant install any custom rom, again i installed mokee rom it showed some starting steps in startup like setup wifi and google account then again it started bootlooping
happens with every rom

geek.shivam said:
nothing odd i can remember, i flashed twrp many times still facing this issue.
i am sure if i will flash the latest fastboot rom it will work its downloading but i cant install any custom rom, again i installed mokee rom it showed some starting steps in startup like setup wifi and google account then again it started bootlooping
happens with every rom
Click to expand...
Click to collapse
what i trying to say was First install the latest fastboot rom it got latest firmware then install twrp and try to flash custom rom
---------- Post added at 01:04 PM ---------- Previous post was at 01:02 PM ----------
New TWRP v3 also available in original development section in xda...try that if it does the trick

[email protected] said:
what i trying to say was First install the latest fastboot rom it got latest firmware then install twrp and try to flash custom rom
---------- Post added at 01:04 PM ---------- Previous post was at 01:02 PM ----------
New TWRP v3 also available in original development section in xda...try that if it does the trick
Click to expand...
Click to collapse
wait let me actually try that

Still same problems persists, i flashed laterst twrp recovery flashed latest fastboot rom too still i cant able to flash any custom rom still bootloops happen . the rom booted after several bootloops but soon i got on setup of new rom selected language and again bootloop :/

i tried everything i can it seems like i can only use a fastboot rom here on my phone and that too outdated i cant update it either . am i the only one facing this problem,?

Before flashing the rom. Format the phone from recovery and after flashing the rom try to factory reset it. Hope it works...

chauhansonu104 said:
Before flashing the rom. Format the phone from recovery and after flashing the rom try to factory reset it. Hope it works...
Click to expand...
Click to collapse
i have tried this many times this wont help me and same problem persist

failed
chauhansonu104 said:
Before flashing the rom. Format the phone from recovery and after flashing the rom try to factory reset it. Hope it works...
Click to expand...
Click to collapse
bro i tried that too still same problem persists
i cant able to flash a single rom except fastboot rom
not even the stable miui

Use latest firmware file
first get everything stock, i.e ROM< RECOVERY<KERNEL
after that flash latest TWRP<then download the latest CM build< flash it< wipe cache and dalvik< install the firmware file which u can find on the CM 13 Thread #3 post< wipe cache and dalvik again... reboot and enjoy
hope i helped

I also have the same problem.....
Is ur problem solved now???
Please reply

stuck in twrp logo

hi
today i installed this rom
http://forum.xda-developers.com/lg-g3/development/rom-turbo-rom-layers-t3346477/page8#post66165937
and everything works fine .
but i didn't like the rom and decided to install another bu when i tried to boot into recovery i got stuck in twrp logo and can't do anything
i always boot to recovery and never had any problem except this one . could u plz help me
twrp recovery version 3.0.0

iYazeEeDzZ said:
hi
today i installed this rom
http://forum.xda-developers.com/lg-g3/development/rom-turbo-rom-layers-t3346477/page8#post66165937
and everything works fine .
but i didn't like the rom and decided to install another bu when i tried to boot into recovery i got stuck in twrp logo and can't do anything
i always boot to recovery and never had any problem except this one . could u plz help me
twrp recovery version 3.0.0
Click to expand...
Click to collapse
Im a noob total noob actually but im guessing that that rom doesnt support twrp 3.0 i say this because ive seen a rom that i wanted. A stock M 6.0 at that but the instructions said not to use with v 3.0 which is what i have so i skipped out on it.. Again just my hypothesis

Bootloop after Bootloader Unlock

Hi Mates,
I was unlocking the bootloader of my Xperia M Dual. It went well but after that the phone went into bootloop. I read quite a few threads which suggest to flash stock rom. But I am having a few problems :
1. Cant find Indian stock rom, some links dont have the file others have a brazilian version. Please give a link.
2. Will flashing stock rom would work as I havent installed any backup CWM or TWRP ?
3, Can I flash cynogen nightly directly instead of flashing stock rom ?
4. Other things I should know prior flashing being a newbie.
5. BTW how much time does it takes to boot after unlocking bootloader ?

Ckp1991 said:
Hi Mates,
I was unlocking the bootloader of my Xperia M Dual. It went well but after that the phone went into bootloop. I read quite a few threads which suggest to flash stock rom. But I am having a few problems :
1. Cant find Indian stock rom, some links dont have the file others have a brazilian version. Please give a link.
2. Will flashing stock rom would work as I havent installed any backup CWM or TWRP ?
3, Can I flash cynogen nightly directly instead of flashing stock rom ?
4. Other things I should know prior flashing being a newbie.
5. BTW how much time does it takes to boot after unlocking bootloader ?
Click to expand...
Click to collapse
A1. This thread helped me. - http://forum.xda-developers.com/showthread.php?t=2532190.
A2. Yes, flashing stock rom would work even if you haven't installed any backup using CWM or TWRP.
A3. You can still flash CyanogenMod Nightlies directly instead of flashing the stock rom and then flashing CM again.
A4. Newbie here too! so I can't actually Suggest you anything
A5. It is supposed to take 5-10 minutes but even my phone went into bootloop.
What I did :-
> Flashed the old TWRP recovery from flashtool
> Installed CM and GApps
> Wiped Data/Factory Reset
> Rebooted the Device.
And VIOLA! the phone works like a charm!
I've been using the ROM for 2-3 days now and I have no major problems as of yet.
Hope this works out in your favour!
Happy Flashing!

After unlocking bootloader Bootloop is normal. You have to flash stock rom to fix it and also you can also flash any custom recovery(Cwm,Twrp) then flash any custom rom to fix it.
4.3 Indian Stock Rom
Recovery - CWM Philz

I am getting application error on flashtool help

LineageOS-based roms won't boot - Firmware 4.1.0

I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.

do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/

bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong

vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.

Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot

Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM

go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further

indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen

Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!

AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes

indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)

AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now