Related
Been having a lot of trouble flashing new roms. Curently running tazz froyo v1.0. Have been able to root, flash many different types of roms (2.1, froyo etc)
But lately been wanting to try out Nonsensikal v4.6 but for some reason cannot get it to load. It'll either get stuck onthe white screen or if it does make it past the boot freezes during the boot animation and will remain stuck for a long time. Have let it go for 30-40 minutes. Batt pull, both wipes reflash and same thing.
So it has to be corrupted downloads. Tried on different computers, same results. Reformatted my card (was already no partitions, fat32 for froyo).
I would like to figure this out as i really want to try nonsensikal ( ran v 3.4 and loved it)
Any ideas? Battery is always fully charged when flashing. Sd card is good.
Maybe it's a computer issue?
Appreciate any responses.
Thannks
Stephen,
Thanks for the input. No setcpu for me anymore. Its only phone but never activated. I can flash other roms. It's just certain ones won't finish booting.
I'll have to verify the md5s and focus on the corrupted download issue.
Thanks again.
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
You did wipe. My mistake.
bftb0 said:
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
Click to expand...
Click to collapse
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Jp50 said:
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Click to expand...
Click to collapse
Let me know if you have tried booting it without the SD card in the phone (the first time you try booting it). If you already said you did that and I missed it, then my apologies.
Some dev ROMs (not all of them) have "USB debugging" enabled in their boot scripts (some don't), so you can sometimes detect what the problem is using logcat. Maybe you do the "wipe-flash-boot without SD card" experiment and at the same time do this:
- Turn phone off
- Plug it in to the PC and bring up a command window
- in the PC, enter the command
Code:
adb wait-for-device logcat > logcat_boot.txt
The command prompt will not return - it will just sit there, waiting for the phone to start up. So, then:
- boot the phone.
Let the phone sit, even if you think it is going in to a boot loop. The "adb" command will also just sit there until you interrupt it. Wait for 10 minutes if necessary.
Hit Ctrl-C in the PC Command window. You should see the command prompt return.
If the phone booted successfully, then you can just delete the "logcat_boot.txt" file.
If the "logcat_boot.txt" file is zero length, that means that the dev did not enable the "adbd" service on bootup, so this particular technique is of no value.
If the phone went into a bootloop and you have a big "logcat_boot.txt" file, I will probably suggest you post it up to a pastebin somewhere (e.g. http://pastebin.com/ ) so we can look at it.
bftb0
ran the logcat test and it returned nothing. phone still won't boot nonsensikal. just freezes on the white screen. battery pull, reboot now its in boot loop city.
i think i've wasted enough time on this rom. I'm running cyanogen Tazz v2.0 and I was able to flash it over v 1.0 with no issues (other than the camera).
I guess nonsensikal rom doesn't like my phone. the dev was a lot of help, but i think the issue is my phone is just ****ed. I can't overclock anything over 604 without it freezing.
Time to move on and get back to having a real life and not obsessing over a phones interface. tazz's rom is more than good enough and I just have to move on. The amount of time I wasted on this is just silly. This phone took over my life and I have to lick my wounds and admit defeat.
thanks for all your help everyone. not all phones are created equal.
My wife and I recently traveled to Chicago and on the bus ride there, she turned off her eris to conserve battery. When we arrived in Chicago, she turned her phone back on and it gets stuck on the screen with the droids on skateboards. We let it sit for an hour plus with no results. I have searched for resolutions on this site, but all I could find were issues with already rooted phones.
When I go into the system recovery, I get a message E: can't open /cache/recovery/command. I wiped cache partition and wipe data/factory reset and rebooted and it still gets stuck.
I also downloaded the latest OTA update and renamed it to update.zip and pasted it on the sd card and tried to apply sdcard:update.zip but I get a message E:signature verification failed.
Is there anything I can do to resolve this problem and get the phone to boot? Is there a way that I can root the phone even though it wont boot up? We went to a verizon store and that was pretty much a waste of time.
Thanks for the help.!!
thats crazy man. you have no nand backup? i got in a bootloop once but i was rooted. i downloaded a random rom and booted to recovery then mounted usb and transfered rom to sdcard then flashed it and it booted right up. i would think if you got the click root program for eris and flashed it in recovery and then flashed a rom it would work but im not sure im no excerpt. hope you figure it out
kd,
The procedure you used (wipe data/factory reset using the stock recovery) should have worked with a non-rooted phone... assuming that all the hardware was still OK.
You should not have experienced a verification failure applying a valid OTA file as an update.zip, but it is not obvious to me that you should be trying to fix the problem that way in any event.
If the phone is under warranty, I think that the right thing to do is contact VZW or whomever sold you the phone about warranty return. Only if there is NOT a warranty available would I consider further "repair" experimentation on your part.
Let me ask a single question before I give any other advise: what bootloader version is on your phone? (You should see this in the HBOOT or FASTBOOT screen); probably it will be one of these three:
1.47.0000 S-ON
1.49.0000 S-ON
1.49.2000 S-OFF
I would advise you to avoid trying PB00IMG.zip or "RUU" rom reflashes at the moment. I can provide "cautious" instructions about how to proceed; but first- what bootloader do you have?
bftb0
I have contacted VZW and the phone is not under warranty so she is pretty much stuck with this phone.
Here is what I see on the bootloader screen:
PB00100 XC SHIP S-ON
HBOOT-1.46.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Oct 5 2009, 19:21:56
Any instructions would be GREATLY GREATLY appreciated!!
Thanks
kdcroswell
kdcroswell said:
PB00100 XC SHIP S-ON
HBOOT-1.46.0000 (PB0010000)
Click to expand...
Click to collapse
This is hopeful.
What I am going to suggest is that you proceed carefully by flashing as little as possible to the phone; the first step is to get the engineering bootloader onto the phone. (In principle, this could allow recovery of 100% of your wife's current configuration and data.) The top-level "outline" of the plan I have in mind looks like this:
- flash ONLY the 1.49.2000 S-OFF bootloader to the phone using the Root PB00IMG.zip file and the "toastcfh" battery pull trick using HBOOT.
- soft-boot a custom recovery to the phone without flashing it (this uses the PC utility "fastboot")
- Immediately make a Nandroid backup of the current contents of the phone.
- Perform a diagnostic "flash" that will report on the state of the MTD partitions.
- Make a decision on how to proceed from that information.
Before we begin, though, we should get a couple of preliminaries out of the way.
(A) You need to have a method to be 100% sure that the files you download to your SD card are in "perfect" condition. If you don't know what a "MD5" signature is, you should review what that means and then download a utility (either from Microsoft, or even better, an opensource GUI tool) to your PC that will allow you to compute "MD5" signatures of files that you download from the Internet.
Simple mistakes in transferring large files to an SD card can cause them to be truncated or corrupted, and this can have disastrous consequences if you flash a corrupted file to your phone. Making sure that you check the "MD5" checksum of the files you download - after you have transferred them to the SD card will prevent this kind of trouble. (This type of error might be what caused your trouble with the "update.zip" you used which failed a verification/signature step)
(B) The method I am going to suggest requires you to work at the command line of your PC, and also get some USB drivers installed. The easiest way to install the drivers is probably to run the "Official 2.1 RUU" Utility right up to the point where you would attempt to flash the phone - but DO NOT actually begin the flashing procedure. You can get that RUU Utility from this page:
Consolidated HTC RUU, Leak, and OTA Downloads
The RUU Utility you are looking for is listed on that page as "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU) - (Eclair/2.1)" -
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
Note that the file size and MD5 checksums are given on the above-mentioned page; use this download to familiarize yourself with computing MD5 checksums with whatever tool you decided to use.
Here's some other downloads that you should pull down to your PC in preparations for all of this:
1) The Amon_RA custom recovery (v1.6.2) - file name: recovery-RA-eris-v1.6.2.img
2) The ROOT PB00IMG.zip file - [ 2.19.605.1 ] Find this in the above URL "Consolidated HTC RUU..." - file name: Eris_RootROM_v2.19.605.1_PB00IMG.zip
3) The fastboot utility for your PC/Mac/Linux machine; you can get this from HTC about midway down this page. (Note that this page also provides you a MD5 checksum.)
I would suggest that you get your PC set up with drivers, and verify that you can communicate with your phone with the fastboot (command-line) utility, before you start doing anything to the phone. This could go smoothly, but probably depends on what O/S version you have on your PC. As I said, the easiest way to get drivers installed onto your PC is to run the RUU Utility right up to the point where you would begin flashing stuff to your phone (but then you exit that utility without actually starting the flashing operation.).
In both cases - the "dry run" of the RUU to install the USB drivers, and the communications check with the "fastboot" tool, you will need to put the phone into fastboot mode; this is done by powering the phone off completely, and then turning it on by holding the Send key and End/Power key together (make sure to press the Send key first). If you do this (and the phone and PC are connected with the USB cable), you can verify communication between the PC and the phone with the fastboot command with:
Code:
fastboot devices
If the USB drivers on your PC have been installed correctly and you are communicating with the phone, the above command will print your "device ID number" on the screen.
Once you get to this point, come back here and give a status update, and I'll provide some further instructions. (Also, since I don't know what your skills are - you might mention whether you are familiar with using the command line or other rooting/phone manipulation methods - reading between the lines, I see that you are more skilled than most of the newbs that come here looking for help)
If you get this all set up, you can also review the following descriptive article (with pictures) on how to do the PB00IMG.ZIP install - including the "battery pull trick".
You can also review a description of how to make a Nandroid backup.
bftb0
PS - One more thing to remember. While the phone is in an unusual state, it is a good idea to keep it fully charged. Don't let it sit in either HBOOT or FASTBOOT modes for extended periods of time - the phone will discharge even if it is plugged in to the charger. You can leave it in that mode for 5-10 minutes, but don't let it sit in either of those modes unattended.
Don't want to threadjack, but for easy MD5 checking on Windows or Mac, you can use HashTab (which is awesome). I can't direct link yet, but: www [dot] implbits [dot] com/Products/HashTab.aspx
I have downloaded the RUU utility and ran it to install all of the needed drivers. I have also downloaded the fastboot utility and verified that the phone and PC are talking by using the code you provided.
I have also downloaded the Amon_RA custom revovery and the ROOT PB00IMG.zip file and verified the MD5 signature for both files.
I read the link on how to do the PB00IMG.zip install including the battery pull trick and the link to how to make a nandroid backup.
I didnt do anything else but verify that the phone and PC are talking and downloaded the files that I will be needing.
I am not real familiar with rooting phones but the instructions you have given me so far are easy to follow.
Now that we verified that the phone and PC are talking, what should I do next?
Thanks again for all your help!!
kdcroswell said:
I have downloaded the RUU utility and ran it to install all of the needed drivers. I have also downloaded the fastboot utility and verified that the phone and PC are talking by using the code you provided.
I have also downloaded the Amon_RA custom revovery and the ROOT PB00IMG.zip file and verified the MD5 signature for both files.
I read the link on how to do the PB00IMG.zip install including the battery pull trick and the link to how to make a nandroid backup.
I didnt do anything else but verify that the phone and PC are talking and downloaded the files that I will be needing.
I am not real familiar with rooting phones but the instructions you have given me so far are easy to follow.
Now that we verified that the phone and PC are talking, what should I do next?
Thanks again for all your help!!
Click to expand...
Click to collapse
OK.
(1)
The first step is to charge the phone fully, and attempt the HBOOT+PB00IMG.zip install, using the "battery pull trick":
- charge the phone completely.
- move the "PB*.zip" file to the SD card top-level folder, making sure it is renamed to "PB00IMG.zip".
- Make sure to verify the MD5 of the PB00IMG.zip file on the SD card - not the copy on your computer.
- Turn your phone off.
- Take the back cover of the phone off.
- With the phone off, pull the battery a couple of times and re-insert it to get familiar with how long it takes to pull the battery. You should try to do this within one second of the screen going dark (please re-review the instruction post on AF). The timing is not super-critical, but when you press the button to start the flashing, the "bootloader" flashes very rapidly - something like 1/4 of a second, and then the screen goes dark. Practicing the battery pull will get you used to it.
- Re-review the instructions in that "Visual Example" post over on Android Forums
- Start the phone in HBOOT mode (Hold Vol-Down+End key).
Hopefully, you will not get a "Main Version is Older!" message after HBOOT unpacks and inspects the PB00IMG.zip file. If you do, proceed no further and report that result.
- Accept the flash (start it), and then pull the battery as soon as the screen goes dark. Do NOT pull the battery before the screen goes black - do it as soon as possible after it goes black.
If this all goes well, you should be able to re-start the phone to see if the bootloader flashing occurred.
DO NOT start the phone in HBOOT mode, because the PB00IMG.zip will repeat again., Instead, after you re-insert the battery, start the phone in FASTBOOT mode: Send+End.
You should see "S-OFF" and "1.49.2000" if the flash succeeded.
(Note: some people have reported that occasionally, the "flashing" process will continue after powering up the phone, even though this is not the desired outcome. I have done the "battery pull" trick with the HBOOT+(Root) PB00IMG.zip install perhaps 50 times, and I think it happened to me twice. If this occurs, don't panic - just let it go to completion.)
(2)
If the flash succeeded, put the phone into FASTBOOT mode (Send+End), and perform a soft-boot of the Amon_RA image:
Code:
fastboot boot recovery-RA-eris-v1.6.2.img
The easiest way to make this work is to have the "recovery-RA-eris-v1.6.2.img" file in the same folder that you have the "fastboot.exe" program in (unless you have changed your PATH environment variable to include that location; in that case you can run the program from any "current directory").
This is one of the features of the S-OFF bootloader: using the "fastboot" program, you can shove a bootable image across the USB connection, and tell the phone to boot it up; doing this does not alter any of the flash memory on the phone. You should be able to use Amon_RA to make an initial Nandroid backup at this point.
I'll add another post to this in a couple minutes.
bftb0
OK.
Now, normally - if the phone in question had not been acting up when it was "stock", we would be proceeding much more rapidly. But, in the past, we have observed cases where just "flashing" a ROM, especially using the RUU utility or HBOOT+PB00IMG.zip method can cause the phone to become a hard brick if there are problems with the flash memory partitions.
So, download the attached "flashable .zip" file: MTD_Inspect_v0.9.zip
File: MTD_Inspect_v0.9.zip
Size: 2,786,881 bytes
MD5: 17a39da9d554bef76930ea0499fc8851
You can transfer files to your SD card when it is in Amon_RA recovery - that is the menu item "MS-USB" toggle. Use that mode to transfer this file ("MTD_Inspect_v0.9.zip") to the root folder of your SD card.
(BTW, since you are using the "MS-USB" toggle feature, now is a good time to rename or delete the PB00IMG.zip file on the SD card - you don't wan't the install to re-start automatically should you accidentally start the phone in HBOOT mode)
(BTW #2, I should mention that your phone will charge when it is running Amon_RA - so it is safe to leave the phone in Amon_RA recovery for extended periods of time - so long as you eventually plug it in either via USB, or on a charger)
You can "flash" this above package after you have transferred it to your phone. It actually doesn't "flash" anything - it runs a diagnostic program to look at the health of your phone's flash memory.
When it finishes, it will create a report file on the SD card named "MTD_Inspect.txt". It will have some lines of text at the top of the file which look like this. Post the top of that report (as shown below).
(I just ran this on my phone - this shows you what the first several lines of that file look like)
Code:
Eris MTD Partition Status Report Generated on Wed Mar 16 05:20:45 UTC 2011
PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS
misc /dev/mtd/mtd0 655360 0 5 0 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 0 20 0 0 0
system /dev/mtd/mtd3 178257920 1 1360 0 0 0
cache /dev/mtd/mtd4 136314880 1 1040 0 0 0
userdata /dev/mtd/mtd5 167247872 0 1276 0 0 0
What I am most interested to look at are the "bad block" counts. Some phones have none; as you can see my phone has 1 bad block in each of the system and cache partitions. (Zero or low numbers are OK - we are just checking here to see if there is anything horribly wrong).
Also, BTW - please report if you saw any errors reported when you make the Nandroid backup. You will see an "E:" and a message on-screen if an error occurs.
bftb0
Hi kd,
It occurred to me that - because you had already performed a "factory reset" procedure using the stock recovery boot - that there is little value in performing a Nandroid backup. (Although, if errors occur during the backup, that information could be useful for diagnostic purposes).
I had been thinking something along the lines of "wouldn't it be great to get hand the phone back to the wife just as she had last used it" - but that is clearly impossible if the /data partition got cleaned up.
So... what you probably want to do is download a ROM file to load onto the phone after we review the results of the "MTD_Inspect.txt" report.
The one that will be most familiar to your wife, and 100% stock, is this one:
[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
It's not even rooted - it literally is identical to the most recent "stock" HTC/VZW code for the Eris. Putting a rooted ROM on the phone is also possible, and there are versions that are extremely close to stock, such as "xtrSense 5.0", if you want to put that on the phone as an alternative. (The phone will be a little snappier in it's behavior.)
Anyway, you might want to download a ROM file, transfer it to the root folder of your SD card, and verify it's "MD5" signature (the copy on the SD card, not the one on the computer).
Assuming that no problems occurred with the Nandroid backup and the "MTD_Inspect.txt" report doesn't indicate huge problems with any of the "boot", "system", "userdata", or "cache" partitions, the next step you will be taking is to flash the ROM file using the Amon_RA menu.
bftb0
Hey bftb0,
I have followed the steps you listed and successfully flashed the bootloader to 1.492000 and performed a soft-boot of the Amon_RA image. I created a nandroid backup without any errors.
I downloaded the attached MTD_Inspect_v0.9.zip file and transfered it to the sd card using Amon_RA custom recovery tool and flashed it. I attached the report it left on the sd card.
bftb0 said:
I had been thinking something along the lines of "wouldn't it be great to get hand the phone back to the wife just as she had last used it" - but that is clearly impossible if the /data partition got cleaned up.
So... what you probably want to do is download a ROM file to load onto the phone after we review the results of the "MTD_Inspect.txt" report.
The one that will be most familiar to your wife, and 100% stock, is this one:
[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
It's not even rooted - it literally is identical to the most recent "stock" HTC/VZW code for the Eris. Putting a rooted ROM on the phone is also possible, and there are versions that are extremely close to stock, such as "xtrSense 5.0", if you want to put that on the phone as an alternative. (The phone will be a little snappier in it's behavior.)
Click to expand...
Click to collapse
I think the wife will be happy with a working android phone. She is currently using an old windows phone (HTC ozone). I think she would be very happy with xtr sense.50 rom if it makes the phone a little snappier. She had complaints about the stock rom lagging between making calls and what not.
After you take a look at the inspect report and don't see anything out of the ordinary, I can give it a shot.
I will wait for your reply.
OK, everything looks normal. (1 bad block in /cache, but I don't know why that would cause a problem)
Go ahead and flash a ROM file after performing a
wipe -> wipe data/factory reset
in Amon_RA.
Watch the screen carefully for any errors (indicated with an "E:")
If flashing of the ROM succeeds, power the phone off with the menu, start it up in fastboot mode (Send+End), and then perform a flashing operation of the recovery partition:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Then, after waiting for all visible activity to cease on the screen, pull the battery, re-insert it, and power the phone up normally. It will take quite a bit longer to get to the initial screen than normal, but that is typical for a first boot.
Let me know if you see any errors anywhere - watch the phone closely through all these steps.
bftb0
kd
I just remembered that - because you did a factory reset with the stock recovery on your phone - you will need to "activate" the phone.
The phone may request to do activation during the initial start up of the phone. I think that any other phone which is registered on that line needs to be switched off for this to work correctly (but am not completely sure, since I don't flop back and forth between phones). I guess that means that the Ozone should be off when you start up the phone.
If you've already gone past that point and need to do it manually, dial *228, and then enter option 1.
Whether this works or not depends on what Verizon did for you when you visited them. (It won't work if they removed the phone from the account) If it doesn't activate, give Verizon a call on another line and tell them "your phone came back from the dead".
bftb0
No errors!!!!
She now has xtrSense 5.0 running on her phone and it booted up!!!!!!
Thank you for all the help you provided!!
We activated the ozone when we got home from Chicago by dialing *228 opt 1.
So after I got the new rom loaded on her eris, I followed the prompts and activated the phone again.
Everything seems to be working normal again!!
I can't thank you enough for all the help you gave me!!
So far, running the xtrSense rom, the only thing that she has noticed different was the internet icon in the apps list. I got her facebook set up without any issues. (thats all she really cares about)
Thanks again for everything!!!
OK, you're welcome.
Sorry we went through a lot of extra effort (I was afraid of a scenario that didn't exist on your phone), but it sounds like your wife had a phone to use in the meantime.
Make sure to get rid of the PB00IMG.zip file (either delete it or rename it or move it out of the top-level folder) so it doesn't cause any disruption should the phone get booted into HBOOT mode.
A couple of other points are worthwhile to make, too.
1) You are an Eris rooter now, whether you wanted it or not
2) If you flashed the recovery ("fastboot flash recovery recov..."), you can now boot directly in to it (the custom recovery) by holding the Vol-Up and End/Power buttons when the phone is turned off.
3) You have means to make complete backups on your wife's phone with Nandroid. Once she has her phone fully configured, you might want to do that once as a insurance policy against further disasters.
Cheers and safe travels,
bftb0
PS It didn't escape me that you had absolutely no troubles with any of this stuff, including the command line, which usually eludes younger windows users. Compute much?
That was no big deal going through the extra effort! I am just relieved that we dont have to puchurse a different eris thru craiglist or ebay.
I deleted the PB00IMG.zip file when you mentioned it in a previous step.
I am going to have to look into rooting my phone now!! It was kind of fun!
I wouldn't say that I compute much. When I was a child and first introduced to computers, there was no such thing as windows. It was all dos. My father is a software engineer so I picked up alot from him back in the dos days.
My wife can't thank you enough for all the information you provided!
Cheers to you!!
kdcroswell
Hello,
I want to send out a Heavy thanks for this thread. I too was able to restore my wife's phone and flashed xtrsense 5.0. All other forums I visited for this topic ended with a verizon exchange and that wasn't possible for me. But right on! this was a tremendous help. Thanks again!
bftb0, I am having the same issue but it seems the process may be a little different for me do to my boot loader.
Mine shows 1.49.0000 S-ON
I did all of the same steps up to the point that I received the error as follows.
"Main Version is Older!" message after HBOOT unpacks and inspects the PB00IMG.zip file.
You advised to Stop and ask for further guidance so I am doing that now.
In advance I appreciate the help. This thread has been more helpful than any other resource I have found so far.
I've been trying to install smoke in a bottle, and when trying to revert back to the original ROM on my G tab, I had issues of it not showing up on my computer when connceted. Now, however, I've run NVFlash...And first it got stuck in an endless boot loop, the N symbol would show up then it would turn off, and restart the process.
I then went ahead and did an NVflash format, a-la http://forum.xda-developers.com/showthread.php?t=974422
Then did a standard NVflash.
Now I get a 'magic number mismatch' with some odd garbled symbols with the occasional V, and refuses to boot at all except into APX mode. I can NVflash it into oblivion, but it still gives that error and has absolutely no indication it is on unless I use NVflash when it's in APX.
Furthermore, it seems to have no recovery mode at all, leaving me wondering if I've managed to just permanently brick this thing.
Wonderful.
If I've managed to overlook something simple, I apologize.
My site.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Start with code red.
You are now my personal e-hero. Thank you so much.
For some reason when I performed the "Code Red" it booted back to normal. Now when I restart it goes straight into APX mode. Any suggestions? Also, when I ran NVFLASH it didn't reformat. It is like I just turned it back on. It runs fine until I try and turn it off. Then it will only start in APX mode.
Don't give up!
Here is a link to the series of steps I used that brought my tablet back to properly functioning state (I too struggled for a while with only being able to boot with nvflash). I saw tonight where the steps worked for someone else as well.
http://forum.xda-developers.com/showpost.php?p=15432280&postcount=19
accidentally posted twice....this one can be deleted.
The problem is I can't boot into recovery. I can only boot in to APX mode. It seems all the fixes are for you to be able to boot into recovery. I have been reading for hours and I am lost.
If you read and follow djab67's procedure carefully you'll see that it will force the tablet to boot into recovery. I use the same technique in my procedure (linked below and has the added benefit of not requiring ADB). I highly recommend you try his procedure as I've looked it over very carefully and it should take care of your problem. If it doesn't please let us know and we'll find you another solution.
My procedure: http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Been there. Don't fret. I've done so many terrible things to my G Tablet and it hasn't died on me yet. I'm pretty sure with the hardware and this community, this tablet is unbrickable.
If you can get into APX mode and your PC will recognize it when you run the NVFlash script, you are ok. If it doesn't see it when you run the script, there is still hope.
I have tried djab67's fix I don't know how many times now. Every time I click on the .bat file it tells me the file is gone. I have tried downloading it from multiple different posts with the same let down on each of them. Could my problem be that my rom is the current 4349 set up?
cryorayne,
I am going to go out on a limb here because it sounds like you are running windows on your pc (based on you choosing to use the ".bat" file instead of the ".sh" file), so hopefully another current windows user can validate my response.
It may be best to run the bat file from within the windows command window rather than trying to double click launch with in explorer (file manager, not the browser). Once at the command prompt you also need to navigate the old fashioned DOS way to your working folder location.
It is extremely important to set up all the files in a location the bat file expects to find them. Open up the bat file for editing and check any file/folder paths that are defined. You may need to change them to point to your nvflash working area.
Another thing to check is to make sure your user account on windows has administrator permissions (not just "standard user"). A while back, when I used windows more heavily, I seem to recall some cases where I had to give myself "system" level permissions to do some types of things. However, I highly doubt you need that level to run a batch file with nvflash.
Hope this helps. The steps worked for me and I have seen where at least one other person has used them successfully, so they should also work for you. Getting all the tools and files in place and set up for your computer is a key to success.
Finally, if your various downloads came from sources other than those I referenced in the write-up, then I suggest re-downloading and checking the hash sums.
Hope this helps.
Re-posted restore guide with a little additional information
Just wanted to let everyone know that I re-posted the restore steps as a thread (as opposed to a "reply" where it sits today). I was hesitant to do that before I knew the steps had worked for at least one other person. Should be a little easier to find now. Also, I added a little clarifying content to help with understanding APX Mode and nvflash use.
I am hoping the community can help with responding to requests for help. I try to read questions and respond, but don't have the time to be as quick as I would like and I know from experience how frustrating it can be to have "soft bricked" g tab.
As I learn additional information I will add content to the thread from time to time. However, I do not plan on changing the original steps (except maybe for format reasons) since they are the exact ones that worked for me.
Thread Link:
http://forum.xda-developers.com/showthread.php?t=1167944
My viewpad 7 is boot-looping, it is restarting before reaching the launcher screen, and also stuck while booting into cw recovery mode. I changed font files of the root before this happened. Any way to restore it's rom without using cw recovery mode? Is it possible to boot from sd card?
Can you boot your VPAD7 into CW Recovery Mode ? (Hold down Vol. UP and Vol. Down buttons and press Power at the same time to get into recovery mode)
Anyway, you most likely need to flash a stock ROM first using the SUTL3_v1.7.9 utility available from Viewsonic and then one of the FM6*.nb0 files - it might not recognize or "see" the device, keep trying & reset/reboot and use that small "reset" button on the bottom if necessary.
Check your FTM (Factory Test Mode) for your Hardware & Software build info - and try to match the closest *.nb0 file for flashing. Hold down Vol. Down while pressing Power to start & run FTM, use tiny pin hole to press & reset device/exit this mode.
I haven't done this in a while, but it will most likely change the device back to unrooted, stock form. And, you will lose all your custom app settings - but it should come to life after a successful flash, restart & give it 5 to 10 minutes to complete initial install & setup - and, you should see your original screen again.
Then, follow steps to get it rooted again, do a NAND backup & set it aside for safe keeping, then reflash your choice of custom Rom, etc. Detailed directions are here on XDA - good luck & let us know if we can be of further help ....
I was making the root to my viewpad 7, and during the process, I took out the cable by accident. And now it's impossible for me that the process finish, it always stuck. Some ideas, please?
luisete123 said:
making root .... and during the process .... took out the cable .... And now it's stuck. Some ideas, please?
Click to expand...
Click to collapse
OMG, okay - relax & take a deep breath ....
It should be recoverable, I think - you will just need to flash the "proper" factory stock ROM first, get it working again & then repeat the rooting process.
First, check your hardware/software version in the FTM mode (it's for diagnostic, flash & download to ROM, etc. ....) & safe to do - hold down the left Volume Down key on top while pressing the Power button with the device off. If necessary, get someone to reset the device (use the smallest pin hole on the bottom of the device.) A pin works best but small paper clip will do.
In a few moment, it will show "Enter FTM Mode" and then display the VPAD7's info -
SWVer=3.410 or whatever is on yours
Model: FM6-0001 or whatever yours say
HWVer: 107 (106, 103 or whatever)
What to do with this info - it will help you select the correct or closest factory ROM to flash & restore your Vpad7 to stock condition, unrooted.
You will need one of the SULT3 or for oldest ROM, maybe SULT2 is better - download & save to PC, unzip the SULT* - and follow onscreen prompt & instructions to select your *.nb0 file.
Another suggestions, since you cannot get into Recovery Mode to wipe dalvik, cache & full system/data first, it might help to flash the *.nb0 file twice - it will take a bit of time, maybe 10 minutes or so and a few more minutes to do its initial boot-up configuration. Be patient - and write down any error messages, etc. if you run into problem.
It's best to take out any SIM card and even mSD card from your device, not required but recommended. When you can boot up again & get pass the Android activation wizard/screen, you can power down - put the mSD card back in and reboot again.
http://vsg.viewsonic.com/ViewPad7/
Good luck - there's a wealth of helpful info posted here, please set aside & take time to read it first & refer to those notes. Good Luck & Cheers - let us know if you succeed ....
A thousand of thanks Letitride!!
Before continue making mistakes, I want to ask if there is any problem to use SULT3 (because I read u posted it before) instead of SULT2, because yesterday, before post my question, I already installed SULT3_v1.7.9...
When I enter FTM Mode, the display shows:
SWVer=3.16R
Model: FM6-0001
HWVer: 106
So now I dont understand. I am a little bit lost, but I think I must to download something else from the viewsonic web that u posted (I can't repeat the link because I am new), isn't it?
Thanks again for your help. I know there are lots of help already posted, but about my problem I didnt find anything, that's why I asked. Thanks!!
Ok, I will explain what I tried, and the next error:
As I said, I already installed SUTL3_v1.7.9, so I used it. I downlodes for the viewsonic web that you posted FM6-316Q-0-1008-A01.nb0, and this is the error that the program said me:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
Maybe I need to uninstall SUTL3_v1.7.9 and try with SUTL2.1_v1.8.4? During the process I don't need to select nothing in the ViewPad screen, do I?
Thanks again!
EDIT:
I installed the SUTL2.1_v1.8.4 (without unistall the SUTL3_v1.7.9, and there is the next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
luisete123 said:
Ok, I will explain what I tried, and the next error:
I installed SUTL3_v1.7.9, FM6-316Q-0-1008-A01.nb0, the error:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
EDIT:I installed SUTL2.1_v1.8.4 (without SUTL3_v1.7.9, and next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
Click to expand...
Click to collapse
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Letitride said:
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Click to expand...
Click to collapse
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I think it was a problem while I was downloading yesterday, because I don't know why, the speed was very very low. Otherwise I can't understand, because in this other laptop that I tried, the Windows is not original, and in mine it is...
So now, as I understand, I can root it without any problems, can't I? I will wait untill tomorrow, because I am on hurry now, and I dont wan't to do any more mistake
I am really greatful Letitride, thanks again!
luisete123 said:
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I can root it without any problems, can't I?
Click to expand...
Click to collapse
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Letitride said:
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Click to expand...
Click to collapse
I am again really thank you! But, I still have the same problem... I am trying to use SuperOneClick v1.7 program, and again get stuck...
I will try with GingerBreak, but I was reading here another post about this program and I will need to read it again, in order not to make another stupid mistake!!
Cheers anyways!!
First time poster, but thought I'd share how I managed to fix my problem, in hope that it helps someone else out.
I recently received the OTA Marshmallow update for my Stock Nexus 9 (unrooted and locked bootloader), but unfortunately it didn't work, and threw me into "bootloop" where it continually tried to apply the update but failed. First off I followed instructions to clear the Cache, which only made the problem worse, as all the tablet would do then was boot into the “swirling colour dots” and do nothing else until eventually the battery died.
After reading several forum posts I discovered that the usual solution is to flash via fastboot, however on a Nexus 9 you need to unlock the bootloader by activating "Enable OEM Unlock" from within Android. As I'm running a 100% Stock Nexus 9 I had never done this, so couldn't flash it.
Eventually though, after having an absolute nightmare trying to get it to work again, I found a working solution! Just use "Apply update from ADB" under Recovery, along with the correct update image!
A lot of what's in the steps below is likely to be known to most of the community, but I’ve tried to keep the steps extra simple so anyone can pick this up.
Steps:
1. Reboot into HBOOT (Hold down Volume Down + Power Button).
2. Press Volume Down to highlight Recovery, then press the Power Button to enter it.
3. Wait until the Google logo goes away, and you should see a picture of an Android laying on it’s back. Hold down the Power Button + Volume Up (very important to hold Power FIRST).
4. On the Recovery page it lists a few details about your version at the top. Note down the 6 character identifier for your device (which is in the format of 3 text characters, 2 numeric, and another text char). For me I was running 5.1.1 before the update, so my identifier was LMY48T.
5. Find the OTA update that upgrades from your current version to the next version. For me I was going from 5.1.1 to 6.0.0 on a Nexus 9, so I searched for LMY48T on Google and found that this was the OTA update needed: https://android.googleapis.com/pack...83199e.signed-volantis-MRA58K-from-LMY48T.zip
6. If you don’t have it already, download and install “Minimal ADB and Fastboot”: http://forum.xda-developers.com/showthread.php?t=2317790 – when it’s installed let it run straight away, and leave the command prompt open you’ll need it in a min.
7. If you don’t have it already, download and unzip the Google USB Driver: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
8. Copy the OTA update file you downloaded to the folder that Minimal ADB was installed in (usually C:\Program Files (x86)\Minimal ADB and Fastboot\).
9. Back on your device use Volume down to get to “Wipe Cache Partition”, and press the Power Button to activate it. If you want to be really sure this will work you should do a “Wipe data/factory reset” too, but be aware you will definitely lose your data.
10. Use Volume up to go to “Apply update from ADB”, and press the Power Button to enter it.
11. Plug your tablet into your PC (if it’s not already). You’ll need to go to your Device settings on your PC and you should see a new device named the same as your device or possibly just “Android”. Go to the Properties of the device and force the Driver to be the ADB Google driver from the Google USB Drivers that you downloaded earlier. (There’s plenty of other longer tutorials on how to do this if you’re having issues)
12. On your PC, in the Minimal ADB Command Prompt (that you should still have open from earlier) enter “adb sideload {NAMEOFOTAFILE}” e.g. for me this was “adb sideload ab835e17c874202049463ccd916f86fede83199e.signed-volantis-MRA58K-from-LMY48T.zip”.
13. Let it run. It took less than half hour for it to install for me, and I’m now the proud owner of a working Stock Nexus 9 with Marshmallow!
So why does this work but applying the stock images via fastboot doesn’t? As far as I can see it must be due to the “signing” of the files. The regular stock Google fastboot flash images don’t include signature information (as far as I’m aware) so they’re rejected as unsafe by the locked bootloader, whereas when you run the OTA update files through ADB sideloading signatures are on the OTA update files, and your device determines that these are safe to install.
Yeah, as long as your system partition is intact, "adb sideload" is a good option. I'm not so lucky...
nothint to do with mine, it doesn't show any OS versione unfortunately.
works well
Hi,
I had exactly the same upgrade failure, despite of a clean stock Nexus 9.
I followed the procedure and it works great for me.
Thank you for this post !
FYI - You don't need to go searching for OTA files on Google. They're all conveniently posted here:
http://forum.xda-developers.com/showthread.php?t=2906492
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
gijosh28 said:
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
Click to expand...
Click to collapse
The same situation, maybe have any other solutions?
I wound up calling HTC and getting an return authorization. I have to pay shipping to them. They cover shipping back to me. But the whole thing is going to wind up taking about 2 weeks. Couple days to get there, 7-10 days to fix, couple back. I haven't sent it out yet. I bought mine at BestBuy, so I was going to see if I could swap it out there first.
Josh
it doesnt show any OS version either, what can i do?
Guide works perfectly. Massive thanks.
The trick is finding the latest OTA zip. Here for the moment.
http://apk-bro.blogspot.com/2015/12/download-android-601-marshmallow-ota.html
I got it to work but I'm never buying another HTC product again. I called warranty service in the first guy refused to help me out unless I had the tablet in front of me. The second guy did help me but I'm still waiting for the RMA ticket, it still has not showed up. So when I got these instructions I managed to resurrect for my Nexus 9 which is good. Now I have a working tablet to which I'm talking to the right now, but other than that HTC still sucks ass and I'm never going to buy anything from them again. Done.
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
harishvr9 said:
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
Click to expand...
Click to collapse
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
harishvr9 said:
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
corkiejp said:
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
Click to expand...
Click to collapse
I did a stock image flash using the Nexus Root Toolkit. But the message is still appearing whenever I restart the device. Otherwise the device is working perfectly.
When I get to step 4, I don't see device identifier text. I got text in pink saying
Code:
" *** Device state - LOCKED *** "
What do I do now
Just got it back from 'repair' via HTC, if anything it's got worse, with random freezes, lock screen freeze and bootloop.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.
Many Thanks!!!!
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
1. Share the link where you like, the Original Finder of this is mentioned in the link
Posted here
2. Have you enabled developer options? Or does Android N not have that feature.
Found the developer options!!
Thanks and yes I found it. I had to reboot my tablet to see the Android version. It must be a bug but I will be happy to deal with a small bug like that. Much better than a bricked tablet. The first thing I did was to enable unlocking of the bootloader in case this happens again. Fool me once but not twice..lol