Database Users

[Q] Soft brick after trying to flash resurrection

I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?

Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?

untamed1 said:
I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?
Click to expand...
Click to collapse
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.

RETRObruzzin said:
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.
Click to expand...
Click to collapse
Retobuzzing, thank you for the quick response. Thanks also for your last recommendation, gotta do that too next time.
I have actually found my solution reading in a post that I should try entering download mode by pressing both volume keys together while you connect the micro usb connector. That worked even though the screen gives you no feedback except for the led turning red (kind of scary at first :fingers-crossed.
After doing that I was able to follow the directions in the article titled: "How to unbrick LG G2 with stock firmware" at the Androidcure.com site.
The phone was restored to the original stock conditions and later I was able to update it to software version 26A.
Note to Forum Moderators: You can close this tread if desired. Thanks.

Yes I am!
Snuzzo said:
Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?
Click to expand...
Click to collapse
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?

untamed1 said:
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?
Click to expand...
Click to collapse
Only 1 assumption. Didnt downdate back to 12b bootloader/modem.

Help - i9505 unable to restore from CWM backup in Lollipop

Hi all, I've got a stock i9505, rooted, with Philz Touch recovery & Lollipop (I9505XXUHOB7_I9505BTUHOB4_BTU).
I made a (no errors reported) backup & loaded up Resurection Remix ROM (Resurrection-Remix-LP-v5.5.3-20150804-jfltexx) and GApps (gapps-lp-20141109-signed) and all seemed OK.
I then decided to go back to Lollipop & thats when things started falling apart - I did what seemed a successful restore from the backup but when it rebooted, it initially gave the error 'Inconsistent System UID' and about fixing permissions so I flashed TWRP & fixed permissions & went back to Pilz & tried another restore but ever since, it went into a boot loop (I think - I'm a bit new at this) at the point where the Samsung logo is still up & the stars are pinging out. Never moves on from this.
I then thought I'd take it back to stock & re-flashed Lollipop, did the root & reloaded Philz Touch & tried another restore - same thing.
I then tried CWM to see if that would do a decent restore but still no joy.
I wonder if my backup has been corrupted?
I can get it up & running but I'd like to be able to access all my backed up data etc.
I'm not knowledgeable enough to to a custom restore (in Philz) as I'm not sure what to restore & what to leave!
Can anyone help?
Kind regards,
Nic

wow400 said:
Hi all, I've got a stock i9505, rooted, with Philz Touch recovery & Lollipop (I9505XXUHOB7_I9505BTUHOB4_BTU).
I made a (no errors reported) backup & loaded up Resurection Remix ROM (Resurrection-Remix-LP-v5.5.3-20150804-jfltexx) and GApps (gapps-lp-20141109-signed) and all seemed OK.
I then decided to go back to Lollipop & thats when things started falling apart - I did what seemed a successful restore from the backup but when it rebooted, it initially gave the error 'Inconsistent System UID' and about fixing permissions so I flashed TWRP & fixed permissions & went back to Pilz & tried another restore but ever since, it went into a boot loop (I think - I'm a bit new at this) at the point where the Samsung logo is still up & the stars are pinging out. Never moves on from this.
I then thought I'd take it back to stock & re-flashed Lollipop, did the root & reloaded Philz Touch & tried another restore - same thing.
I then tried CWM to see if that would do a decent restore but still no joy.
I wonder if my backup has been corrupted?
I can get it up & running but I'd like to be able to access all my backed up data etc.
I'm not knowledgeable enough to to a custom restore (in Philz) as I'm not sure what to restore & what to leave!
Can anyone help?
Kind regards,
Nic
Click to expand...
Click to collapse
You can always copy the backup to your computer and extract the files you need.

Lennyz1988 said:
You can always copy the backup to your computer and extract the files you need.
Click to expand...
Click to collapse
Thanks for the reply Lennyz - I have copied the backup to my PC but when I try to extract or look at any of the .tar files, they all say they are unknown format or damaged (hence my thought on perhaps the backup is corrupt?)
That's assuming that I can use Winzip or similar to look inside the .tar files?

Aah, out of the 3 data ext.tar files, I can only extract stuff from one of them (and that still comes up with a message about unexpected end of archive?

Bootloop on Lollipop Stock

So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.

Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.

I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.

N910C bootloops except on CM 13

Hello everyone,
A couple of days ago I've tried to switch a N910C from CM 13.1 to SimplRom. To my surprise, that resulted on bootloops on any possible scenario.
This was not different when flashing the latest stock for it, N910CXXU2DPG8_N910CZVV2DPI1_N910CXXU1DPE4_HOME.tar.md5, and even fully formatting/repartitioning the phone, using TRELTE_EUR_OPEN_SEA.pit, the right PIT file for it.
All flashing processes done by TWRP and Odin were successful.
I was able to use the phone again only after a restore of the nandroid backup of the CM 13.1 on TWRP.
So, I have a few questions, please:
1. Is there a possibility that, even doing all of this, some corrupted/incompatible settings were still present on the phone, avoiding any rom to boot?
2. Is possible that the EFS partition could be causing the bootloops? When I try to access some subfolder of /efs using Total Commander I get reboots on CM 13.1. The same happens when trying to access the Hardware tab of Samsung Phone Info app.
If this partition is corrupted, how repair it?

Solved using https://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132.
I hope that this info could help someone else.

my n910c currently stuck on samsung galaxy note 4 screen, is it a bootloop ? i tried to flash rom via ordin but it stop at cache. then i tried with kies it load very slow and stop at around 65%, i can't connect adb with twrp even got driver installed. i even flash stock with pit file.. i guess i tried everything but still no way to restore my phone ! can anyone help ?

Rom and recovery not booting

Hi everyone,
I hope that you all had/are having a lovely christmas. Unfortunately for my S4 christmas has been terrible. The phone has had low storage for a week now and was crashing as a result and I didn't have time to fix it. Yesterday the phone was running horribly and wasn't doing anything that I touched. So I rebooted which took way too long and when I did it again the phone now does not pass the galaxy s4 screen and also TWRP recovery will not pass its boot screen either.
I have attempted flashing stock recovery which said error mounting all partitions, afterwards a reboot allowed me to wipe cache thinking it would allow the phone to boot, but no change.
I am thinking to flash stock samsung rom through download mode since it is still functional so I can recover my data before moving to my new phone. Will this be a good idea considering that the Lineage OS rom is significantly smaller than the stock samsung rom or will it not worsen the situation?
Thanks for your help!

Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?

audit13 said:
Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?
Click to expand...
Click to collapse
Thank you for your response! I have tried flashing flashing both the same TWRP and different version which was in fact smaller. This saw no improvement in the condition and I still can not pass the TWRP boot screen.
What else do you suggest I try?
Thanks for your time!

Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.

audit13 said:
Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.
Click to expand...
Click to collapse
I am actually unable to flash anything without odin because I can't boot into my recovery which hangs on its twrp screen. Also if I have set my partitions to f2fs will this interfere with flashing the stock rom?

I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.

audit13 said:
I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.
Click to expand...
Click to collapse
Do you think it could possibly be a bootloader or kernel issue? Perhaps I could try flashing those first before a full factory firmware?

I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.

audit13 said:
I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.
Click to expand...
Click to collapse
So I took the plunge and installed the stock firmware now the phone boots and I'm greeted with a message asking to factory reset because encryption failed. I reinstalled TWRP and for some reason that still can't fully boot. I want to get it working so I can access the storage to remove the important files through either mtp or adb. There is some form of adb working whilst TWRP is booting but it can't access or see anything in the partitions or mount them even running as root.
Any ideas to get TWRP or any other recovery working on the phone? (The stock recovery booted just fine before I flashed TWRP)
Any help is much appreciated!
Kind Regards,
Crapping_Bricks

I think the stock Rom doesn't recognise the file system and thinks the encryption failed.
I'm not sure what else to suggest other than a factory reset since twrp doesn't allow pulling the data via adb or mounting the data partition.