Develop Bugs

Htc One X brick?

Hi guys.
I flash the fullscreen mode with cmw recovery, and when the system was reebot it stop to a boot screen (white with HTC One written).
I tried to lock bootloader and installing RUU, but it say me who phone is not plug on the pc.
I tried to wipe cache/dalvik/etc etc but I'm not able to restart my phone.
Anyone can help me?

I just try to "fastboot erase cache" and "fastboot reboot-bootloader"...but nothing.

..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on

j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Click to expand...
Click to collapse
I learn it yesterday evening, I don't forget to do it next time.
Now I'm trying to flash the RUU, before I didn't enter in fastboot.
Installing complete.........
anxiety....
...it work.

Yeah I had the same issue after installing the full screen patch too. Thankfully I'd done a Nandroid backup just after I rooted so I just did that. Would have installed a custom Rom otherwise
Sent from my Desire HD running Virtuous Affinity Sense 3.5

j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on
Click to expand...
Click to collapse
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?

kaminix said:
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?
Click to expand...
Click to collapse
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium

nooomoto said:
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Ah, yes. This is indeed what I'm looking for. Thanks, guess I'll just wait a little longer then.

my too sgs2 hard bricked becuase one for wrong bootloader and other for synah rc 3.6 kernal, so i bought one x and now lets see......will this work or not?

You have to make sure your RUU is for the same network and country and is newer then your current RUU or the CID will block it

return to stock rom

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.

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

[Q] Bumping????

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

Should I unlock my bootloader for safety reasons

I've always had my devices rooted and running a custom rom or at least a custom kernel or something of the sort "But" ever since I got my pixel about a year ago I haven't felt the need to root at all, stock rom is just perfect and so battery life and I don't see a reason to.
However I was just thinking that now with locked bootloader if for any reason my phone gets bricked then I'm probably [email protected]*t out of luck because I won't be able to flash a factory image to bring the phone back to life.
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?

Getting bricked is the direct result of flashing images.

nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
I could not disagree more. There are countless threads of individuals taking OTAs and running into boot loop. Additionally I have read through multiple threads where individuals were simply using their phone to play a game, text, phone call etc and the phone shuts off and goes into a loop.
The users with an unlocked bootloader were able to salvage the device. Users without a locked bootloader looked for a RMA.
To the OP- I personally will never own an Android device with a constantly locked bootloader. The safety net of being able to factory reset and flash stock images is something I've always cherished and do not wish to get rid of.
There are security risks to having an unlocked BL. If an Android savvy criminal were to steal your device they could do a lot of damage with obtaining personal information. For me, I'm much more worried about my phone going in to boot loop than I am some criminal being able to take my phone from me.

Sab3elbromba said:
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Click to expand...
Click to collapse
if for any reason, something did get corrupted on your phone with a lockedbootloader and it tripped verified boot. you would be locked out, no course of action but to get an RMA... so if u plan on tinkering with your phone or just would like a failsafe, at least with an unlocked phone. you would be able to flash firmware, etc...
just remember, not to relock your bootloader; unless your phone is running stock firmware and is wiped.... otherwise you will trip verified boot and brick it...
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
no, it's not. getting a bricked phone is pretty much always because the person did something ill advised or dumb... like relocking their bootloader running custom firmware...
so a diect result of user error, nothing to do with flashing images.