Related
I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.
legofan623 said:
I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.
Click to expand...
Click to collapse
Andyt95 said:
Download Magio R4
reboot into recovery, type in cmd
Code:
adb devices
adb shell
mount data
exit
adb push /path/to/magioR4.zip /data/
[I](you should reboot here, in which case you'll
need to type[/I] "mount data" [I]again after adb shell,
but it's not really essential and should work anyway)[/I]
adb shell
mount /data /sdcard [I](creates a virtual sdcard)[/I]
flash your ROM in recovery just like you would normally (select .zip from sdcard) and boot up
run rumrunner, it should work, giving you S-OFF which will let you flash absolutely anything. If it doesn't, let me know and I'll come up with a workaround.
Click to expand...
Click to collapse
should work
Andyt95 said:
should work
Click to expand...
Click to collapse
Well first:
~ # ←[6nmount data
mount data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
But instead I just used a USB OTG and flash drive so no big deal
And then Magio popped up with its installer and I went through that and then hit "reboot" to be greeted with the bootloader, so I hit "reboot" in the bootloader, but it still brings me back to the bootloader immediately after a black screen, so I thought "Oops, needed to flash the boot.img", so boot.img was then flashed. Now the green HTC logo is sitting there and isn't doing anything, probably frozen.
Code:
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
means /data is already mounted
I actually got it up and running from a nandroid restore, I tried it once before but the restore didnt finish so I thought it wouldnt work. Thanks for helping me out anyway though!
Hello Guys,
I am having a serious problem, I can not acces my SDCard with CWM, it keeps saying "Can't mount /sdcard" I really don't know what to do, I installed the Xperience Kernel and now nothing is working.
Adb Sideload is not working too when flashing the stock ROM, it keeps saying: "* failed to write data 'protocol fault (no status)' *"
I really have no idea what to do now.
Thanks
Fliwatt
Fliwatt said:
Hello Guys,
I am having a serious problem, I can not acces my SDCard with CWM, it keeps saying "Can't mount /sdcard" I really don't know what to do, I installed the Xperience Kernel and now nothing is working.
Adb Sideload is not working too when flashing the stock ROM, it keeps saying: "* failed to write data 'protocol fault (no status)' *"
I really have no idea what to do now.
Thanks
Fliwatt
Click to expand...
Click to collapse
Try this -> http://forum.xda-developers.com/showthread.php?t=1011355
Or this -> http://spafdroid.wordpress.com/2014/06/29/adb-sideload-failed-to-write-data-protocol-fault/
Power of google
Thank you, all of these did not work but I fixed it finally by installing a new recovery:
http://forum.xda-developers.com/showthread.php?t=2563599
Not the touch one.
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 !
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
Ok, first off let me say thank you in advance. I had the Oneplus 7t and (Tmo) and played hell with it trying to root until I found that MSMTool and then had a hayday with it. Now I have the 8t, I have been waiting for a working TWRP because I really like TWRP and I really like Magisk. As of yesterday my stock Rom was fully rooted with TWRP, Magisk, and busybox. It had been that way for several days with no glitches or errors, so obviously bootloader unlocked, phone is carrier unlocked and got my oneplus unlock token last tuesday (5 days ago). On my 7t after trying several ROM's I settled on Havoc-OS so with my 8t I was just going to go straight to Havoc-OS even thought I might try messing around with a kernel update at some point in the near future. BUT...... somehow I have angered the Android God's and am being punished. I have been through much frustration in the past with things Android, have always been able to figure it out thanks to XDA, but today I must humble myself, finally make an account and ask for help. To the best of my recollection here is what I have done with the results.
But before that my current state is, I can boot to TWRP recovery, fastboot, bootloader, EDL and all that but I wiped partitions prior to starting the flashing process so right now I can not boot to system.
I started at techsphinx.com/smartphones/install-havoc-os/ It is a very straighforward guide. but gave error 7, which I believe is wring device error so I checked and it's the kebab havoc like it should be (I think, I'll get to that in a moment) so I look it up and everything says to get in to the file and find the update binary and update script and edit the update script, blah blah EXCEPT that in my copy of havoc-os in the called out directory I have different files. Mine are otacert and metadata. two completely different scenarios. otacert is a binary file while metadata when opened with notepad gives this text:
ota-property-files=payload_metadata.bin:1784:116801,payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-required-cache=0
ota-streaming-property-files=payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-type=AB
post-build=OnePlus/havoc_kebab/OnePlus8T:11/RQ3A.210805.001.A1/eng.kshiti.20210826.065117:userdebug/release-keys
post-build-incremental=eng.kshiti.20210826.065117
post-sdk-level=30
post-security-patch-level=2021-08-05
post-timestamp=1629960471
pre-device=OnePlus8T,OnePlus9R
I can't remember when was supposed to be remarked in the updater-script file but there is nothing like that in this file. That is all that is present in this directory, META-INF/com/google/android
Everything I try to push to the device errors out before it completes with a broken pipe error, adb sideload is similar in that it won't finish the transfer to the phone. Now anything I try to do in TWRP gives me error can't mount partition_name. I had a nandroid backup but I can't use it because partitions can't be mounted.
I wondered if it was the tmobile variant thing so I tried the msm tool for switching tmobile to universal edition first but I can't get msm tool to work in my device manager the now soft-bricked device shows up as the QS BULK device which is not the right one so I install the automatic driver installer for the qualcomm usb drivers, no effect so I follow how to install manually and windows will not let me and tells me it's likely that the driver file is corrupt or has been tampered with.
My frustration level right now is just before the part where I take a hammer to the phone and make as many small pieces as I can.
The state of my phone right now is that I can't even get it into edl mode because I can't get it to turn off. reboot to power off, holding volume up and power both leave it to when I push both volumes in the screen comes on and I am in bootloader mode. I am at a complete and utter loss.
I need my phone for work tomorrow
@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.
BillGoss said:
@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.
Click to expand...
Click to collapse
Thank you, I have one issue (at least) that I can't find anything on in your instructions... I have been unable to install the usb drivers, on 2 different laptops one old one new one running windows and one running Linux with Windows in VMWare. same thing both times. I have tried the oneplus exe file, the qualcomm auto-installer andstlil show up as QUSB_BULK_ CID...... When I try to manually install by clicking on let me choose one Windows won't allow it. Windows says the file is possibly corrupted or tampered with. So I am unable to use any of the MSMTool versions I have tried.
Any ideas on that?
Cancel that. Please forgive me if I seem panicky if I can't get my phone working by tomorrow morning there will be hell to pay at work. So in your instructions where you write:
"If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ), extract the files, then install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you extracted the CAB file and selecting that directory."
I downloaded the file (brought back memories from doing my 7t) and extracted it to a folder on my desktop oddly enough without even updating the driver my edl mode device was detected correctly.
Working on the rest I'll get back to you shortly and once again I can't even begin to express my thanks!
@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?
Frustrated_AF said:
@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?
Click to expand...
Click to collapse
Like I said, the Havoc thread instructions relate to the pre-TWRP method. And I've never used that method.
The TWRP instructions say to sideload the rom and installer (TWRP installer zip) because installing the Havoc rom also installs a recovery, thereby replacing TWRP. That's why you need to reinstall TWRP after installing Havoc.
@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!
Frustrated_AF said:
@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!
Click to expand...
Click to collapse
Glad you're ok now. Those error messages are common when installing roms because those partitions (what used to be the system partition and is now a set of virtual partitions inside the physical super (sda15) partition) don't get properly setup until you reboot.
The 8T is a virtual A/B device which makes life more complicated than the old simple partition and straight A/B partition devices.