Database Develop

[Q] Help! bricked + corrupt system?

I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?

uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.

First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color

Yes! Thank you! That worked!!

It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom

[Q] Note randomly turns off and gets stuck in bootloop.

I've had my Note for around a month now, and I'm having an issue where the phone will shut itself down at a random time.
If you try to turn the phone on, it'll get stuck on the Galaxy Note N7000 splashscreen. Occasionally if I go into recovery
and select Reboot Phone Now it'll boot properly, but very rarely does it work. I've also tried leaving it on the splashscreen
and coming back an hour later and it will be fine again. It happened twice yesterday and once today.
If I can't get it to boot, the only thing I can do is restore a CWM backup, but doing that multiple times a day is very frustrating.
I'm running a stock XXLSA deodexed and rooted ROM. I've also tried a stock XXLSA non-deodexed and unrooted ROM with the
same issue. The phone was working fine on ICS 4.0.4, but I really need the use of MultiWindow so downgrading is not an option.
I'm using Philz Kernel 3.99.
Any ideas?

iPWNtehNOOB said:
I've had my Note for around a month now, and I'm having an issue where the phone will shut itself down at a random time.
If you try to turn the phone on, it'll get stuck on the Galaxy Note N7000 splashscreen. Occasionally if I go into recovery
and select Reboot Phone Now it'll boot properly, but very rarely does it work. I've also tried leaving it on the splashscreen
and coming back an hour later and it will be fine again. It happened twice yesterday and once today.
If I can't get it to boot, the only thing I can do is restore a CWM backup, but doing that multiple times a day is very frustrating.
I'm running a stock XXLSA deodexed and rooted ROM. I've also tried a stock XXLSA non-deodexed and unrooted ROM with the
same issue. The phone was working fine on ICS 4.0.4, but I really need the use of MultiWindow so downgrading is not an option.
I'm using Philz Kernel 3.99.
Any ideas?
Click to expand...
Click to collapse
That's a common issue with the JB leaks. You have the following options:
- Do a nand backup, do a full wipe, format cache, system and preload, restore your nand backup (might work)
- Do a full wipe, format cache, system and preload, reflash the rom (works always)
Even if you manage to fix it, be prepared that the problem will occur again. For me it was always the same, I flashed the rom, it worked for several days, suddenly it got stuck at the boot logo, I fixed it, after several days the bootloop reoccured.... Eventually I decided to flash a stock ICS rom in order the get a stable device.

May have bricked my phone! Need help!

Here's the story:
I bought an AT&T HTC One that had an unlocked bootloader and was rooted. I SIM-unlocked it so I could use T-Mobile. Everything worked perfectly fine.
Today I decided I wanted to try out AR HD. I use CWM to flash it, and have a few problems the first few times because of Aroma Installer. Eventually it installs fully, but when I rebooted, something went wrong. It wouldn't boot up. Eventually I had to wipe everything (including the internal storage, which had a backup of mine), and now I'm trying to flash a working rom on this phone.
So now I've tried pretty much everything. The main problem now is that in recovery, when I try to flash a ROM it says it can't mount the the sdcard. I've tried using Nocturnal's method of using the stock recovery to wipe the partitions and everything, but it still gives the the can't mount error.
If anyone could help me I would really appreciate it! Looks like I'm going to have to get a SIM adapter to use with my Galaxy Nexus until I can get this fixed.

aka757 said:
Here's the story:
I bought an AT&T HTC One that had an unlocked bootloader and was rooted. I SIM-unlocked it so I could use T-Mobile. Everything worked perfectly fine.
Today I decided I wanted to try out AR HD. I use CWM to flash it, and have a few problems the first few times because of Aroma Installer. Eventually it installs fully, but when I rebooted, something went wrong. It wouldn't boot up. Eventually I had to wipe everything (including the internal storage, which had a backup of mine), and now I'm trying to flash a working rom on this phone.
So now I've tried pretty much everything. The main problem now is that in recovery, when I try to flash a ROM it says it can't mount the the sdcard. I've tried using Nocturnal's method of using the stock recovery to wipe the partitions and everything, but it still gives the the can't mount error.
If anyone could help me I would really appreciate it! Looks like I'm going to have to get a SIM adapter to use with my Galaxy Nexus until I can get this fixed.
Click to expand...
Click to collapse
Download the All-In-One toolkit from the development section and follow the directions to ADB SIDELOAD a ROM onto your phone.
EDIT: now with a link to the thread: http://forum.xda-developers.com/showthread.php?t=2183942&highlight=all-in-one

