Help please! :( need to nflash b70 device. - Eee Pad Transformer General

Hello, need some help please.
Had my 101 with JB Nightlies rom and wanted to try another rom. I've downloaded super wipe for samsung galaxy S3 and run it in my CWM.
The process didn't finish and the tablet restarted giving me an endless message saying to wait a few moments and that it was deleting everything.
The problem is that this process does not stop and i can't get in CWM again. It just stays there... tried to restart and the message comes again and no CWM.
I figure it out that i have to nflash my device but i never did it. I found Wheelie on this link: http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/.
But i just don't know how to do it on linux... just installed Ubuntu.
Can anybody help me please? :crying:

SWEagle said:
Hello, need some help please.
Had my 101 with JB Nightlies rom and wanted to try another rom. I've downloaded super wipe for samsung galaxy S3 and run it in my CWM.
The process didn't finish and the tablet restarted giving me an endless message saying to wait a few moments and that it was deleting everything.
The problem is that this process does not stop and i can't get in CWM again. It just stays there... tried to restart and the message comes again and no CWM.
I figure it out that i have to nflash my device but i never did it. I found Wheelie on this link: http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/.
But i just don't know how to do it on linux... just installed Ubuntu.
Can anybody help me please? :crying:
Click to expand...
Click to collapse
First don't run scripts that are made for other devices, especially a super wipe script, not only that, some roms done need a super wipe, refer to the install directions on each ROM page.
Second,using olife though terminal is probably one of the more dificult methods to use to do what you need.
Try this
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=tool+one+click+stock
It's basically a simplified package instead of you using terminal, it's really straight forward but ask if you need help.

Great software m8 this is probably what i need!!!
The funny thing is that i've been here for 2 hours clicking on vol + and power button and i can't get in to APX mode and i know that i have the correct drivers installed because after the problem append i successfully connected to APX once

SWEagle said:
Great software m8 this is probably what i need!!!
The funny thing is that i've been here for 2 hours clicking on vol + and power button and i can't get in to APX mode and i know that i have the correct drivers installed because after the problem append i successfully connected to APX once
Click to expand...
Click to collapse
Are you clicking like a short press or actually holding them down.
To get into apx you need to hold both of those buttons down while the power is off, usually for about 5-10 seconds.
If it's boot-looping try holding the power and volume + button for like 30 seconds to 2 mins.
I've gotten stuck in a boot loop before and I just had to hold the buttons down for a while before it did anything.
Keep trying, good luck!
Btw is the script you're running on the internal storage or on an SD card?
If it's not even letting you boot android or recovery I think APX mode is your only hope.

nvflash for b70+ devices: http://androidroot.mobi/2012/05/31/wheelie-for-windows-beta/
edit: oh I didnt saw you already have that

fauxsoul said:
Keep trying, good luck!
Btw is the script you're running on the internal storage or on an SD card?
Click to expand...
Click to collapse
It was from the sd card.
I think my problem is my cable because before this happend to me i tried to copy a rom from the computer to the tablet and it wouldn't connect. I've order another cable from Ebay yesterday and let's see what will happens.
This program is very easy to use so i think i will not have a problem. :good:
Will report when i get the cable
Thank you very much!!!

Well, i tried on another computer and i got in APX mode and used the software to nvflash... it totally worked.
Thank you very much fauxsoul for your help :good:
This means that my tablet will never have anymore problems again despite the fact that is a b70 device except if i drop it on the floor! eheheh
Cheers

SWEagle said:
Well, i tried on another computer and i got in APX mode and used the software to nvflash... it totally worked.
Thank you very much fauxsoul for your help :good:
This means that my tablet will never have anymore problems again despite the fact that is a b70 device except if i drop it on the floor! eheheh
Cheers
Click to expand...
Click to collapse
Nice glad that worked out for you!

Related

[Q] Problems with recovery

Heey guys,
I have a huge problem.
I recently restored my Azure 1.01 rom back to defaults,
BUT now my phone won't boot
I tried to go in recovery on my Windows 7 x32 pc
And on Ubuntu and a x64 machine.
But I still can't acces the recovery functions of my phone.
My phone is rooted though, But in windows i keep getting the message that he needs to install the driver called "Qualcomm CDMA Technologies MSM"
I tried looking around for 2 days now but i can't find anything!
Please Help!!
P.s. I'm sorry for my english
pcfreak13 said:
Heey guys,
I have a huge problem.
I recently restored my Azure 1.01 rom back to defaults,
BUT now my phone won't boot
I tried to go in recovery on my Windows 7 x32 pc
And on Ubuntu and a x64 machine.
But I still can't acces the recovery functions of my phone.
My phone is rooted though, But in windows i keep getting the message that he needs to install the driver called "Qualcomm CDMA Technologies MSM"
I tried looking around for 2 days now but i can't find anything!
Please Help!!
P.s. I'm sorry for my english
Click to expand...
Click to collapse
You can load the default recovery by holding down VOL - and POWER, select RECOVERY, then press AND HOLD, VOL + and POWER to load update.zip which *should* load ClockWorkMod.
Try wiping cache and do another factory reset. First boot may take many many minutes
Edit: Also, no question under development! Mod, please move to general..
Moved to general as not development
Kwen said:
You can load the default recovery by holding down VOL - and POWER, select RECOVERY, then press AND HOLD, VOL + and POWER to load update.zip which *should* load ClockWorkMod.
Try wiping cache and do another factory reset. First boot may take many many minutes
Edit: Also, no question under development! Mod, please move to general..
Click to expand...
Click to collapse
Wow tnx man for your quick response,
I tried your methode BUT it seems that it can't reed my SD-Card
When i select 'Apply sdcard:update.zip' it comes with a lot of errors:
Cant mount /dev/bl......
Cant find /sdcard/upd.....
I checked and double checked if the update.zip was there, it is!
And also i reformatted my SD twice.
But still it wont work i also tried to wipe everything but that wont work either.
I have also noticed that everytime i boot my phone normally it creates a .dm file on my SD!?
in case it is usefull my bootscreen keeps reappearing with everytime a shorter sequence
If yo can help my please!!!
p.s. I'm sorry i placed it in the wrong catagorie...
pcfreak13 said:
Wow tnx man for your quick response,
I tried your methode BUT it seems that it can't reed my SD-Card
When i select 'Apply sdcard:update.zip' it comes with a lot of errors:
Cant mount /dev/bl......
Cant find /sdcard/upd.....
I checked and double checked if the update.zip was there, it is!
And also i reformatted my SD twice.
But still it wont work i also tried to wipe everything but that wont work either.
I have also noticed that everytime i boot my phone normally it creates a .dm file on my SD!?
in case it is usefull my bootscreen keeps reappearing with everytime a shorter sequence
If yo can help my please!!!
p.s. I'm sorry i placed it in the wrong catagorie...
Click to expand...
Click to collapse
It look like your phone i bricked, go into this tread (http://forum.xda-developers.com/showthread.php?t=751265) and follow the steps
HpX said:
It look like your phone i bricked, go into this tread (http://forum.xda-developers.com/showthread.php?t=751265) and follow the steps
Click to expand...
Click to collapse
I thought that to but now the problem is that i can't boot at all!
That i forget to mention maybe!?
But the methode requires to have the phone working???
Or am i wrong?

Bricked my Advent Vega

I posted this in the Android Development Thread under Fuji-Vega. Hope I can get some help with more exposure on my problem.
I think I've busted my Vega. I installed Fuji-Vega V.07, then I wiped the device/factory reset, I then wiped Davlik cache and then I wiped the Battery Stats.
Now its stuck on the Vega bootup animation and it doesn't go any further.
Any suggestions of what to do?
I've shut the device down and powered back on but the same thing happens.
I personally now don't think I should have wiped the caches.
The device Recovery is ClockWorkMod 3.
Help much appreciated.
luckily for you the vega is almost impossible to brick so do a full system restore
http://www.myadventvega.co.uk/full_system_flash_instructions.pdf
If you have a nandroid backup then you can try to restore with the VegaFixer. I wrote a small tutorial how to use it.
C64c said:
I posted this in the Android Development Thread under Fuji-Vega. Hope I can get some help with more exposure on my problem.
I think I've busted my Vega. I installed Fuji-Vega V.07, then I wiped the device/factory reset, I then wiped Davlik cache and then I wiped the Battery Stats.
Now its stuck on the Vega bootup animation and it doesn't go any further.
Any suggestions of what to do?
I've shut the device down and powered back on but the same thing happens.
I personally now don't think I should have wiped the caches.
The device Recovery is ClockWorkMod 3.
Help much appreciated.
Click to expand...
Click to collapse
All fixed now. Many Thanks!!
C64c said:
All fixed now. Many Thanks!!
Click to expand...
Click to collapse
A tip, next time wipe first then flash, not the other way around.
Some ROM have stuff in the data partition that they need and if you wipe after flashing, this stuff is missing when it boots.
VEGA CANNOT BE BRICKED! There's always a way out.
No you have not bricked your Vega it is not possible.
boot into recovery and install the official rom from Advent website by following their instructions. Then reflash your custom rom
Hi Guys,
I don't know if I am in the right thread but I try...
I have kind of the same problem, but with a newly acquired Viewpad 10s (I haven't found any specific section for this tablet in the forum) and I am a true newbie...
I wanted to install the Android Market following the procedure described here:
oudmaijer.com/2010/12/12/android-market-on-pov-mobii-101-tablet/
and after having transfered the market_update0.zip file on my sd-card and applied it through the Software Tool (in Settings menu), the tablet turned off then on.. but I only get a black screen. It won't even show the Android robot picture again.
The stupid thing is that I have no backup rom (the one delivered with the Viewpad 10s) on my computer and I don't even know what I can do (I guess the aforementioned rom for advent would not work)...
Please help! I just want the tablet to work again, whatever rom it uses!
Thank you,
Elena
Try VEGAFixer (a few posts above) to get your tablet back to work without data loss.
If this doesn't fix it, get stock Viewpad 10s ROM and flash it. Get the PDF file from this site as well, so you know how to flash it.
You can as well flash my Gambaro ROM V0.2 ROM. Download the Gambaro ROM V0.2NV version, for this the flash procedure is the same as for stock ROM.
elena007 said:
Hi Guys,
I don't know if I am in the right thread but I try...
I have kind of the same problem, but with a newly acquired Viewpad 10s (I haven't found any specific section for this tablet in the forum) and I am a true newbie...
I wanted to install the Android Market following the procedure described here:
oudmaijer.com/2010/12/12/android-market-on-pov-mobii-101-tablet/
and after having transfered the market_update0.zip file on my sd-card and applied it through the Software Tool (in Settings menu), the tablet turned off then on.. but I only get a black screen. It won't even show the Android robot picture again.
The stupid thing is that I have no backup rom (the one delivered with the Viewpad 10s) on my computer and I don't even know what I can do (I guess the aforementioned rom for advent would not work)...
Please help! I just want the tablet to work again, whatever rom it uses!
Thank you,
Elena
Click to expand...
Click to collapse
Thank you BeeGee_Tokyo!
I followed the instructions of the pdf and downloaded the files from the official link and after having struggled a bit for the reboot procedure (with the timing if the back/power buttons).
Then it went smoothly!
You are a guru BeeGee_Tokyo, thanks again!
I will definitely try your ROM soon too!
Elena
Got same problem few times on my Viewpad 10s. At last I installed market via CWM and finally it works fine.
yioti said:
VEGA CANNOT BE BRICKED! There's always a way out.
Click to expand...
Click to collapse
So I will give it a new try.
It seems mine is broken.
No Advent Vega, but POV Mobii - however using nvflash to put back Stockrom on machine is the same procedure on both.
POV got rooted with this Add-On.
http://forum.xda-developers.com/showthread.php?t=931337
Put CWM on tablet via Recovery Easy Install ( http://android.modaco.com/content/a...d-clockwork-recovery-3-0-2-4-easy-install-v2/ )
and Wireless ADB. (No ADB via USB with POV because OF different USB-behaviour)
Yesterday tab was runnning fine - nothing put on additionally (my Mom is using it) and suddenly restarting the POV only gives a black sreen (backlight is on, but nothing else to see)
Drivers are fine - NVIDIA USB-Boot-recovery driver shown in Win7x64. OS is recognizing the Tablet when switched on with specialkeys connected via USB.
Running ****POV-Full-Flash.exe or ****Vega.exe gives the same message in DOS-BOX:
"Unknown device found"
Press enter to continue
So connection s good, but for whatever reason device is not recognized as vaild.
Did flash Stock-Rom 2 days before this way succesfully. (purchased as returned but new article and wanted to start from clean ROM)
I am having a Nadroid-Backup, thought easy cake, StockRom - CWM and restore nandroid - but I am totally stuck...
Any hint to get out of there welcome..
I don`t wanna t be the first who succeeded in .. *Grmpf*
For whatever reason flashing the StockRom via nvflash was possible now - nvflash accepted the connected device.
So I am not the first one who brickes his POV/Vega
HELP Hard Brick Novice
I thought I could do it I really did... I cant, I cant hack, or do anything with code... its just not me.
Today I tried to flash my Viewsonic Viewpad 10 with a rom (vegan tab) and completely bricked the device. I see posts about restoring the system using an SD card... problem the system runs on the internal SD card is there anything I can do?
Ok, I'm usually a lurker, but I need help.
HAppens that I was trying VegaComb 1.5.2 (works great, but I NEED flash) and decided to go back to CorvusV5. I flashed correctly, or so I thought, but now my Vega loops on the Boot Logo.
I've tried to get it into NVRecovery, but the screen just flashes with light for 2-3 secs and then the device turns off everytime I repeat the sequence. Additionally, the PC does not seem to recognize the device at any time.
Some help here?
Thanks!
jhondidfool said:
Ok, I'm usually a lurker, but I need help.
HAppens that I was trying VegaComb 1.5.2 (works great, but I NEED flash) and decided to go back to CorvusV5. I flashed correctly, or so I thought, but now my Vega loops on the Boot Logo.
I've tried to get it into NVRecovery, but the screen just flashes with light for 2-3 secs and then the device turns off everytime I repeat the sequence. Additionally, the PC does not seem to recognize the device at any time.
Some help here?
Thanks!
Click to expand...
Click to collapse
screen does not come on in nvflash mode your doing it wrong
right turn of vega (hold power for 6 secs)
put vega on charge connect to computer via usb
hold back for two seconds
hold power until computer bleeps recognises device
release power then back
ensure correct drivers installed
run recovery program
Edit: You will never brick your vega no one ever will if it is at all possible it will be an extremely experienced dev doing something extremely complicated you cant do it from CWM im not annoyed just informing you all
Fixed! thanks!
what most people forget, including me, is that you need a minimum 60% charge before you can flash the stock rom using the power button method, so you can press away all you want, but if it's not charged, it's not happening
Although I followed all above instructions, I can not restore my Vega.
Had it off for a couple of days, tried to switch it on and it stuck in blank screen (screen on). Have it on the charger but light indicates battery is full (thought that battery could be dead).
Used the Advent Vega Driver Installer, drivers are installed properly, but can not enter recovery mode at all, every time it goes into this "blank screen" state with the screen being on.
Any ideas?
have you installed vega tools?

[Q] A500 Boot Issues...need assistance

I've searched and found a few similar (not identical) problems that people were having, and tried some of the solutions, and none have worked.
I'm trying to fix this stock Acer A500 for a friend. It will boot up part way, goes past the acer screen and android screen, but then stops at a black screen with 'android system' in the upper left corner, the home and back buttons in the bottom left, and the time, signal, and battery life logos in the bottom right. Then there's the Power Off thing in the center of the screen, and it says shutting down but it never shuts down.
I boot into the stock recovery mode, and it says in the upper left on the acer screen:
erasing cache before SD update
SD update cmd: recovery
--update_package=sdcard:update.zip
booting recovery kernel image
then it shows the android with the turning gears, then goes straight to the android with the warning symbol.
Since I can't get into the OS, i have no idea which version or specific model this is, but i downloaded a few different honeycomb update.zips, and put those on the SD card, and when i tried booting with those, the loading bar pops up under the android logo, and it goes to about 1/3 of completion before switching back to the warning symbol.
I tried downloading what im pretty sure was a full version of jellybean for this tablet, and it went straight to the warning symbol, no loading bar. same when i tried renaming the file update.zip >.>
im clearly very new to all this, but i'd really like to get this thing working.
is there a way to do a factory reset without booting all the way into the OS?
im not sure because it seems like the only file its looking for in recovery mode is update.zip.
if anyone has any bright ideas, id appreciate the help.
Also, not sure if this is relevant, but when i boot it normally, and it goes to the 'shutting down' screen, the battery level indicator says its almost dead, but i can leave it plugged in for hours and nothing changes at all.
EDIT: Also, it won't even boot if the power cable is not connected.
Similar issue hope there is a solution
I have a similar problem. Tablet was working fine, sitting on docking station. Returned to it the next day and when I went to wake it, it would not wake. Rebooted it but will not reboot. Sits on the ANDROID screen after the ASUS title screen indefinitely. If I try and boot into recovery it fails at "update.zip" and I see the broken Android image laying there.
Is there a means to restore it from PC via the usb cable and can someone please post a very noob friendly walk through step-by-step?
Greatly appreciate any positive advice!
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
zardoz99 said:
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
So, dead chip? So soon? Nice.
NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
Yep.. 14 months old in my case. Contacted Acer and said "what about a fix?" They said, "no chance unless you cross our palms with lots of silver."
So, bought a Samsung Note 10.1 instead. Acer can "stuff it". I won't be buying a tablet from them again. Considering that I bought their "flagship" product of the A501 with the 64GB memory, this is truly unacceptable.
I was incredibly careful with it and certainly never did anything to void the warranty. But, you only get 12 months and then it's over.
NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
skurtov said:
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
Click to expand...
Click to collapse
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
NoOneSpecific said:
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
I'll have him PM you when he is able.
Thanks!
skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
coluwyvurne said:
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
Click to expand...
Click to collapse
You are quite right sir, however the button combination I am most familiar with is holding the power and the reset button (the one you have to stick the paper clip in) when you first start it up. It should then either say APX mode on the screen or be blank, either way the computer will identify it as a APX device and automatically install the drivers.
Going into APX MODE manualy
You enter APX mode by holding down the Reset button(with paper clip). Do not release it. Hold down power for 3 secs and then release it. After another second, release the reset button.
Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
The screen of your tablet is black.
Quoted from Civato
Click to expand...
Click to collapse
The next course of action is to get the SBK, from what it sounds like the tablet didn't write a partition properly and that's why it's not booting. So what you can do is wipe out the partitions and install a custom bootloader and recovery. Not only does it fix things but it also opens up his world to custom roms . Okay, back to the matter at hand, I don't know if he has his SBK or not, and if he does skip the step to find it and just run babsector below. If not then follow the next step.
You'll have to pull the UID from the tablet using this method described here:
http://git.pappkartong.se/?p=a500/apxuid.git;a=snapshot;h=HEAD;sf=tgz
There's a readme
After getting the UID and calculating your SBK you'll just go to the next step.
All credit goes to user eppeP.
Click to expand...
Click to collapse
Run this file hosted here:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
And this file basically rewrites and formats the partitions out installs a custom bootloader and recovery
Credit goes to Danny2 for finding this and posting it.
Click to expand...
Click to collapse
Once this is done, pick a new rom. I prefer the Civato ones, load it on a SD, boot to recovery, erase dalvik cache, cache, do a factory reset wipe (from the recovery menu!), then wipe system, flash the rom and go on your merry way
Many thanks for the reply.
As per your instructions, I have booted the tablet into APX mode. However, as I do not know the UID of the device, I've had to try to run the utilities to create a driver for the device and then pull UID from the tablet...
I am able to create the driver for the device and install it with driver signing off in Windows, but I can't figure out how to run the script to get the UID. I notice the file in the package you directed me to contains an .SLN file, which would indicate it is a programming solution file. I have Visual Studio on my system but it cannot open this particular .SLN file.
How would I run what's in the package to pull out the UID of the tablet?
Any help getting past this hurdle would be much appreciated!

ACER A500 Iconia Tablet -- Stuck at Acer Logo...

Was using tablet and just playing a game -- tablet reset, robot with ! showed up.
After that, reboots bring me only to the Acer screen.
I can do the VOLUME UP + POWER -- vibrates, powers up, toggle the switch, let go of power button and it does:
ERASING USERDATA...
ERASING CACHE...
Then it reboots back to the ACER logo, and just sits there. I have downloaded one of the ROMs and done the VOLUME with POWER BUTTON start up and it doesn't do anything. Just stays at ACER logo.
I've looked at quite a few things here on the forums and it hasn't done me any good -- nothing seems to want to work with the tablet unless it's in debug mode (which means it has to be a working tab). When connected to a PC it does detect as an MTP USB DEVICE and says "THIS DEVICE IS WORKING PROPERLY." But I can't get much of anything. The only thing I've used that remotely works is USBDEVIEW which gives me the device info including a serial #, which I understand is NOT the cpuid. I do have the box, so I guess that would have the CPUID? Any help appreciate. More than willing to just blast this thing with a one touch factory reset from the PC, if it will just connect.
If you had it at the dead android guy, it means you probably didn't have the decrypted "update.zip" on your Ext SD card. If you had stock ICS running before, you can try downloading those 4 update.zips I posted a few threads ago. Will have to try each one, and hopefully one of them works.
Here's the post...
http://forum.xda-developers.com/show...54&postcount=2
This would be the first thing I try.
MD
Moscow Desire said:
If you had it at the dead android guy, it means you probably didn't have the decrypted "update.zip" on your Ext SD card. If you had stock ICS running before, you can try downloading those 4 update.zips I posted a few threads ago. Will have to try each one, and hopefully one of them works.
Here's the post...
http://forum.xda-developers.com/show...54&postcount=2
This would be the first thing I try.
MD
Click to expand...
Click to collapse
It went to the Dead Android guy when it rebooted after a crash. I haven't seen it since. Just got to the Acer logo screen and stops.
Your linked post is going to what it actually shows instead of the real link.
Fastboot
Sent from my Kindle Fire using xda app-developers app
Vintage144 said:
Fastboot
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Don't think he has V8 bootloader Mate.
Moscow Desire said:
If you had it at the dead android guy, it means you probably didn't have the decrypted "update.zip" on your Ext SD card. If you had stock ICS running before, you can try downloading those 4 update.zips I posted a few threads ago. Will have to try each one, and hopefully one of them works.
Here's the post...
http://forum.xda-developers.com/show...54&postcount=2
This would be the first thing I try.
MD
Click to expand...
Click to collapse
I'm also stuck at the ACER logo. I d/l'd all four of the zips from your link. All four appear to install correctly but when the flash finishes and the tablet reboots, it's still stuck at the logo.
Also, when I just tried the link again, it is no longer working.
where were you coming from when you tried this ? what BL? gb?JB? what recovery , theres a alot of reading to be done with this device Acer didnt make it easy , but if you read and take it slow there are/were some great devs that left the door open for us all to use these ? Explain where your started from and how you got to where you are now? (Moscow is a sharp dude he can help)!
Vintage144 said:
where were you coming from when you tried this ? what BL? gb?JB? what recovery , theres a alot of reading to be done with this device Acer didnt make it easy , but if you read and take it slow there are/were some great devs that left the door open for us all to use these ? Explain where your started from and how you got to where you are now? (Moscow is a sharp dude he can help)!
Click to expand...
Click to collapse
I bought the tablet used and it would loop on the green "ANDROID" screen. So I don't know what version it was on. I tried the volume +, rotation left and power on to clear the cache and user data. After that it hangs at the ACER screen. I'm assuming it had HC because it has standard recovery. IOW, if I hold the volume - when powering on, it goes to the green Android logo and if an "update.zip" file is present, it will flash it. I've tried just about every "full" ROM I can find and most of them flash but none of them get past "ACER".
I've tried pushing the reset button while powering on while connected to both a Linux box running Mint 15 and a Win7 box. The Win7 box see the tab but won't load the driver. Even though I d/l'd the USB driver from the Acer site. Mint 15 sees the tab but comes up with the error box saying it can't be mounted.

[Q] Stock Nexus 4 bad install of 4.3 OTA

Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.
gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:
Didn't work Will try other method
Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.

Categories

Resources