Hello all,
In order to receive the new OTA, I got back to stock, and received it successfully.
Then, I downloaded and flashed TWRP 3.0.2-0-hima, and created a backup. After, I tried installing SuperSU 2.78 and each time got a boot loop. So I booted to recovery, and restored my backup, and tried installing version 2.46 instead. Now my phone is stuck on the white screen.. I can't seem to turn it off, or boot to bootloader. When I try ADB, I get 'insufficient permissions for device'.
Is this it? Is it bricked?
Sorry, probably shouldn't be a Q&A post.. I don;t really know how to change it however.
Well, let the battery drain out, got into the bootloader, and restored the backup.
Now only need to find a way to install SuperSU
Related
So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
EDIT*
I'm trying to do this process in ROM Manager- I also have tried flashing it more than once.
Brazildiogo732 said:
So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
Click to expand...
Click to collapse
If you can boot up normally, load rom manager (download from market), and go to install alternate recovery, and install any alternate recovery. Then when that is complete, go back and install the Clockwork recovery version you want on top of the alternate.
What happens is SOMETIMES recovery will get messed up while installing, and you'll get exactly that, loop at the HTC screen.
If you cannot reflash an old, then the proper recovery through Rom Manager, you can do it via fastboot with your computer and USB, there are a few guides on the developer forum on how to do that. If you need i can try to dig up the fastboot recovery method guide later... but really, if you can boot up, Rom Manager is your best/easiest bet.
Yeah, I'm trying to do it using ROM Manager. and It still doesnt work. Ive rooted- unrooted and did everything, idk what I'm doing wrong. I tried flashing the new recovery like 4 times, it doesn't work for me. Thanks for the reply!
a few weeks ago I wanted to get the 4.4.3 update on my M8 but being rooted and missing apps I couldn't, so I found the developer edition rom and flashed the rom then flashed the firmware.
the thing is I have had root access ever since with out the need to use SuperUser, a little concerned any APK could access the phone and make a Mess I downloaded chainfires SU from google store, it immediately told me I needed to up date the SU binary, I cancelled and backed out but the phone rebooted and factory reset as if it was trying to update the SU via recovery.
eventually the phone rebooted and guess what, I am now missing the same APK files as before.
is it possible that it is the superuser apk causing the loss of the other apks and not the rooting process?
I am now going to have to reflash the ROM when I get home, how ever this morning before work I wanted to flash it, but when I used "FastBoot Boot Trecvoery.img" (touch recovery) the phone just hung and did not boot into recovery, stock recovery, longer shows the usual htc phone and red triangle logo, instead it just shows a white screen with htc written in grey
the phone works fine, but how do I get the ROM to reflash if I cant boot into custom recovery, I do not want to flash custom recovery as I prefer stock everything until my warranty expires.
am I going to have to S-off and start again?
Im on ATT M8, I recently flashed over 3.28.xxx.6.....everything was fine, vanir was running great and I had no problems with recovery.....I wanted to flashed MaximusHD Sense rom, so I downloaded both the OTA manual package and the ROM......When I booted into recovery, i could not wipe anything as I kept getting red error messages within the recovery.....I cant remember exactly what it said. Ive seen this before and all I had to do was reflash a recovery. The thing I had done before was flash a different rom without wiping anything, then bootload boot into recovery where I was able to wipe everything and start over, but after flashing Maximus (aroma)....it went to like 5% I believe and automatically rebooted to where it sits now.....The only two screens that it remains still is the bootloader and the bootscreen right before boot animation, any help would be appreciated. I think Im going to redownload a recovery, rename it 0P6BIMG.zip and bootload flash the recovery since my windows 7 computer is not recognizing my device even after installing moborobo and htc sync manager......
also everytime I try to reboot into recovery, it automatically restarts the phone.....just a tidbit info I forgot to mention
I had the same issue. Grab the partition fixer here somewhere and flash that after you flash your recovery again in bootlloader. For some reason the internal storage gets messed up sometimes and causes this.
Damnit, you are right and I completely forgot...and I changed my dang baseband back to 401.5 and went straight to dees troy version of twrp
Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk
Hello,
today I accidentally tapped on "Update" (to 7.1.1) on my rooted Nexus 5X... Something you usually shouldn't do, but it was 2am and I was tired and.... Doesn't matter. After this my phone rebooted and almost instantly showed the dead android with the message "No command". And now I'm stuck there. After rebooting I still land there.
Since the error message almost instantly appeared and since I still can boot into TWRP (3.0.2-2), I think the update wasn't installed and I hope to find a way to avoid the factory reset of my phone. Do you have some tips or possible solutions what I should do in this case?
Thank you for your help.
Its odd this happened, when rooted and twrp installed. in my experience, the update will just simply fail and it will boot back up.... in your case, it sounds like something flashed but the phone didnt like it.... All I can think of is if you cant get into twrp, boot into fastboot and flash the factory image from google, you will loose all data though.....
EDIT, RE-READ you post, if you CAN get into TWRP, try flashing a backup... you should have a backup I hope, lol... First rule of root and flashing is make a backup asap....LOL
When I rooted my phone I did a backup. But the problem is, it was several months ago. So I tried the only method I could save all my data. It wasn't safe, I knew this, but no risk no fun.
My solution was: Download the ota update from Google and flash it with TWRP... Voila! My phone boots properly with the new update... But this method is like I mentioned before not safe and can probably cause a boot-loop with an overwritten recovery. I had to flash my recovery again, but everything works fine now.