[Q]Galaxy nothe stuck on boot logo after installing philz kernel - General Questions and Answers

Please help me i rooted my Galaxy note (N7000) a week ago and it worked fine,then today i tried installing philz kernel ,i boot the galaxy note and after the first boot logo my phone turnd off
the first thing i did was go into recovery and did a wipe cache partition
then wipe data/factory reset
then i went to advance (reminder: i used philz kernel)
then i did a wipe delvik stats
then i go back and went into mounts and storage
and i formated /cache
/system
/data
/preload
/emmc
then when i tuned on the phone and the phone just stayed on the galaxy note logo (the first logo)
and did nothing
please help i only have 3 hours b4 my dad gets home from work
please anyone reply

Mate, you've formatted all your partitions. There is nothing on your phone to boot, therefore it's not booting anything.
Never, ever format any partitions except /data and /cache, unless you know exactly what you are doing. By formatting /system, /preload and /emmc, you've wiped the contents of your phone, including your ROM. You're lucky it's not a brick.
You will need to obtain a stock ODIN .tar for the N7000, and flash back to complete stock. That is the only way to fix what's done - you can't just flash a zip and fix it. There are plenty of tutorials for this in the N7000 sections.
Good luck.

Related

Sk4g stuck in recovery mode

I'm trying to flash Glorious Overdose ROM to my sk4g. Rooted...check.
CWM...check.
Booted the phone into recovery and got the regular recovery screen.
clicked on 'reinstall packages'
Got the orange Clockwork recovery.
clicked on wipe data/factory reset.
following screen shows:
formatting /data
formatting /cache
formatting /sd-ext
E: format_volume make_extfile4fs failed on /dev/block/mmcblk0p2
formatting /sdcard/.android_secure...
And it stopped right there.
It's been like this for the past 15 minutes. I have the phone plugged into my computers usb port to keep it powered up during the flash.
I don't want to pull the battery for fear I might brick the phone. The sk4g has the latest kj2 update. I'm somewhat of a noob. I have rooted and added CWM,but this is my first time flashing a custom ROM. Pls help. CWM version 4.0.0.2
u must heimdall or odin back to stock via download mode n btw wipe cache then wipe data first
Was able to get back to stock rom by pulling battery and rebooting, tried wiping cache first then data, and same problem.

Bootloop + Unable to mount /data [SOLVED]

Hi guys, I'm so frustrated, I can't fix my Nexus 5. I'll explain.
I wanted to flash stock firmware and did it but now my Nexus 5 is stuck on bootanimation, I don't know what to do!
Tried with TWRP, and it says Unable to mount /data, same with CWM...
Hope you help me, thanks in advance.
- EDIT -
I fixed it, by flashing every img inside the image-hammerhead...zip, TWRP and wiping cache. The first time it booted I had unknown baseband and IMEI and like 4 fc's. Then I found this post, so I flashed it all again and now it's 100% working.
All you had to do is perform a factory reset from the stock recovery to fix it.. Or even a /cache format could have fixed it..
Anyways, glad you fixed it yourself!

[Q] How do I repair partitions on my rooted tab?

I have a galaxy pro 12.2 rooted with CM12.1.
I tried to install a nightly but I couldnt wipe the cache. The console always says "can't mount cache"
I tried it 300 times and rebooted 300 times and it wouldn't mount.
After googling for a little bit, a majority of the pages I found said TWRP isnt stable with partitions and I was supposed to choose rm -f instead of formatting the partition or it corrupts the partition.
I'm assuming this is what happened to me because I just wiped the cache instead.
I wiped the cache and dalvik and system and did a factory reset and then I installed the nightly. It would boot but then it got stuck on the boot screen. So I tried to clear the cache again but I got the same error.
Then I reset my phone and wiped /system and data but not cache because I couldnt mount cache. And then I installed a stock rom. This rom also gets stuck on the boot screen. So now I have a tablet with a stock rom installed and what I'm assuming is a corrupt cache partition.
Also, I did back up before I installed the nightly. I have a working backup on my phone. It worked fine when I used it and it gave no errors when I backed it up and I got no errors when I restored it other than cant mount cache.
So I tried to boot into my working backup too. Still didnt work.
How do I fix this?

[Q] TWRP crahes and reboots when wiping

I've read this issue with other devices, however. i've not found a solution for this yet
I'm new to this forums, let me know if i don't do something right.
I've been using Alberto97's AOSP Lollipop 5.1.1, it's my first custom rom install, i got it on
the first try, TWRP 2.8.6.0 running with no problems.. flashed other stuff like moto camera, marshmallow bootanim, and that's all
Last week i've tried to update to the CAF latest version of his build, however, TWRP
reboots when i try to wipe the /data partition, in the custom TRWP 2.8.7.0 thread found
i might need to repair the partition, i tried it with no success, repaired /cache with no problem, but when i try to fsck /data on TWRP it gaves me an error, haven't tried /system yet.
tried using CWM and it got stuck at wiping /data for like an hour (endless loop), i rebooted, the data was wiped, but i couldn't flash the ROM image, rebooted to clean system with no problems, it wipes cache and dalvik with no issues.
What's causing this? i have not faced apps FC or anything, just the TWRP random crashes at wiping, i'm using a Moto G XT1032 16GB TWRP 2.8.6.0 No custom kernel or non official recovery.
justpaste.it/wipedar
Leaving recovery.log on external page for reference.
hope you can help, thanks in advance.
Same problem here
You can use CWM by PhilZ for fixing what I think is a broken symlink to the emulated internal storage card.
I am using philz-6.58.7-falcon that you can find and download here: http://forum.xda-developers.com/showthread.php?t=2639583
Once you have flashed the new recovery you can go to "Advance menu", then to "change sdcard target" and define it to /data/media (you just have to tap on the option to set it).
Go back, select "Wipe option", then "Wipe User media" and the process should be successful.
If you reinstall TWRP and wipe "/data" now the rebooting problem should be gone and everything back to normal.
Hope this helps for you.
By the way this is my very first post here. So I hope I am doing this right.
Greetings.
Thank you for the help, i fixed it by repairing the userdata partition with the latest TWRP

Galaxy S7 930f can't access twrp

Hello, thanks for your help.
It seems I bricked my galaxy s7 while trying to format the /data partition.
I installed TWRP 3.2 and a custom rom, and everything went smoothly until then.
I tried installing an audio mod which throwed a " can't mount /data" error, searching for solutions I read that formatting the data partition to fat and back to ext4 should solve the problem, I tried formatting it to fat with TWRP, however on the first try I got a message that it suceeded, followed by a message that /data could not be mounted, TWRP seemed to be still working (there was no reboot button or any other buttons, just a "working" bar). After giving the phone 3 hours I decided to restart it, now I can't access TWRP; it stays on it's "splashcreen", and of course the phone won't boot.
I'm having a rough time with this so I will appreciate it a lot if you can help me.
Thank you.
Boot to download mode, flash stock firmware using Odin, then retry the TWRP installation.
For wiping data, you have to make sure you use the wipe option that makes you type out 'yes' to wipe, the other factory wipe methods don't actually properly wipe the partition.
iirc you also then need to flash the dm no verity zip from the TWRP thread.
Bro you didn't have to do anything but just formating the phone in the first place. Aassuming you're on oreo , it happens to a lot of people and myself, after flashing a kernel twrp was unable to munt data, all i had to do is a data format in twrp that fixed the problem .

Categories

Resources