I had the PA android build of 4.4 running on my tablet and decided to flash the franco kernel, which put me in a bootloop. I have since then flashed stock back onto the nexus 7 but with no luck at all, it's still in a bootloop. I tried to flash Clockwork mod onto it, but it got stuck on the google logo when i tried to boot into it.
I've been screwing around flashing stock images back onto the device but nothing seems to be working.
I'm not really sure what I'm doing wrong here so any help would be appreciated!
I'm not sure if this is the same issue I had before, but after going back to stock I've always had to do a factory reset (you can do it from stock recovery), otherwise it would lock up at the X screen.
that did the trick. I've never actually needed to do that after flashing back to stock before, but it seems to have done the trick!
Of course I missed something obvious like that though 9.9
Related
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
jay-red said:
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
Click to expand...
Click to collapse
Im stuck in the same boat with my S4
which ODIN version are you using and are you using the links from SAMMOBILE to get the firmware you need ? also what are your methods of procedure and is odin giving out any errors or saying pass and still no boot ?
so much like a handful of other people around here today, I soft bricked my phone yesterday morning with an ATT OTA update.
I have managed to get CWM 6.0.4.7 working, and I have tried multiple ROMS, but I can not get anything to boot past the splash screen.
please, I know I must be missing some simple thing, but I can not find out what I am doing wrong despite digging through threads all day here.
I have reset caches, data, etc, dalvik, all the recommended steps...
nothing seems to be able to boot, but I feel like I am soooo close.
thanks in advance
solution - revert, reset, reinstall
this softbrick with no potential for rollback was solved with a combination of techniques.
firstly, I used zadig and heimdall to flash a cm11 recovery into the phone.....
then, I used that recovery to install roms....
they were all locking up on boot.
I reverted back to a stock recovery for the phone 4.3 ish
then did the zadig / heimdall recovery again, installed the latest nightly of CM, and it booted!
flashed carbon kitkat, with the proper gapps, and back in action...only took a whole day!
For some reason my phone isn't booting up all the way to the rom/OS. It gets stuck on the boot animation and goes on forever and hasn't been able to boot up since yesterday, when my powered off at 20% battery, which is something normal for my phone. I was rooted and on android 4.3/MK4, but when I put it to charge and tried booting it back up, the phone would boot up, but would get stuck on the boot animation, going on forever. It wouldn't freeze it would just continue to play the animation. I tried removing the battery, factory wiping it, and installing a new rom, which I found out was for a different baseband. When i finished installing it it still wouldn't boot up all the way through.:crying: I then tried installing the previous rom, and still no good. After all that I installed a stock firmware using odin, hoping it would work. I installed the 4.4.2 NE2 firmware, which isn't for my phone but watching zedomax's video, he said to download the latest build date, which is what I did. Well, downloaded it and flashed it through Odin with a PASS and everything going good. Although, when it was rebooting-even after a factory and cache wipe-it still wouldn't boot up. I tried installing other firmwares aswell, but still no luck. I'm just waiting for it to finally boot up, so if anyone can help me out, I WOULD GREATLY APPRECIATE IT, otherwise, anything is going to help at this point. Since I flashed the firmware, I now have a stock recovery and rom(I hope). I've been through these types of situations, but not to this point.. :crying:
It seems odds, but you may want to try a new battery. I recently went through a total disaster with my device and it ultimately was the battery. You may want to try booting with it connected to the a/c wall charger. It may give you an indication.
Have you tried the quick fix posted? My phone did the same thing when i had the stock recovery it showed error mounting efs folder. I noticed after installing clockwork that error didnt show up. It was still the same problem though. Wouldnt hurt to check it out. I got my note two from a friend who described the issue starting the same way you said happend to yours. The phone had never been rooted though. Good luck to you in trying to fix it.
Sent from my SM-T217S using XDA Free mobile app
So i got a deal on a nexus 9, and no longer need my 7. I decided to give it to my dad and wanted to give him a clean experience. I had been using dirty unicorns 5.0. So I grabbed the stock image off googles site and tried installing it with their directions but didnt work. I tried deleting everything with twrp except usb/otg in custom wiping options, then again following stock install technique, and that didnt work. now when the tablet boots up it gets stuck into a bootloop trying to load up twrp from powering on. Any ideas? Never tried to flash a device stock before.
Not really sure what the heck is going on. I decided to roll back to 7.1.2 so i could get back button kill again (dont judge me lol).
Rolled it back, no problem. saved a backup in twrp of stock 7.1.2. Then tried to install pure nexus rom, EX kernel, vendor image. But it bootlooped and i got stuck on the white google splash screen.
Then it all went to hell and i cant figure out what the problem is. Tried flashing the rom again, but then twrp said No OS. So i went back and tried to flash the factory 7.1.2 image again, but I couldnt get that to work. Got error 'createprocess failed'.
Then i dont know what i did, but I got twrp to work again, so i tired flashing the rom again (this time no kernel). and bootlooped again. So i went back to twrp and now im back to an encrypted twrp. So im out of ideas at this point.
If you can get to bootloader mode, you can flash a factory image from here https://developers.google.com/android/images. never flash backup of factory images through twrp, it's a little fiddly. Also when flashing a factory image find flash-all.bat and edit it, just find -w and delete it.
If you can't then it's bricked. I had the same problem and flashing the factory image fixed it.
cnoevl21 said:
Not really sure what the heck is going on. I decided to roll back to 7.1.2 so i could get back button kill again (dont judge me lol).
Rolled it back, no problem. saved a backup in twrp of stock 7.1.2. Then tried to install pure nexus rom, EX kernel, vendor image. But it bootlooped and i got stuck on the white google splash screen.
Then it all went to hell and i cant figure out what the problem is. Tried flashing the rom again, but then twrp said No OS. So i went back and tried to flash the factory 7.1.2 image again, but I couldnt get that to work. Got error 'createprocess failed'.
Then i dont know what i did, but I got twrp to work again, so i tired flashing the rom again (this time no kernel). and bootlooped again. So i went back to twrp and now im back to an encrypted twrp. So im out of ideas at this point.
Click to expand...
Click to collapse
I thought Google made it to where we couldn't go backwards anymore but to do it right you have to do a factory reset a stock Google one if you still can do it.
mac796 said:
I thought Google made it to where we couldn't go backwards anymore but to do it right you have to do a factory reset a stock Google one if you still can do it.
Click to expand...
Click to collapse
After hour and hours I finally have 7.1.2 loaded on my pixel. i was able to do it using platform-tools. So rolling back is still possible. Now I just have to figure out how to get custom rom and possibly xposed loaded without jacking it up again.
cnoevl21 said:
After hour and hours I finally have 7.1.2 loaded on my pixel. i was able to do it using platform-tools. So rolling back is still possible. Now I just have to figure out how to get custom rom and possibly xposed loaded without jacking it up again.
Click to expand...
Click to collapse
I remember last time I did it all I had to do was Flash the factory image with the w
cnoevl21 said:
After hour and hours I finally have 7.1.2 loaded on my pixel. i was able to do it using platform-tools. So rolling back is still possible. Now I just have to figure out how to get custom rom and possibly xposed loaded without jacking it up again.
Click to expand...
Click to collapse
Flashing custom ROMs on pixel devices is tricky. If you don't do everything in the EXACT order you're suppose to (usually specified in the OP of the custom ROM thread) it'll usually end up badly.
I've had this phone for over a year and just last week was the first time I successfully flashed a custom ROM, firehound on 8.1. I would make sure you're using the latest TWRP as well.