I flashed the latest version of Xenon HD 11-26 for my D852 and it gave me an error on reboot from TWRP saying that root wasnt there anymore and to reapply root, I said yes and reboot and now I cant get back into TWRP at all.
Im not sure if Im doing the back buttons right, but Im kinda starting to panic and Im not sure what to do since the phone wont boot to an OS now for me to try and use the software to reboot back into recovery.
Any sort of guidance would be extremely appreciated.
Thanks in advance.
I finally got Recovery to go back up, so, Im trying to reflash now.
Sorry for making a panic thread, guys.
Related
Hi all,
I did some things with my phone this afternoon, but now when I try to boot it into recovery mode, it just boots into android.
The problem is, it won't boot into android either. It keeps showing the boot animation..
The recovery I use(d): CWM 5 by MoltenMotherboard
The ROM I use(d): Maclaw AOSP ICS Final 2
What do I have to do? I can still enter downloadmode so it's not hardbricked or something, but I have no idea what to do now.
Can I just flash the stock firmware with Odin?
The recovery I use is ext4 only, so that'd mean that when I'm back at the stock rom I can't use the recovery, right?
Update: At the moment I'm trying to flash this rfs+ext4 recovery via Odin, but it's already at 10 minutes and still no "Finish" message or something.. :/
Update 2: Flashed the stock rom via Odin, but now after it shows the blue glowing Samsung logo, it reboots and does it all over again.. It won't go into recovery either.. Please, can anyone help me!?
Update 3: Finally, after a pretty long time I finally got my phone working again.. I was so stupid to use the wrong combination to open the recovery (I used the CWM combination..) Thanks for "all your help" XD
LOL We were giving yo time to figure this out on your own. Good thing you followed your intuitions
Peteragent5 said:
LOL We were giving yo time to figure this out on your own. Good thing you followed your intuitions
Click to expand...
Click to collapse
Hehe, sorry for posting too quickly, but I haven't had any problems like this before so I was a bit scared and things like that
So I was running the New Rom gohma in the Dev section everything was fine and I flashed a update on my phone so I went to factory reset it to pair it to my phone and boom I got stuck in a boot loop. After my hour of being brain dead and forgetting how to get in the bootloader. Now I have that figured out. I can get it to take different recoveries but when I flash a boot.img and system.img it either gets stuck at the M or it just boots into TWRP (or recovery) . I tried to clean some things to make sure it was a fresh install using -w witch now even if I flash a system or a boot.im TWRP wont mount recovery or back up I must of brooked the partition. So im guessing there is a way to fix this but I feel like im going the opposite direction with a phone I would just go for it till I got it because I feel more complaint that I wont destroy my device. where iam starting to doubt myself of that with the MOTO 360. I decided to put it down for the night to try and get some advise or help from others. I really enjoy learning these stuff and im ok with it for a learning project as long as I can save it at this point. I was also very frustrated so I decided to take a break . ANY HELP ADVISE
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
supy99 said:
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
Click to expand...
Click to collapse
this thread may help
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Don't panic
Grab the latest version of philz touch recovery https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The zips are made to be flashed from a recovery like cwm. Install it using cwm, reboot into recovery and philz should come up. You should be able to proceed with wiping and installing your custom rom at this point.
If the zip doesn't work out for some reason, you could also use Odin to flash a .tar.md5 from that link to update your recovery.
Try this: http://forum.xda-developers.com/showpost.php?p=60162192&postcount=2
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
Bricked my phone ! please help!!!
Hello everyone, I think I messed up my phone pretty bad. So I did everything on this instructions to load twp and everything seemed fine. (https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206)
Was able to get to twp and tried to install Renovate Ice ROM. After the flash was done the phone kept booting into TWP. . didn't know what to do so I did the whole process again thinking i will get my original ROM back. ( i know, stupid mistake ). Once i saw that things weren't going anywhere i decided to flash the Stock ROM back in and try to start over, the flash completed but now i'm stuck on a boot loop, the phone won't turn off and recovery is unacceptable.
I really would appreciate any help and am willing to donate a few bucks if someone is able to get me out of this mess.
thanks!
eborjas09 said:
Bricked my phone ! please help!!!
Hello everyone, I think I messed up my phone pretty bad. So I did everything on this instructions to load twp and everything seemed fine. (https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206)
Was able to get to twp and tried to install Renovate Ice ROM. After the flash was done the phone kept booting into TWP. . didn't know what to do so I did the whole process again thinking i will get my original ROM back. ( i know, stupid mistake ). Once i saw that things weren't going anywhere i decided to flash the Stock ROM back in and try to start over, the flash completed but now i'm stuck on a boot loop, the phone won't turn off and recovery is unacceptable.
I really would appreciate any help and am willing to donate a few bucks if someone is able to get me out of this mess.
thanks!
Click to expand...
Click to collapse
Are you able to get the phone into download mode?