[Q] LG G2 stuck in TWRP 2.7.0.0 - G2 Q&A, Help & Troubleshooting

Hey guys,
I am kind of a noob when it comes to android, but I'm decent with PC. I wanted to get Cyanogen mod 11, as I have used it before on previous Android phones and liked the features it had.
I was on the Kit Kat OTA update for the Verizon VS980 version of the G2. I downloaded TWRP v2.7.0.0 using AutoRec. I had put the newest nightly build of Cyanogen Mod 11 in the /sdcard file path. However, when I tried to install it using TWRP, I got "Skipping MD5 Check: no MD5 file found" in the prompt. It says the install is successful, however I am stuck in a boot loop at the LG logo. I read somewhere that totally formatting the data worked for someone so I gave that a shot and still nothing. I have cleared both cache and Dalvik Cache and completely wiped the phones memory.
I have been using ADB sideload to try to flash different ROMs to the phone, but no success. They all transfer to the phone successfully, but when the phone tries to apply them, I get the same response "Skipping MD5 Check: no MD5 file found". It says the file has been applied successfully but I am still stuck in the boot loop. I have also attempted what has been listed in this thread http://forum.xda-developers.com/showthread.php?t=2451696
The only part of my phone I still have access to is TWRP recovery mode.
Any help would be awesome. Just ask if you need any clarification.
Thanks.
Mike

The skipping MD5 check means nothing. Most ROMs I've seen say that. Which other ROMs have you tried? Since you're on 24A the ROMs have to be made with true 4.4 sources to boot. CM nighlies are not one of them. I suggest trying Mahdi. Download the newest ROM, patch and whatever gapps you prefer. Transfer them to the phone. Go to TWRP Advanced Wipe and select Dalvik, System, Data, Cache. Then flash Mahdi, Patch and gapps. It should boot up just fine.

JRJ442 said:
The skipping MD5 check means nothing. Most ROMs I've seen say that. Which other ROMs have you tried? Since you're on 24A the ROMs have to be made with true 4.4 sources to boot. CM nighlies are not one of them. I suggest trying Mahdi. Download the newest ROM, patch and whatever gapps you prefer. Transfer them to the phone. Go to TWRP Advanced Wipe and select Dalvik, System, Data, Cache. Then flash Mahdi, Patch and gapps. It should boot up just fine.
Click to expand...
Click to collapse
Ill give this a shot right now. I can do this through ADB sideload right? because thats the only way i have access to transfer data to the phone.

I just tried it and it worked! Thanks so much!
Why couldn't i have thought of that...

djilluminate said:
I just tried it and it worked! Thanks so much!
Why couldn't i have thought of that...
Click to expand...
Click to collapse
Glad you got it! Make sure the ROMs you flash from now on are specifically 4.4.2 sourced. If you don't see mention of it you can always ask in the thread. Most of the ones that are will say in the OP you need a true KK modem. If you want CM11 again you can go here http://forum.xda-developers.com/showthread.php?p=53232344. Its for 24a.

Related

[Q] i9505 (jgedlte) fails to boot system after installing ROM

I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).

What did I do wrong? Trying to Install CM11

I rooted my phone installed twrp via autorec--> http://forum.xda-developers.com/showthread.php?t=2715496 . Then I backed up my phone through twrp and then I rebooted and put the newest cm11 stable build --> http://download.cyanogenmod.org/?type=snapshot&device=vs980 on my phone. (I put it in the download file of my phone if that makes any difference), then I went to twrp and wiped everything but internal storage and proceeded to flash cm11 which i found in my download file where I put it (it was a zipped file) and I flashed it, then it went into a boot loop! Currently installing the recovery in twrp that I just made. I do not know what I did wrong could someone please enlighten me? This is the first time doing this sorry if its a noob question.
Thanks.
FYI the recovery worked my phone booted up fine. Also it is a VS980. I do have the verizon variant.
UPDATE:
Tried flashing again, this time with gapps as well (forgot to the first time) same results, flashing the recovery again rn. I AM CLUELESS!!!!
bobberserker said:
FYI the recovery worked my phone booted up fine. Also it is a VS980. I do have the verizon variant.
UPDATE:
Tried flashing again, this time with gapps as well (forgot to the first time) same results, flashing the recovery again rn. I AM CLUELESS!!!!
Click to expand...
Click to collapse
Would uninstalling autorec do anything?
flash the latest recovery from here. Then afterwards check if you have the right version for your variant and check the md5
Krenol said:
flash the latest recovery from here. Then afterwards check if you have the right version for your variant and check the md5
Click to expand...
Click to collapse
Again this is my first time getting this far so here are some noob questions: Would I just flash the zipped folder in twrp? Would I need to wipe anything? Would I need to create another recovery? Would it delete my old recovery?
Thanks.
EDIT:
Also why would updating twrp make such a big difference?
Just Flash the zip File for your variant then Reboot the recovery and go to settings and hit restore default. Don't wipe anything for changing the recovery. And this will just update the rec nothing else

Moto x pure XT1575 What am i doing wrong?!

I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.
RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.

Stuck in bootloop trying to flash 7.1 custom rom

My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..

flashing firmware zip fails every time

I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Use Unbrick Tool and Restore
Hey,
You can Flash your Mobile using the Unbrick tool at - https://androidfilehost.com/?w=files&flid=204903
Use the Latest file which I guess comes with OOS 5.1.3 - https://androidfilehost.com/?fid=962339331458999196
If you try to Go to Open Beta ROM First Flash Open Beta 12--> Open Beta 13 --> Open Beta 17
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Flashing newest oos doesn't always work l have had this sometime l have had to go back 3 oos versions then flash them in order to flash the latest release.
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Hi ! Do you have some news about it ? I have the same issue since Monday...
I've tried like anything i've found and even more, but nothing did the job ...
The only way to have my OP5 working is downgrade to an old version running Android 7.1.1

Resources