Database Users

Soft brick but common fixes not working

Hi,
I got my N7000 stuck in a bootloop. i did NOT flash any other rom not for the N7000. i was planning to flash the paranoidandroid rom and while shifting from ICS to GB [as it suggested] this happened.
I still have download and recovery modes. Flashing different stock roms is going through, and some custom kernels too [the yellow triangle appears after and the flash count increases]
trying to recovery from my nandroid backups gives the same result as the stock flashing
i.e. its goes through then get stuck in the boot screen before the animation [the screen which says Samsung Galaxy bla bla, the screen where the yellow triangle shows up to be clear]
What can i do now please??
thanks
edit: should i try to format /system /data /preload /emmc fom CWM recovery 5 becuase i can do that

So you flashed successfully gb? If you are on a gb and you have used a safe kernel to revert. Did you try to Wipe data and cache from recovery? Try it, it should bring you out of the boot loop.
Sent from my GT-N7000 using Tapatalk 2

Hi,
I don't know on what rom i am at the moment. it should be GB since i flashed SGN_XX_OXA_KJ1_FACTORYFS.tar
wiping data on the CWM worked before but this time it got stuck with out any progress in the blue bar for like 20min.
i was suggested to flash a wipe rom, but i dont know where to find one exactly

Like Baxos said. Try wipe all since you r at old GB. Its worked 4 for me. I've been at your stage then wipe all then root and flashed paranoidandroid. Try Get back to recovery and wipe all then reboot.
n7000 paranoid android v2
Will update to v3 when got time

wipe all = also formatting /system /data /preload /emmc fom CWM recovery 5?
because i did many of the restore to factory and clearing cache

the problem seems to be due to the fact that /data is not being wiped. the progress bar gets stuck and then reboots
any idea how i can wipe this partition?

Did you first install a safe gb kernel when you were on ics before downgrading the rom to gb? If not then you will have performed a wipe under ics kernel and it sounds like brick bug symptoms.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!

jan-sgs said:
the problem seems to be due to the fact that /data is not being wiped. the progress bar gets stuck and then reboots
any idea how i can wipe this partition?
Click to expand...
Click to collapse
Maybe your /data is corrupted. You can make a new /data with adb.

hi,
sorry for the late reply. i was busy with uni work
i will try the adb method.
thanks

all partitons were wiped on a different rom version.
the boot loop seems to be irreparable and i will have to send it abroad to get it fixed. hopefully i dont have any of my data on it

[Q] Please help, TWRP will not flash/ wipe/ restore anything

I was running CM10.1, I was switching to Google Rom, wiped data/ factory restore, flashed zip, but forgot to flash Loki.
Went back, tried to flash loki, but it comes out as failed. looking through logs, I get
E:Unable to mount /data
E:Unable to mount Internal Storage.
I tried to do wipe of system, data, cache, and nothing wipes.
When I was rebooting 2nd time, I got a prompt to install Root as I was not rooted, but I did root weeks ago, when I went to CM.
Any help/ advise/ suggestions are welcome.
I would really rather not ODIN to stock, but will if I have to, is there a way to snatch internalSD files before the flash?

Dimon1990 said:
I was running CM10.1, I was switching to Google Rom, wiped data/ factory restore, flashed zip, but forgot to flash Loki.
Went back, tried to flash loki, but it comes out as failed. looking through logs, I get
E:Unable to mount /data
E:Unable to mount Internal Storage.
I tried to do wipe of system, data, cache, and nothing wipes.
When I was rebooting 2nd time, I got a prompt to install Root as I was not rooted, but I did root weeks ago, when I went to CM.
Any help/ advise/ suggestions are welcome.
I would really rather not ODIN to stock, but will if I have to, is there a way to snatch internalSD files before the flash?
Click to expand...
Click to collapse
If you can't boot into system, and TWRP will not restore your Nandroid I think ODIN to stock is inevitable. It really doesn't take too long. ODIN stock, re-root, install TWRP/CWM and restore your backup or flash Google Rom and LOKI this time.

blyndfyre said:
If you can't boot into system, and TWRP will not restore your Nandroid I think ODIN to stock is inevitable. It really doesn't take too long. ODIN stock, re-root, install TWRP/CWM and restore your backup or flash Google Rom and LOKI this time.
Click to expand...
Click to collapse
Thank you, from what I read, ODIN does not wipe our internalSD, is that correct or am I misreading it?

