Database Info

[Q] Bricked ns4g?

I have a Nexus S 4g with ICS. Phone was rooted last year. Ran stock ICS for the past month (Sprint OTA update). Last week it rebooted when downloading an app. After the reboot all of my apps were "closing unexpectedly", not force closing. After about 10 minutes it tried to reboot and got stuck on the boot animation.
-Tried doing factory wipe/reset through the OS, TWRP, CWM and Fastboot. When it reboots, nothing has been wiped.
-Flashed Stock ICS and Gingerbread images. ICS will start and get the app close cascade, then get stuck on the splashscreen. Gingerbread hangs on the google screen/does not boot.
-Cannot write to sdcard but can copy everything off the phone to my PC. Toggling USB Debugging does not help.
Flashed stock rom using odin. It said that everything was successful but it booted up to the same problem.

disifer said:
I have a Nexus S 4g with ICS. Phone was rooted last year. Ran stock ICS for the past month (Sprint OTA update). Last week it rebooted when downloading an app. After the reboot all of my apps were "closing unexpectedly", not force closing. After about 10 minutes it tried to reboot and got stuck on the boot animation.
-Tried doing factory wipe/reset through the OS, TWRP, CWM and Fastboot. When it reboots, nothing has been wiped.
-Flashed Stock ICS and Gingerbread images. ICS will start and get the app close cascade, then get stuck on the splashscreen. Gingerbread hangs on the google screen/does not boot.
-Cannot write to sdcard but can copy everything off the phone to my PC. Toggling USB Debugging does not help.
I am out of ideas. I tried using Odin but could not find the PIT file for my phone.
Click to expand...
Click to collapse
if u have installed stock rom go to recovery and do a factory reset and clear cache

