Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
keinam.ty said:
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
Click to expand...
Click to collapse
There's not much you can do here. If you don't have TWRP or unlocked bootloader, you should just RMA the device direct through Motorola.
You could try to sideload the update you had received that caused this.
Other than that, RMA.
I was hoping not to hear RMA - but thanks for the reply.
Related
Hi Guys,
I updated my Vodafone Ireland HTC One to Android 4.4.2 OTA version (4.19.161.10) a couple of weeks ago. I have serious problems with the phone since then, it's not much of use anymore. I get the following error messages on homepage when the phone starts: "shoebox engine has stopped", "com.android.phone has stopped" , and I constantly get "google play services has stopped" error message. Worst thing is that the phone restarts itself a few times a day and when it restarts, it goes back to the state it was on the day I updated it. Anything I saved on my phone since the update gets removed (contacts, pics, sms, whatsapp messages, progress in games).
I tried a factory reset, but it doesn't work. Phone restarts to do the reset and shows me a triangle with an exclamation mark in it for a minute or so, and then just restarts normally, no reset done. HTC phone support couldn't offer any solution.
So, I would like to wipe all the data off my phone and go back to official Android 4.3. I never rooted the phone and it's still "Locked" with S-On. I'm not really interested in rooting, I just want to have the device working properly. Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps? HBoot version is 1.56, would it cause any problems?
Any additional feedback is welcome, appreciate your help! Thanks
I never rooted the phone and it's still "Locked" with S-On.
Click to expand...
Click to collapse
Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps?
Click to expand...
Click to collapse
Is the bootloader unlocked or not? my guess is you meant to say unlock?
You should be able to flash RUU without doing anything else
JPS7 said:
Hi Guys,
I updated my Vodafone Ireland HTC One to Android 4.4.2 OTA version (4.19.161.10) a couple of weeks ago. I have serious problems with the phone since then, it's not much of use anymore. I get the following error messages on homepage when the phone starts: "shoebox engine has stopped", "com.android.phone has stopped" , and I constantly get "google play services has stopped" error message. Worst thing is that the phone restarts itself a few times a day and when it restarts, it goes back to the state it was on the day I updated it. Anything I saved on my phone since the update gets removed (contacts, pics, sms, whatsapp messages, progress in games).
I tried a factory reset, but it doesn't work. Phone restarts to do the reset and shows me a triangle with an exclamation mark in it for a minute or so, and then just restarts normally, no reset done. HTC phone support couldn't offer any solution.
So, I would like to wipe all the data off my phone and go back to official Android 4.3. I never rooted the phone and it's still "Locked" with S-On. I'm not really interested in rooting, I just want to have the device working properly. Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps? HBoot version is 1.56, would it cause any problems?
Any additional feedback is welcome, appreciate your help! Thanks
Click to expand...
Click to collapse
I don't think you will be able to downgrade to 4.3 without s-off, You sure you don't have an app that kitkat doesn't like. Since you want to wipe all data, why not backup all apps and then uninstall everything you downloaded and installed, reset the phone gain and see what happens.
Or perhaps try a custom rom
Backup the SD card/any data you want and factory reset the phone and set up 4.4.2 again from scratch. Sometimes and OTA doesn't 'take' properly the first time from my experience
I think a factory reset would solve a lot of problems, but the phone doesn't want to do it. When I try to factory reset, it first shows Red triangle with exclamation mark and then just restarts with nothing removed. Tried both through the menu and with hardware buttons.
I read on several guides that "Fastboot" needs to be switched off before a factory reset. Maybe that's the problem. Because if I disable "Fastboot" in "Settings -> Power", the phone will not have this setting saved when it restarts. As I wrote in the original post, when the phone restarts, all of the settings and data in the phone go back to the state they were on the day I updated it to 4.4.2. My e-mails, messages, pictures, songs, app settings, even the temperature on the weather app :silly:
Bootloader is currently "Locked" and it was never unlocked before. I upgraded only OTA versions so far. Thanks for the opinions. I just don't want to do anything wrong while trying to make it better. Still don't know if I should skip s-off or not. Would it harm the phone if I just try with s-on?
JPS7 said:
I think a factory reset would solve a lot of problems, but the phone doesn't want to do it. When I try to factory reset, it first shows Red triangle with exclamation mark and then just restarts with nothing removed. Tried both through the menu and with hardware buttons.
I read on several guides that "Fastboot" needs to be switched off before a factory reset. Maybe that's the problem. Because if I disable "Fastboot" in "Settings -> Power", the phone will not have this setting saved when it restarts. As I wrote in the original post, when the phone restarts, all of the settings and data in the phone go back to the state they were on the day I updated it to 4.4.2. My e-mails, messages, pictures, songs, app settings, even the temperature on the weather app :silly:
Bootloader is currently "Locked" and it was never unlocked before. I upgraded only OTA versions so far. Thanks for the opinions. I just don't want to do anything wrong while trying to make it better. Still don't know if I should skip s-off or not. Would it harm the phone if I just try with s-on?
Click to expand...
Click to collapse
Wow!!!! UNLOCK BOOTLOADER!!!!!!! Install twrp. In recovery wipe data only that's a factory reset. If you read the s-off threads fully you will have no problems,so go forth and profit. The fastboot setting in power settings is for a quick power on only. It has nothing to do with anything else.
[email protected] said:
Wow!!!! UNLOCK BOOTLOADER!!!!!!! Install twrp. In recovery wipe data only that's a factory reset. If you read the s-off threads fully you will have no problems,so go forth and profit. The fastboot setting in power settings is for a quick power on only. It has nothing to do with anything else.
Click to expand...
Click to collapse
It's a pain. I can't even unlock the bootloader. I followed the steps correctly and got to the screen on my phone where it gives all the information about warranty and asks "Unlock the bootloader?". I volume up and pick "Yes". Device restarts and nothing happened. Again back to the day I installed 4.4.2 and the bootloader is still locked
You will somehow have to unlock. Have you tried from command line to use the unlock.bin file, or have you tried it via AIO to see if there are different results when it asks? To downgrade you will need to get that done, S-Off, downgrade HBoot, and run the RUU if there is one for your device. If not, grab one of the stock 4.3's from the forums, and do it manually. Personally I would change CID if needed and RUU the dev edition, but that's just me.
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse
dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:
Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.
Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.
I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.
I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.
After much messing and a headache I finally got to c432b370
And everything back to normal
tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk
I recently had to replace the motherboard on my Nexus 6. I could only find refurbished ones, and bought one on AliExpress, with item description clearly specifying as unlock. I installed it, and it appears it is actually locked status 2. Looks like demo version used in T-Mobile retail network. Some settings inaccessible u such as developer mode or Apps. Trying to get refund but both AliExpress and the vendor are in denial mode.
I have 7.0, NBD92G installed. Very hard to unlock as I cannot access developer mode to allow usb debug. Pressing build nr several times won't help. I get message "you're already a developer" but actually usb debug does not work.
Anybody can help?
Go download factory image from Google and flash it manually by using the command prompt.
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Strephon Alkhalikoi said:
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Click to expand...
Click to collapse
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
FYBRU said:
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
Click to expand...
Click to collapse
I think I figured out how to do this but the other question is whether I won't be stuck afterwards being requested to enter the only registered user's login which I do not have (I cannot register a second user, as this setting screen is locked too). Do I need to sideload the OTA corresponding to current version / build or can I sideload an older one?
Download the oldest OTA available, as long as it is a full system OTA (easily detectable by size). You're going to have to bypass Factory Reset Protection to be able to resolve this, and the older the OTA, the better.
If this doesn't work, you're going to have to fight with the place you got the motherboard from, and file a chargeback with your credit card company if need be.
Ultimately I can go for the refund, but there is no place where I can find 64 GB MBs outside China, which means I'll have to wait again for something like 3 weeks with poor backup device, and with no certainty I don't receive again a locked MB.
I tried with 6.0 OTAs (page with instructions I followed: https://developers.google.com/android/ota#shamu) and even with just older versions of 7.0, I got every time abortion after about 45% installation, with the msg that I cannot update with older versions.
I am a bit confused now, I just tried to install same build as what I had installed (https://dl.google.com/dl/android/aosp/shamu-ota-nbd92g-2b65257b.zip), it worked but it looks like absolutely nothing has changed on my phone. I thought it would have erased pretty much everything. Am I missing something?
OTA updates don't wipe system. That's why nothing changed.
Ultimately, I think you're going to have to go for the refund and take the risk that the next motherboard you get is going to be locked. Unless the version of Android you're on can have its FRP bypassed - and I don't think it can - you're stuck.
Thanks, bad news. Would it be worth trying wipe data / factory reset accessible from the recovery mode + power/volume up menu ?
You can try it, but it won't help. Doing a factory reset will cause Factory Reset Protection to kick in, meaning you'd need to know the original owner's account information.
Surprisingly it worked. I could log in with the google account I used before the reset. Everything works, but indeed I was expecting some more difficulties
@FYBRU: This is one of those times where I'm pleased to be wrong. LOL.
Glad you got it resolved.
Most of the time I am the guy helping people out. This time I think I did something pretty dumb.
I have an old "beater" P9 plus that I was using as a casual gaming device. Most of the apps I was using were beginning to no longer be supported because for some reason the device NEVER updated. Any time I check for a possible update the phone stated it was up to date. After much searching I discovered that this device SHOULD have updated quite a few times.
I used firmware finder to find a supported update and the first one went somewhat unexpected. The firmware was downloaded and put in the correct folders but kept failing after 5%. I decided that the next thing to do was to find a cool rom and go through the process of unlocking and installing TWRP. I usually try to install the latest TWRP. This turned out not working at all so I went for an older version and it booted into TWRP, however it found the update and installed it!
I kind of wanted to keep it stock, but updated stock so I went for a bigger upgrade to Android 7 firmware. This only worked partially and (stupid and I know better) forgot to do a backup. I did not know that TWRP was gone and root was gone. The battery died and I rebooted like normal and there was a much improved interface. However, a good bit of stuff stopped working like bluetooth and the boot screen was in red stating the device can't be verified and ended up in something like a NOR905 test keys build. I did a backup, selected a downgrade package that was checked and "updated" to the downgraded firmware through Project Menu. It successfully stated it was 100% complete.
Now it is stuck on the boot screen for an unlocked device.
What works (or is possibly a good thing):
The hardware keys can get me to the bootloader (fastboot)
ADB recognizes the device is in fastboot
Phone is Unlocked
FRP is unlock
What doesn't work:
Everything else. All I have is fastboot and an unlocked bootloader. I can try to flash recovery but that never boots, it just stays suck on the recovery boot screen. The system will not boot at all.
UPDATE:
I broke down and spent the money to use the DC-Phoenix software to unbrick the phone. Several of the options for firmware did NOT work. The one file set that did work was to use this firmware:
VIE-L29_C900B101_Firmware_countryValue_Nonspecific_Android_6.0_EMUI4.1
Then use this as the customization:
update_data_C900B101_hw_default
The phone originally started out as VIE-L29C636B130. This changed it to VIE-L29C900B101 and is on EMUI 4.1 android version 6.
Now the fun part is going to see if I can find a version of TWRP that will work and see if I can root it. Maybe even try a custom ROM. We'll see though. The device is just an old beater for fun. But at least, she's not broken anymore. Guess I'll grab a beer and celebrate my "unbricked" device.
I have encountered device corrupt error on my pixel 4Xl few days back.. In few instances device worked normally for few hours but kept on switching off and getting the same error as device corrupt. I did factory reset once when I could switch on the device as suggested but currently issue is still persistent. I am using original OS Android 12 with latest Nov security update installed. I have never sideloaded any apps or done any changes to my OS. Device is always upto date with updates available. Please help me with any resolution to fix this issue. Currently my phone is out of warranty by few months.
@Prudhvi89
Sounds like your bootloader is locked? If you have done a factory reset and the issue is still there it is more than likely a hardware issue you cannot fix. You could try flashing a full OTA image from recovery mode using adb on your computer. If this sounds like too much, I would still call Google. I have had my phone replaced twice, once outside the warranty. Just explain everything you have done so far (they may ask you to factory reset again to verify) but you may end up being covered out of warranty. It is definitely worth a try.
Hello,
did you do an OTA update before your problem ? If yes, it's not the right one that you used, in this case, you just have to update again with the right version.
Hey!
Did you try this tool form google: https://flash.android.com/welcome?continue=/?hl=pt-br
It allows you to flash firmware, even if the bootloader is locked. If the botloader is unlocked it allows to make a full firmware flash, if not it flashes only some partitions.
If it doesn't help, and you have the bootloader locked, you will need to use the EDL mode.
More on that on this thread!