[Q] Trouble With Flashing CM10.2 and Wrong Kernel

So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!

alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??

Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?

alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.

Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?

alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4

Cache partitions erase error.

Guys, I need some help with my Galaxy S4 - 9505.
I'm running Omera rom with TWRP recovery.
I had one random restart and decided to wipe cache and dalvik. But I can't. , recovery report that cache could not be mounted.
I changed recovery with PhilZ but its the same. Also the partition size is shown 0MB.
This is the second time i got this issue.
Could anyone of you help me to understand why this happen?

re: cache issues
samo_ said:
Guys, I need some help with my Galaxy S4 - 9505.
I'm running Omera rom with TWRP recovery.
I had one random restart and decided to wipe cache and dalvik. But I can't. , recovery report that cache could not be mounted.
I changed recovery with PhilZ but its the same. Also the partition size is shown 0MB.
This is the second time i got this issue.
Could anyone of you help me to understand why this happen?
Click to expand...
Click to collapse
First you should do a nandroid backup.
Your best bet is to do a system reset (under settings in the phone) and then download the stock odin
flash pre-rooted i9505 rom from here: http://forum.xda-developers.com/showthread.php?t=2409867
Odin flash it and then check out the phone make sure all is well.
After that get the Odin flashable Philz, CWM or TWRP recovery and flash it, (or simply use goomanager to get twrp)
then get the latest update of SuperSU and flash that in recovery. (both goomanager & superSU are free apps at the playstore)
Then after checking everything out making sure everything is working properly make another nandroid backup.
After that flash any of the i9505 compatible custom rom you like.

@Misterjunky, thanks for the reply.
I actually have done this first time i got this issue, so did same and now.
More or less I try to understand why cache got corrupted? And could this be some kind of hardware issue with the internal memory.

[Q] Flashing various TW Lollipop fw over existing CM12 fails

Hello,
actually I'm using a SGS4 I9505 with cm-12-20150304-NIGHTLY-jfltexx and CWM 6.0.5.1.
I've tried to flash several TW Lollipop firmware wich i found in the I9505 forum:
1. Kushan+Touchwiz+Lollipop+Lite+Rom+v.1.2
2. S4_Echoev42_EchoePop2_020315
3. OA7-2.1F
4. XXUHA07-v2.01
Before flashing any oft this firmwares i made a factory reset, wiped both caches and installed the modem Firmware via Odin.
After flashing firmware # 1 and 2 my phone was stuc in a bootloop (only Samsung Galaxy S4 Logo appears).
Flashing firmware #3 and 4 fails and cwm reports error 7.
Flashing cm12 afterwards isn't a problem and runs fine.
I think the wipe fails or doesn't work properly. Is it enougth to select factory reset in cwm and wipe the dalvik cache manualy?
What can I do?
With besteht regard
Mirko (NemesisMF)

What if it is a recovery problem?

Thought about that too.
Should i try twrp or philz?

I switched to Philz Recovery and flashed S4 Echoe Rom v42 without any Problems.
CWM seems to have a problem to falsh TW Lollipop images ower an existing CM12 an the I9505.

You need to do full wipe not just cache.

ranger4740 said:
You need to do full wipe not just cache.
Click to expand...
Click to collapse
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.

Factory wipe is not full wipe, you need to do a full wipe as in format to install new rom, phillz recovery has this feature can't remember exactly where, I think its under advanced.
Just have a look in the sub menus.
Just to explain it better when you do a full wipe it deletes every part of the existing
Rom including the system, data and cache and some other stuff completely removing the android operating system, so unless the rom you install does a wipe before install parts of the existing system will remain and can cause boot issues. For example as you've already discovered you are trying to install a tw rom over an existing cyanogenmod 12 installation which Will cause it to hang on boot.

NemesisMF said:
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Click to expand...
Click to collapse
Do you mean a factory reset from within Android itself? If so, then that's a complete obsolete step. When before flashing a rom you should perform a factory reset, then they always mean a full wipe from the recovery. You need to do a full wipe from the recovery. That means the /system partition is being wiped. You will see it in the screen during the wipe if it wipes /system.
But it also could have been a problem of CWM. I don't think it is being updated anymore, so better use TWRP or Philz.