Re: COMPUTERS, THE AGONY AND THE ECSTASY
Posted: 09 Apr 2015, 12:59
Part of the benefit of modern technology is that there is always lots of information on the internet for the various platforms for devices and such. If you have a reasonable amount of technical nous many faults can be sorted without having to resort to manufacturers service and repair facilities.
I had an appeal from a friend with a busted Google Nexus tablet to see if I could help her out and recover the device. It had failed during its update to the latest version of Android (Lollipop) and was stuck in what was effectively a boot loop. Pushing the start button started the boot process but it halted when trying to load the desktop and just sat there rotating the little coloured Google balls. Forcing a restart just brought it back to the same position, all does not always go smoothly in some areas of Linux land it would seem.
There are a number of different models of the Nexus as the device has evolved. A problem with one in a situation such as this is that you cant determine exactly which model it is or which version of the OS it is running unless it is booted up. It soon became clear by trolling the various support forums on the web that there are numerous versions of each release of the Android OS depending on the chipset of the device it sits on. Nexus devices have been manufactured by Samsung, LG and Asus. You need to determine the build information in order to select the right software for the device.
Jill had brought it in is box but the information on the product label dis not give the full story of the device. It had a date of manufacture which said January 2012 but no hint on which particular genre it was. I scanned all the barcodes on the labeling but nothing definitive was produced so I had to make an educated guess on which OS image to download for the device. The ultimate object was to upgrade it to the latest version of the OS but I thought it would be best to recover it back to its original build first in order to prove that the hardware was in good order, there were a few hardware issues noted in the forums which could actually give the same symptoms so I thought this would be the best course.
The process of recovery involves gaining control of the device during the boot strapping process and then flashing the device with a new OS image of the correct release for the targeted hardware platform. You need some form of software to handle the control and flashing of the device so I hunted around on the forums and after a bit of homework settled on an open source utility called "Nexus Root Toolkit", this looked to be a well established bit of software with plenty of support should things go wrong.
Going off the manufacture date on the label I assumed that the device would originally be running Android KitKat and that it was an Asus built device. I downloaded the required image, attached the Nexus to my laptop via USB, ran the toolkit and booted the device into its service menu. This allowed me to get into rooting mode and then force load a factory image of it's original OS. I was quite pleased that it all went according to plan until I went for the reeboot after the load. I instigated the command from the toolkit, the device rebooted and then died completely! It was now no longer stuck in a boot loop but completely dead in the water, a condition known in the trade as "bricked".
Back to the forums with much head scratching. To rule out a corrupted image I downloaded another copy from a different Google distribution mirror, the checksums for the download were all correct so I flashed the Nexus again. Same result, completely dead. I was beginning to suspect that an underlying hardware problem may be causing the fault which would really require that the device was sent back to Asus for service. I continued hunting round the forums for a bit and came across a post that indicated that some devices with dates shown in early months of the year could actually have been built in the latter months of the previous year. If this was the case with Jills, the unit would need an earlier version of the OS.
Nothing to lose at this stage as a bricked device is only useful as a doorstop, a Nexus tablet even less so as its only thin and wouldn't really be effective in that role either. I downloaded a new zipped image for an earlier build and flashed the ROM for the third time. The forums indicated that the first reboot could take 15 minutes to half an hour as the OS is unpacked and installed on the unit so I disconnected it from my computer, reconnected to the charger to ensure a solid power source and left it to do its stuff. Twenty minutes later it had built perfectly and was sitting at the new back to factory out of box welcome screen.
I went through the initial settings to put Jills name back on the device and attached it to my WiFi and Google account so that it could see the Internet and access any updates that it might need having turned back the clock three years on the device. I didn't take it long to determine that it would benefit from the latest version of the OS and it proceeded to download the replacement. I stopped it doing an automatic deployment and instigated the update manually which then installed without any problems, it did take about half an hour to deploy after the download but eventually arrived at the new look Android Lollipop welcome screen.
After a reasonable amount of testing for functionality and giving it a full discharge / charge cycle I removed my Google account settings and gave it back to Jill. I left my WiFi settings on it in case it comes back but it obviously disconnects once out of range. It would find her settings once back at her home. That was about six weeks ago and having seen her since, all appears to be well and she is very happy with the upgrade.
I can recommend the Nexus Root Toolkit that I downloaded as a fully featured bit of freeware for interacting with these types of devices. You can use if for all Nexus devices and other Android types including some models of smartphones.
I had an appeal from a friend with a busted Google Nexus tablet to see if I could help her out and recover the device. It had failed during its update to the latest version of Android (Lollipop) and was stuck in what was effectively a boot loop. Pushing the start button started the boot process but it halted when trying to load the desktop and just sat there rotating the little coloured Google balls. Forcing a restart just brought it back to the same position, all does not always go smoothly in some areas of Linux land it would seem.
There are a number of different models of the Nexus as the device has evolved. A problem with one in a situation such as this is that you cant determine exactly which model it is or which version of the OS it is running unless it is booted up. It soon became clear by trolling the various support forums on the web that there are numerous versions of each release of the Android OS depending on the chipset of the device it sits on. Nexus devices have been manufactured by Samsung, LG and Asus. You need to determine the build information in order to select the right software for the device.
Jill had brought it in is box but the information on the product label dis not give the full story of the device. It had a date of manufacture which said January 2012 but no hint on which particular genre it was. I scanned all the barcodes on the labeling but nothing definitive was produced so I had to make an educated guess on which OS image to download for the device. The ultimate object was to upgrade it to the latest version of the OS but I thought it would be best to recover it back to its original build first in order to prove that the hardware was in good order, there were a few hardware issues noted in the forums which could actually give the same symptoms so I thought this would be the best course.
The process of recovery involves gaining control of the device during the boot strapping process and then flashing the device with a new OS image of the correct release for the targeted hardware platform. You need some form of software to handle the control and flashing of the device so I hunted around on the forums and after a bit of homework settled on an open source utility called "Nexus Root Toolkit", this looked to be a well established bit of software with plenty of support should things go wrong.
Going off the manufacture date on the label I assumed that the device would originally be running Android KitKat and that it was an Asus built device. I downloaded the required image, attached the Nexus to my laptop via USB, ran the toolkit and booted the device into its service menu. This allowed me to get into rooting mode and then force load a factory image of it's original OS. I was quite pleased that it all went according to plan until I went for the reeboot after the load. I instigated the command from the toolkit, the device rebooted and then died completely! It was now no longer stuck in a boot loop but completely dead in the water, a condition known in the trade as "bricked".
Back to the forums with much head scratching. To rule out a corrupted image I downloaded another copy from a different Google distribution mirror, the checksums for the download were all correct so I flashed the Nexus again. Same result, completely dead. I was beginning to suspect that an underlying hardware problem may be causing the fault which would really require that the device was sent back to Asus for service. I continued hunting round the forums for a bit and came across a post that indicated that some devices with dates shown in early months of the year could actually have been built in the latter months of the previous year. If this was the case with Jills, the unit would need an earlier version of the OS.
Nothing to lose at this stage as a bricked device is only useful as a doorstop, a Nexus tablet even less so as its only thin and wouldn't really be effective in that role either. I downloaded a new zipped image for an earlier build and flashed the ROM for the third time. The forums indicated that the first reboot could take 15 minutes to half an hour as the OS is unpacked and installed on the unit so I disconnected it from my computer, reconnected to the charger to ensure a solid power source and left it to do its stuff. Twenty minutes later it had built perfectly and was sitting at the new back to factory out of box welcome screen.
I went through the initial settings to put Jills name back on the device and attached it to my WiFi and Google account so that it could see the Internet and access any updates that it might need having turned back the clock three years on the device. I didn't take it long to determine that it would benefit from the latest version of the OS and it proceeded to download the replacement. I stopped it doing an automatic deployment and instigated the update manually which then installed without any problems, it did take about half an hour to deploy after the download but eventually arrived at the new look Android Lollipop welcome screen.
After a reasonable amount of testing for functionality and giving it a full discharge / charge cycle I removed my Google account settings and gave it back to Jill. I left my WiFi settings on it in case it comes back but it obviously disconnects once out of range. It would find her settings once back at her home. That was about six weeks ago and having seen her since, all appears to be well and she is very happy with the upgrade.
I can recommend the Nexus Root Toolkit that I downloaded as a fully featured bit of freeware for interacting with these types of devices. You can use if for all Nexus devices and other Android types including some models of smartphones.