Related
i'm not really into all of that stuff.. but i just tried and failed miserably, haha.
so this is my problem:
i got a htc one x, rooted it and everything was alright. after that i tried to flash cyanogenmod 10 on it. i followed these stepps in this video: /watch?v=elDvcVot7qo (i would enter the full link.. but i'm not allowed to, because this is my first post here)
so i downloaded the cm10_endeavoru-ota-eng.noeri-007.zip and ripndroidgapps-jb-20120805.zip .. but instead of putting both of them onto my sd card, i put all the datas which were IN the files onto my device. now my handy is stuck on the bootloop and i have no access to my sd card anymore.. i just need the access to fix it, does anyone know a solution for it?
Beeeck said:
i'm not really into all of that stuff.. but i just tried and failed miserably, haha.
so this is my problem:
i got a htc one x, rooted it and everything was alright. after that i tried to flash cyanogenmod 10 on it. i followed these stepps in this video: /watch?v=elDvcVot7qo (i would enter the full link.. but i'm not allowed to, because this is my first post here)
so i downloaded the cm10_endeavoru-ota-eng.noeri-007.zip and ripndroidgapps-jb-20120805.zip .. but instead of putting both of them onto my sd card, i put all the datas which were IN the files onto my device. now my handy is stuck on the bootloop and i have no access to my sd card anymore.. i just need the access to fix it, does someone can help me please?
Click to expand...
Click to collapse
Have you tried just holding volume down as it bootloops to see if it will go into cwm?
McBeaker said:
Have you tried just holding volume down as it bootloops to see if it will go into cwm?
Click to expand...
Click to collapse
that works well, i can get into fastboot and cwm
Beeeck said:
that works well, i can get into fastboot and cwm
Click to expand...
Click to collapse
If you did a backup in cwm you can restore it or try and flash the rom again just make sure you read through the whole process a couple of times, mistakes are very easy to make, also look for threads about the rom you are flashing and try and cross reference the procedure, this sometimes helps ...good luck!
McBeaker said:
If you did a backup in cwm you can restore it or try and flash the rom again just make sure you read through the whole process a couple of times, mistakes are very easy to make, also look for threads about the rom you are flashing and try and cross reference the procedure, this sometimes helps ...good luck!
Click to expand...
Click to collapse
i did not put the zip files onto my sd card.. so i can't flash them again, i also did not make a backup the files which i need to complete it, are not on my sd card. all i need is getting access to my sd card, so that i can put the files on it.
Beeeck said:
i did not put the zip files onto my sd card.. so i can't flash them again, i also did not make a backup the files which i need to complete it, are not on my sd card. all i need is getting access to my sd card, so that i can put the files on it.
Click to expand...
Click to collapse
Plug your phone into you pc, boot into recovery, then in cwm go to "mounts and sorage" - "mount USB storage" and the sd card should pop up on your screen
McBeaker said:
Plug your phone into you pc, boot into recovery, then in cwm go to "mounts and sorage" - "mount USB storage" and the sd card should pop up on your screen
Click to expand...
Click to collapse
i tried it, but it doesn't work.. i get an error:
"clockworkmord recovery v5.8.2.7
E: unable to open ums lunfile (no such file or directory) couldn't open directory."
Beeeck said:
i tried it, but it doesn't work.. i get an error:
"clockworkmord recovery v5.8.2.7
E: unable to open ums lunfile (no such file or directory) couldn't open directory."
Click to expand...
Click to collapse
Damn, sorry to say that's where my knowledge ends, I've never seen that error but I would suggest googling the error and see if you can find anything info on it while you wait on here for more help...
McBeaker said:
Damn, sorry to say that's where my knowledge ends, I've never seen that error but I would suggest googling the error and see if you can find anything info on it while you wait on here for more help...
Click to expand...
Click to collapse
could it work,if i update the cwm to the latest one?
Update to cwm 5.8.4.0 it allows mounting USB storage in recovery
Sent from my HTC One X using xda premium
bogfather said:
Update to cwm 5.8.4.0 it allows mounting USB storage in recovery
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
thank you very much, it worked
Beeeck said:
do i just have to flash the new version, without deleting anything?
Click to expand...
Click to collapse
I think you can flash straight over the top of it
htc one x boot loop
McBeaker said:
Plug your phone into you pc, boot into recovery, then in cwm go to "mounts and sorage" - "mount USB storage" and the sd card should pop up on your screen
Click to expand...
Click to collapse
I've been looking around a lot and I'm seriously to the point where I'm totally confused, I have my friend's HTC ONE X (international one) where we followed Hsasoon2000's tool kit (which also uses htcdev website) to unlock the boot loader and it apparently it did and everything was good but when we tried to install the CM10 rom for jellybean using his toolkit the phone got into this "boot loop" and we can't figure how to fix it.. we can get to the bootloader.. where if we select recovery it takes us to this "team win recovery project" thing and gives us several options but .. we are pretty new to this and we don't want to screw this even more. I got to the USB storage mount and I'm able to get into the files through the computer.. can any of you guys help please?? WOULD GREATLY APPRECIATE IT
You need to flash the boot.img.
BenPope said:
You need to flash the boot.img.
Click to expand...
Click to collapse
I truly appreciate your response .. do you recommend any video we could follow.. like I said we are new to this and learning as we go. THANKS
The command is
fastboot flash boot boot.img
You can search how to get and use fastboot, I have no link. It is requirement for pretty much any ROM, though.
BenPope said:
The command is
fastboot flash boot boot.img
You can search how to get and use fastboot, I have no link. It is requirement for pretty much any ROM, though.
Click to expand...
Click to collapse
I got it working thanks alot for all your help!!!!
what i did
i use CC rom and updated to latest rom, it corrupted sommehow i guess
it was locked into HTC bootloop and i could not reach recovery with volume button.
i did all guides , they did not work for me...
THEN I found http://forum.xda-developers.com/showthread.php?t=1604439
Kit and it alowed me to enter the recovery with a ADB command Problem solved, i installed latest backup and it started again.
SOLVED
I am in a situation sort of like this guy:
http://forum.xda-developers.com/showthread.php?t=1948389
Except my father was trying to fix it and wiped the virtual SD card. Any clues on how to push the zips I need onto it?
It is recognised in fastboot but not adb, so I can flash boot.img. I also have CWM recovery.
I have tried the RUUs but they fail with an unknown error.
I tried manually pushing a system.img from the RUU's rom.zip but it's too large for fastboot (Error 000000006)
In cwm use mount USB storage and connect the hox to the pc.
Now u can copy ur ZIP to the phone.
odd29 said:
In cwm use mount USB storage and connect the hox to the pc.
Now u can copy ur ZIP to the phone.
Click to expand...
Click to collapse
Doesn't work. Gimme a mo and I'll copy the error code.
Something like "E: No umsfile"
dangercrow said:
Doesn't work. Gimme a mo and I'll copy the error code.
Something like "E: No umsfile"
Click to expand...
Click to collapse
Try flashing a different recovery, TWRP should work fine
Michealtbh said:
Try flashing a different recovery, TWRP should work fine
Click to expand...
Click to collapse
The HTC One X isn't on the supported list?
EDIT: Found the recovery file, it's booting up now
Solved, thanks to Michealtbh, TWRP allowed me to mount it to push the files over.
From here it should be a piece of cake xD
Hi guys, I was changing Roms and accidentally hit wipe internal storage in TWRP.
I've tried to flash a Sinless ROM, an insert coin ROM and also looked on htcdev website to get an RUU to try and put it back to stock, yet every time I try and install a zip file through twrp it says "unable to open zip file".
I've also taken a shot at trying to add sideload the rom on there, no progress is made and eventually fails again... I've got no backups saved or anything...
Is there anything else I can try to make my phone work again? I was possibly thinking trying to get my brother to do a backup on his M8, put his SD in my phone, then restore from his back up, will this work?
Is there anything else I can try in the mean time? Really don't know what to do next...
Many thanks in advance guys
Oli
Hi,
In my ignorance, i think the failed flashes could be caused by two things:
1- the recovery you are using is not updated. Try to flash the lastest TWRP recovery or change recovery version.
2- corrupted ROM zips. Maybe there are problems while downloading the ROMS or while you copy them to your external sd card. Try to download them on another computer AND using a different browser. And maybe put the zips on a different SD card if you can. But, MOST IMPORTANT thing, check the MD5 after you've finished to download the zips.
About the nandroid backup... I think it could work BUT be sure that your brother M8 has the same brand, firmware and Android version of your M8 (before you wiped everything).
However, about this last part w8 maybe for somone else more expert the me w
oli3107 said:
Hi guys, I was changing Roms and accidentally hit wipe internal storage in TWRP.
I've tried to flash a Sinless ROM, an insert coin ROM and also looked on htcdev website to get an RUU to try and put it back to stock, yet every time I try and install a zip file through twrp it says "unable to open zip file".
I've also taken a shot at trying to add sideload the rom on there, no progress is made and eventually fails again... I've got no backups saved or anything...
Is there anything else I can try to make my phone work again? I was possibly thinking trying to get my brother to do a backup on his M8, put his SD in my phone, then restore from his back up, will this work?
Is there anything else I can try in the mean time? Really don't know what to do next...
Many thanks in advance guys
Oli
Click to expand...
Click to collapse
Get into fastboot and type in fastboot: fastboot erase cache
Than reflash your recovery with with fastboot: fastboot flash recovery recovery.img
Than make sure that your downloaded zip isn't corrupted by trying to unzip it. If its successful, place the rom into the SD card and insert it into your M8 and flash from there.
Set up everything and voila, all done!
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
OmniSlyfer said:
Hi,
In my ignorance, i think the failed flashes could be caused by two things:
1- the recovery you are using is not updated. Try to flash the lastest TWRP recovery or change recovery version.
2- corrupted ROM zips. Maybe there are problems while downloading the ROMS or while you copy them to your external sd card. Try to download them on another computer AND using a different browser. And maybe put the zips on a different SD card if you can. But, MOST IMPORTANT thing, check the MD5 after you've finished to download the zips.
About the nandroid backup... I think it could work BUT be sure that your brother M8 has the same brand, firmware and Android version of your M8 (before you wiped everything).
However, about this last part w8 maybe for somone else more expert the me w
Click to expand...
Click to collapse
My apologies, didn't notice your reply. If his is s-on, he can try his brother's nandroid and if it fails, nothing will happen so its possible for him to restore his brother's nandroid if they are based on the same firmware
I unlocked my boot loader by htcdev, phone is s-on though.
I've downloaded each file twice, and also downloaded the insertcoin rom on another computer, made no difference. I'm using twrp 2.7.0.2 I believe...
Where would I get a new recovery.img file from? Sorry to sound stupid but I'm not sure and don't wanna mess my phone up more. Also when you download the file do you have to have it in the same directory as adb.exe, so when you run the adb command it will get it from that directory?
Bobbi lim said:
Get into fastboot and type in fastboot: fastboot erase cache
Than reflash your recovery with with fastboot: fastboot flash recovery recovery.img
Than make sure that your downloaded zip isn't corrupted by trying to unzip it. If its successful, place the rom into the SD card and insert it into your M8 and flash from there.
Set up everything and voila, all done!
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
My apologies, didn't notice your reply. If his is s-on, he can try his brother's nandroid and if it fails, nothing will happen so its possible for him to restore his brother's nandroid if they are based on the same firmware
Click to expand...
Click to collapse
Just tried doing this fastboot method, I typed in adb devices to see if the phone was recognised, didn't show up, I typed in fastboot erase cache and it still did so. I then pushed the latest TWRP recovery.img file on to the phone, it's now running the latest version of TWRP, but still won't let me flash anything, still keeps saying unable to open zip...
oli3107 said:
I unlocked my boot loader by htcdev, phone is s-on though.
I've downloaded each file twice, and also downloaded the insertcoin rom on another computer, made no difference. I'm using twrp 2.7.0.2 I believe...
Where would I get a new recovery.img file from? Sorry to sound stupid but I'm not sure and don't wanna mess my phone up more. Also when you download the file do you have to have it in the same directory as adb.exe, so when you run the adb command it will get it from that directory?
Click to expand...
Click to collapse
Have you made sure the insertcoin rom that you have downloaded is compatible with your device? Your device needs to be running the lastest firmware as all the roms are updated to 4.4.4
As for the recivery, the lastest is 2.8.1.0
Here's the link to the recovery: http://forum.xda-developers.com/showthread.php?t=2717932
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
oli3107 said:
I unlocked my boot loader by htcdev, phone is s-on though.
I've downloaded each file twice, and also downloaded the insertcoin rom on another computer, made no difference. I'm using twrp 2.7.0.2 I believe...
Where would I get a new recovery.img file from? Sorry to sound stupid but I'm not sure and don't wanna mess my phone up more. Also when you download the file do you have to have it in the same directory as adb.exe, so when you run the adb command it will get it from that directory?
Click to expand...
Click to collapse
Make sure you have HTC drivers installed. if you don't, download HTC Sync and uninstall HTC Sync leaving the drivers in your computer than type in: adb devices.
Boot into fastboot and flash the recovery: fastboot flash recovery recovery.img ( or you can just directly drag the "recovery.img" into cmd and press enter)
Load the rom into a external SD card and insert the SD card into your device and flash the rom from there
Also, do you check MD5 after downloading the ROM????
My device was running 4.4.4 prior to this happening. I did download the latest recovery and push it to the phone, it did work, but upon trying to flash a new rom, it still says failed.
The phone is being detected in adb, when it's in recovery it says so, sideload it says so, just not fast boot?
Oli
Forgive me for beimg stupid but how do I check the md5?
oli3107 said:
Forgive me for beimg stupid but how do I check the md5?
Click to expand...
Click to collapse
http://www.guidingtech.com/9800/what-is-md5-checksum-how-to-verify-it/
Compare it with the MD5 given in the ROM topic
I had the same problem where I couldn't flash anything and it wouldn't mount my storage. I had to adb flash RUU though that only works for s-off users
So if the md5 was to be fine and matched up, what would you try next?
Thanks
Oli
Try unzipping the .zip file on your pc with 7zip and then re-zipping it and try to flash again. I've also had some .zip files that can't be read and it wouldn't even open on the pc itself(giving errors) until I unzipped it with 7zip and re-zipped it.
BerndM14 said:
Try unzipping the .zip file on your pc with 7zip and then re-zipping it and try to flash again. I've also had some .zip files that can't be read and it wouldn't even open on the pc itself(giving errors) until I unzipped it with 7zip and re-zipped it.
Click to expand...
Click to collapse
Also a fail to unzip will point towards a bad download.
Hi guys.
So I tried a new SD card, matched up the md5s, tried flashing a new recovery.img file (which worked, I'm running the latest twrp now), unzipped and rezipped using 7zip, yet when I try and flash it still fails! I've tried flashing on the phone and sideloading it, both still fail.
Sideload failure says:
"installing '/external_sd/sideload.zip'
checking for md5 file
skipping md5 check:no md5 found" - that's where it gives up...
Phone flash failure says exactly the same except another line after sayi ping "error flashing zip '/external_sd/ROM.zip"
I really don't know what to try anymore... I've tried so much and I just can't see anything working now
Thanks for your help so far guys
Oli
oli3107 said:
Hi guys.
So I tried a new SD card, matched up the md5s, tried flashing a new recovery.img file (which worked, I'm running the latest twrp now), unzipped and rezipped using 7zip, yet when I try and flash it still fails! I've tried flashing on the phone and sideloading it, both still fail.
Sideload failure says:
"installing '/external_sd/sideload.zip'
checking for md5 file
skipping md5 check:no md5 found" - that's where it gives up...
Phone flash failure says exactly the same except another line after sayi ping "error flashing zip '/external_sd/ROM.zip"
I really don't know what to try anymore... I've tried so much and I just can't see anything working now
Thanks for your help so far guys
Oli
Click to expand...
Click to collapse
Did you try flashing from Internal memory instead of sdcard?
No I havent. How can I get the rom to the internal memory mate? the phone has no OS on, so it's stuck in recovery or bootloader, how can I transfer the file to internal rather than the sd card?
Twrp 2.8.1.0 has MTP working.
oli3107 said:
No I havent. How can I get the rom to the internal memory mate? the phone has no OS on, so it's stuck in recovery or bootloader, how can I transfer the file to internal rather than the sd card?
Click to expand...
Click to collapse
Since your device only boots into the bootloader menu, all you'll have to do is highlight the Recovery option using the Volume Down button and select it with the Power button. If you do not see the Recovery option, just select Bootloader with the Power button and it should pop up.
Once in TWRP, tap the Advanced option and select ADB Sideload.
From there, you will be given the option to Wipe Cache and Wipe Dalvik Cache partitions, so go ahead and do so by checking the boxes and Swipe to Start Sideload. After it starts, you will be ready to start your ROM flash.
With your device connected to your computer and your ROM file already on your desktop, you are ready to flash.
Kill ADB using the adb kill-server command, then restart it with adb usb.
Make sure your computer can identify your device with the adb devices command.
Flash your ROM with adb sideload Desktop/ROM.zip (be sure to change "desktop" to "downloads" or where ever your ROM is stored, and change "ROM.zip" to the name of your ROM file).
Sorry mate I didn't understand your previous post but I tried this method already, tried flashing Roms using sideload and they still fail, I've posted the error message in one of my previous posts if that helps?
Oli
Hi guys,
I was using latest version of TWRP + DU. I want to try CM13 ROM I did a backup, make a factory reset and install ROM, but it stucks at the end of the flashing process (more details here with 1 screenshoot: http://forum.xda-developers.com/pix...unofficial-t3393765/post67334545#post67334545 ) and when I try to restore my backup I get this error message "Failed to unmount `/system `(Device or resource busy)" and after that I can´t boot in to ROM.
I think that I have some problem with system partition, I try a lot of things and always there is a problem with /system, what can I do? Can I post some kind of log? What other relevant info/log/details can I provide for you?
Thanks in advance guys.
Istvan_86 said:
Hi guys,
I was using latest version of TWRP + DU. I want to try CM13 ROM I did a backup, make a factory reset and install ROM, but it stucks at the end of the flashing process (more details here with 1 screenshoot: http://forum.xda-developers.com/pix...unofficial-t3393765/post67334545#post67334545 ) and when I try to restore my backup I get this error message "Failed to unmount `/system `(Device or resource busy)" and after that I can´t boot in to ROM.
I think that I have some problem with system partition, I try a lot of things and always there is a problem with /system, what can I do? Can I post some kind of log? What other relevant info/log/details can I provide for you?
Thanks in advance guys.
Click to expand...
Click to collapse
You can try using ADB sideload to install an OTA image (not factory image). However, I think it might wipe your internal. I forget.
YevOmega said:
You can try using ADB sideload to install an OTA image (not factory image). However, I think it might wipe your internal. I forget.
Click to expand...
Click to collapse
Hi,
I´m very busy in the work, sorry for the delay of my answer. Can you give me a bit more information on what you mean?
Thanks in advance.
Istvan_86 said:
Hi,
I´m very busy in the work, sorry for the delay of my answer. Can you give me a bit more information on what you mean?
Thanks in advance.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/ota#fugu
Get the latest Ryu image from the link above, set up adb on your computer. There are guides all over XDA. Boot into TWRP - - > Advanced - - > ADB Sideload, then open terminal, with your pixel C connected to your computer. Run the command adb devices to check that your computer sees it, if it does, then adb sideload filename, where the file is the image you downloaded. Make sure you get the OTA image, not the factory image.
YevOmega said:
https://developers.google.com/android/nexus/ota#fugu
Get the latest Ryu image from the link above, set up adb on your computer. There are guides all over XDA. Boot into TWRP - - > Advanced - - > ADB Sideload, then open terminal, with your pixel C connected to your computer. Run the command adb devices to check that your computer sees it, if it does, then adb sideload filename, where the file is the image you downloaded. Make sure you get the OTA image, not the factory image.
Click to expand...
Click to collapse
Hi again,
I have adb and fastboot minimal package installed this is enough? also I´m downloading the 3 OTA from the link that you provided me but i can´t see what is the latest, they don´t have release date...
I´m afraid of losing my internal storage MTP doesn´t works for me and if I lost my sdcard I can´t transfer again the files for flashing things and try to repair my Pixel.
Thanks again mate.
Istvan_86 said:
Hi again,
I have adb and fastboot minimal package installed this is enough? also I´m downloading the 3 OTA from the link that you provided me but i can´t see what is the latest, they don´t have release date...
I´m afraid of losing my internal storage MTP doesn´t works for me and if I lost my sdcard I can´t transfer again the files for flashing things and try to repair my Pixel.
Thanks again mate.
Click to expand...
Click to collapse
MTP doesn't work in TWRP? That's a TWRP issue. Just try going to adb sideload and doing what I said. Also, I think the latest OTA is the H file.
YevOmega said:
MTP doesn't work in TWRP? That's a TWRP issue. Just try going to adb sideload and doing what I said. Also, I think the latest OTA is the H file.
Click to expand...
Click to collapse
When I run adb devices adb recognices my Pixel C. I´m going to sideload as you said, I post result in few minutes.
Really thanks for all your help.
Sorry I forget to swipe on recovery to start sideload but I get the error message: "CAn´t install this package over newer build - Updater process ended with ERROR: 7
Maybe I should try another package?
Hey YevOmega,
Finally I decide to use Nexus Root Toolkit and my Pixel C is fine again, I think I lost everything except recovery, but who cares?? xD
Now I just need to flash again Dirty Unicorns.
Really thanks for all your help mate.
Istvan_86 said:
Sorry I forget to swipe on recovery to start sideload but I get the error message: "CAn´t install this package over newer build - Updater process ended with ERROR: 7
Maybe I should try another package?
Click to expand...
Click to collapse
Istvan_86 said:
Hey YevOmega,
Finally I decide to use Nexus Root Toolkit and my Pixel C is fine again, I think I lost everything except recovery, but who cares?? xD
Now I just need to flash again Dirty Unicorns.
Really thanks for all your help mate.
Click to expand...
Click to collapse
You should have wiped /system and cache before trying to sideload, and it would have probably worked. Glad you're back in business though.
YevOmega said:
You should have wiped /system and cache before trying to sideload, and it would have probably worked. Glad you're back in business though.
Click to expand...
Click to collapse
Hehe, I take note of your advice for the next time. Now I´m running DU without any kind of problems.
Really thanks again for all your help.
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working
Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!