Database Develop

[Q] Unable to revive phone! In dire need of help!

Hello XDA community!
I have a big problem, I have already flashed several custom ROMs and even stock firmwares, with Odin and Heimdall too without any issues, but now I'm completely unsure what happened. I flashed CM KK ROM a while ago and phone went into bootloops and giving errors in recovery. I have experienced and successfully dealt with these problems before, but now I just can't solve those.
So the problem is, my phone is either bootlooping, or giving me the "can't mount sdard" or "mmcblk0p1" errors. I have read lots of threads to solve this but none of them seems to work. I tried flashing all kinds of stock firmwares (Eclair, Froyo, GB) with and withou Re-Partition, but I still get those errors everytime. In recovery, I tried manually format and mount data and sdcard but it gave me the can't mount errors. I also flashed dbdata.rfs, and custom Kernels, but nothing works. I also read that my internal SD card is corrupted and I have to manually partition it with a 8GB external SD card but I own only a 2GB one.
So I really hope some of you clever guys can give me some help, or atlest bring me closer the the solution!
Thanks for the answers!

bp1122 said:
So the problem is, my phone is either bootlooping, or giving me the "can't mount sdard" or "mmcblk0p1" errors.
Click to expand...
Click to collapse
try using the correct version of CWM and flashing the KK ROM (download again) again follow this
If still same, read this and look at using ADB or speedmod kernel to format the corrupt partition
Check this out! Links to useful Guides and " Banned " Documentaries ​

Thanks for the fast answer!
I checked and followed the intstructions in the links and flashed stock JVU, then also the fixed JVU kernel from your post, but I still get the "E:failed to mount /sdcard (files exists),
E:copy_dbdata_media:Can't mount /sdcard" error even after flashing dbdata.rfs However I didn't try the Speedmod Kernel becouse after download it's just a zImage file without the .tar so Odin cabt recognize it and I do not know how to compress to that format!
Thanks for the answers!
Update: I have managed to flash Speedmod kernel, and I could convert SYSTEM filesystem, but when I try to convert filesystems to RFS it gives me the "cant mount/dev/block/mmcblk0p1" and "cant mount /mnt/sdcard" errors... This is like an infinite loop of errors and I am to unfamiliar with this to cope with. Please help

Try to open terminal and type this commands
su
fsck -y /dev/block/mmcblk0p1
It is command to check file system for errors and repair it. Please write about results.
Отправлено с моего GT-I9001 через Tapatalk

Dark_Sleipnir said:
Try to open terminal and type this commands
su
fsck -y /dev/block/mmcblk0p1
It is command to check file system for errors and repair it. Please write about results.
Отправлено с моего GT-I9001 через Tapatalk
Click to expand...
Click to collapse
I'm sorry I don't understand what kinda terminal you are talking about :/ I can't turn on my phone only recovery and download mode works. Sorry but I'm new to this stuff...but thanks for the reply!

Probably you can execute the command Dark_Sleipnir said by going to Download Mode, then connect the phone to your PC, then access the phone through ADB...

c-droid said:
Probably you can execute the command Dark_Sleipnir said by going to Download Mode, then connect the phone to your PC, then access the phone through ADB...
Click to expand...
Click to collapse
I figured it out that I must use ADB (for the 1st time ever) I have managed to set up ADB but when i type su or fsck the cmd says the system cant recognize those as commands. Can you provide the exact commands? By the way if I connect the phone to PC my phone drives appear as transparent in My Computer and i cannot open nor format them (this happens only in recovery mode, in download mode there are no drives showing up at all, not even in the device manager). Maybe thats the problem?
Thanks for the help!

Sorry, I don't know if you could enter Android terminal console through Recovery, I haven't use ADB also. I just understand (have read it from some Android tutorial/guides) that you could enter Android terminal console via ADB...

I can enter ADB in recovery mode, and it recognizes my device (I tried "adb reboot recovery", works like a charm), my problem is that it won't recognise "su" and "fsck" commands. I appreciate your help!