clear caches
I have done factory reset from the ICS UI, stock recovery (ICS and GB), CWM, and TWRP. I've cleared the regular cache, Dalvik cache, sdcard and everything that is clearable or wipeable in in CWM, TWRP, stock recovery. I've cleared the cache in fastboot and did "fastboot -w" (don't know exactly what that wipes) with no effect. I even had Windows try to format the phone. I have done any and all combinations at least three to four times apiece.

Tried to inställning CM - stuck at boot (n8020)

Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!

vargfloejt said:
Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!
Click to expand...
Click to collapse
Bump

vargfloejt said:
Bump
Click to expand...
Click to collapse
I have seen something similar when I installed Cyanogenmod on a kindle fire, I had to do a factory reset after restoring back to stock firmware.
I would suggest that you try doing a factory reset after restoring factory firmware on your GNote.

Success with Philz recovery
Had the same problem loading onto my N8020.
In the end I used a different recovery and it worked first go.
Try using Phils recovery http://forum.xda-developers.com/showthread.php?t=2202714

Reboot/Freeze Issue Upon Reboot (Repeatable)

Hi all,
I have been struggling with an issue for several months. Everytime I restart my phone the phone boots to my ROMs lock screen freezes and reboots again. Sometimes I can get my pin entered and sometimes not. Even if the phone unlocks it freezes and reboots shortly after.
I have had this issue on every ROM I have tried (Exodus, Euphoria, CM nightlies). I am currently running fastboot flashed stock COS 12.1, no root, stock recovery. My modem is current and I don't use any battery saving apps.
Has anyone experienced a similar issue?
Sent from my A0001 using Tapatalk

bucketheadmjs said:
Hi all,
I have been struggling with an issue for several months. Everytime I restart my phone the phone boots to my ROMs lock screen freezes and reboots again. Sometimes I can get my pin entered and sometimes not. Even if the phone unlocks it freezes and reboots shortly after.
I have had this issue on every ROM I have tried (Exodus, Euphoria, CM nightlies). I am currently running fastboot flashed stock COS 12.1, no root, stock recovery. My modem is current and I don't use any battery saving apps.
Has anyone experienced a similar issue?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
When flashing are you wiping properly (system, data, cache, dalvik cache)? Flashing the stock images with fastboot doesn't wipe data so unless you wiped data with TWRP first that hasn't happened and could be causing your problems.

If after trying wiping data it still doesn't work. Upload /proc/last_kmsg (dmesg from last boot) and the logcat.
Maybe we can find out what's going on by looking in the logs.

Heisenberg said:
When flashing are you wiping properly (system, data, cache, dalvik cache)? Flashing the stock images with fastboot doesn't wipe data so unless you wiped data with TWRP first that hasn't happened and could be causing your problems.
Click to expand...
Click to collapse
I didn't realize that flashing image files didn't completely overwrite the partition. I did a cache wipe today but it didn't seem to work from the stock recovery.
I have data encryption enabled BTW...
Sent from my A0001 using Tapatalk

Thymo said:
If after trying wiping data it still doesn't work. Upload /proc/last_kmsg (dmesg from last boot) and the logcat.
Maybe we can find out what's going on by looking in the logs.
Click to expand...
Click to collapse
I need to be rooted to provide the kernel logs and logcat correct?
Sent from my A0001 using Tapatalk

I will clean flash wiping and formatting everything this morning just to make sure and report back. Thanks for the support!!!
Sent from my A0001 using Tapatalk

Just a quick update... I took my OPO all the way back to stock using OnePlus's patch files that @Heisenberg re-posted. I did this after a full format of all the usual suspects. I then updated via OTA all the way to COS 12.1.
Prior to installing any apps I started experiencing the "double reboot" issue. I then erased and flashed both the persist image and reserve4 image.
I have since rooted, flashed twrp, and slowly begun to rebuild and test COS 12.1. So far no double reboots (which will now start to occur since I said that).
Admittedly, I don't completely understand the persist and reserve4 roles being played in all of this...
Sent from my A0001 using Tapatalk

I would like to go out on a limb and say my issue is fixed! Thanks to everyone for their help. This issue had plagued me for months through countless flashing...
Sent from my A0001 using Tapatalk

I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.

TeoJohn92 said:
I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.
Click to expand...
Click to collapse
Doesn't look like battery issue.Maybe caused due to xposed.

Mr.Ak said:
Doesn't look like battery issue.Maybe caused due to xposed.
Click to expand...
Click to collapse
After a clean flash, the phone worked smoothly for a whole day; but last night it restarted and began to reboot and lock on the unlock screen. (After the clean installation, I restored the apps and data via Titanium and the old Nandroid Backup). Now I'm installing a new rom, I'll see if the problem persists. Have no idea how this problem occurs.

Bootloop with 6.x.x and 7.x.x ROMs

My bootloader is unlocked.
Using FlashTool 0.9.18.6, I flashed "Sony Xperia L C2105 15.3.A.1.17 Generic DE" - FTF, which I downloaded from:
https://forum.xda-developers.com/xperia-l/general/sony-xperia-l-flashable-ftfs-locked-t2560642
Downloaded CM11 from FreeXperia's thread, from that I extracted boot.img and using FlashTool flashed it.
Downloaded CM12.1 from Oliver's thread and moved it into my external sdcard. Using CWM, did a clean wipe (dalvik, cache, data and system), and flashed the zip.
ROM installed and was working fine.
Downloaded CM13 from Oliver's thread and moved it into my external sdcard.
Enabled USB debugging.
Downloaded TWRP 3.0.2-0, from:
https://dl.twrp.me/taoshan/twrp-3.0.2-0-taoshan.img.html
Rebooted into bootloader using adb. And flashed TWRP, using fastboot:
"fastboot flash boot twrp.img"
Rebooted into recovery. The interface was flickering non-stop and the left part was overlapping over the right part and vice-versa, but I managed to factory reset and wipe my dalvik, cache, data, system, sdcard and android secure.
Then I flashed CM13 from my external sdcard.
No errors.
Wiped dalvik, cache and my external sdcard.
Rebooted.
Bootloop.
Rebooted into CM Recovery.
Factory Reset and wiped cache.
Rebooted.
Bootloop.
I have also tested 7.x.x (CM14 and Resurrection Remix) and it also gets me in a bootloop until the battery reaches 0%.
The problem started with Beta 2 of CM13 (anything before it works fine), after I flashed it almost a year ago. I also made a post there at that time about my problem:
"I'm not certain if this is the right thread to ask, and I don't think this qualifies as a bug report, I'm just asking for some help as my phone is stuck on the boot logo forever until the battery runs out (from 90-100% to 0%).
I've previously used CM11, CM12.1 and the previous beta 1 of CM13, but after flashing beta 2 a couple days ago it's just stuck on trying to boot.
The recovery I'm using is TWRP 3.0.2. I wiped my phone completely(the system, sdcard, cache etc). After that I connected my phone to my PC, while on recovery, and copied the ROM zip and GAPPS zip to my external sdcard. I disconnected my phone from the PC. Flashed the ROM and after that GAPPS (Open GApps Platform: ARM / 6.0 / pico). The logs didn't show any error so I wiped the dalvik cache and rebooted the phone. The phone went into the boot logo and now is just stuck there, I waited ~5 hours and it still didn't fully boot after an hour or so the battery ran out. So I decided to do everything again, charging the phone to 100%, wiping the phone completely 10 times(for reasons) and flashing everything the same way(I also downloaded the ROM from a different mirror, and tested both zips for any errors), this time I left it overnight, keeping the charger connected and in the morning it was still stuck on the boot logo. The third time I tried a different GAPPS package(A-GAPPS) and the same result. Can anyone provide some help? Maybe I'm just missing something or being really stupid. I'm sorry for being such a bother."
https://forum.xda-developers.com/xperia-l/orig-development/rom-cyanogenmod-13-0-t3254779/page20
I made this thread in hope of finding out what's causing this. Any help is appreciated.

It's been almost a year and I still have this problem with newer ROMs. Does nobody have any suggestions, anything at all? Is more information required? I'd be happy to give/do anything*, if it would mean getting these ROMs working.
The only error I've noticed is that after flashing LineageOS 14.1, if I try a fully factory reset through the default "Android Recovery" it will fail and I'll get "E: format_volume: failed to open /persist/footer" (This doesn't happen if I do a factory reset through TWRP).

[Help] Flashed Franco Kernel over CM13 Stock and ended in bootloop

Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please

First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?

leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.

Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.