Related
Well i messed up oin this one, i tried to put a new lockscreen onto my EVO and deleted the .apk, and now im in a bootloop can anyone help me get out of this? is my phone screwed, and if i unroot can i still take it to sprint so they can fix it?
Mr_Smiley227 said:
Well i messed up oin this one, i tried to put a new lockscreen onto my EVO and deleted the .apk, and now im in a bootloop can anyone help me get out of this? is my phone screwed, and if i unroot can i still take it to sprint so they can fix it?
Click to expand...
Click to collapse
Flash the same ROM you were using. It should restore things. If that does not work, then just do a full wipe.
I already attempted to do a full wipe, and i was on the 2.3.3 stock ROM still. Maybe im missing how to do the full wipe, i am quite new to this, but dont you go into recovery mod and wipe everything through there because that sent me into boot loop again
Mr_Smiley227 said:
I already attempted to do a full wipe, and i was on the 2.3.3 stock ROM still. Maybe im missing how to do the full wipe, i am quite new to this, but dont you go into recovery mod and wipe everything through there because that sent me into boot loop again
Click to expand...
Click to collapse
Yes you wipe partitions in Recovery. Once you do that all you have to do is reflash the ROM.
This link will take you to the latest EVO Stock ROMs available:
http://forum.xda-developers.com/showthread.php?t=1455340
I would pick the ODEX option.
PM me if I could be of more help.
Good Luck
If reflashing your ROM doesnt work then you most likely did something else that you didnt realize.
Well i wiped bloody everything haha. Trying ROM flash now, would it be ok if i tried to flash an entirely new ROM?
Yeah flash a brand new ROM and see if that fixes the problem. If it doesnt then you may have screwed something else up. Or there is some kind of hardware malfunction going on with your motherboard.
Once wiped, flash a ROM. You must wipe before flashing a ROM. Wipe system, cache, dalvik cache, data before flashing. I think one other but I forget
Sent from my PC36100 using xda premium
reflashing a new rom ,maybe can solve the problem^
Gee, I'm going crazy! Yesterday, I tried CM7(FXP117 and Nightly), and after I restored apps and set up everything, I rebooted the phone, then it stucked after boot animation, black screen.
Now I installed SE.Tweaked(Gingerbread), and it's doing the same!
What to do? Tried wiping cache, dalvik and data, but still not working! I have also tried different kernels!
Thanks for help!
Which kernel do you use?
Crenshaw-PCGH said:
Which kernel do you use?
Click to expand...
Click to collapse
Tried a bunch of them. Including various builds of DoomKernel.
Did you tried to flash the stock rom again?
Crenshaw-PCGH said:
Did you tried to flash the stock rom again?
Click to expand...
Click to collapse
Yeah, tried everything(kernel reflash, wiping etc.)
Try flashing a stock gb firmware with flashtool then use cwm.
sinksterĀ©
Using CWM select, format /system
Thank flash a new fresh rom, with correct kernel.
I installed the 01-29 Nightly & 12-12 Gapps on my shiny brand new 7105 and now it won't boot. I've searched till to I'm blue in the face and I'm about to have a breakdown. I can find stock roms & etc for the 7100 but not the 7105. Someone please point me to a stock Odin Rom so I restore this thing.
Here you are:
http://www.sammobile.com/firmware/?page=8&view=11110
Corey
Sent from my GT-N7100
If I helped you, please hit Thanks..
fishingfon said:
Here you are:
http://www.sammobile.com/firmware/?page=8&view=11110
Corey
Sent from my GT-N7100
If I helped you, please hit Thanks..
Click to expand...
Click to collapse
Thanks downloading it now.
I finally got this installed through Odin, but it now hangs up on the Samsung logo. What can I do now?
sholsten said:
I finally got this installed through Odin, but it now hangs up on the Samsung logo. What can I do now?
Click to expand...
Click to collapse
Hi,
Try this:
Turn your phone off
Boot your phone in to recovery (hold home + volume up + power)
Do a factory reset
Wipe cache ect
Then reflash the ROM with Odin
Then leave it for at least 10 min to boot. As it can take a while.
Let me know how it goes.
Cheers
Corey
Sent from my GT-N7100
If I helped you, please hit Thanks..
I did the factory reset & wiped the cache as you suggested. It rebooted before I get it turned off and I let it go. It booted on up and I'm good to go again. You helped me get my new phone back and I appreciate it. I don't know if I'll try anymore custom rom's or not on this 7105.
sholsten said:
I did the factory reset & wiped the cache as you suggested. It rebooted before I get it turned off and I let it go. It booted on up and I'm good to go again. You helped me get my new phone back and I appreciate it. I don't know if I'll try anymore custom rom's or not on this 7105.
Click to expand...
Click to collapse
Completely up to you, mate. You just have to be very cautious when flashing things on your phone. You have to be very particular with the files you're downloading. Just ensure that everything's for your N7105. ^^
sholsten said:
I did the factory reset & wiped the cache as you suggested. It rebooted before I get it turned off and I let it go. It booted on up and I'm good to go again. You helped me get my new phone back and I appreciate it. I don't know if I'll try anymore custom rom's or not on this 7105.
Click to expand...
Click to collapse
Hi,
Glad you got it working.
It should be pretty safe to flash ROMs on it, just make sure they are for the N7105.
Always make a cwm backup, then u can just flash that to restore everything.
If you follow theses rules when flashing ROMs, they should boot fine most of the time:
Wipe data/factory reset
Wipe cache
Install ROM
Wipe data again
Wipe cache
Fix permissions
Custom ROMs are so much better then stock, so its a shame not to use them
Cheers
Corey
Sent from my GT-N7100
If I helped you, please hit Thanks..
Did you do a data/cache wipe when you installed CM nightly over the stock rom ? Maybe that's why it wouldn't boot up.
Anyway, don't be afraid of custom roms, if CM10.1 is what you'd rather use - try again and if something goes wrong - there's tons of people here who can help
Also *always* make backup of IMEI, it can get borked for no reason :silly: TWRP has the ability to backup only single partitions eg.
Akiainavas said:
Did you do a data/cache wipe when you installed CM nightly over the stock rom ? Maybe that's why it wouldn't boot up.
Anyway, don't be afraid of custom roms, if CM10.1 is what you'd rather use - try again and if something goes wrong - there's tons of people here who can help
Click to expand...
Click to collapse
Yes, I did the Factory Reset and wiped cache & delvik cache first.
Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
4. flashing the CM10 on my SXS with built number *.2.55 will work?
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.
chossen said:
Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.
Click to expand...
Click to collapse
I dont have an Xperia yet, but from reading and experience from other phone ...
1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware.
2) if you wiped, try to restart with flashing the firmware again and wiping everything.
3) if nothing working reflash stock, boot stock once to see if it is working without bootloops and then restart from scratch.
4) if also not working .... is it the correct firmware? did you forget something?
There are good instructions for the firmwares, if you do everything as explained, you shouldnt get bootloops. But ... no howto is perfekt.
Its mostly trying as much as possible, till you have the correct way to flash a firmware. Bootloop isnt that bad ...
If you have a way which works for you, keep the steps for later flashing and tell the community what you had to do differently or if you missunderstood some points, even then tell it, because that can make these instructions better.
---------- Post added at 04:36 PM ---------- Previous post was at 04:31 PM ----------
chossen said:
4. flashing the CM10 on my SXS with built number *.2.55 will work?
Click to expand...
Click to collapse
I would say that it doesnt matter which firmware is on the phone, as long as you unlock the bootloader and the fastboot or flashtool is working.
The custom firmwares use the same methods but might have added recovery for easier flashing later.
You should even be able to downgrade to older firmware with unlocked bootloader and flashing the ftf file.
Its only important to wipe the data, cache and dalvik cache that the firmware is working.
thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?
chossen said:
thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?
Click to expand...
Click to collapse
With different phone and different firmware i had some issues with recovery, specially if i didnt wipe directly after flashing the new firmware without reboot and without reboot into recovery ...
I hope i dont mix anything up. CWM is the recovery (?)
The recovery function is part of the kernel image which is exactly the boot.img.
You can see at the freexperia project page howto install CM10, i cant post links at the moment.
3rd point is flashing the CM kernel (boot.img)
4th point is booting into recovery
From that recovery you can flash the custom rom as described in point 5.
Point 6 is wiping the device, which is neccessary for first custom rom or if you change version (eg. CM9 to CM10) or if you change to a different ROM.
Most bootloops happen if you forget to wipe the device. I am not sure, but most important is dalvik cache, if that one is wiped the next boot takes longer, as it will be rebuilt during boot.
If you get into a bootloop after flashing kernel and custom rom, go into recovery and wipe the device, try rebooting.
If still in bootloop, try to reflash the custom ROM as in point 5 (starting at 4th point) and wipe device after flashing
If it didnt help, try reflashing the kernel and ROM, starting at point 3 and include the wiping the device.
If that didnt help, try to go back to full stock (kernel and rom) and repeat.
But check if you got the correkt ROM for your device.
Play a bit around with the steps, you can even reflash the kernel and leave the rom. I had once a bad situation with bootloops, but they are easy to fix. More important is the part with the kernel, i think there you can brick your device.
But when you follow the instructions you shouldnt have too many problems, just dont jump over a step at the first flashing. But as allways sayd, every custom rom, every kernel flashing can harm your device and you're responsible on your own.
But if you get into problems, write down what you did and you will get help here.
Edit:
"if not possible then reflash the firmware ..." There i had once a problem with a different device. I forgot to wipe after flashing a new version and got into a bootloop. In recovery i couldnt wipe the device fully, something got bugged, but reflashing helped. Reflashed wiped and i could reboot into system. As it was longer time ago i dont remember what exaclty happend, but i think the problem was about forgetting to wipe the device.
Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium
chossen said:
Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
didnt take too much time
in case of first custom rom, changing custom rom version (e.g. CM9 -> CM10) or changing to a different custom rom: all: factory reset, cache and dalvik
in case of updating (e.g. CM10->CM10): dalvik should be enough, maybe cache and dalvik.
If something not working, do a complete wipe.
As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app
daddyc00l said:
As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
No, he has no bootloops, from what i understood he is scared to get into bootloops and doesnt know what to do if it happens.
Hmm, kernel flashing after upgrading from ICS to JB? or all the time?
By kernel flashing you mean the boot.img flashing with fastboot, and its the same file as flashed before?
I've only ever fastboot'd my first kernel, advanced stock kernel. Any others have always been in recovery and never had any issues
Sent from my Android 4.2.2 Xperia S
It seems that you got the wrong Kernel. I'm not sure, of course.
But I had that issue some time ago, and a fix it flashing the right kernel that I found on xda forum. Ohh, dont forget to do the proper wipes.
I hope u solve this as soon as possible.
For some good info on recovering a phone read through the recovery thread in my signature.
Even if you don't have any issues now, you can see what others have done wrong & right.
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread
OK. I flashed the wrong kernel on my new Nexus 7 (2013). My stupid, I flashed the kernel (franco) for the old Nexus 7 on the new one.
Luckily, I can still access bootloader and recovery (TWP). Now it's stuck at Google (again, I can still go to bootloader and recoery).
Where can I find the stock kernel that I can use? Or Can I flash a custom kernel?
Thank you in advance and I appreciate every comment.
http://forum.xda-developers.com/showthread.php?t=2380380
I recommend flashing a custom kernel.
Username invalid said:
http://forum.xda-developers.com/showthread.php?t=2380380
I recommend flashing a custom kernel.
Click to expand...
Click to collapse
Thank you indeed.
opticaldh said:
Thank you indeed.
Click to expand...
Click to collapse
I have flashed this kernel http://forum.xda-developers.com/showthread.php?t=2390173
and I'm still stuck at Google, I can go to bootloader and recvery (TWP). Please help me (
Have you considered trying this which will return your Nexus 7 to its original factory settings with a stock image? I haven't used this method but it may get your tablet working again. Also, for future reference, you should always make a nandroid backup before you flash something new in case you run into problems like this.
Wiping the cache/dalvik cache usually works for me when it would hang on the boot screen after a flash.
Username invalid said:
Wiping the cache/dalvik cache usually works for me when it would hang on the boot screen after a flash.
Click to expand...
Click to collapse
I did it but nothing changes
Do you have a ROM installed?
Try restoring to factory settings, reflashing a ROM, and then flashing the kernel. Wipe cache/dalvik once you're done and see if that works.
cyberprodigy said:
Do you have a ROM installed?
Try restoring to factory settings, reflashing a ROM, and then flashing the kernel. Wipe cache/dalvik once you're done and see if that works.
Click to expand...
Click to collapse
I'm running on STock, so I have to download a custom ROM, right?
and how to restoring to factory settngs, btw? in twp, a factory reset is wipes data, cach and dalvik. I did that.
opticaldh said:
I'm running on STock, so I have to download a custom ROM, right?
and how to restoring to factory settngs, btw? in twp, a factory reset is wipes data, cach and dalvik. I did that.
Click to expand...
Click to collapse
Try flashing the stock rooted ROM here.
To restore to factory settings, go to "Wipe" then slide the slider at the bottom of the screen.
Sent from my Nexus 7 using xda app-developers app
opticaldh said:
I'm running on STock, so I have to download a custom ROM, right?
and how to restoring to factory settngs, btw? in twp, a factory reset is wipes data, cach and dalvik. I did that.
Click to expand...
Click to collapse
Thanks cyberprodigy and Username invalid for helping me.
I fixed it.
After flashing 2 custom kernels (all of them were said to be completed install) but I was stuck at Google.
So I tried to flash a stock kernel (I downloaded it from here, sorry for hotlink-ing from another forum: http://droidbasement.com/asus/razor/flo/sys-backup/jb-4.3_ota-full_n7_razor-flo.zip). I will also uploaded the stock kernel file extracted from that link in case somebody needs it but doesn't want to download the whole Stock ROM.
The file extension is .img, so for people not knowing how to flash this file, use this command
"fastboot flash boot <the file name.img>"
Thanks again.
Here is the llink to the stock kernel for N7(2013). it's 16Mb so I can't attach it.
http://www.mediafire.com/download/8t7lu3jc00mt0b9/bootN7.img