Try to use "adb shell" command - it emulate android terminal via PC adb. Also if fsck does not working try "mke2fs -S /dev/block/mmcblk0p1"
Отправлено с моего GT-I9001 через Tapatalk

adb - can't mount system

I've noticed that I'm unable to mount /system using adb to pull or push files. Whether I use adb remount or mount -o rw,remount blahblahblah /system through adb or terminal.
If I open root explorer and mount system rw, it will then let me pull or push.
I've read its because of not having insecure adb. Now this seems to be only on a stock ROM or my stock rooted.
I sent it through the kitchen again and unpacked the kernel, chose the adb insecure option, repacked ...rebuilt...flashed...and still the same.
How can I get around this?
Sent from my SAMSUNG-SM-G870A using Tapatalk

Nickovtyme said:
I've noticed that I'm unable to mount /system using adb to pull or push files. Whether I use adb remount or mount -o rw,remount blahblahblah /system through adb or terminal.
If I open root explorer and mount system rw, it will then let me pull or push.
I've read its because of not having insecure adb. Now this seems to be only on a stock ROM or my stock rooted.
I sent it through the kitchen again and unpacked the kernel, chose the adb insecure option, repacked ...rebuilt...flashed...and still the same.
How can I get around this?
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
you can't change anything in the kernel ramdisk, Locked BL prevents that. :crying:

Copy firmware using clockworkmod

Hi guys, I received a sxl with no firmware. I can only manage to use the clockworkmod. I tried to copy the file from my pc using the command adb push, and even ms-dos says it is everything fine, he writes at what speed, how many bytes and how much time passed, when I go to install zip from sdcard the phone doesn't show me the firmware...
What am I doing wrong???
I was thinking about to try install using sideload,but I don't know how it wok.
Any help?
Regards

using adb sideload is easy:
just type: adb sideload filename.zip
before you have to set in cwm the sideload feature..
Gesendet von HUAWEI Ascend P7-L10 B609 - rooted

by set the feature in cwm you mean just to click on it?

Dirty ROOT solution - for unlocked BL

I have ported the Z5 Compact root method to Z5.
Please note that both recovery.img and kernel img are different from the Z5 Compact thread. Do not use recovery or kernel for Z5 Compact on your regular Z5 phone.
Disclaimer
I am well aware that this is not the nicest method of rooting, but I got the phone a few hours ago and haven't got the time to put together a better way.
Credits
@Tommy-Geenexus for Zombie kernel
@AndroPlus for Z5 recovery and guidance :good:
@Chainfire for SuperSU
Guide
First, you need to unlock you bootloader (I know, I know, now stop weeping :crying::crying::crying
A rooted device does not boot using default kernel, so you need to install an insecure kernel.
I have repacked stock Z5 (32.0.A.4.11) kernel to disable Sony RIC, dm verity, make it insecure, etc.
Flash using:
Code:
fastboot flash boot z5_stock_fixed.img
Reboot your phone using:
Code:
fastboot reboot
And verify that it works as expected.
Now, reboot your phone to bootloader again (see info how to at the end of post).
Then issue:
Code:
fastboot boot recovery.img
This recovery is partly broken, but it works well enough to install root.
Thanks to @AndroPlus for TWRP.
The phone will boot to a black screen, but you can connect to it using ADB.
You need to manually mount the system and userdata partition by issuing:
Code:
adb shell mount /dev/block/platform/soc.0/by-name/system /system
adb shell mount /dev/block/platform/soc.0/by-name/userdata /data
If you get this error:
mount: mounting /dev/block/platform/soc.0/by-name/system on /system failed: No such file or directory
You probably just need to wait a while and try again. You usually have to wait ~120 sec for the mount to work. Be patient.
If you got /system and /data to mount, you can now push SuperSU to the phone and install it:
Code:
adb push UPDATE-SuperSU-v2.46.zip /data/media/0/
adb shell twrp install /data/media/0/UPDATE-SuperSU-v2.46.zip
adb shell rm /data/media/0/UPDATE-SuperSU-v2.46.zip
If it all works, just reboot and enjoy root:
Code:
adb reboot
Files
z5_stock_fixed.img
recovery.img (for Z5)
Extra info
Boot to bootloader by adb command:
Code:
adb reboot bootloader
or by turning off the phone, and then hold down VOL UP while plugging in the USB cable.

works like a charm, finally I can use my Z5 =)
thank you mate.

