Related
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
mrchew1982 said:
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
Click to expand...
Click to collapse
It's not bricked.
No need to open at this point.
The links you have looked at are very good starting point.
you may need to put your tablet in APX mode to NVflash a recovery.
APX is power off. Power on with VOLUME (-) (not vol+) and hold until a black screen pops up.
If you have the correct drivers, your PC should recognize the tablet.
You can run the nvflash.bat at this point
I recommend using the method HERE. This is one of the ORIGINAL NVFlash posts for the GTab. I have also posted my own nvflash folder for windows users HERE there is both a 1.1 and 1.2 bootloader version up there.
APX mode blues
Thanks for the quick replies.
I have re-flashed the tablet using APX mode about 20 times already. Both 1.1 and 1.2 branches. With and without cwm. Multiple tries with each image to make sure that there wasn't an error.
I have used the "FORMAT" flash as well, received the mismatch error. flashed all four versions of roms (1.1, 1.1cwm, 1.2, 1.2cwm) after redoing the "FORMAT".
Still nothing. It hangs on the boot image. If I attempt to enter recovery mode it hangs after displaying the text. Even if I hold volume+ during flashing so that it will go directly into recovery mode after the flash.
I know that it is taking the flash, one of the images that I tried has the Tegra logo instead of the Viewsonic as the boot screen. NVflash completes every time without error.
I am really at the end of my rope here as I haven't been able to find anyone that couldn't get into recovery after flashing.
Thanks for the help, any further suggestions would be greatly appreciated!
p.s. I tried once more tonight using Roebeet's instructions and the NVflash Pixelrider provided just to make sure that i didn't miss a step. Still hanging on the boot screen...
Try this:
1. nvflash back to a stock ROM (1.1 or 1.2). I strongly recommend bekit's original 1.1 images.
2. power off before the gTab boots into the stock ROM you just nvflashed.
3. put gTab into APX mode and run this command:
Code:
C:\> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go[/B]
The tablet will try to boot into the stock ROM (for the first time).
still no luck!
Thank you very much for the reply. Something new to try! Unfortunately it still freezes up.
recap:
Downloaded the "bekit 1105" image (nvflash_windows_20100500.zip)from Roebeet's sticky and the windows version of nvflash. Unzipped both into a folder on my desktop. 30 files weighing in at 202MB. (ADX drivers for Windows7x64 were previously manually installed through Device Manager)
Started gtab with "volume-" button depressed. Screen flashed on with Viewsonic logo then flashed off. Attached usb cable. Heard connection sound from Windows.
Opened folder previously mentioned, double clicked nvflash_gtab.bat. Clicked "Run" on warning popup.
cmd.exe window pops up:
Code:
C:\Users\Desktop\Desktop\bekit1105>"nvflash.exe" --bct gtablet.bct --setbct --bl
bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:
(did not press key yet...)
turned gtab off using power button. Disconnected usb and pressed key to exit NvFlash_gtab.bat window.
Turned gtab on whilst pressing "Volume-". Screen flashes on then goes blank. Windows plays connect sound.
Ran command:
C:\Users\Desktop\Desktop\bekit1105>nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Formatting partition 7 please wait.. done!
Formatting partition 12 please wait.. done!
C:\Users\Desktop\Desktop\bekit1105>
Click to expand...
Click to collapse
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Waited 10 minutes. powered off using button, disconnected USB. Powered back on, Viewsonic logo appears, black bar flashes onto bottom of the screen, and...
Nothing else happens!
Waited another 10 minutes. Tried to get into recovery mode using "Volume+", still hangs, even with an image on the microsd card. Tried the whole thing over again, still nothing.
The fact that it never reboots after nvflash has me worried that there is something deeply wrong. Is there a way that I could repartition and totally wipe it via nvflash?
This thing is stubborn! Still hoping to find a solution...
Thank you again for the help!
mrchew1982 said:
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Click to expand...
Click to collapse
The ``--go'' parameter to nvflash will cause the bootloader to try to boot into the ROM after the requested actions complete. Without a ``--go'' parameter, the bootloader will wait to further commands and you'll have to power off. If the gTab did not boot into the ROM with ``--go'' then something is wrong.
BTW, does adb work in recovery mode? Run this command:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
and post that text file here if it was any output.
Right now it looks like I'll have to build a custom recovery for you to test things out. In the mean time, try the procedures in this post one by one. See if any of them help. And, stick to bekit's recovery until we resolve this.
Thank you!
Thank you!
I will setup adb later tonight and give it a try. I was reading up on it elsewhere. It will be interesting to see if it responds.
Would hitting the reset button on the motherboard do any good? I have opened the case before to re-solder the power connector...
Thank you, can't say that enough!
mrchew1982 said:
Would hitting the reset button on the motherboard do any good?
Click to expand...
Click to collapse
Try it.
I have opened the case before to re-solder the power connector...
Click to expand...
Click to collapse
Hmm. Now this can't be coincidence, can it? User raywaldo on this board is reporting the same problem after he soldered wires to fix his loose connector. See this thread where I mention this.
Ordinarily, based on the symptoms, I would've said that this was a bootloader incompatibility problem. But, both of you have done a full nvflash, so that's out. I'm leaning towards a HW fault right now, but, we'll need more data to make a definitive determination.
As I said, try out the other procedures first (and don't have a micro SD card with the CWM update file in it while you're doing those procedures--the stock recovery will try to install update.zip files if it finds them; CWM will not). If none of them work, then I'll send you a custom recovery image which will let us know if the bootloader did actually load and run the recovery/std kernel.
no adb. reset didn't change anything.
Thank you for sticking with me rajeevvp.
I installed the android sdk (and JDK) per the instructions:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
I used SDK manager to download the platform tools and the google usb driver. Followed the instructions to uninstall the NvFlash driver and installed it as a composite ADB per the instructions. When i started the tablet normally it loads the usb storage device drive and assigns it drive letter E: (which never shows up in "My Computer" and says "Device not ready" from cmd prompt).
It would only connect as an ADB device when i put it into APX mode, which i don't think is right...
It showed up under USB deview, but said that the driver was winusb.sys, which doesn't sound right to me either...
used the echo command, ran "adb kill-server" and "adb devices". it didn't show anything connected.
next i tried the command that you posted and it said "access is denied".
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
I am looking for damage on the PCB but haven't found any yet. I will desolder the power connector later tonight and give it a bath in some PCB cleaning spray.
Thanks for your help once again!
mrchew1982 said:
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
Click to expand...
Click to collapse
Try that adb command on Linux; Windows is too much pain--don't want to troubleshoot an "ADB is not working" problem too.
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
Click to expand...
Click to collapse
Go through this thread as well.
OK. Now for some troubleshooting.
1. Remove any external microSD cards, as always.
2. Put gTab into APX mode and run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go[/B]
This will format all the problemmatic partitions and then upload CWM-2.5.1.1-bekit-0.8 with a different kernel onto both the "recovery" and "boot" partitions. The kernel has been modified to print boot-up messages as it does on standard Linux. If the bootloader loads and runs either kernel ("boot" or "recovery") then you should see, first, the 2 penguins logo (one for each processor), and then, the kernel messages below that. After the kernel finishes, /init will run, clear the screen, and print "ANDROID" in small caps, and then CWM should start.
3. Use the bootloader.bin--which is from 1.1-3588, the last VS 1.1 update--and the recovery.img in the zip attachment.
surgery done...
I wasn't happy with the solder joints that I laid on last time, it looked like I might have bridged two of the pads... so I removed the power connector completely only to find that the housing was split down the middle. Found a new connector (perfect match here: http://www.dcpowerjacks.net/catalog/index.php?main_page=product_info&cPath=15&products_id=202), got it today. Cleaned the pads and carefully connected the new one. sprayed everything clean, it looked great afterwords, but no change in behavior... I didn't see anything loose or missing either when I went over it with the magnifying glass.
Ok, reflashed per your instructions. here is the output:
Code:
C:\Users\Desktop\Desktop\bekit1105>nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928940/928940 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Formatting partition 7 please wait.. done!
Formatting partition 8 please wait.. done!
Formatting partition 9 please wait.. done!
Formatting partition 10 please wait.. done!
Formatting partition 12 please wait.. done!
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
C:\Users\Desktop\Desktop\bekit1105>
It rebooted into the screen that you described but stopped short of going into clockwork. for a long time the last lines were:
Code:
19.213803 so340010_kbd: probe of so340010_kbd failed with error -1
19.217161
19.217164 I2C Slave is *New*
19.820563 NvOdmMouseDeviceOpen failed
20.019509 android_usb Gadget: high speed config #1: android
I then heard the USB connection sound and windows notified me that a USB storage device had been installed (no drive shows up in "My Computer").
Then it started reprinting an error message about every 5 minutes:
Code:
257.010389 INFO: task cpufreq-dvfsd:286 blocked for more than 120 seconds.
257.013674 "echo 0 > /proc/sys/kernal/hung_task_timeout_secs" disables this message.
257.016995 cpufreq-dvfsd D c050ac38 0 286 2 0x00000000
{continued from reboot}
246.807349 Backtrace:
246.810534 (<c050a11c>) (schedule+0x0/0xc18) from (<c00e1680>) (kthread+0x70/0x90)
246.813892 (<c00e1610>) (kthread+oxo/0x90) from (<c00c8498>) (do_exit+0x0/0x73c)
246.817285 r7:00000000 r6:00000000 r5:0000000 r4:0000000
366.817615 INFO: {then it repeats verbatim}
After repeating 3-4times then it goes to a page with just a bunch of numbers inside of parenthesis on the left hand side (counter overran the buffer?) and no text on the right.
When I rebooted it without the USB attached the last message shown is "NvOdmMouseDeviceOpen failed" before it went into the "INFO" error messages.
Still think its a hardware problem?
I will get a linux boot CD setup to try ADB mode again, but i'm hoping that the messages above will be enough to figure this out.
Thank you, once again, for your time and help.
pictures...
Just in case I missed something, I attached some screenshots.
they are in chronological order, 989 is before the "INFO:" error messages pop up, 990 shows those error messages, and 991 is the final screen with no messages.
Thanks for the screenshots. Judging from the visible kernel messages, this looks very much like a hardware fault. The "so340010_kbd" is the driver for the soft keys to the right of the display. The error messages indicate a failure to communicate with the controller for those soft-keys.
I suggest that you start at those soft-key pads and trace the lines back to their controller chip then scrutinize the circuit traces from this chip all the way back to the CPU. See if everything looks OK.
Try ADB on Linux, but, I don't hold out much hope for getting anything out of it: The kernel looks like it is having serious problems with the hardware--I don't think it has even got around to starting up the user-land processes. And, don't worry about the INFO messages relating to cpufreq-dvfsd. You can disregard them for the moment.
EDIT: A thought just struck me. It's winter-time over there, right. Did you take the proper precautions while handling the board? It's very easy to fry a chip silently this time of the year over there using ESD: walk on the carpet, pick up a load of static electricity, then toast something with a simple touch. I borked a board like that one time I was there.
bricked
i have been having same problems with my g-tab, i tried the modified recovery and was able to get to clockwork. i tried updating to few roms, i have NVflashed 100 times. Everytime i NVflash, it shows the tapNtap boot screen, it cycles through this for 4 to 5 times, then just shuts off. Then i try to start again, get nothing, can only go into APX mode which i can only do NVflash and just does same thing. So i tried the modified recovery, goes to clockwork and tried installing other roms, installs without problem, but when restart system will not boot at all. Just black screen and can only do APX mode... also tried opening case unplugging battery, pressing reset button on motherboard... i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
theterminator69 said:
i have been having same problems with my g-tab,...
Click to expand...
Click to collapse
If you can boot into CWM and install ROMs, then you don't have the same problem. And, that modified CWM was meant to be a diagnostic aid--it was not intended to be a cure for gTab illnesses.
i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
Click to expand...
Click to collapse
Is the data still there after you "Partition SD card" in CWM? Make sure you remove any external microSD cards from the tablet first.
Hello, I'm having problems trying to "unbrick" my rezound while referring to con247's guide posted here
HTML:
http://forum.xda-developers.com/showpost.php?p=30595790&postcount=26
.
the first problem is it isn't even mounting like it should because in kmsg it keeps showing up only as ttyUSB0 instead of the expected sdX12.
the second problem is the connection is very sporadic (as in it connects and disconnects in under a full second) so when it does get detected which isn't always the case it can't write the entire hboot
here's the output from my latest attempt:
Connect device into emmc partition mode NOW
Waiting device /dev/ttyUSB0.......
Foundit!
dd: writing `/dev/ttyUSB0': Input/output error
4+0 records in
3+0 records out
6484 bytes (6.5 kB) copied, 0.210596 s, 30.8 kB/s
Return code is 256
can ANYONE help me?
I would recommend PM'ing con247 or maybe dmeadows.
Hello,
to cut a long story short I have my device with this configuration:
Smartphone: Motorola RAZR XT910
ROM: 982.124.14.XT910.Retail.en.EU
Kernel: 3.0.8-g7198280 [email protected] #1 SMP PREEMPT
The problems that I am experiencing:
1) Neither Mac, Win, nor Linux detect my RAZR when I connect it to the computer. Weird thing is that RSD (on Win) and Terminal (Linux) seem to detect the phone.
I tried switching ON/OFF USB debugging, Mass Storage, MTP but no luck at all.
2) I cannot root it! When I try to apply the Dan Rosenberg method all I get is:
[email protected]:/tmp/share$ sudo ./run.sh
[+] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Device found.
[+] Pushing exploit...
3791 KB/s (366952 bytes in 0.094s)
4466 KB/s (1867568 bytes in 0.408s)
1559 KB/s (64498 bytes in 0.040s)
4031 KB/s (1578585 bytes in 0.382s)
pkg: /data/local/tmp/Superuser.apk
Success
[+] Rooting phone...
[+] Your phone may appear to reboot. Please ignore this and continue with the exploit.
/system/bin/sh: /storage/rfs0/pwn: not found
[+] Please press any hardware button on your phone.
[+] Don't worry if the phone is unresponsive at this time.
[+] The device will vibrate when the exploit is complete.
[+] Press enter to continue once the device has vibrated.
Then it does not vibrate and no root is applied.
No luck either with this http://forum.xda-developers.com/showthread.php?t=2257137
3) I cannot boot into recovery! When I switch on pressing Power + VolUp + VolDown I get into the screen with robot & red ! triangle but even pressing buttons from there does not take me anywere! I don't know what to do.
4) Last but not least I would like to unlock the bootloader and change kernel. I got to know that this 982.124.14.XT910.Retail.en.EU appears to lock you yet I would like to ask if someone found some turnaround.
Can you help me?
Thanks a lot for the support!
Alberto
albertaz said:
Hello,
to cut a long story short I have my device with this configuration:
Smartphone: Motorola RAZR XT910
ROM: 982.124.14.XT910.Retail.en.EU
Kernel: 3.0.8-g7198280 [email protected] #1 SMP PREEMPT
The problems that I am experiencing:
1) Neither Mac, Win, nor Linux detect my RAZR when I connect it to the computer. Weird thing is that RSD (on Win) and Terminal (Linux) seem to detect the phone.
I tried switching ON/OFF USB debugging, Mass Storage, MTP but no luck at all.
2) I cannot root it! When I try to apply the Dan Rosenberg method all I get is:
[email protected]:/tmp/share$ sudo ./run.sh
[+] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Device found.
[+] Pushing exploit...
3791 KB/s (366952 bytes in 0.094s)
4466 KB/s (1867568 bytes in 0.408s)
1559 KB/s (64498 bytes in 0.040s)
4031 KB/s (1578585 bytes in 0.382s)
pkg: /data/local/tmp/Superuser.apk
Success
[+] Rooting phone...
[+] Your phone may appear to reboot. Please ignore this and continue with the exploit.
/system/bin/sh: /storage/rfs0/pwn: not found
[+] Please press any hardware button on your phone.
[+] Don't worry if the phone is unresponsive at this time.
[+] The device will vibrate when the exploit is complete.
[+] Press enter to continue once the device has vibrated.
Then it does not vibrate and no root is applied.
No luck either with this http://forum.xda-developers.com/showthread.php?t=2257137
3) I cannot boot into recovery! When I switch on pressing Power + VolUp + VolDown I get into the screen with robot & red ! triangle but even pressing buttons from there does not take me anywere! I don't know what to do.
4) Last but not least I would like to unlock the bootloader and change kernel. I got to know that this 982.124.14.XT910.Retail.en.EU appears to lock you yet I would like to ask if someone found some turnaround.
Can you help me?
Thanks a lot for the support!
Alberto
Click to expand...
Click to collapse
Have you installed the latest drivers? Sounds like that's you issue..
And to boot into recovery turn off your device then press power+volume up+volume down and select recovery,when you get to the android with red triangle press volume up+volume down for about 10 seconds I think then let go and you'll enter to the recovery mode.
Sent from my XT910 using xda premium
Thanks for the reply.
Yes, I have the latest drivers installed both on Win and on Mac, as for Linux I guess they are not needed
Yet nothing happens... On Win I keep hearing that notifications sound but nothing shows up. On the RAZR screen I read something like "AT command service start", "AT command service stop" when I plus/unplug it to the PC USB. And that's it
As for the recovery: thanks a lot. It worked although I had to try a couple of times as the device sometimes freezes even during that boot stage.
AztekSoul said:
Have you installed the latest drivers? Sounds like that's you issue..
And to boot into recovery turn off your device then press power+volume up+volume down and select recovery,when you get to the android with red triangle press volume up+volume down for about 10 seconds I think then let go and you'll enter to the recovery mode.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I got the same problem when updated to JB to root the phone. Just try to root again since phone couldnot root first time i tried. Then i run the script again and it was ok...
After several attempts I used a linux computer and did step by step what Dan described in his root procedure.
I found out that there was a last problem which was that the phone was looking for "rfs1" while the "run.sh" on linux was using "rsf0" so I edite the "run.sh" file in the folder /tmp/share (you should find that at line 47):
echo "[+] Rooting phone..."
echo "[+] Your phone may appear to reboot. Please ignore this and continue with the exploit."
$adb shell /storage/rfs0/pwn 1 ---> I modified that into $adb shell /storage/rfs1/pwn
then I saved and re-applied the last part of the ROOT procedure and it worked smoothly.
2) USB connection reappeared!
ersink said:
I got the same problem when updated to JB to root the phone. Just try to root again since phone couldnot root first time i tried. Then i run the script again and it was ok...
Click to expand...
Click to collapse
albertaz said:
After several attempts I used a linux computer and did step by step what Dan described in his root procedure.
I found out that there was a last problem which was that the phone was looking for "rfs1" while the "run.sh" on linux was using "rsf0" so I edite the "run.sh" file in the folder /tmp/share (you should find that at line 47):
echo "[+] Rooting phone..."
echo "[+] Your phone may appear to reboot. Please ignore this and continue with the exploit."
$adb shell /storage/rfs0/pwn 1 ---> I modified that into $adb shell /storage/rfs1/pwn
then I saved and re-applied the last part of the ROOT procedure and it worked smoothly.
2) USB connection reappeared!
Click to expand...
Click to collapse
That's useful info. I always try custom roms and smtimes razr got soft bricked so i flash the firmware again then root again. Every rooting process i stuck first then reroot the phone. This is the situation why at first try phone cannot rooted.
I am trying to unlock my HTC Incredible 4G on Verizon to load a new ROM onto it. All of my attempts have failed up to this point, by using the WinDroid v2.3 automated tool. I get the following output during the process:
Code:
Task:
1) WINDROID USERS CHOOSE THIS OPTION!
2) Set CID to SuperCID (11111111) - Requires Root
3) Revert CID to original state (VZW__001) - Requires Root
4) Re-lock the bootloader
5) Install recovery
6) Put phone into temp-root mode
10) Exit
Choose a task: 1
========================
= Step 1: Temp-Root =
========================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA************ device
Under "List of devices attached" above, you should see your device
listed (looks like HTXXXXXXXXXX).
Do you see your device (Y/N)? y
Now unlock your device and confirm the restore operation.
By the time you are done reading this sentence, it should be safe to
accept the restore prompt on your device. You should not have a backup
password set on your phone, so leave both password fields empty.
If this process is successful, the script will continue. If not, this
shell will run forever and you must exit by closing this window.
When you see this message, the restore is complete. Your phone will
now reboot to what looks like an unusable state (be patient!). A
status bar will show across the top, but there will be no ring unlock.
This is good! Wait for the script to begin step 2: SuperCID.
========================
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
2+0 records in
2+0 records out
1024 bytes transferred in 0.025 secs (40960 bytes/sec)
142 KB/s (1024 bytes in 0.007s)
31 KB/s (1024 bytes in 0.032s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.035 secs (29257 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.011s]
finished. total time: 0.012s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
There are two things I notice here:
1) My phone is not identified as "HTxxxxxxxxxx" but rather "FA**********".
2) It appears to work, with the reading and writing of the files, but then it doesn't work.
One thing that I noticed was that when I go into the bootloader when this does not work, I get the first attachment.
When I go to the "Recovery" option, then I get the second attachment.
It appears that I originally put a ROM or S-off'd and unlocked my phone, but somehow lost the unlock and can't figure out how to fix it.
Any help in figure it out would be appreciated.
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
junkmail9 said:
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
Click to expand...
Click to collapse
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
keithsmessina said:
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
Click to expand...
Click to collapse
Sorry for the delay in response. Looking again at your screenshot in the OP, you are indeed missing the CID. It should appear between "FIREBALL" and "HBOOT":
I have not dealt directly with that one before, but I would imaging that during temproot, you'll need to recreate the directory. I vaguely recall in a post in this forum on how to manually push a different CID via memory chunk. That might be the best approach to rebuild that area so that you can get going again.
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
junkmail9 said:
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
Click to expand...
Click to collapse
Thank you for the suggestions.
1. I tried this, but got the message: "Main version is older." I think I can only do that if my version is lower than the current RUU.
2. I tried the fastboot write, but I got:
Code:
(bootloader) fighter_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) sdcc_init_memory_device done
(bootloader) SD clock freq = 19MHz....
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.172s]
finished. total time: 0.174s
When I tried: adb devices with the phone at "fastboot USB", I didn't see anything, so I think it failed for that reason. I tried killing adb, removing and reinserting the USB, adn then running adb devices, but still comes up empty.
I'm really at a loss, but appreciate the help from you guys.
I managed to figure out the read-inly access. HTC Sync Manager started each time and grabbed the SD card before the script could do anything. I renamed the HTC Sync Manager to stop it from running. Then I re-ran the script and got:
Code:
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
333 KB/s (1024 bytes in 0.003s)
71 KB/s (1024 bytes in 0.014s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.010s]
finished. total time: 0.012s
So, I am still not getting the right CID, but progress nonetheless.
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
wmuflyer said:
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
Click to expand...
Click to collapse
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
The next problem that I am running into is getting an error message when trying to flash the pacman fireball ROM:
Code:
This package is for device: fireballx; this device is .
Really appreciate all the help in getting me to this point.
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
wmuflyer said:
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I realize that I kept running into an issue changing one of the file systems during that first process which meant that only one of them changed: the "Data" filesystem.
The "Internal Storage" filesystem gave me an MTP error, but then said it finished successfully. It stayed as a vFAT filesystem.
I did get Liquidsmooth up and running with PaGapps, but am now looking for a way to resize my partitions, as there isn't much room left to install apps.
People have looked at resizing the partitions but nobody has had any luck. The partition change seems to be the best bet it was set up by MDMower for his CM builds http://mdmower.cmphys.com/cyanogenmod-fireball/ it might give you more information to make the swap. Beeko has stopped work on Liquid Smooth so for current Android 5.x PAC or CM are the choices and they only work with the partition swap. I have PAC on my Fireball but will probably try CM 12.1 soon.
keithsmessina said:
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
Click to expand...
Click to collapse
Excellent! Glad you got it done.
junkmail9 said:
Excellent! Glad you got it done.
Click to expand...
Click to collapse
I've managed to swap the partitions and get the Pacman ROM installed, thanks to the instructions you sent me, wmuflyer. No hiccups with the Pacman ROM, it seems to be polished and working flawlessly. Thanks again for all the help, guys! Really appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1801 (Chinese) and A1811 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original Chinese Firmware with OTA updates.
Click to expand...
Click to collapse
@Neur_User for PACEfied, STRATOSfied projects and other stuff
@Cracklydisc for AmazIT, StratOS projects and other stuff
Capara @1immortal for his great support
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues)
4. Wait to the end of the process and don't touch anything
********************************************************
CN Verge 3.0.12.0 Stock Firmware Installer by Saratoga
********************************************************
1. Connect the watch to the PC
********************************
*******************************
2. Rebooting to Fastboot mode
*******************************
****************************
3. Checking the connection
****************************
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.535s
***********************************
5. Waiting connection in Recovery
***********************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.3 MB/s (9437184 bytes in 1.232s)
system.img.gz: 1 file pushed. 5.1 MB/s (318817711 bytes in 60.127s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.002s)
flash_rom.sh: 1 file pushed. 0.2 MB/s (458 bytes in 0.002s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.924353 seconds, 9.7MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 96.290046 seconds, 8.6MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
*************************************
10. Changing language to Chinese
*************************************
List of devices attached
d41e250a device
**************************************
Stock recovery installation process
**************************************
********************************
11. Rebooting to Fastboot mode
********************************
***************************
12. Booting temporal root
***************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.373s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.422s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.2 MB/s (687 bytes in 0.003s)
recovery.img: 1 file pushed. 2.8 MB/s (16777216 bytes in 5.662s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Done. OTA updates should now work.
*******************
15. Removing files
*******************
***************
16. Rebooting
***************
************
17. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
* Step 14 may be different for you
Click to expand...
Click to collapse
Latest version
Stock CN/Chinese 3.0.43.0 Firmware Installer with OTA updates | Mirror
Previous versions
Stock CN/Chinese 3.0.29.0 Firmware Installer with OTA updates | Mirror
Stock CN/Chinese 3.0.12.0 Firmware Installer with OTA updates | Mirror
Stock CN/Chinese 3.0.10.0 Firmware Installer with OTA updates | Mirror
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual Installation Method
Manual Installation Method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in Post #1.
On your terminal, go to the path where all the files were unzipped and you are good to go.
Manual command installation
You can copy and paste all needed commands.
Firmware installation
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery-mod.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.426s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.303s
5. Wait until you get a triangle with an exclamation mark (!) in your watch
6. Copy the files to the watch (it may take upto a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
adb push boot.img /data/media/0/
7546 KB/s (9437184 bytes in 1.221s)
adb push system.img.gz /data/media/0/
7194 KB/s (228153632 bytes in 30.969s)
adb push md5s.txt /data/media/0/
88 KB/s (91 bytes in 0.001s)
adb push flash_rom.sh /data/media/0/
297 KB/s (458 bytes in 0.001s)
7. Start Firmware installation (it may take up to 2 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.953804 seconds, 9.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 89.945101 seconds, 9.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to Chinese language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language zh
adb shell setprop persist.sys.country CN[/COLOR]
Stock recovery installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-CN-adb-root.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.206s
13. Copy stock recovery files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/[/COLOR]
Output (or similar)
Code:
[100%] /data/media/0/install_recovery.sh
[100%] /data/media/0/recovery.img
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Or if above command doesn't work, do it in 2 commands
Code:
[COLOR="blue"]adb shell cd /data/media/0/
adb shell sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.461221 seconds, 6.5MB/s
Done. OTA updates should now work.
15 . Delete stock recovery installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img [/COLOR]
16. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
17. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Wipe dalvik/cache
Code:
[COLOR="blue"]adb shell reboot bootloader
fastboot erase cache
fastboot reboot[/COLOR]
Do a Factory Reset (You will lose all the data in your watch. Unpair the watch from Amazfit app while doing this?
Code:
[COLOR="Blue"]adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot reboot[/COLOR]
Reserved 1
Reserved 1
I tried flashing back from 3.2.0.5 back.
First error at Step 4 when the recovery-mod.img is flashed to boot and the booting failed.
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' FAILED (status read failed (Too many links))
Finished. Total time: 1.082s
***********************************
5. Waiting connection in Recovery
***********************************
So I have to do manually:
\Verge_Stock_CN_3.0.12.0_Firmware_Installer>fastboot boot recovery-mod.img
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.545s
2nd error is during the flash prompt, ADB exited shell before system flash is completed:
Step 7 no flash system complete message
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.952945 seconds, 9.4MB/s
Flashing system.img
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>
Took me a while to re-connect to shell and reissue the flash command.
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb reconnect
reconnecting c5121c27 [connecting]
Finally able to reconnect to shell
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
# ls
cache
charger
data
default.prop
dev
etc
file_contexts
flash
fstab.watch
init
init.rc
init.recovery.watch.rc
mnt
proc
res
root
sbin
sdcard
sepolicy
sideload
sys
system
tmp
ueventd.rc
ueventd.watch.rc
# ls data/media/0
Alarms
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
WatchFace
boot.img
flash_rom.sh
gpxdata
md5s.txt
system.img.gz
# sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.950465 seconds, 9.5MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.986899 seconds, 8.1MB/s
Finished
After rebooting I am able to receive 3.0.13.0 OTA and install.
apollow2007 said:
I tried flashing back from 3.2.0.5 back.
First error at Step 4 when the recovery-mod.img is flashed to boot and the booting failed.
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' FAILED (status read failed (Too many links))
Finished. Total time: 1.082s
***********************************
5. Waiting connection in Recovery
***********************************
So I have to do manually:
\Verge_Stock_CN_3.0.12.0_Firmware_Installer>fastboot boot recovery-mod.img
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.545s
2nd error is during the flash prompt, ADB exited shell before system flash is completed:
Step 7 no flash system complete message
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.952945 seconds, 9.4MB/s
Flashing system.img
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>
Took me a while to re-connect to shell and reissue the flash command.
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb reconnect
reconnecting c5121c27 [connecting]
Finally able to reconnect to shell
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
# ls
cache
charger
data
default.prop
dev
etc
file_contexts
flash
fstab.watch
init
init.rc
init.recovery.watch.rc
mnt
proc
res
root
sbin
sdcard
sepolicy
sideload
sys
system
tmp
ueventd.rc
ueventd.watch.rc
# ls data/media/0
Alarms
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
WatchFace
boot.img
flash_rom.sh
gpxdata
md5s.txt
system.img.gz
# sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.950465 seconds, 9.5MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.986899 seconds, 8.1MB/s
Finished
After rebooting I am able to receive 3.0.13.0 OTA and install.
Click to expand...
Click to collapse
Glad you were able to install and update.
May I ask for your Windows version and previous ROM version on watch?
Saratoga79 said:
Glad you were able to install and update.
May I ask for your Windows version and previous ROM version on watch?
Click to expand...
Click to collapse
Windows 10 Pro.
Previous ROM was 3.2.0.5 which was converted from 3.0.13.0.
Stock 3.0.14.0 firmware if you want it.
Great work Saratoga79.
My Verge prompted me for an update this morning, I have stock 3.0.14.0 (zh but set to en) on it if you want a copy.
Hi.
Possible to update the ROM image here to 3.0.29.0?
Flashing back from US to CN rom will have to start update from 3.0.14 all the way to 3.0.29.0
apollow2007 said:
Hi.
Possible to update the ROM image here to 3.0.29.0?
Flashing back from US to CN rom will have to start update from 3.0.14 all the way to 3.0.29.0
Click to expand...
Click to collapse
OP updated with 3.0.29.0 Firmware Installer.
Ayuda!
I have the 1801 version of China. With room 3.0.28 of saratoga, but I constantly get request to update to official 3.0.29. So how do I give an update and do not miss the Spanish language?
Sliv33 said:
I have the 1801 version of China. With room 3.0.28 of saratoga, but I constantly get request to update to official 3.0.29. So how do I give an update and do not miss the Spanish language?
Click to expand...
Click to collapse
My ROM is since a week ago based on 3.0.29.0.
Hello people , I have verge that keeps freezing when receiving several notifications and has sever battery drain. I have factory reset and re-installed the English firmware . But doesn't seem to help.
Will installing the latest Chinese firmware help.
Than I can install the last english os .
Could this help
cetuss4 said:
Hello people , I have verge that keeps freezing when receiving several notifications and has sever battery drain. I have factory reset and re-installed the English firmware . But doesn't seem to help.
Will installing the latest Chinese firmware help.
Than I can install the last english os .
Could this help
Click to expand...
Click to collapse
Not sure but you can give it a try.
For this Version
Can change language Chinese >> English without error
Have anybody any news/information when will be official update from Amazfit for Verge (International version) with integrated Alexa or other voice assistant for the rest of the world costumers like: Europe countries and ect?
Can i use NFC function on A1811 with Chinese stock rom?
I heard there are NFC chipsets in A1811 too
Flashing chinese bootloader on A1811 bricks my watch??
vsc0705 said:
Can i use NFC function on A1811 with Chinese stock rom?
I heard there are NFC chipsets in A1811 too
Click to expand...
Click to collapse
No, you can't, AFAIK, but you can give it a shot. I think there is no NFC, since NFC can't be enabled on CN Firmware. There is a dedicated switch for that in the firmware, but it's reported that NFC doesn't turn on for A1811. for A1801 it does.
vsc0705 said:
Flashing chinese bootloader on A1811 bricks my watch??
Click to expand...
Click to collapse
No, it doesn't.
Saratoga79 said:
I think there is no NFC, since NFC can't be enabled on CN Firmware. There is a dedicated switch for that in the firmware, but it's reported that NFC doesn't turn on for A1811. for A1801 it does..
Click to expand...
Click to collapse
NFC is in Verge http://cn.amazfit.com/verge.html before you post asnwer, check information in official web site - it's easy and no need a lot of time :highfive:
As i know NFC will be available later (if talk about US market), why is not activated in China's version i don't know. As i understand NFC is available only for payment process, so everthing maybe working somehow automatic. I can't explain reasons, but as i mentioned web site and others official source saying that NFC is in Verge (Chinese software) and will be later in International (i guest they mean US market only for this moment)
P.S. This is official Amazfit Verge commercial https://www.youtube.com/watch?v=PydD99xx2dk, look what doing guy in commercial from 34 second, he doing payment. Payment process is doing with NFC, what is meantioned in Amazfit web site So yes chinese version must have NFC available, why is not, need to ask Amazfit, but i guest, cos costumers which flashing Chinese ROM is not from China and maybe somehow by GOS is detecting that is not China country and features is not available. It's nonensese probably you will say, but when please explain me why the same software version for International costumers with Alexa working only in US, i got this software with Alexa, but i can't use Alexa, cos i'm not from US, if say exactly i'm not right now in US... I guest in the say working NFC. But maybe i'm wrong
About A1811 i guest you are right, i did not tried, but probably as i mentioned will not works, cos somehow *probably by GPS) this watch is really smart and detecting what you are not in the same market in which these features working If i understand you wrong, sorry, english is no my primary - national language
xdauser2019 said:
NFC is in Verge http://cn.amazfit.com/verge.html before you post asnwer, check information in official web site - it's easy and no need a lot of time :highfive:
As i know NFC will be available later (if talk about US market), why is not activated in China's version i don't know. As i understand NFC is available only for payment process, so everthing maybe working somehow automatic. I can't explain reasons, but as i mentioned web site and others official source saying that NFC is in Verge (Chinese software) and will be later in International (i guest they mean US market only for this moment)
P.S. This is official Amazfit Verge commercial https://www.youtube.com/watch?v=PydD99xx2dk, look what doing guy in commercial from 34 second, he doing payment. Payment process is doing with NFC, what is meantioned in Amazfit web site So yes chinese version must have NFC available, why is not, need to ask Amazfit, but i guest, cos costumers which flashing Chinese ROM is not from China and maybe somehow by GOS is detecting that is not China country and features is not available. It's nonensese probably you will say, but when please explain me why the same software version for International costumers with Alexa working only in US, i got this software with Alexa, but i can't use Alexa, cos i'm not from US, if say exactly i'm not right now in US... I guest in the say working NFC. But maybe i'm wrong
About A1811 i guest you are right, i did not tried, but probably as i mentioned will not works, cos somehow *probably by GPS) this watch is really smart and detecting what you are not in the same market in which these features working If i understand you wrong, sorry, english is no my primary - national language
Click to expand...
Click to collapse
Yes, I know A1801/CN version has NFC, I managed to enable it and I have done some test with 3th party apps but is not usable out of China.
I meant that A1811/International version has no NFC or lacks "something" as flashing Chinese firmware on it NFC doesn't work.
Saratoga79 said:
Yes, I know A1801/CN version has NFC, I managed to enable it and I have done some test with 3th party apps but is not usable out of China.
I meant that A1811/International version has no NFC or lacks "something" as flashing Chinese firmware on it NFC doesn't work.
Click to expand...
Click to collapse
As i know NFC is not just activated yet, if i understand right, coz now is negotiations are under way with markets (probably with companies, where will work services with NFC or something like is, i don't no details), soon must be everything available. But how i mentioned before, probably will works only in US market (like is with Alexa now). Oh well we will see... i hope update will be very soon and maybe with all ours answers
P.S. NFC is microchip which update will not add to watch, so yes NFC is already in yours device, it's just not activated, there is no option to do that yet Keep patience future will show all features... and keep in mind Verge international version is very new, so what you can see in Chinese version, i 'm sure, i hope will be in international version too, just keep waiting patience
Why not working with Chinese software in international version device (A1811 is for all world, except Asia region, as i understand)? I already write my minds, how they are correct i don't know, but idea that not working for reason, coz watch detect somehow (probably by GPS) that you are not in China for me sounds most probable. Why? You got 3.2.20 software update? What was written in it? Alexa that's right? Where is she? Cos working only in US? Are you in US? No, so probably that's reason why is no available for you NFC with Chinese software... But this is just my mind, maybe i wrote totall nonsenses, but i can't to image another reason why with the same software in one market working Alexa in other no, why can't to be the same with NFC and the same software for different market?
By the way are you sure that in Stock CN/Chinese 3.0.29.0 version already was available/activated NFC for China market too? This is second idea which came to head. I really really don't know how Amazfit made software, i mean how it working, so sorry if i wrote something insane, just lound thinking and trying to understand reason