Related
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
MobileWon said:
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
Every phone i have had from the g1, mytouch 3g, vibrant, and now g2 it never fails to amaze me how people who dont know what they are doing manage to brick their phone in under a day. PROTIP READ learn what you are doing before you go in doing it so you dont screw yourself.
If you have the hboot menu and you seem to have s-off so you can restore official htc rom or a custom rom
Sent from my HTC Vision using XDA App
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Hot_Hands said:
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Click to expand...
Click to collapse
Yup, exacly what he said.. also, I don't think editing the statusbar from a stock is possible because its odexed, correct me if I am wrong though.. unless you really know what you're doing.. so now after flashing recovery, try again with a nandroid if you have yours if not with fastludeh's stock odex or deodex rom if you want to keep it stock.
Sent from my HTC Vision
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Hot_Hands said:
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Click to expand...
Click to collapse
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
Nope. Just put it on your SD and flash from recovery.
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
No, you do not need to rename it.
Sent from my HTC Vision using XDA App
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
EDIT: Oh wait, it says SHIP S-OFF, shouldn't it say ENG S-OFF if you had the ENG boot loader? Did you even flash the new HBOOT?
KoolKidsKlub said:
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
Click to expand...
Click to collapse
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
ianmcquinn said:
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
Click to expand...
Click to collapse
Yeah I just noticed that and edited my post about 1-2 minutes ago.
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
MobileWon said:
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
Click to expand...
Click to collapse
Yeah ummm you might be screwed, we assumed that you flashed the engineering HBOOT, and only with the engineering HBOOT can you use fastboot to save your self and it seems like you don't have it. I'm not sure what to do now, I think some one said that you might have to flash the stock ROM but I'm not sure how. Wait around for some other guys to help you out, they know more than me with this stuff.
Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Ok, I have the stock rom already. How do I flash a RUU? Or can you give me a link?
Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
EDIT: And if you do have to flash an RUU, could you please explain how? I would like to know how just in case I screw something up(which I probably won't because I have been on my computer searching the forum, asking for help and to double check that what I have learned is correct and what to do if something bad happens for the past week or two) and I can also use the information to help other users.
KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
That was a warning because if you had S-Off and root it would put S-On and remove root. It was an issue because for a while it was impossible to root the DZ's 1.72 RUU but this has since been worked around and doesn't apply to the G2.
Ok, guys Im not an idiot. I previously had a HD2 and had no problems...just rushing to get my phone right before I go out of town for the weekend. So, whatever I have to do to get it right.
KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
You might be right.
Ok,... So you have gone into your Hboot screen, select fastboot, then it says Fastboot on the screen yeah? Do:
fastboot devices
in cmd, do you get anything?
Two days after owning this phone I had the dreaded bent metal issue near the volume button. I flashed pure nexus on it though and I'm trying to get it back to stock before I take it back into bestbuy to get a new one. My stock nandroid backup fully flashes but it won't boot. All I see is the google logo.
Any ideas? I know I can fb flash the stock, but that's so much more of a process. Plus, it doesn't make sense to me that it wouldn't work... -_-
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
did you follow the directions in #4?
Soulfly3 said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
did you follow the directions in #4?
Click to expand...
Click to collapse
Yes, to the letter.
I fastboot flashed all the files and relocked my bootloader, about to take it back into best buy now. I'd still like to know why the heck my backups didn't work... >:|
andrewnelson23 said:
I fastboot flashed all the files and relocked my bootloader, about to take it back into best buy now. I'd still like to know why the heck my backups didn't work... >:|
Click to expand...
Click to collapse
Did you have a modified boot.img(dm verity checks removed) for you're stock back up. Cuz stock will not boot from twrp if you don't have a modified boot.img. you need dm verity removed in order to use twrp.
Sent from my XT1080 using Tapatalk
toknitup420 said:
Did you have a modified boot.img(dm verity checks removed) for you're stock back up. Cuz stock will not boot from twrp if you don't have a modified boot.img. you need dm verity removed in order to use twrp.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Hmm I don't think that was in the guide I read. So cool. So if I simply restored my nandroid and then flashed a custom kernel it would be fixed?
So that means the only way to really return to full stock is to fastboot flash it?
andrewnelson23 said:
Hmm I don't think that was in the guide I read. So cool. So if I simply restored my nandroid and then flashed a custom kernel it would be fixed?
So that means the only way to really return to full stock is to fastboot flash it?
Click to expand...
Click to collapse
That is the most reliable way.
Looks like there is a new update coming.
https://9to5google.com/2016/12/05/android-7-1-1-update-ota-nexus-pixel-december/
Interesting that it is coming to Verizon pixels but no factory images from Google yet. Curious to see if both models will always have the same updates or if sometimes Verizon models will have specific ones.
Edit: Guessing this is just the January security update.
So do you think it will go to Google sold models on the Verizon network? That's what I have and when I got the phone it immediately updated to Verizon firmware, then Dec seemed like a unified update and I got that. Just had phone check for updates and I have none.
Sent from my Pixel XL using Tapatalk
ahent said:
So do you think it will go to Google sold models on the Verizon network? That's what I have and when I got the phone it immediately updated to Verizon firmware, then Dec seemed like a unified update and I got that. Just had phone check for updates and I have none.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
You'll get updates based on SIM.
Don't take it, if you even have a choice!
Ker~Man said:
Don't take it, if you even have a choice!
Click to expand...
Click to collapse
Why not? Isn't one of the benefits of the Pixel the monthly security updates?
JU57US said:
Why not? Isn't one of the benefits of the Pixel the monthly security updates?
Click to expand...
Click to collapse
Rumor is that the next Verizon OTA will make the devices bootloader permanently unlockable. If the doesn't bother you, then have at it!
Ker~Man said:
Rumor is that the next Verizon OTA will make the devices bootloader permanently unlockable. If the doesn't bother you, then have at it!
Click to expand...
Click to collapse
I may be missing something, but didn't that already happen with the Dec 5 update to 7.1.1?
Ker~Man said:
Rumor is that the next Verizon OTA will make the devices bootloader permanently unlockable. If the doesn't bother you, then have at it!
Click to expand...
Click to collapse
Yea you are a little behind. That update was released the beginning of the month. It was the 7.1.1 update. So if you get a phone from Verizon and it shipped with 7.1.1 or you let it update right away.. then you can't unlock it.
Droidlife did a story on this. http://www.droid-life.com/2016/12/27/pixel-xl-android-update-nmf26u/
Sent from my Pixel XL using Tapatalk
JU57US said:
I may be missing something, but didn't that already happen with the Dec 5 update to 7.1.1?
Click to expand...
Click to collapse
It did yes, you're correct.
I've already unlocked my bootloader, is it safe to update or do I need to stay on 7.1?
game_guy said:
I've already unlocked my bootloader, is it safe to update or do I need to stay on 7.1?
Click to expand...
Click to collapse
It's safe, just don't relock.
Sent from my Pixel XL
Rydah805 said:
It's safe, just don't relock.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thanks man, one more question I forgot to include in my first post, do i need to re-root or will it stick?
game_guy said:
Thanks man, one more question I forgot to include in my first post, do i need to re-root or will it stick?
Click to expand...
Click to collapse
I believe reroot
Sent from my Pixel XL
Rydah805 said:
I believe reroot
Sent from my Pixel XL
Click to expand...
Click to collapse
im on 7.1 unlocked bl... rooted w/ twrp/supersu method... vzn pixel xl
to confirm - if i flash 7.1.1 NMF26U, then:
a) bl will NOT get relocked unless i enter the fastboot cmd to do so (which i dont plan to);
b) i will have to AND will be able to reroot using twrp/supersu method; and
c) i will lose all my data unless i delete the "-w" from the flash-all bat (which, unfortunately, i cant do for wutever reason)
much thx in advance, and thx to all for the hard work
peterlee928 said:
im on 7.1 unlocked bl... rooted w/ twrp/supersu method... vzn pixel xl
to confirm - if i flash 7.1.1 NMF26U, then:
a) bl will NOT get relocked unless i enter the fastboot cmd to do so (which i dont plan to);
b) i will have to AND will be able to reroot using twrp/supersu method; and
c) i will lose all my data unless i delete the "-w" from the flash-all bat (which, unfortunately, i cant do for wutever reason)
much thx in advance, and thx to all for the hard work
Click to expand...
Click to collapse
A) correct, your bootloader will not relock unless you command it to.
B) Correct, you will have to, and will be able to, reroot with whatever the current rooting procedure is
C)Correct, if you use the flash-all.bat without removing -w you will lose your data. You could extract all the images from the factory image zip and individually flash them and not lose your data
neilrl79 said:
A) correct, your bootloader will not relock unless you command it to.
B) Correct, you will have to, and will be able to, reroot with whatever the current rooting procedure is
C)Correct, if you use the flash-all.bat without removing -w you will lose your data. You could extract all the images from the factory image zip and individually flash them and not lose your data
Click to expand...
Click to collapse
much thx neilrl
quick follow up on (c) - how do i go abt this process? id prefer to not lose my data and not go thru the tibu restore process
peterlee928 said:
much thx neilrl
quick follow up on (c) - how do i go abt this process? id prefer to not lose my data and not go thru the tibu restore process
Click to expand...
Click to collapse
I use note ++ but I'm on Windows. Just right click the file after u un zip it and click edit with note++, remove -w and then you can just double click on the flash all bat file and it will install
peterlee928 said:
much thx neilrl
quick follow up on (c) - how do i go abt this process? id prefer to not lose my data and not go thru the tibu restore process
Click to expand...
Click to collapse
You could do this....
mac796 said:
I use note ++ but I'm on Windows. Just right click the file after u un zip it and click edit with note++, remove -w and then you can just double click on the flash all bat file and it will install
Click to expand...
Click to collapse
Or....
extract all of the images from the factory image zip( right click on the file and hit extract), make sure they are in same location as Fastboot
Then run through he commands...
Fastboot flash bootloader (name of file).IMG
Fastboot reboot bootloader
Fastboot flash radio radio.img
Fastboot flash boot boot.img
Fastboot flash system system.img
I'm sure a quick search would get you some more in depth instructions than I'm giving but it's a really simple process.
Also if you do it by Fastboot flashing the images manually, just skip flashing the recovery image and you'll still have TWRP installed for rerooting.
neilrl79 said:
You could do this....
Or....
extract all of the images from the factory image zip( right click on the file and hit extract), make sure they are in same location as Fastboot
Then run through he commands...
Fastboot flash bootloader (name of file).IMG
Fastboot reboot bootloader
Fastboot flash radio radio.img
Fastboot flash boot boot.img
Fastboot flash system system.img
I'm sure a quick search would get you some more in depth instructions than I'm giving but it's a really simple process.
Also if you do it by Fastboot flashing the images manually, just skip flashing the recovery image and you'll still have TWRP installed for rerooting.
Click to expand...
Click to collapse
There isn't a recovery image anymore, it's part of boot image now
Hey, I've ready 20+ threads here and it seems that miflash is the best way to go completely back to stock?
I'm on A2017U (US model) and I'm on stock through Draken's back to stock zips. If I flash a stock recovery, would that make it fully stock? I have unlocked bootloader.. does that need to be flashed too?
Just want to avoid miflash if I don't have to since it's a huge download and I read it's finicky.
I have the original recovery & boot partitions backed up using axon7tool.exe from when I first bought my phone in August 2016. If I restore those 2, would it work? Would they be out of date from the newest stock roms and cause problems?
Thx
Yes, MiFlash is the best option to get fully stock.
WesTD said:
Yes, MiFlash is the best option to get fully stock.
Click to expand...
Click to collapse
Alright, off to download. Thanks
What file do you use with miflash to go back to full stock? I would like to as well. To get ota and stuff.
ShiverStorm said:
What file do you use with miflash to go back to full stock? I would like to as well. To get ota and stuff.
Click to expand...
Click to collapse
EDL files such as the ones in WesTD's own stock edl images thread. of course flashing one from another model is bad. so don't.
Choose an username... said:
EDL files such as the ones in WesTD's own stock edl images thread. of course flashing one from another model is bad. so don't.
Click to expand...
Click to collapse
Haha yeah, I found one with ota files but I didn't see one for the U version.. Thank you for the response!
I recently flashed my 6T to stock from EvolutionX and locked the bootloader, and somehow in the process, it seems my keyboard isn't able to display or type any emojis. The steps I followed are:
HTML:
1. fastboot reboot bootloader
2. fastboot boot twrp
3. flash latest OOS
4. reboot bootloader
5. fastboot boot twrp
6. flash OOS
7. boot system
8. reboot bootloader
9. fastboot oem lock
10. boot system and setup (sign in to google, etc)
Is there any step that I missed, or any way to recover this without rooting/unlocking again?
Neontc said:
I recently flashed my 6T to stock from EvolutionX and locked the bootloader, and somehow in the process, it seems my keyboard isn't able to display or type any emojis. The steps I followed are:
1. fastboot reboot bootloader2. fastboot boot twrp3. flash latest OOS4. reboot bootloader5. fastboot boot twrp6. flash OOS7. boot system8. reboot bootloader9. fastboot oem lock10. boot system and setup (sign in to google, etc)
Is there any step that I missed, or any way to recover this without rooting/unlocking again?
Click to expand...
Click to collapse
Reflash your ROM through stock recovery ..
You're missing the reserve partition cause you've flashed through twrp..
If you still dont have emoji
root your phone and flash this module
https://androidfilehost.com/?fid=1899786940962618515
That would be this link here, correct?
https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156215016
Neontc said:
That would be this link here, correct?
https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156215016
Click to expand...
Click to collapse
Yes
cultofluna said:
Yes
Click to expand...
Click to collapse
Maybe I'm missing something? The only options I see when I'm recovery are reboot and wipe data/cache
Neontc said:
Maybe I'm missing something? The only options I see when I'm recovery are reboot and wipe data/cache
Click to expand...
Click to collapse
Yes you're missing the essential you evidently need TWRP to do that...
Neontc said:
Maybe I'm missing something? The only options I see when I'm recovery are reboot and wipe data/cache
Click to expand...
Click to collapse
Local upgrade
You could also just run msmdownloadtool, it will reset the device to full stock. There is a version for 10.3.0, just run it and upgrade.
Striatum_bdr said:
Yes you're missing the essential you evidently need TWRP to do that...
Click to expand...
Click to collapse
I thought I had to use stock recovery to flash this. Can I just fastboot boot twrp and flash it from there?
cultofluna said:
Local upgrade
Click to expand...
Click to collapse
From the settings menu in the os right? I tried that and it kept asking me to move the upgrade file to the root of the internal storage, like it didn't see it or something
efex said:
You could also just run msmdownloadtool, it will reset the device to full stock. There is a version for 10.3.0, just run it and upgrade.
Click to expand...
Click to collapse
This is a T-Mobile device that has been converted to international fw. Would I use the international 10.3.0 msm file?
Neontc said:
I thought I had to use stock recovery to flash this. Can I just fastboot boot twrp and flash it from there?
From the settings menu in the os right? I tried that and it kept asking me to move the upgrade file to the root of the internal storage, like it didn't see it or something
This is a T-Mobile device that has been converted to international fw. Would I use the international 10.3.0 msm file?
Click to expand...
Click to collapse
Nope, Tmob MSM, international one won't run anyway in your case.
Neontc said:
I thought I had to use stock recovery to flash this. Can I just fastboot boot twrp and flash it from there?
From the settings menu in the os right? I tried that and it kept asking me to move the upgrade file to the root of the internal storage, like it didn't see it or something
This is a T-Mobile device that has been converted to international fw. Would I use the international 10.3.0 msm file?
Click to expand...
Click to collapse
Yes just move it to the root of the internal storage..
And install it..
You will have the reserve partition back..( and working emojis)
efex said:
You could also just run msmdownloadtool, it will reset the device to full stock. There is a version for 10.3.0, just run it and upgrade.
Click to expand...
Click to collapse
Msm 10.3.0 ?? Link please
cultofluna said:
Local upgrade
Click to expand...
Click to collapse
No luck using the latest official fw from OnePlus website. Is there anything else left to try?
Neontc said:
No luck using the latest official fw from OnePlus website. Is there anything else left to try?
Click to expand...
Click to collapse
You've flash it but still no emojis?
cultofluna said:
You've flash it but still no emojis?
Click to expand...
Click to collapse
Correct. Flashed using local upgrade from inside the os and still didn't fix it.
Edit: after uninstalling updates for Gboard they returned. Thanks everyone for all the replies!
clubhouse00 said:
Msm 10.3.0 ?? Link please
Click to expand...
Click to collapse
I found it here on xda, but seem unable to do so now.. I have the files on my work PC, I could upload it tomorrow if you want it. It's for the international OP6T
Edit: Uploading now, will provide link when finished
Edit2: Mega link