Well, I got it to flash a ROM, but now there's a new problem...
I got it to flash the ROM by using CWM to flash a ROM after using Nocturnal's method instead of TWRP.
So now I'm in setup, and am prompted to select a WiFi network. I selected my network, put in the password correctly (it shows connected), and now when I press Next, it transitions forward and then straight back to the WiFi page. Won't let me progress past it.
I think it might have something to do with HTC Sync Manager (I have it installed and running just fine), but I don't know what to do about it.

aka757 said:
Well, I got it to flash a ROM, but now there's a new problem...
I got it to flash the ROM by using CWM to flash a ROM after using Nocturnal's method instead of TWRP.
So now I'm in setup, and am prompted to select a WiFi network. I selected my network, put in the password correctly (it shows connected), and now when I press Next, it transitions forward and then straight back to the WiFi page. Won't let me progress past it.
I think it might have something to do with HTC Sync Manager (I have it installed and running just fine), but I don't know what to do about it.
Click to expand...
Click to collapse
You can skip the wifi setup. Try changing the channel on the router sometimes phones and routers on certain channels don't get along.

Z1 stuck in boot loop after fumbling my way around a Chinese recovery

So I recently tried updating MIUI v5 to MIUI v6. However, I stupidly opted for the FOTA update, rather than updating using recovery.
After running the update, my phone rebooted and it worked fine, MIUI v6 running great. However, because I'd updated using the in-built updater, my data and apps were still there from before. This was causing no-end of 'process stopped running' alerts, which drove me crazy after around 10 minutes.
Therefore, I decided to try and wipe my data. I went to the recovery menu and found that MIUI had installed its own Chinese recovery, my previous TeamWin one was gone. So I fumbled around and managed to find the 'Wipe data' etc. option, and chose it. I was presented with a couple more options which I didn't understand, and (stupidly) accepted both. This left me with a phone that would no longer boot past the 'Sony' logo. I was also unable to access the Chinese recovery menu.
Feeling a little worried at this point, I started to Google around for guides on how to flash a recovery back onto a phone stuck in a boot loop. After hours of searching, I decided it wasn't possible and instead follow a guide for fixing 'boot loops' through flashing an original Sony 'ftf' firmware using flashtool.
Now, the guide I was following was quite old, and provided a link to 'C6903_14.2.A.0.290_Global LTE' - so this is what I used to flash (which I'm now regretting). Before flashing, I was presented with some options, for which the guide I was following recommended I deselect the 'kernel' option. So I did this too.
After around 10-15 minutes and what seemed like a successful flash, I tried turning the phone on. This time, the Sony logo appears, then disappears to a black screen, and then the backlight turns off, followed by the Sony logo, then a black screen, then backlight turning off, etc. So slightly different behaviour to before, but still boot looping.
I think what may have happened is that MIUI includes an updated kernel, and through flashing the 14.2.A.0.290 firmware without a kernel, I've introduced some sort of incompatibility.
The problem I'm having now is getting another firmware onto the phone in order to resolve this. For some reason, despite flashtool recognising the phone being plugged in with flash mode, it refuses to load the firmware - I'm instead presented with the message:
"You must have the according fsc script to flash this device."
Does anyone know how I might be able to get around this? I admit to being a bit of a noob when it comes to flashing so have probably dug my own hole here, and seem to have left myself completely unable to work out what I need to do in order to get back out! Any help would be hugely appreciated.

Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!

langauld said:
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
Click to expand...
Click to collapse
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)

Just2Cause said:
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Click to expand...
Click to collapse
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.

langauld said:
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
Click to expand...
Click to collapse
Glad I could help.

Phone randomly shows boot animation on custom rom

Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)