Hi!
After reading massive amounts of tutorials and forums, I just have to admit I cannot handle this and a little help would be nice!
I just bought a nice second hand HTC One (the European m7_ul version, it seems) and there is a big problem: I cannot install any ROMs and the phone just kind of gets into a boot-recovery (ClockworkMod) loop.
This phone has been ridiculously tampered with no knowledge, so it's very hard to pinpoint what on earth has happened in the past. That is why I got it quite cheap. Nice, but now it does not work as a phone at all after I tried some recovery techniques myself.
THE HISTORY AS FAR AS I UNDERSTAND:
-The phone has been first rooted in order to install custom ROMs: Android Revolution HD etc I think.
-It has also been S-offed
-The original user tried to do a "Total factory reset", he wanted the phone to be completely "Stock". He failed-ending up with S-On BUT Tampered/Unlocked etc..
WHAT HAVE I TRIED:
-Tried to OTA Update as the system offered this option. Didn't work, because of Status 7 error on ClockWorkMod.
-Same problem with all of the ROMs I downloaded and then tried to install from SDcard/Sideload (Status 7 error)
-Tried also fastboot flash recoveries, just ending up in a boot loop with HTC logo and sometimes even the exclamation mark+red triangle.
-Frustrated and tired, tried also several instructed ways of S-OFF (Which probably was a dumb idea also).
THE STATUS NOW:
-HTC One only boots into the HTC Logo Screen/ClockWorkMod, but does not let me install any of the ROMs I've tried.
INFO:
Fastboot getvar all gives me:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I also got some info from the last known working system while it still was running, before the stuck-in-boot-loop-era:
Android Version 4.3
Sense 5.5
Version 3.62.401.1
HTC SDK API 5.65
Build 3.62.401.1 CL264544 release-keys
The big question: IF it was first rooted, s-offed and then messed up completely (S-on seems to be now forever), is there still hope to get it to work?
--
UPDATE: Got it booting after installing Android_Revolution_HD-One_51.0, which seems to work OK. Normal fastboot sideload installation. I think this phone has been locked (S-ON) while using this exact ROM (Android_Revolution_HD-One_51.0, even the build numbers seem to match with the previously mentioned system. Still, no other ROM can be installed on this phone.
So, seems like we're just stuck with Android 4.3 and I need to backup closely. Am I completely lost with this S-ON theory?
--
Thanks!!
Related
I bought a T-Mobile USA HTC One from a guy who said it would randomly reboot. When I got it, it was S-ON had Bixie GE Rom and would reboot consistently about every 3 minutes. I managed to downgrade to get S-OFF and have spent a week trying every back-to-stock guide, RUU, firmware flash, Nandroid backup imaginable for both Sense and GE. On GE, I can at least get past the intro and use the phone until reboot, but Sense will always boot to the lock screen and never go further. Any Sense Rom or RUU would not bring up the initial setup. All still had a 3 minute reboot.
Of everything I tried, the [ROM] [AUG 3] [ANDROID 4.3] 3.06.1700.10 - Stock HTC Google Play Edition v1.1 was the only one to fix the reboot issue, but I'm still not able to get service (Baseband and IEMI unknown).
I accept there might be problem with the SIM slot, but does anyone happen to know why this particular Rom would work when everything else failed? All my Google-fu point toward using RUU's, but they simple will not stick, unlocked, relocked, stock recovery, you name it.
T-Mobile Kernel issue?
Any help is appreciated.
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
This is after I tried stock
Sieze said:
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
Click to expand...
Click to collapse
Yes, it goes into bootloader just fine. This is my getvar after my last attempt at T-Mo RUU:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**********
(bootloader) imei: 355**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
looks normal too me. have you tried a cutsom kernel? and have you tried full GPE conversion at any time?
it deffinately sounds like the phone is being a boner. if you have TWRP flashed try doing a factory data reset through it and see if it has issues wiping certain things most namely cache and dalvik cache.
and if after you do that nothing presents itself make sure youve got a ROM zip in phone storage or on a flash drive for use with usb otg and wipe system then try and flash a stock ROM and see if it fixes it.
best of luck and hopefully you get it working.
hello dear friends; here is lots of expert users in the forum;
I bought an AT&T phone, the seller ask me to do it is s-off, I said yes;
Everything was working fine, but when I wanted to update its ROM to ARHD 41 (4.4),
My phone became just a waste for me
I can enter hboot, I could upload a twrp 2.6.3.3, I can use adb sdeload,
And also I can flash a ROM, but; it is not starting,
when I power on it, HTC logo is showing, it is getting a Reset and after this it is directly going yo TWRP screen
and then doing this in a loop
There is no expert to correct this problem in my country
And the service will not repair it because it is an AT&T device.
If one of you be my guide, I will be greatful to you
I have tried too many things and now I am very tired to try something
I also changed the cid to upload a new ruu, or I tried to make partitions again etc etc ((((
By the way I cannot wipe the phone from TWRP, it is getting an error : unable to mount /cache and /data
If you explain me what to do step by step I can easily apply it.
Which raido? Which firmware? Which rom? Which RUU? etc... To give it a life again
My main target is to use a stable and fast custom rom. (Like maximus or arhd)
Current infos:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 21 2013, 20:19
Here is current getvar all result:
D:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT38CW1234566
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4333mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
skuyumcu said:
hello dear friends; here is lots of expert users in the forum;
I bought an AT&T phone, the seller ask me to do it is s-off, I said yes;
Everything was working fine, but when I wanted to update its ROM to ARHD 41 (4.4),
My phone became just a waste for me
I can enter hboot, I could upload a twrp 2.6.3.3, I can use adb sdeload,
And also I can flash a ROM, but; it is not starting,
when I power on it, HTC logo is showing, it is getting a Reset and after this it is directly going yo TWRP screen
and then doing this in a loop
There is no expert to correct this problem in my country
And the service will not repair it because it is an AT&T device.
If one of you be my guide, I will be greatful to you
I have tried too many things and now I am very tired to try something
I also changed the cid to upload a new ruu, or I tried to make partitions again etc etc ((((
By the way I cannot wipe the phone from TWRP, it is getting an error : unable to mount /cache and /data
If you explain me what to do step by step I can easily apply it.
Which raido? Which firmware? Which rom? Which RUU? etc... To give it a life again
My main target is to use a stable and fast custom rom. (Like maximus or arhd)
Current infos:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 21 2013, 20:19
Here is current getvar all result:
D:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4333mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Edit your post and remove your serial no and the modelid was ok to leave. you already said it's at&t.
you said you flashed recovery
did you clear cache after ?
did you check the MD5 of the rom you downloaded before flashing it ?
your phone shows it was developers edition last .. is this correct ?
your probably going to need to RUU back to stock.
but first try booting to bootloader fastboot USB
and from your pc
fastboot erase cache
fastboot reboot-bootloader and try and flash your Rom again (if it passed the md5 check)
hello clsA; thank you very much for your quick answer, I edit the message and delete the serial but you quoted it
I have made all the things you wrote; but Suddenly I solve the whole problem
When I tried to install SuperSU in TWRP; everything was gone right!
I flashed the ARHD 41, and it is working now
I was trying to fix this problem for 48 hours
at&t htc one m7 problem
But Dear clsA; you can still help me about something; what firmware and radio versions would be your suggestions?
I am living in Turkey, my carrier supports HSPDA
Kind Regards
skuyumcu said:
But Dear clsA; you can still help me about something; what firmware and radio versions would be your suggestions?
I am living in Turkey, my carrier supports HSPDA
Kind Regards
Click to expand...
Click to collapse
The firmware your on now should be fine ..are you getting poor signal of other problems ?
at&t htc one m7 problem
Actually I have no problem; It's signal bars are indicating lower than my old IPhone 4S,
but its coverage and signal quality(also sound quality) is much better than it
I just wanted to be sure by asking you,
And another thing it is writing a caution with red color while booting (This rom is a development purposes only etc. bla bla bla)
This is not bothering me, it can write, if there won't be any problem with stability or performance
Thank you again for your answers
skuyumcu said:
Actually I have no problem; It's signal bars are indicating lower than my old IPhone 4S,
but its coverage and signal quality(also sound quality) is much better than it
I just wanted to be sure by asking you,
And another thing it is writing a caution with red color while booting (This rom is a development purposes only etc. bla bla bla)
This is not bothering me, it can write, if there won't be any problem with stability or performance
Thank you again for your answers
Click to expand...
Click to collapse
your fine ..enjoy your phone
Hello all,
As the title states, I have been having the worst time trying to use the latest signed RUU for the AT&T M7:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I have attempted more than 20 times trying to get this damn thing to work, and each time fastboot crashes or I get an error 155. I am relocked, on a completely stock ROM:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
I have done multiple things to get around the issue like having the phone already in fastboot when running the RUU, trying to run the RUU as admin, and even trying to run the RUU from the AndroidOS itself. I can't seem to find a .zip alternative for a command install and was maybe thinking that might work better.
Phone is CID: CWS__001, modelid: PN0712000, S-Off, HBoot 1.55, Relocked
Can anyone verify what the problem might be? This is beginning to really piss me off...
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ****************
(bootloader) imei: ********************
(bootloader) meid: *******************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
digitalism said:
Hello all,
As the title states, I have been having the worst time trying to use the latest signed RUU for the AT&T M7:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I have attempted more than 20 times trying to get this damn thing to work, and each time fastboot crashes or I get an error 155. I am relocked, on a completely stock ROM:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
I have done multiple things to get around the issue like having the phone already in fastboot when running the RUU, trying to run the RUU as admin, and even trying to run the RUU from the AndroidOS itself. I can't seem to find a .zip alternative for a command install and was maybe thinking that might work better.
Phone is CID: CWS__001, modelid: PN0712000, S-Off, HBoot 1.55, Relocked
Can anyone verify what the problem might be? This is beginning to really piss me off...
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ****************
(bootloader) imei: ********************
(bootloader) meid: *******************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Yeah that 4.4 RUU is really strange... It worked for me when it came out but I have never gotten it to work again. I just install the 3.x.502.x RUU and do the OTApkg.zip update's
clsA said:
Yeah that 4.4 RUU is really strange... It worked for me when it came out but I have never gotten it to work again. I just install the 3.x.502.x RUU and do the OTApkg.zip update's
Click to expand...
Click to collapse
Strange...but I ended up doing the same. I was hoping to find a .zip of this RUU, but have had absolutely no luck. Everything is running good now, so no troubles to speak of at the moment.
It happened to me as well. I couldn't complete the 4.4 RUU flashing. Instead, I had to flash the 4.3 RUU and then use the OTA package from stock recovery.
Sad to say, but it seems like the AT&T section for the M7 is really lacking as far as ROM production and suitable software. I tried jumping over to the international M7 sections, SuperCID'd my phone, installed some various ROM's, all which ate up my battery much too fast for what I tend to like. So I swapped back to almost pure stock.
Any of you guys have a good recommendation as far as international M7 ROM's that use Sense 6 with decent battery conservation? I was previously on ARHD, tried out CleanROM, and a few AOSP releases. Each seemed to progressively destroyed my battery life after a few days, even restarting the phone didn't seem to fix the horrible battery consumption.
digitalism said:
Sad to say, but it seems like the AT&T section for the M7 is really lacking as far as ROM production and suitable software. I tried jumping over to the international M7 sections, SuperCID'd my phone, installed some various ROM's, all which ate up my battery much too fast for what I tend to like. So I swapped back to almost pure stock.
Any of you guys have a good recommendation as far as international M7 ROM's that use Sense 6 with decent battery conservation? I was previously on ARHD, tried out CleanROM, and a few AOSP releases. Each seemed to progressively destroyed my battery life after a few days, even restarting the phone didn't seem to fix the horrible battery consumption.
Click to expand...
Click to collapse
I pretty much only use Stock Rooted with a custom kernel (ElementalX) or Insertcoin
clsA said:
I pretty much only use Stock Rooted with a custom kernel (ElementalX) or Insertcoin
Click to expand...
Click to collapse
Yes, I was at one point, but after trying out Sense 6, I fell in love. The only problem is the battery performance.
Um theres the rom I put out thats made from developer us build which is same as att device...battery life is good from whats been reported...
I soft bricked my AT&T M8 and am hoping some of the great minds here at XDA can help. Unfortunately, this happened back in September so I've forgotten a lot of what I did to get myself in this mess, but I will try to remember as best I can.
I had originally modified my MEID and was running a GPE ROM. When an OTA update was pushed by Google, I foolishly tried to install it and the phone became stuck in a bootloop. I tried to rectify the situation by performing a system wipe, relocking the bootloader, and running the stock AT&T RUU from the SD card. The RUU failed to run and I received "ERROR 159." I am now stuck with the stock recovery image and my device is no longer recognized in fastboot.
First 6 lines of text on the HBoot screen:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning**
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx (this was populated, I just masked)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done! finished. total time: 0.013s
Correction, I think it was a GPE RUU that I had installed and not a ROM because my recovery screen is black. I read in another thread that a black screen may indicate this.
I unlocked my bootloader, installed TWRP, and installed Android Revolution 22.1 and the phone still will not boot past the HTC splash screen. I also tried both available RUUs; 1.58 and 2.23. Any suggestions?
I think youd have to revert back to mid of sense version. if s-on I am not sure how you got it to convert in the first place.As I havent ever liked or had the idea of changing the device to gpe. Maybe in the conversion thread you used to convert the device that got you to this point. Are you able to install a gpe rom? I am unfamiliar with ARHD builds
I also have no clue how you got as far as you did without S-OFF. You shouldn't have been able to run a GPE RUU.
ARHD also won't play nice without the 3.x firmware.
Try the desktop .exe versions of the RUUs, if you haven't already, and make sure the md5 matches.
If you can still get twrp on your phone, try restoring a 1.12 or 1.54 backup from here http://forum.xda-developers.com/showthread.php?t=2701376 or http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966.
Make sure to factory reset in twrp.
Your cid and mid are still at&t stock, so I don't think those are the cause of your problem. The fields where the firmware version should be displayed are empty though, and I don't know how you got to that state.
If none of that works, then I'd try a 4.4.4 based GPE rom that still works with the 2.x firmware, like an older version of skydragon. An older version of a sense based rom still using 4.4.3 might still work.
Okay, so I've got an AT&T M7 that has has (as far as I can tell - a stock version running 4.42 and HTC Sense 6.0) the Software number is 5.12.502.2.
The problem is, that apparently something is extremely corrupted - and I get messages like "Swiftkey has stopped", except replace Swiftkey with tons of other things, as it keeps happening over and over.
If I reboot, any changes that were made (downloads, settings, ANYTHING), apparently gets erased, or is not saved.
I can boot into recovery (which is TWRP 2.7.1.1, and again - any changes I make are not actually written. I can attempt to flash roms (cm, htc1guru stock images, etc.), and they will generally go through the motions of running - and even say 'successful' at the end, but if you reboot after that, everything is still as it was before. No changes at all (think of it like Groundhog Day... every day I can kill myself, eat whatever I want, kill other people(delete stuff, change things, add things) - but after the phone sleeps (aka restarts), the day (aka the phone) is reset as if I did absolutely nothing.)
I have tried wiping cache, data, system, literally EVERYTHING and it does absolutely nothing.
Also, if I try the main Factory Reset from inside the ROM itself, it says it is doing something, but then reboots and everything is back as it was also.
I've tried fastboot boot <insert multiple recovery images multiple times.img>, and it just locks up the phone and I have to hard restart it.
I've tried fastboot flash <new recovery.img> - it actually says successful, but again - does nothing after rebooting.
I am literally going crazy here... I can push files temporarily to the device, and try to do stuff with them, but in the end nothing can seem to make any difference.
I have tried going through htcdev unlock with Unlock_code.bin, and it doesn't do anything.
fastboot oem lock does nothing
Everything I've found says maybe S-OFF would help, but I can't seem to find any way to get that done.
Please, can ANYONE help me figure out how to get this stupid thing to be at all useful again? All help is appreciated. Below is my
e:\Downloads>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSOREDFORMYPARANOIA
(bootloader) imei: CENSOREDFORMYPARANOIA
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Follow the unlock your bootloader thread..
wingsltd said:
Follow the unlock your bootloader thread..
Click to expand...
Click to collapse
Bootloader is unlocked, and I have tried re-unlocking. Nothing changes. I mean, I appreciate the input - but did you even read the post above? Answers like that make me feel like I'm talking to Tier I tech support at Gateway or something.