Related
Hi, I've had lot's of problems with my HTC recently, no adb access etc, device not being recognised and recovery playing up, ie not being able to wipe install roms etc... however I fixed the recovery issue and managed to do a nandroid backup, I put on I think it was 1.5 HTC sense hero rom... and recently realised that i can only flash 1.5 roms, not 2.1 anymore? would any developer know what would of caused this problem? Any 2.1 rom just locks on the Hero logo, and I've left it for over an hour in some cases and nothing happens. Again, I used to be able to put on any custom rom.... I'm all out of ideas.
wipe
did you wipe? what recovery image you using etc etc?
1. post in the correct section.
2. remove the ext4 partition from your sdcard, or change it to ext2 or ext3.
3. get adb logcat, otherwise this is like the question "my car won't run, can anybody tell me why?"
I have wiped numerous times... sorry for the "my car won't run type question etc...." just that I've done my research, gooogled, posted detailed info previously on here and another forum, I even fixed my own problem of the recovery image, without fixing that I would have nothing. But anyway the card is partitioned with swap, ext2, fat32 using the latest Amon_Ra image 1.6? something... i've spent weeks trying to resolve this and learnt a lot along the way.
Obviously not where to find the adb logcat... don't worry I'll google it.
Apologies for posting in the wrong forum, if it can be moved could a mod do so?
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Thanks for your reply, I will approach this method again at some point and give it a try, but I think I read somewhere that I couldn't do it for whatever reason, but I'll look into it again seeing as you've had the same issues. Thanks.
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Actually I believe I didnt attempt this because I was no longer able to get my HTC hero working with ADB, as soon as I plug the device in, it comes up as device unrecognised, so I think goldcard method it out.. :-(
on the risk of offending you again (even though i am trying to help here...): you did not provide really much valid info. for most things you just said "doesn't work". what happens if you start by pushing home+power? saying the recovery doesn't boot up tells what does NOT happen, for a diagnosis we need the info what DOES happen.
anyway, if i get you right your recovery is now working. now repartition your sdcard (ext2 and fat, NO swap), do a full wipe, then install the rom you desire to use, then move the log to sdcard ("other" in recovery). reboot your phone and execute "adb logcat > c:\logcat.txt" on your pc. if it doesn't boot up after five minutes stop logcat with ctrl-c and post the two logfiles (recovery.log and logcat.txt). you need to set up adb, if you have problems with that sort them out, there is no way to get any information about your problem without the log.
oh, and about the goldcard: i don't know too much about goldcard'ing, but i can't see how this should help here. my strongest guess is that the swap partition interferes with the boot process...
No worries no offence taken. Pushing Home+Power works and takes me to recovery. Back+Power takes me to bootloader and USB Bootloader device is recognised, so I am able to get Fastboot.
Just recently installed stock rom, to see if that solved the USB and ROM issues but no such luck, re-rooted, put anom latest recovery back on, and went on to do what you have advised to help.. i've attached only the recovery.log in zip format only, as when doing adb logcat command use mentioned(after installing new rom), all I get is "waiting for devices" whilst the phone is stuck on the Hero logo, I waited about 10 minutes, exited from the adb, and the log file was empty as I guessed. I've tried every possible way that I found on the web to try and get the ADB function working again and I realise this is important to get some info.. but I've ran out of ideas for that.
Maybe the recovery(attached) may show something, all I noticed is that the cache and something else was not wiped for some reason? If you or someone has time, have a look through maybe someone knows what is going on.
Thanks for your help and patience
***SOLVED***
I did attempt two. I was unable to sideload using TWRP because it was unable to mount. I decided to format data again. Then I put my flashdrive into the OTG cable and plugged it into the phone. I flashed CM 10.2 Stable and BOOM it worked. Moral is that if you cant mount, reformat it and try using an OTG cable if you cant sideload. Three days paid off. My phone works again!
-Donald
***SOLVED***
(Below is original question)
First of all, hello everyone. I just made an account and am glad I've done so. Seems like a website that's friendly to a mildly knowledgeable android user (well, im a bit of a noob).
Phone:
HTC ONE m7att, twrp recovery, unlocked bootloader (dont know what version, but latest im assuming b/c i got it off warrantee December) I think it isnt rooted anymore because when i reboot from TWRP, it asks me if I want to install SuperSU.
Description:
I was trying out CWM (latest one) to flash CM 11, and it worked, but I didn't like the look. So I flashed TWRP (latest one) to restore my TWRP CM 10.2 backup. I wanted to wipe 'dalvik cache' 'cache' 'data' and 'system' (advance wipe), but i ended up also wiping internal memory. Oops.
Attempts:
1.) I decided to try this http://forum.xda-developers.com/showthread.php?t=2251800
I ended up stuck where I am suppose to flash the ROM zip. My guess is that I have been flashing the wrong ROM files (I tried flashing a few after failed attempts) I guess the solution to this would be to find the right file, but I cant seem to find it after hours of searching, amongst other methods to add an OS. (Oh and I should note, my bootloader was LOCKED before I tried the RUU) Speaking of which...
2.) I decided to sideload a custom ROM. Ive never done this (First time rooting was late September 2013 with d2att Galaxy s3, which is MUCH easier to work with). I tried mounting it with data and later USB-OTG with little success. When I try to ADB Sideload, it is unable to mount. (Bootloader is UNLOCKED)
Questions:
If i was to do attempt 1, can someone please provide me with the correct link to the correct ROM.zip? Ive tried several download threads for the AT&T HTC One with no success.
If I was to do attempt 2, (which i prefer because I want to run CM 10.2) How do I fix the "unable to mount"? Ive tried reflashing the TWRP recovery through fastboot. And also, bonus points for showing me how to transfer zip with sideloading (bonus because I have found a few videos and threads, but they were not clear)
I have done about 4 to 5 hours of research with no luck. Please dont ridicule me for "not searching the threads," because I am frustrated after doing just that with little luck. I know this should be an easy fix, which adds to the frustration. Please help!! Thanks for reading.
I just looked this over, and my ignorance clearly shows, so please be respectful about that. Guidance is helpful, judgement is not, so dont post what I already know about my semi-lack of knowledge with using Android. Thanks.
UPDATE (Still need help):
Another problem I ran into was that the /sdcard would not mount for any recovery. Im guessing the /sdcard is corrupted. Any help with that would be appreciated. Also, I was able to sideload CM10.2 zip file with CWM on another computer, but when I reboot it, it got stuck in a boot loop.
Its been a whole days worth of trouble. First World Problems huh? Please help ASAP! Thanks again.
Hello community
sorry for bothering, but it's two days I'm stuckl with a problem and... zilch.
last day my phone, an O2 Galaxy Fame, ran out of battery (damn me) and decided finally to enter perpetual bootloop. Sometimes when rebooted took like 2, 3 hours to get out of the loop, today it's already 24 hours and more of bootloop. I can log into the recovery system (CWM, installed today in a desperate try to gain root access).
I would like to perform a reset, but doing so I would lose all the details of the Exchange mail and the wireless setting. that wouldn't normally be a problem, but tomorrow I'll be outside the country for a 3-day meeting and I'd need to read the mail. and configure the phone again, that is; is there a way I can force myself into the phone, gain superuser access and retrieve the files I need? I can read and understand adb shell commands, I'm not completely noob on linux and can follow guides.
There is so much mess in the android rooting - IMHO. at this moment I'm stuck with "adb cannot run as root in production builds" and can't sideload Superuser.apk from the recovery sideload screen.
If you could help me before tomorrow it would be great!
thanks!
Seems like a bit of a tough spot there. So it seems like you won't be able to access root that way due to the kernel blocking it. You'd essentially have to have to split the kernel, then decompile the ramdisk and edit default.prop and change ro.debuggable to 1, then recompile and flash the kernel.
So the phone goes into bootloops whenever it runs out of battery? Seems like kind of a big design flaw or a serious bug. Since you now have CWM, you can try and just see if clearing the cache and dalvik cache + fixing permissions might help. Won't make it any worse and won't wipe any important data. Other than that, maybe see if there is a stock rom that's exactly the same as the version you have and flash it over top of your current set up while wiping the caches. If that doesn't work, then you can try to wipe the caches and /system and reinstall Only do this if you know the rom works or you have a way to reload it completely via the PC - so this is a last resort because without /system, you have nothing to boot to!
I've no way to test this, but with most devices, if you have CWM installed, you can flash the SuperSU zip from Chainfire to root the device ( http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip ), but this will not necessarily allow you to do anything in recovery still if the kernel does not let you mount adb via root without making the other changes.
thanks, I've returned today from the business trip but since there is no IT today, this leaves me some more time to try with what you said - I'll let you know how goes.
Well, SuperSU loaded and for a brief second a "apps are starting" popup came out. Better than nothing!
but I'm stuck into bootloop as well.
My tought is: if I flash the same android version on the phone again, won't this delete the /data folder as well?
...I came up with one thought: there isn't any recovery distribution acting as a full android? can I trick android with Odin installing android on the recovery partition, so that it boots into that, and from that with su powers recover what's left in the "main" area?
I'm thinking it as a hard disk with two main partitions, one with android and one with a recovery system.... tell me if I'm wrong.
no one helping?
at least explining why?
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
What's the radio version that is installed? Should be viewable on the bootloader screen at the top. That will help determine which RUU you need to get back to running again.
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe
If it matches the numbers/letters after the Radio_ part there, then that is the file you need. Let me know, and I can download it for you and extract the rom.zip from the exe and upload that. Then you can use fastboot commands to install it on the phone. If your radio version does not match that, please post and we'll see if there are other options.
I don't believe that flashing another rom would work right now since all the storage and such got wiped, but it might be possible to use adb while in recovery to push a rom to the internal storage and install it and then use fastboot to install the boot.img from the rom in bootloader mode since you are S-On.
es0tericcha0s said:
What's the radio version that is installed? Should be viewable on the bootloader screen at the top. That will help determine which RUU you need to get back to running again.
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe
If it matches the numbers/letters after the Radio_ part there, then that is the file you need. Let me know, and I can download it for you and extract the rom.zip from the exe and upload that. Then you can use fastboot commands to install it on the phone. If your radio version does not match that, please post and we'll see if there are other options.
I don't believe that flashing another rom would work right now since all the storage and such got wiped, but it might be possible to use adb while in recovery to push a rom to the internal storage and install it and then use fastboot to install the boot.img from the rom in bootloader mode since you are S-On.
Click to expand...
Click to collapse
Hey there , i ended up making a 2nd thread, in the HTCONE section.. I am currently trying a fix that someone just posted. http://forum.xda-developers.com/htc...date-issue-t2898480/post55889272#post55889272 I will try your fix next, if this does not work =0) Thanks again !! DEFINETLY APPRECIATE IT !!
IF mod can close this thread to avoid confusion, it would be appreciated.
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
OK, no one is helping....ive tried some things, learned a few but this seems to be over my head....can anyone really help ? I managed to get past the white HTC screen by fastboot flashing a new recovery (philz then dees troy version of twrp)....I got a bootable commotio build....I also flashbooted 2.22.401.5, i thought it had fixed everything but in recovery i am getting the following errors.....
unable to mount /cache
failed to wipe dalvik
did I somehow mess up my partitions ? I need to wipe dalvik cache and cache in order to get a working rom on this damn phone.....
The issue has been fixed....
jxcorex28 said:
The issue has been fixed....
Click to expand...
Click to collapse
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
redpoint73 said:
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
Click to expand...
Click to collapse
Im not exactly sure what went wrong in the first place. I never pulled a logcat (from an app or through adp) since the problem no longer exists it looks like I never will unless I go through another similar thing. I wish I did know because it's killing me to know. I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
I have flashed atleast 500 times over a 8 year period on 4 different android phones, and Ive never once experienced the problem I had 2 days ago. Ive had 2 HTC phones, although, the experience with basebands were similar they were actually very different in every aspect. I had a TMO HTC G1 back in the day ( I had to learn how to do everything back when scripts or programs werent doing the grunt work (root)...
I had a TWRP backup of beanstalk saved (so kiddies, do your backups) that is what saved my ass. I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
I actually had to repartition my computer's hard-drive and reinstall windows 7 home edition, so I had to start over with practically everything...Im not going to use toolkits anymore. As you said earlier, it's just the easy way out. You wont learn anything about how to use ADB or Fastboot (although I applaud the one's who make the scripts or toolkits for those of us on the go).....
P.S.......If I can ever manage to break away from my dueling school schedule and my other priorities in life I plan on learning more about starting from the ground up and building roms, and not just throwing a few things together in the kitchen.....
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
jxcorex28 said:
I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
Click to expand...
Click to collapse
Yeah, I'm going to pull back on my previous statement that "3.28 will likely cause reception issues on AT&T's network" to instead say "may cause issues". And feel free to try it at your own discretion.
Reason being, I've seen maybe 3 reports now of this firmware working ok on AT&T, and no reports to the contrary so far.
Although, when folks tried the 2.22.401 "international" firmware on AT&T, there were several (even numerous reports) of signal issues, even NO SIGNAL. No reports of this so far on 3.28, so I'll be cautiously optimistic for the time being (until I see reports otherwise). Haven't personally tried it, and not sure I will as I don't really have time ATM to mess around with the possibility of signal issues or no signal.
jxcorex28 said:
I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
Click to expand...
Click to collapse
Did you try fastboot erase cache before trying to re-install recovery, or a different recovery? I've seen this simple step alleviate some pretty drastic issues with recovery.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
jxcorex28 said:
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
Click to expand...
Click to collapse
I can't speak personally, I'm not a Linux PC person. But my friends that are, seem to split among various distros: Ubuntu, Kubuntu, and Arch. One friend that is a particular Linux aficionado is on Arch, and said he was very happy with it.
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
jxcorex28 said:
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
Click to expand...
Click to collapse
Id highly rrecommend Linux Mint 17 Qiana MATE Edition .I use it with Windows 7. It is my favorite Linux OS. Not to mention that its perfect for Linux beginners.
That info would of been great a few days ago, but my laptop is screwed up now. Earlier I tried logging on,and couldn't because of some kind of remote error near the password field box on win7 HE...So I tried a system restore,and it failed so I f8 into recovery options and try using HP Recovery..everything went smooth into the first boot. I ended up getting a recovery installation incomplete and a 205 UIA failed 3 times. I believe my laptops recovery partition is corrupt,and I don't have a HP recovery disk, a win7 recovery DVD / Win7 recovery USB stick... I found what I need on HPs website, but its 30 bucks...BestBuy GS wants to charge me $69.99 for a diagnostics test and a retail version of win7 cost like 130
Its a 2011 HP Pavilion G-series laptop with windows 7 Home edition. What makes matters worse is I just partitioned the system a few weeks ago by using the recovery option HP makes for their devices...
Everything was great til about 10pm tonight...FML...now I actually gotta go to school to do my damn school work
jxcorex28 said:
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
Click to expand...
Click to collapse
I had that exact same issue yesterday... Twrp couldn't wipe anything and eventually kept rebooting after 20 or 30 sec in recovery.
I had to download the 1.58 RUU and run that, then flash Twrp back, reroot, then restore one of my backups from earlier in the day.
As far as fw goes, I had updated to 2.22.401.4, had that for a couple days, then updated to the 3.xx fw to install arhd 20.3. I liked it, but decided I love my dirty unicorns rom so decided to go back to the 2.xx fw. I tried to flash renovate 4.5.0, and that's when all the issues in twrp started. From what you're saying, it sounds like the issue could be caused from the fw updates.
How did you end up restoring your backup when they issue happened? I tried to restore mine with fastboot, but it was compressed and I couldn't extract the img files from the win files
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
jxcorex28 said:
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
Click to expand...
Click to collapse
I got it from skulldreamz thread on flashing fw by renaming it and putting it on root of ext SD card
Did you look into the contents of that zip to see if there was a recovery.img or boot.img file ? Those files usually overwrite the custom recovery (ie...TWRP or CWM). There are two ways to correct those red error messages you get in TWRP...
1. by flashing partition-fixer.zip (I have a copy if you need it)
2. By using a terminal emulator,and typing this command...
mke2fs /dev/block/mmcblk0p46
I believe this command is essentially what's included in the flashable partition fixer ( I haven't actually taken a look in that zip,so I could be wrong)...
I haven't had any problems as of late...either I'm starting to get back in the hang of dealing with HTC devices or I'm just lucky...
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
jxcorex28 said:
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
Click to expand...
Click to collapse
With the ones I got from skulldreamz' thread, I believe they were modified bc I didn't have to flash a custom recovery again after I flashed the fw. I never fastboot flashed them, I've always just renamed it 0P6BIMG.zip and put it on the root of the ext SD card
That's probably because skull removes those 2 files before uploading for download. I'm not sure if he does that for every zip....