Awesome, do we need to backup TA partition anymore to keep X-Reality etc?

komugi said:
Awesome, do we need to backup TA partition anymore to keep X-Reality etc?
Click to expand...
Click to collapse
You need to unlock the bootloader, so I don't think you can backup the TA partition.

Does this change anything in the kernel? Will battery life be the same?

If you unlock yourbootloadeR TA partition it lost forever! You can't get it back and things like x-reality won't work anymore.
Gesendet von meinem E6653 mit Tapatalk

We know that, but it must have a way (yet to find?) to backup and restore the TA partition just like previous devices (it was possible on Z and Z1, don't know about the others)
Sent from my E6653

are there unlocked bootloader Z5s? how do we check if our bootloader is locked?

GOOGLE
Go to calls,enter *#*#7378423#*#* and go to service info-configuration.
Sent from my E6653 @ XDA Portal

I ran through these instructions, and I now have root privileges, but I can't write to /system. Is there something I missed to enable this, or does this just not work?
Sent from my E6653 using Tapatalk

mindstormsguy said:
I ran through these instructions, and I now have root privileges, but I can't write to /system. Is there something I missed to enable this, or does this just not work?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
You need to mount /system as read/write (default: read-only).
You can use an app or shell command to do this.
For example:
http://forum.xda-developers.com/wiki/Guide:Using_the_Terminal#Mount

nilezon said:
You need to mount /system as read/write (default: read-only).
You can use an app or shell command to do this.
For example:
http://forum.xda-developers.com/wiki/Guide:Using_the_Terminal#Mount
Click to expand...
Click to collapse
I see I have this problem too.
Using terminal cmd
# mount -o rw,remount /system
replies
mount: Operation not permitted
Also not possible with Root Explorer
In this way it's also not possible to install Busybox.
I reinstalled kernel but didn't change anything.

Operation not permitted for me too. And I also tried reinstalling the kernel before posting.
Sent from my E6653 using Tapatalk

mindstormsguy said:
Operation not permitted for me too. And I also tried reinstalling the kernel before posting.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Hmm. Same for me. Maybe Sony RIC or SELinux is not fully disabled after all.

harfot said:
I see I have this problem too.
Using terminal cmd
# mount -o rw,remount /system
replies
mount: Operation not permitted
Also not possible with Root Explorer
In this way it's also not possible to install Busybox.
I reinstalled kernel but didn't change anything.
Click to expand...
Click to collapse
nilezon said:
Hmm. Same for me. Maybe Sony RIC or SELinux is not fully disabled after all.
Click to expand...
Click to collapse
@DooMLoRD:
Hello my friend,
Long time no see - hope you are doing well.
Am I wrong if I remember this "half" root once in a DooMKernel? Cannot find it but I'm sure you know the reason.
Thanks

It looks like Zombie kernel doesn't have changes like this:
https://github.com/AndroPlus-org/an...mmit/f0544c997bb22da293005ffcaaeeeb4a55394c8d
I think he can improve this current method...

AndroPlus said:
It looks like Zombie kernel doesn't have changes like this:
https://github.com/AndroPlus-org/an...mmit/f0544c997bb22da293005ffcaaeeeb4a55394c8d
I think he can improve this current method...
Click to expand...
Click to collapse
I don't think it is needed.
Setting:
CONFIG_SECURITY_SONY_RIC=n
in kernel config seem to solve the remount rw problem.
It's much cleaner to remove Sony RIC module this way, than just patching it, IMHO.
It's sad this can't be done by just repacking stock ramdisk.

@nilezon do we need a new compiled kernel for every new firmware?

Azdian said:
@nilezon do we need a new compiled kernel for every new firmware?
Click to expand...
Click to collapse
You can run an older kernel, but the latest is often then best.

nilezon said:
I don't think it is needed.
Setting:
CONFIG_SECURITY_SONY_RIC=n
in kernel config seem to solve the remount rw problem.
It's much cleaner to remove Sony RIC module this way, than just patching it, IMHO.
It's sad this can't be done by just repacking stock ramdisk.
Click to expand...
Click to collapse
Is the fixed version in the main post now, then?

Write error in System - Device rooted - Any fix ?

I am using OOS 3.5.4. My device is rooted. But I cannot make changes to system files, when I am trying to remove a file from 'init.d' folder it says resource busy. When I am trying to copy a file to the init.d folder it says it failed to copy. Same with other folders in system. How to explore root and write ?

ProudRed said:
I am using OOS 3.5.4. My device is rooted. But I cannot make changes to system files, when I am trying to remove a file from 'init.d' folder it says resource busy. When I am trying to copy a file to the init.d folder it says it failed to copy. Same with other folders in system. How to explore root and write ?
Click to expand...
Click to collapse
Have u rooted your phone with systemless meathod or normal usual method with su in system partition
if you use the normal method then mount ur system as read wite use Root explorer apps like ES file explorer, Root Explorer etc.
Press the thanks button if i helped u.

Azaruddin said:
Have u rooted your phone with systemless meathod or normal usual method with su in system partition
if you use the normal method then mount ur system as read wite use Root explorer apps like ES file explorer, Root Explorer etc.
Press the thanks button if i helped u.
Click to expand...
Click to collapse
Hi, mine is system less method. I have been using ES File explorer, after mounting when I am trying to delete any file it says resource busy.

One of the examples.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A3003 using Tapatalk

ProudRed said:
One of the examples. View attachment 4167740
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
ok. First Enable the root explorer option from the navigation drawer of the ES File Explorer the mount ur system read write mode and then try.
if that doesn't work boot into twrp and mount ur system as read write mode and then try :good:

Azaruddin said:
ok. First Enable the root explorer option from the navigation drawer of the ES File Explorer the mount ur system read write mode and then try.
if that doesn't work boot into twrp and mount ur system as read write mode and then try :good:
Click to expand...
Click to collapse
Root explorer is enabled. But rw is mounted only when I am doing it from twrp

ProudRed said:
Root explorer is enabled. But rw is mounted only when I am doing it from twrp
Click to expand...
Click to collapse
Since ur using Systemless root first boot into ur TWRP and mount us system as R/W and try. but if u modify ur system the u will trigger the dm-variety. if u want to modify ur system then go for usual normal root method. root ur device with superSU.

Azaruddin said:
Since ur using Systemless root first boot into ur TWRP and mount us system as R/W and try. but if u modify ur system the u will trigger the dm-variety. if u want to modify ur system then go for usual normal root method. root ur device with superSU.
Click to expand...
Click to collapse
Flashing super su from twrp ? Still its systemless root I guess. As it doesnt gets installed in the system.
Sent from my ONEPLUS A3003 using Tapatalk

ProudRed said:
Flashing super su from twrp ? Still its systemless root I guess. As it doesnt gets installed in the system.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
using SuperSU u cant root ur device in both the method either systemless or using system.
Are u using magisk? give some more info about ur scenario.

Azaruddin said:
using SuperSU u cant root ur device in both the method either systemless or using system.
Are u using magisk? give some more info about ur scenario.
Click to expand...
Click to collapse
Yes I am using magisk but rooted with super su. Magisk is the root manager. Previously when I rooted with super su, it didnt get installed into the system. I flashed from twrp

ProudRed said:
Yes I am using magisk but rooted with super su. Magisk is the root manager. Previously when I rooted with super su, it didnt get installed into the system. I flashed from twrp
Click to expand...
Click to collapse
Try the Magisk module "Magisk init.d | Universal init.d enabler!"
https://forum.xda-developers.com/apps/magisk/module-magisk-init-d-universal-init-d-t3579305
or
try the following commands from the twrp terminal:
su
mount -o rw,remount /system
mkdir /sdcard/init/
cp /system/etc/init.d /sdcard/init/
rm -r /system/etc/init.d/*

Azaruddin said:
Try the Magisk module "Magisk init.d | Universal init.d enabler!"
https://forum.xda-developers.com/apps/magisk/module-magisk-init-d-universal-init-d-t3579305
or
try the following commands from the twrp terminal:
su
mount -o rw,remount /system
mkdir /sdcard/init/
cp /system/etc/init.d /sdcard/init/
rm -r /system/etc/init.d/*
Click to expand...
Click to collapse
already using the init.d enabler. It does mount the init.d files. But I cannot make any changes to system files.
I trued using these commands in terminal app. When I entered this "mount -o rw,remount /system" got "invalid argument" error.

ProudRed said:
already using the init.d enabler. It does mount the init.d files. But I cannot make any changes to system files.
I trued using these commands in terminal app. When I entered this "mount -o rw,remount /system" got "invalid argument" error.
Click to expand...
Click to collapse
hmm k then no other go u have to root ur device with system based root then only u can modify the system partition.

Azaruddin said:
hmm k then no other go u have to root ur device with system based root then only u can modify the system partition.
Click to expand...
Click to collapse
How do I do that ? these days super su have become systemless. Any other alternative ?

ProudRed said:
How do I do that ? these days super su have become systemless. Any other alternative ?
Click to expand...
Click to collapse
First make an Nandroid back up and try these steps, so that if any thing goes wrong u can restore the backup (recommended).
Step 1: boot the device and full unroot in Supersu app.
Step 2: try to flash the stock boot.img if that fails flash the stock OOS (dirty flash is enough, no need of clean flash)
Step 3: boot into twrp >go to the terminal > and type: "echo SYSTEMLESS=false>>/data/.supersu"
Step 4: now flash supersu v2.71 or higher in twrp (if you read the logs, it should say something like "installing in system mode")
Then u will be installing su in system mode.
Smash the thanks button if i helped u

Azaruddin said:
First make an Nandroid back up and try these steps, so that if any thing goes wrong u can restore the backup (recommended).
Step 1: boot the device and full unroot in Supersu app.
Step 2: try to flash the stock boot.img if that fails flash the stock OOS (dirty flash is enough, no need of clean flash)
Step 3: boot into twrp >go to the terminal > and type: "echo SYSTEMLESS=false>>/data/.supersu"
Step 4: now flash supersu v2.71 or higher in twrp (if you read the logs, it should say something like "installing in system mode")
Then u will be installing su in system mode.
Smash the thanks button if i helped u
Click to expand...
Click to collapse
Thanks I will try it once back home. Btw how to flash the stock boot image ? Extract it from the zip ?
Sent from my ONEPLUS A3003 using Tapatalk

ProudRed said:
Thanks I will try it once back home. Btw how to flash the stock boot image ? Extract it from the zip ?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
hmm you can also do that or dirty flash the full rom zip of OOS 4.1.3.

Azaruddin said:
hmm you can also do that or dirty flash the full rom zip of OOS 4.1.3.
Click to expand...
Click to collapse
I am on 3.5.4. That will do right ?
Sent from my ONEPLUS A3003 using Tapatalk

ProudRed said:
I am on 3.5.4. That will do right ?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
hmm s you can flash 3.5.4 :good:

Azaruddin said:
hmm s you can flash 3.5.4 :good:
Click to expand...
Click to collapse
After the optimization of apps are done, the device gets into soft reboot mode and stuck at boot animation. (the brightness is very dimmed).