For the most up-to-date information please see THIS POST HERE, as I will no longer be updating this thread. It's not necessary to have this thread in two different places.
If a moderator feels the need please delete this thread. I have re-posted this in the Development section of the Droid Incredible 2 form!
Thanks, and happy downgrading! =D
will this cause a continuous bootloop on sense roms?
Bradh024 said:
will this cause a continuous bootloop on sense roms?
Click to expand...
Click to collapse
In some cases yes. On my phone I got a continuous bootloop after downgrading, however it was easily fixed by pushing the clock work mod recovery and installing an AOSP rom (cm9 for me). On the other hand, while downgrading my gf's phone i did not experience any bootloops. Not sure whats causing them at this time but i'll be looking into it.
Also, if you want to stay on a sense rom you can go into the factory recovery menu and wipe user data/cache (essentially a factory reset, but will not lose s-off or root) and the bootloops should cease until you turn off the phone.
cool, i'm gonna give this a shot. I have 2 inc 2's to send back. so if i screw one up, oh well.
Bradh024 said:
cool, i'm gonna give this a shot. I have 2 inc 2's to send back. so if i screw one up, oh well.
Click to expand...
Click to collapse
haha cool let me know how it goes:good:
Everything worked good. I'm on the sense4a rom, and trying to figure out how to put it into a bootloop. Could you please tell me the trick? I gotta figure it out before I give this to my wife, so it doesnt start ****ing up on her. So far so good though, I've rebooted and everything seems fine.
so if i understand you correctly your running the sense4a rom and experiencing no bootloops, but you want it to bootloop?
dets34 said:
so if i understand you correctly your running the sense4a rom and experiencing no bootloops, but you want it to bootloop?
Click to expand...
Click to collapse
HAHA, Yes and no. I just want to make sure I know what causes the bootloop, and be sure that it wont when I hand the phone over to my wife.
Bradh024 said:
HAHA, Yes and no. I just want to make sure I know what causes the bootloop, and be sure that it wont when I hand the phone over to my wife.
Click to expand...
Click to collapse
lol okay. well mainly the boot loops are just caused from the downgrading itself. Maybe try pulling the battery and restarting the phone, boot into recovery, bootloader, ect. Not sure what actually triggers the bootloops besides the sense roms themselves but thats really cool that the sens4a rom doesnt seem to be causing them ill have to look into that.
My guess is the RIL code written by the devs here for the Sense 4 ROMs aren't plagued by the boot loop issues.
Sent from my ADR6425LVW using Tapatalk 2
my guess is as good as yours
if u r on the new 6.xxx software, cna u pull system/lib/modules folder before downgrading.--it's sow e can use the new kernel.
andybones said:
if u r on the new 6.xxx software, cna u pull system/lib/modules folder before downgrading.--it's sow e can use the new kernel.
Click to expand...
Click to collapse
I am no longer on the 6.01 software but i will edit the OP to ask for someone to do so.
I just upgraded my old phone and will be getting a droid by the end of the week. If no one has done it, I'd be happy to do so, provided someone tells me how to pull the system/lib/modules folder.
Please help, been trying this for so long, everything goes smooth with all the commands and everything but when at the very end i get the error message (FAILED: 12 signature verify fail). Or something to that extent, I went back up to to OP Post and researched some more and I seen something about needing to have an unlocked bootloader and then I need to lock it back with (fastboot oem lock). So do i need to use htcdev to unlock bootloader first then try this or whay. Pleeasee
Hey dets34, I followed your process to downgrade and also got the boot loops; always rebooting at the lock screen. I am using CondemnedSoul's StockOTA 605.05. I was about to give up and use CM72 when I noticed the radio version was .0622 (an older version?) So I flashed the .0312 radio, and guess what? No more boot loops!
Has anyone with this boot loops problem tried flashing another radio? Would the radio version be the main problem?
Sent from my ADR6350 using Tapatalk 2
MIVLives said:
Hey dets34, I followed your process to downgrade and also got the boot loops; always rebooting at the lock screen. I am using CondemnedSoul's StockOTA 605.05. I was about to give up and use CM72 when I noticed the radio version was .0622 (an older version?) So I flashed the .0312 radio, and guess what? No more boot loops!
Has anyone with this boot loops problem tried flashing another radio? Would the radio version be the main problem?
Sent from my ADR6350 using Tapatalk 2
Click to expand...
Click to collapse
If you had that radio, you shouldn't have needed to downgrade
Sent from my Incredible 2 using Tapatalk 2
But I was originally using the stock 605.05 and s-on. I used dets34 process to down grade and gain s-off. Was there another way?
Sent from my ADR6350 using Tapatalk 2
MIVLives said:
But I was originally using the stock 605.05 and s-on. I used dets34 process to down grade and gain s-off. Was there another way?
Sent from my ADR6350 using Tapatalk 2
Click to expand...
Click to collapse
Well, never mind
Sent from my Incredible 2 using Tapatalk 2
Please help, been trying this for so long, everything goes smooth with all the commands and everything but when at the very end i get the error message (FAILED: 12 signature verify fail). Or something to that extent, I went back up to to OP Post and researched some more and I seen something about needing to have an unlocked bootloader and then I need to lock it back with (fastboot oem lock). So do i need to use htcdev to unlock bootloader first then try this or whay. Pleeasee
Related
Froyo SBF and Bootloader for Flipside MB508 AT&T USA
Bootloader: BL_917B_4G_sageemu_Consumer_replacer.zip
Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com
SBF Flash :
Android 2.2.2 ------ Blur_Version.2.159.17.MB508.ATT.en.US
SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz
Download SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz for free on Filesonic.com
WARNING: ONCE YOU FLASH THE FROYO SBF ANY ATTEMPT TO DOWNGRADE TO ECLAIR MIGHT RESULT IN A HARD BRICK !!!!!
These files are made available as a general courtesy and I assume no responsibilty for your own actions.
Thanks, I was just looking for this.. I did an update from eclair to froyo (2.1 - 2.2) and everything was fine until I did a hard reset and lost service and it kept crashing each time I would go into the settings and wireless/APN options. Wouldn't take ATT and TM sim cards.. Going to try flashing the SBF and see if this resolves it.
Edit: aaand, flashed and all fixed.
Great find, nice to have an option in case we screw something up. I wonder if there's any benefit to flashing the 2.2 sbf instead of flashing a clean 2.1 and updating to 2.2...
OH I HOPE THIS FIXES MY FREEZING ISSUE!!! Im so sick of having to take out the battery 10 or more times a day when this thing freezes, plus Im sure it does damage as hard shutting down a computer does. Ill let everyone know.
How would I flash the bootloader?
pre4speed said:
OH I HOPE THIS FIXES MY FREEZING ISSUE!!! Im so sick of having to take out the battery 10 or more times a day when this thing freezes, plus Im sure it does damage as hard shutting down a computer does. Ill let everyone know.
How would I flash the bootloader?
Click to expand...
Click to collapse
Ya know what...i'm not really sure how to flash it...or why it would be needed as opposed to a regular bootloader...
Got it flashed. Same way as you flash a rom. Like you tho, I havent a clue why. I also flashed the rom. Did NOT help with freezing, in fact seems worse now. Cant use my phone for more than 3-4 minutes before it freezes. Any idea who Id contact at Motorola to get assistance with this, because this is ridiculous. Thanks for posting this.
pre4speed said:
Got it flashed. Same way as you flash a rom. Like you tho, I havent a clue why. I also flashed the rom. Did NOT help with freezing, in fact seems worse now. Cant use my phone for more than 3-4 minutes before it freezes. Any idea who Id contact at Motorola to get assistance with this, because this is ridiculous. Thanks for posting this.
Click to expand...
Click to collapse
Hey check your SD card. My phone wasn't just freezing....it would completely just reboot and stay on the moto screen. I found out that i was my memory card. When I removed it, it worked fine and when I put it back in, it shut down automatically. Found out the problem was the 2nd partition I to use the link2sd...had to change it so that the 2nd partition was set to primary and its been working fine ever since. Not one single freeze or anything.
Dunno if that is going on with you but if it is I hope this helps
How do I set the second partition as primary? I've noticed also when anything gets linked, it goes to the first partition. First partition mem goes down, whereas second stays the same.
Sent from my MB508 using XDA App
I use something called 'EASEUS Partition Master 8.0.1 Home Edition' that I think I downloaded on google (I don't remember) but you can use it to change create and format partitions and you just gotta make sure you set it to 'primary' and not 'logical'. Try to see if you can find it and do it and let me know. If you can't find it let me know and I'll see if I can send you mine. And if you do and you still have trouble, detail to me what is going on and i'll walk you through it. It took me a lil while to figure it out.
So I could use minitool partition as well? That's the one I have. I will try that out. Phone hasn't froze today for a long time, but now that I said that, well you know. Lol I will keep you updated for sure. Thanks.
Sent from my MB508 using XDA App
Yep, that will work just fine.
JBallin4life27 said:
Ya know what...i'm not really sure how to flash it...or why it would be needed as opposed to a regular bootloader...
Click to expand...
Click to collapse
Found out why the need for the updated bootloader. Froyo does not support the Eclair version of the bootloader, so if you need to flash again, you would not be able to unless you update the bootloader. HTH
I'm honestly kinda a noob at this... never messed with anything like a bootloader. Can somebody explain to me how to do this? I'm wanting to flash back to a clean 2.2 and the post before mine sounds like that might be bad without updating boot loader first.
Also the rom, just install it with RSD?
boazjuggalo said:
I'm honestly kinda a noob at this... never messed with anything like a bootloader. Can somebody explain to me how to do this? I'm wanting to flash back to a clean 2.2 and the post before mine sounds like that might be bad without updating boot loader first.
Also the rom, just install it with RSD?
Click to expand...
Click to collapse
You will flash the bootloader the same as the froyo rom in RSD. Do the bootloader first. Then flash the froyo rom. Any questions, don't hesitate.
Sent from my MB508 using XDA App
pre4speed said:
You will flash the bootloader the same as the froyo rom in RSD. Do the bootloader first. Then flash the froyo rom. Any questions, don't hesitate.
Sent from my MB508 using XDA App
Click to expand...
Click to collapse
Phone fully on or update mode or what? For both?
USB Debugging on?
Version of RSD need to be up or still using 4.9?
I'm not 100% of this, as I don't have the MB508 as of the moment, but I believe once you flash the stock 2.2 rom or OTA you will loose root.
Someone correct me if I'm wrong, this is just intended for those who want to know info.
boazjuggalo said:
Phone fully on or update mode or what? For both?
USB Debugging on?
Version of RSD need to be up or still using 4.9?
Click to expand...
Click to collapse
When you flash you will need to go into bootloader mode. Power off phone, the use the proper key funtion (sorry don't remember what it is) to start bootloader. Then flash updated bootloader. When flashing via RSD, it doesn't matter about usb debugging because you aren't fully booted into the phone. I used version 4.9 and had no problems flashing both. Good luck.
Sent from my MB508 using XDA App
kaijura said:
I'm not 100% of this, as I don't have the MB508 as of the moment, but I believe once you flash the stock 2.2 rom or OTA you will loose root.
Someone correct me if I'm wrong, this is just intended for those who want to know info.
Click to expand...
Click to collapse
Yes this is correct. I belive this is the case anytime you flash using RSD. You can gain root again after using the most current version of superoneclick.
Sent from my MB508 using XDA App
This, along with a link to RSD Lite to install it, needs to be stickied! I was trying to upgrade a friend's Flipside following the directions on Motorola's website and it bricked the device. flashing the sbf file saved the day!
links death
any one can reupload the files?
the links are no more alive
Hi,
1. For a month ago i've learned how to root my galaxy s2, and since then i've flashed new ROM's and kernels almost every week, and thats because almost everyone told me that it was almost impossible to brick the phone.
In 2 days i will recive my new Galaxy Nexus, and i don't know if i will Root it or not, is it worth doing this to this phone?
thanks
People say it's almost impossible.. Just search the threads where people think they bricked their phones
It is EXTREMELY hard to brick the Galaxy Nexus.
And it is definitely worth rooting. There are some amazing ROMs and kernels available
Learning to root and use android from scratch, I bricked this fella at least six times, but mostly due to bad file transfers and user error.
Use a toolkit, wugfresh's makes it excessivlely easy.
Sent from my Galaxy Nexus using xda premium
I did not wipe data out before flashing, my phone could not start. I thought i bricked my phone but after went to recovery mode to wipe data, my phone worked fine.
As far as I know, the only time that you can brick this phone is when flashing bootloaders. For example, the lights go out during the 2 secs required to flash it. But the window of opportunity is so small you have to really be unlucky, and if you have UPS or do it on a laptop, that won't be a problem at all. The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
TwilightSparkle said:
I bricked this fella at least six times
Click to expand...
Click to collapse
So what you really mean, is that you didn't actually brick it once?
Lol - interesting thread...
I'll bet that I can brick one in a few minutes, so it can't be that hard... xD
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
thirtynation said:
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
Click to expand...
Click to collapse
No. As long as your volume button and power button are not broken, you can start into the bootloader and start over.
Bricking is a very final thing that one can not repeat on the same device. Once bricked, it's only good as a paperweight. If you can revive the device, then it was never bricked in the first place
Wrong radio will brick your device for certain. Kernel and ROM not so much...
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought I remembered reading that in some /r/android comments a few months ago. Thanks for confirming.
So since I'm on 4.0.2 running the leaked 4.0.3 radios, if I wanted to run 4.0.4 everything would you recommend just reverting back to pure stock 4.0.2 via this thread or similar method, and then going from there?
Vangelis13 said:
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
Click to expand...
Click to collapse
Not confirmed with this phone, but typically the bootloader will do an md5 type check, but recovery doesn't. If you disable signature verification in recovery, then it's all in your hands...
j.go said:
[snip]
The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
Click to expand...
Click to collapse
Not sure if the bootloader flow is the same on the Galaxy Nexus (probably not), but on the Nexus One, the bootloader will not flash a bootloader that is not signed. Period. Unless of course there is no NAND lock (i.e., S-OFF for HTC devices).
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
psycho2097 said:
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Dare you to flashable radio from another phone...
danger-rat said:
Dare you to flashable radio from another phone...
Click to expand...
Click to collapse
LOL!!!!!
Sent from my Galaxy Nexus using Tapatalk
I Dare y'all to flash the 4.0.4 update on a GSM phone. ;P
Sent from my Galaxy Nexus using xda premium
Since it appears the One also can potentially lose its IMEI upon flashing an AOSP rom like a few other devices, I have a couple of questions...
#1 - will "adb reboot nvbackup" and nvrestore work on the One, or was that a Samsung only thing for the S3?
#2 - I was about to ask about backing up EFS via recovery, but it appears, at least with TWRP, that's not an option yet
#3 - is there any other way to backup the IMEI before flashing an AOSP rom? I've had no issues with CM, but after NOT backing up my IMEI when I had a GS3 and going through the massive headache to get that working again, I'd prefer to have a backup before trying any others
TIA!
jntdroid said:
Since it appears the One also can potentially lose its IMEI upon flashing an AOSP rom like a few other devices, I have a couple of questions...
#1 - will "adb reboot nvbackup" and nvrestore work on the One, or was that a Samsung only thing for the S3?
#2 - I was about to ask about backing up EFS via recovery, but it appears, at least with TWRP, that's not an option yet
#3 - is there any other way to backup the IMEI before flashing an AOSP rom? I've had no issues with CM, but after NOT backing up my IMEI when I had a GS3 and going through the massive headache to get that working again, I'd prefer to have a backup before trying any others
TIA!
Click to expand...
Click to collapse
yuuup.... I jumped the gun and installed GPE without even considering this... now no VZ signal even after the restore. am I totally screwed without a backup?
Wait what's going on? I've flashed a few aosp ROMs already and back to sense and haven't lost anything g yet as far as I can see
Sent from my One using Tapatalk now Free
crazyg0od33 said:
Wait what's going on? I've flashed a few aosp ROMs already and back to sense and haven't lost anything g yet as far as I can see
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
Same here - well only CM so far. But others are reporting what sounds like IMEI loss after flashing AOSP. Doesn't sound as widespread as it was with the S3 - but if there's even a remote chance, I don't want to mess with it! Just hoping to get more info... hopefully it's not as big of a concern.
jntdroid said:
Same here - well only CM so far. But others are reporting what sounds like IMEI loss after flashing AOSP. Doesn't sound as widespread as it was with the S3 - but if there's even a remote chance, I don't want to mess with it! Just hoping to get more info... hopefully it's not as big of a concern.
Click to expand...
Click to collapse
what happens with an IMEI loss? we lose cell service?
BaBnkr said:
yuuup.... I jumped the gun and installed GPE without even considering this... now no VZ signal even after the restore. am I totally screwed without a backup?
Click to expand...
Click to collapse
If you are S-OFF, flash the RUU posted, and that will fix you up.
Yikes. I've flashed GPE (didn't enjoy so much), bonestock (LOVE) and am now on CM (like so far) and haven't had any issue. Hopefully I don't!
Sent from my HTC One.
Has anybody figured this out yet and is it still an issue??
Sent from my HTC6500LVW using xda app-developers app
andybones said:
If you are S-OFF, flash the RUU posted, and that will fix you up.
Click to expand...
Click to collapse
Yuup. That worked .
Sent from my stock (but rooted) VZW HTC One now Free
andybones said:
If you are S-OFF, flash the RUU posted, and that will fix you up.
Click to expand...
Click to collapse
Where is the RUU posted at?
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
i mean its been 10 minutes, but still stuck on bootloop any ideas?
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
Out of date ADB can cause this. I have seen it a few times reported by other people.
Try rebooting PC then reboot phone back to boot loader and use THESE adb and fastboot apps. I copied the from the latest SDK Manager
If that does not resolve then post back
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
You should probably include a screenshot of everything you did in the command prompt... boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Good point!
Scott said:
Good point!
Click to expand...
Click to collapse
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Scott said:
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Click to expand...
Click to collapse
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Agreed! But on the same note, in the OP's defense there is not a very clear Q/A thread that tells you what you need to do. Everything is scattered. However, that is not anyones fault. This device is new to "ALL" of us. The whole SLOT thing, etc. Its all new unless you had a Google Chromebook. So I cant much blame people with issues. The good thing... 99.99% of the issues posted can be fixed with some patients. :good:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Just ignore it, it's due to the unlocked bootloader
Sent from my Pixel XL using Tapatalk
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Nothing you can do about that at this time. I am sure someone will hack the aboot or hboot, which ever on an HTC device to remove it. For now wear it as a badge of pride :highfive:
iKenta said:
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
Click to expand...
Click to collapse
Could have been. I would recommend you not install TWRP at this time. Its finicky but being worked on. I know for fact it will be great soon.
I hope @Chainfire updates his Flash Fire. Easier to use than TWRP!