Related
[Edit] I got the CM 1.4 recovery to flash and updated CM from sd card... Then hit reboot. It's been sitting on G1 screen for like 10 minutes. Do I need to wait longer or is this a bad sign? What should I do?
Please help!
THank you!
------
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.
arsieiuni said:
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.
Click to expand...
Click to collapse
A couple of things:
5.0.7 IS the latest stable build. If you want 4.2.15.1, you're going to have to search the forum for it because Cyanogen is no longer working on Donut (1.6) builds.
However, if you want the latest CM, its very simple.
First, download either the latest clockwork recovery or amon_ra recovery. follow the instructions to flash recovery. to check if it installed correctly, you dont power on while holding X, you power on while holding the home button. (alternately, grab the "quick boot" app from the market and you can one-touch boot to recovery or bootloader from your home screen)
Next, download the latest radio and appropriate SPL. In order to install these, follow the instructions here:
http://wiki.cyanogenmod.com/index.php/DangerSPL_and_CM_5_for_Dream#Prerequisites
Note: MAKE SURE YOU FLASH THE RADIO FIRST OR YOU WILL BRICK YOUR PHONE.
Once you follow those steps, you'll have CM 5.0.7 installed.
EDIT: I noticed you grabbed CM recovery 1.4. That recovery is old and outdated, also no longer supported. You need to grab one of the recovery files I mentioned.
Crap...
So trying to follow the instructions at Cyan WIki...
And like I said above, it's now sitting on G1 screen indefinitely...
Have I lost my phone?
Is there any way to fix this?
power off the phone by pulling the battery. boot into recovery by holding home+power. plug your phone into your computer. once there, use ADB from your computer to flash the new recovery, then power the phone off again. power it back on into recovery again (home+power) and then follow the steps in the wiki page i linked you to.
OMG that's wonderful I thought I had ruined it!
But I have no idea how to use ADB. I have never used it before. I found the site but I'm totally lost at that point o_o
If I plug phone into my computer it doesn't recognize to let me access the folder so I can't add files there since I can't Mount it.
How do I add the recovery from ADB?
ok, first things first, make sure you have your drivers installed and adb working (for this, youre going to need the adnroid SDK installed, which can be found here: http://developer.android.com/sdk/download.html?v=android-sdk_r06-windows.zip). to check and see if adb works, open a command prompt on your computer(start>run>cmd), navigate to the sdk tools directory (for example, mine is C:\android\tools\ yours might be different depending on where you install the sdk) and then type "adb devices" without the quotes. if it shows your device connected, proceed to the next step:
Copy the recovery image you're going to install to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your G1 via usb to your computer and type the following commands into the command prompt
adb shell
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/custom-recovery-name-here.img
once that's done, you will have your new recovery going, then proceed with the steps to upgrade the radio and SPL from the wiki page i linked earlier. after you have the radio and SPL done, flash CM and you're all set!
Okay... I tried to use the SDK to install the drivers (it says in INstalled packages: Drivers r3) but It's not showing up under ADB devices when I check it in CMD.
It just says List of Devices: then there's nothing.
I think maybe because my phone won't go past recovery right now, I can't get the drivers working?
Is there a place I can manually download the drivers so I can manually install them?
I went in and followed the instructions here; http://developer.android.com/sdk/win-usb.html to install or upgrade and either way my computer is telling me I have the best driver installed for the HTC android phone. I don't SEE a place exactly like they say that says ADB Interface device.. that doesn't even appear on my list.
I really, really wish I could find my sd card adapter. That would make this considerably easier.
Please could someone help with the last question above?
I'm trapped at this point and can't figure out how to go onward.
For starters, don't flash your radio or SPL. FASTBOOT them.
Setting up adb is very useful. Download the sdk and extract it to where ever you want it and add the "tools" folder to your windows Path. There and HUNDREDS of tutorials on how to do this. Google it. Fastboot is just as easy as using adb, and safer than flashing.
I've made this thread to focus our investigations about the problem in just one thread.
The problem is originally made when you use a odin3 flasher for captivate, that downloads on your phone the stock version of the captivate rom, that has different radio version and locks the phone while booting, entering in a never-ending boot cycle.
As the captivate has different button layout, we can't enter in download mode, but it stills on the phone. The screen doesnt' show when the usb is plugged, i dont know why yet.
I've managed to get one loading circle by plugging and unplugging repeatedly the USB while pressing vol+,vol- and power button (i think its probability to get it, i'vent seen any specific thing that enables it) , and lasts until you stop pressing one of those buttons, but i haven't been able to connect the usb while its, and check if in that screen the phone answers the adb/fastboot commands. Every button combination you may imagine/read doesn't work, so we'll have to use a software method to get into the download mode
For all the people affected, make a batch file with this
Code:
cd [directory where you have adb.exe]
:1
adb wait-for-device
adb reboot download
goto 1
and plug/unplug the usb, to check if in a concrete phase of the boot procedure the rom listens to adb.
Threads of affected people:
http://forum.xda-developers.com/showthread.php?t=749546
http://forum.xda-developers.com/showthread.php?t=735462
and much more people that is not in this forum
We hope help from developers, thank you.
Any luck getting adb to recognize??
Here no luck
Any progress with this more and more users have problem with this wrong flash
I suggest contacting with the creator of the odin 3 captivate flasher to warn i9000 users that it'll brick the phone
Guzmanus said:
I suggest contacting with the creator of the odin 3 captivate flasher to warn i9000 users that it'll brick the phone
Click to expand...
Click to collapse
I agree... The programs look exactly alike, and so much for the "download mode always remains untouched" comment people were throwing out there... It appears Odin does make changes to the download mode, or at least the captivate's odin does... Is there another Odin for the vibrant as well? and what happens to the captivate and vibrant when they are flashed with the i9000's Odin?
I've read something about that vibrant users can flash i9000 roms without any problem, but im not sure about captivate users
samsung captivate brick
i have the same problem... im running windows 7 x64(64 bit) and i was updating my phone to the rooted 2.2 froyo update via odin with the "I897UCJI6-OCD-REV02-Low-designgears" while updating the phone when the odin program froze and ruined/bricked my phone... i have tried all the steps to try and un-brick my phone but at this point im about ready to give up.... at this point my phone will not power on in any mode nor will it go into recovery mode or download mode... if any one has any info on how to fix this please let me know....
Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.
+sticky
excellent write up. a must-read for anyone even thinking about flashing
Original Post updated to add my information
bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.
STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App
This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky
Bump Bump Bump
Great Info
Updated original post with extra info.
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
Thanks, great info.
FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.
+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App
Moving this to the top. More questions in QA that can be helped by reading these tips first.
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!
thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.
I bought an Acer a500 tablet a few days ago not knowing how broken it is.
After loads of research and attempting different techniques I still haven't had any progress.
The software issue:
When booting up the tablet, it goes to the black screen with "android system" at the top and power off/ shutting down in the middle of the screen.
Fixes I've tried:
1.
Since I don't know anything about what operating system is on this tablet, I have been blindly flashing different "stock" (from Vache) versions of HC.
--The android logo with gears shows up, the green bar loads but freezes when it gets 1 cm away from finishing.
--After turning off the tablet and booting it up again, "updating bootloader shows up on the upper left hand corner of the screen. Then a message pops up saying "apk installer: all pre processes complete". Then it returns to the black screen.
2.
The tablet will not go into apx mode (using the reset botton at the bottom).---Fixed. I didn't execute the steps properly. Apx mode works fine.
3.
I plugged the tablet into an older windows laptop and the computer could not install the correct drivers to sync with the tablet. Again also my lack of knowledge. I installed drivers from Acer.com
4.
These two guides seem to be exactly what my problem is but I can't seem to make sense of them:
http://forum.xda-developers.com/showthread.php?p=24531880#post24531880
http://forum.xda-developers.com/showthread.php?t=1572622
This is as far as I've gotten.
Other complications:
--The battery is dead. I have to use it while plugged in by the charger.
--Most of the thread that I have looked at use Megaupload as the source of downloading their files.
--The original owner of the tablet will not help me out. As I stated before, I don't know what version android OS was on here before it was bricked and on top of that the original owner won't answer my questions. As far as I know though, this tablet is not rooted or has anything "non-OEM" installed in it. The story goes that this tablet was bricked when the owner tried to "update" it. Before that, it was functioning perfectly.
-----It looks like Darvis is having the same issue and frustrations I'm having but reading his threads makes me think that this tablet is a dead end.
http://forum.xda-developers.com/showthread.php?t=1427983&page=4
http://www.androidtablets.net/forum...32467-please-help-me-unbrick-my-iconia-5.html
If someone could point me in the right direction toward fixing this tablet, I would appreciate it very much.
Thank you for reading my Thread.
KiwiN said:
http://forum.xda-developers.com/showthread.php?t=1572622
Click to expand...
Click to collapse
First off......I hope u didn't pay much for the tablet.
Secondly the guide above looks pretty straight forward but maybe this is one of the ones that has files at megaupload?
I know that the ra recovery and timmydean's files are accessible as I have downloaded both of them.
Maybe someone who has done this previously will chime in and get you the other file if it is indeed unreachable.
Sent from my A500 using xda premium
I would suggest trying to connect the tab to a Windows 7 PC after installing the USB drivers from ACER. Then check if your device appears in the device manager. As long as you have its UID you can flash the tab from the PC with one of the EUU tools - check my signature on "how to revert to 3.0.1" or TimmyDean's thread which offers an EUU with rooted HC 3.2.1 (it's linked in my thread as well).
How exactly did you try to get into APX mode?
p.s. I have the EUU files if you can't access them from the threads links. I can send them to you.
getting into apx mode
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
I'm trying to follow the instructions from the root 3.2.1 v4 file.
I can't perform the first step where it instructs me to turn on Usb debugging. The problem is that I can't open the settings by clicking the clock. Nothing happens.
I realize that one complication of my tab is that it will not charge. The battery power is below 15% so none of these fixes might not be effective for me. That might be the ultimate problem?
CyaN1de-
I paid $100 for the tablet. As of this moment I feel like I paid too much.
Thank you both for you quick replies. I have to say that most of the problems that I'm having is because of my lack of experience but I'm learning. I hope I fix this tab soon.
if this dont fix it, i'll give you what you paid for it;0
someone posted a while back that a hard reset fixed the android systems screen error
not sure where you're at now but no harm in trying it
Try using hard reset:
1) Turn off your tablet,
2) Rotation lock s to your left;
3) Press Vol+ (which is next to rotation lock) and power on simultaneously
4) As soon as the tablet vibrates you can release the power on button and you
should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
Thanks for the suggestion but I didn't accomplish anything by hard resetting it. I've done this many times and nothing has changed.
I haven't given up on unbricking this tablet yet and even though it's frustrating I'm learning from the process. If I decide to sell it, I'll contact you Dibb.
KiwiN said:
.....
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
Click to expand...
Click to collapse
i've seen the 2 methods u described but i've not seen anyone else have success with it apart from the OP'ers - seems OTT to me but hey if it works for ya...
I've used timmydeans method ALOT on HC it never failed to work and that includes reverting back to HC from ICS - if it doesnt work for your issue then id be tempted to use blackthund3rs APXFlash Tool and civato's HC_ICS_Bootloader zip to flash a new bootloader and rom package on yr tab - but for the moment we'll run with td'sv4 - if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
as i said this is worth a go,,,,how about the update.zip have u tried that.....
else the only other way i know is apx flash....ya still need to get into apx
mode and if u cant then ???? sometimes youll try something over and over
and then out of the blue it will work...you'll swear you never did anything different , it jsut worked this time.....
hope you find some joy
Thanks Dibb for your words of wisdom. I've put it aside for now but I'm going to pick it up in the morning.
As addition to what dibb_nz said - Windows 7 would do the trick - I'm almost 100% sure you'll be able to connect in APX mode with the drivers properly installed. Then use one of the EUUs.
Drained battery really looks like the ultimate problem now because as far as I know you cannot charge the tab in APX mode - haven't tried that. Eventually I would suggest to crack the tab open, remove the battery and charge it somewhere - I don't know alternative ways but...may be another tab or you own charger with proper connector ...
http://www.youtube.com/watch?v=xvXihNIdQ1M
p.s. 15% power ... seems enough to flash through the PC...but who knows - don't waste them and get everything you need before starting the procedure.
no probs m8 hope u have better luck tomorrow
if u wanted to try the EC method i have those files if you want them
good luck m8
dibb_nz said:
if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
hope you find some joy
Click to expand...
Click to collapse
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.
KiwiN said:
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.
Click to expand...
Click to collapse
do u get on yr tab the big 'PASS' in white leetters or "entering download mode" at all???
think we're beyond update.zip if EUU failed but you can try it -
you can get to apx which is a start - getting a new boot/recovery image on there is the main priority I think...as i posted earlier i've only ever seen a fix for this problem work for 2 people, so on new ground here....
But anyway check out the APXFlash method/walkthru in my sig....all the info is in there and the links to the required files ....do we know if you're on HC or ICS B/L????
I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
dibb_nz said:
yes if you're talking about the stock roms from vaches thread, you need the full rom package - you cant just use an 'update' package as they need a full rom to work properly....
for instance my original HC3.2.1 Stock build is 7.014.15_COM_GEN1
and theres no FULL Rom for 3.2.1, so i have to use the HC 3.2 FULL instead
.....Acer_A500_7.006.03_COM_GEN1.zip
Once flashed, thankfully I recieve the 2 small OTA Updates to get up to 3.2.1 again
Another couple of days the ICS OTA d/l'ed and installed with no probs....
is that clearer or am i making things worse????
Click to expand...
Click to collapse
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.
KiwiN said:
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen.
Click to expand...
Click to collapse
I could never get mine into apx mode with the usb cable plugged in. So try that if you haven't. And it is literally hold reset, then press power, without letting up on the reset, release the power button after 3 seconds (use a watch or timer!) then one more second before you release the reset... It does work, but the timing has to be close. It must have a tenth of seconds or less tolerance. Very picky... I've done it on 2 different a500s so far and I am heading to do another tonight. If it doesn't work I'll be right back!!!
KiwiN said:
I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.
Click to expand...
Click to collapse
Hi m8 Hwya goin - just got home - what's the lay of the land???
Holey motley we just had a good shake....thort was gonna carry on thank fk it stooped, phew, just been awhile since we had one like that, scary
Crikey just as I finished typing "....land"
Back to more important matters..... whr u at m8????
None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?
KiwiN said:
None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?
Click to expand...
Click to collapse
recovery mode???
u need a new boot and recovery image on that thing
the HC EUU based flash arent working even tho u got a PASS on screen after TDv4
So HC based methods arent up to it. You need nvflash/fastboot.
We need ICS with the unlocked bootloader it has access to another level below where HC worked because HC b/l is and always has been locked down.
If ICS cant fix it, I have no idea what will and my offer to buy is off the table!!!!
check out civatos guide and ready yourself for nvflash via zip files in that post or blackthund3rs APXflash tool, with a complete tutorial for using it, all links in my sig.
good luck
Just to chime in with a tip on getting google drivers to work.
When getting any device not recognized, or driver error, generally I go into windows device manager, select the unknown or offending device, update driver, only I choose which driver to use, and ignore the error message where it says "may not be compatible with your device", and use it anyhow.
I get that occassionally when swapping back and forth between devices.
Also, battery not charging and display errors, are usually a sign of EC Power control. So you were on the right track about that. Once you get a rom up and running, if the batt don't charge, then there are some EC flash's you can do from CWM.
Back at it again using BT's nvflash tool. And tablet is still bricked.
I've tried a few different bundles and none allow me to operate the tablet. Everything goes smoothly and I get "pass" at the end of the process. When I go to reboot the tablet, it gets stuck at the black start up screen.
Found another lead: http://forum.xda-developers.com/showthread.php?t=1579490
Sounds like he was in the same situation as I am but has a bit more skills and knowledge dealing with problem solving.
You say you were able to flash roms. So apparently recovery is working OK. Have you tried flashing civato's flexreaper? It has code that will detect whether you bootloader is HC or ICS. You may just be flashing a rom that doesn't match your bootloader... I know I'm jumping into the middle of this, but it's just a thought.
Also, when you did the hardware reset with the rotation lock switch did you get the confirmation that it was, in fact, being wiped?
Failing all that, I'd be willing to take it off your hands for spare parts...
Sent from my A500 using Tapatalk 2
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
I had heard it was coming. Good deal. Now I can give up root to get repaired without fear.
Could someone host the two needed files somewhere? Its a pain in my ass to load these from these Chinese hosters...
coming soon! uploading to hotfile..
hope helps
https://hotfile.com/dl/169617659/de8c673/CWM.rar.html
https://hotfile.com/dl/169617791/ac3fa3c/root.rar.html
nsxt99 said:
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
Click to expand...
Click to collapse
Any steps to follow on how to root my TPT ROW on a mac?
Does not work at all for me. nvflash shows me the typical 0x4 error when it tries to injct the bootloader bin file...
This will work only on unlocked devices, because it uses nvflash and i can't find any sbk in the bat files (cwm.zip). The root.zip only contains the known exploit for devices below ICS.
nsxt99 said:
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
Click to expand...
Click to collapse
Yes, I heard this and tried it on my US 32Gb version, but i failed.
Got an write/read error/warning, then the program stopped.
As I know, this rooting method ONLY works on ROW versions, but not US version.:crying:
It did fail, but did not bring any bad effects to my TPT. I just updated to the stock OTA3.5 smoothly.
Anyway, thanks for sharing.
Hey guys, i just wanted to tell you that it worked for my OTA3 TPT ROW.
Tip: try extracting the recovery image from your rom (eg. US) and put it instead of the one provided in there rars, it might work for you.
Cheers!
Google did it's best to translate the think but I'm a little weary to try it as the steps are still a bit garbled.
EDIT: Does anyone have a stock rom? I'm looking to do what the last commenter suggested and switch out the image.
goodboynyc said:
Google did it's best to translate the think but I'm a little weary to try it as the steps are still a bit garbled.
Click to expand...
Click to collapse
I followed the translated instructions and am now running CM10 on my 16GB ROW. It's fantastic -- like having a new device.
The instructions are pretty simple to follow. I had one problem though.
To use nvflash, you need to start the tablet by holding down the rotation lock button and then install the provided driver in Windows. This works well. However, after performing a flash, Windows would no longer recognize it if you power it on while holding the rotation lock button. To gain access to the special recovery mode again, I had to uninstall the device and driver in Windows Device Manager, and the reinstall again when prompted.
Because the whole procedure requires multiple flashes with nvflash, I had to perform this uninstall-reinstall process several times.
Other than that, it worked perfectly well.
Hope this helps if anyone encounters the same issue.
Does this mean we have the key for nvflash?
Sent from my ThinkPadTablet using Tapatalk 2
My question in regards to this is can we build a flashable rom of this? And would this work with the US TPT?
Sent from my ThinkPad Tablet using XDA Premium HD app
crabnebula said:
I followed the translated instructions and am now running CM10 on my 16GB ROW. It's fantastic -- like having a new device.
The instructions are pretty simple to follow. I had one problem though.
To use nvflash, you need to start the tablet by holding down the rotation lock button and then install the provided driver in Windows. This works well. However, after performing a flash, Windows would no longer recognize it if you power it on while holding the rotation lock button. To gain access to the special recovery mode again, I had to uninstall the device and driver in Windows Device Manager, and the reinstall again when prompted.
Because the whole procedure requires multiple flashes with nvflash, I had to perform this uninstall-reinstall process several times.
Other than that, it worked perfectly well.
Hope this helps if anyone encounters the same issue.
Click to expand...
Click to collapse
I need to try this. But from what I understand this only works for ROW versions and not US versions(given the attached files from the OP). If someone could post an image of a US version I'd cross my fingers and give it a go.
I can't even get past CWM.bat.
I get an NvError 0x30011.
goodboynyc said:
I can't even get past CWM.bat.
I get an NvError 0x30011.
Click to expand...
Click to collapse
Same here and before is a hidden 0x4 hidden by a CLS command inside the script.
I'd be great if we could get some developers input. I program in C++ and Visual Basic but have no experience with Android/Linux to be able to look deeper into this :S
Moved To General​
If somebody wants to write a guide and supply a proper dev section thread, fine. But this thread is not development.​
Hi, I have succesfully rooted my ROW 16GB Wifi-only ICS 4.0.3 tablet following chinese guide. Excuse my english, Im not native speaker . I'll try to explain what I did:
1. make sure you can see your TPT with "adb devices" command.
2. turn off your device, make sure you have USB cable connected, hold rotation lock button + power on device to get to APX mode. Screen will not turn on, but windows will find new APX hardware unknown.
3. update software driver for APX, set CWM folder manualy. You should now have NVIDIA USB Boot-recovery drover for Mobile devices installed.
4. in APX mode run "cwm.bat", after its done, reboot device to APX mode and press any key, dont press it before you restart your device. You can see CWM_recovery.img installing to your tablet. Follow instruction...
5. After step 4 is done, reboot your device to Recovery, when you see small lenovo logo spam volume up button until you see "booting to recovery kernel mode".
6. Navigate to mount and store using vol +/- button, power button to confirm. Select mount /system
7. make sure you can still ses your device using "adb devices" command, and run root.bat, follow instruction. When all is done, select power off in recovery menu.
8. Now you have root, but you cant boot to system. You need to get to APX mode again and run "403 recovery.bat", follow same steps as with "cwm.bat".
9. reboot and you should now have rooted TPT.
Hope this help, Im not so good at giving instructions .