When I upgrade rom of CHT9110 by P3600i ROM. I got an error Invalid Vendor ID. And screen now is USB Bootloader. How I can restore to the original rom or is there any rom can upgrade for CHT9110 to support English language
up top......................
up up
up up ...............
I confronted same situation as you before. When i tried to flash my 3600i(HK traditional Chinese version) using "RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship.exe" found in forum, my 3600i finished with same error as yours "Invalid Vendor ID" and stayed on 3-color bootloader screen after rebooting. however, It restored to the original rom after I tried to flash my 3600i with upgrading software "D810_GPS_HK_TradChinese.exe" which got from download link appeared on software update in my Htc e-club. flashing "D810_GPS_HK_TradChinese.exe" failed with something like "wrong model" then my 3600i rebooted automatically and restored to the orginal state. I hope my case could do a little help to you.
also found the following from readme.doc in "RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship"
8. Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter CE OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It’s normal and can be recovered. Please follow the instructions below to reset your device and to establish a connection with the computer.
1. Disconnect your Mobile Device from the USB cradle/cable.
2. Reset your Mobile Device.
3. Reconnect your Mobile Device to the USB cradle/cable.
4. Check that the communication cradle/cable is connected properly.
5. Return to the ROM Update Utility.
Note: You should ignore the ActiveSync connection.
So... I flashed chromatic 4.0 and have been using that for a few days. I like it... I used the ROM Manager app to flash the Clockwork recovery so I could utomatically check for updates...
Last night my phone froze so I hard reset it and it got stuck at the custom boot image... so I reset it again holding down to go in to recovery... didn't go and would not reset...
Did some research and found that other people have been having that issue and all I would have to do is delete the recovery through fastboot... always had some issues with my phone getting recognized and that kind of stuff. I followed the directions in the tutorial... I got it from unrecognizable to it saying ADB Interface with the sub of Android 1.0 in the device manager... first, is that right? then when I open the command promt... I can't get it to list "fastboot devices"... I tried erasing the recovery anyway and it just says "waiting for device." I don't know if I turned "debugging on" previously...
*edit* it says to reinstall the drivers but when I try it says it cant find them...
main question... Am I screwed? or is there another way to erase the recovery?
sorry
I will read below... another thread addresses my issue kinda... didn't see it before... sorry
THE BEAST WAKES!
wooo!
Hello everyone!
After successfully rooting a Motorola Defy and a Galaxy Y I thought I would help a friend root his Nexus One (2.3.6 GRK39F):
- unlocked the bootloader
- applied boot img via fastboot as described here: code.google.com/p/bexboot
However there is a big problem: the Wifi will not turn on; when attempting to turn on it will just display the status "Error". With my limited knowledge I tried to fix it:
- used an app called "FXR WiFi fix and rescue" : FAILED
- tried flashing an older baseband - 5.08 (it had 5.12) : FAILED
Now I have no more ideas on what to try (to be honest I am afraid to try more things because I don't know the actual cause of this error and don't want to damage the device).
Any ideas or guidance that you can provide will be highly appreciated.
Thank you!
kwhiper said:
Hello everyone!
After successfully rooting a Motorola Defy and a Galaxy Y I thought I would help a friend root his Nexus One (2.3.6 GRK39F):
- unlocked the bootloader
- applied boot img via fastboot as described here: code.google.com/p/bexboot
However there is a big problem: the Wifi will not turn on; when attempting to turn on it will just display the status "Error". With my limited knowledge I tried to fix it:
- used an app called "FXR WiFi fix and rescue" : FAILED
- tried flashing an older baseband - 5.08 (it had 5.12) : FAILED
Now I have no more ideas on what to try (to be honest I am afraid to try more things because I don't know the actual cause of this error and don't want to damage the device).
Any ideas or guidance that you can provide will be highly appreciated.
Thank you!
Click to expand...
Click to collapse
Did you flash a correct boot image? Try to flash a standalone kernel or clear data and cache in wifi settings and then do the set up again.
taodan said:
Did you flash a correct boot image? Try to flash a standalone kernel or clear data and cache in wifi settings and then do the set up again.
Click to expand...
Click to collapse
Yes I flashed the correct image. After several more attempts of fixing this (having read countless forum posts and guides) I gave up and flashed latest stock then rooted with Superoneclick. All is well now.
Thank you! Considered SOLVED.
reboot your phone
I m new at this, I had the same error when trying to use wi-fi after rooting. I could get it fixed after a reboot.
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
You might want to try flashing the update manually, using ADB and Fastboot. Doing so will wipe your device, so if you have anything in the internal storage, back it up if you can.
I try flashing manually via adb/nexus toolkit and it just says error code 7 on the phone. The device is bootlocked.
this may help
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
I have no backup, the phone is under warranty and as this has happened before. Stock update killed phone, i'm taking it to vodafone today.
I can't be bothered to mess about when my contract comes with warranty
Good thinking...
Didgeridoohan said:
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
Click to expand...
Click to collapse
Exactly same problem, struggling for a day now.
unable to unlock bootloader for flashing the device
"fastboot flashing unlock" returns OKAY but the screen still shows "Device is LOCKED. Status Code: 2"
any suggestions??
Try "fastboot oem unlock".
Strephon Alkhalikoi said:
Try "fastboot oem unlock".
Click to expand...
Click to collapse
"fastboot oem unlock" gives:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
But of course I can't do that as I cannot get it to start. I tried "adb sideload image-shamu-mmb29x.zip" too, but it fails for signature verification probably because it shows I have "MMB29V" on the phone. Downloading "MMB29V" image now, will try that too.
With your bootloader locked, you cannot flash factory images using fastboot, and ADB is not for flashing factory images. You have to flash the Android N preview as an OTA in recovery to restore your device to an operable state. Once Android N finishes optimizing apps and is booted, you need to go into the hidden Development Options menu in Settings and tick "Enable OEM Unlock". Then you can unlock the bootloader in fastboot with the command " fastboot oem unlock" so you can flash factory images.
Aston Martin said:
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
Click to expand...
Click to collapse
Got into the same situation yesterday. Seems like it was not just a security update (it didn't say so though), but it was update for the Android-N preview.
Wasted a whole day trying to figure out what did I do to brick my phone. In the end it was just the stupid update by google.
The solution to the problem now is to update your phone to Android-N preview OTA update - you can get it from here: http://developer.android.com/preview/download-ota.html
aHR0cDovL2RldmVsb3Blci5hbmRyb2lkLmNvbS9wcmV2aWV3L2Rvd25sb2FkLW90YS5odG1s --> base64decode this to get the link [new users not allowed to put direct links ]
Steps for solving your problem:
Connect your phone to the computer
On your phone go to the No Command screen and press the three buttobns (Vol-UP + Vol-DOWN + POWER) simultaneously [it will take a couple of tries before you succeed]
You will now reach the Android Recovery screen
Select the option "Apply update through ADB"
From the computer execute "adb sideload <OTA_UPDATE_FILE_NAME>.zip"
Wait for a few minutes and you will see the update progress on adb
Here OTA_UPDATE_FILE_NAME.zip is the name of the ota-update file you download from the developer.android.com link [given above as base64]. For Nexus 6 it is - shamu-ota-npc91k-201dd8d1.zip
Hope it will save someone a lot of their important time.
Well, I am having the same issue as OP. Stock Android on Nexus 6 (t-mobile), received OTA security patch last night. Checked that I have a little over 1GB storage left (24.90GB out of 25.98GB available) and proceeded with installation. Now it says "device is corrupt" and after the four rotating colorful circle animation it gives me the "Unfortunately, Settings has stopped" message box over and over again which I cannot get past. I tried safe mode and it hits the same error.
I am trying the manual OTA update now as ravikumr posted, but I suspect it may run out of storage space since the zip file is 855MBs. Any way I can go in and clean up some space before the installation?
If the reason the original OTA update failed was due to insufficient storage, that would be a really stupid way to annoy the user. I have been reasonably happy with my phone so far but this experience today sucks. I depend on the phone for a lot of things so I never tried to root it or modify in any way, but I guess that's still not enough to make the phone reliable.
I will post my results with the manual update.
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Target: google/shamu/shamu:N/NPC91K/2751853:user/release-keys
Patching system image unconditionally...
Verifying the updated system image...
E:unknown command [retry_update]
system partition has unexpected contents after OTA update
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Anyone has suggestion I can try?
I couldn't wait since I needed the phone to work so I did factory reset. I had to do it twice since the first time it looked hung formatting /data (I waited over an hour) but second time it went through fairly quickly. Afterwards it was stuck on the google logo at boot, probably due to the bad system. I reinstalled the Android N preview OTA patch and it successfully completed this time, and I was off setting up the phone again.
I am still not convinced that what I have experienced was not a simple mistake that whoever put this package together forgot to put in code to check for available storage space before allowing the installation to proceed, or it could be a bug that when space ran out the installation code didn't handle it gracefully and started to do bad things. Either way it was a bad experience for me. Luckily I saved all my pictures and videos a week ago so only lost a few pictures plus other data.
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Kam_El said:
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Click to expand...
Click to collapse
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
mikeprius said:
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
Click to expand...
Click to collapse
This worked for me, specifically with the update issue on a fully stock and OEM locked Nexus 6 that became buggy after the update was attempted but there was not enough memory. After the update failed and it booted back up (there was an error your device is corrupt message on bootup) there were a ton of error messages and the settings app was broken. Package installer was also broken and Google play and media services were broken, therefore couldn't use the Wugfresh Nexus toolkit, couldn't use fastboot as OEM was locked and couldn't access settings to change it. Factory reset from stock recovery did not fix the errors and following bootup the startup wizard couldn't start either.
The only option was to sideload the OTA - however, for the Nexus 6, after the OTA installed the OEM unlock option was transparent and set at off (because my bootloader was always locked). I then enrolled the device on the Beta programme, and then unenrolled it. Almost immediately a downgrade able OTA notification arrived which dropped it back down to Marshmallow. After bootup all seemed fine, then play services stopped working. I was worried until I recieved a notification for a Marshmallow update - after that was installed everything worked fine as normal. The OEM unlock option was again available (although I decided to keep it locked).
For other devices it won't work, as I believe the Android N OTA is for a select few Nexus devices and possibly GPE devices (full list available on the website above).
Whether this work if you've completely deleted the OS - again I'm not sure. But I cannot see the harm in trying in that scenario. More experienced users could assist here. It should work as long as you can get into stock recovery.
Hope this helps.
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
lyuanrich said:
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
Click to expand...
Click to collapse
Glad to have helped. I had already attempted a factory reset before momentarily losing hope lol. Incidentally I'm now running N on my Nexus 9 - loving the new notifications.
Anyway ✌?