So, I made the mistake of trying to upgrade, but then root my ATV. The upgrade worked, but soooooo slooooowww. So I thought if I could get all these apps I'll never use off to save space but also free up ram I'd be better off. Tried king root, it did root and I had access. But upon first reboot I'm getting boot loop. Downgraded back to kit Kat, still boot loop!
I can't get to recovery to try to install anything else, or clear data or anything else that might need to happen. I have a zip file of all the factory files needed, but I can't install or execute any of them without recovery...
Help, am I screwed?
Also please feel free to move this if needed. This seemed the most appropriate place to ask about this....
Related
Hi,
I know next to nothing about phones (although am OK when it comes to computers). I've an HTC Desire which I've had a couple of months which I've not touched the operating system on. I received an OTA update yesterday which I duely installed. The phone has been unable to boot since.
From reading around I've discovered that there's a recovery mode which installs a file update.zip from the SD card. I'm assuming this is what's corrupted on the phone (as it won't boot by installing this file either).
HTC have been no help, neither have O2 in the UK. They all seem to think wiping the data is the only solution and if I try anything on my own I'm going to invalidate the warranty. I can't see how installed a working official update file will invalidate anything, but I'd just like a copy of the file to try.
Does anyone have any ideas on how to fix the phone without having to do a hard reset?
Thanks.
Before the update were you getting an o2 logo when booting up the phone? If so, download the file at the bottom of this post and then:
1. Turn the phone on holding the back button to get into FASTBOOT
2. Connect phone to the PC
3. Once drivers are installed run the file
It should get you back to stock BUT it will mean losing all data on the phone
File to download:
http://ship.ibeta.org/shipped/Bravo...00.32U_5.09.05.30_2_release_144166_signed.exe
Yes, I still get the O2 logo when I try to boot (it just gets stuck at the logo). The phone is still stock, I've never tried to mess with it before, it's just had an automatic update installed which corrupted it.
Is there any way to get the phone to work WITHOUT losing the data on the phone?
Otherwise I'll try that file (or follow the hard reset instructions).
I'm currently becoming a quick study of all things phone operating systems.
Unfortunately not
EddyOS said:
Unfortunately not
Click to expand...
Click to collapse
Would not an update.zip from another phone be able to fix the problem?
Or is there a way of getting the data off a phone stuck at the boot screen?
I'm beginning to feel that the old expression about microsoft building bridges might be better applied to phones. I can normally fix my computer when things go wrong and not lose the data if I do need to rebuild.
The ONLY way you can get it working is to wipe the cache - which you can't do with a stock ROM. All you can do is either wipe the data as it is or install the RUU
Surely there must be a way to wipe the cache without wiping the data?
Is there a way of getting a working recovery file onto the SD card and getting the phone to boot off that? I'm assuming that won't mean I lose all the data.
As I've already said, there's no way of doing it. You're going to have to lose your data unless you root first, back it up then wipe but to restore you'd have to root again
If there was a way of doing it I think I'd have posted it by now
Hey Guys,
So I am totally stumped at the moment.
I have used the Hasoon2000 HTC all-in-one and performed the following:
Unlocked the bootloader
flashed the recovery
Installed SuperSU
My phone is rooted and all is good but now everytime i try to open an app that has something to do with i think either the gpu or sound it freexes then restarts.
What should i try?? I have tried to flash stock recovery with no success and wiped the cache and tried full factory reset. All results in the same issue. I ahve even tried to remove the SU in the system/xbin and bin folders.
Should i try flashing with a stock rom?
Any help is much appreciated
scycer said:
Hey Guys,
So I am totally stumped at the moment.
I have used the Hasoon2000 HTC all-in-one and performed the following:
Unlocked the bootloader
flashed the recovery
Installed SuperSU
My phone is rooted and all is good but now everytime i try to open an app that has something to do with i think either the gpu or sound it freexes then restarts.
What should i try?? I have tried to flash stock recovery with no success and wiped the cache and tried full factory reset. All results in the same issue. I ahve even tried to remove the SU in the system/xbin and bin folders.
Should i try flashing with a stock rom?
Any help is much appreciated
Click to expand...
Click to collapse
Which apps are doing it, are they stock or 3rd party??
You will find there are still a lot of apps out there that dont work or arent too clever on ICS, so if its from the market id investigate its ics compatability b4 you do anything.
It has happened to me, PROPMODDER, it loads, but as soon as you try to alter something it all goes wrong.
Failing that, try booting into recovery, wipe the cache, dalvik cache, and finally fix permissions, see if that helps any, if it is stock apps causing the problem and you dont want to use 3rd party apps you could also boot into fastboot, open a cmd prompty changing to your ADB directory were fastboot is and try FASTBOOT ERASE CACHE, this can sometimes help with issues.
Good luck with it, i hope you solve it.
Thanks for the suggestion.
I have tried clearing both caches and fixing permission (clockwork recovery) but it has made no difference. it is any app including stock that cause this issue. Seems to be anything related to the GPU or sound (pretty sure sound).
I have the srock RUU, should i lock the boot loader and install the RUU (1.28)??
as a basic test i just tried Youtube and as soon as the video begins to play it freezes for 10 seconds then restarts
Attempted to install orignial RUU but got an image error unpn installation
I checked my phone which matchs the below file, dont know why it thinks its wrong
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
scycer said:
Attempted to install orignial RUU but got an image error unpn installation
I checked my phone which matchs the below file, dont know why it thinks its wrong
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
Click to expand...
Click to collapse
Did you lock your boot loader before flashing the ruu?
Also, did you read some threads around here so you could understand what you are doing to your phone? I'm asking this because the all in one tool is nice, but it's also dangerous when you don't quite understand how it works
Well no i didnt have the bootloader relocked as it wouldnt load the OS back up, it just kept booting to bootloader. Turns out that was a good thing. Ran RUU and now im back to the beggining lol thanks all for your help. I will do some more reading before I root again
Any recommendations? all i want to do is a simple root to connect a ps3 controller lol
http://forum.xda-developers.com/showthread.php?t=1592355
I did a pretty extensive search for a solution to this and was unable to find one.
I flashed JB to my KF using KFU and TWRP and everything went fine. However after flashing and rebooting, the regular Kindle Fire logo comes up and JB starts. I can't get back into TWRP to go back to a stock KF.
I have no experience using adb or even how to set it up and all the previous posts that sorta resembled this problem were confusing and frustrating for me.
Please help a noob...
If the system actually loads select reboot then recovery. Flashing stock wrong will just make the situation worse please provide greater detail. The stock boot ani. Indicates to me that you don't have a bootloader the bootloader allows you to access recovery when the system fails to load. Without it your at a turning point that requires the use of a factory cable to put the bootloader in place so that you can thus enter recovery to restore, wipe or flash a new system. Post 9 you can purchase one from one of our dedicated members http://forum.xda-developers.com/showthread.php?t=1392693. When you have it pm me I would be happy to assist you in recovering your device. If your shell is not missing or corrupt then the cable will not be needed but my guess is that it is.
I can get into and use Jellybean on my Kindle. I have tried to use GooManager to reboot in recovery but it just restarts the kindle and goes right back to the kindle animation and the JB rom animation. When I try to get into flash roms it asks for superuser permission. If I allow it simply returns to the main screen.
There is another option but we will have to get together to get it done. It requires the use of an older version of Smirkit. Just simply install busybox and jrummies root browser, move a folder to your sdcard and run a script walla new bootloader and rewrite your recovery problem solved.
Alright...I already have busybox and root browser installed. What do I to do?
PM sent unread your private messages.
Problem solved thanks to much help from ThePooch! Much Thanks .
You`re welcome.:highfive:
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
So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Did you format you're SD card?
Sent from my SM-N920F using Tapatalk
Lost My Mind said:
So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Click to expand...
Click to collapse
Did you get it working??
Sent from my SM-N920F using Tapatalk
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Lost My Mind said:
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Click to expand...
Click to collapse
Please help! what was your own way and what did you do to get the bootloader unlocked?