Related
I have a B70 transformer (just 20 days old). Rooted with universal rootkit.
Wanted to install Ubuntu[emmc install].
Checked sbk version using sbkcheck uitlity. It first gave sbk version 1.
So went ahead Ubuntu install. Could'nt complete beacuse of "connection failed nverror 0x8".
So again ran sbkcheck utility. Got some error cant remember.
and now i cant do anything.
Just displays Entering NvFlash recovery mode when plugged in to usb.
Tried nvflash unbbricking gives "USB device not found"
Please Help!!!
You can try to use NVFLah unbricking method.
http://forum.xda-developers.com/showthread.php?t=1123429&highlight=nvflash
Tried nvflash unbbricking tool it gives "USB device not found"
I just ran into something along these lines too, accept i was installing the ICS alpha build.
I used the NvFlash from the revolver 3.11 thread to get back to a working state at least
Download link to NvFlash:
http://www.multiupload.com/PFMWB39SK4
Just run flash.bat
1pratham said:
I have a B70 transformer (just 20 days old). Rooted with universal rootkit.
Wanted to install Ubuntu[emmc install].
Checked sbk version using sbkcheck uitlity. It first gave sbk version 1.
So went ahead Ubuntu install. Could'nt complete beacuse of "connection failed nverror 0x8".
So again ran sbkcheck utility. Got some error cant remember.
and now i cant do anything.
Just displays Entering NvFlash recovery mode when plugged in to usb.
Tried nvflash unbbricking gives "USB device not found"
Please Help!!!
Click to expand...
Click to collapse
do you get the transformer into apx mode at all?
Thanks for your replies
Got nvflash unbricking tool working from windows. Don't know why it wasnt working on linux.
All fine now.
Just to make sure, since the unbricking tool worked, does it mean I have a sbkv1 device?
Yes you have sbk v1
I have a similiar problem. But i have an 3G model (TF101G), and its not mine its from a friend.
When i power on it only gets to the Eee pad Logo, than it stays there.
Can get into the wipe menu, where you can choose between wipe and "cold booting Linux", but cant get into asus recovery menu (Android Guy with gears).
Tried also nvflash with Windows and Linux, but everytime error "0X4".
my SN begins with "BA0K", so probably a SBKv3 device or?
But i cant be brick! there must be a way, because i can get into the Asus wipe menu and into APX-Mode. Everytime here in the forum its said that this is not really a brick, but perhaps though?
I hope not.
Or have i to be wait until the SBKv3 key will released?
pls help me
When i power on it only gets to the Eee pad Logo, than it stays there.
Can get into the wipe menu, where you can choose between wipe and "cold booting Linux", but cant get into asus recovery menu (Android Guy with gears).
Tried also nvflash with Windows and Linux, but everytime error "0X4".
Click to expand...
Click to collapse
@knopper84
That's exactly my problem , except I have the non-3G model (TF101). I'm currently downloading munsterrr's solution:
Download NvFlash revolver:
Just run flash.bat
Click to expand...
Click to collapse
Hope it will work . You should try it too.
[EDIT: Just tried munsterrr's solution. It didn't work at all. I guess I'll just wait for you guys to find a solution ]
Regards,
HorClok.
hmm i think i have tried it yesterday. Its this file ( http://www.multiupload.com/PFMWB39SK4 ) or? it gave me the same error (0X4)
For me it looks like exactly the same nvflash + bat like usual.
Or maybe is there something different there?
Which SBK you have? I think SBKv1 or?
IDK what SBK is...
I thought there was something different there.
i still tried the SBKcheck util on Linux-Live CD. It worked with "sudo", but i get SBKv1.
I think that is only because of the tool, because i have an 3G Model or?
knopper84 said:
i still tried the SBKcheck util on Linux-Live CD. It worked with "sudo", but i get SBKv1.
I think that is only because of the tool, because i have an 3G Model or?
Click to expand...
Click to collapse
Couldn't tell you, I don't use Linux.
So the Mac Version of the sbkcheck util works better?
Horclok said:
Couldn't tell you, I don't use Linux.
Click to expand...
Click to collapse
You have a B80 according to your other thread. This mean nvflash won't work.
knopper84 said:
i still tried the SBKcheck util on Linux-Live CD. It worked with "sudo", but i get SBKv1.
I think that is only because of the tool, because i have an 3G Model or?
Click to expand...
Click to collapse
If I remember correctly, 3G models have the SBKv3 but it reads as SBKv1.
Sent from my Transformer TF101 using XDA App
Hi, I know there are many threads with this particular problem, I did my research and I find this kinda strange (Iam also desperate...)
Long story:
Ive been swapping between official ROM and customs like a madman and Ive always rooted using this method (downgrade, then vipermod), but this time I accidentaly tried to enter recovery at first boot and since then Iam stucked at "EEE Pad" logo with half full progress bar.
tl;dr summary:
no adb
C10 transformer, sbkv2
no recovery
on boot w/ volume down it says 8.6.6 - the one Ive downgraded to; It also says "checking for ota recovery"
sucessful APX mode connect, universal drivers
When using standard nvflash ROM the process is terminated with "write error" message and disconnects the transformer - sbk2 problem, so Ive tried EasyFlasher which utilizes Wheelie for B70+ devices and the exact same thing happens (well, console and GUI says that everything is OK, but when the nvflash is getting ready the device gets disconnected too). There are many people saying in the thread that Wheelie helped them with basically the same problem...
Now Iam downloading linux to try Wheelie manually.
Any ideas how to fix this or I can pretty much toss my transformer out of the window?
Thanks for replies.
nevermind, Iam an idiot - did not realised that I actually have TF101G so sbkv3 and no nvflash for me
so, do you know if there is any "nvlash-for-sbkv3" project in progress?
Dear transformers,
My Transformer TF300T is a brick !!
I've got TF300T, with stock JB 4.1.1.
I'm not sure if it permanent, please help !!
I've unlocked my device via the official Asus unlock device tool.
It went well.
After few days, I've downloaded few programs from the "Google Play".
One of the programs, allowed to automatically enter recovery after reboot.
I opened the program (of course I don't remember it name), click on "enter recovery after reboot", and then the problem started !
Please see attached screenshot.
The device is stuck on the Asus logo, without any progress.
When I'm trying to enter the recovery menu, with "Power + Volume Down", the device turning of for 3 seconds, and getting back to the exact same position.
I cannot choose "RCK", no Android, no USB option, nothing !!
What you see in the screenshot, is the permanent condition...
When the Transformer worked, my computer recognize it, but now when it stuck on the Asus logo, it seems that the computer even doesn't see the device !! (although the driver is installed...)
How bad is it ??
It is a hard brick ??
Can I do anything without RMA it to Asus ??
I'm pretty sure that Asus won't support the device, because I've unlocked it
Please help !!
If XDA couldn't help me, I'm really lost... :/
Thanks a lot !
Transformist.
Are u sure to use the right tips to enter< rck>< fastboot>
Vol down and power
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Absolutely, more than that, it worked in the past...
I can only get the APX mode...
What should I do from there ??
How can I recover the brick from APX ?
Thanks,
Transformist.
okrasitna said:
Are u sure to use the right tips to enter< rck>< fastboot>
Vol down and power
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
so you have NVFlash that you can enter APX Mode?
then you could just restore a backup like here - but I'm really confused an APP should have broken your rck/fastboot menu
-angel* said:
so you have NVFlash that you can enter APX Mode?
then you could just restore a backup like here - but I'm really confused an APP should have broken your rck/fastboot menu
Click to expand...
Click to collapse
Thanks for your answer !!
It seems like the only thing that respond, is NVFlash...
But I still don't know what exactly to do with it...
The link you've sent me is for TF700...
This is the output of it (screenshot attached).
I absolutely agree with you that apps from the Goggle Play shouldn't prevent me to enter RCK / fastboot, but the RCK / fastboot worked until I've installed and used it... that all I know about why it's happened.
Is there a step-by-step solution for how to work with NVFlash (or wheelie) with TF300T ??
Thanks again !!
Transformist1.
transformist1 said:
Thanks for your answer !!
It seems like the only thing that respond, is NVFlash...
But I still don't know what exactly to do with it...
The link you've sent me is for TF700...
This is the output of it (screenshot attached).
I absolutely agree with you that apps from the Goggle Play shouldn't prevent me to enter RCK / fastboot, but the RCK / fastboot worked until I've installed and used it... that all I know about why it's happened.
Is there a step-by-step solution for how to work with NVFlash (or wheelie) with TF300T ??
Thanks again !!
Transformist1.
Click to expand...
Click to collapse
I've made a small progess (??)
I got an error message from our friend "wheelie"
(Of course from APX mode...)
Does somebody knows what it should means ??
Thanks,
Transformist.
Unless you already generated your device-specific NVFlash files while still on ICS, you will not be able to use NVFlash/Wheelie at this point. Wheelie needs those files to run and they will only work on the device they were generated on. The NVFlash files cannot be generated after upgrading to JB as of now.
Does your computer recognize it as an ADB device?
jimpmc said:
Unless you already generated your device-specific NVFlash files while still on ICS, you will not be able to use NVFlash/Wheelie at this point. Wheelie needs those files to run and they will only work on the device they were generated on. The NVFlash files cannot be generated after upgrading to JB as of now.
Does your computer recognize it as an ADB device?
Click to expand...
Click to collapse
Thanks for your answer !!
Unfortunately I cannot get to a situation that my device is recognize as ADB in my computer (that is because I cannot get into RCK / fastboot mode)...
As far as I succeeded, I can only get to APX...
BTW, I've tryied to use a lot of times with the "hard reset" button, with no success...
So... if I cannot use NVFlash/Wheelie, and I don't have any backup for my device, what can I do now ??
You want to tell me that I can throw my device, if I don't have a backup and only can get to APX ??
Thanks again,
Transformist1.
transformist1 said:
Thanks for your answer !!
Unfortunately I cannot get to a situation that my device is recognize as ADB in my computer (that is because I cannot get into RCK / fastboot mode)...
As far as I succeeded, I can only get to APX...
BTW, I've tryied to use a lot of times with the "hard reset" button, with no success...
So... if I cannot use NVFlash/Wheelie, and I don't have any backup for my device, what can I do now ??
You want to tell me that I can throw my device, if I don't have a backup and only can get to APX ??
Thanks again,
Transformist1.
Click to expand...
Click to collapse
Dear Transformers,
I hope it's allowed to share external links (and if not - I'm really sorry...):
I saw a guide to work with a program called "easyflasher", to unbrick if you have only APX mode...
http://new-ones.blogspot.co.il/2012/11/asus-transformer-tf101-only-in-apx-mode.html
Does anyone knows if there is a similar solution to TF300T ??
Thanks,
Transformist1.
transformist1 said:
Thanks for your answer !!
Unfortunately I cannot get to a situation that my device is recognize as ADB in my computer (that is because I cannot get into RCK / fastboot mode)...
As far as I succeeded, I can only get to APX...
BTW, I've tryied to use a lot of times with the "hard reset" button, with no success...
So... if I cannot use NVFlash/Wheelie, and I don't have any backup for my device, what can I do now ??
You want to tell me that I can throw my device, if I don't have a backup and only can get to APX ??
Thanks again,
Transformist1.
Click to expand...
Click to collapse
hm so if you don't have the ICS backup'ed device-specific files NVFlash can't help you - only thing I found was this with unblob'd system updates - what would make sense would be if you could do the same with unblob'd TF300 blob's - other thing which I would recommend to try first is THIS as it sounds like the same problem and ppl seem to agree (although OP didn't answer anymore) - hope I can help you a bit although I'm not familiar with NVFlash
-angel* said:
hm so if you don't have the ICS backup'ed device-specific files NVFlash can't help you - only thing I found was this with unblob'd system updates - what would make sense would be if you could do the same with unblob'd TF300 blob's - other thing which I would recommend to try first is THIS as it sounds like the same problem and ppl seem to agree (although OP didn't answer anymore) - hope I can help you a bit although I'm not familiar with NVFlash
Click to expand...
Click to collapse
Hi everyone,
After 4 long weeks I officially announcing my TF300T is dead...
After hundreds of posts, I understand that with only APX mode (no RCK, no fastboot0), there is nothing that can be done.
Thanks for all of you for your support, I'll now contact ASUS for RMA.
Thanks again,
Transformist1.
transformist1 said:
Hi everyone,
After 4 long weeks I officially announcing my TF300T is dead...
After hundreds of posts, I understand that with only APX mode (no RCK, no fastboot0), there is nothing that can be done.
Thanks for all of you for your support, I'll now contact ASUS for RMA.
Thanks again,
Transformist1.
Click to expand...
Click to collapse
hello, what said asus and how much cost asus Reinstalling
RMA
Repair of bricked ASUS TF300T in Czech Republic - 500,- KC ... cca 20 Euro ... :laugh:
Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
from the loop,If you hold the power button for 10s when reboot and immediatly press the volume down button, what you have asus loop or the screen with the 3 icons (RCK ecc) ?
Claudisimo said:
Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
Click to expand...
Click to collapse
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Sadly, the tablet came with Android 4.1.x :S
atoma1972 said:
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
Click to expand...
Click to collapse
Use of the bootloader information may allow access to recovery, adb, or fastboot. Access to any of the three may allow the ability to recover your tablet.
None of the ways worked for me.... can't access that menu...
Claudisimo said:
None of the ways worked for me.... can't access that menu...
Click to expand...
Click to collapse
If you still have no adb, fastboot, or recovery I don't know how to help.
Same situation
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Mynzer said:
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Click to expand...
Click to collapse
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
It Work
tobdaryl said:
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
Click to expand...
Click to collapse
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Great! I'm glad I could help.
help...
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Fullpoweradonf said:
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Click to expand...
Click to collapse
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Would be nice if you could use someone else's file to fix a brick. Has anyone tried it.
Mynzer said:
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Click to expand...
Click to collapse
Could You explain step by step which driver and how do you get up Yours TF300T?
I have the same problem, only recovery starts (TWRP2.5.0.0)
possible brick?...
After downgrade the console from the v. 4.2 to 4.1, following tutorials in this forum, because it would not let me install a Custom Rom (yes the recovery, not the root) I can think of to make a choice Wipe from the Stock 4.1 Recovery and restart WW I stand still Asus logo, white, and trying to restart pushing Recovery again, I go and I follow the fixed logo. I do not recognize the device SDK and have seen many posts and I can not find the solution ... buf! Someone has been the same? ... The strange thing is that lights ...
In case nothing else works (another fix) worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, don't forget to hit thanks button if it works =)
i have an odd question
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
racerocm said:
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
Click to expand...
Click to collapse
If you cannot access to fastboot, IMHO there's nothing you can do. I am in your same boat: no adb and fastboot access, my PC recognize the tablet only in APX mode but with NVflash I cannot do anything because I not have a backup.
Bye
EDIT: I am in this situation after a wrong recovery flash. I flashed a new recovery but I could not load it and I made the (big) mistake to try a wipe from the recovery menu. My Tf300t is now stuck at asus logo and I cannot access to the bootloader anymore. I do not know what to do, is the tablet definitely bricked or there's something I can try before going to ASUS service?
Thanks in advance.
Bye
Hi there,
a friend of mine, gave me this tablet because was bricked. Now i have tried the famous easyflasher with his "flash default stock" ability.
I have already installed the naked driver on my pc, and the tablet in apx mode is correctly recognized by windows.
Via easyflasher i have already started the flashing of the recovery "RogueXM Touch v1.5.0-R1" and now i'm going to flash the stock rom.
All goes pretty well, but at this time the process is stucked on the screen:
"""""
Nvflash started
[resume mode]
"""""
The tablet is still recognized by windows (i can find them on hardware connected).
So the question is: it's normal that the Nvflash take long time, and don't give me any output on his work? Nor if it's going to do something?
Let me know.
Thank you...
costal said:
Hi there,
a friend of mine, gave me this tablet because was bricked. Now i have tried the famous easyflasher with his "flash default stock" ability.
I have already installed the naked driver on my pc, and the tablet in apx mode is correctly recognized by windows.
Via easyflasher i have already started the flashing of the recovery "RogueXM Touch v1.5.0-R1" and now i'm going to flash the stock rom.
All goes pretty well, but at this time the process is stucked on the screen:
"""""
Nvflash started
[resume mode]
"""""
The tablet is still recognized by windows (i can find them on hardware connected).
So the question is: it's normal that the Nvflash take long time, and don't give me any output on his work? Nor if it's going to do something?
Let me know.
Thank you...
Click to expand...
Click to collapse
sorry i have found that i have wrote this post on the wrong place. You can remove him. Thank you and sorry for the mistake.