Related
hi everyone i am currently trying to install android 3.2 on my htc hd2 and the steps i am following are to copy the android folder to the root of my sd card and then once i have done this then to tap on the CLRCAD file then tap the haret file then a loading bar comes up then goes to a black screen and in small writing in the top left hand corner it says
haret boot
shutting down hardware
turning off mmu...
in preloader
psr=600000df
tags preloaded to 0x11b00100 (size 0x0000f00)
kernel relocated to 0x11b0b000 (size0x0023f12c)
initrd relocated to 0x12200000 (size 0x001d0137)
jumping to kernel...
i have repeated this process a dozen times to ensure that i have not missed anything out last nite i made sure that the battery was fully charged and also i updated my rom from the htc website to the latest version as i have read that some people cant get android working at all unless they did this. i did the process until i got the black screen again and left it all night thinking that it may take a long timer as it is the first time i have ever tried loading android but i woke up and the screen was still there i am not sure what i have done wrong i have watched videos on youtube and read forums but no one else seems to have had this problem any help would be greatly appriciated thanks
i have just tried to boot an older version of froyo android the 2.2v i got past the first black screen and it went to the black screen where the white writing starts to scroll down the the writing faded into white lines what am i doing wrong
back up your sdcard contents to your computer.
format it, preferably from a linux box. if your stuck with win-blows, then you can do a full format, not the quick format.
now put JUST THE ANDROID folder on the sdcard.
put sdcard in phone, boot into android. when it boots, dont do ANYTHING for 5 min. reboot.
once it reboots, goahead and log in, synch etc.... then reboot
after that you can coppy the rest of the sdcard contents back over and be good to go.
which winmo rom, radio rom, and android build are u using?
i am using the darkstone froyo 3.7 build i am not sure what radio is or which one i am using i will try what you have suggested and let you know how it goes
right i formated (full) the sd car using windows vista the only way i could do this is plugging my phone into my laptop using the usb and formatting it that way
then i copied just the android folder to my sd card
rebooted the phone and went to file explorer opened the android folder doulbe clicked on clrcad then on haret
i was then stuck on the screen that i was before so i waited 5 mins just like you said to rebooted the phone and it was still on windows.
i repeated the same steps and waited ten minutes still no luck
also just so i understand after i waited five minutes should i be able to reboot the phone i do i have to pull the battery out like i did and where you put (when it reboots login etc)
is there any way you could email me a file to see if it is the files i am using
thanks for all you help so far guys!!!!
i am from th UK i dont know if that makes a difference
i have a 2gb sd card
i have just done some research on the radio versions and round a thread called master radio for the htc hd2 on xda but i am unsure which one to use and could this be the root of my problem thanks again
OS version 8.2.2.1869(21869.5.0.82)
manila version 2.5.20121429.0
ROM version 1.72.206 (8637200) WWE
ROM date 04/15/10
radio version 2.07.51.22_2
Protocol version 15.32.50.07U
i have just done a bit more research and found out that i need to use a .50 for flashing could this be a problem if i dont could this be th root of my problem
very big part I'd say.... It does say on just about EVERY build that you need a .50 radio NOT a .51....
snowy88 said:
i have just done a bit more research and found out that i need to use a .50 for flashing could this be a problem if i dont could this be th root of my problem
Click to expand...
Click to collapse
could be...
u need at least 2.08.50 or higher radio i thought so.
linkie he Definitve Guide To Android On HTC HD2
[RADIO] The HTC HD2 Master Radio Thread ( i would try Leo_RADIO_2.12.50.02_2 or 2.14 )
Good luck tell us when it did work
t1h5ta3 said:
back up your sdcard contents to your computer.
format it, preferably from a linux box. if your stuck with win-blows, then you can do a full format, not the quick format.
now put JUST THE ANDROID folder on the sdcard.
put sdcard in phone, boot into android. when it boots, dont do ANYTHING for 5 min. reboot.
once it reboots, goahead and log in, synch etc.... then reboot
after that you can coppy the rest of the sdcard contents back over and be good to go.
Click to expand...
Click to collapse
snowy88 said:
i was then stuck on the screen that i was before so i waited 5 mins just like you said to rebooted the phone and it was still on windows.
i repeated the same steps and waited ten minutes still no luck
also just so i understand after i waited five minutes should i be able to reboot the phone i do i have to pull the battery out like i did and where you put (when it reboots login etc)
Click to expand...
Click to collapse
no, depending on the class (speed) of your card it'll take 15-20 min to initalize on the first boot... theres alot going on in the background.
once its booted...ie: once it shows the initial android log in screen. ie: it has actualy booted into android.
if you pull the battery in the middle of the first boot, you just corupted the data it was writing.
format the card again - get rid of the corupted files.
now start over.
and yes, you got to have the corect radio installed etc.
most roms have a requirements list... if not folow the stickies.
as ive stated a ton of times in a ton of thereads, its worth installing ether droid explorer or adb on your pc if for no other reason but to be able to run a logcat so you can watch it run comandline, aswell as post it so others can help you debug/troubleshoot.
I have the same issue with linux showing that message then it boots up a green htc sign and stays there.. i left it there for 40 minutes waiting to see if anything would happen and never did. I had android running before but did a full format on my sd card and then installed another and this happens everytime i try.
I am running Miri_Dinik- V 19.0 WWE
Radio: 2.15.50.14
I also am using the 16g sd card that came with my tmo hd2
i have been searching for days for an answer and decided to finally make a post to see if i can get any answers
thanks
A7 Internet Tablet
Firmware Update
To determine the firmware version currently installed on your tablet, go to Settings > About device and scroll to the bottom to see Build number. The last 5 digits of the Build number indicate your current firmware version.
The February 4, 2011 Firmware Update addresses issues with micro card formatting and capacity and offers improvements to Wi-Fi connectivity.
The Firmware Update for your A7 Internet Tablet must be downloaded to your PC or Mac and copied to a MicroSD card for installation.
IMPORTANT: A MicroSD card is required to update the firmware. The USB port is a host only and cannot be used for firmware updates.
Note: Since the files stored in the Tablet may be deleted or overwritten during the update process (including the pre-installed movie trailers), please copy any files which you have stored in the Tablet before updating.
Please follow these directions carefully for a successful update:
A7 Firmware Update Instructions
Download the Firmware Update ZIP file at the bottom of this page to your PC or Mac.
Copy the ZIP file from your PC or Mac to a MicroSD card. The file must be copied to the ROOT DIRECTORY of the MicroSD card. Make sure you do not copy the file into a subfolder.
Insert the MicroSD into the slot at the top of the A7 Tablet.
Plug the A7 Tablet into an electrical outlet using the AC adaptor.
Open Settings > About device > System updates > Update device.
Follow the on-screen prompts. The system will restart automatically in update mode, then will restart when the update is complete.
To confirm that your update has been correctly installed, open Settings > About device. Scroll down to Build version and you should see PBJ8000.2.0127.
Download here: http://elocitynow.com/downloads/firmware/update.zip
CPG
MyTabletLife.com
Ok, who is going to see what happens when this is applied to their A7 that has Dexter's Mod 1.1 on it? I'm too scared. I've just about got mine working ok. I just need to get the newer version of the Market, Calendar fixed, and Bluetooth PAN tethering via Blackberry working. I didn't expect such a learning curve on this device.
Im about to try it will keep you posted!
Boot Loop
My unit arrived this morning.
I put the Feb 4 OEM update on first then applied dexter's mod and ended up in a boot loop.
I was not sure how to get out of the loop so I tried a couple shut downs to no avail.
So I reset and ran the Feb 4 update again.
I have a lot more icons than to shipped version, but I do not think I have the google apps market place.
I am very new to android so I'm a bit in the dark.
Is there a way to get out of the boot loop?
Thanks
Ekk! Boot Loop!
Did you guys wipe Data/Cach?
I'm updating through recovery mode. I'll update everyone shortly...
FANCY "eLocity" boot screen! No loop here.
Sweet! Shows My 8gb card at 7.38 Empty space!
For the people in the boot loop try powering down your device and powering it back on.
The A7 No longer force closes when you select the Brightness tab!
Just did that it worked great! I can see my sd card woot! No market
I did the data wipe and every seems to work.
Thanks for reading.
Don't forget to wipe Data/Cach. Thats almost always the issue!
Does it have Market or any or the Dexter mods
Does it have Market?
hudd333 said:
Does it have Market?
Click to expand...
Click to collapse
It does not tried installing it but it doesn't work. Getjar is really low on good apps
hudd333 said:
Does it have Market?
Click to expand...
Click to collapse
No, The fireware downloaded from the Elocitynow.com website does NOT come with Market.
New firmware
Will Dexter be modding this one for us?
I would hope so!
I would love if Elocity or Dexter would tackle the App2SD problem
no Market
Sorry. Just niticed no market in an earlier reply. Let's hope Dexter can mod this to re-add market, etc. Thks
Observations of New Firmware Release
Memory Reporting - External SDCARD memory properly reported, USB properly reported mounted, usb size not reported in settings
Booting - Data wipe necessary otherwise will hang on Android or Boot Loop
Wifi - Works, no issues; quick connect
Bluetooth - Works, paired with my bluetooth QSTARZ GPS module
Audio - No issues
Video - Flash works tested with CNN.com
Adhoc -Not Present
VPN - Not tested
WPA/WPA2 - Works, no issues, quick connect
WEP - Not tested
Interface - No changes
Installed Apps - No changes
Market - Not present
CIFS - Not present
3G USB - Not present
Kernel Version - 2.6.32.9-svn2514
Build - PBJ8000.2.0127
Quadrant Score - 2396
Summary: Most noticeable change is memory reporting, otherwise no significant changes, no issues either.
Mine is working fine after update.
Update is same size as the last file?
R
Seems to boot much quicker. Also works with manually installing .apk apps
Notice any improvement in wifi?
I can't really say I notice anything but it was running good out of the box for me.
I think boot up may be slightly improved.
I do notice more verbose initial boot up screen which reminds me of linux a while back!
So far no data or applications were lost but version number has changed.
A smooth upgrade
Although the file size was identicle to the previous release the version is different yet the same.
Rob
Hi, I installed version 1.4 dexter, now no longer works USB and SD, I could help. I have to install the previous version to solve the problem?. Thanks.
Same here...by the way try to read some of the posts under development tab....
Regards
personally, it's worked great for me.
Really...could you do me a favor and let me know what the folders name are that refer to usb and sdcard....mnt/sdcard/sdcard0-disk0 and usb0-disk0 or just sdcard-usb and usb-disk...
Regards
location: /mnt/sdcard
names are
usb0-disk
sdcard-disk
create with IOFilemanager..
btw, version 1.41 fixes it (just tested removing sdcard-disk folder)
Have fc on the market and a few other apps I wiped and reset any ideas?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
no sorry.. ive not seen such an issue, except if you havent wipe'd signatures can be a problem.. but otherwise its not know why..
you might check the 1.41 update im posting now
Hey dex thanks I thought I had wiped but I didn't reinstalled and followed your direction and everything great donation comming yr way . Hey on a personal note I'm looking to buy another 7 inch what would you suggested. The new HTC or the new acre just wanting yr professional input
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nthknd said:
Hey dex thanks I thought I had wiped but I didn't reinstalled and followed your direction and everything great donation comming yr way . Hey on a personal note I'm looking to buy another 7 inch what would you suggested. The new HTC or the new acre just wanting yr professional input
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
HTC Flyer!!! (im getting it!)
Dexter_nlb said:
HTC Flyer!!! (im getting it!)
Click to expand...
Click to collapse
I So want a HTC Flyer, don't think they are bringing them to the US though.
Its called internet purchase
Man that was it...as soon as I removed that "0" from the sdcard folder name it got recognised by the system...did the same thing with usb folder but it did not help there...hope that mod 1.41 will do the job with usb stick
Thanks Dexter for the clue...
Regards
Hey Dex and Net just read the flyers coming stateside this spring but with 2,2 not 3,0 kinda bummed about that but still looking to get one ( or the Acer iconia a100) just read sprint will be releasing it as there HTC tab. Still no price just yet.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nthknd said:
Hey Dex and Neo just read the flyers coming stateside this spring but with 2,2 not 3,0 kinda bummed about that but still looking to get one ( or the Acer a100)
Click to expand...
Click to collapse
so thats less good news.. was hoping to see a new HTC Sense 3.x for android 3.0 especially on a Tegra platform :-( maybe ill reconsider and going for samsung 10" or simply XOOM
Great minds think alike Dex. All I want is a tab that has it all 3.0 cameras, market,tegra 2 great screen SD slot, good form factor.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nthknd said:
Hey Dex and Net just read the flyers coming stateside this spring but with 2,2 not 3,0 kinda bummed about that but still looking to get one ( or the Acer iconia a100) just read sprint will be releasing it as there HTC tab. Still no price just yet.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
That is weird. I had read that the reason for delaying UK release was to work out bugs between Sense and Honeycomb. Doesn't make sense to me to do all the work for Honeycomb just to release it with Froyo in a different market.
Dexter_nlb said:
so thats less good news.. was hoping to see a new HTC Sense 3.x for android 3.0 especially on a Tegra platform :-( maybe ill reconsider and going for samsung 10" or simply XOOM
Click to expand...
Click to collapse
Sense 3.0? I thought the new release was going to be Sense 2.0. (Ok, I checked, wow am I behind the times lol )
I hope someone here can tell me what I'm doing wrong, since I have been unsuccessful in downloading Dexter's updates and thus haven't been able to fully utilize my tablet! I've been trying to look through all the pages but haven't seen information to help this situation. Hope I don't end up feeling foolish because I've overlooked one simple thing...
This is what's happening:
(A comment: I had to download file from Dexter's site; for some reason, even when I give permission to download the blocked file from here, I just get an "about.blank" page on two different computers!)
I copy the file to my micro sd card (not an sdhc, since it seems that's not relevant). Each time, there is a folder called "LOST.DIR", along with the folder I saved as "update" (I don't add the .zip since it already recognizes it as a zip file.). The "lost" always has a time several hours later than the “zip” file. (Note: I had no problem updating the firmware with the same SD card.)
Since the first time I tried to apply the 1.3 update, and now with the 1.41, I can't install it as directed on p. 1--I can't get into the recovery area because it powers off. Instead, I follow directions found on YouTube: settings, about device, system updates, update device, do it, ok.
“Detect recovery flag, booting update kernel” flashes quickly
"loading" bar is under box with arrow and android avatar for a couple of minutes (the YouTube said it would take about five minutes), then it stops.
I hit home and in blue it says:
Android system recovery <1e>
Android system recovery utility
Reboot system now
Apply update.zip
Wipe data/factory reset
Wipe cache partition
Under the blue line in yellow, it says:
E:Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds
Installation time out.
Installation aborted
Formatting MISC:…
Selecting any of the blue options now does nothing except go back to the box, arrow and android. A couple of times, one took me to a screen that had a list of “no”s with a “yes” option to do something I don’t remember but I didn’t think it was a good idea.
Clearly, I need help!
arrkaycee said:
I hope someone here can tell me what I'm doing wrong, since I have been unsuccessful in downloading Dexter's updates and thus haven't been able to fully utilize my tablet! I've been trying to look through all the pages but haven't seen information to help this situation. Hope I don't end up feeling foolish because I've overlooked one simple thing...
This is what's happening:
(A comment: I had to download file from Dexter's site; for some reason, even when I give permission to download the blocked file from here, I just get an "about.blank" page on two different computers!)
I copy the file to my micro sd card (not an sdhc, since it seems that's not relevant). Each time, there is a folder called "LOST.DIR", along with the folder I saved as "update" (I don't add the .zip since it already recognizes it as a zip file.). The "lost" always has a time several hours later than the “zip” file. (Note: I had no problem updating the firmware with the same SD card.)
Since the first time I tried to apply the 1.3 update, and now with the 1.41, I can't install it as directed on p. 1--I can't get into the recovery area because it powers off. Instead, I follow directions found on YouTube: settings, about device, system updates, update device, do it, ok.
“Detect recovery flag, booting update kernel” flashes quickly
"loading" bar is under box with arrow and android avatar for a couple of minutes (the YouTube said it would take about five minutes), then it stops.
I hit home and in blue it says:
Android system recovery <1e>
Android system recovery utility
Reboot system now
Apply update.zip
Wipe data/factory reset
Wipe cache partition
Under the blue line in yellow, it says:
E:Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds
Installation time out.
Installation aborted
Formatting MISC:…
Selecting any of the blue options now does nothing except go back to the box, arrow and android. A couple of times, one took me to a screen that had a list of “no”s with a “yes” option to do something I don’t remember but I didn’t think it was a good idea.
Clearly, I need help!
Click to expand...
Click to collapse
Info on your PC setup please. Mac? PC? Linux?
Also, I noticed this "along with the folder I saved as "update"" in your post. you are not creating an actual folder on the MicroSD are you?
Assuming your SD card reader is drive F: (assuming also Windows machine) then your ROM's complete path should be F:\Update.zip
Just trying to avoid confusion that maybe you are creating F:\update\ElocityMod141.zip or something similar
Here is instructions on how to show extensions for known file types http://forum.xda-developers.com/showthread.php?p=11745552#post11745552
As for
Since the first time I tried to apply the 1.3 update, and now with the 1.41, I can't install it as directed on p. 1--I can't get into the recovery area because it powers off.
Click to expand...
Click to collapse
I think the trick might just be to let go sooner...
Start from the device being completely powered down (not just in sleep mode)
Hold power button for 2 (or 3) seconds
Let go for just a split second and hold it down again.
The screen will come on and you will see something along the lines of "to boot into kernel recovery continue to hold for 5 seconds"
Keep holding it until you see something like "booting into recovery" (I can't remember the exact wording)
AS SOON AS YOU SEE THAT LET GO.
Bam, recovery mode.
I think when you get the update you just save one over the other replacing the file this gave me errors IE bad update everytime. Download the 1.41 leave the name it has the same. Delete the update off your sd and cop the newly downloaded one to it after. Once its on card rename it.
netstat_EVO said:
Info on your PC setup please. Mac? PC? Linux?
Also, I noticed this "along with the folder I saved as "update"" in your post. you are not creating an actual folder on the MicroSD are you?
Assuming your SD card reader is drive F: (assuming also Windows machine) then your ROM's complete path should be F:\Update.zip
Just trying to avoid confusion that maybe you are creating F:\update\ElocityMod141.zip or something similar
Here is instructions on how to show extensions for known file types http://forum.xda-developers.com/showthread.php?p=11745552#post11745552
As for
I think the trick might just be to let go sooner...
Start from the device being completely powered down (not just in sleep mode)
Hold power button for 2 (or 3) seconds
Let go for just a split second and hold it down again.
The screen will come on and you will see something along the lines of "to boot into kernel recovery continue to hold for 5 seconds"
Keep holding it until you see something like "booting into rsucecovery" (I can't remember the exact wording)
AS SOON AS YOU SEE THAT LET GO.
Bam, recovery mode.
Click to expand...
Click to collapse
Thanks for such a quick reply!
I'm using Windows 7 Home Premium on a Samsung N150 Plus.
I saved the file as "update" blank SD card. Deleted files each time before attempting a fresh download. Each time have the two files as listed: lost.dir as a file folder and update.zip as a compressed (zipped) file, currently 1,427 kb.
The powered down sequence still does the same, trying it a few times--goes right to device bootup. I remember that from the firmware update (which went without a hitch!) but it's not working now
Aha...progress! May have held down too long but now see in blue
Android system recovery <1e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
(followed by several rows of "no"s and a yes
Beneath that in yellow:
E:recovery.c Can't open /cache/recovery/command
Formatting MISC:...
Have been here before; not sure how I got out!
IN MY INFINITE WISDOM, I replaced my build.prop with the one from a Motorola Xoom in an attempt to get Sketchbook Pro to show up in the market. Now my tablet is boot looping.
I backed the original up in the same directory, as build.prop.OLD. If I could mount system and replace the file with a PC, I'd imagine that the tablet would work again. How could I do that?
However, THERE IS ANOTHER COMPLICATION! I used the 'Acer Phone Disabler' app to remove the telephony drivers, which means that I cannot flash a rom or the tablet will brick. I'm not sure what this means for Nandroid backups.
The tablet has the leaked stock 3.1 rom installed, it's rooted, and it has Clockworkmod recovery.
Thanks in advance for any help!
Oh god.
I used ADB to pull my build.prop.OLD, renamed it to build.prop, and pushed it back. Now... the tablet boots up, and it shows the Android "Welcome" screen. Clicking the only button available doesn't work. It just highlights as if it is selected, and doesn't do anything when I lift my finger up.
I DO have a Nandroid backup from several weeks ago of the same rom, but from BEFORE I removed the telephony drivers. I am only going to try restoring it as a last resort; does anyone have any ideas? Remember, flashing a rom would result in a brick because I used Acer Phone Disabler. Is a nandroid backup safe?
Thanks guys. I'm really hoping this tablet isn't too screwed.
I'm hoping someone else chimes in here but I am under the impressing that the nandroid backup would override any changes you could make as long as you don't break recovery. As far as my experience goes if you had a backup of your current configuration you could do an "advanced restore" and only restore your "system"
Sent from my A500 using Tapatalk
Restoring just system worked! My homescreen is back to stock but all my apps are still installed, so I don't really care. Thanks a bunch, I was so worried.
COOL!!!
Glad I could help.
Sent from my A500 using Tapatalk
Help needed for a boot loop
Well as said in the video, i reuse an existing thread about bootloop...
I'm stuck in a bootloop with an iconia A500... but let's look at the steps that got me there...
The First mistake was to answer yes to my friend who asked me to connect his Vodafone k3565 to his iconia A500, but as i read Android was linux based and i did use linux a lot as a student, i didn't even imagine it could go wrong...
Tablet was stating to run :
Android 3.1
Bernel 2.6.36.3-00009-9dddf6f2
Build 4.015.05-EMEA-CUS3
i did root with iconia root 1.3
then added Busybox and a terminal program.
reboot, try a SU and could access the devices
Here is the second mistake... i should have wondered how to restore to normal state before starting, because i don't have any SD card that suit the device ( mine are normal sized ones, you know.. Stamp sized :/ )
Then i got to the thread
http://forum.xda-developers.com/showthread.php?t=1058846&page=7
and i used an usb key to transfer it to the device, but before applying the files i took a look to them and found 3 of them would overwrite actual system files, so i did a backup of them :
/system/build.prop
/system/etc/apns-conf
/system/bin/rild
and looking at the build.prop i saw differences in the values of the one on the A500 and the one in the package so i decided to get only the missing lines from the new system.zip file and add them to the original file
And here is the 3rd mistake, and i guess the reason of the problem : i did that merge on a windows computer, and i fear it did add those pesky CRLF at the end of lines, turning my build.prop into a build.prob(lem).
I'm not sure, as i didn't check before it was too late.
rebooted and... boot loop, with 1 times out of 2, the little android with yellow triangle and exclamaition mark.
Cried, runned in circles, then looked on forums to find a solution.
Reboot with Power+Volume gives :
"Erasing cache before SD update...
SD update cmd:recovery
--update_package=sdcard:update.zip
Booting recovery kernel image"
Then i get the android with gears for a few seconds, then below him is a bar like the one in the android store when you download a file, then half a second later, again the exclaimation mark.
I also tried plugging a keyboard to hit the home key...
( in fact two : Logitech G110 and trust easy scroll silverline )
no difference, maybe because those are gaming keyboards and they arent loaded soon enough by the tab, or maybe it crashes before keyboard loading.
Tried then to install ADB using post
http://forum.xda-developers.com/showthread.php?t=1155664
hoping i could use the USB cable to put the backup files back in place but when i plug the device into the windows host, it recognises an unavailable USB MTP device, whose properties say "Acer iconia tab a500" in the "signaled bus description"(translated from french display, may be something else in english)
I manually force added the Acer ADB interface, but both the devices are unavailable to windows, with a warning sign, stating "this device cannot start (code 10)"
"Adb shell" answers "Error:device not found",which is expected, as windows can't see the devices properly
the strange thing is that, with USB plugged from A500 to PC, the Android with exclaimation stays forever, while without the cable, the system boot-loops
so i'm at this point :
i have a boot looping device, and the backup of the modified files on an USB key, and no way to put them back on device.
I found on the forums a lot of different .imgs that could be put on the /system to reload the device but none with EMEA-CUS3. So if i overwrite the files, i can't go back
I read you need a SD card to patch the device but not all of them work...
And my only computer with a SD slot uses a big one, not micro one, so i also need an adapter to write on the sd card.
Is someone near me (belgium/postcode 4000) having a SD ward working with the device who could lend it or help me doing the job ?
else
i saw in a nearby store ad "Sigma SDHC 4Go" or "Sigma SDHC 8Go", with apparently an adaptor for a normal sized SD slot, can anyone confirm it works or it don't work for sure ?
else
Can anyone tell me an SD card know to work, and being sold currently with an adapter so i have a chance to find one in a store near me ?
Is there a way to create an update.zip that will only update the files i did overwrite ?
if not, has someone an image for the same system i have ?
Well... lots of questions, but i'm very worried, especially as the device is not mine and not working anymore atm.
-> update
Looking closer at the modem (Vodafone k3565) it has a trap that says "SD card" so i guess i won't need an adapter... still need the reference of a SD card known to work for the restoring.
[bump] and more :
this thread http://forum.xda-developers.com/showthread.php?t=834144
lists working SD cards, but don't tell with which device. i'd take the guess it applies to the iconia A500 and take the list to the shop to see if anyone is available...
Did you install the Acer USB driver, found here? http://www.acer.co.uk/ac/en/GB/content/drivers
You might need to go into device manager after installing and right click/update drivers on the tablet, then manually direct it to the Acer driver folder. That's what I did, then ADB worked.
Haemdaer said:
Well as said in the video, i reuse an existing thread about bootloop...
I'm stuck in a bootloop with an iconia A500... but let's look at the steps that got me there...
The First mistake was to answer yes to my friend who asked me to connect his Vodafone k3565 to his iconia A500, but as i read Android was linux based and i did use linux a lot as a student, i didn't even imagine it could go wrong...
Tablet was stating to run :
Android 3.1
Bernel 2.6.36.3-00009-9dddf6f2
Build 4.015.05-EMEA-CUS3
i did root with iconia root 1.3
then added Busybox and a terminal program.
reboot, try a SU and could access the devices
Here is the second mistake... i should have wondered how to restore to normal state before starting, because i don't have any SD card that suit the device ( mine are normal sized ones, you know.. Stamp sized :/ )
Then i got to the thread
http://forum.xda-developers.com/showthread.php?t=1058846&page=7
and i used an usb key to transfer it to the device, but before applying the files i took a look to them and found 3 of them would overwrite actual system files, so i did a backup of them :
/system/build.prop
/system/etc/apns-conf
/system/bin/rild
and looking at the build.prop i saw differences in the values of the one on the A500 and the one in the package so i decided to get only the missing lines from the new system.zip file and add them to the original file
And here is the 3rd mistake, and i guess the reason of the problem : i did that merge on a windows computer, and i fear it did add those pesky CRLF at the end of lines, turning my build.prop into a build.prob(lem).
I'm not sure, as i didn't check before it was too late.
rebooted and... boot loop, with 1 times out of 2, the little android with yellow triangle and exclamaition mark.
Cried, runned in circles, then looked on forums to find a solution.
Reboot with Power+Volume gives :
"Erasing cache before SD update...
SD update cmd:recovery
--update_package=sdcard:update.zip
Booting recovery kernel image"
Then i get the android with gears for a few seconds, then below him is a bar like the one in the android store when you download a file, then half a second later, again the exclaimation mark.
I also tried plugging a keyboard to hit the home key...
( in fact two : Logitech G110 and trust easy scroll silverline )
no difference, maybe because those are gaming keyboards and they arent loaded soon enough by the tab, or maybe it crashes before keyboard loading.
Tried then to install ADB using post
http://forum.xda-developers.com/showthread.php?t=1155664
hoping i could use the USB cable to put the backup files back in place but when i plug the device into the windows host, it recognises an unavailable USB MTP device, whose properties say "Acer iconia tab a500" in the "signaled bus description"(translated from french display, may be something else in english)
I manually force added the Acer ADB interface, but both the devices are unavailable to windows, with a warning sign, stating "this device cannot start (code 10)"
"Adb shell" answers "Error:device not found",which is expected, as windows can't see the devices properly
the strange thing is that, with USB plugged from A500 to PC, the Android with exclaimation stays forever, while without the cable, the system boot-loops
so i'm at this point :
i have a boot looping device, and the backup of the modified files on an USB key, and no way to put them back on device.
I found on the forums a lot of different .imgs that could be put on the /system to reload the device but none with EMEA-CUS3. So if i overwrite the files, i can't go back
I read you need a SD card to patch the device but not all of them work...
And my only computer with a SD slot uses a big one, not micro one, so i also need an adapter to write on the sd card.
Is someone near me (belgium/postcode 4000) having a SD ward working with the device who could lend it or help me doing the job ?
else
i saw in a nearby store ad "Sigma SDHC 4Go" or "Sigma SDHC 8Go", with apparently an adaptor for a normal sized SD slot, can anyone confirm it works or it don't work for sure ?
else
Can anyone tell me an SD card know to work, and being sold currently with an adapter so i have a chance to find one in a store near me ?
Is there a way to create an update.zip that will only update the files i did overwrite ?
if not, has someone an image for the same system i have ?
Well... lots of questions, but i'm very worried, especially as the device is not mine and not working anymore atm.
-> update
Looking closer at the modem (Vodafone k3565) it has a trap that says "SD card" so i guess i won't need an adapter... still need the reference of a SD card known to work for the restoring.
Click to expand...
Click to collapse
The reason "some" SD cards don't work is down purely to formatting. Normally, reformatting them in an Android phone sorts it out. Not always, but normally. Don't worry about the GEN3 stuff too much, it's just regional variations anyway... More important to get the tab working again, no?
Yes i did ( on 2 different computers, just to be sure )...
and still the device is not recognised as "adb device".
Windows shows a "USB MTP Device"
Tried to manually add the "ACER Composite ADB Interface" and "ACER Fastboot Interface" to the installed peripherals, it shows with yellow exclaimation mark, never shows up running.
Without any useable answer about one week later, i did buy a Traxdata 2Gb SD card with adapter ( the cheapest i found with an adapter from micro SD to normal SD ) and flashed with the Emea_Gen3 ROM from http://forum.xda-developers.com/showthread.php?t=1113878.
Now the tablet works, but is telling me 4.010.42-COM-GEN1 instead of the previous 4.015.05-Emea-Cus3.
Seems to work correctly, so i go on with the modem connexion.
After rooted the official gingerbread my device was never the same.
Let me try to explain what is happening to see if someone can help.
Official roms:
When I turn my device to PC via USB and then choose the option Mount USB Storage what happens is in the device the Android stays Green with the option below to mount storage, the SD card is apparently un-mounted from device but in the PC I can see the SD card content normally and see it as a removable storage drive
Custom roms:
When I turn my device to PC via USB and then choose the option Mount USB Storage what happens is in the device the Android stays Green with the option below to mount storage, the SD card is apparently un-mounted from device but in the PC I can see the SD card content but can’t make any changes as it opens up as a CD drive. Imagine you put a CD/DVD in your drive you can see all the files but you cannot write on it.
What can I do as seems to be a deep system alteration that won’t change by doing anything at all such as flashing new roms, changing complete content of pink screen, factory resets, etc, etc.
Can someone plz help me with this?
try this with cm7
settings->about phone->project menu->USE GOOGLE USB
I stuck with 2.3 official again!!!
I think I going to deliver my phone to TMN and say that got ****ed up after official upgrade instalation
I've read somewhere that the TMN ones (or some of them) are called "black sheep" since they have some problems (installing other roms I think), maybe your problems where there all along and the updates brought them to the surface...
Yeah, send it back
Yes I know, but I got lucky as my device is like a Hummer.Mine is not.
Goes over of it all, until I messed up... lolol
druida did you format the sd card on the pc and chnage the partition size?
I have the device partitions resized months ago.
yes card was formated and formated and formated.
priestx said:
I've read somewhere that the TMN ones (or some of them) are called "black sheep" since they have some problems (installing other roms I think), maybe your problems where there all along and the updates brought them to the surface...
Yeah, send it back
Click to expand...
Click to collapse
I have a so called "black sheep" and official 2.3.5 is rooted and runnin' flawlessly.
try revert to 2.2.2 using internal sd card.
I got it at last doing this:
Dial * # * # 2846579 # * # *
Background Setting > USB ports setting > choose "Normal Mode" and then rebooted.
The option that was by default and was giving me all this trouble was "Manufacture mode".
Tried to choose "Google Mode" but after reboot revert back to "Manufacture mode" again.
This way every time I connect the USB and choose the option Mount Usb Storage the SD was getting unmounted in the device but in the PC was showing as removable disk giving me full access.
When I unplug the cable I had to mount the card again.
****ing weird!!!!
priestx said:
I've read somewhere that the TMN ones (or some of them) are called "black sheep" since they have some problems (installing other roms I think), maybe your problems where there all along and the updates brought them to the surface...
Yeah, send it back
Click to expand...
Click to collapse
no they are not (me +2other friends have such phones). it's hapenning the same as before: people messing up.
Well, this problem is not related to 2.3.5 update, but with updates in general, 'cause i have it about a month ago. Same thing as you, but if U use a 2.2 custom ROM (flb or void) you should mount usb properly. If U go to device manager you will see that the drivers aren't properly installed.
Altough I don´t know the exact time, i think my probelm begins when after flashing a ROM I got the blue screen and needed to install b138 elisa. I guess after we get a blue screen the phone never is the same.
BTW i got 0 imei. And have an theory to this to. The IMEI are related to an operator, so when flashing a official rom not from operator, maybe the phone goes crazy and the IMEI begins to shown 0, it's not a big deal, since we can communicate normally with people.
so how do I install the drivers correctly?
I found a way to revert from 2.3 and I'm in MIUI again but USB issue still there shiiiiiiit
Druida69 said:
so how do I install the drivers correctly?
I found a way to revert from 2.3 and I'm in MIUI again but USB issue still there shiiiiiiit
Click to expand...
Click to collapse
I d0n't lnow, i don't have an solution, I install some drivers that are in huawei server, but with no luck.
The main point is: using a 2.2 rom, all ok, upgrade to a 2.3 rom, and U have problems, so the problem it's not on pc and in hardware, the problem somehow is software.
What I'm wondering it's that the official 2.3.5 help with this problem, but with your report the hope dissapear...
yes the problem is in the device nt in PC.
I think its missing the adb USB drivers inside the device.
and yes its software problem not hardware
Druida69,
Is your IMEI 0 ?
Do you have wifi ERROR in 2.3 Custom Roms ?
I have that USB problem since I tried to format SD Card directly from the mobile, with CM7... all problems started there... and there is another user over here that made the same with MIUI.
nrdl said:
Druida69,
Is your IMEI 0 ?
Do you have wifi ERROR in 2.3 Custom Roms ?
I have that USB problem since I tried to format SD Card directly from the mobile, with CM7... all problems started there... and there is another user over here that made the same with MIUI.
Click to expand...
Click to collapse
ME! Me Me! lol
I have this problem, but don't have problems with wi-fi, my imei is 0 also, but if you use custom or stock 2.2 the usb works fine, so don't think that the problem is caused by formating the sd... I guess is that the libraries in 2.3 somehow changed, i guess the libraries from geno changed a while ago, and therefore this bug appears. It's not for everyone 'cause we all know that x5 have personnality, so...
regarding IMEI yes its 0.
I don't know when it happen and how it was before as I never look for it, up to this moment.
Regarding the USB, I think start to happen when I tried to root the official 2.3.
All drivers in computer are fine as I uninstall them and install all again just to make sure.
Something change something deep inside the phone software and mess all of it.
I manage to do a shortcut though. In official 2.3 you can mount usb storage again if you do this:
dial *#*#2846579#*#*
then you will be inside Project Menu.
Go to Background setting > USB ports setting and you will see these options:
Normal Mode
Google Mode
CTS test mode
Manufacture mode
Authentication mode
Other Mode
By default all systems are with Google Mode activated.
Change to Normal Mode and it solve the problem.
If you try to change this option in CM7 for example, won't work, odd but I don't know why...
Hello !
This USB issue happens to me since CM7 (imei 0, wifi error...). And it happens with all roms (even 2.2.2 stock rom)
I can use usb storage, but in the end I have to manualy mount card again.
With 2.3.5 Official I went into Project Menu and was already in Manufacture Mode, if I change it to Google Mode everything works normally... but after a reset setup returns back to Manufacture Mode.
It is a solution... temporary... but it is
why dont u switch back to cm7 or oxygen and give it a try . surely there is some problem with official 2.3 , mine sometimes says " sd card damaged and stuff .format ... " . am switching back to cm7 . dont want this waste of time rom . ( u know how long we have waited 4 this official update . cant even manage power widgets n LED without external app . f**kin huawie )
mkr17 said:
why dont u switch back to cm7 or oxygen and give it a try . surely there is some problem with official 2.3 , mine sometimes says " sd card damaged and stuff .format ... " . am switching back to cm7 . dont want this waste of time rom . ( u know how long we have waited 4 this official update . cant even manage power widgets n LED without external app . f**kin huawie )
Click to expand...
Click to collapse
As I said before, this problem, regardeless appears more often now, it's not related with the update to official 2.3.5 since I and at least to people more, have this problem before official beta rom appears... It is related to the process of upgrading any rom, and I think it happens when we get a pink screen...