Database Develop

Unable to acces Recovery / Reboot "loop" Recovery with possible Solution

Hey everybody out there,
I had to following problem.
I used the AIO Tool to unlock bootloader and flashing CWMTouch Recovery.
Then I installed ARHD 10.0 over ADB Sideload and everything went fine.
Now I wanted to upgrade to ARHD 10.2 but everytime when im in Bootloader and want to acces recovery my phone reboots.
I can see for like a half second the startup screen from either CWM or TWRP but they all reboot the phone after a half sec.
I tried like all recovery out there its the same with everyone.
Since ARHD wasnt wiped yet the solution for me was to reboot in ARHD and install RomManager via Market and flash Recovery over RomManger and also reboot into Recovery over RomManager.
Now I can acces again my Recovery
For everyone who might have the same Problem
MiXed

[Q] No OS installed after wiping system and internal storage

So I wanted to do a factory reset while keeping the ROM (Android Revolution). Here's what I did
1. Recovery (TWRP)
2. Wipe, advanced wipe, checked system and internal storage
3. Restarted
before rebooting the system, it says "NO OS INSTALLED"
My question is does transferring Android Revolution back to my phone and installing it again in TWRP solves the issue?
I tried that but the issue now is my pc can't read my htc one and I don't know what to do. Please help.

See my post that's on page 2. I did the exact same thing and have gotten everything back up and running with some help from hayame. These are the steps he suggested and I took;
1 - Find the stock recovery.img for your device (I found mine in the AT&T HTC ONE forum)
2 - Flash the stock recovery.img via fastboot
3 - From the hboot menu, choose factory reset (when I did this it rebooted and froze on the HTC logo screen, so I had to power + vol down to get back into hboot)
4 - Reflash newest TWRP via fastboot
5 - Then adb sideload the rom you want with TWRP (this took the longest since I had to update my android sdk and refresh myself on how to use adb)
Hope this helps.
Oh and never wipe System again....I myself will consider that a lesson re-learned

You only need to do that if your SD card partition won't Mount. Otherwise just side load

[Q]bootloop after succeeded guru reset and ota update

