Sim-card not found after flashing PhilZ Touch custom recovery - Galaxy Note II Q&A, Help & Troubleshooting

Hello everyone,
i've flashed the newest version of the PhilZ Touch custom recovery and now my note 2 can't find my sim-card...
Custom recovery found @ http://forum.xda-developers.com/showthread.php?t=2028103
I flashed it from version 4.35 to 4.63 so the custom recovery was installed and working before.
After reboot i didn't had the possibility to unlock my sim-card (entering PIN-code).
Now i have no network connection at al (obviously)
Everything else is (so far) working...
I'm using the rooted stock rom
greetings,
p.s. i would reply in the specific topic but i can't yet.

Try another recovery or phone.
Sent from my GT-N7100 using xda app-developers app

Stupid question?
UtkarshGupta said:
Try another recovery or phone.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Is it, in any way, possible that a sim-card gets affected when you flash a custom rom?
I'm thinking about this question because my sim-card broke just after flashing without touching it...
(no need to touch your sim-card to flash, but i haven't done anything else where i would have needed to remove/change it)
Its probably just coincidence but it's strange that it just happend after flashing.
(sorry if my english is hard to understand )
greetings from Belgium

ye same problem here, tell me when u found out to get it back so I can use that method =p

I've had no problems after upgrading the recovery.
I would suggest you post in PhilZ's thread. He is very active and will help find out what happened.

Unexist6969 said:
ye same problem here, tell me when u found out to get it back so I can use that method =p
Click to expand...
Click to collapse
Well, i've changed the sim-card (have one for data only...) and that one worked fine...
I tried it in another phone too but i was thinking that it wasn't working because i used an adapter to have a normal sim-card and not the micro-sim format so i did the thing mentioned above...
I decided to sent my parents to a Belgacom support center (one of belgians telecom operators) to ask a new one.
I need to work this weekend and i didn't had the opportunity to go myself, it's stupid to walk with a phone without the ability to call/send messages :silly:...
I just inserted the sim-card my parents got from the center and i've recieved al my missed messages so i know that the new one is working fine.
This is undoubtedly strange that it's possible that a sim-card gets affected/broken when changing/updating custom recovery.
I'm "glad" (if you understand what i mean) that i'm not the only one who is having this problem.
Can someone with experience explain to me and the others what could have been the problem?
Edit: can't post yet in his thread due to too low count of messages
Edit2: i'm sorry that i haven't any easy sollution...
Yours sincerely,

what do you actually get from philz? i can't even feel a butterfly flies in my tummy..
in my opinion, the perseus one is the best choise.

rymote said:
what do you actually get from philz? i can't even feel a butterfly flies in my tummy..
in my opinion, the perseus one is the best choise.
Click to expand...
Click to collapse
Nothing special?
I don't know why you are asuming that i need to get something from it...
I'm just saying in this thread that there has been a problem with the sim-card after flashing this custom recovery .
So i only wanted to say "Hey, after performing this, that went wrong, how to find a solution"
This has nothing to do with liking a custom recovery.
I'm happy for you that you like the perseus one but this one was aproved by someone to solve another problem (and worked)...
I can't understand the point of your reply in this topic, it has nothing to do with not finding/reading the sim-card
p.s.: my wording may seem wrong but well meaning, my english is not perfect since it is not my native language

ahhh .... the device I was rooting was simlocked, he didn't say anything ffs.. that's why
@op try flashing a stock rom(remove sim card), then factory reset in recovery, then flash philz, then flash w/e u want

Unexist6969 said:
ahhh .... the device I was rooting was simlocked, he didn't say anything ffs.. that's why
@op try flashing a stock rom(remove sim card), then factory reset in recovery, then flash philz, then flash w/e u want
Click to expand...
Click to collapse
thanks for your reply, i'll do it when i have some time :good:

Unexist6969 said:
ye same problem here, tell me when u found out to get it back so I can use that method =p
Click to expand...
Click to collapse
same problem just flashed philz and not showing network plz help....

Related

[DEV][WIP] Recovery of IMEI/Baseband of Sprint Galaxy Note 2

Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Me too. ..
Sent from my MASSIVE Galaxy Note® II...*
mackentosh said:
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
but how did it happened ? can u please explain steps what u did that wiped yr imei?
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
i got the same problem with tmobile ver the problem is the partition i did tried to repartition in odin with gt-7100 pit file it did not work
can you see your storge and see your internal sd space
sorry for my english
An fyi when u get ur baseband back 3g will not work. I was able to get mine all back and working but I was always on 1x. T3 hit me up in gtalk.
Sent from my SPH-L900 using Tapatalk 2
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
You care to clarify which ROM you flashed in particular caused this to happen so that we don't replicate your problem? I want to assume it's your own ROM but just want to make sure.
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Click to expand...
Click to collapse
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
i did flash the s3 rom and after that i lost everythng my phone i need to know how to restor the orgenal sd card cuz im looking with rootexplore it sdcard0
when i go to setting storge it only show 266mb used and 0.00 avilabel any body can help please
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Which ROM had the "In Call Recorder"? I've been looking for a replacement to that functionality after dropping HTC/ Qualcomm with the 2WCR patch on the kernel. ..
Sent from my SPH-L900 using xda app-developers app
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
it didnt actually wipe our imei. it repartitioned the phone.
t3project said:
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
Click to expand...
Click to collapse
Good to know it wasn't released here publicly. Happy to hear you found a solution to the problem too.
dc13 said:
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Try this.
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
t3project said:
it wasnt a rogue rom. It was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. I'll post it up in a few
Click to expand...
Click to collapse
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
mccurt29 said:
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
Click to expand...
Click to collapse
simple, wasnt it? lol..................
mackentosh said:
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Was it mine? I can tell you that if any of the previous stuff happened to you, it wasn't from the ROM. Could have been a bad download, coinsidence, etc. The ROM flash wouldn't have caused it.
Sent from my SPH-L900 using Tapatalk 2

N7105 No Signal and IMEI after Flashing custom ROM

hi everyone.. i just bought Samsung Galaxy Note II 4G on first december, from Optus Australia..
and last night i try to root, and flashing Omega v7.3 Rom from N7100, it is work well but the IMEI and Signal is gone, and also the S-pen is not working..
and i try use N7105 custom rom http://forum.xda-developers.com/showthread.php?t=1985200
and also my signal is still not detected, but my S-Pen is working back..
somebody please help me...
how to fix my signal problem
benatis said:
and flashing Omega v7.3 Rom from N7100
Click to expand...
Click to collapse
Why in first case did you flash a ROm which isn't intended to be for your device?
Well you killed your EFS partition (bricked)
I hope you mad a EFS backup BEFORE you flashed. So you can restore it and all will be fine.
You could try the Stock Firmware via Mobile Odin if it fixes your EFS problem. No Guarantee here, sometimes it dsoes work and sometimes not.
Good luck to you
Higgins12 said:
Why in first case did you flash a ROm which isn't intended to be for your device?
Well you killed your EFS partition (bricked)
I hope you mad a EFS backup BEFORE you flashed. So you can restore it and all will be fine.
You could try the Stock Firmware via Mobile Odin if it fixes your EFS problem. No Guarantee here, sometimes it dsoes work and sometimes not.
Good luck to you
Click to expand...
Click to collapse
hmm.. i never used Samsung device before.. this is my first Samsung device i have ever..
different with my old HTC devices..
i will try ODIN now... use Stock ROM....
-----
and also, i have tried to wipe data from CWM, why my Note2 device still can boot?
i mean, like not wiped the data completely
benatis said:
hmm.. i never used Samsung deviced before.. this is my first Samsung device i have ever..
different with my HTC devices
Click to expand...
Click to collapse
I believe the reason you are experiencing this issue is because this new firmware you flashed doesn't contain a custom radio and the n7100 firmware did. You will need to find a n7105 radio, flash that through CWM or TWRP and you should be back in business mate.
chrisaw said:
I believe the reason you are experiencing this issue is because this new firmware you flashed doesn't contain a custom radio and the n7100 firmware did. You will need to find a n7105 radio, flash that through CWM or TWRP and you should be back in business mate.
Click to expand...
Click to collapse
where i can download n7105 radio ???
and how to flash the radio?
where i can download the stock Radio, Firmware, and rom of N7105 ???
i Have tried Odin, and flash Stock rom... but i dont know how to wipe data and chache from odin..
i just flash it..
and now, my Signal is appear... lol...
thanks for everyone...
Would be glad to help you but you seem to have skipped the first rule : read, read, read before you do anything else. You even admitted that this is your first Samsung device, so why did u assume that everything should have been htc like ?
Anyhow, you can try to flash the newest 4.1.2 update for the 7105, even though I fear that your problem is your efs folder, and since this is unique for each device, no flashing any rom will put it back in place.
http://forum.xda-developers.com/showthread.php?t=2027586
Good luck,
P_
pakalrtb said:
Would be glad to help you but you seem to have skipped the first rule : read, read, read before you do anything else. You even admitted that this is your first Samsung device, so why did u assume that everything should have been htc like ?
Anyhow, you can try to flash the newest 4.1.2 update for the 7105, even though I fear that your problem is your efs folder, and since this is unique for each device, no flashing any rom will put it back in place.
http://forum.xda-developers.com/showthread.php?t=2027586
Good luck,
P_
Click to expand...
Click to collapse
yah.. i have flash that ROM just now..
but, why my signal is verry in poor level? only showing 2 bar?
im sorry, im not experienced with samsung devices
Since you said that the phone is from Australia and Optus you may want to flash its original firmware back in place :
http://www.sammobile.com/firmware/?page=3&model=GT-N7105&pcode=OPS&os=1&type=1#firmware
If you do not use the phone in Australia you may want to find a firmware (if available) for your device/geographical region.
P_
benatis said:
i Have tried Odin, and flash Stock rom... but i dont know how to wipe data and chache from odin..
i just flash it..
and now, my Signal is appear... lol...
thanks for everyone...
Click to expand...
Click to collapse
I am facing the same problem you had before, however when i try to Odin the stock 4.1.1 firmware back to the phone, it stops at the Samsung logo when restarting. I have to force back to recovery mode to flash the omega back to have it start again. Can you please tell me the steps you did on putting back to stock firmware? thanks
If you haven't yet reflashed the EFS partition (don't do that, ever ! unless you have a good reundant set of backups), you actually don't need to reflash to stock firmware at all (and I doubt that it'd do any good anyways. It just puts back a generic EFS with the files set at default values, but certainly can't put back the data you had in your own device's EFS, this is unique to each phone).
Just head on over to the Galaxy S2 forums and look for a thread called "Restore your IMEI in 9 steps" (something like that. There's actually quite a number of threads describing the same procedure, you can find them by searching "samsung restore imei" in all forums, works just as well).
I had the same problem the other day (and no backup of course, silly and impatient me... ), it worked like a charm..
It's topics like this that i know that People Will get Hurt on. Come on, read and study before doing anything on a smartphone. There's a reason why android doesn't come with administrator rights from factory.
Sent from my GT-N7100 using Tapatalk 2

HTC One X G-sensors not working all of a sudden!

Hey guys... My friend bought an HTC One X second hand. It is rooted with what seems to be stock 4.0.3 Sense 4.0. The phone is also S-OFF and everything.. I will post pictures of it.
So here's the deal:
My friend was watching a movie but suddenly he felt as if the screen wasn't rotating... Now (According to AndroSensor App) the magnetic field, orientation, gyroscope, accelerometer etc... In short.. All of the GRAVITY SENSORS and the orientation sensors aren't working.. They are DETECTED by the app but say "Waiting for event"
tried hard resetting and everything. I have put many Custom ROMs in phones before. So i can flash ROMs etc if i have to
I have attached the pictures about everything and need help.. Alot appreciated thanks.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I noticed i forgot to upload all the attachments.. I also have noticed that people have this problem on Sense 5. This one is sense 4 o.o
Can anyone help me in this. Also the phone has its bootloader LOCKED. I have to unlock it now?
Sent from my Nexus
WasifSal said:
View attachment 2362068I noticed i forgot to upload all the attachments.. I also have noticed that people have this problem on Sense 5. This one is sense 4 o.o
Can anyone help me in this. Also the phone has its bootloader LOCKED. I have to unlock it now?
Sent from my Nexus
Click to expand...
Click to collapse
take it to the shop, it is under warranty till may 2014
nogotaclue said:
take it to the shop, it is under warranty till may 2014
Click to expand...
Click to collapse
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
My question is that "CAN I FLASH A SENSE 5 (4.2.2) ROM ON THIS BAD BOY BY JUST FLASHING VIA RECOVERY?"
I'll then check the other powering off and stuff i read till i get my hands on my frnd's HOX. Cuz im a bit busy waiting for the Nexus 5 launch o.o
WasifSal said:
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
My question is that "CAN I FLASH A SENSE 5 (4.2.2) ROM ON THIS BAD BOY BY JUST FLASHING VIA RECOVERY?"
I'll then check the other powering off and stuff i read till i get my hands on my frnd's HOX. Cuz im a bit busy waiting for the Nexus 5 launch o.o
Click to expand...
Click to collapse
you should update it first, that is a very old version, you should have updates available. as it is s-off you can flash anything you want but I think you will need to update the hboot first, once that is done you have a lot of options available to you
nogotaclue said:
you should update it first, that is a very old version, you should have updates available. as it is s-off you can flash anything you want but I think you will need to update the hboot first, once that is done you have a lot of options available to you
Click to expand...
Click to collapse
Ermm... So i just update it via OTA? or flash a ROM of Sense 5 or. Something?
WasifSal said:
Ermm... So i just update it via OTA? or flash a ROM of Sense 5 or. Something?
Click to expand...
Click to collapse
well with such a low version there must be quite a few OTA's waiting
nogotaclue said:
well with such a low version there must be quite a few OTA's waiting
Click to expand...
Click to collapse
Yeah you might be right... So what you are suggesting is I do a ROM flashing? Seeing the phone is already s-offed and everything
Anyways can you please list me a step by step procedure? Seeing this is my friend's phone so not doing this on my own :x
Bump?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Go to settings and check for an update. What we all recommend is that you send it to HTC, all untampered One Xs should still be in warranty, so send it to them, if it can't be fixed they'll send you a One X or a One X+, or sometimes they could send a HTC One if you're lucky :/
Sent from my HTC One X using Tapatalk
humzaahmed155 said:
Go to settings and check for an update. What we all recommend is that you send it to HTC, all untampered One Xs should still be in warranty, so send it to them, if it can't be fixed they'll send you a One X or a One X+, or sometimes they could send a HTC One if you're lucky :/
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
Nay i live in Pakistan :/ if this was in warranty even they wouldn't have accepted it :/ or requested a cost for it... Either way thanks for your reply... So doing an OTA update won't create problems on an S-OFFed device right?
WasifSal said:
Nay i live in Pakistan :/ if this was in warranty even they wouldn't have accepted it :/ or requested a cost for it... Either way thanks for your reply... So doing an OTA update won't create problems on an S-OFFed device right?
Click to expand...
Click to collapse
OTA need relocked or locked device , stock recovery and stock ROM
and if you still have a problem with your g-sensor , check my signature , there is an alternative way to fix it
HTC Venom said:
OTA need relocked or locked device , stock recovery and stock ROM
and if you still have a problem with your g-sensor , check my signature , there is an alternative way to fix it
Click to expand...
Click to collapse
bootloader doesn't need to be locked or relocked for ota, only stock rom, stock boot.img and stock recovery
nogotaclue said:
bootloader doesn't need to be locked or relocked for ota, only stock rom, stock boot.img and stock recovery
Click to expand...
Click to collapse
Oh alright! Btw if i flash a recovery via fastboot, then i am able to flash (say) a custom ROM Sense 5, 4.2.2 right? Just asking for it i will update it by OTA (provided there isnt a custom recovery... Since i didnt check that) :/
HTC Venom said:
OTA need relocked or locked device , stock recovery and stock ROM
and if you still have a problem with your g-sensor , check my signature , there is an alternative way to fix it
Click to expand...
Click to collapse
Oh i'll get right on it when i get my hands on the device can i request you to stay put to this thread? Cuz i will report back here
if you flash a custom recovery you can do anything you want, ie flash a rom, sense or no sense, or flash back to stock and because you are s-off you can even change your cid to install an update from a different region.
this can go on and on and people are starting to repeat themselves and you have had all the information you need to move forward. so what you need to do, as you say you cannot fix under warranty, is :- let the phone update via ota, this will update everything including the rom, the version of sense and the hboot. then once it is finished with all ota's available you can install a custom recovery( I recommend philz touch recovery or the latest twrp) and then you can flash all the rom's or mods you like.
and if you find you still have a problem with sensors check @HTC Venom signature for a possible solution
nogotaclue said:
if you flash a custom recovery you can do anything you want, ie flash a rom, sense or no sense, or flash back to stock and because you are s-off you can even change your cid to install an update from a different region.
this can go on and on and people are starting to repeat themselves and you have had all the information you need to move forward. so what you need to do, as you say you cannot fix under warranty, is :- let the phone update via ota, this will update everything including the rom, the version of sense and the hboot. then once it is finished with all ota's available you can install a custom recovery( I recommend philz touch recovery or the latest twrp) and then you can flash all the rom's or mods you like.
and if you find you still have a problem with sensors check @HTC Venom signature for a possible solution
Click to expand...
Click to collapse
Woah thanks for that reply man! Keep in touch bro i'll update it with the details when my friend lends me his One X once again thanks!
same issue
WasifSal said:
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
same thing happened to my one x also, bought it from olx, and it was new (somewhat)...g sensor not working...i did hard reset...and it started working, but again after few days its not working, and now i have done even factory reset, but not working
what should i do
Click to expand...
Click to collapse
bilalzahid29 said:
WasifSal said:
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
same thing happened to my one x also, bought it from olx, and it was new (somewhat)...g sensor not working...i did hard reset...and it started working, but again after few days its not working, and now i have done even factory reset, but not working
what should i do
Click to expand...
Click to collapse
Try to do the hard reset after couple of days. Once you feel your device is warm enough. Chances to get them back gets better with time
Sent from my HTC Sensation Z715e using xda app-developers app
Click to expand...
Click to collapse
i got them back except for temperature sensor....althought i did this thing several times, but once it worked out...i restarted the phone by long pressing the power button, even after the TURN OFF menu appears...on the start screen pressed volume down button to go in safe mode, all sensors started working, then i restarted mobile to come in normal mode.
working fine uptil now, i dont have restarted or powered off after that. so dont know if they will keep working after restart or again same problem will occur
all the people having same problem, just keep on trying restarts, safe mode, factory reset etc etc most probably they will start working. its just hit and trial

[Q] Can one kill his phone forever?(what mistake mostly makes this)

Hi guys
i want to root and install custom roms on my note 2 . i just want to know what are the most common problem comes that make your phone completely dead!
is it even possible that one can kill his phone completely that it can never be recovered?
Bumping the thread
why no one answers?
nicholes said:
Hi guys
i want to root and install custom roms on my note 2 . i just want to know what are the most common problem comes that make your phone completely dead!
is it even possible that one can kill his phone completely that it can never be recovered?
Click to expand...
Click to collapse
If you flashed wrong custom ROM via recovery won't be a problem, just reflash any other compatible stock ROM then your problem will be fixed. BUT if you flashed wrong stock ROM via ODIN and you will end up brick. You need a JTAG to revive your phone.
Its pretty hard to destroy your phone completely just by flashing another rom.
Flashing bootloader through recovery is a bad idea.
Repartitioning your device in odin, with files not specific to your device, is a bad idea
Dramatic over-clocking with increased voltages, can be a bad idea
Dropping your device is a bad idea.
Bumping a thread without waiting more than 24 hours, is a bad idea
EmptyArea said:
Flashing bootloader through recovery is a bad idea.
Repartitioning your device in odin, with files not specific to your device, is a bad idea
Dramatic over-clocking with increased voltages, can be a bad idea
Dropping your device is a bad idea.
Bumping a thread without waiting more than 24 hours, is a bad idea
Click to expand...
Click to collapse
i understood sir:good:
soralz said:
If you flashed wrong custom ROM via recovery won't be a problem, just reflash any other compatible stock ROM then your problem will be fixed. BUT if you flashed wrong stock ROM via ODIN and you will end up brick. You need a JTAG to revive your phone.
Click to expand...
Click to collapse
and what is JTAG here?please explain
nicholes said:
i understood sir:good:
and what is JTAG here?please explain
Click to expand...
Click to collapse
JTAG = Joint Test Action Group.
http://en.m.wikipedia.org/wiki/Joint_Test_Action_Group
Sent from my GT-N7100 using XDA Premium 4 mobile app

Question My phone is completely effed up now....

Locked my boatloader by mistake now it won't boots I need help ASAP.... I'm losing my mind over here I need someone to help me please for the love of God somebody... Just bought this phone for like $1,000 and now I'm looking at a ****ing brick......
no worries, you technically cant brick it that easily.
Check the MSM thread for your exact model and follow the steps get it back and running again.
^ Yeah an MSM flash will have you right as rain. Just wondering how the you locked the bootloader "by mistake" that seems like a difficult mistake to make.
was trying to restore and forgot how op works lol...i got it fixed now. while your here, how can i flash twrp and flash a rom? having issues with this now..
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
So I'm not sure about YOUR phone, if you have a recovery partition you can just flash recovery, if you don't have a recovery partition then you need to fastboot boot twrp first. And there are a few ways to flash a rom, my recommendation would be Fastboot Enhance I personally haven't tried it yet but it seems to work pretty good and even though it's in the 8T category it should work fine. Now one thing that is noteworthy with Fastboot enhance though is that it flashes the current slot instead of the inactive slot.
this.guy.lol said:
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
Click to expand...
Click to collapse
Didn't reply accidently, not the first time I've done that. Read my previous post.
Brandon.Bissonnette said:
Didn't reply accidently, not the first time I've done that. Read my previous post.
Click to expand...
Click to collapse
thx man

Categories

Resources