Database Users

A70 + 3G USB = not enough bus power

I have 3G usb dongles:
Huawei E1550
ZTE MF100
And this two dongles writes in dmesg:
Code:
usb 2-1: new full speed USB device using musb_hdrc and address 6
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=12d1, idProduct=1001
usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-1: Product: HUAWEI Mobile
usb 2-1: Manufacturer: HUAWEI Technology
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: rejected 1 configuration due to insufficient available bus power
usb 2-1: no configuration chosen from 1 choice
Code:
usb 2-1: new high speed USB device using musb_hdrc and address 5
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=19d2, idProduct=0016
usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-1: Product: ZTE WCDMA Technologies MSM
usb 2-1: Manufacturer: ZTE,Incorporated
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: rejected 1 configuration due to insufficient available bus power
usb 2-1: no configuration chosen from 1 choice
usb_modeswitch works ok.
It`s fail for Archos 70 IT (8Gb) device?

As it is stated everyewhere, the A70 only outputs 100mA and that doesn't seem enough for those sticks.
So get yourself a usb Powersupply and try again.

Moved to general as not android development

For what it's worth I have got the USB dongle to work with my Archos 101.
I guess this would be one of the reasons to choose a 101 over a 70

Hi i realise this is an old topic but i dont wish to start a new thread if theres already one here.
Im using a 16gb PNY flash drive in my archos 101, latest firmware and it isnt recognising it? iv formatted it every which way and it just wont do.. am i missing something i should have checked? you say you managed to get it working?
Any help appreciated!
Thanks alot.

Sibere just released a Kernel that provides 200mA
Try it

Hey lennb, thanks for the reply. Got another question, im already running SDE and the solution in Ardatdat's thread with a mix of kernals and intframfs.. How would i flash this kernal over that? or instead of it? Im a bit new to the android dev/hack world and i dont wanna brick it hehe.
Any help appreciated!
Thanks

Just do it like you flashed artadats kernel
Boot>>Volume - Button>>Recovery System>>Developer Edition Menu>>Flash Kernel and initramfs
Then just connect your Archos to your pc and copy the two files. Then press ok on archos.

Thanks again Lenbb, iv done a search in the forum trying to find the kernel and the only upload iv found so far to do with the usb hack had to be used in junction with sauron(sp?) kernel, is there a all in one tutorial im missing for this gen8 kernel or is it a case of searching through the posts and compiling it all?
Also, this may sound stupid: Does the flash drive have to be formatted to ext3 to be recogised by the Archos? Iv just thought about any other ways i could try and make this work and found a post on the Archos site saying the android uses ext3... if thats the case i might just slap myself for the over sight!
Any help greatfully appreciated!
Thanks!

Okey, sorry but i dont understand your first question...
Nope it doht have to be ext3, it also can be fat32 and if you have urukdroid you can also host ntfs devices!

haha sorry, im trying not to sound to needy! In basic i was just seeing if theres a all in one thread for the walkthrough of flashing with this usb hack? and cheers for clearing the ext3 question for me!

Nufan1121 said:
n basic i was just seeing if theres a all in one thread for the walkthrough of flashing with this usb hack?
Click to expand...
Click to collapse
What do you mean? Flashing a Kernel is always the same way
___
Edit:
Thank you for giving me the 2. Part of my thanks bar

Aha no worries! you deserve it. Im using the urukdroid 1.0 install method at the moment because i remember in the post i found the usb hack in that it could be use alongside it. Do i have to completely reformat my archos before i flash again?
Im also a bit confused about how to install the new firmware to the sd card? so that i can actually root this thing.

Nufan1121 said:
Do i have to completely reformat my archos before i flash again?
Click to expand...
Click to collapse
Nope, you dont have to do this
But you could joyn sibere (the developer of that kernel) and me at Urukdroid Developement Thread with discuss about this At the moment we want to set the limit up to 500 mA to support HDDs

I will do just that. Im not sure its the right thread but it wouldnt let me post because of my low post count =/. Just one last confusion and i will leave you to your excellent work! haha. Iv got urukdroid 1.0 up and running... but then i realised that sibere's download contained another Zimage and infram. Do i just flash those over the top of urukdroid already installed, or do i completely uninstall my developer edition, then mix sibere's zimage and infram with the urukdroids installer and start again?
Sorry if im not being clear!
Many thanks!

Nufan1121 said:
I will do just that. Im not sure its the right thread but it wouldnt let me post because of my low post count =/. Just one last confusion and i will leave you to your excellent work! haha. Iv got urukdroid 1.0 up and running... but then i realised that sibere's download contained another Zimage and infram. Do i just flash those over the top of urukdroid already installed, or do i completely uninstall my developer edition, then mix sibere's zimage and infram with the urukdroids installer and start again?
Sorry if im not being clear!
Many thanks!
Click to expand...
Click to collapse
Just flash over the top.

msticninja said:
Just flash over the top.
Click to expand...
Click to collapse
Yep, its the Urukdroid 1.1b3 Kernel Just with the Usb modifactions
And you just need 10 Posts to post at the Developer Section

Haha, ill have to hurry and get them then! I installed urukdroid to a 2gb sd yesterday, and was happy with the results apart from a few force closes of some apps and unability to use the market? im not if thats something i did wrong or if its a bug on my archos... I guess ill have to learn more about these divices before i start jumping in and modding them. I flashed the usb kernel imagge and infram over the top of urukdroid's but it didnt give me usb access... im thinking about just buying an adapter untill a simple (for me hehe) guide comes out.
Cheers again =]

Ho well I can post my kernel here too

Is it possible to Flash this usb hack if you are not running uruk?
Currently i am running Chulri root and Harfainx's system memory hack?

Corrupt partition table or fried emmc?

Hi Guys,
I've been researching about this topic now for quite a while, but i am still not certain, whether if the eMMC of my DZ is fried..
Story is as follows:
Just rooted my newly bought DZ (lost my old one )using downgrade, then gfree, everything went fine so far.
After that i went to recovery, flashed virtuous affinity and rebooted. I gave it time to boot, but it got stuck on the "loading initial setup" screen (waited patiently about 20 mins or so). I thought it would be no big deal to pull the battery and let it boot again (Did this with my previous DZ numerous times and all was fine)
On second boot nothing happened, so i checked recovery and saw that the /data and /cache were obviously corrupt. Formatting was not possible by any means, neither by the tools in recovery, nor through flashing superwipe.
I can confirm that my eMMC is one of those possible faulty M4G2DE, see: http://forum.xda-developers.com/showthread.php?t=1039504&highlight=can+t+format&page=3
But it is mentioned in the thread, that it could be either a faulty chip or a defective partition table, which should be possible to rebuild either with a RUU or by adb shell:
Code:
mke2fs -t -ext3 /dev/block/mmcblk0p27
It was also mentioned to check whether
Code:
cat /proc/kmsg | grep mmc0
would say anything about an initialization error, which is not the case for me:
Code:
cat /proc/kmsg | grep mmc0
<3>[ 7.565124] mmc0: No card detect facilities available
<6>[ 7.565765] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.565917] mmc0: Platform slot type: MMC
<6>[ 7.566162] mmc0: 4 bit data mode disabled
<6>[ 7.566284] mmc0: 8 bit data mode enabled
<6>[ 7.566528] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.566680] mmc0: Slot eject status = 0
<6>[ 7.566802] mmc0: Power save feature enable = 1
<6>[ 7.567077] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2a924000
<6>[ 7.567199] mmc0: DM cmd busaddr 0x2a924000, cmdptr busaddr 0x2a924300
<6>[ 7.723022] mmc0: new high speed MMC card at address 0001
<6>[ 7.724884] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
I know, from this point, being unable to do a RUU, nor flash a PC10IMG.zio via fastboot, nor recreate partitions in any other way, would suggest that the eMMC is fried and i should see that i send it in for repair.
BUT
I came across this:
http://tjworld.net/wiki/Android/HTC/Vision/EmmcPartitioning
Basically he is saying, that the hboot is trying to create an extended partition on the end of the blocks, if unallocated blocks are still available this should do no harm. But if the disk is fully partitioned, it simply overflows and creates the partittion at the beginning of the disk. According to that, this causes the usual tools to be unable to reformat the disk, because they get stuck in the same overflow.
He mentions a way to fix this, by unallocating the last partition, but i am not sure how this could be done.
Can the hboot be the problem? The new DZ runs eng hboot 84.2000, on my old one i used to have the normal pvt ship (see sig)
Maybe some of you would like to help me think
And maybe we can find a solution for some of the fried eMMC's

Hi Xadro
unfortunatly i have currently exactly the same problem. I can't manage to format the system partition (mmcblk0p25) and the cache partition (mmcblk0p27).
Do got any solution for it?
Thx in advance
Chris

Small update:
I managed to format each in 4EXT with tools formating to use ext3. Now my info is showing me the attatched screeni. Before that he crashed everytime when I opend that view and system and cache was ext4 but also without size values.

Kind of an awkward way of thinking, but... I see that you have a 32GB Sd Card.
Could that have any link to your problem?

Mhh dont know. Shouldn't as i never had problems before.
My target was to use Android Revolution HD 7.0.2 and I may should add the whole story in short form:
followed http://forum.xda-developers.com/showthread.php?t=1178912 to do a downgrade -> worked perfectly
followed the rest of http://forum.xda-developers.com/wiki/HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD to gain perm root until step 7. -> worked perfectly
used http://forum.xda-developers.com/showthread.php?t=1493404 to gain a new rom
it was written to use 4EXT -> so installed what worked and also the info was displaying the correct sizes
applied ZIP and restarted -> waited 30min but only boot animation was displayed and after some time it restarted -> boot loop
applied the ZIP again -> same result
found in http://forum.xda-developers.com/showthread.php?t=840040 to load SuperWipe...what i did and it reformated worked with out error
applied ZIP again
didn't started anymore -> stucked there
During all the restartings it can be that i may interrupt some important "reallocating" of partitions...but not sure.
But I can try replace the SD with the original one. But not thinking that it is a problem, cause it is normal accessable :/
Any way big thanks for trying to help me!

try a fastboot wipe, cleaner than even your best superwipe - then when you pick a rom to flash pick an old tried and true like the stable cm7 or miui.us

Hi,
unfortunatly that didn't worked
if I start "fastboot erase system -w" (i think you ment that) he just writing "erasing 'system'..." and just stops there. my phone is displaying the whole time the fastboot white screen, but i can't do anything there anymore (vol up/down...). I waitet 2h...only could remove battery
I realy appresiate any other recommendation :/
Update:
Also this hangs:
Code:
./fastboot -w
erasing 'userdata'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 3627.265s

Phone needs to be in flashboot usb, and when you open cmd on your comp you need to open it to where you have fastboot stored or change directories to it. Or you can add it to your variables and open it anywhere.
Sent from my HTC Desire Z using xda premium

Sorry for answering a bit late, but was in weekend holidays
Of course i did it in the fastboot folder and my phone was in fastboot usb (red blinking on phone screen). Otherwise i would get "<waiting for device>". Just got that error message posted above. Any ideas left? Otherwise it seams to be a broken eMMC

So when conected phone displayedfastboot usb in red? If so when you typed fastboot devices did it display one?
Sent from my T-Mobile G2 using xda premium

Yepp, it does show serial and "recovery".

And if you try to flash the hboot/spl now what happens?
Sent from my T-Mobile G2 using xda premium

Hi again,
I tried to flash the hboot while in fastboot with following message:
Code:
C:\android-sdk-windows\platform-tools\rom_26>fastboot flash hboot hboot_7230_Vision_HEP_0.85.0005_101011.nb0
sending 'hboot' (1024 KB)...
OKAY [ 0.183s]
writing 'hboot'...
FAILED (remote: image update error)
finished. total time: 2.904s
Also tried to do it with "dd" what seem to work but as soon as i restart the phone it still says it is in an "VISION PVT ENG S-OFF" while i was flashing a non-ENG hboot...and the version also not matching "HBOOT-0.84.2000" while flashing 0.85.0005
I also tried to put a newer (2.42.405.2) PC10IMG.zip from RUU on SD Card but it fails with message "BOOTLOADER - Fail-PU" and "Partition update fail! Update Fail!"
I realy think the eMMC got bricked...If you do not have any advices anymore i will look for a replacement from somewhere.

I still searched around and found that post: http://forum.xda-developers.com/showthread.php?t=1039504&page=6#post14645519
Its exactly my situation with same outputs and also the "bad" eMMC. I will try to send it in. Reading all that i have to admit that i already had before trying rooting it, i couldn't do a normal restart (just had a black screen after splash screen). It must have been connected to USB to be able to do a restart. So I think i didn't done anything wrong...just have a hardware issue

Sorry for not answering you chrisdeath, was busy with other stuff lately, so i hadn't had the time to stop by here. Have you been sending in your phone already? Telling from the stuff you wrote earlier, it is very likely a fried emmc. There is a way to confirm this, using two shells. With one shell, you need to display the log using
Cat /proc/kmsg ¦ grep emmc0
With the other shell, try to do any kind of write access (e.g. format partition or dd anywhere)
If there are any errors in the log referring to the write fail, your chip is bricked.
It will probably get fixed free of charge, even if the phone is rooted, others have told me that they got it new without payment. If your new one has the same chip, you should if by any means possible, never pull the battery during operation, as this seems to be the main cause for bricking the chip.
Sent from my HTC Vision using XDA

debugging UART3 (ttyMSM2) in gen2

Could somebody answer this question. The ZTE Blade has a serial connector at the back, also see http://android.modaco.com/topic/325947-rs232-on-the-blade/ .
I've seen some old kernel logs, http://pastebin.com/YWtjyRhQ, on a gen1 where ttyMSM2 is found and intialized.
[01-01 00:00:00.470011] [1: swapper]msm_serial: detected port #2
[01-01 00:00:00.470011] [1: swapper]msm_serial.2: ttyMSM2 at MMIO 0xa9c00000 (irq = 11) is a MSM
[01-01 00:00:00.470011] [1: swapper]msm_serial: driver initialized
Click to expand...
Click to collapse
On my device, which is winflashed to GEN2, so i can't test this hypthesis myself unfortunately, i can't get my device to find this serial port. I have a feeling ZTE didn't just disabled fastboot they also disabled this UART3 port, which is a true shame as i want to use this port to display the printk messages to debug some stuff. Question, did ZTE disable UART3 and is it possible to get the port working again..
To test it, you'll need a kernel where config_serial_msm=y and you should see if ttyMSM2 is seen.

Have you tried talking to wbaw? I think he knows tpt stuff quite well

Can answer my own question now, 2.6.32 makes the serial port work..

Bricked Nook Glowlight 3

I installed relaunchx and rooted the device sucessfully. It was running okay. I set the home button to restart in relaunch rather than the nook software. I rebooted and all it would do is go to the front-screen with the nook barnes and noble logo on the front. I could turn it on and off, but that was it. It charged. I tried to start packages on the device via adb but it said the system wasn't running. I could see processes system processes with ps.
I issued a reboot recovery command via adb. The Nook finally responded with something other than a reboot and it went into recovery and did a full factory reset. I thought I was in the clear. But no. It rebooted and went back to the logo screen as before. However, now I no longer have adb access.This might be because the factory reset turned off usb debugging. So now I can't access the device at all. Does anyone have any ideas how I might be able to proceed? I think the device is functional, but the bootloader is damaged somehow so I can't start Android on the device. Without adb access, I think it's effectively gone.

It's likely that you don't have any home application working.
Or maybe it's completely borked.
Have you tried holding various buttons on a power up to see if you can try recovery again?
The next worst case is just using the hardware console connection (inside the case) to see if you have a shell and what's going on.
For the old NST we had a whole setup to boot over USB even with a totally wiped out flash.
That hasn't been looked at for the newer iMX6 (vs OMAP) Nooks.

Hi,
Renate NST said:
For the old NST we had a whole setup to boot over USB even with a totally wiped out flash.
That hasn't been looked at for the newer iMX6 (vs OMAP) Nooks.
Click to expand...
Click to collapse
I tried to manually root using https://forum.xda-developers.com/showpost.php?p=76496894&postcount=13, replicating commands on Linux, and I totally bricked my Nook - probably bad repacking on boot image.
Code:
[884213.478979] usb 3-3: new high-speed USB device number 123 using xhci_hcd
[884213.607636] usb 3-3: New USB device found, idVendor=15a2, idProduct=0063
[884213.607642] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[884213.607645] usb 3-3: Product: SE Blank MEGREZ
[884213.607648] usb 3-3: Manufacturer: Freescale SemiConductor Inc
[884213.609540] hid-generic 0003:15A2:0063.000C: hiddev0,hidraw0: USB HID v1.10 Device [Freescale SemiConductor
Inc SE Blank MEGREZ] on usb-0000:00:14.0-3/input0
Can you point me to NST setup to recover over USB, I would spend some time to try to recover my Nook.
Thank you!

If you had just wiped out P1 you should still have recovery (on P2) just fine.
Do a restart holding the Home button down.
If this doesn't work you somehow managed to wipe the bootloader.
To get the USB HID bootloader to work would be a bit of a project.
There is the starting point of this tool: https://github.com/boundarydevices/imx_usb_loader
Anything that is written about USB recovery on the NST (which uses OMAP) has nothing to do with the new Glows (iMX6SL).
Hmmm, the Kindle Paper White 2 seems to have the same processor/ROM bootloader...

For what it's worth, here is an overview of the low-level MMC:
Code:
Name 32kB units 512B sectors Byte addresses /dev/block
Start End Start Size Start End
---------- ----- --- ----- ----- ------- ------- ----------
mbr 0 1 0 1FF
sn 1 1 200 3FF
bootloader 2 1022 400 7FFFF
hwcfg 1024 2 80000 803FF
ntxfw 1030 256 80C00 A0BFF
bootenv 1536 510 C0000 FFBFF
boot 33 223 2048 12224 100000 6F7FFF mmcblk0p1
waveform 225 544 14336 20480 700000 10FFFFF
logo 545 608 34816 4096 1100000 12FFFFF
recovery 609 1632 38912 65536 1300000 32FFFFF mmcblk0p2

Renate NST said:
If you had just wiped out P1 you should still have recovery (on P2) just fine.
Do a restart holding the Home button down.
If this doesn't work you somehow managed to wipe the bootloader.
Click to expand...
Click to collapse
I was lucky!
Restart holding the Home button down made no difference.
Trying randomly, I observed restart holding the Home and Right Up buttons goes into fastboot.
I recovered P1 partition for which I had backup and my Nook is live again.
Many thanks!!!
imx_usb_loader would have taken some time to learn.

So you're stuck in the ROM USB bootloader?
To look into a solution I had to get the ROM USB bootloader to run on my Nook to test things.
I didn't feel like bricking the Nook, so that was out.
I disassembled the ROM bootloader and found the correct, erm, workable entry point in the ROM.
Code:
eBR-1A # go [i]<entry address>[/i]
Code:
iManufacturer: 0x01
0x0409: "Freescale SemiConductor Inc "
iProduct: 0x02
0x0409: "SE Blank MEGREZ"
So now I can play around with the ROM USB bootloader.

Renate NST said:
So you're stuck in the ROM USB bootloader?
Click to expand...
Click to collapse
No.
After fastboot got enabled I booted nnglow3.img and then I recovered P1 partition with dd.
My Nook is like new
Thanks,
C

cipibad said:
No.
After fastboot got enabled I booted nnglow3.img and then I recovered P1 partition with dd.
My Nook is like new
Thanks,
C
Click to expand...
Click to collapse
I'm having the same issue as yours, could you please help me to unbrick my device?
I'm a newbie to technology so please help me step by step

Will not boot after forced update through adb

A while ago now I tried to update the stock rom with the update that it downloaded ota and repeatedly failed to install.
This in turn ended with the phone not giving any signs of life at all.
Put in uUSB cable to charge, no reaction on display and no charge led.
hold power button, no reaction etc...
I have opened it up, disconnected the battery, waited a while then reconnected with no change.
If I remember correctly (I bought a huawei p20 lite since I needed a working phone and have been using it since), I had unlocked the bootloader and had twrp (spelled wrong?).
Is it a paper weight now or is there any way to get any life into it again?
I do have JTAG programmers if I can find the correct places to connect the leads on the board and also soldering experience on very small things (not bga ic's).

marcosource said:
A while ago now I tried to update the stock rom with the update that it downloaded ota and repeatedly failed to install.
This in turn ended with the phone not giving any signs of life at all.
Put in uUSB cable to charge, no reaction on display and no charge led.
hold power button, no reaction etc...
I have opened it up, disconnected the battery, waited a while then reconnected with no change.
If I remember correctly (I bought a huawei p20 lite since I needed a working phone and have been using it since), I had unlocked the bootloader and had twrp (spelled wrong?).
Is it a paper weight now or is there any way to get any life into it again?
I do have JTAG programmers if I can find the correct places to connect the leads on the board and also soldering experience on very small things (not bga ic's).
Click to expand...
Click to collapse
Hello.
In order to install stock updates you needed stock recovery, it does not work with TWRP recovery.
I'm not a technician but I think, I repeat I think, you f***ed the phone.
Use your tester or take your phone to the service point, maybe the motherboard is gone ..
P.S.: Have you tried first with another cable / charger, both ?
Regards

Dadditz said:
Hello.
In order to install stock updates you needed stock recovery, it does not work with TWRP recovery.
I'm not a technician but I think, I repeat I think, you f***ed the phone.
Use your tester or take your phone to the service point, maybe the motherboard is gone ..
P.S.: Have you tried first with another cable / charger, both ?
Regards
Click to expand...
Click to collapse
I've tried a lot of things, including other cables, chargers ++
I guess it is dead.. ah well..
Thanks anyway

Have you tried booting to Fastboot?

The Restless Soul said:
Have you tried booting to Fastboot?
Click to expand...
Click to collapse
Can't get any sign of life from it at all.
In linux, if you connect a usb device you see a message with a command called dmesg that gives info about the connected device, there is no reaction when i connect it.
Example when connecting my p20 lite:
[176821.173652] usb 1-6: new high-speed USB device number 18 using xhci_hcd
[176821.326319] usb 1-6: New USB device found, idVendor=12d1, idProduct=107e, bcdDevice= 2.99
[176821.326321] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[176821.326322] usb 1-6: Product: ANE-LX1
[176821.326323] usb 1-6: Manufacturer: HUAWEI
[176821.326324] usb 1-6: SerialNumber: <REDACTED>
[176821.355138] usb-storage 1-6:1.1: USB Mass Storage device detected
[176821.355224] scsi host6: usb-storage 1-6:1.1
[176821.355301] usbcore: registered new interface driver usb-storage
[176821.356740] usbcore: registered new interface driver uas
[176822.386058] scsi 6:0:0:0: CD-ROM Linux File-CD Gadget 0404 PQ: 0 ANSI: 2
[176822.386549] sr 6:0:0:0: Power-on or device reset occurred
[176822.386980] sr 6:0:0:0: [sr0] scsi-1 drive
[176822.386981] cdrom: Uniform CD-ROM driver Revision: 3.20
[176822.387121] sr 6:0:0:0: Attached scsi CD-ROM sr0
[176822.387181] sr 6:0:0:0: Attached scsi generic sg3 type 5
[176822.869111] ISO 9660 Extensions: Microsoft Joliet Level 1
[176822.872240] ISOFS: changing to secondary root
Click to expand...
Click to collapse
And when connecting the p9 lite, there is no reaction what so ever.