Hey folks,
I'm no noob,And I did search tons of post n treads before deciding to making one.
More than 6 months ago, I have tried Resurrection Remix, though I was aware it require JB Bootloader,so had flashed Loki Bootstacks.
Steps were;
-Downloaded RR zip, GApps,Loki Bootstacks(md5 checked)
-Flashed Loki Bootstacks
-Rebbot recovery
-Flash RR zip
-Flash GApps
-Wipe Cache n Dalvik
-Reboot System.
Upon reboot Screen got black! That's was the first time ever any of My Android brick!
Connected it to PC n saw bunch of Partitions( Qualcomm HSUSB_BULK 9006) immediately understood that it got Bricked!
Took sometime to learn n in under night, get back up n running with help of tools n appropriate guidelines.
After that Rooted again as it was back to Stock 20C took OTA zip from 20C > final KK build.
Few days I have played around with bunch of ROMs, tried every single ones available, and than one day exactly week later from first brick tried Resurrection Remix again.
Actually flashing ROM this time let me setup device n after updating SuperSU binary, prompt me to Reboot System, that's where all happen.:crying:
This time around it Bricked without showing any partition but Real Hard Bricked!! QHSUSB_BULK 9008
So my question to active flashaholic, what went wrong?
Why My G2(D800) got bricked only on Resurrection Remix OS and not any other ROM?
My G2 is still dead! Really hoping for some legitimate answer, why other ROMs didn't brick n only RR?
Related
Hello, I had some issues with my LG G2 while attemping to flash a new rom, here's my problem:
I checked for the latest crDroid 6.x rom and the gapps, everything went fine, I flashed the rom with no problems at all and then continued with the gapps. But here's the problem, when I tried to boot it, nothing popped out from the display, just the LG logo, then it was completely black. After trying to install another custom rom (cm 13 nightly), nothing happened. Then, I tried to go back to my AICP rom. I had to use ADB installer since I didn't have any zips avaiable, but when I tried to install tk gapps (downloaded from the AICP forum), Error code: 20 came out. I did a research, and this looks weird, because that error only pops when the gapps are not compatible with the current rom, but clearly they were. Any ideas on how to fix this up?
Avrammm said:
Hello, I had some issues with my LG G2 while attemping to flash a new rom, here's my problem:
I checked for the latest crDroid 6.x rom and the gapps, everything went fine, I flashed the rom with no problems at all and then continued with the gapps. But here's the problem, when I tried to boot it, nothing popped out from the display, just the LG logo, then it was completely black. After trying to install another custom rom (cm 13 nightly), nothing happened. Then, I tried to go back to my AICP rom. I had to use ADB installer since I didn't have any zips avaiable, but when I tried to install tk gapps (downloaded from the AICP forum), Error code: 20 came out. I did a research, and this looks weird, because that error only pops when the gapps are not compatible with the current rom, but clearly they were. Any ideas on how to fix this up?
Click to expand...
Click to collapse
for your rom to boot you need hybrid bootstacks
wipe all/flash hybrid/ go to main menu/ then reboot into recovery from recovery/ once in recovery again proceed to flash rom and gapps.
use the one for your variant
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
Hi guys,
I have the standard note III 9005 and I had always installed CFWs on it.
I wanted to update to newer 6.0.1 Roms (had 6 roms before) but I seem to have a VERY annoying bug:
I tried to install Temaseks rom and resurrection rom but I had huge issues with it. I got bootloops although I got the newest 3.0.2.0 Team Win Recovery Project
I installed rom, GAPPS (correct version of course 6.0.1) , install rom again then delete cache and then it worked on both roms.
So a simple "install rom, GAPPS, then clean cache" didnt work. I tried to install multiple times until I got the installation! YAY! BUUUT!
Here is the fun part:
If I restarted the phone acidentally or on purpose I got stuck in a bootloop. After that the phone was unuseable again so the installation was useless.
Only solution is to completely wipe and reinstall and experiment with the order of installation until it works!
I did install STOCK rom because I was so freaked out and then went with ODIN the complete rooting guide for clean rooting, but still problem exists.
I tried two other roms but the problem was that while flashing the phone restarted automaticly and then TWRP said no installed rom? ???
Huge thanks for helping me!
New info:
I was able to make the rom work. I restarted and got stuck into bootloop!
I could boot normally after deleting dalvik cache!
But after rebooting I got into bootloop. Tried deleting cache again but this time it never booted properly.
How can I avoid by always deleting dalvik whenever I have to restart my phone (if battery dies or purpose)?
PPS: Stock Rom flash works flavlessly. I am waiting in stock rom until I find a proper solution :"(
Suggest you read the roms faqs and Q&A particularly with regard to TWRP .
Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!
Okey.. So I used to flash many ROM on my Xiaomi Redmi 3s prime and they were very stable and awesome also I had flashed RR nought ROM and used to work well but it was a buggy ROM so I flashed another 6.0.1 rom stable ROM and few days later I found stable nought ROM but when I flash them then it show boot animation (loading screen) like for 1min and then get stuck and then automatically gets turn off I tried many times to start but got same results but i can flash marshmallow ROMs but not nought ROM and also like 4-5months ago when I was using 7.0 ROM and then got back to older then my WiFi and Bluetooth stopped working :crying:
Flash wifi and modem patch provided with custom roms in there thread or if every this is right i.e you flash all patches then try to wipe your data partion or factory reset your phone.Take back up your data before doing factory reset.
I had that with RR official rom latest. I just had to disable DM thingy after wiping dalvik and then boot to system. The first boot will kind of not go past beyond the RR animation and then I have to powercycle once and then everything was the way it should be. The latest RR also has Magisx which will not boot the phone if you have some other root like SuperSU for some reason.
In short after making the backup through TWRP, wipe the lot using the advanced wipe, install the RR ZIP and wipe dalvik install pico Gapps (some reason Aroma version didn't work) wipe Dalvik and disable DM and then boot system If it gets stuck in the RR animation for longer than 3-5 mins in the first boot just hold the power button to cycle it once and it should work.
Hello,
I wanted to reach out as I am having some difficulty getting custom ROMs to work correctly, and the issues I am experiencing seem to be unique in that no-one else in the ROM threads are having the same issues, so I suspect there may be something I am missing that is causing me issues.
I previously was on an older version of lineage, but decided to take the plunge and try out treble, so I have upgraded myself to EMUI 8.
The version I went to is 8.0.0.369, although the build number shows as 8.0.0.046 (0OXY).
From there I flashed a Treble TWRP - https://forum.xda-developers.com/p8...lopment/unofficial-twrp-3-2-1-0-oreo-t3773970
I then went to try out Haky86's LineageOS 16.0 Huawei P8 Lite 2017 PRA-LX1, but this required me to flash a new TWRP, but I had to do a ADB shell command to clear data every time I went into TWRP. I had a few other issues too, but there isn't much point going into them here. I raised them on the thread.
I then tried out DarkJoker360's LineageOS 15.1 for Huawei P8 Lite 2017 but I kept getting strange issues on first launch (Google services crashing etc)
I am now back to stock.
I can't work out why I am getting all of these strange issues given that most users don't have a problem. Is there something I am missing here?
I am pretty familiar with the standard process of flashing a ROM:
Clear Data & System
Flash ROM & GApps
Wipe data & Clear cache
Apologies for the long story, and thanks for your time in advance!
Thanks,
Charlie
Hey,thats my way.
After brick i flashed new stockrom over erecovery with wifi,in new rom it comes directly the last ota update,bo problem at all.
So i have perfectly installed all rom etc on my pra lx1.
First ive flashed Ascuccius twrp (need bootloader unlocked),from twrp i choosed shutdown device.
Now power on the phone until see the bootscreen with the warning blabla.There ive used volume + to boot to erecovery,there i done factory reset and reboot to twrp,in twrp i format data partition and rebootet to once more to twrp to flash rom and gapps with dalvik and cache wipe after flash,rebootet and have errors like you.So again to erecovery and again factory reset,now in twrp i flashed rom and gapps and wiped dalvik and cache and reboot system,boom,perfect.After this flashed Magisk to root,even perfect till now,have tested 3 times with different pie roms,no issues at all.So i hope you have luck and fun by do it,many greetz!!!