Hi guys, my first post on here so hopefully this is in the correct forum!
Okay, so I've decided to flash a custom ROM (candy5 version 1.5.1) on to my HTC One XL (code name: Evita)
Being new to this, I had to unlock Bootloader on my phone and flash Clockwork Mod. I followed some steps on YouTube and everything was working perfectly up to this point. (One thing that might've been wrong now that I look back was that my Bootloader had ***TAMPERED*** on top of ***UNLOCKED***)
Not knowing that that might have been a problem, I went ahead and installed Candy5 version 1.5.1 (an unofficial build of Cyanogenmod 12) and Google Apps 5.x.x onto my phone. This was when the problems arose with both of them having "installation aborted" messages.
I decided to go on regardless and flashed boot.img from my PC using Command Prompt. It came up with two "OKAY" messages so I thought everything was alright. So then I rebooted my phone, and surprise surprise, it didn't work.
So I decided to do a bit of detective work and because I am a noob at this stuff, I clicked on Factory Reset on Bootloader and I wiped my whole phone.
That deleted my backup on Recovery and I now cannot access any files on my SD card as it comes up with the message "E: can't mount /SD card." I also cannot access my phone to make any phone calls etc. as I only have access Bootloader and Recovery and I cannot connect my phone to my PC.
So as you can see, I am in a bit of strife here and I now have a very expensive paperweight...
Any advice to, first of all, make my phone usable would be much appreciated. Furthermore, any information to make my phone run Andoid Lollipop 5.0.2 using a custom ROM would be awesome too!
Thanks in advance for all your replies!
Related
Hope you all are doing great today.
I am on my 3rd LTE (1st Android phone). The first I rooted using REGAWMOD with no issues. Shortly after I became unable to connect to WiFi. Unrooted it using the RUU and returned it to BestBuy and got another. 2nd one wouldnt connect to WiFi from day 1 so I took it back too. Current phone I attempted to root using REGAWMOD, but it got an error after unlocking the bootloader. I then installed BusyBox and SuperSU w/ no problems. I'm S-On, using TWRP v2.1.8 for recovery, and running Charmeleon 5.0.0.
When I attempt to wipe system from recovery, it looks like it's going to complete the task, but within 5 seconds it stops and says "System Wipe Complete" at the top of the screen. Inside the gray box it says Verifying filesystems...then Verifying partition sizes Running boot script... Then Finished running boot script. Formatting /system then the completed message pops up. I know it should take longer than it does to wipe the system.
To possibly correct this, I'd like to install the newest version of TWRP but I can't figure out how to install a new recovery on a phone that currently has one. I've looked all over the place for an answer but cant seem to find one. I would greatly appreciate it if you guys would give me hand.
I love the phone and love the idea of being able to customize it while increasing performance. It's frustrating that the makers of these phones don't ship them totally optimized. Kind of like Microsoft limiting what we can do with the XBox.
Thank you all very much for any and all help and suggestions
King of the Couch
I've been doing research on this for a while, and I decided to sign up and ask about this question. Majority of the topics here dealing with bricking either have solved it because of access to fastboot, or some users have given up and either retired their devices or sent them in to ASUS.
Long story short, I installed Clockwork Recovery Mod and Cyanogen mod with no issues. After a couple of weeks, I decided I wanted to go back to stock. I did some research and found a topic which said I needed TWRP in order to flash back the stock ROM. I installed TWRP, but some things seemed to have gone awry with that install and I no longer have access to the fastboot menu and the tablet keeps booting straight into recovery.
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2). So far, I think I can get it back on track if I could somehow install a new recovery, or start my device from scratch somehow.
Also whenever I transfer to device memory, if I reboot the tablet, everything gets erased and the log is littered with errors about not being able to find and mount /data. From what I've read, it should be solved with a simple format of the file system. However, all of my attempts to use the recovery's built in wiping/formatting tools have ended with no success. If I put in a microSD, that gets wiped as well so in order to load a ROM, I have to push it using adb.
I thought I had fully bricked it, but it seems that since it's accessible through adb, it's still somewhat fixable. I know about backing up everything with nvflash, now, I guess I just didn't do enough research before getting into this. Any ideas, feedback, is appreciated, so far I'm learning a lot about android devices from this experience.
lino4 said:
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2).
Click to expand...
Click to collapse
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Yeah I found that thread not too long ago, I pushed the bootloader and was able to load the stock rom and get everything going.
(HTC One M8 on Verizon. HTC6525LVW.)
Hi everyone.
Got S-OFF Through the Sunshine method a few days ago.
No matter what custom ROM I installed I wasn't able to boot -- even messing with custom after flashing the lollipop firmware (this thread: ) I finally got my first custom ROM to actually boot last night (ARHD 40.3), only to find the roaming icon in the status bar, with no data after I turned off roaming.
I was worried that, according to one warning elsewhere, I may have corrupted my "NV partition," and that was causing the data problems. However, a quick NANDROID restore of my previous working stock ROM (w/root) booted with full cell service no problem. So that indicates that I don't have a corrupted NV partition.
Am I missing something simple within the ROM? I've rebooted a few times, the SIM gets recognized and I have my correct phone number, and I've tried the typical 2G/3G/4G auto options/selections in the mobile data settings...to no avail.
----
As an aside, everytime I exit/reboot with CWM (using cwm_v6.0.4.8_m8vzw-3.img ), it says "You may lose root. Attempt to regain root? (This process is irreversible...) yes/no. I'm wondering if this matters at all? I have root just fine inside my stock ROM, and full S-OFF, so I don't think it matters but I thought I'd ask just to be sure.
Related note: Is TWRP "better"? I did try to FASTBOOT flash recovery of the latest TWRP (twrp-2.8.5.0-m8_wlv.img) for my phone, but that recovery doesn't boot. (I saw an indication yesterday that I might just need to flash this TWRP recovery from inside a ROM or something...but in any case, the recovery seems to be working fine overall.)
----
My apologies that this isn't in the right thread(s) -- I haven't a lot of time before I go on a trip next week, and figured I would just post to see who could point me in the right direction.
Thanks in advance for all the help!
Everyone around these forums, myself included, seem to be using twrp and you did describe the current version number. I would first recommend figuring out how to get twrp installed. It's weird that you were unsuccessful getting it flashed with fastboot. To make sure, the device was recognized by "fastboot devices" and you typed "fastboot flash recovery <name_of_file>.img" right? You might also try finding a copy of the recovery that has been loaded into a 0p6bimg file that can be flashed automatically in the bootloader. I think captain throwback posted one for a user somewhere in this forum a week or two ago.
Did you flash the latest s-off ruu? You need the latest firmware for most of the current roms. That is likely why none of them boot.
...
Up to speed =)
Thanks to the first two posters! I did get TWRP finally installed (seems more capable than cwm), and did flash the firmware prior to posting the thread, but the ROMs still didn't install or work properly.
After flashing the latest RUU, I flashed SkyDragon, which seems to be working well!
Also have learned a lot more about the entire process...
Thanks again!
There does seem to be a snag with TWRP and the new 5.0 firmware. Seems like you finally got around it. I was newly S-Off and wanted to go from 4..4.4 to 5.0.
I went this route using the top firmware which has TWRP built in:
http://forum.xda-developers.com/showthread.php?t=2723159
Another issue is it must be flashed twice. For me it took three times. I also flashed the new radio although it may have already been in the firmware. The dev that posted the above also wrote your ROM so found a good match.
schneid said:
There does seem to be a snag with TWRP and the new 5.0 firmware. Seems like you finally got around it. I was newly S-Off and wanted to go from 4..4.4 to 5.0.
I went this route using the top firmware which has TWRP built in:
http://forum.xda-developers.com/showthread.php?t=2723159
Another issue is it must be flashed twice. For me it took three times. I also flashed the new radio although it may have already been in the firmware. The dev that posted the above also wrote your ROM so found a good match.
Click to expand...
Click to collapse
What version of twrp did you flash? I haven't had any issues flashing ROM's. Some of them do take a long time to boot at first.
As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?