Rom installed wrong ? - AT&T, Rogers HTC One X, Telstra One XL

I just installed official 4.2 android for htc one x.
after a few days it died . can't power it anymore.
I tried all the methods or powering a phone , belive me , all of them !
Did this happen because maybe , just maybe , the rom didn't install corectly ?
i went to a service and they told me they must "rewrite the boot"(i translated what they said , i'm from Romania)
what does that mean ?

hmmm......
Alaek12 said:
I just installed official 4.2 android for htc one x.
after a few days it died . can't power it anymore.
I tried all the methods or powering a phone , belive me , all of them !
Did this happen because maybe , just maybe , the rom didn't install corectly ?
i went to a service and they told me they must "rewrite the boot"(i translated what they said , i'm from Romania)
what does that mean ?
Click to expand...
Click to collapse
because ure device with a few days, why you dont bring the device to the service center. because iam afraid the phone physical defect. no offense just my opinion and i was experienced thats before with xmiro

Alaek12 said:
I just installed official 4.2 android for htc one x.
after a few days it died . can't power it anymore.
I tried all the methods or powering a phone , belive me , all of them !
Did this happen because maybe , just maybe , the rom didn't install corectly ?
i went to a service and they told me they must "rewrite the boot"(i translated what they said , i'm from Romania)
what does that mean ?
Click to expand...
Click to collapse
You haven't provided enough information. You need to tell us which phone you have, your bootloader details, exactly which ROM you installed, exactly which methods you tried to power it on. Saying "I've tried everything" pretty much means nothing here, we need all the details to be able to help you.
Sent from my Evita

Leave the phone plugged to the wall charger (not connected to a computer by USB) overnight, and try to power on again. Try both regular power on, and bootloader. Try these while the charger is connected (as well as not connected), also.
There is a known bug with the phone, where it can sometimes be difficult to power on after draining to shutdown. You may be experiencing this bug, rather than anything to do with the ROM install. Especially if you didn't experience any other bugs for a few days after the ROM flash, I would tend to think it is not the fault of the ROM.

Related

[Q] I bricked my wave 525, It don't even get into download mode

I was trying to port Android on Samsung Wave 525, So I got into Download mode then I just used the BOOTFILES and fota, but nothing happened, I just got some error (Didn't notice :crying: ) after that I just removed the battery and reinserted it and now its not even switching on. Its completely dead, I can't even get into Download mode too :crying:
Please some one help me :crying:
Please ignore if I had posted in wrong section, I'm completely confused, I really don't know what to do :crying:
No Body ?
spkpravee said:
I was trying to port Android on Samsung Wave 525, So I got into Download mode then I just used the BOOTFILES and fota, but nothing happened, I just got some error (Didn't notice :crying: ) after that I just removed the battery and reinserted it and now its not even switching on. Its completely dead, I can't even get into Download mode too :crying:
Please some one help me :crying:
Please ignore if I had posted in wrong section, I'm completely confused, I really don't know what to do :crying:
Click to expand...
Click to collapse
Nobody here to help me :crying:
spkpravee said:
Nobody here to help me :crying:
Click to expand...
Click to collapse
If your device is under warranty, go to a Samsung SC. Probably your ROM has gone bad. Basically it doesn't know what to do when you press the POWER button.
P.S.: No need of telling the SC guys about the android porting and all. Just tell them that your phone has gone dead and they will probably change your motherboard right away.
If your device's warranty has expired, then the MoBo charges will be around 2-3k (not sure though)
Re:
akshaylodhi said:
If your device is under warranty, go to a Samsung SC. Probably your ROM has gone bad. Basically it doesn't know what to do when you press the POWER button.
P.S.: No need of telling the SC guys about the android porting and all. Just tell them that your phone has gone dead and they will probably change your motherboard right away.
If your device's warranty has expired, then the MoBo charges will be around 2-3k (not sure though)
Click to expand...
Click to collapse
I don't have warranty for that mobile, Its old one.
I checked with Service center and they said, Mother Board is dead and want to replace it.
They said its around 2.7k.
Thanks for your reply
It also happened to me on my samsung wave two. all i did is i have remove the the battery and th mmc for an hour. After that i tried download mode and and it worked! hope this help give it a try.
you kill boot. You can restore the phone using JTAG or Riff BOX. they are in SC

[Q] Samsung wave II bricked

Hi everyone!
A friend of mine found a samsung wave 2. Because it was locked with a password i tried to flash new firmware on it with multiloader.
It gave an error and now i can't get into download mode anymore, it appears on the screen for half a second and then the phone reboots.
I also can't charge it anymore because if i plug it in, the empty battery appears, and the phone reboots after 15 seconds. It doesn't seem to charge and i guess that's why i cant stay in download mode. Also it gets quite hot while charging...
Any ideas how to fix this? I've found numerous topics spread across the internet but none give a real solution :s
Thanks in advance.
Flash a stock firmware using Odin. That should help.
Press thanks if I've helped you
Sent from my GT-P5110 using XDA Premium HD app
No you didnt help, but i managed to charge the battery by wiring it to my galaxy s2, quite dangerous imo
but i succeeded and managed to get into download mode without rebooting, SOLVED
Bricked samsung waves s8530
I have samsung wave s8530... I had tried to flash the same using the turko Cfw version 9,but could not do it correctly... Now the phone is not switching on. And also not going into download mode... Wat should I do plz help
bango7886 said:
I have samsung wave s8530... I had tried to flash the same using the turko Cfw version 9,but could not do it correctly... Now the phone is not switching on. And also not going into download mode... Wat should I do plz help
Click to expand...
Click to collapse
So... Looks like it's hard bricked ... So ... just go to an Authorised service centre, and Play Dumb. Just tell that suddenly your phone wouldn't turn on and that you donno what happened (don't tell about rooting or anything) .... So, depending on how well you acted and how dumb the service centre people are, you 'may' get a replacement under warranty ..
ndmicH perfectly
niranjan94 said:
So... Looks like it's hard bricked ... So ... just go to an Authorised service centre, and Play Dumb. Just tell that suddenly your phone wouldn't turn on and that you donno what happened (don't tell about rooting or anything) .... So, depending on how well you acted and how dumb the service centre people are, you 'may' get a replacement under warranty ..
Click to expand...
Click to collapse
Thanks for the advise.... But is there a way I can myself unbrick the moblie?
bango7886 said:
Thanks for the advise.... But is there a way I can myself unbrick the moblie?
Click to expand...
Click to collapse
No ... i don't think so ... SInce you can't even turn on the phone ... the answer is No ... sorry ...
works condya
Thanks dude.... Tried to flash it once again.... 100% success...
Hhahahaha epic! i fixed it
I used the battery of my galaxy s2 (which has 1 more connection pin and a is lot larger) with some super technical skills and managed to flash a new rom and it worked!

R7 PlusM doesn't boot properly anymore

Hi there, I have tried to find a solution today for this issue but I can't find anything useful anywhere .
Last night I received another update via OTA 151115 and proceed to install it as the earlier ones didn't work. Surprisingly this one worked and after restart my phone didn't had any trace of google apps on it, try to install google play, framework and so but the phone says it's not compatible with google (Big time). Then I went to the bootloader to perform a wipe/erase everything and here's when the problem began, it was stuck in the screen that says optimising applications (the one before starting the setup) and after half an hour unattended the phone restart itself one after another, like in a loop.... From this point on, I haven't been able to power on the device anymore.
It was bought through a third party seller from China, already contacted them and waiting for an answer...
Any clue about what can I do to use my phone again?
Update: I can see the oppo logo after pressing volume up plus power buttons for around 15 seconds but it shows for less than a second the screen it appears when it's updating the software and then it switches itself off... Is this a sign of possible recovery in some way?
just downloaded the last 151115 official update from the oppo community forum but I've got a problem. I can not enter the fasboot or recovery mode because the phone is like trying to install something and it constantly switches itself off... The day this happened, I had two files in my root directory, one was the few update and the other was a full Google thing in the same format than the fw file, I'm afraid I selected the wrong one and that's why the phone went crazy. I guess if there's some way to cancel that attempt to update the wrong file or reset that thing in some way, I'd be able to start over but I can't find anything grgrgr
By the way, the last ota update allowed google maps to work flawlessly and also Instagram, two of my biggest concerns with the phone
I'm even trying to contact oppo service to send the thing and sort it out that way xx
Cheers
Pedro
I've just contacted Oppo Customer Service in Europe to see if they have any solution for my problem as I can't make this thing to start and the battery also doesn't seems to be charging though... No response for the moment, just an automated one confirming the reception of my enquiry
Should I start thinking about my lovely new phone as my new paper weight?
peterpanda1970 said:
I've just contacted Oppo Customer Service in Europe to see if they have any solution for my problem as I can't make this thing to start and the battery also doesn't seems to be charging though... No response for the moment, just an automated one confirming the reception of my enquiry
Should I start thinking about my lovely new phone as my new paper weight?
Click to expand...
Click to collapse
No, no you have a chance to save your phone. If you have to R7 plus M Oppo Chinese version, I can help you. I also had this problem, but he was able to solve it. My Skype: ed_mobstyle.
Hi mate, thanks for the answers. Yes it is the China mobile version "M" I don't have Skype I'm afraid grgrgr
Cheers
Pedro
I was able to fix this problem fairly easily.
First I entered recovery (press Power + Volume Down when the phone is booting up)
Then from the device menu I installed a ROM, you want to download the version you last used. (MAKE SURE IT IS FOR THE OPPO R7 PLUS M)
After installing the stock rom, it will go into installation and have you set up your phone.
After you installed the ROM, download OPPO tools v 1.6.5
Open Oppo Tools and root your phone this will take a few minutes.
After you have rooted your device open Oppo Tools again and select Unlock Google Mobile Services (this too me two weeks to figure out).
Let the phone restart, after it is finished, you should have basic google functionalities (Playstore and Frameworks).
Now since you are rooted, it means that your phone will not download any further OTAs and you will have to install them as ROMs, you can do so by repeating the above process, but I'm not sure of the functionality of Oppo Tools past the most current version.
I cant post links to provide you to where the ROM files and Oppo Tools are at this moment
The roms will be located on the "[ROM][STOCK] Official R7 Plus Roms | R7Plus, R7PlusF, R7PlusM [15 Sep 2015]" of Oppo Fourms
The Oppo Tools will be located when you google "OPPO Tools apk" on your computer and it will take you to the thai version of Oppo Fourms follow the link there to download the apk
Hi mate, thanks for your answer but my problems is that I can't enter the recovery mode cause the phone try to install something and then it switches itself off
I've tried to connect the phone to my laptops and sometimes they recognised it as Qhsub something and I can't find anywhere this driver. Then all the softwares I've got ask me for a scatter file which I don't have....
Also trying to contact support from the brand. For now just send them my data and the phone's imei and now waiting for the magic response... They are excessively slow in their answers!
Thanks so much anyway
Cheers
Pedro
hi mate I guess un the malysia oppo community you can fin the drivers and every things about oppo r7pkusM
sollitair said:
hi mate I guess un the malysia oppo community you can fin the drivers and every things about oppo r7pkusM
Click to expand...
Click to collapse
Just checked in and didn't find anything but the bloody oppotools lol.
Cheers mate!
so please if you still with the same problem let me know I'll try to write an email directly to you with all
links you need for it.
[email protected]
best of luck
Still at the same point mate! The thing keeps on trying to install something and switches itself off. My windows laptop runs on win10, the other is a Mac so I guess useless for this matters... The battery runs out faster than ever even being off. Disaster! Lol
I would really appreciate your help
Cheers
Pedro
This is a video I made to explain how this thing try to boot and it never makes it further...
https://www.youtube.com/watch?v=2LNiWODlUd0
Hi matr
believe me I have just coming back from oppo office and I show them your video and what they said '' you have to change it with the guarantee you have''.
it clear now for me and I state that I had the same problem all what I did is installing the oppo drivers on my PC boot on fastboot mode give some commands to unlock it and tjen I flash the original recovery from oppo then tje coloros was installed and updated as well before flashi'g again TRWP recovery and right now I''m writing to you from my r7plusm it's work smothly rooted with the same original oppo rom coloros.
I hope that your just missing something and let me know to to follow you step by step on this.
cheers P
sollitair said:
Hi matr
believe me I have just coming back from oppo office and I show them your video and what they said '' you have to change it with the guarantee you have''.
it clear now for me and I state that I had the same problem all what I did is installing the oppo drivers on my PC boot on fastboot mode give some commands to unlock it and tjen I flash the original recovery from oppo then tje coloros was installed and updated as well before flashi'g again TRWP recovery and right now I''m writing to you from my r7plusm it's work smothly rooted with the same original oppo rom coloros.
I hope that your just missing something and let me know to to follow you step by step on this.
cheers P
Click to expand...
Click to collapse
Hi mate, my problem is that my computer detects the phone as qhsusb_bulk and I've tried every single file I found with that name and nothing changes, well, the device name from unknown to com1, com2... up to com13 I have seen.... Other thing is that I can't enter the fastboot mode or recovery mode neither. I wish I had an oppo service near home but I live in Uk, now I'm trying to get service from oppostyle and waiting for an answer. To be honest with you, I'm really annoyed with all this, never had a problem with bricked androids or iphones until I met this "guy" lol
Cheers
Pedro
I'm really sorry dude I hope I can help you as I did for mine it was quit simple with the same driver problems,so try to uninstall all drivers you have for oppo and install the one I shared with you taken from my ohone directly that the only way you can give any commands to your phone to switch to fastboot mode even if the problem still present
when I try to install the driver on my win10 laptop it says this...
Using an old win7 laptop I managed to install the bloody Qhsub driver and now the phone appears in the com ports under the name Qualcomm HS-USB QDLoader 9008 (COM4) does this means the phone really doesn't exist?
Update to this thread, I can't do anything until I find a proper driver for the phone which actually is recognised by my laptop as Qhsub_bulk and I can't bloody find this anywhere at least for making 6795 processors or specifically for this model...
Any clue?
peterpanda1970 said:
Update to this thread, I can't do anything until I find a proper driver for the phone which actually is recognised by my laptop as Qhsub_bulk and I can't bloody find this anywhere at least for making 6795 processors or specifically for this model...
Any clue?
Click to expand...
Click to collapse
No need panic ))) I've sent you a set for recovery your device )))) Good luck
ed_mobstyle said:
No need panic ))) I've sent you a set for recovery your device )))) Good luck
Click to expand...
Click to collapse
Hi mate, thanks for your help. Tried to open the link you sent me but it says it's not available anymore grgrgr
Cheers
Pedro
peterpanda1970 said:
Hi mate, thanks for your help. Tried to open the link you sent me but it says it's not available anymore grgrgr
Cheers
Pedro
Click to expand...
Click to collapse
Hi, please check now

[ROM][6.0] CyanogenMod 13.0 [ALPHA] [HARD BRICK FIX]

[ROM][6.0] CyanogenMod 13.0 [ALPHA] have bricked some XPERIA L devices. So this thread is to help those people who are facing the problem. I came across some methods to recover their Xperia L. Although, I am not sure it will work because I haven't tried it myself (Can't risk bricking my phone on purpose just to check this method which may or may not fix it ). But please go ahead and try it.
It's better to try than to cry!
Click to expand...
Click to collapse
METHOD 1
Remove Battery, press power button for around 10-12 seconds..then press and hold volume up, a Insert the battery , fash tft file using flastool
Source: https://www.youtube.com/watch?v=lycyxdkNlz8 (Comment by KãyRá S.s)
METHOD 2
Disconnect the phone from PC if connected Remove the battery Press and hold the power button for 15-20 seconds Re-insert battery Flash latest FW using flashtool..
Source: https://www.youtube.com/watch?v=lycyxdkNlz8 (Comment by BEST FULLAPPS)
If anyone know a better method or a suggestion please post it...
you can't fix in any way broken partition table, only with jtag and similiar, this all should work for semibricked devices...
Hard Brick......
Flashing_Expert said:
you can't fix in any way broken partition table, only with jtag and similiar, this all should work for semibricked devices...
Click to expand...
Click to collapse
Sir plz help me out i have bricked my device. When i connect it to a charger it shows a greenish light for a second and the it fades out. No detection my pc. It says that it is an unidentified device. actually it happened after i flashed cm13 by olivier. It booted up fine. I then just shut it down to install gapps. But it didnt respond any more.
udaykapoor97 said:
Sir plz help me out i have bricked my device. When i connect it to a charger it shows a greenish light for a second and the it fades out. No detection my pc. It says that it is an unidentified device. actually it happened after i flashed cm13 by olivier. It booted up fine. I then just shut it down to install gapps. But it didnt respond any more.
Click to expand...
Click to collapse
You had to install the latest package.. if u didn't only then u would've got hard bricked... cm13 is now tested by too many people and it runs without bugs.. so it may be the fault with the version of cm13 you used..
udaykapoor97 said:
Sir plz help me out i have bricked my device. When i connect it to a charger it shows a greenish light for a second and the it fades out. No detection my pc. It says that it is an unidentified device. actually it happened after i flashed cm13 by olivier. It booted up fine. I then just shut it down to install gapps. But it didnt respond any more.
Click to expand...
Click to collapse
oh damn another one guy same happened to me with same rom ...
sorry but this means your phone is dead like mine, your bootloader is corrupted so device is unable to boot to kernel nor to system
no flashmode or fastboot mode, you can see it only in device manager (with proper drivers) as qhusb dload 9008
sadly we don't have proper files for QPST software so nobody unbricked his XL to this date
only chance is motherboard replacement
udaykapoor97 said:
Sir plz help me out i have bricked my device. When i connect it to a charger it shows a greenish light for a second and the it fades out. No detection my pc. It says that it is an unidentified device. actually it happened after i flashed cm13 by olivier. It booted up fine. I then just shut it down to install gapps. But it didnt respond any more.
Click to expand...
Click to collapse
btw you had 2 partitions on your microsd? I need to know...
Hi, is it possible to have some more information on the situations with cm13 that have caused a hard-brick? I understood that that the features such as link2sd and app2sd are potentially dangerous? Is this understanding correct? If yes, could you please explain why and under which circumstances this could create troubles?
Do you have any further suggestions on what to avoid?
Many thanks in advance for your expert advice.
I wanted to try cm13 on my spare xperia l, but would like to avoid a hard brick...
Cheers,
Hennng
xleng said:
Hi, is it possible to have some more information on the situations with cm13 that have caused a hard-brick? I understood that that the features such as link2sd and app2sd are potentially dangerous? Is this understanding correct? If yes, could you please explain why and under which circumstances this could create troubles?
Do you have any further suggestions on what to avoid?
Many thanks in advance for your expert advice.
I wanted to try cm13 on my spare xperia l, but would like to avoid a hard brick...
Cheers,
Hennng
Click to expand...
Click to collapse
Its already been fixed in newer builds, also, the developer has stopped the development. But you can surely use CM13 Based ROMs since they also have better editing options.
I really cant wait for cm13. It really pleases me If rom get fixes

serious problem with xiaomi mi4w 3g version

hello to forum
i have xiaomi mi4w 3g version with mui rom 7(5.12.11 beta)
everythink is fine but in sometimes on a day the mobile just freeze and force power off and i cant even power on it again(even if get to power nothink of light has come just like dead phone)
except i remove the battery(so to remove battery i need to open it and all screws remove to unplug the battery)
i already did hard reset
i already change to custom rom
i already make everythink is possible but nothink work
so please any idea for help me with this is appreciated
thank you
anestef said:
hello to forum
i have xiaomi mi4w 3g version with mui rom 7(5.12.11 beta)
everythink is fine but in sometimes on a day the mobile just freeze and force power off and i cant even power on it again(even if get to power nothink of light has come just like dead phone)
except i remove the battery(so to remove battery i need to open it and all screws remove to unplug the battery)
i already did hard reset
i already change to custom rom
i already make everythink is possible but nothink work
so please any idea for help me with this is appreciated
thank you
Click to expand...
Click to collapse
i think its time for you the device to meet the service centre.. go to Authorised service centre
just plug the mi4w to computer
If computer shows too many new drive that means your GPT partition got corrupted
then try this tutorial
http://forum.xda-developers.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927

Categories

Resources