This forum is really big and I am new. I apologize if I am asking this in the wrong place. I have been reading a lot about how android working, and serving Google for answers.
I always thought that the only way to hard brick a device was to erase or corrupted the bootloader. Since even if the ROM and recovery had problems, you could use fastboot mode to fix things.
Now I am reading that Roms ussualy include a kernal, and flashing a kernal can lead to a hard brick. Does this apply to the Nexus 7 2012, or just devices that use download mode/ODIN instead of fastboot?
I always thought of a boot loader like an i intersection where you normally keep driving strait (into the main rom), or turn left (into recovery), or stay at the intersection (fastboot). How does a kernal tie into this? Do all Roms include their own kernal, or are different kernals and Roms usually flashed sepretly?
Thank you for helping me to understand this better.
Related
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
jbergen said:
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
Click to expand...
Click to collapse
Whatever you do, DO NOT DO ANYTHING ELSE UNTIL BTFB0 responds to your plea for help.
Do not just start trying different solutions, DO NOT FLASH ANY RUU, if you know what that is. BTFB0 is the guy who can get your phone unbricked if anyone can. He is the expert, I won't pretend to be able to duplicate his knowledge in this area.
Be patient until he has a chance to see this. You don't have to PM him, I'm sure he'll respond when he has a chance here in public. He will ask specific questions about what version of bootloader you have, 1.47 or 1.49, and you might as well find out if it's S=OFF or S=ON.
Also, do you have Amon RA recovery on your phone and can you get to it?
Have you tried flashing anything else since your phone has gotten stuck in this boot loop? If not and you can get into recovery still, then simply wipe data, wipe dalvik, and try flashing again. Don't worry you're phone doesn't sound bricked, just like you got a bad download or an error when flashing the rom. I would probably try a different rom or at least re-download the one you want to use.
It may still be wise to wait for BTFB0 to get here and offer some more advice as I am sure he has more knowledge in this area than me. But I do feel confident that he will say the same thing as I have.
Well, the OP merely said that he is having trouble with a specific ROM; he didn't mention failures during flashing; so, his problem could be as simple as having failed to "wipe" before flashing his ROM.
jbergen:
If you can boot into a custom recovery, your phone is not "bricked". It's not even soft-bricked; it's just not booting into the main OS correctly.
Providing as much detail as you can is helpful to people that are offering help to you; in particular, the following pieces of information:
- What recovery is on your phone? (Amon_RA, Clockwork? What version #?)
- When you are flashing the ROM file with your recovery, do you notice any "E:" messages?
An "E:" at the beginning of a line on the screen means that an error occurred!
- Are you having this same trouble on more than one ROM, or is this the only ROM you have tried since you rooted?
- What method did you use to root the phone?
- Did you use the "Wipe data/factory reset" menu item before you flashed the ROM file?
- Did you make any Nandroid backups that you still have on your SD card? If yes, did you attempt to restore one? What was the result? (BTW, every rooted phone user should be making Nandroid backups before they flash ROMs - no exceptions.)
- Do you have a media card slot or USB card reader device that will allow you to copy a different ROM file onto your SD card? -OR-
- Do you know how to "mount" the SD card onto the PC when your recovery is booted? (On Amon_RA, it is called "Toggle MS-USB" or something like that; it's also in the Clockwork menu somewhere too)
Given the information you have provided, there are any number of things that could be going on. I would suggest downloading a different ROM to your PC (let's say the stock HTC Eris March 2011 ROM), and then transferring it to your SD card. Then,
- Verify the exact size of the file and/or MD5 signatures of the file (if the developer provided it).
- make sure your phone is well charged
- perform a "Wipe data/factory reset" from the recovery menu
- Flash the ROM file from the recovery menu - and pay attention to the screen to see if there are any `E:' errors
- If there are errors, there is no point in attempting to boot the phone
- If there are no errors, boot the phone.
- Report your results here - and answer the questions that I asked.
OK, dumb question here, but I'd like to know. What's the difference between flashing the kernel and flashing the ROM. It sounds like flashing the kernel can lead to borking the tablet easier than flashing the ROM. I've tried several different ROMs with not problems but I have not knowingly yet flashed the kernel.
I'm having that problem with bringing screen back up after the tablets been sleeping and having to hit the power button several times before it stays on. Another thread indicated a kernal update as a fix.
Thanks,
Tim
I have had that same problem with bringing the screen back on, and I've also been wanting to switch to ext4, which some kernals support, but don't know which ROMs do.
lpsisrl said:
OK, dumb question here, but I'd like to know. What's the difference between flashing the kernal and flashing the ROM. It sounds like flashing the kernal can lead to borking the tablet easier than flashing the ROM. I've tried several different ROMs with not problems but I have not knowingly yet flashed the kernal.
I'm having that problem with bringing screen back up after the tablets been sleeping and having to hit the power button several times before it stays on. Another thread indicated a kernal update as a fix.
Thanks,
Tim
Click to expand...
Click to collapse
Slightly Askew said:
I have had that same problem with bringing the screen back on, and I've also been wanting to switch to ext4, which some kernals support, but don't know which ROMs do.
Click to expand...
Click to collapse
The process for doing each is about the same (depending on how it's packaged) ... most are packaged as a .zip file that you simply flash with CWM.
And in actuality, if you've flashed a ROM, you HAVE flashed a kernel. The ROM packages include not only a kernel, but the /system files and other items.
The kernel packages only contain the kernel.
Your likelihood of borking your tablet is (in my opinion) about the same for each.
Assuming you are familiar with CWM and backup your existing setup, you are pretty safe. Worst case scenario you are going to have to learn about nvflash.
I don't mean to be cavalier about flashing these tabs, but quite honestly if you have basic computer skills, and patience (and don't get all flipped out if you bootloop), you can revive these things from just about anything but an actual hardware failure.
Thanks, Zaphod. I tend to be a little reckless when it comes to these things. I just don't want a brick.
lpsisrl said:
Thanks, Zaphod. I tend to be a little reckless when it comes to these things. I just don't want a brick.
Click to expand...
Click to collapse
Well, it's certainly wise to do a lot of reading before you dive in. Even though I've not put myself into a situation needing nvflash, I have read up on it a bit and have all the files downloaded just in case
The biggest mistake I see people do on these boards is flash without reading up just a little bit more. Then they freak because the are stuck at the white birds
At that point they think they're sunk. In reality, nvflash will get you back to square one, it's just a little more work.
I'm sure if you try hard enough you could make a brick out of it, but I think you'd actually have to work at it.
I have been reading a whole bunch of stuff but can't seem to piece together what to do. My atrix is unlocked and rooted. I was flashing a rom and it started to boot loop. I would like to just flash it back to stock now. Confused if I should use fastboot or rsd. Some of the possible fixes I have found have bad links for downloads. I also saw a few things that said flashing back to stock with rsd could brick the phone??
After unlocking the phone I /would not/ recommend using RSD to flash /anything/.
When you unlock your phone, you burn a bit fuse that tells the phone you've unlocked it. There is no way to undo that. Using RSD improperly can cause your phone to hard brick and render it useless.
To avoid possibly breaking your phone from this point I would recommend taking a close look at what ROMs are available in the development section to see which one(s) suit your needs. Listed below are the ones I use on any of my three Motorola Atrix 4G's ( US ATT )
Neutrino ( CyanogenMod 7 Base )
NottachTrix ( Closest Stock Experience IMO and more customizable )
Currently I run NottachTrix because I like webtop, but prior to getting a lapdock for this phone I ran solely on Neutrino EE with 0 issues.
You'll want to take a look at setting up Motorola's USB drivers for ADB / Fastboot usage these are a must.
For either ROM to flash properly, AFAIK, you'll need to use ROMRacers Recovery found here.
These are just my personal favorites, as there are a plethora more ROMs out there in the development section. There may be a stock ROM that I just am not aware of you can flash through recovery, but I wouldn't know off the top of my head.
As far as fixing the boot-loop issue goes I would go into recovery and wipe cache / data / dalvik cache, under advanced in recovery, and then reflash the ROM you're trying to use.
That got me on the right track. Thanks it's fixed.
Awesome! Glad to have helped. =)
I have a spare Fascinate to hack around with. I've flashed all sorts of ROMs, but I've been consistently surprised with how much work it takes to reformat and flash ROMs.
Could someone describe the boot flow for this device? I suspect this would shed some light on why flashing ROMs requires the dance of three-finger booting and specific order of operations.
What is preventing us from building our own system images to be flashed through Odin?
My end-goal is to work towards making the Fascinate much more approachable, when it comes to modding. Since the bootloader isn't locked (right?) and we have a debug interface we can access via Odin and Heimdall, I'm not sure why it's such a hassle.
OK so it started with having a well balanced stock rooted 4.0.1
the main reason i root is for tethering
i had a carrier update that i was hoping was 4.1 cuz i am dying for google now
ran that but got stuck in the boot (as in not a boot loop but just infinite boot)
i would simply like to have my phone back on a stock rooted ROM* preferably ICS
i attempted "solutions" i found on here for using odin to "plop" a stock rooted ROM* on there but it turned out to be Gingerbread -_-
so i am currently dealing with that and what appears to be a stock Bootloader*
*i barely understand all these terms so please let me know i love to learn and i just cant wrap my head around all of it but any tips would be great. as far as i understand the boot loader is like the boot menu on a computer in the bios and is accessed when holding down all three hard buttons and gives you the selection menu, and the ROM is like the OS, and i think flashing is whenever you use odin to install the ROM instead of the boot loader for some reason.
I apologise for the noobieness but this is like the only way i learn...from direct Q&A :/
thank you in advanced
First off, download:
UCLE5 ICS- This is the stock AT&T GS2 ICS and is already rooted.
Fire up Odin, and:
Code:
Put UCLE5_Stock_Rooted.tar in the PDA slot in Odin.
Reboot your phone.
Oh and, a ROM is sort of a firmware that runs atop a kernel. Usually ROMs and kernels are put in ZIP files for flashing via ClockworkMod Recovery, but in specific cases (such as with Samsung), you can flash them via Odin or Heimdall in .tar formats.
Basically an Android phone needs both a ROM and kernel in order to run. From my very limited knowledge, a kernel is what controls overclocking and other processor related tasks. It also can help define the keylayouts for this particular device. It also contains the system recovery. A ROM holds all the system framework files that arguably makes the phone what it is to the average user. There are many ROMs that are available, such as Touchwiz (Stock/Modded Samsung), AOSP (Stock/Modded Android), Miui (Based off of either Samsung or AOSP, sort of it's own thing).
EDIT: Also, don't be sorry! Feel free to ask questions (as long as you've searched already), and remember that everyone starts somewhere.
We understand that you're new but please attempt to search your problem. Also, 4.0.1 does not and has never existed for our device so I don't know where you got that. Everything else though is easily found on Google, I don't buy that "I need spoonfeeding" line for a second.
Sent from my Zanpakuto using Getsuga Tensho!
PM me and I can give you further instructions if you still can't figure it out.
Hey thanks for your response!
I haven't had the time to try it out just yet (super busy lately) but as soon as i get the chance i will leave a reply as to how it goes.
Also thanks for the explanation. That really helps. I have always wanted to get more into the android field to learn more about the devices i'm using every day.
Ps: The reason for the apologetic sorry is to stand as a polite understanding tone from people who frequent the forums and discourage new posts while assuming no research has been done. i have searched for a good two hours but finding something relevant enough that i would be comfortable progressing through is very difficult and as i mentioned earlier i do learn better from direct Q&A. Thank you for understanding.
~Killubear
estabien said:
First off, download:
UCLE5 ICS- This is the stock AT&T GS2 ICS and is already rooted.
Fire up Odin, and:
Code:
Put UCLE5_Stock_Rooted.tar in the PDA slot in Odin.
Reboot your phone.
Oh and, a ROM is sort of a firmware that runs atop a kernel. Usually ROMs and kernels are put in ZIP files for flashing via ClockworkMod Recovery, but in specific cases (such as with Samsung), you can flash them via Odin or Heimdall in .tar formats.
Basically an Android phone needs both a ROM and kernel in order to run. From my very limited knowledge, a kernel is what controls overclocking and other processor related tasks. It also can help define the keylayouts for this particular device. It also contains the system recovery. A ROM holds all the system framework files that arguably makes the phone what it is to the average user. There are many ROMs that are available, such as Touchwiz (Stock/Modded Samsung), AOSP (Stock/Modded Android), Miui (Based off of either Samsung or AOSP, sort of it's own thing).
EDIT: Also, don't be sorry! Feel free to ask questions (as long as you've searched already), and remember that everyone starts somewhere.
Click to expand...
Click to collapse