Related
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
hushpup131 said:
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
Click to expand...
Click to collapse
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
jamcar said:
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
Click to expand...
Click to collapse
I am not able to get into the APX mode. The basis of my belief is there is no audible signal (USB to PC) and there is no new window opening inviting me to explore a new drive.
I have disconnected the battery both short term as well as over night, no response from the power only and power plus volume – buttons.
The charge light has turned green; no response from the buttons.
Measuring the voltage at the charger tip read 12+ volts. I am using a new USB to PC cable. Out of curiosity I unplugged the battery connector and re-connected to see the charge light switch off and on while the charger was connected. As a novice here, I suspect that test eliminated the charging circuit as a fault.
I'm in UBUNTU
loaded and extracted gtab.nvflash.1.1.branch.20110422 with cwmv8.zip
the response says:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
- what does this mean?
1. Is there any sort of display brightening (even briefly?) after you power on? In APX mode, for example, the screen will brighten slightly, then go dead again.
2. Try this test on Ubuntu to see if the tablet has gone into APX mode:
Code:
[I]Power off gTab.
Power on gTab using Power & Vol [-].[/I]
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[18045.279886] usb 1-1.2: new full speed USB device number 6 using ohci_hcd
[18045.384823] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7820[/B]
[18045.384830] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18045.384835] usb 1-1.2: Product: APX
[18045.384839] usb 1-1.2: Manufacturer: NVIDIA Corp.
$
A USB product id of 7820 indicates APX mode on the gTab.
Post the exact output (if any) of your run here.
For reference this is the output when the gTab is running either CWM or the ROM:
Code:
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to the gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[17516.799429] usb 1-1.2: new full speed USB device number 5 using ohci_hcd
[17516.911353] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7100[/B]
[17516.911361] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17516.911366] usb 1-1.2: Product: NVIDIA Harmony
[17516.911370] usb 1-1.2: Manufacturer: NVIDIA
[17516.911374] usb 1-1.2: SerialNumber: 0270308341006257
$
The product id will be 7100.
[email protected]:~$ coonected USB to Gtab, power button plus vol minus 2 minutes
coonected: command not found
[email protected]:~$ sudo dmesg -c >/dev/nul
bash: /dev/nul: Permission denied
[email protected]:~$ pwd
/home/ubuntu
[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ pwd
/
[email protected]:/$ sudo dmesg -c >/dev/null
[email protected]:/$ dmesg
[email protected]:/$
[email protected]:/$
It's not surprising that you got no output--I screwed up. The sequence of steps was incorrect: the cable has to be connected between the 2 dmesg commands. Please repeat.
(If you want to insert inline comments on the command line do it like this:
Code:
$ [B]# This is just a comment.[/B]
The shell will ignore everything from the `#' character to the end of the line.)
And, this video is what I recommend to people whose bootloader seems to be trashed--which is what I think your problem is: How to unbrick your Viewsonic G-Tablet
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
The first 2 commands are not needed:
hushpup131 said:
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
Click to expand...
Click to collapse
Yeah, as I suspected, its a bad bootloader and/or other critical partition problem.
If you are certain that the USB cable and ports are OK (check using another device--try a "sudo adb devices" command with a phone, for instance) and you ran the second dmesg command after connecting the USB cable (otherwise, power off and do the sequence again), then your only option now is to follow the K1 pad-shorting procedure shown in the video.
BTW, you didn't answer question #1 in post #5, above. Is there any change in the display brighness after powering on?
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
[13557.908045] usb 4-1: new low-speed USB device number 4 using uhci_hcd
[13558.145227] input: Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input17
[13558.145525] generic-usb 0003:045E:00E1.0003: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00] on usb-0000:00:1a.1-1/input0
[13558.256080] usb 1-4: new high-speed USB device number 6 using ehci_hcd
[13558.397196] scsi9 : usb-storage 1-4:1.0
[13559.397403] scsi 9:0:0:0: Direct-Access Motorola A855 0001 PQ: 0 ANSI: 2
[13559.398816] sd 9:0:0:0: Attached scsi generic sg3 type 0
[13559.403602] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[email protected]:~$
question one, post five... there was no change in the display
There was no change in the display after shorting K1
hushpup131 said:
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
Click to expand...
Click to collapse
Your USB cable seems OK, but, I don't like that line above. Can you describe exactly what you did when you captured that output?
And, run through that dmesg sequence once again exactly as described and post the output. Also, connect the gTab directly to a USB port, and not through a hub.
hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!
Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer
jac10000 said:
Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer
Click to expand...
Click to collapse
I've tried to unplug and replug and also to restart my pc,but I recive everytime the same line without what I need ..
I'm running ubuntu 12.10 fully installed on an external hdd..can this be a problem?
Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043
jac10000 said:
Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
I've not bricked the phone with the guide,but after I flashed an RUU and tried to update OTA to JB..then,during the automatic process ,the phone stopped band gone bricked . so I can 't follow the guide from the start and the files that I need ha ve been passed to me by some people on another site.
PS.I can't write on that thread because I ve not 10 posts yet
UMBYDD said:
hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!
Click to expand...
Click to collapse
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck
bluebenno said:
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck
Click to expand...
Click to collapse
well..first of all this is not a problem of speed.. I'm really really quick! then the 10 seconds procedure works well for me..after 10 sec the qualcomm. inc. etc disappear.
I have the bakp4 because I take it from another friend on the forum.
now I've not comprise so well your procedure ..can you explain me better the 2 steps? thank you!
ps.I've tried to do the step 12 but it tells me COMMAND NOT FOUND
Please see if someone helps me, I've tried all the tutorials I've found and unbrick no way to flash my Asus.*
I had installed CWM Recovery 5.5.0.4 and wanted to upgrade it, so I installed Rom Manager and then click on the Install ClockWorkRecovery and I installed version 6.0.1.3, there seemed to be no problem until you restart the tablet, and I was on the logo Android and there was no more, I did a factory reset and wipe cache and nothing was the same. I just reinstalled the rom would solve the problem but when I started at the Recovery and gave him the option Install zip from sdcard, surprise: Can not mount / sdcard, so I can not access the sdcard. I do not know if the memory is screwed up or the fault of the recovery. I tried flashing with nVFlash, Easyflaser and I installed the ADB but I can not revive it.*
I do not know what else to give, the problem is that my Slider is B80 and apparently there is no system for flashing, no driver support, or can not find it.
Not completely bricked, I can enter the Recovery, but does not recognize SDcard and MicroSD.
I appreciate any help.
(Sorry for my incorrect English)
maikelbus said:
Please see if someone helps me, I've tried all the tutorials I've found and unbrick no way to flash my Asus.*
I had installed CWM Recovery 5.5.0.4 and wanted to upgrade it, so I installed Rom Manager and then click on the Install ClockWorkRecovery and I installed version 6.0.1.3, there seemed to be no problem until you restart the tablet, and I was on the logo Android and there was no more, I did a factory reset and wipe cache and nothing was the same. I just reinstalled the rom would solve the problem but when I started at the Recovery and gave him the option Install zip from sdcard, surprise: Can not mount / sdcard, so I can not access the sdcard. I do not know if the memory is screwed up or the fault of the recovery. I tried flashing with nVFlash, Easyflaser and I installed the ADB but I can not revive it.*
I do not know what else to give, the problem is that my Slider is B80 and apparently there is no system for flashing, no driver support, or can not find it.
Not completely bricked, I can enter the Recovery, but does not recognize SDcard and MicroSD.
I appreciate any help.
(Sorry for my incorrect English)
Click to expand...
Click to collapse
This should be in Q&A, not Development.
However, you can boot to CWM, then use PERI to unbrick. It will install Rogue Recovery.
If you do not have a ROM zip on the internal memory, you will need to use ADB to push a .zip file to the internal memory then flash that.
I would stick with the CWM 5.5.0.4 for the slider. The 6.X versions were never adapted, and ROM Manager does not work with Asus tablets.
http://forum.xda-developers.com/showthread.php?t=1671598
frederuco said:
This should be in Q&A, not Development.
However, you can boot to CWM, then use PERI to unbrick. It will install Rogue Recovery.
If you do not have a ROM zip on the internal memory, you will need to use ADB to push a .zip file to the internal memory then flash that.
I would stick with the CWM 5.5.0.4 for the slider. The 6.X versions were never adapted, and ROM Manager does not work with Asus tablets.
http://forum.xda-developers.com/showthread.php?t=1671598
Click to expand...
Click to collapse
Sorry if the post is not in place, would be grateful if any moderator can move.
The problem is that I can not use ADB, because if I type "adb devices" does not my ASUS in the list of devices, since none of the four drivers I've tried works. I used PERI but does not work, and says "tablet is not ready for nVFlash". I need a driver that works on Slider SL101, TF101 drivers do not work. Those in the official ASUS serve no APX mode.
Thanks for your help.
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
Give these drivers ago from this thread
pops106 said:
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
Give these drivers ago from this thread
Click to expand...
Click to collapse
Thanks but not work
Posted a video with errors and an image of the Show Log of recovery.
http://youtu.be/AUogpmDT7pA
http://i299.photobucket.com/albums/mm287/maikelbus/_DSC4593_zps2de84e2e.jpg
maikelbus said:
Posted a video with errors and an image of the Show Log of recovery.
http://youtu.be/AUogpmDT7pA
http://i299.photobucket.com/albums/mm287/maikelbus/_DSC4593_zps2de84e2e.jpg
Click to expand...
Click to collapse
I had the exact same problem when I upgraded my recovery. I used ADB successfully though. I had to push another recovery blob. I have not attempted to re upgrade since.
I am pretty sure that unless you can get ADB working, you are in trouble.
APX mode won't work because AFAIK, the SBK has not been cracked for the SL101.
Might want to try another cable - I have seen numerous cables that charge the tablet, but do not work for USB (ADB, APX or MTP connections). New cable solved it.
frederuco said:
I am pretty sure that unless you can get ADB working, you are in trouble.
APX mode won't work because AFAIK, the SBK has not been cracked for the SL101.
Might want to try another cable - I have seen numerous cables that charge the tablet, but do not work for USB (ADB, APX or MTP connections). New cable solved it.
Click to expand...
Click to collapse
I bricked my th101 and could not use Adb either. I had a bad cable. Order a new non OEM and it worked. Unbricked and happy again. Did not even need to use adb push just a all in one tool. Hope u get it working again.
Sent from my Galaxy Nexus using Tapatalk 2
Ok, try another cable to see if we are
lucky and commented, thanks to all
maikelbus said:
Ok, try another cable to see if we are
lucky and commented, thanks to all
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1681155
Maybe give this a blast as well, it worked for everyone one i have flashed.
Cheers
pops106 said:
http://forum.xda-developers.com/showthread.php?t=1681155
Maybe give this a blast as well, it worked for everyone one i have flashed.
Cheers
Click to expand...
Click to collapse
I tested the 4 versions of PERI and any works, the problem is probably the cable, but in my town costs a lot to find, Asus does not provide too purchase. Nor do I know if there are several models, is it possible to have a cable that flash and another cable that forbid? On the website of Asus only sell the charger cable, not loose. In Spain.
http://shop.asus.es/shop/es/es-ES/H...on-conectores-para-EURO-y-UK).aspx?show_popup
On Amazon there are two.
http://www.amazon.es/Mobiles®-Cable...SZK2/ref=sr_1_1?ie=UTF8&qid=1361305799&sr=8-1
http://www.amazon.es/GTMax-Cable-me...1_fkmr0_1?ie=UTF8&qid=1361305799&sr=8-1-fkmr0
It's a great price, but do not know if the original cable, and if it will work.
The cable I have now bought it at Deal Extreme, so I guess it is not original, I know. The original purchase box broke down quickly.
Either should work. I would probably go with the bottom one, no reason why.
Sent from my Galaxy Nexus using Tapatalk 2
Hi,
I have finally decided to buy the cable GT-max, I consulted the dealer and assures me that is identical to the original Asus and because the other is identical to the one I bought last year in Dealextreme:
http://dx.com/p/usb-data-charging-cable-for-asus-eee-pad-transformer-tf101-95cm-length-114609
While I get the new cable, I decided to install Android ADB in Ubuntu and I have the same problem, the tablet is not recognized. I have setup several parameters in the file 51-android.rules and none works:
SUBSYSTEM==”usb”, ATTRS{idVendor}=="0955", ATTRS{idProduct}==:"7820", MODE=”0666″
SUBSYSTEM==”usb”, ATTRS{idVendor}=="0955", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955:7820", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7820", SYMLINK+="libmtp-%k", MODE="0666"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0955",ATTRS{idProduct}=="7820",MODE="0666",OWNER="rehcla" #Asus Transformer
Can anyone tell me what is the correct line for the Asus?
with the command lsusb I get the following:
[email protected]:~$ lsusb
Bus 008 Device 002: ID 040b:2011 Weltrend Semiconductor
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0955:7820 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b083 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
While ADB does not recognize the device, I'm not able to do anything, do you?,
Reconsidering, I think the recovery 6.x after installing updated the Rom unchecked USB debugging mode, so it is possible that all problems are for that reason, then format the rom, and now can not turn on USB debugging.
Is there any way by the ADB to enter the bootloader and force the flash? memory left clean, and you can install everything from scratch? I am new to this.
regards
maikelbus said:
with the command lsusb I get the following:
[email protected]:~$ lsusb
Bus 008 Device 002: ID 040b:2011 Weltrend Semiconductor
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0955:7820 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b083 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
While ADB does not recognize the device, I'm not able to do anything, do you?,
Click to expand...
Click to collapse
You are now in nvflash mode. adb never works in nvflash mode. Only nvflash works in nvflash mode.
josteink said:
You are now in nvflash mode. adb never works in nvflash mode. Only nvflash works in nvflash mode.
Click to expand...
Click to collapse
Sorry, I was confused, thinking that the ADB was used in APX mode, in normal USB mode, the tablet does not recognize either, as the new cable does not work, I'll have to send it to ASUS service center.
Thank you.
I have already received the new cable and no solution, apparently APX mode does not work on devices like my Slider B80.
As APX mode flash no way, I managed to install a compatible Samsung drivers recovery mode and I was able to install the recovery Rogue with Peri. Now I recognize the MicroSD but no internal SDCard. I tried installing the latest firware from Asus and it reads:
-- Instaling: /sdcard/WW_epad-user-9.2.1.27.zip
Finding update package...
Opening update package...
Instaling update...
assert failed: write_raw_image("/tmp/blob", "staging")
E: Error in /sdcard/WW_epad-user-9.2.1.27.zip
(status 7)
Installation aborted.
If I do a Wipe data / factory reset tells me:
--Wiping data...
Formating /Data...
Error mounting /Data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android.secure...
Error mounting /sdcard/.android.secure!
Skipping format...
Data wipe complete.
I can do now? Any idea?
Edit:
Solved! I used the HD Super Wipe Full Eeepad.zip to recreate the system partition without reboot after I installed the ROM HD Revolution 3.5.
Thank you very much to all who have helped me
Explain the solution, as I have asked private and will not usually entered in the forum, and I think it's better than staying here for anyone who has this same problem:
The problem I have is that the partition table is damaged, you have to recreate it, for it uses the full Android superwipe, and then you can already install any Rom.
You need to first install a Recovery that allows access to the MicroSD, since the internal SDCard is inaccessible.
If the current Recovery permitting, no problem. but you need to install another recovery Android do for ADB, as the slider is not supported apx, using nvflash programs are not going to run, but those using adb.
Install another recovery with peri 0.4, this tablet if you recognize the adb interface as being in recovery mode.
decompresses the peri 0.4 on the desktop.
1. connect the tablet to the pc being torn into recovery mode (no apx mode or with the tablet asus on screen)
Two. mouse right button on EasyRecoveryV0.4.bat and run as admin.
Three. you type r and hit Enter
*Out a notice that going to flash the rogue recovery, press enter
*if you connect well and see your recovery 1234567ABCD hit Enter
*recovery begins pushing, if all went well, press enter again
*flash the recovery begins, when done you will only restart the tablet, let it restart
*Now if you should see a rod installing the new recovery.
Once installed, insert a MicroSD with Android_Revolution_HD_Super_Wipe_Full_EeePad.zip I install it in the usual way. They create new Android partitions and internal SD Card.
In the MicroSD also puts your favorite rom and install it later.
This process erases the entire contents of the internal memory, but no other known remedy.
Greetings.
asus slider bricked
Hi! I would like to know if it is now possible to unbrick an asus slider with serial B80?
Fhurzel said:
Hi! I would like to know if it is now possible to unbrick an asus slider with serial B80?
Click to expand...
Click to collapse
Depends, how did you brick it, can you get to recovery, did you install a custom recovery?
I am writing a tool under Linux as an implemention of Qpst under linux
plateform: Qualcomm msm8909
PC OS: Linux (ubuntu 12.04) with qcserial model for Gobi QDL
Actually， two protocols refered，(sahara + firehose)
I have some documents about the details of the protocols and I have implement them in C on linux,
There’s a /dev/ttyUSBx for gobi QDL,
below’s a flow on QDL mode(bricked)
PC ——a firmware bin———> PHONE // sahara protocol
PHONE runs the firmware just downloaded, programming the emmc via firehose protocol .
the program has almost done, but the success rate’s low while trying to flash the images to phone.
for example:
if there’s a image named XXX.bin (1k),
the tool will tell the firmware: “hi, i am going to send you a xxx.bin image, please flash it on sector 8787, and the it covers 2 sectors(1K)”,
the firmware:” oK, place send me the raw data of the XXX.bin”,
the tool then sends the raw data to firmware via ttyUSBx ~~
I tried so many times, but most failed though somethins It succeeded. It seems the data lost on the USB wire, , :crying:
Is there any ways to debug the serial port ttyUSBx ? I am not familiar with kernel programming.
I will insist to open source the program when the tool’s finished if it could do more help for other guys.
It’s not a duty work for company, but there’s docs ，programs and devices in work, so I am not quite sure about the legal risk ,
It’s JUST a simplified QPST (QDLtool?) for LINUX.
https://git.linaro.org/landing-teams/working/qualcomm/qdl.git/about/
usage : ./qdl --debug prog_emmc_firehose_8992_lite.mbn rawprogram0.xml patch0.xml
Great tip!
ryu_hayabusa said:
usage : ./qdl --debug prog_emmc_firehose_8992_lite.mbn rawprogram0.xml patch0.xml
Click to expand...
Click to collapse
I was experimenting with the encryption and my Lenovo Vibe K5 (a6020a40) phone was somewhat "bricked": I was able to install and play with various recovery images, but any system image kept stuck on a boot loop. I tried to restore a stock rom with QPST by I was not able to make it talk with the phone: I do not have a windows machine and I had to borrow one, with limited opportunity to tweak the operating system.
Finally I returned to my beloved Debian linux machine, compiled qdl and tried again to install the stock ROM (A6020a40_S033_160824_16G_ROW_qpst.7z, found on shreps web site).
Code:
sudo systemctl stop ModemManager
cd dir_with_mbn
# connect powered off phone and push VolumeUp+VolumeDown+PowerOn
/usr/local/src/qdl/qdl --debug prog_emmc_firehose_8929.mbn rawprogram0.xml patch0.xml
# HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 ....
After several minutes of XML output I got a diagnostic (Chinese) screen. When I rebooted, without touching anything, the system was in recovery mode with the original recovery image. Then everything worked as usual: I flashed my Lineage 14.1 and my phone was back to life.
Thank you!
I can't help you. I do not know the answer either. Good luck though.
I have an htc Desire 526G (MT 6582), the phone was working bad, so I found a thread here on XDA about flashing the phone via Fastboot.
I use only Linux, Ubuntu, and I installed ADB and Fastboot. The procedure was OK, but the result was bad, now the phone is bricked.
So, in the same thread, I found a ROM scattered to use with SP Flash Tool and I downloaded Sp Flash Tool for LInux (SP_Flash_Tool_v5.1628_Linux) and Installed the MTK drivers. I suppose that the MTK driver is working because the pc can recognize another identical phone as "MTKXXX device".
Unfortunately the SP Tool is not able to access my phone, this is the output
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1479500736.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
comboTimeout index(3) saved.
To make the "Download" I make a click on the "download" button, the tool start waiting for the connection, so I insert the usb in the phone (in power off), I tried with battery and without battery.
It's strange that I tried the connection hundreds of times, using different USB ports, cables, Full/High speed, with and w/o battery, auto detect mode, different agents and so on, and once (only once) SP tool could connect to the phone, but it said thet PMT was chamged, so I found on the net that I should format the phone, but there were no more successes in connecting.
Could someone help me in fixing this problem?
XDA Visitor said:
I have an htc Desire 526G (MT 6582), the phone was working bad, so I found a thread here on XDA about flashing the phone via Fastboot.
I use only Linux, Ubuntu, and I installed ADB and Fastboot. The procedure was OK, but the result was bad, now the phone is bricked.
So, in the same thread, I found a ROM scattered to use with SP Flash Tool and I downloaded Sp Flash Tool for LInux (SP_Flash_Tool_v5.1628_Linux) and Installed the MTK drivers. I suppose that the MTK driver is working because the pc can recognize another identical phone as "MTKXXX device".
Unfortunately the SP Tool is not able to access my phone, this is the output
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1479500736.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
comboTimeout index(3) saved.
To make the "Download" I make a click on the "download" button, the tool start waiting for the connection, so I insert the usb in the phone (in power off), I tried with battery and without battery.
It's strange that I tried the connection hundreds of times, using different USB ports, cables, Full/High speed, with and w/o battery, auto detect mode, different agents and so on, and once (only once) SP tool could connect to the phone, but it said thet PMT was chamged, so I found on the net that I should format the phone, but there were no more successes in connecting.
Could someone help me in fixing this problem?
Click to expand...
Click to collapse
Hello,
Please register for a XDA account to post and reply in the forum.
Also you might try posting your query here Android Q&A Forum with all relevant details, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.