Hello im new
and this is my first post .
So i bought a Htc One mini black 2 days ago .
The phone was great !
I unlocked , added a custum recovery twrp , and rooted the phone the same day
Yesterday i download some roms and flashed them , the phone rebooted to bootloader /hboot and kept just rebooting there .
i then went to recovery and flashed a recovery .
and then it kept rebooting at White screen htc logo
so i went to bootloader an did factory reset
when my phone had went on it booted in bootloader and i went to recovery and seen that suprsu is gone
because trwp was asking to install it ?
I then tryed to restore to factory setting
so i Relocked my phone , then Downloaded the 4,3 Factory Ruu
opend the Ruu and tryed to default my phone but got an Image error 155
Basically i am stuck in endless looping
How can i make my phone work again
Aryan33 said:
Hello im new
and this is my first post .
So i bought a Htc One mini black 2 days ago .
The phone was great !
I unlocked , added a custum recovery twrp , and rooted the phone the same day
Yesterday i download some roms and flashed them , the phone rebooted to bootloader /hboot and kept just rebooting there .
i then went to recovery and flashed a recovery .
and then it kept rebooting at White screen htc logo
so i went to bootloader an did factory reset
when my phone had went on it booted in bootloader and i went to recovery and seen that suprsu is gone
because trwp was asking to install it ?
I then tryed to restore to factory setting
so i Relocked my phone , then Downloaded the 4,3 Factory Ruu
opend the Ruu and tryed to default my phone but got an Image error 155
Basically i am stuck in endless looping
How can i make my phone work again
Click to expand...
Click to collapse
Please provide the following information:
How did you unlock the bootloader? HTCDEV method?
Which ROM did you flash?
Can you still enter TWRP recovery?
How did you relock the bootloader? fastboot oem lock?
Error 155 usually means wrong RUU version.... you definitely have the correct RUU?
ALSO, DO NOT do anything else until you let us know the above information....
nelvinchi said:
Please provide the following information:
How did you unlock the bootloader? HTCDEV method?
Which ROM did you flash?
Can you still enter TWRP recovery?
How did you relock the bootloader? fastboot oem lock?
Error 155 usually means wrong RUU version.... you definitely have the correct RUU?
ALSO, DO NOT do anything else until you let us know the above information....
Click to expand...
Click to collapse
Im sorry i forgot the password en witch e-mail i used to signed up aryan33.
Well the problem was im a newb when it comes to unlocking , custem rom etc ..
I flashed a custom cyanmod and it went ****ed
I was able to enter twrp
I unlocked ,relocked , re-unlocked with htcdev ,fastboot oem lock in cmd
well i found that there problem was that there is no Htc one m4 version-main: 2.12.114.2 t-mobiel RUU
i was unable to adb sideload , or push a diff zip to the phone
so i got a otg adapter and a usb flash drive and mounted it with files then flashed a custom rom that was compatible
and my phone works
Nice! Great work! Enjoy your phone!
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install
total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Thanks!
Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day
Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse
Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app
I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation
Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing
Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...
i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)
As title says... I had unlocked bootloader and flashed TWRP then SuperSU and ROOT was working fine.
- Last OTA I got which was yesterday (as only just got the phone) was XNPH33R.
- I used TWRP to install the update which went fine except I lost ROOT access.
- Went back to TWRP and reinstalled SuperSU which shows as installed on my phone - however no apps that require ROOT can get ROOT access and RootChecker shows that the phone is not rooted.
- Rebooted to System / Tried to Fix Permissions / Tried to reinstall newest SuperSU - nothing works
Does anyone have any suggestions as to how I can regain ROOT or is not possible on XNPH33R?
Further issues I have now got no ADB access in Fastboot no matter what drivers I install... don't know if this is all linked!!!
Jesus christ
Any help appreciated.
Thanks in advance
Too much work if you do a full wipe and re rooted ?
Also try to put zip file with airdroid and flash it in download mode
So I've found out that although adb was telling me that it couldn't recognise any devices in fastboot mode - all the actual commands from the OnePlus One toolbox were actually getting through as I relocked my Bootloader to see what would happen and then tried to Flash Recovery and it told me Bootloader was locked - so that confirmed adb commands were working.
To solve my ROOT problem I did the following:
1) Flashed CM XNPH22R
2) Installed all OTA updates
3) Unlocked Bootloader
4) Installed TWRP - then chose REBOOT TO SYSTEM (this told me I wasn't rooted and then followed prompts)
5) I chose to install SuperSU from Play Store
6) Opened SuperSU and updated binaries
7) Turned off Update CM Recovery in Developer Options
8) Rebooted and installed and ran Root Checker....
9) Success!
Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.
Cholerabob said:
Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.
Click to expand...
Click to collapse
Thanks - wish you told me that earlier!!
I assumed it should be on because it's CM right!!! Doh!
Oh well - this might help someone else...
Hi y'all.
I was on Android 11.
Device rooted and bootloader unlocked.
Update with new features impossible until before yesterday.
Update successfully downloaded and installed.
Android 12 was available for my device.
Root unavailable.
An update on Android 13 was available the next day.
Downloaded and install it without prob.
TWRP and root not available.
Decide to install TWRP with fastboot as usual.
Fastboot flash recovery with TWRP .img.
Nothing happened.
Device don't boot at all.
Orange state your device has been unlocked and can't be trusted your device will boot in 5 seconds and the current image(boot/recovery) have been destroyed and cannot boot appeared.
No way to start the phone.
Np for send boot.img or TWRP but without success.
One hour ago i flashed Orange Fox recovery with success.
Device has been not formated.
Don't wanna lose ALL my data !!!!
I hope no.
Just need to remove this orange this orange state and current image have been destroyed.
All i would is to proper boot normally and retrieve Android 13 rom like before all this mess.
Install root with Magisk 25.2 and retrieve TWRP.
Im completely lost , don't know what happened.
PLEAZ NEED HELP !!!!
99 views and 0 replies...
Thx XDA, it's always a pleasure to ask for help
I dont think there is a way to get your phone to boot again without losing everything.
twrp is not compatible with android 13, try to change recovery again , you can install orangefox recovery https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-01-apr-2023.4391139/
BarOn OF Hell said:
Hi y'all.
I was on Android 11.
Device rooted and bootloader unlocked.
Update with new features impossible until before yesterday.
Update successfully downloaded and installed.
Android 12 was available for my device.
Root unavailable.
An update on Android 13 was available the next day.
Downloaded and install it without prob.
TWRP and root not available.
Decide to install TWRP with fastboot as usual.
Fastboot flash recovery with TWRP .img.
Nothing happened.
Device don't boot at all.
Orange state your device has been unlocked and can't be trusted your device will boot in 5 seconds and the current image(boot/recovery) have been destroyed and cannot boot appeared.
No way to start the phone.
Np for send boot.img or TWRP but without success.
One hour ago i flashed Orange Fox recovery with success.
Device has been not formated.
Don't wanna lose ALL my data !!!!
I hope no.
Just need to remove this orange this orange state and current image have been destroyed.
All i would is to proper boot normally and retrieve Android 13 rom like before all this mess.
Install root with Magisk 25.2 and retrieve TWRP.
Im completely lost , don't know what happened.
PLEAZ NEED HELP !!!!
Click to expand...
Click to collapse
You'll have to factory reset to fix the different systemwide problems you have created, there's no way around it - just bite the bullet.
Once you have things back up and running, flash the correct version of Orangefox for custom recovery not TWRP.
Lastly, use the flashable firmware to get rid of the orange state