My current situation:
->twrp installed
->everything formatted!(sdcard,data etc)
->unable to mount /system error in both cwm/twrp
-> No OS installed
->stock partition
->unable to flash any ROM, yes any custom ROM out there(from sideload or from sdcard) with this error "failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system No such file or directory
unmount of /system failed; no such volume"
->Unable to flash MI roms through miflash because of unspecified error (0xffffff01)!
-> hope from you guys.
My mi3 was running on lollipop ivan ROM. everything was ok. I thought lets flash mokee. after flashing mokee and using it for few days(With no gapps, unable to flash) I reverted back to ivan AOSP from my old backup(thank god!).
Crysis started after this point.
I extended the partition from this guid->http://forum.xda-developers.com/xiaomi-mi-3/general/howto-resize-extend-partition-capacity-t3011918
It was successfull. But whenever I tried to flash any rom , it gave me the error mentioned above(failed to mount /dev/block/...)
So I fomatted everything, and reverted the partition changes to stock. But the error was still there, on both cwm/twrp.
So I thought of using miflash method to solve this issue. But miflash is giving unspecified error. Yes, I'm doing everything correctly in miflash method,no space in folder name and etc.But it's giving error.
Now I don't have anything in my phone except twrp. Cant flash AOSP/CM romes because of the error and cannot flash MIUI from meflash. What should I do? Seriously I'm completely broken. Need Help. :crying::crying:
If under warranty take it to the nearest service center. They should fix your phone.
Flash MIUI through recovery method.
dude, flash back to stock partitions and only after u flash that through cwm/twrp (try both if its still not working ) it will work Mi Flash. I experienced the same problem, just kept flashing (cmw/twrp) the stock partition zip and it worked
Guys. I installed mm miui beta. after I want go back miui kk. and I flashed stock partition with cwm. now I cant flash any zip with twrp, cwm or orj miui recovery. I cant flash fastboot rom. I can only flash recovery with fast boot. in twrp menu internal stroge looking 0 mb. SDcard working but recovery cant flash any zip bec. internal stroge looking 0 mb. And I cant flash rom with adb.
mi flash error: 0x80004005:FAILED (remote: partition table doesnt exist ) Im very sad guys. I love my phone pls help me. with out battery cant give me 9008 port. I cant try testpoints.
Sorry for my bad lang. Who can help me?
in my partition table cant see rm 25 and 26
my partition table = i.imgur.com/XxyPuVA.png
I solved my problem with qpst guys. dont need thread thanks. firstly ı removed partition table with adb. after my pc connected with port10. with qpts ı write blocks. and install with mi flash my offical rom
en.miui.com/thread-138246-1-1
use http and html in end and . wherever necessary cant post link
There is a solution to unbrick using miflash here http://en.miui.com/thread-59891-1-1.html
Flash partition first then try I'm even faced the problem
Flash partition first then try I'm even faced the problem after upgrading to mm
Try to flash partition ill post u the link in next reply
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
This guide is for you
What you will need:*
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)*
2. Windows
3. The device defined somehow Device Manager*
4. The latest version of*MiFlash*
5. MIUI firmware developer for fastboot*here
6. Adb and fastboot installer*here
Connect your phone in fastboot mode*
Enter this
Fastboot flash partition gpt_both0.bin
This file is in fastboot rom.*
This will restore stock partitions, then flash all the kitkat rom.
"Fastboot flash partition gpt_both0.bin"
I must note: I use linux. I only used Windows because SPFT Linux version gave me a chip mismatch error I couldn't fix easily.
1: Please read. It explains what problems might arise. Especially post #6 and #13.
2: There are 2 versions of the scatter file. The MT6735 version is what I used successfully. The MT6737Tmod version is what comes from post #6 & #13.
3: Please use each scatter file to Readback your boot and recovery partitions first, renaming as fit, so you can have a backup BEFORE ANYTHING. Then test unpacking them to see if everything went correctly. Then readback every partition in the scatter file so you don't have to depend on the stock ROM for a backup. I didn't and it led me to take this route.
3: Seem to be a difference in the naming of the scatter file and sizes of system, cache, and userdata inside from the stock ROM and what works..
4: DO NOT choose Format+Download until you know which scatter file works, unless you want to chance a Hard Brick.
5: Wiping the dalvik and cache in stock recovery before flashing TWRP seems to be the best thing to do to avoid boot loops or a hung boot.
THIS ROOT PROCESS WAS DONE OVER THREE DAYS OF CAR WORK, DRIVING, FAMILY, AND COMPUTER WORK. MOST OF THE TIME SPENT WAS THIS MORNING TRYING TO GO TO SLEEP. DIDN'T HAVE TIME TO DOCUMENT AND TAKE PICTURES. THIS WRITE-UP IS FROM WHAT I REMEMBER DURING THIS PROCESS. IF I CAN REMEMBER SOME VAGUE DETAIL THAT YOU NEED, GOOD. IF NOT, DON'T STRESS ME. THE HARD PART IS DONE. A GOOGLE SEARCH OF SOME OF THESE PROGRAMS WILL GET QUICKER RESULTS IF YOU DON'T HAVE THEM. THE MAIN THING NEEDED FROM MY RESEARCH WAS THE SCATTER FILE. LINKS FOR SCATTER FILE AND RECOVERY IMAGE ARE BELOW.
Looking for a way to root first day getting this phone in February. Read this post last Tuesday about MT67xx rooting, thanks lsemprini. Spent two days finding which versions of the programs work with this phone, already had the ROMs, drivers, and tools. Dove right in.
I downloaded the ROM from needrom. Scatter file was unusable. Wrong chip error. Phone reads MT6735 scatter file read MT6737. Did a manual diff. Used SP Flash Tool v5.1524 to flash, formatted instead of downloading by mistake, cord got pulled, Hard brick. Fought with Windows7 to get drivers to recognize a hard brick. Still don't know how I did it but it read then flashed. Looked like another hard brick but SPFT would recognize it for the Memory Test. I just held power+vol_down with just charging block power to get it to come on. Sometimes just one of the buttons was enough to get it to power on and start a bootloop. Took two minutes sometimes. Flashing the wrong recovery led to bootloops. Starting SP Flash Tool and plugging in the USB to the phone as soon as it powers off during a loop will let the preloader "register" and the images to be flashed. Flashing from a stock ROM will lead to IMEI being erased. Used SN Write Tool v1.1716 to write the IMEI numbers. Got them from the side of the box. The MD1_DB and AP_DB files needed are in the stock rom.
Ported TWRP, credit to jemmini for the post https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601. Used that recovery as a base. Ported according to the myriad of guides that I have been reading over the past few days. None of them worked as instructed, had to modify trial and error style. Finally got TWRP to read the internal partitions AND remain after a reboot. A lot was going on when I did this. Not sure if I formatted before, I remember flashing a lot of because of something. I mounted the system just in case & flashed SuperSu from chainfire's website, no formatting afterwards. Rebooted and installed SuperUser and BusyBox. I tried adb and fastboot. They work but not for everything. Hooked phone up to computer with debugging enabled.
Code:
adb root
gives a shell, no errors unlike before. Edit: ADB won't let me start as root anymore.
Needed files
Blu Vivo XL2 TWRP 3 Recovery
MT6735 Scatter File
MT6737T Scatter File
BLU Vivo XL2 V0070UU Stock ROM if you don't have a backup of your partition images.
Step 1
Install Minimal ADB and Fastboot and USB VCOM drivers.
Download SP Flash Tool, SN Write Tool, scatter file, and twrp3.0 to a working folder.
Download SuperSu zip & SuperUser apk then put them on your SD Card.
Install SD card into phone.
Step 1.A For Full ROM Flash and IMEI Write
Download Stock ROM and extract to working folder.
Move twrp3.0 to ROM folder.
Step 2
Install SP Flash Tool and SN Write Tool and run.
Step 3 To flash TWRP only
Reboot phone to recovery then wipe cache and dalvik. Can't remember if it is a dalvik option in the stock recovery now.
Power off phone. Make sure it is not plugged up to the computer.
IN SP Flash Tool:
Load scatter file that works from working folder.
Make sure download only is selected in drop down menu.
Check only the recovery partition box and click the name of the recovery file on the same line.
Browse to TWRP recovery image and select.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success.
Step 3.B OPTIONAL
Select format and flash all using stock ROM or images backed up from your phone.
Stock ROM must be extracted and custom recover put into same folder and renamed to "recovery.img" to make
everything automatically load.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success
Step 4 Only needed when formating+downloading ROM
With phone still powered off and unplugged, write IMEI numbers using SN Write Tool.
Step 4.A
Click System Config.
Select IMEI in Write Option Area.
Make sure IMEI Checksum and Dual IMEI are checked.
Load MD1_DB and AP_DB files from ROM folder.
Click Load Modem DB from DUT box.
Click Save.
Step 4.B
Click Start.
Input your IMEI numbers from box.
Click OK. Success
Step 5
Boot to recovery.
Swipe to make permanent.
Wipe dalvik and cache.
Flash SuperSu..
Reboot.
Install SuperUser apk and BusyBox of your choice.
Step 5.A
If SuperUser apk or any app that ask for root permission cannot get it, reboot to recovery.
Mount system partition: Shouldn't matter but it worked for me.
Flash SuperSu zip again.
Reboot.
Install SuperUser apk and BusyBox of your choice.
ENJOY
When i connect the device after clicking download, it says "CHIP TYPE NOT match!"
mind you the device is off, i tried to troubleshoot but still getting the same error.
any help would be appreciated
UPDATE: Im thinking it has to be the scatter file, but im not sure.
UPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
[QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.[/QUOTE]
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.
=smith901;72841007][QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
Click to expand...
Click to collapse
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.[/QUOTE]
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
ANJIII said:
chip type not match. pls help
Click to expand...
Click to collapse
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
ANJIII said:
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
Click to expand...
Click to collapse
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
ANJIII said:
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
Click to expand...
Click to collapse
Good. I had to name it that because of the chip mismatch error. It was from the V7 ROM. The other two are updates. I also messed up big time along the way. My phone always read MT6735 but it does have MT6737T in different files. I always wondered about that. I got it to work without buying another phone.
It seem that the phone boot logo never goes away. What should I do now?
Alexis96312 said:
It seem that the phone boot logo never goes away. What should I do now?
Click to expand...
Click to collapse
Hope you Readback your original recovery and other partitions. I didn't and worked hard to get it back. When I just flashed the recovery and something went wrong, it reverted back to the stock recovery.
Try doing this:
1. Start SPFT with the reçovery you want to flash.
2. Hold down the power button. AS SOON AS IT VIBRATES, PLUG THE USB CORD IN.
3. Hopefully you timed it right and it will flash and boot.
Sometimes it took 15 minutes to get past the boot logo.
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Alexis96312 said:
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Click to expand...
Click to collapse
Try flashing stock ROM, wipe data in stock recovery, then flashing TWRP, wipe dalvik.
If that don't work, wipe data then flash stock ROM with TWRP recovery, wipe dalvik.
The scatter file from the stock ROM gave me problems. Had to modify mine.
Don't forget to restore your IMEI afterwards since you formatted+flashed.
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Alexis96312 said:
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Click to expand...
Click to collapse
The one I attatched on the first post #1 is my modified scatter file. The mods included changing the size to the system, cache, and userdata. Just compared all three. The stock MT6737T scatter file and the V12 ota scatter are the same. The one I changed, MT6735, have the file name, platform name, and partition changes. I don't know why I had to modify it., especially the size parts. It all worked when I did that. I basically gave up on it because of a hard brick. Then I remembered reading MT6735 in some file a few months back while roaming the file system. Made the changes and was back in business. Maybe you need the stock scatter file, here it is.
It's what the end result of this post @ANJIII did minus the size changes..
He just did the name changes and it worked for him. Ya'll seem 180° from where I was.
The second one is from the V12 OTA update. It is very minimal, must be all that is needed for a scatter file. Not really sure tho. Hope it is just scatter file issues.
As long as SPFT is reading your phone, it's still a chance on it all working out. That is how I viewed it.
@andromedaXVIII Don't know if you got it working. This might be a potential solution.
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Alexis96312 said:
Unable to find partition for path '/sdcard'
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
I take it TWRP flashed successfully, it is having a problem reading those four partitons. Possibly encryption is stopping you. Try flashing this in TWRP before anything else to remove the encryption.
I didn't get any errors. I know the userdata partition was different in the scatter files. That could be the reason for /sdcard not being recognized. Must be a difference in the layout of phones, not really sure. My protect_s, protect_f, and nvdata partitions and /sdcard all mount fine, pictures attached. I am able to do a backup in TWRP. I have been playing around with porting different ROMs and came across an issue similar to this. Had to change some lines in updater-script.
I checked fstab.mt6735 file in the stock recovery, the modded twrp3 recovery, and stock boot recovery to make sure I didn't make any typos or leave anything out. They all have the same lines. Had to do this:
Code:
("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system")
in the updater-script I was working on. I got ahead of myself flashing a ROM and was stuck on the 1st logo screen. Held power+vol_down to get it unstuck. Yes I was all calling myself kind of names like I'm sure some people have done following this guide.
Which scatter file you used? Did you do a readback in SPFT with the WORKING scatter file and mount one of those images to check if you can read and write the files. I mounted system.img from the stock ROM to make sure I could read and write the files before I started with flashing. I'm thinking there is are internal differences in the XL2s. You might have to reflash using the stock ROM with TWRP as the recovery with the Format+Download option since you got TWRP installed.
Once I get through playing around with trying to flash this ROM, I will restore and try to find all the partition mappings and update TWRP to work with the format from the updater-script and see if that work. Will let you know what happened.
Alexis96312 said:
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Here is all the information I have pulled so far from the phone. Have a screenshot attached from About device in settings. The attached zip file is all the information I could think to pull using adb . The attached file is my partitionlayout. I just ran cat against every file to see what it would give me and redirected the output. Using adb while the phone is in recovery let me pull and read the files I couldn't while the phone was booted.
@Alexis96312, try to run this command in terminal to get your partition map:
Code:
adb shell "su -c 'ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/'" > someFileName.txt
I have mine listed in the zip file as partitionLayout.txt It will list which names go to what device in /dev and save it in your current directory. The file can be used to get the correct partition layout on your phone. Post the results and I will repack the recovery to see if it will work for you. You can do it also with Carliv Image Kitchen, it has a menu :good:. You will have to modify the fstab files in the ramdisk folder of the extracted image to what the partition map specifies. I went thru all of them to be sure when I first ported TWRP.
@ANJIII is correct about the different versions, nice catch. I forgot about that. I assumed you had the V0070UU version like mine, fault on me for not asking. Mine specifically says BLU_V0070UU_V07_GENERIC 25-11-2016 09:46. I'm thinking the GENERIC part comes from me having to flash the stock ROM. I think it had BLU_V0070UU_V07 with user/keys before I bricked it and had to flash the stock ROM. Got three extra apps that I instantly removed. Seems like the stock ROM function the same as before bricking flashing stock.
ScreenShot
ANJIII said:
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Click to expand...
Click to collapse
Answer in pictures
ADB USB
It seem that the computer can't find it what now
Do I need to install the ADB driver again?
I'm trying to do it on stock recovery
Do I have to do it on TWRP recovery?
Alexis96312 said:
It seem that the computer can't find it what now
Do I need to install the ADB driver again
Click to expand...
Click to collapse
It look like the pid:vid aren't recognized correctly. Usually a reboot will help.
Are you connect using adb while in recovery? If so, see if Windows will install new drivers for you. My Linux box read mine as a Samsung at one point. Try running the ls part of the command in TWRP terminal.
This is where I fought with windows when the cord got pulled during flashing. I never got an error like the 2 at the top, always like the bottom one. I kept adding legacy hardware in device manager until one of them worked. The Linux version of SPFT always give a chip mismatch error. Wish it worked so I won't have to boot to Windows.
I kept doing format+download and and plugging the phone in until Windows recognized it because it was in a bootloop when that happened. You need the preloader to be recognized.
Both stock ROMs are on needrom.com. I downloaded the UU version, the EE version is what you might need. I'll pm you a link to my backups from TWRP to see if they will work for you. Same thing happened to me playing with the new ROM. Restoring my boot and system got it back working.
Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash
cant solve this please help
tried edl recovery flashed well but didnt solve problem
i have unlocked the bootloader and flashed many raw firmware didnt solved problem
flashed twrp sucessfully but cant mount storage intenal storage 0mb and cant swipe anything
get this message everytime in recovery
Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash
please help
I have no idea it helps, I had my phone crash on me and me trying my old-and-tried flashing etc. I did not have such BCB message, but it sounds like there is an issue with the partitions or partitioning.
There are nice YouTube videos at least that show how to flash the stock ROM (not giving link here for advertising etc).
it boils down to (FIRST get your data off the phone as you are going to lose this)
- TWRP being bootable
- in TWRP: factory reset, wipe data
- flash stock ROM twice: to partition A and after reboot to TWRP, to partition B. I do not know why this needs to be done, love to learn it by myself.
- flash without wiping a custom recovery if wanted.
- restore your data
I am just new to this flashing custom roms or firmware and twrp also. And dumb enough to not back it up.
I wanted to install arrow os in my phone. When I was about to wipe data, cache and dalvik, I accidentally checked metadata also and wiped. Then problems created more problems.
problems right now:
I cant put a file in my storage
Internal Storage is just blank on my pc
No OS
TWRP on both slots
please help me i really needed help and knowledge about it
I hope the attachment helps
EDIT--
Solutions to my problems:
WHEN you softbrick your phone and you only have fastboot and nothing else
Thanks to this guy..
SOLUTION: download your original firmware but choose the fastboot one and not recovery after download just unzip. Double click flash_all.bat and its back to square one.
WHEN you dont know how to flash or the file you have is .img
SOLUTION: find a guide in xda because apparently you can install a .img file in "fastbootd" mode
the guides here: https://forum.xda-developers.com/t/...sues-all-without-any-custom-recovery.4337099/
COMMENT: not the usual thats what on top of youtube search.
WHEN you see errors in twrp/orangefox recovery you might get panic and search for solution.
COMMENT: try to find and use a solution that doesnt delete something first. In my experience it got bricked even more.
Thanks to the people who commented back on my post and helping me get to know what to do next.
Try putting the stock ROM on a SD card or usb (if you have a dongle).
georg3_ said:
Try putting the stock ROM on a SD card or usb (if you have a dongle).
Click to expand...
Click to collapse
SD card that you put on beside the sim? if yes
Do I download stock ROM in official website? Cus I dont have 1 right now
then flashing it there by using twrp? is that how its gonna run? because i really dont wanna assume and create another problem
Try flashing this stock ROM (global) from a SD card, in TWRP. It's a recovery package, so you can install it as any zip.
Also, can you boot into fastboot/bootloader from TWRP?
Plus, where did you get the ArrowOS image? There are no builds, official or not.
georg3_ said:
Plus, where did you get the ArrowOS image? There are no builds, official or not.
Click to expand...
Click to collapse
I found it here
It is made my myst33d and it is a beta build
im getting a sd card right now to test it out
And yes I still can go to fastboot/bootloader from twrp
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
Click to expand...
Click to collapse
Is the twrp detecting your sd card？try click on the Install image and change to install zip
can you sideload?
I can now see it, I think I reflashed twrp, now I can, but I cant install because of failed to mount system_root and I have done change file system of data to Ext4. when it resets it comes back to f2fs
edit: change file system of data to Ext4 failed
edit2: thank you guys really for commenting back and helping me
is no verity affecting it? cus I am not able to install it now
you should format data and put the arrow build in it, maybe it will work
J6idot said:
you should format data and put the arrow build in it, maybe it will work
Click to expand...
Click to collapse
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
Click to expand...
Click to collapse
Must change it to zip.
EDIT: Extract the file, there's a zip or img inside.
raikiro1 said:
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
Click to expand...
Click to collapse
Try to sideload it, maybe it'll work.
georg3_ said:
Must change it to zip.
Click to expand...
Click to collapse
Should have said "extract the file, there's a zip or img inside", don't change the file extension.
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
raikiro1 said:
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
Click to expand...
Click to collapse
no problem next time installing, stick to sideloading, less room for error
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
A12 shouldn't be a problem.
Probably you should flash another vbmeta.img.
OR
I don't know if there is an .img twrp around, but if there is you can:
Code:
fastboot boot {recovery.img}
and then [Advanced]>[Install Recovery Ramdisk].
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
what vbmeta are you using?