Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
lyciansarpedon said:
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
Click to expand...
Click to collapse
Hey,
Not to worry just run this command from fastboot (Power button +vol down while booting-> fastboot) plug your phone in and run
fastboot erase cache
Click to expand...
Click to collapse
and if its not fixed, just flash again. Make a back up next time! BTW if you need adb just get it from HERE (hint clickn 'here') if you need more help PM me, im always available
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Ba7rani said:
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Click to expand...
Click to collapse
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
lyciansarpedon said:
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
Click to expand...
Click to collapse
If you have Titanium backup pro you can restore from nandroid file
Menu > restore from Nandroid ..
* Its not recommended to restore system apps or data by Titanium
Found my mistake:
lyciansarpedon said:
\mnt\shell\emulated\clockworkmod\backup (that's where the CWM ROM manager says that it would have backed up to)
Click to expand...
Click to collapse
Missed that I needed to create that directory, oy. Recovery found it just fine, and restored it just as I left it.
Thanks all!
Related
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
Hello there!
I have an international HTC One with ViperOne 5.5.1.
I recently made my phone S-OFF (it has 1.54).
Now the problem: As soon as I try to flash either a kernel or a bootscreen, the phone reboots. I currently have CWM Touch (just 5 minutes now, I flashed CWMT because TWRP had the same problem). The problem is not in the recovery, since they both don't work. Fastboot works (I could flash a different recovery). It's just that as soon as something tries to flash into /system, the phone reboots itself. I tried pushing the bootscreen via adb, but that gave a 'protocol failure.'
tl;dr: Phone reboots while flashing in both TWRP and CWM Touch, eventually it didn't flash anything at all.
I am beyond reasoning and have no clue on what to do.
R3NC0N said:
Hello there!
I have an international HTC One with ViperOne 5.5.1.
I recently made my phone S-OFF (it has 1.54).
Now the problem: As soon as I try to flash either a kernel or a bootscreen, the phone reboots. I currently have CWM Touch (just 5 minutes now, I flashed CWMT because TWRP had the same problem). The problem is not in the recovery, since they both don't work. Fastboot works (I could flash a different recovery). It's just that as soon as something tries to flash into /system, the phone reboots itself. I tried pushing the bootscreen via adb, but that gave a 'protocol failure.'
tl;dr: Phone reboots while flashing in both TWRP and CWM Touch, eventually it didn't flash anything at all.
I am beyond reasoning and have no clue on what to do.
Click to expand...
Click to collapse
Try this: go back to recovery (TWRP 2.6.3.3. or .4 recommended for 4.4 ROMs at the moment)
dirty-flash the ROM, then while still in recovery (no reboot), flash kernel, etc.
then reboot
Wow, that actually worked. Weird stuff if you ask me.
edit: okay it didn't entirely work. The bootscreen didn't work, but I'll retry that after again rebooting.
edit 2: Weird, the bootscreen just won't work. I guess that's just a problem with the bootscreen then.
R3NC0N said:
Wow, that actually worked. Weird stuff if you ask me.
edit: okay it didn't entirely work. The bootscreen didn't work, but I'll retry that after again rebooting.
edit 2: Weird, the bootscreen just won't work. I guess that's just a problem with the bootscreen then.
Click to expand...
Click to collapse
You sure the "bootscreen" zip is for your ROM? they changed the file-naming in 4.4 or 4.3 (don't remember as i never use them), so double check that part
Yeah, I already fixed it!
Thanks for the help!
[THIS THREAD CAN BE CLOSED]
Hi
i was hoping for a little help the image attached is of a nandroid backup downloaded from here it matches my cid amongst other things how do i flash his to my phone is there a idiot proof way of doing this ?
at the moment i have unlocked bootloader via htcdev & twrp 6.2.33 installed i flashed viper but it said it didnt install properly so now the phone boots goes to lock screen if i try unlock it just goes back to htc splash screen then i press sleep button off then on brings the lock screen back then the same thing happens again then the phone reboots itself this happens continuously.
i can get into fastboot and recovery all i want is the phone working again
Are you sure it's a TWRP backup? Perhaps CWM?
How would i know ?
ive attached the recovery log from the backup
vattmann said:
How would i know ?
ive attached the recovery log from the backup
Click to expand...
Click to collapse
Clockworkmod recovery 6.0.4.4 and the beigining of the log file you posted
vattmann said:
How would i know ?
ive attached the recovery log from the backup
Click to expand...
Click to collapse
Its Clockworkmod recovery 6.0.4.4.
So you need to flash this recovery and try to restore. It should help.
Else if you want a custom rom, boot into recovery, and connect your phone to computer. enable mounting of internal storage. With this you can push a new custom rom (of your choice) onto your internal storage. flash it via recovery.
Hope this helps
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
farahtasnim said:
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
Click to expand...
Click to collapse
please state your current bootloader status. Is it unlocked or still locked?
TechnoSparks said:
please state your current bootloader status. Is it unlocked or still locked?
Click to expand...
Click to collapse
I have unlocked my bootloader. Thank you for replying!
farahtasnim said:
I have unlocked my bootloader. Thank you for replying!
Click to expand...
Click to collapse
Splendid! Knowing that your BL state is unlocked, this will make the whole process A LOT easier!
http://forum.xda-developers.com/xperia-sp/development/ubl-twrp-f2fs-support-xperia-sp-huashan-t3150230
Please go to the above link to get TWRP. Also, please keep in mind that TWRP is now the only still supported recovery around. CWM and PhilZ are both really outdated and no longer maintained due to the introduction of Cyanogen Recovery which is very minimal in features.
Once you get yourself the download, extract the files from the zip and get the twrp.img file. We will need this to flash into the boot partition of Xperia SP, granting you a direct boot into recovery once it is flashed. Please then copy the original zip to your sd card, as we will be flashing the original zip via TWRP later to give you access to TWRP in the future.
Using your preferred tool, flash the twrp.img file into the boot partition.
Connect your Xperia SP via fastboot. Make sure SP is shut down, hold volume up key and connect the SP with your computer.
If you're using a fastboot tool via command prompt, the command would be
fastboot flash boot twrp.img
If you're using flashtool, hit the lightning icon in the toolbar, select fastboot mode. Then select "Select kernel to flash". Make sure the file type is "img" else you won't able to find your TWRP img file. Navigate to mentioned img file and select it.
Afterwards, when flashing complete, you may insert sdcard and start the device. It will boot directly into TWRP as we flashed a recovery to the boot partition.
Clean wipe data, cache, dalvik cache, system. You may leave internal storage.
Flash the ROM zip you acquired (make sure file integrity is checked beforehand!) then the TWRP zip earlier. Flashing the TWRP zip grants you a persisting recovery, as explained in the linked thread.
You may now reboot and enjoy
Hello, I've been trying to bring back to life this old XT1068.
In the past years, I had installed several ROMs until one day the phone stopped working (probably I made some mistakes like flashing something not supposed to be flashed on this device, probably) and since that moment if I turn it on it remains stuck on the boot animation (the coloured google dots moving...).
I tried everything. I have TWRP 3.1 installed, I tried to wipe everything, I tried factory reset, I tried to erase the internal storage, I tried to install new ROM, including a stock ROM and the stock recovery. The result is always the same: no errors at all in TWRP, but it's like nothing changes. It does not boot and if I go to TWRP I can still see files that I put in the phone years ago, after I tried every possible wipe. Imagine that I still see the WhatsApp folder of years ago.
As I already mentioned, I also tried to flash a stock recovery: the process finishes without errors but if I reboot to recovery, I always end up in TWRP.
The only thing I can do is to reboot into recovery or fastboot.
The phone is recognized by the computer ("adb devices" / "fastboot devices").
Does anyone of you guys ever experienced something like this?
Thanks in advance.
I have exactly the same issue. Did you find a solution?
I never got that problem, is pretty strange, i think some zip you flashed before is still installed automatically, for example, there is some option on supersu called survival mode, if you enabled that, i think an supersu uninstaller zip could work, also you can try to install any rom, install supersu and check on supersu settings
---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------
Also probably some partition got damaged or anything, i recommend to flash an stock rom that flashes many things except for nvdata and nvram partitions because it could make you can't get signal if those partitions are from another zone
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
eagledipesh said:
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
Click to expand...
Click to collapse
Hello!
I`ve done the process to install via mfastboot the stock IMG, no errors at all. When the phone reboots it goes into the previous installed rom boot animation and stays there at bootloop.
I even tryed to install an updated TWRP recovery (3.4) via fastboot. Is shows "OK" but when it loads it is still the previous version.
It looks like the phone is "write pretected".
Any further suggestion?
Thanks in advance.
Allisson
Same problem here. I can accces the fastboot menu via "VOLUME DOWN + POWER" but whatever I try, the red error message comes up. I can boot into twrp via USB/PC but i cannot install it. I cannot factory reset.
when I reboot from TWRP I come to lineageOS boot loop.
ANY IDEAS?