Hi, I Have installed in my Olipad clockworkmod v08.
Now, when i start in recovery mode, appear on display:
Recovery key detected
Booting recovery kernel image.
Can anybody help me?
Please.
Not to be rude but why would you install something designed for the GTab on your Olipad?
Curiosity and wanting to learn.
For Olipad ther'isnt custom rom.
Judging by the screen shots of the thing, I can see where you would think it might work. It's almost a carbon copy of the GTab, and it looks like it has TnT loaded as well. Unfortunatly, this is well beyond my scope.
Hi, I also have an olipad and I already went down a long road with CWMod and other moddings.
I can tell you that you are risking the booting capabilities of your device as there is something peculiar with the partitions and the boot.
I'm currently with a working pad, but I have to do a "tethered bot" because power button always brings up "apx mode" that is a low level mode to reprogram the device.
IF your device still boots with power button, I could try to give you some suggestion and you could help me "undo" a few mistakes.
Regards
SimonePDA
Not that this is going to help you right now, but I would avoid GTAB mods until a dev / modder with an Olipad can verify that these are, in fact, working. And maybe has a nvflash image of an Olipad device to give you a backout.
I've gotten a few PM's about this device too, and I've mentioned the same. I think it's similar to a zPad T2, at least from the little I know of it.
Hi, in this moment I have a tablet that boot but not work the recovery consolle.
Olivetti has relesed this file:
http://forum.xda-developers.com/showpost.php?p=12404697&postcount=1
Hi't possible use this for restore all stock rom?
tatoone said:
Hi, in this moment I have a tablet that boot but not work the recovery consolle.
Olivetti has relesed this file:
http://forum.xda-developers.com/showpost.php?p=12404697&postcount=1
Hi't possible use this for restore all stock rom?
Click to expand...
Click to collapse
Hi,
What's missing from that list of files is the partition list, and possibly the .bct.
The former would tell you the number and size of the partitions, and if you don't have that you wouldn't know which of those .img files goes where.
The latter is a kind of mystery file, but is apparently critical.
Jim
tatoone said:
Hi, in this moment I have a tablet that boot but not work the recovery consolle.
Olivetti has relesed this file:
http://forum.xda-developers.com/showpost.php?p=12404697&postcount=1
Hi't possible use this for restore all stock rom?
Click to expand...
Click to collapse
yes try to rename the files update.zip and place in the root of the internal memory
then try reboot holding +
Also make sure you remove any sdhc card, when trying this, especially if you already have a recovery on it...
Related
Hi,
I've been doing reading, trying to understand options for recovery and backup.
Are there two different recovery mechanisms/modes: APX and non-APX?
http://forum.xda-developers.com/showthread.php?t=827384#9062668
http://wiki.tegratab.com/index.php/ROMs
and one of these you hold VOL+ vs. VOL-?
And with one of these you use nvflash?
Also, how to create the files needed for these?
Thanks,
Jim
jimcpl said:
Hi,
I've been doing reading, trying to understand options for recovery and backup.
Are there two different recovery mechanisms/modes: APX and non-APX?
http://forum.xda-developers.com/showthread.php?t=827384#9062668
http://wiki.tegratab.com/index.php/ROMs
and one of these you hold VOL+ vs. VOL-?
And with one of these you use nvflash?
Also, how to create the files needed for these?
Thanks,
Jim
Click to expand...
Click to collapse
APX mode is the failsafe mechanism. If all else goes wrong, you can put your G Tablet in APX mode and use the nvflash tool to flash a new image to your tablet. You hold down VOL- when booting to get into APX mode.
Clockwork Mod Recovery is a much simpler tool to use. Once installed, you just press and hold VOL+ while booting, and you get a nice, easy text menu you can scroll through, and you can flash new ROMs from your internal SD card storage (or an external SD card too). You can also backup and restore your whole system as an image stored into the internal SD card, which is absolutely critical if you are trying new ROMs out, so you can restore in case something goes wrong. You can also fix partition issues that sometimes crop up, and clear cache and the Dalvik cache using Clockwork Mod, which can fix many issues when installing new ROMs.
To install Clockwork Mod, see the HOWTO thread here: http://forum.xda-developers.com/showthread.php?t=865245
Hi,
What kind of got me started on this was post #53 on this thread:
http://forum.xda-developers.com/showthread.php?t=844088&page=6
Now, I just got my Gtab this weekend, and I haven't backed it up completely yet, so I was figuring out how to do it. Everybody seems to recommend CWM, but then I saw that thread/post, and went "oh, oh. If I do that, then there'd be no way to get completely back to stock and get OTA updates (because CWM replaces the "stock recovery").
I did see the reply to that, but haven't found the reference mentioned in the reply.
The other thing is that I kept seeing references to the Gtab's "stock recovery", which seemed to be different from the CWM and APX recovery methods, and which I really haven't been able to find an explanation of.
Also, the ways to initiate the recoveries seemed to be different:
Power+VOL-
Power+VOL+
Power+VOL+ AND VOL-, then VOL+ only
Thus, my (still) confusion ...
Jim
jimcpl said:
Hi,
What kind of got me started on this was post #53 on this thread:
http://forum.xda-developers.com/showthread.php?t=844088&page=6
Now, I just got my Gtab this weekend, and I haven't backed it up completely yet, so I was figuring out how to do it. Everybody seems to recommend CWM, but then I saw that thread/post, and went "oh, oh. If I do that, then there'd be no way to get completely back to stock and get OTA updates (because CWM replaces the "stock recovery").
I did see the reply to that, but haven't found the reference mentioned in the reply.
The other thing is that I kept seeing references to the Gtab's "stock recovery", which seemed to be different from the CWM and APX recovery methods, and which I really haven't been able to find an explanation of.
Also, the ways to initiate the recoveries seemed to be different:
Power+VOL-
Power+VOL+
Power+VOL+ AND VOL-, then VOL+ only
Thus, my (still) confusion ...
Jim
Click to expand...
Click to collapse
You definitely can go back to full stock even if you've installed Clockwork Mod, I know a fair number of people have done it. See this thread for one method: http://forum.xda-developers.com/showthread.php?t=861950
However, the *only* reason you'd want to do that is if you are planning on returning the tablet to the store, or if you are developing ROMs like Roebeet. There is no other good reason.
The stock recovery image is extremely minimal. It does exactly one thing, as far as I can tell - when you boot up holding down VOL+, it loads update.zip from the SDCard directory and flashes it. But to the best of my knowledge, there is no recovery mode that will make backups, restore backups, and let you pick ROMs to flash. Thus "stock recovery" just refers to the stock, out-of-the-box image on the recovery partition that lets you flash an update.zip file, rather than to any genuine recovery functionality.
As far as everything we've seen tells us, the stock TNT software will always be worse than the custom ROMs you can download here, and there's no functional reason you'd ever want the stock recovery + stock TNT over a rooted, fixed TNT build like TNT Lite. Or something better like Vegan ROM.
Regarding APX mode, that's not a recovery image that you can boot into like Clockwork Mod. It's a special low-level firmware programming mode in the device that you access by pressing VOL- at boot.
The third thing you mentioned, pressing Power+VOL+ AND VOL-, then VOL+ only, I've never heard of. That sounds like somebody might have been mistaken about something to me. Or it's some really cool function I've just never heard of. To the best of my knowledge, booting into recovery mode is always accomplished by VOL+ while powering on, and booting into APX mode is always accomplished by VOL- while powering on, and that's all there is for special modes.
Hope this helps!
rcgabriel,
I saw a number of references to VOL+/VOL- then VOL+, e.g.:
http://forum.xda-developers.com/showthread.php?t=824804&highlight=flash&page=99
post #990. That calls it "APX mode":
"The first step would be to get into APX recovery mode:", which is what has been confusing me.
Is it just VOL-, or VOL+/VOL- then VOL+?
Jim
Power plus volume up = recovery mode
Power plus volume down = APX mode
APX mode is where you would use a tool like nvflash to backup your device and flash it, but you have to be very careful with that tool. Make one mistake and your partition structure is completely borked. It's fixable, but you have to know what you're doing.
Is there a program that will save all my apps and settings so I can update to a new rom and then load everything back on the new rom?
roebeet said:
Power plus volume up = recovery mode
Power plus volume down = APX mode
APX mode is where you would use a tool like nvflash to backup your device and flash it, but you have to be very careful with that tool. Make one mistake and your partition structure is completely borked. It's fixable, but you have to know what you're doing.
Click to expand...
Click to collapse
roebeet,
My understanding is that when using CWM, you do the power+volume up to get to CWM. Correct?
So, when CWM is installed, it replaces the "stock" "recovery mode". Correct?
Finally, when CWM is installed, is the APX mode (power+volume down) still available? And that's the "ultimate" recover when things go really bad?
Thanks,
Jim
Yes, yes, yes, and yes.
delete post wrong thread
You also need titanium backup to complete your backup arsenal
It will allow you to restore all your appear and their setting between rom version if needed
Sent from my GTablet-TnT-Lite using Tapatalk
Moved to general.
I have been reading around for a while now, and noticed a lot of ppl soft-brick there device and are asking devs for help. I have noticed a lot of issues revolve around people trying to hop form on ROM to another.
A very easy way to recover from any sort of brick(or issue) is to use nvFlash. Its is very easy to setup and use and I highly recommend that everyone should setup nvFlash. You can find the guide on how to set it up from http://forum.xda-developers.com/showthread.php?t=861950
I think after the update last night a lot of people will brick there devices trying to mod it, and nvFlash will help you recover. I think we can really help out the dev if we all learn how to use nvFlash, because then they wont have to ans to alot of the support issues that keep coming up, and it will free up some of there time which they can use to create newer roms that will work with the new update.
If for some reason you follow that guide and are not scussefull in setting up nvFlash, then feel free to leave me a pm and i'll help you set it up.
I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc
steve1040 said:
I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc
Click to expand...
Click to collapse
No its not a replacement for cwm. NVFlash will help you recover if you every brick your device and need to go back to stock image.
Couple of scenarios where it will be helpful is if you update to the new stock update from VS and decided you want to go back to one of the custom roms like Vegan GB RC1, then you will need nvFlash to go back to stock, otherwise you will brick your device.
Also I have noticed that I have to use nvFlash if I want to go from GB rom to FORYO rom.
Cannot get NV Flash to finish?!?
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
nvflash unsuccessful or wrong version
sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
Sounds like the nvflash wasn't successful. The message you are getting when you boot to recovery...Power + vol(+) indicates that CWM is installed. If you nvflashed a stock version, cwm would not be there (unless you nvflashed a stock version with cwm preinstalled). Are you sure you flashed with the correct bootloader version. You should have used the 1.1 b/l version. Here is a link to b/l 1.1 version 3588 with cwm preinstalled http://www.mediafire.com/file/picrzt9pdkuqbj0/gtab.nvflash.1.1.branch.20110422%20with%20cwmv8.zip. Nvflash this & see what happens. By the way. when doing the nvflash, the cmd shell output should look something similar to the attached file...won't be exact since this was for a bl1.2 4349 version I nvflashed yesterday.
Al
sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
My website linked in signature. You're a code red.
Hello, thanks for the response! I am downloading now and will let you know shortly...
Mike
goodintentions said:
My website linked in signature. You're a code red.
Click to expand...
Click to collapse
What is a code red?
Code Red is the condition of your G Tab. If you follow the link in the signature of Goodintentions post (Viewsonic G-Tablet for Dummies) you will find complete and simple instructions on how to recover your G Tablet. You can also find links to the files you will need. It's a great site for anyone having problems with their tablets. It's where I got all my information when I first started.
some notes
rooted using Root RK29 Tab Toolkit 1.3.
reset and vol + = flash mode rock usb.
RKAndroidToolv1.37 and RKBatchToolv1.7 work for flashing.
used rock usb driver included in either of the flash
tools. when flashing several things needed done to
enable flashing and or adb. do not enable usb storage
on the device. on windows pc used the safely remove
mass storage tool. only on the removable drives that
showed in my computer after plugging in the tablet.
in RKAndroidTool or RKBatchTool use the "switch" button
to put the unit into flash mode. I used RKAndroidTool
to flash the cwm. I tried several cwms, PER5274B_CWM.zip
was only one to boot to recovery for me
(tried many including ones from developerof cwm, just
happened to find one to boot after trying
over and over). so far. succesfully made full backups of
the unit to sd card. obviously mount the ext sd in cwm
first before backing up to sd. succesfully flashed
gapps-jb-20121011-signed.zip using PER5274B_CWM.
the stock recovery tool rejected all gapps. note gapps
sometimes closes for no apperent reason with no error.
all other gapps versions i tried crash soon as i
opened them.
cwm file working so far PER5274B_CWM.zip. have only figured
out how to boot to recovery using reboot apk.
key combo is unknown to me so far. actively trying other cwms.
Other cwm's have booted to a white screen for me.
a word to the wise, make full flash backup soon as you
get cwm on. its the only way to turn back to stock as
far as i know. I cannot find a factory rom for this
unit anywhere.
downloading cm 10.1 for rk29xxboard now, will report
results!
Cheers hope this helps out someone.
well cm10 didnt work out so well. the unit is now resting with no response. I can however still flash it with rkandroidtool. the issue I am facing now is I do not have a full dump image for this unit. I am looking for one that will at least allow me to get it to boot properly to cwm lol. I can see it with rkbatchtool as well. what I would need there is the proper parameter file. pretty sure thats all I need. I did happen to make a backup with cwm but if I cant get the tablet into cwm (currently a no go) thats not going to help me. figures I have since found out how to generate a parameter file.
good news is its not dead, just not working.
I have gotten my moneys worth out of it, not only in using this tablet but also in hacking the thing passing time.
will report further updates.
Cheers!
Well its running again, after many firmwares etc. I have the stock firmware running and two others I have modded removing system Apks I didn't want and adding a few as well.
Have several cwm backups as well, a few I plan to post links to. Googleplay works to, root, cwm and busybox also.
Still trying to get hardware keys working to launch cwm at boot by editing the parameter file. It will run when I edit the file with notepad++ and flash it but then I end up in a cwm boot loop forcing me to reflash the orig parameter file to get out of it. Cold boot will get me out if I completely drain the battery otherwise nothing short of flashing it will get me out of cwm. Using notepad++ and inserting "COMBINATION_KEY: 0,6,A,7,0" right after the kernel IMG line gets the power + volume key to start cwm at boot. Then I can't get back out lol.
stinkster said:
Well its running again, after many firmwares etc. I have the stock firmware running and two others I have modded removing system Apks I didn't want and adding a few as well.
Have several cwm backups as well, a few I plan to post links to. Googleplay works to, root, cwm and busybox also.
Still trying to get hardware keys working to launch cwm at boot by editing the parameter file. It will run when I edit the file with notepad++ and flash it but then I end up in a cwm boot loop forcing me to reflash the orig parameter file to get out of it. Cold boot will get me out if I completely drain the battery otherwise nothing short of flashing it will get me out of cwm. Using notepad++ and inserting "COMBINATION_KEY: 0,6,A,7,0" right after the kernel IMG line gets the power + volume key to start cwm at boot. Then I can't get back out lol.
Click to expand...
Click to collapse
Stinkster,
Have you made any other progress? Got my kids couple LT7035-F tablets.
Thanks
To the both of you... LT7035-J
curtisint has firmware for model lt7035-j; however, when using rkbatchtool it fails at 97%. My tab is only able to connect to the pc as of now. I can see it with batchtool; however, have not found a firmware.img file to flash to it that completes and works. Very interested in the parameters file you speak of in your second post. Don't know what you know now but I was able to get it root with a tool I found on the net. I think I have it somewhere. Well anyway I was trying to reflash stock firmware because I had no sound just a popping noise/key tone which was silent only when mute. If anyone could help out with a firmware.img that will work for me that would be great.
stink you sound like you know what you are talking about, do u java develop or something?
Hello Friends and first I have to say sorry for my english.
OK, I try to tell whats happend.
2 Days ago I would like to flash a new rom on tf700t. For that it was neccessary to change from TeamWinRecovery to ClockworkModRecovery.
To do this at the easiest way, I have done this Job with the Rom Manager App.
That was my first error.
After Installing I reboot my tf700 and was surprised, TeamWin was still there...
Ok I have created a full backup, after that I performed a full wipe.
After that I have rebootet again, but know TeamWin was not there anymore, Clockworkmod was also not not there.
Booting with Power + Vol Down Fastboot mode is starting (I think so) 3 Symbols in the Middle.
Starting RCK Mode, but nothing happens, only a text left above, Recovey Rom is loading (or somthing like that)
Booting with Power + Vol Up APX Mode is running. Black Screen and Pong on my PC. Nvidia Driver installed.
OK later, verry late at night I have by mistake Used The Wipe Button, I dont wont to do that but I have pressed the wrong button.
Now the follow things happend by Booting.
Only Presss Power:
Tab is starting to Asus Logo in the middle, in the left corner abowe The Device Is Unlockes. Nothing else happens.
Press and hold Power and Vol down: The same like above No Pong on PC, the same screen like starting the tab normaly.
Press and hold Power and Vol up: APX Mode ist starting.
I have many Full Backups TWRP.
I have the Stock Asus Rum on SD Card.
I have the nvflash Package for my tf700t.
I have the flatlinetf700t.img
And many other files.
Oh I dont have createt bevor any blop files.
What I will ask you is: Is it possible to repair the Tab by using nvflash?
I think the bootloader is defect...
What is needed for that
wackaman said:
What I will ask you is: Is it possible to repair the Tab by using nvflash?
Click to expand...
Click to collapse
Not without the blobs.
"Wipe data" + broken recovery + no blobs for nvflash = hard brick. There is no known fix.
Is it possible tu use blob files from an other tf700t 64gb??
I have here a original asus tf700 Stock rom, wich I have full extracted twice. So now I have the rom as a blob file wich was in the zip. 800 MB.
What can I do with that file?
Here I found something to use the android toolkit but it cant work, there is no fastboot mode anymore. If I try to use fastboot, power and Vol down, nothing happens, there is no device installed at pc, only in adb mode, but android toolkit could not handle adb mode.
Read
Last hope is to use some other blob files..
Whats about RMA? Prices for that job?
Thanks.
wackaman said:
Is it possible tu use blob files from an other tf700t 64gb??
I have here a original asus tf700 Stock rom, wich I have full extracted twice. So now I have the rom as a blob file wich was in the zip. 800 MB.
What can I do with that file?
Here I found something to use the android toolkit but it cant work, there is no fastboot mode anymore. If I try to use fastboot, power and Vol down, nothing happens, there is no device installed at pc, only in adb mode, but android toolkit could not handle adb mode.
Read
Last hope is to use some other blob files..
Whats about RMA? Prices for that job?
Thanks.
Click to expand...
Click to collapse
You need the blob files from your device. They store keys particular to yours. When you started the nvflash process it sounds like you never completed it. That means you have no means of recovering.
List the files you have.
RMA will set you back between 200 to 300 dollars but ask Asus for a quote. You might be better off selling it for parts and getting something newer.
What I have is all from here, means the nvflash files for my tf700t.
I also have the original asus stock rom for my device and some other roms, twrp backups and so on...
The most is not usable while there is no fastboot / adb mode possible.
I have never read something about some blob files needed for other devices...
I dont understand what for blob files I need to bring recovery back. Thats all I want to have.
I tried to flash via nvflash the stock asus extracted till to a blob file. I remember nvflash wrote than somewhat like, no blob files found...
Maybe its really time to say goodby to this ....
wackaman said:
What I have is all from here, means the nvflash files for my tf700t.
I also have the original asus stock rom for my device and some other roms, twrp backups and so on...
The most is not usable while there is no fastboot / adb mode possible.
I have never read something about some blob files needed for other devices...
I dont understand what for blob files I need to bring recovery back. Thats all I want to have.
I tried to flash via nvflash the stock asus extracted till to a blob file. I remember nvflash wrote than somewhat like, no blob files found...
Maybe its really time to say goodby to this ....
Click to expand...
Click to collapse
If you followed the instructions on that page including the wheelie part to extract and save your blobs then your device is salvageable. The question is did you?
If yes you can use this guide to restore.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
If no, sell the device for parts as it is dead.
Thanks again.
I have asked Asus for Support and I post again after an answer from asus.
**** happens. That with the strongly recommed to do to make this device bricksave has to be placed on every first sites about this Thing.
Are there more devices who needs those files (means blobs)
wackaman said:
Thanks again.
I have asked Asus for Support and I post again after an answer from asus.
**** happens. That with the strongly recommed to do to make this device bricksave has to be placed on every first sites about this Thing.
Are there more devices who needs those files (means blobs)
Click to expand...
Click to collapse
Get a used motherboard on Ebay and replace it yourself. Sure to revive your darn tab for much less. What is it an Asus technician can do that you can't? It ain't rocket science after all. Go to this site and learn how to take it apart.
I dont know, what asus can do...
I have now looked many days for a mainboard for my device. Only 32GB Version are listet by ebay.
Maybe I have to wait...
wackaman said:
I dont know, what asus can do...
I have now looked many days for a mainboard for my device. Only 32GB Version are listet by ebay.
Maybe I have to wait...
Click to expand...
Click to collapse
Asus will do nothing other than charge you hundreds of dollars to replace the main board.
wackaman said:
I dont know, what asus can do...
I have now looked many days for a mainboard for my device. Only 32GB Version are listet by ebay.
Maybe I have to wait...
Click to expand...
Click to collapse
Since you are giving up and looking for a new mother board, you can PM and we could try a few different things to see if we could wake it up... If you have some spare time to waste then you could give it a shot, hahaha....
Hi all,
Today I tried to flash an older version of the stock rom (v1.2.1) and thought I didn't need to flash userdata.img. That was a big mistake..
Now the tablet stuck at a bootloop. After that I thought I could simply flash twrp over the bootloader to peform a /cache & /data wipe so that I can fix the bootloop.
And now we come to the other BIG problem. I can't access the bootloader. It directly boots up the tablet with the Nvidia logo. Is there any solution to fix the tablet?
I tried at the bootloop to enter via adb into the bootloader but my PC isn't recognize my device (probably no usb debugging).
There is no way to rescue it? No apx drivers out there?
Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
amartolos said:
Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
Click to expand...
Click to collapse
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
ThunderArts said:
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
Click to expand...
Click to collapse
I notice in your sig that you do in fact seem to have a fully working new replacement tablet. That got me thinking along the following:
1. new tablet is fully functional, old one is not
2. both tablets have the same hardware spec
3. pull firmware from new one, and somehow get it onto the old one
4. hopefully old tablet should work!
The biggest problem is step 3... I only know of nvflash that might be able to help here, but I've never used it myself so I'm completely useless here. Maybe someone more knowledgeable could help out here, but otherwise it seems like you might be out of options.
If you do want to take a stab at nvflash yourself, THIS PAGE has a nice writeup of what some commands do, BUT BEWARE! It's not for our device, so don't just copy-paste commands! As long as you're not writing things to the new tablet, it couldn't hurt to try stuff, right?
It wish someone could help me with NvFlash because I have no knowledge with it.
So it's possible to make a copy of the system of my working tablet and flash it on my old tablet with NvFlash?
I hope someone helpful with NvFlash experience could help me out.
Btw I need to have an un-blob'd stock rom version to get it back alive? Afaik is there no public version.
NVflash is only useful if you have backed up using it BEFORE you brick it.
sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
-deleted-
ThunderArts said:
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
Click to expand...
Click to collapse
No the blobs are specific to the device.
sbdags said:
No the blobs are specific to the device.
Click to expand...
Click to collapse
Okay. So it seems that there is no way to rescue it. Btw is there no accessible bootloader in OTA 1.2.1 because I flashed the boot.img without any error and I don't understand why I can't access it.
sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
Bogdacutu said:
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
Click to expand...
Click to collapse
Indeed - I was just talking about nvflash use in general. I haven't seen it used since tegra 3.