Hi all, I made a major mistake this morning flashing fauxs ultimate kernel. Basically forgot to wipe cache and davlik and now can't do anything with tablet. I backed up before flashing so can I get back into recovery through a dB and if so what commands to I need. Any help will be greatly appreciated
Wait you can go to recovery, and restore your backup and you call this a brick? I
Am little confused here.
(go into bootloader from there to recovery and recover it)
Sent from my Nexus 7 using Tapatalk 2
You forgot to wipe cache/dalvik and this "bricked" your device and then you posted your question in the wrong section?
You need to read and search and understand what you're doing prior to posting threads here.
shottle said:
Hi all, I made a major mistake this morning flashing fauxs ultimate kernel. Basically forgot to wipe cache and davlik and now can't do anything with tablet. I backed up before flashing so can I get back into recovery through a dB and if so what commands to I need. Any help will be greatly appreciated
Click to expand...
Click to collapse
If you have a custom recovery, plug your n7 into a computer, then boot up while holding volume down + power to get into fastboot mode, which will allow you to go into recovery.
Worst case scenario, you can use fastboot to reflash a stock image.
As others have said, you'll want to look it up and read more carefully. Most kernels don't even require wiping, though if you think this one does, you can try wiping them then reflashing the kernel again.
Related
I did a search but couldnt find any answers so please point me to the relevant post if this has already been answered, but is there any guide for the functions of TWRP 2.0? im coming from CWM on SGS II so would like to clear up a few things:
TWRP gives options to backup/restore 6 things - system, data, boot, recovery, cache, and .android_secure. Im mainly concerned about boot and recovery.
1) If we have TWRP and FIREFIREFIRE isntalled and working normally - then under normal circumstances should there ever be a need to restore boot or recovery, normally we would only restore system right?
2) If I was to restore the recovery while in recovery, could I not potentially brick/break recovery? If not, then I assume then either restoring/intalling a .zip containing the stock boot, recovery and system will return my kindle to stock (and ensure I no longer break warranty!!)?
Thanks in advance
Alchemist07 said:
I did a search but couldnt find any answers so please point me to the relevant post if this has already been answered, but is there any guide for the functions of TWRP 2.0? im coming from CWM on SGS II so would like to clear up a few things:
TWRP gives options to backup/restore 6 things - system, data, boot, recovery, cache, and .android_secure. Im mainly concerned about boot and recovery.
1) If we have TWRP and FIREFIREFIRE isntalled and working normally - then under normal circumstances should there ever be a need to restore boot or recovery, normally we would only restore system right?
2) If I was to restore the recovery while in recovery, could I not potentially brick/break recovery? If not, then I assume then either restoring/intalling a .zip containing the stock boot, recovery and system will return my kindle to stock (and ensure I no longer break warranty!!)?
Thanks in advance
Click to expand...
Click to collapse
I have read many forums of people boot bricking their kindles with twrp I would be very careful if thinking about doing this until a good tutorial is out that confirms this working with no bugs, just to be on the safe side. whatever your choice good luck and please post anything you find out so that we all can benefit from others experiences...! I am currently working on a good way to do just this and will post back to this forum when I work it out completely
Just bumping this in case anyone has answers for these questions yet?
Thanks,
Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root.
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.Try a stable ROM like CM7 and see what happens. I didn't want to do too much damage so haven't tried this option yet.
2.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Edit: I just tried Newtrino rom and stuck @ Moto screen which says unlock.
Edit 3/4/2012: Please go to the last post for the solution. Tenfar's CWM is old and cannot deal with latest ROMs. Use ROMRACERS latest CWM or touch based Koush's CWM for future ROM flashing.
Old CWMs will give you sleepless nights!
Ok tried restore again after wiping data, cache & dalvik cache.
Now after reboot, My Moto Logo screen says unlock and just starts flashing.
I can still get into recovery......
can someone please help me......
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
vsg005 said:
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
Click to expand...
Click to collapse
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Masterguy said:
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Click to expand...
Click to collapse
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
littleemp said:
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
Click to expand...
Click to collapse
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
flash the latest recovery and wipe everything in recovery and flash neutrino again. It should work after that. try neutrino 2.2 though. 2.5 still has it's kinks.
1st off, relax. It's difficult to brick your phone from this point Just don't get any bright ideas with .sbfs lol.
As others have said, make sure you're on latest recovery.
Question: are you installing from internal or external SD? Internal is recommended for flashing most ROMs.
Sent from my MB860 using xda premium
Masterguy said:
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
Click to expand...
Click to collapse
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Solved:boot loop issue
littleemp said:
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Click to expand...
Click to collapse
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Masterguy said:
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Click to expand...
Click to collapse
Thank you sooo much. I was having this exact problem. I did what you suggested and my phone works. Thanks!
Damn I'm dumb, I thought I'd have a go at attempting to make it so the bottom buttons would be hidden as I use gestures anyway
I modified the .prop file as a tutorial recommended but now after the Google logo (unlocked bl) I just get a black screen
I can access recovery which gives me the options START, RESTART BOOTLOADER, RECOVERY MODE and POWER OFF.
I am going to guess I need to bring it back to stock somehow - how would I go about doing this?
Any help is appreciated, Thanks
Kevin
TRIED:
Relocking and unlocking the bootloader - was hoping it would format the phone but it appears it keeps the build.prop.
I can boot into clockworkmod recovery but I'm scared to flash it for the moment before I get some advice from you guys
[EDIT] I see that Fastboot detects it - so I guess I can flash stuff.
In an attempt to fix this I flashed the stock rom from Google that ATGAdmin pointed out. Here's what I did below
0. Download above recovery image, extract into a directory with fastboot
1. Hold down power for 10 seconds to power off
2. Hold down voldown and then power for a few seconds until recovery appears
3. Run flash-all.bat or flash-all.sh if on Linux.
4. Phone should reboot.
Now device is stuck on nexus X logo, attempting reflash... Same problem
Halp D:
why dont you do restore the build.prop to the original one and also do a wipe cache and wipe dalvik from CWM
My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool
kn100 said:
My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool
Click to expand...
Click to collapse
You could sell me your phone:fingers-crossed: lol.... Hope you fix it
if you still have recovery clear dalvik cache and cache.
if you do not have recovery search for fastboot commands to do so as I guess you can still go into fastboot mode.
Recovery still works fine and I can boot into clockwork mod etc, it all appears to be working fine, except I just noticed in clockwork mod it's not able to format SDCard whatsoever - if this helps at all - I haven't flashed clockworkmod just to keep my options open, I just boot to it.
Any suggestions, I've tried flashing the google stock rom twice now and it doesn't appear to work.
boot in CWM and do a wipe dalvik and wipe data+cache bro ....
Try using mskip toolkit to flash stock image just done the exact same thing and works a treat. Didn't have any faults myself was just tinkering with it. Hope it helps
Sent from my Nexus 4 using xda premium
Booted into CWM
Wipe data/factory reset:
Wiping data, Formatting /data, Error mounting Data!
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure!
Skipping format
Data wipe complete.
wipe cache partition
Formatting /cache
Cache wipe complete
Wipe Dalvik cache
**page just refreshes, assume it just wiped**
After reboot stock recovery is used and again I am stuck at the X.
go into mounts, mount the data partition manually and then do a factory reset.
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Glad you fixed it:good:
glad you can now enjoy it
kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Awesome bit of kit. Glad you got it sorted pal
Sent from my Nexus 4 using xda premium
Congratulations, you have been the first to almost* break their N4. You have now began the famous tradition for this model , many shall follow, but we shall always know of your name first.
, glad it's fixed
Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?
For what it's worth, all that needed doing was flashing system via fastboot.
kn100 said:
Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?
Click to expand...
Click to collapse
Hahaaha I remember those days (hint-my avatar)
As a side note, you could have just followed the Galaxy Nexus guides for restoring to stock, but just replacing the system image files with those applicable to the Nexus 4.
Hey folks. I'm trying to flash Cyanogenmod to my Nexus 7 running 4.2.1. I am rooted and unlocked. I downloaded the nightly 10.1 as well as the stable 10.0 along with Gapps. Flashing both with Clockworkmod recovery gets me stuck in a bootloop with both options, forcing me to restore to my backup.
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup. I'm wondering if I should restore to factory on my current first? Am I missing any steps in this process? I'd like to be able to just tap and install if possible. I had bad experiences with flashing when I had my Galaxy Captivate.
I appreciate any help with this. I have gone through several forums and threads, but none seem to be device or situation specific so I thought I would bring up this specific situation. Thanks for any help.
JavaMac said:
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup..
Click to expand...
Click to collapse
You left out the "how you flashed" part. If you were using something such as ROM Manager, it may have wiped for you. But typically, for manual flashing from the recovery you need to do a "factory reset" procedure prior to installing a new rom. (A wipe which erases everything in /data except what is /data/media)
I've used a CM10.1 nightly and sequentially flashing the gapps, no troubles. Perhaps different versions though, the devil is always in the details.
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
JavaMac said:
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
Click to expand...
Click to collapse
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
JavaMac said:
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
Click to expand...
Click to collapse
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Success! TY.
Hello there, I just got my N10 32MB a few weeks ago and after playing with the stock rom for a bit decided to try some custom roms. I've tried CM10.1M3 and Paranoid and a couple others all with the same result. I flash them and they stay on the loading screen forever. I've used the Nexus 10 Toolkit donater version and I'm no stranger to dropping a custom rom on an android device I've been playing with them since the original Motorola Droid. I would have thought the N10 would have been cake to do this on but nothings is working. The ONLY rom it will take is the stock rom 4.22. I was able to successfully re-install it via adb after wiping all the roms off of the device. If anyone has any insight I would really appreciate it.
Go back in recovery, format /system, wipe data/factory reset, reflash ROM, gapps, reboot. Normal steps for flashing a ROM.
And you didn't use ADB to reflash stock images, but fastboot. Damn toolkits...
Sent from my Nexus
I'm no expert , but my first time I got the same result as you, what saved my bacon
Was that I done a backup first.
If I were to guess what my problem was
Maybe a corrupt donwload
And then make sure you do these steps
In recovery (cwm,tcwm)
Wipe -> Factory reset -> Cache and Davilk cache
Then go in
Install -> ROM -> Gapps
I take no responsibilities in case it bricks yours... but this as work for me.
Plus YouTube makes it really easy to do...if you need a videos tut's...
Sent from my Nexus 10 using xda app-developers app
Thanks for both the replies. Yes, I've done all this formatted system wiped both cache redownloaded the files tried sending them to the device from different PC's. You're right I didn't flash the rom via adb it was fastboot, I ened up having to sideload something via adb in tcwm maybe it was when I returned it to stock unrooted and relocked it to start all the way from square 1. I'm really at a loss I've let it sit at the boot screen for as long as 30 min and nothing starts up. It only seems to want to run stock 4.22.
ironhelix said:
I'm no expert , but my first time I got the same result as you, what saved my bacon
Was that I done a backup first.
If I were to guess what my problem was
Maybe a corrupt donwload
And then make sure you do these steps
In recovery (cwm,tcwm)
Wipe -> Factory reset -> Cache and Davilk cache
Then go in
Install -> ROM -> Gapps
I take no responsibilities in case it bricks yours... but this as work for me.
Plus YouTube makes it really easy to do...if you need a videos tut's...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Make sure your boot loader is unlocked. I remember having this issue on my Skyrocket awhile back. It would hang on the custom ROM installs.
cowabunga said:
Make sure your boot loader is unlocked. I remember having this issue on my Skyrocket awhile back. It would hang on the custom ROM installs.
Click to expand...
Click to collapse
It is...I even relocked it and unlocked it again as well as unrooted and rooted again to make sure.