Related
"Turning wifi on..." is all my Wi-Fi settings says after flashing CM10.2. I probably did something wrong. Initially I flashed CM with twrp 2.4, which didn't boot. So I updated to the current twrp 2.6, wiped caches & system, and reflashed CM and rebooted. It seems fine aside from no wireless, so I've attached logcat here in hopes someone can point out my mistake. Apologies and appreciation in advance.
binaries:
cm-10.2-20131007-NIGHTLY-tf700t.zip
gapps-jb-20130813-signed.zip
briankb said:
"Turning wifi on..." is all my Wi-Fi settings says after flashing CM10.2. I probably did something wrong. Initially I flashed CM with twrp 2.4, which didn't boot. So I updated to the current twrp 2.6, wiped caches & system, and reflashed CM and rebooted. It seems fine aside from no wireless, so I've attached logcat here in hopes someone can point out my mistake. Apologies and appreciation in advance.
binaries:
cm-10.2-20131007-NIGHTLY-tf700t.zip
gapps-jb-20130813-signed.zip
Click to expand...
Click to collapse
Have you updated to the bootloader required for CM 10.2?
sbdags said:
Have you updated to the bootloader required for CM 10.2?
Click to expand...
Click to collapse
No I didn't, thanks for pointing me in the right direction. I was at 10.4.4.20.
Update: same problem after wiping system/caches and reinstalling. My only guess at this point is twrp 2.5, going to try again with cwmod
Well I didn't get far with that. After installing ClockworkMod 6.0.3.9 on my tf700t and it shows an error 'E: Can't mount /sdcard' when selecting 'choose zip from /sdcard'
show log produces several messages including:
e: Can't mount /sdcard
I: Skipping execution of extendedcommand, file not found..
I: using /data/media for /sdcard
mount: mounting /dev/block/mmcblk0p8 (file exists)
E: Can't mount /sdcard
[solved]
I solved the issue by formatting /data.
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!
So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..
ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.
Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:
ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !
Hey everyone, I have this very strange issue
The other day I made a nandroid backup because I wanted to mess around with some stuff I wasn't sure was going to work. I then restored the backup, and tada, bootloop. I was stuck on the boot animation. Tried a deleting data/dalvik/cache from recovery (CWM 6.0.4.7), installing rom again, but nothing worked.
Now, what I did may or may not have been smart. I wiped everything using "wipe userdata" in the adb shell. Everything gone. Now I want to put on a working rom again, but I can't. Two problems:
1. My CWM recovery is doing this . Not only when I boot into it trough bootloader, but, maybe this is because I don't have a working rom, it also seems to go into it after my bootloop attempts to boot twice, as seen here.
I have no idea what's happening and why and how. It just keeps flashing like this and I can't access the menu. I tried reflashing, flashing the touch version, flashing TWRP which doesn't have default adb access, and flashing it once again but same result. So I can't choose a rom to flash. How do I fix this?
2. I can still push files to /data/media/ and /sdcard/, but after that I have no way to install them. No tutorial I found seemed to work, e.g this one from xda says I have to mount /data/ but when I do that I get
> C:\sdk\platform-tools>adb shell
~ # mount data
mount data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
And I've also done this one which states the rom should install, but it doesn't. The cd and push are successful, but I can't do anything with it. I also think my /sdcard/ got unmounted at some point, but I was able to push a file to it so not sure here.
Does anyone know how to fix this. I have no idea what to do, pretty hopeless at this point. Thanks so so much if you have any tips
-Josh
Duplicate.
http://forum.xda-developers.com/general/xda-assist/bootloop-nandroid-restore-tried-t3153174
1) Accidentally wiped all data including Internal Storage
2) Twrp 3.0 is working, but can't able to install any rom, Getting E:failed to mount / cache (Invalid argument) etc etc..
3)Getting "NO OS Installed" message in TWRP &- Internal Storage size is 0 (TWRP)
4) Followed Steps to flash factory image (WINDOWS)
Download the factory image fastboot package
Extract the contents of the fastboot package into a folder.
Download this flashing tools package
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.bat, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run flash-all.bat by double clicking on it.
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button
But getting this error while flashing: http://imgur.com/g3NozUJ
After reboot,phone is stuck at YU logo..
Yuphoria stuck at YU Logo.
I had got notification for the OTA Cyanogen 12.1 Update and I had updated it. But even after reboot, the same 12.1 Update-notification would still appear again.
Later, I switched off Yuphoria to take out the External-SD-Card for data-transfer. Then when I switched on the Yuphoria, this Yu-Logo Boot-Loop Problem has started.
Now, My Yuphoria is Stuck at Yu-Logo on boot... and showing 'cannot mount partitions' errors when I boot custom-recovery twrp.
I have unlocked the bootloader.
From what I read online, I guess the memory partition-tables have got corrupted.... Now how can we solve this corrupted memory problem ?
I read about fastboot-flashing database.rfs or dbdata.rfs in some xda-developers Threads.
-----------------------------------------
I tried flash-all.bat with latest Cyanogen Official 12.1 ROM signed-fastboot.zip file... but still stuck at Yu-Logo on boot....
I fastboot boot trwp 2.6 custom-recovery.img and installed Cyanogen 12.1 ROM signed.zip file from external-sd card. But trwp says cannot mount partitions '/data', '/system', '/cache' etc...
---------------------------------------
I ran the command e2fsck /dev/block/bootdevice/by-name/system in terminal.
Then this message came : 'superblock has an invalid journal (inode 8) ext4'
I entered yes for correction multiple times and the process completed....
But still stuck at YU Logo on reboot.... Please Help.
-----------------------------------
I erased persist, then flashed persist.img.
Then I booted into twrp recovery, and adb sideload cm-12.1-YPG4PAS8A8-lettuce-signed.zip
The sideload started and then stopped with error : failed to unmount /cache ; failed to unmount /data ;
-----------------------------------
I boot into twrp 2.8.7.2 from fastboot-mode using command : sudo fastboot -i 0x2a96 boot twrp.img
Selected Wipe → advanced wipe → selected data :
It shows :
Mount Point : /data , File system : ext4 , Present: Yes, Removable: No, Size:0MB, Used: 0MB, Free 0MB, Backup Size: 0MB
Then I tapped on change/repair file system → change file system → EXT4 → Swiped IT...
Error : Format Failed.
E: Unknown MTP message type: 1
Failed to unmount '/data' (Invalid argument)
Error changing file system.
Updating Partition details.......
Failed to unmount '/system', '/data', '/cache' (Invalid arguments)
....done
Unable to mount storage.
After 'Change File System' Failed, I tried 'Repair File System' and 'Resize File System' also... all Failed similarly....
Only TWRP 2.8.7.2 and lower versions boots successfully in my Yuphoria.
TWRP 3.0.0 will not boot successfully. The TWRP logo will appear and then show command errors, and the phone will restart.
Please help me reinstall OS in my softbricked Yuphoria.
Goodison14 said:
I had got notification for the OTA Cyanogen 12.1 Update and I had updated it. But even after reboot, the same 12.1 Update-notification would still appear again.
Later, I switched off Yuphoria to take out the External-SD-Card for data-transfer. Then when I switched on the Yuphoria, this Yu-Logo Boot-Loop Problem has started.
Now, My Yuphoria is Stuck at Yu-Logo on boot... and showing 'cannot mount partitions' errors when I boot custom-recovery twrp.
I have unlocked the bootloader.
From what I read online, I guess the memory partition-tables have got corrupted.... Now how can we solve this corrupted memory problem ?
I read about fastboot-flashing database.rfs or dbdata.rfs in some xda-developers Threads.
-----------------------------------------
I tried flash-all.bat with latest Cyanogen Official 12.1 ROM signed-fastboot.zip file... but still stuck at Yu-Logo on boot....
I fastboot boot trwp 2.6 custom-recovery.img and installed Cyanogen 12.1 ROM signed.zip file from external-sd card. But trwp says cannot mount partitions '/data', '/system', '/cache' etc...
---------------------------------------
I ran the command e2fsck /dev/block/bootdevice/by-name/system in terminal.
Then this message came : 'superblock has an invalid journal (inode 8) ext4'
I entered yes for correction multiple times and the process completed....
But still stuck at YU Logo on reboot.... Please Help.
-----------------------------------
I erased persist, then flashed persist.img.
Then I booted into twrp recovery, and adb sideload cm-12.1-YPG4PAS8A8-lettuce-signed.zip
The sideload started and then stopped with error : failed to unmount /cache ; failed to unmount /data ;
-----------------------------------
I boot into twrp 2.8.7.2 from fastboot-mode using command : sudo fastboot -i 0x2a96 boot twrp.img
Selected Wipe → advanced wipe → selected data :
It shows :
Mount Point : /data , File system : ext4 , Present: Yes, Removable: No, Size:0MB, Used: 0MB, Free 0MB, Backup Size: 0MB
Then I tapped on change/repair file system → change file system → EXT4 → Swiped IT...
Error : Format Failed.
E: Unknown MTP message type: 1
Failed to unmount '/data' (Invalid argument)
Error changing file system.
Updating Partition details.......
Failed to unmount '/system', '/data', '/cache' (Invalid arguments)
....done
Unable to mount storage.
After 'Change File System' Failed, I tried 'Repair File System' and 'Resize File System' also... all Failed similarly....
Only TWRP 2.8.7.2 and lower versions boots successfully in my Yuphoria.
TWRP 3.0.0 will not boot successfully. The TWRP logo will appear and then show command errors, and the phone will restart.
Please help me reinstall OS in my softbricked Yuphoria.
Click to expand...
Click to collapse
Exact same problem for me... someone please help..
I too have been stuck up with the same problem, but in Yu Yureka...Brothers, Don't we really have a solution for this issue?!?!?...Please do something dear nerds lot of thanks!!
same prblm
anyone got solution for this ??
Exact problem.........
I ve gave it micromax service center, they asked 400 and began their work. after some time the man came out and sad, this is a board problem, you have to change the board. My friend is an embedded service engineer. He is saying its just a soft brick and the device is perfectly working. Those knowledgeless idiots dont want to find solution for this, the simply trying to change the board. Friends the problem we have is 100% a software issue, pls dont fall in their trap............
Same issue
Guys anyone got the solution ? Please help ...
Anybody got solutions, please respond
Same here
I tried everything but nothing seems to work. Someone help....
Seems to be Soft-Brick Software issue....
TWRP Recovery is not able to mount the /system , /cache and /data partitions...
but inside TWRP Recovery FileManager , we can open and browse all partiton files and system folders/files in /dev directory....
Also the TWRP Terminal shell can be used to run e2fsck and mke2fs commands...
So I think the /system, /cache and /data , and other corrupted android partitions like /misc can be repaired and mounted again, using the right steps and procedures....
Then I believe TWRP Recovery will mount partitons again and work, and we will be able to install/flash new ROM... Phone will boot into OS again...
We need Somebody with enough technical know-how to run Terminal Shell commands and repair corrupted android partitions.
Please if someone can help, would be greatful...
I used my Yuphoria for 10 months... now lying useless for one year...
---------- Post added at 11:42 AM ---------- Previous post was at 11:05 AM ----------
This XDA-Developers Thread has people trying and finding solutions to our problem.... Some even claim to have found the solution.
[Soft Brick] [Flash Stock] [Recovery] [ADB Driver] Yuphoria [Solution] by EssArr , 119 replies.
https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Will try and find out a method there...
Got solved?
chattboyz said:
I ve gave it micromax service center, they asked 400 and began their work. after some time the man came out and sad, this is a board problem, you have to change the board. My friend is an embedded service engineer. He is saying its just a soft brick and the device is perfectly working. Those knowledgeless idiots dont want to find solution for this, the simply trying to change the board. Friends the problem we have is 100% a software issue, pls dont fall in their trap............
Click to expand...
Click to collapse
So did you get the soultion for it? If yes, what?
The post is of no help
Goodison14 said:
TWRP Recovery is not able to mount the /system , /cache and /data partitions...
but inside TWRP Recovery FileManager , we can open and browse all partiton files and system folders/files in /dev directory....
Also the TWRP Terminal shell can be used to run e2fsck and mke2fs commands...
So I think the /system, /cache and /data , and other corrupted android partitions like /misc can be repaired and mounted again, using the right steps and procedures....
Then I believe TWRP Recovery will mount partitons again and work, and we will be able to install/flash new ROM... Phone will boot into OS again...
We need Somebody with enough technical know-how to run Terminal Shell commands and repair corrupted android partitions.
Please if someone can help, would be greatful...
I used my Yuphoria for 10 months... now lying useless for one year...
---------- Post added at 11:42 AM ---------- Previous post was at 11:05 AM ----------
This XDA-Developers Thread has people trying and finding solutions to our problem.... Some even claim to have found the solution.
[Soft Brick] [Flash Stock] [Recovery] [ADB Driver] Yuphoria [Solution] by EssArr , 119 replies.
https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Will try and find out a method there...
Click to expand...
Click to collapse
This is of no help as partitions are not getting mounted.
stuck at yu logo
i accidentially wiped my yu yurekas internal storage and got stucked at yu logo
i approched about 3 local service centers bt they said
it cannot be repaired because of failed to connect with their software box
and atlast i reched another localservice center come sales shop and they also advoced tge same bt understanding my sady situation the service boy at the shop asked me that "may i check it for further options if you allow to took the device as DEAD CONDITION for servicing bcz it may completely dead after this"
i agreed it
after a day he contacted me and said the problem has fix thank god
now its working fine
if any one want to know more details
such as about service centre
feel free to contact me through
[email protected]
thankyou:good:
Have anyone try to Flash stock rom?
nischait said:
Have anyone try to Flash stock rom?
Click to expand...
Click to collapse
Same problem here !!
Tried to flash the ROM with QFIL but the port is not detected by the software.
Also tried with fastboot.exe method still the same sometimes it says write failed for Size too large of system.img and if I change the default size limit (with -S option) it says "Error : Write failed"
degrader said:
Same problem here !!
Tried to flash the ROM with QFIL but the port is not detected by the software.
Also tried with fastboot.exe method still the same sometimes it says write failed for Size too large of system.img and if I change the default size limit (with -S option) it says "Error : Write failed"
Click to expand...
Click to collapse
Try annabathina method
nischait said:
Try annabathina method
Click to expand...
Click to collapse
Hi, can you share the link please?
degrader said:
Hi, can you share the link please?
Click to expand...
Click to collapse
Your device model please
Device is not getting detected
Hi,
I want to flash my Yuphoria. But, when i connect my device in Fastboot mode, my LAP (Windows 7 32 bit) is showing "Unknown USB". How to solve this issue??? please help me.
shashankdatta1218 said:
Hi,
I want to flash my Yuphoria. But, when i connect my device in Fastboot mode, my LAP (Windows 7 32 bit) is showing "Unknown USB". How to solve this issue??? please help me.
Click to expand...
Click to collapse
Install adb and fastboot drivers first
I was following this tutorial wiki.lineageos.org/devices/walleye/install and I am stuck with sideloading Lineage
I run `adb sideload lineage-17.1-20201013-nightly-walleye-signed.zip` while phone shows "Starting ADB sideload feature" then comes "Installing zip file '/sideload/package.zip'" and then I can see the progress bar below moving, but nothing more, no percentage or more textes or whatever. And it does that now for multiple hours.
Before when I tried it, it stopped completely and the progress bar was frozen.
So I guess something is not working here?! I use Lineage from here, 20201013 download.lineageos.org/walleye
I even cannot push the zip to /sdcard
$ adb push lineage-17.1-20201013-nightly-walleye-signed.zip /sdcard
adb: error: failed to copy 'lineage-17.1-20201013-nightly-walleye-signed.zip' to '/sdcard/lineage-17.1-20201013-nightly-walleye-signed.zip': no response: Success
Click to expand...
Click to collapse
Maybe you can use twrp
armuttaqin said:
Maybe you can use twrp
Click to expand...
Click to collapse
In a way Iam using TWRP, like in the tutorial. So I start the adb sideloading within twrp, how else could i use it? So how can I put the zip onto the phone to use twrp install?
and when I did the format data wipe, I got the errors
failed to mount '/system' (invalid argument)
failed to mount '/vendor' (invalid argument)
Click to expand...
Click to collapse
ok I managed to install from OTG usb I again got the error about /vendor, and also "warning no OS installed" before I rebooted, but then I booted into LOS and it seems to work now....
Hi, just wondering if you have any specifics regarding the steps you followed for OTG USB install? I'm new here and I seem to be having a very similar issue with a newer version of the walleye build