Hello guys my nexus 7 recently went into a bootloop almost exactly similar to the once described in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
This started when I reinstalled KaosDroid v.7.0.0 after I realised that I'd forgotten to flash Google apps. Now when I switch on my nexus all I can see is a bootloop between the Google screen and the CWM initial screen. There is a video in the other thread about what I'm talking about. Now,I have a couple of questions....
Please do refer to the other thread to satisfy any questions you might have and.if not, I'll answer your questions.
1. Is it possible by any means to recover my nexus or at least, break out of the bootloop?
2. If the answer to the above is no, then I'd there any point trying to claim the warranty?
Thanks on advance for trying to help me.
Sent from my GT-S5570 using xda app-developers app
Try stock factory image, it'll reinstall stock recovery, bootloader, system.
I got into bootloops after I tried updating to 4.4 (from 4.3 stock) and I just installed stock factory image and everything works as a charm.
Hmmm. Thank you for your reply.It seems you didn't read the other thread. The problem odds that the fastboot mode it's completely inaccessible. All I want you too answer honestly I'd the second question
Sent from my GT-S5570 using xda app-developers app
Related
Hello everybody.
A few days back I managed to brick my Nexus 4 after using it for 1 day!!!! I realize that this all is a very moronic situation and there isn't a fix for my brick because a used a *Toolkit*. Well, I'm already receiving my replacement and it will be here in an hour.
I know how everyone here feels about Google paying for our mistakes but I'm so lucky they're so kind. The advice that I need is on how to NEVER be in this same position. If I were to have set up fastboot instead of a toolkit would all of this have been avoidable? Btw, CM 10.1 is how I bricked my phone....I never have had any luck with that rom.
Thanks everyone for your advice.
Almost all errors are caused by, you guessed it, users. I am skeptical when people claim the toolkit bricked their phone. Also, if cm 10.1 has been troublesome for you, why keep using it? Its the very definition of insanity: keep doing the same thing over and over and expecting different result.
Sent from my Nexus 4 using xda premium
Sooooo, in your professional opinion....would my brick have been less severe if I used fastboot?
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
blitzzz3434 said:
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
Click to expand...
Click to collapse
Well what happened was when I tried to flash it the first time I got a boot loop. So I restored from a backup. Then I redownloaded and when I was in my custom recovery I did a factory reset, a cache wipe and a factory wipe. Then I installed CM.
No after like 3 minutes of booting, I got to my homescreen. I think what happened was I wanted to get off CM because it wasn't working right so I tried to boot into recovery so I held down power and volume keys. I got a yellow light then a red light and now bootloader. After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
My excuse for all of this stupidity is that it was 6am and I hadn't slept yet. Nothing good happens for me without sleep lol. btw, thats as accurate as I remember.
Alpha-Wat3rloo said:
After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
Click to expand...
Click to collapse
What is smirkit? The only hits I could find on it were for the Kindle Fire. It sounds to me like you flashed a bootloader for another device, that would certainly give you a hard brick.
Sent from my Nexus 4
As I suspected, user error.
Sent from my Nexus 4 using xda premium
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Thank you you've actually helped Mr to figure out why it happened. It was super late/early. Serves me right flashing anything without proper rest.
Sent from my Nexus 4 using xda app-developers app
If you had flashed the wrong bootloader or kernel (one meant for a different device) via fastboot then you would still have a hard brick.
Using fastboot instead of a toolkit does mean you have more control over what your are doing, but you still need to make sure you are still flashing the right things.
Sent from my Nexus 4
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your original post made it sound like you used one of the toolkits made specifically for the Nexus 4 and that is what had bricked your phone. It wasn't till half way down the thread you mention you used a tookit for another device. Toolkits are not free from user error even when you use the correct one as you still have to download the correct files and place them in the correct folders. There have been a lot of newbies bricking phones because they have downloaded the incorrect files and then blame it on the developers and or phone for being defective. So this is why people are skeptical when they read these threads.
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that`s what happens when your SMARTphone is Smarter than you.....
Hello all,
I flashed the hotspot mod, and was sure to use the correct (oxed), but I may have used the mdl or mdc. Would that cause a boot loop? how do i fix it? I do have CWM Recovery, but hadn't made a backup(BIG MISTAKE)!
Thanks,
chris
You're going to have to wipe your phone. Unless you have a ROM zip in your phone and dirty flash. If that doesn't help then you could Odin MDL no data wipe.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
You're going to have to wipe your phone. Unless you have a ROM zip in your phone and dirty flash. If that doesn't help then you could Odin MDL no data wipe.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you so much! What I ended up doing was going into the old device(screen broken without a scratch, no idea how) and backed that up and then restored on this phone. Killed two birds with one stone. Sorry to take up space, I just panicked. Also, would a class 10 sd card be that much better than my class 2 I use currently?
Thank you again.
Please read forum rules before posting
Questions and help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
CJ Banks said:
Thank you so much! What I ended up doing was going into the old device(screen broken without a scratch, no idea how) and backed that up and then restored on this phone. Killed two birds with one stone. Sorry to take up space, I just panicked. Also, would a class 10 sd card be that much better than my class 2 I use currently?
Thank you again.
Click to expand...
Click to collapse
Yes it will be faster.
Sent from my SPH-L720 using xda app-developers app
Hey, I have a similar problem. I just did the wifi tether hotspot Services jar, and services odex file swipe that i found on youtube.
After i did all the steps, I rebooted my phone, and now its stuck on the Sprint logo at startup. I did a factory restore and a wipe cache partition, and still nothing. Im running the stock rom of a recently bought Galaxy S4 on sprint (bought it July1st) and now my phone get past the logo, any help please?
I'm assuming you didn't make a nandroid before flashing ? If not, you will probably have to revert to odining back to stock.
Sent from my SPH-L720 using Tapatalk 4 Beta
u'll have to wipe your phone.
Try flashing a kernel made for your device first.
I've been reading through other threads here on XDA about a common boot loop issue that N900T users are experiencing, but nowhere was it mentioned that the Canadian variant users had a similar problem, but I do.
I was wondering if there were any other SM-N90028 users out there that were stuck in a boot loop?
Here is my situation:
I have a Canadian SM-N900W8 (it is, also a Qualcomm LTE version) and I'm in a boot loop... it all started when I tried to restore a Stock-Rooted Rom with TWRP.
I can't, however get it out, and I've tried all of the versions of TWRP, I've also used odin like 30 times... nothing.
I successfully restored a Rooted stock ROM through TWRP, but it wasn't until I re-installed a factory un-rooted one that things got ugly..
So I was thinking about this and perhaps the cause of this is KNOX... since the first thing I did when I rooted my phone initially was uninstall KNOX and all of its files. I know these didn't carry over when I did a TWRP backup, which is perhaps why my restore of that backup worked the first time. The second time, I just went and downloaded everything stock and used Odin, and that's when the bootloop occurred.
if anyone knows of a way to solve this, I'd be forever grateful!
I really hope I will be able to fix this...
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
force70 said:
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thank you, but I've read them all and most are regarding the n900t, I felt it appropriate to ask about the n900w8 variant.
Also, I know that would have been better, but it's too late for that now. I just thought I'd share my experiences here with this issue so that others will know better.
So I tried a different stock ROM, and with the latest version of Odin, but it still is in a boot loop.
However there is one difference; this time it will boot past the Samsung logo and into android, but then a window will pop up saying "Process system isn't responding" and ask me to wait for it to respond or close it. Regardless of what I select, it will end up rebooting seconds later.
In the very short time that everything stays booted for, I can access the two pull-down menus from the top, but selecting anything will yield me no results.
Perhaps this can tell us more about this issue?
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
force70 said:
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
c_est_la_vie said:
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
Click to expand...
Click to collapse
Check post #350 in this thread and read forward. http://forum.xda-developers.com/showthread.php?t=2467001&page=46
this worked!
Hey guys, I'm not sure if anyone's checked this out yet, but I managed to get myself out of the boot loop!
here is the solution:
http://forum.xda-developers.com/showthread.php?t=2471421
Glad your back up and running!
Sent from my SM-N900W8 using xda premium
Thanks!
Sent from my Nexus 7 using XDA Premium 4 mobile app
I took the 4.4 update and now the device bootloops. It was never rooted and never used much at all. I think no more than ten apps were ever installed on it. It belongs to my mother so I'm not familiar with it. I'm very familiar with android as I've been rooting and installing roms on my devices for over 2 years now but I was hoping I could get a quick solution from someone here so I don't spend my whole day trying to fix it
Thanks in advanced!
imucarmen said:
I took the 4.4 update and now the device bootloops. It was never rooted and never used much at all. I think no more than ten apps were ever installed on it. It belongs to my mother so I'm not familiar with it. I'm very familiar with android as I've been rooting and installing roms on my devices for over 2 years now but I was hoping I could get a quick solution from someone here so I don't spend my whole day trying to fix it
Thanks in advanced!
Click to expand...
Click to collapse
Now you can just flash stock firmware using fastboot.
Download the factory image from Google and flash it using fastboot.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Ben Ling said:
Now you can just flash stock firmware using fastboot.
Download the factory image from Google and flash it using fastboot.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thank you very much! sounds easy enough
I've hit my thanks limit for the day but hit thanks anyway :]
I hate to do this but I'm in a rush here don't shoot me...
I am having a hell of a time trying to get TWRP recovery installed.. I have a AT&T SGH-I337 4.4.2 stock rom (rooted).
Tried every way thru TWRP manager no dice...
What is the trick????
Ok EDIT:
Found out i can't use TWRP on NC1 will look into safestrap. mod you can close this thread or delete.
Thanks
Dude, in the future don't post the same problem in so many place. Oeut makes it very difficult to know if you still have a problem and help you. Just saying
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Dude, in the future don't post the same problem in so many place. Oeut makes it very difficult to know if you still have a problem and help you. Just saying
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm with ya 100% I was just in a huge rush I needed to get this phone fixed fast and get it back to my sister and brother in law. I would have never done it otherwise.
I tried to update all the posts accordingly, I will make sure they are showing that I have solved the issue.
Thanks,