Related
Hey I've just been reading posts on the forums and I had to ask, I since the play now supports recovery on locked bootloaders does that make custom roms possible? Specifically will any version of CM7 or 9 work on my bootloader LOCKED R800a (previously carrier locked to Telstra australia) sorry im completely over stock but don't have the money for a bootloader unlock right now
Sent from my R800a using XDA
nogggin1 said:
Hey I've just been reading posts on the forums and I had to ask, I since the play now supports recovery on locked bootloaders does that make custom roms possible? Specifically will any version of CM7 or 9 work on my bootloader LOCKED R800a (previously carrier locked to Telstra australia) sorry im completely over stock but don't have the money for a bootloader unlock right now
Sent from my R800a using XDA
Click to expand...
Click to collapse
Nope, never will either. Have to be able to flash a custom kernel which isn't possible without unlocking the bl. There's a thread around here talking about doing some backdoor crap to try and get around the bl, but it'll never happen due to lack of support for the xperia line in general. I'd say save that money up, it's so worth it
agraceful said:
Nope, never will either. Have to be able to flash a custom kernel which isn't possible without unlocking the bl. There's a thread around here talking about doing some backdoor crap to try and get around the bl, but it'll never happen due to lack of support for the xperia line in general. I'd say save that money up, it's so worth it
Click to expand...
Click to collapse
Hmm okay, I thought I read in another thread that there were some roms that didn't require a custom kernel...
A couple of ROMs don't require a custom kernel like: Gin2ics, NXT and others.
However all Cyanogenmod ROMs require custom kernels.
hi, I did a trade with some here on the XDA for a galaxy nexus. The phone comes with BAMF ROM but I am thinking of returning to the completely stock rom. Since I do not know much information on this phone, I thought I will ask before doing anything stupid.
I am not sure exactly if this is a international or playstore phone (I think it is international) but I do know it is a GSM phone.
Also, it appears to me that the phone is already unlocked (and I think rooted but cannot be sure).
So my question is how exactly should I go through to get the completely stock as I kind of want to try stock JB first. Do I need to relock it and download the image from google (which image as I see there are two version of phone.
I may try different rom in the future so can I just download teh image and flash the rom without relock it? Or I should still lock the phone, flash, unnlock, unroot?
A little bit of background. I am using the phone on T Mobile's network here in the US, so I want to be able to continue using hte phone on the same T MO.
Thanks a lot for all of the helps guys.
Link to the step-by-step, amazing, descriptive guide here
thanks a lot. I follow that thread and I think I have returned the phone to the stock rom.
Quick question, I think my bootloader is still unlocked as when I checked the bootloader, it looks it still says unlocked. Now after I have flashed the stock rom, should I still root it and also install the recovery if I ever plan to play around with the different roms? As of now, when I into recovery, I see the little andrid icon but no selection.
thansk a lot guys.
PUTALE said:
thanks a lot. I follow that thread and I think I have returned the phone to the stock rom.
Quick question, I think my bootloader is still unlocked as when I checked the bootloader, it looks it still says unlocked. Now after I have flashed the stock rom, should I still root it and also install the recovery if I ever plan to play around with the different roms? As of now, when I into recovery, I see the little andrid icon but no selection.
thansk a lot guys.
Click to expand...
Click to collapse
If/when you want to root and mess with ROMs, you'll be using a custom recovery like CWM. You don't need to flash it until you choose to do those things.
thanks. Would I need to root again? The phone is already unlocked (as I did not lock it again). So, I would just have to root and then flash the custom recovery then?
BTW, I notice there's a very nice tool on the sticky that does everything. I am curious if I use that tool and let say choose to unlock it again or root again and such, would that be any issue? Ie, if it's already unlocked and you run unlock again, would that relock, etc?
PUTALE said:
thanks. Would I need to root again? The phone is already unlocked (as I did not lock it again). So, I would just have to root and then flash the custom recovery then?
BTW, I notice there's a very nice tool on the sticky that does everything. I am curious if I use that tool and let say choose to unlock it again or root again and such, would that be any issue? Ie, if it's already unlocked and you run unlock again, would that relock, etc?
Click to expand...
Click to collapse
You can easily root too if you want to in the future
I think you're talking about the toolkit... Me and others here don't recommend using that... Unlocking/locking the bootloader is easy anyways...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
PUTALE said:
thanks. Would I need to root again? The phone is already unlocked (as I did not lock it again). So, I would just have to root and then flash the custom recovery then?
Click to expand...
Click to collapse
Flashing a custom recovery is part of the rooting process.
BTW, I notice there's a very nice tool on the sticky that does everything. I am curious if I use that tool and let say choose to unlock it again or root again and such, would that be any issue? Ie, if it's already unlocked and you run unlock again, would that relock, etc?
Click to expand...
Click to collapse
Don't use 1-click toolkits. You know how to do it manually, do it manually.
got it, thanks a lot guys. Will have to read up more on the root and flashing rom. Android is still relativly new to me.
Hello, and sorry for bugging everyone, but I have somewhat of a problem. I'll just start from the beggining.
First of all I own a SGS II, so I'm used to flashing roms and kernels custom stuff and all...on that. My girlfriend is the one who owns a Xperia Arc S (LT18a, US version if it's relevant or not). And for the live of me, I can't summon the courage to flash it, the process being somewhat different than the flashing of a S2. That's just idiot proof in my opinion, can't go wrong. I'm seeing all over the place guides and stuff for flashing a Xperia Arc S, and don't really know wich one is good/bad etc. So...the actual questions :
1. Where can I find the stock firmwares for Xperia Arc S ? I was hopping on a website something like sammobile for samsung, where I can find every release etc.
2. She now has 2.3.4 (I think not 100% sure) build 4.0.2.A.0.62 and from what I heard that cannot be rooted, or it involved something like unlocking the bootloader or something like that, safe to say that kinda freaked me out a bit.
3. I'm guessing that this build 62 is like on my samsung, where different stock rom's are differentiated by letters (eg. XXLPG, XWLPQ etc) so, someone please confirm that.
4. Is there any noticeable difference between these gingebread builds, cause if build 62 can't be rooted, I'll downgrade to previous build that can be more easily rooted.
5. I really need a idiot proof guide to flashing this thing. She has no warranty on it and I really don't want to mess it up
6. And last (finally, I know ) some links for safe versions of flashtool (equivalent of odin from what I understand) and firmwares, stuff I need to root it etc.
I apologise for such a long post but this stuff is pretty overwhelming for me. Also I apologise for spelling errors (english is not my first language)
Wow, the things we do for love...
OK, here's a quick run-down of how it works.
Firstly the bootloader thing: -
The bootloader is where the "kernel" sits. If you unlock the bootloader then you can pretty much put anything on the phone.
You can flash a custom kernel, and from there on you can use ClockworkMod recovery the same way you do on your Samsung.
(
custom kernels have ClockworkMod recovery built into them since the XPERIA doesn't have a "/recovery" partition for the standard ClockworkMod recovery.
If that didn't make sense then here's a translation "There's no special space for CWM recovery on Sony phones! So custom kernels have CWM recovery built in for easy access."
When one of these kernels starts up the phone there's a point where the hardware buttons light up, and the LED flashes purple. If you press "volume down" at this point then the kernel starts up ClockworkMod recovery instead of booting the phone.
Most roms come with their own kernel that you can use like this. The XPERIA is different to the SGS phone because you can't flash a kernel from the phone itself. You need an unlocked bootloader and fastboot to flash a kernel.
)
So unlocking the bootloader is a good idea, but only after you've made a backup of all your stuff off the memory card.
Here's a really good thread that brings together all sorts of pieces of information that you might need to root the phone - http://forum.xda-developers.com/showthread.php?t=1653188
OK, so that's the unlock thing, and the kernel thing. Once the kernel has CWM recovery built in you can pretty much flash any rom you feel like flashing. There are already some JellyBean roms out that are fast and usable if you're prepared to read up on them and experiment a bit.
Next thing is the "BaseBand". This is the driver for the "cell phone radio". The part of the hardware that's actually responsible for behaving like a phone
Here's a thread where you can get all of the different base-band versions: - http://forum.xda-developers.com/showthread.php?t=1688049
Personally I know that base-bands 72 and 77 both work perfectly. Since they are the 2 newest versions you can choose which-ever one you want. The newer basebands give much better signal strength on the phone, and the call quality is really good.
Good luck with the experimenting - hope you enjoy.
Are you looking to upgrade her arc to ics? It is much easier to find the resources if that is the case
Sent from my LT18i using xda premium
navras1719 said:
I can't summon the courage to flash it, the process being somewhat different than the flashing of a S2. That's just idiot proof in my opinion, can't go wrong.
Click to expand...
Click to collapse
So is flashing on the Arc/S, so long as you can read.
http://forum.xda-developers.com/showthread.php?t=1304634
Thanks for taking the time to answer such a long and frankly, annoying post Seems I got a bit of homework, manny things to read, so...coffee and patience Hope everything will add up nicely
jman2131 said:
Are you looking to upgrade her arc to ics? It is much easier to find the resources if that is the case
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
Not really, from what I hear ICS dumbs down the phone sort of speak. Now I really can't say, but I would test it out a bit, as long as I learn how to go back to GB.
Another thing that I'm a bit concerned is that all the stuff I find are for LT18i and my gf's phone is a american model LT18a. Will this be a problem ? Or that's just to differentiate the hardware stuff in them ? I hope flashing a LT18i firmware doesn't screw anything up
navras1719 said:
Not really, from what I hear ICS dumbs down the phone sort of speak. Now I really can't say, but I would test it out a bit, as long as I learn how to go back to GB.
Another thing that I'm a bit concerned is that all the stuff I find are for LT18i and my gf's phone is a american model LT18a. Will this be a problem ? Or that's just to differentiate the hardware stuff in them ? I hope flashing a LT18i firmware doesn't screw anything up
Click to expand...
Click to collapse
Yep, the differentiating factor is the hardware. the lt18i and lt18a roms are the same as far as I know. ICS does tend to be more resource heavy especially on the arcs but downgrading back to GB is basically the same method as flashing the ICS, just with another rom.
And also, in response to your first post, you can downgrade to the rootable build of GB, root that, and then flash the build 62 kernel back onto your phone so it's rooted and of the desired build
There's a lot of flashing guides on youtube regarding the arc s. I did a quick search and this one seemed pretty accurate and straight to the point.
Ok I pretty much understood the whole shabang, my last question is about the bootloader, if I unlock it once that's it ? I can flash whatever I want and not need to reunclock it...sort of speak. I read that for warranty reasons it can be relocked but that's not the case for me. Also for flashing a stock rom is it necessary to unlock the bootloader or that's just for rooting ?
Oh and almost forgot...if I understood right...I can downgrade...root...then upgrade to 62 and it will still be rooted ? On my samsung if it'a rooted and I flash abother stock rom...bye bye root, so pretty weird for me. Thank you again, I can't stress enough how helpfull you guys were.
Sent from my GT-I9100 using Tapatalk 2
unlocking the bootloader allows a whole lot more things to be done with the arc, but does make some apps defunct such as track id and music facebook like (which many can do without). flashing and/or rooting a stock rom doesn't need an unlocked bootloader because it's stock and yep, you can downgrade/upgrade, root, and then go back to what build you want by flashing a kernel only
jman2131 said:
unlocking the bootloader allows a whole lot more things to be done with the arc, but does make some apps defunct such as track id and music facebook like (which many can do without).
Click to expand...
Click to collapse
That only applies if you use the official method to unlock, use SETool and you'll retain DRM.
Sent from my CM9'd Ray
XperienceD said:
That only applies if you use the official method to unlock, use SETool and you'll retain DRM.
Sent from my CM9'd Ray
Click to expand...
Click to collapse
Thanks for the clarification. I never knew much about bootloaders and all that
XperienceD said:
That only applies if you use the official method to unlock, use SETool and you'll retain DRM.
Sent from my CM9'd Ray
Click to expand...
Click to collapse
If you could help me out with a SETool link and a basic set of instructions that would be awsome
LE: From what I've seen there are 2 versions of SETool and one's free the other is not. Can the free version be used to unlock the bootloader or do I have to get the full version ? Or even simpler, is there anyway to unlock it (LT18a) free and without losing DRM ?
XperienceD said:
http://forum.xda-developers.com/showthread.php?t=1304634
Click to expand...
Click to collapse
So basically from what I read there, no way for free unlock and retain DRM.
navras1719 said:
So basically from what I read there, no way for free unlock and retain DRM.
Click to expand...
Click to collapse
Follow the instructions up to the point just before patching and tell me what it says please?
if you unlock the bootloader NEVER UPDATE OVER THE AIR this will brick the phone.
The're 2 ways to unlock bootloader
1 via Sony web site but this only works for non branded phones,
2 is to pay if you use a service with setools this will unlock bootloader and make phone SIM free.
Xda member jinx13 offers this service contract him for more info.
Sent from my LT18i using xda premium
zolaisugly said:
2 is to pay if you use a service with setools this will unlock bootloader and make phone SIM free.
Click to expand...
Click to collapse
If SETool can unlock any handset I'm not sure why the S1Tool wouldn't, has anyone confirmed in the thread it doesn't work for the Arc S?
XperienceD said:
If SETool can unlock any handset I'm not sure why the S1Tool wouldn't, has anyone confirmed in the thread it doesn't work for the Arc S?
Click to expand...
Click to collapse
Since my bootloader was opened the setools has been upgraded to setools2 which now covers more phones but not sure which.
Sent from my LT18i using xda premium
XperienceD said:
Follow the instructions up to the point just before patching and tell me what it says please?
Click to expand...
Click to collapse
I'm sorry but what are you refering to ? The process that involves opening the backcover under the battery ?
Some additional info, it's not carrier branded, not sim locked...and using the service code in the dialer says bootloader unlockable : yes
Sent from my GT-I9100 using Tapatalk 2
Should have had this done already.
Sent from my CM9'd Ray
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Sent from my XT907 using Xparent Cyan Tapatalk 2
Gblake13 said:
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Click to expand...
Click to collapse
Right now, there is no way to root or unlock the bootloader in your situation. It sucks, but it's where we are.
Don't hold your breath for an exploit, either. Motorola/Verizon closed all known holes for BL-unlocking in the penultimate Jellybean OTA, and the only root method that worked in the last JB no longer works here.
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
gtmaster303 said:
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
Click to expand...
Click to collapse
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
RikRong said:
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
Click to expand...
Click to collapse
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Any luck with a rootkeeper/root survival of any kind?
pnwsr6 said:
Any luck with a rootkeeper/root survival of any kind?
Click to expand...
Click to collapse
Haven't seen it yet.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
Click to expand...
Click to collapse
My story is somewhat different. I tried to find a way to get rooted KK on my phone (trying to play junior hacker again), ended up soft-bricking my phone to where the only way to fix it was to flash stock KK using RSDLite (did try RSD'ing JB first, but my bootloader was having none of that).
So now I'm hopelessly stuck with a completely stock phone without root.
I feel like the only way to get past this is to attack it politically, like if every single Verizon XDA user banded together and flooded Verizon corporate inboxes with legitimate reasons why we need unlocked bootloaders.
Or maybe if someone is good friends with a politician who is more left of center and concerned about consumer rights over corporations. Maybe convince them that it's better for the environment because potentially millions of phones could be saved from going into landfills if we mandate companies must allow bootloader to be unlocked when certain conditions are fulfilled, like if a phone reaches 1-year of age.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Click to expand...
Click to collapse
I new I was losing root with it as well. I liked the features that KK brought with the update and still did it. The update finally got me using Smart Actions and I'm getting pretty decent battery life, nothing mind blowing, but pretty good. Buying a portable battery pack has pretty much solved the problem I had with nonroot. Now I can go about 2 days as long as I carry it around, lol. Luckily it's small.
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Flash a custom recovery via fastboot, and then flash SuperSU zip in recovery.
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
megaghostgamer said:
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
Click to expand...
Click to collapse
^^^He doesn't need an exploit since he has an unlocked BL. Also, this has been checked on the M and HD family of devices, it WILL NOT work because the the current KK updates have already patched the hole that this exploit is meant to take advantage of.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Yes!.. Just use URL="http://androidhosting.org/Devs/Dhacker29/msm8960/CWM6049-RAZR-HD_M-KITKAT.img"]custom recovery[/URL] and flash Superuser zip
And what about aka test points? Many Motorola models had such special test points using which you could get unlock of BL. How about our XT907? Any ideas about test points or shortcircuit of contacts?
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Confirmed working!
Root and bootloader unlock!
Sent from my Droid RAZR M
GnatGoSplat said:
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
Click to expand...
Click to collapse
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Click to expand...
Click to collapse
Ah, I see. Good to know. :good:
Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks
astrovale said:
Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks
Click to expand...
Click to collapse
Because
1) Bumping is used to trick the bootloader into thinking that the boot.img is authentic and from Official LG Sources
2) Without bumping you could have to constantly run fastboot boot boot.img (an example of this was CM11 when it first started development)
3) Bootloader cant be unlocked at this time so we rely on a bootloader exploit in order to run custom recovery
4) Its all about the authenticity. If the LG bootloader does its security checks and anything fails then the system doesnt boot
Thanks for the very easy tuo understand explanation. I should have thought that the problem was unlocking the bootloader! Guess I'll have to with the Flow and bump my new phone. I wish I asked my Carrier for an HTC M8
Sent from my Xperia Tablet Z LTE using XDA Free mobile app
simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.
rhystagram said:
simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.
Click to expand...
Click to collapse
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?
astrovale said:
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?
Click to expand...
Click to collapse
You're making it so much harder for yourself dude.. There really is only one way to install custom ROMs and that is by Bumping your phone. That's it.
You go here and read the entire topic. Don't miss a single thing.
Then go here and flash the zip for the latest TWRP.
After that you can install any ROM in the OG and Android Development section.
That's all there is to it. You can read in those topics for more information about what they do.
if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.
rhystagram said:
if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.
Click to expand...
Click to collapse
OK. Got it! It took a while, but I give up!
Thanks for the help. Coming from the most easy to play with phones (only Nexus so far, but I hate the N6), it isn't easy to have to deal with more stuff than usually needed and hence more complications than usually had.
I thought that, after rooting I could flash TWRP via flashify or rom toolbox and then I would have TWRP without BUMP, but it must be that I'm missing something, if you say I MUST bump my phone to install TWRP.
Thanks and see you around
How to bump lg g3
DevilFan14 said:
How to bump lg g3
Click to expand...
Click to collapse
What exactly do you mean "How to bump"??? Bump and loki are bootloader exploits that allowed us to boot TWRP and all the benefits TWRP offers... On the user side of things you don't "Bump" anything- the Roms, Kernels, and recoveries are "pre-bumped" by the developers and 99.9% of the time they will say whether or not it is "bumped" or "lokied" although loki is really outdated and I doubt you'll encounter it. So in a nutshell we(the user) doesn't "Bump" anything and just make sure to really read before flashing
Sent from my DROID RAZR HD using XDA Labs