At first, this is my story:
-HTC One was untouched
-flashed cyanogenmod with the installer (after some connection-issues it worked)
-wanted back to stock and used guru reset (flashed with CWM)
-wanted to update immediately up to the latest version of android
-ota update (from Htc) failed to install and the phone was stuck in a bootloop (at this state, the phone was unlocked and s-on)
(-panicked)...
-flashed CWM via fastboot
-tried to copy a rom (viper) with adb but adb could not see my Htc (but fastboot could! )
-tried to flash viper with sideload but t failed every time i tried at the end
-at least i was able flash cyanogenmod (sideload and fastboot)
-made a nandroid backup (that was stored in "mnt/shell/emulated/clockworkmod/backup" (root access to see it)
-backup was 1.2Gb big, wen i had 1,2gb free space, it was 1,6Gb big, when there were 1,6Gb of unwritten storage..
so now my questions
1. Why did my it was stuck in bootloop after i tried to update it?
1.1. How can i go back to stock and do ota updates without getting this ee..nice bootloop?
2. Why could adb not see the Htc while fastboot could?
3. Why was the backup stored in the secure path
4. Is more space required for a backup? (used every single bit of my free space both times)
and at least i saw that i have a unusual(?) folder-structure. it is very
do i have ****ed up my folderstructure with adb/fastboot while i did not understand, what i was doing? (so the backups are in the "wrong" path)
that: what confused me:
system(root){mnt\sdcard\( all mediafolders..)
system(root)\mnt\shell\emulated\0\(all mediafolders...)
(legacy folder was in "system/mount/shell/emulated/0/legacy")
system(root)\storage\emulated\legacy\( all mediafolders..)
system(root)\storage\sdcard\(all mediafolders)
why there are so much ways to get to the "normal mediafolders"?
that there are to, because of the splitted internal sdcard ok but..
Thats it
I am very thankful for any help you can give me.

same
I had a very similar issue in which now I stick to CyanogenMod in search of an answer. I had previously used guru rest and ota worked well even up to 4.4.2 sense 5.5, I tried CyanogenMod once more but still missed a few features from stock, I reused guru reset and all went well till the update which seemed good till it started boot loop. The rest was done in panic tho I managed to get CyanogenMod back that's where I'm at. Please any help would be awesome.

Back to stock and ota updates.
Ok now for you and everyone interested.
For going back to Stock Htc Sense and all this stuff, you have to search for a nandroid Backup for your Htc M7. -look for your CID! (s-off is only required if you have to change your CID because you cant find a nandroid for you)
Than just flash the nandroid. (I dont know if you have to or when you need to wipe cache/dalvik..but I would do so for safety)
Next Step: Flash the stock recovery.
Now you are able to get ota updates from HTC.
With the ota update, your root will be lost, so you have to reroot it everytime you made a ota update.. (maybe there are some ways to protect the root)
Please search about this way of getting back to Stock. I am not a pro!
I am not responsible for your messed up phone..
Have a nice flash, everyone.

schnittlauch said:
1. Why did my it was stuck in bootloop after i tried to update it?
1.1. How can i go back to stock and do ota updates without getting this ee..nice bootloop?
2. Why could adb not see the Htc while fastboot could?
3. Why was the backup stored in the secure path
4. Is more space required for a backup? (used every single bit of my free space both times)
Click to expand...
Click to collapse
Maybe because you did not choose the option in guru reset to flash stock recovery, maybe because the guru reset version doesn't match your firmware version.... hard to say without a fastboot getvar all and a link to the guru reset you tried to use.
going back to stock with a RUU, with a guru reset or with a nandroid + stock recovery like you did
ADB only works from booted OS or from custom recovery, not in bootloader (fastboot usb). In bootloader you can only use fastboot commands.
4 and 5) I don't know much about cwm, I'm using twrp.

[Q] HTC One Freeezes after installing Custom ROM

After Installing custom ROM my HTC One is freeze at Welcome Screen. Touch Screen is not working. Only volume key and power button are working. Any Solution?
I am installing this ROMhttp://forum.xda-developers.com/showthread.php?t=2183023&page=5
This is the process I took:
1. Turn OFF the device
2. Turn ON the device in bootloader mode (hold power + vol down)
3. Enter recovery mode using navigation keys
4. Selected "install zip", then "choose zip from /sdcard"
5. flashed Android Revolution HD ROM
At the end of the AROMA installation there was a message "se_metadata_recursiv: some changes failed" but it allowed me to continue
When finished it said Rom was flashed successfully I rebooted, it went to splash screen and went no further.
I tried re installing the Rom again same result
I completely wiped phone clean, restored to factory default re installed Rom.
sd card wont mount so due to not having removable sd card on this device I cant put any other roms or backup files on phone
I tried reinstalling the ROM without using the touch functionality on AROMA, with no success as well
Phone info is
Recovery Clockwork mod v6.0.4.8
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000

Gabrieelh said:
After Installing custom ROM my HTC One is freeze at Welcome Screen. Touch Screen is not working. Only volume key and power button are working. Any Solution?
I am installing this ROMhttp://forum.xda-developers.com/showthread.php?t=2183023&page=5
This is the process I took:
1. Turn OFF the device
2. Turn ON the device in bootloader mode (hold power + vol down)
3. Enter recovery mode using navigation keys
4. Selected "install zip", then "choose zip from /sdcard"
5. flashed Android Revolution HD ROM
At the end of the AROMA installation there was a message "se_metadata_recursiv: some changes failed" but it allowed me to continue
When finished it said Rom was flashed successfully I rebooted, it went to splash screen and went no further.
I tried re installing the Rom again same result
I completely wiped phone clean, restored to factory default re installed Rom.
sd card wont mount so due to not having removable sd card on this device I cant put any other roms or backup files on phone
I tried reinstalling the ROM without using the touch functionality on AROMA, with no success as well
Phone info is
Recovery Clockwork mod v6.0.4.8
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
Click to expand...
Click to collapse
Do you have a Sprint or Verizon phone? If not, try CWM 6.0.4.3 or TWRP 2.6.3.3 or 2.7.1.2

majmoz said:
Do you have a Sprint or Verizon phone? If not, try CWM 6.0.4.3 or TWRP 2.6.3.3 or2.7.1.2
Click to expand...
Click to collapse
I have the international one, bought from Vodafone Australia.
I changed to the recovery TWRP 2.7.1.2 and now the phone freezes at the splash screen

Gabrieelh said:
I have the international one, bought from Vodafone Australia.
I changed to the recovery TWRP 2.7.1.2 and now the phone freezes at the splash screen
Click to expand...
Click to collapse
Try to get into bootloader/FASTBOOT USB and run the following:
Code:
fastboot erase cache
fastboot reboot
If you have a nandroid backup of your stock rom, you might want to try it.

Also you needed to wipe cache and dalvik cache and data before you installed the Rom. So your device is so fresh and so clean
Sent from my SM-G900I using XDA Free mobile app

Well no arhd wipes cache and dalvik as part of the install script. I would flash twrp 2.6.3.3. It works best with that Rom

Thank you all guys, the phone is back working again.
I changed the TWRP recovery to 2.7.1.1 and did the dalvik/cache wipes and it got back to work. The splash screen took a somewhat long time to finish in the first time, but everything worked.

Whenever you flash a new Rom you should wipe data, cache and dalvik.
Sent from my SM-G900I using XDA Free mobile app

Stock Recovery

Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help

EdrichVerburg said:
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
Click to expand...
Click to collapse
I would suggest that you install the latest twrp with flashify and then update your phone, because the newest twrp has the emui updater already built in, so you don't have to re-flash recoveries all the time.

Thanks Sproker,
One problem though. The lastest twrp does not seem to work because it is EMUI 3.0 and I am on EMUI 2.3?? I recently fixed it finally, but I still want to upgrade to EMUI 3.0... Is it worth it? And if it is, what am I to do?

Download the update.app (B135)
And extract the recovery.img
Now download ADB/Fastboot and the latest driver (HISiute).
Connect your phone with the computer and boot your phone into recovery mode.
Now boot into bootloader mode and search the device with "fastboot devices" if it is correctly connected, it should be displayed.
Now flash (first move the recovery.img into the ADB /Fastboot folder) the recovery.img you extracted before.
"fastboot flash recovery recovery.img"
Now you should have the stock recovery back on your phone.
But if twrp didn't work (erasing cache) the stock will also not work.
Try to erase cache via fastboot. But I don't know the code...