[Q] Malata Zpad bricked? - G Tablet Q&A, Help & Troubleshooting

I have a real Malata Zpad (from China) which I have been trying to get a new ROM installed (for english GUI). I tried both the Zpad rom and the GTab roms. In both cases nothing worked. I have been unable to boot the tablet and need to do an NVflash. The only one I can find is for the Gtab and the hardware is just different enough that I do not think it will work. Does anyone have a nvflash bootloader.bin for a Zpad?
Update: Tried the GTab NVflash. It didn't work. Found the original stock flash here: http://www.ez-pad.net/android-1340-1-1.html.

nvflash for malata
Newanzer said:
I have a real Malata Zpad (from China) which I have been trying to get a new ROM installed (for english GUI). I tried both the Zpad rom and the GTab roms. In both cases nothing worked. I have been unable to boot the tablet and need to do an NVflash. The only one I can find is for the Gtab and the hardware is just different enough that I do not think it will work. Does anyone have a nvflash bootloader.bin for a Zpad?
Update: Tried the GTab NVflash. It didn't work. Found the original stock flash here: http://www.ez-pad.net/android-1340-1-1.html.
Click to expand...
Click to collapse
can you post how you manged all this. I am a newbie to android and I have zpad that I want to take back to scratch. Tried CWM but with the gtab mod I used it just runs over CWM
Thanks

I also bricked my Zpad some time ago, and finally unbricked it.
Here is the thread where I told about my attempts:
http://forum.xda-developers.com/showthread.php?t=1039547
One of the main thing I learned at that time is that the odmdata flag is one of the keys. It is really linked to the boot image you use. In the thread above, I used --odmdata 0xbb0c0011 with the various parts extracted from nvflash_t2_mp_wifi_1202.rar.
Later on (and not announced on the thread above), I also succeeded to flash directly the gtablet files from thread http://forum.xda-developers.com/showthread.php?t=861950, but this time using --odmdata 0x800c0011.
You should also take care of which bootloader you send to nvflash (using the --bl command line flag). Some of them for example did load but stopped immediately without doing anything. Try first to use the bootloader.bin that comes in the rar or zip archive with all the other files (bct, img, cfg ...) and if this fails, try to use another bootloader, from another file (but in this case use a relative path, like -bl ../another-directory/bootloader.bin) instead of copying the bootloader.bin in your current directory. The reason for that is that the bootloader.bin is also copied in the tablet for normal boots, so the one that comes with the rar/zip is important and should not be overwritten b the temporary bootloader.bin you use only during the nvflash run.

Hi I managed to use the viewsonic gtab after installing ROM. You need to root first.
Its some time ago now so i do not remember what i did exactly
but after installing ROM (look at market) and rooting you start the tablet while simultaneously pressing the volume up. Make a backup and place the update files on the sd card. There are some real good posts here on xda where it is explained in detail. Just use th search feature good luck!
BTW: My malata has 3g too but I did not manage to get that working yet because i think it is not available in the gtab version...

Related

Help with everything. Installing a ROM on a TF201 for the first time ever.

Okay, I bought this Transformer Prime from my brother. I tried getting a custom recovery on it once, and I hard bricked it. I got a super lucky fix ($40), and it's back to being new again. Now, I really want Cyanogenmod on it, along with a good custom recovery (I'm partial to Clockword Mod, but open to suggestions). It currently has Android 4.1.1 on it, and I've looked up step by step instructions online on how to install CWM and CM9.1 and CM10 on it, but every description is way different than the various screens my Prime gives me. There is no Eee Pad screen, it just says Asus. When I hold down the Volume Down and Power, it gives me a screen with four different icons to choose from. This is where I died last time. Currently it has Root and the bootloader is unlocked, but that's as far as I've been willing to go. Anyone able to point me in the direction of more recent updates/directions so that I can be sure to get something that suits my tablet? And I'm pretty familiar with Android for phones, been rooting, hacking, what have you those for a few years now. Thanks!
Get your NVFlash blobs first, that will help prevent a brick again. Here is the thread in the development forum http://forum.xda-developers.com/showthread.php?t=2455920
jjubenv said:
Get your NVFlash blobs first, that will help prevent a brick again. Here is the thread in the development forum http://forum.xda-developers.com/showthread.php?t=2455920
Click to expand...
Click to collapse
I've seen a couple things on nvflash, and been to that tutorial page before. What I'm confused on and haven't seen a clear answer to is, how in the world do I download it? Is it something that can even be downloaded, or is it embedded into the bootloader and I just need to access it?
*Edit* Nevermind, found what my brain was missing all this time. This is why I don't like attempting stuff after getting home from work, I usually wait till a day off.
Anyone know a good tutorial for my other two questions?
Once I figured out the NVFlash thing, I read around about ROMS (It seems like you already have some familiarity with these). I picked a ROM that is really well supported on this site (HairyBean http://forum.xda-developers.com/showthread.php?t=2407248 ) and I read the whole devel thread. It's recently released and so the instructions are relevant and current. There is a good video link by wwjoshdew in the first post which showed me what I should expect and what a normal install should look like (the forum thread shows brief "Works for me, this is great!" posts and bunch of "I have this problem" or "that problem" posts which could be off putting). So I installed TWRP from HairyBean instead of CWM (I like the GUI touch stuff) and HairyBean after that and had great success. I don't have any affiliation with the Androwook team, or HairyBean, but I they have a stable ROM and it is very well supported (Thanks to flumpster and the team). Now I like my Prime even more.
How do you install TWRP from HairyBean, then install HairyBean? I'll work on NVFlash this weekend.
It's in the first install step in the first post of the HairyBean thread. Just watch the video in that first post and he shows you step by step. The HairyBean bootloader and TWRP are installed in the first step. The video (also in the first post of the HairyBean devel thread) shows you how to get into recovery, he goes into TWRP, which he had installed before. You will have a new recovery partition (CWM I believe) once you make your NVFlash blobs. You can use that to flash the HairyBean bootloader and TWRP at the same time (It's one ZIP file) from a MicroSD card. No need to unzip it, just put it on the root of the MicroSD card and select that to install. (I can't remember the exact steps to do this from the CWM install left over by the NVFlash process).
jjubenv said:
It's in the first install step in the first post of the HairyBean thread. Just watch the video in that first post and he shows you step by step. The HairyBean bootloader and TWRP are installed in the first step. The video (also in the first post of the HairyBean devel thread) shows you how to get into recovery, he goes into TWRP, which he had installed before. You will have a new recovery partition (CWM I believe) once you make your NVFlash blobs. You can use that to flash the HairyBean bootloader and TWRP at the same time (It's one ZIP file) from a MicroSD card. No need to unzip it, just put it on the root of the MicroSD card and select that to install. (I can't remember the exact steps to do this from the CWM install left over by the NVFlash process).
Click to expand...
Click to collapse
I got pretty far in the NVflash process, but when I try to direction that says to run "wheelie --blob blob.bin" while the tablet is in APX mode, I get "Error 3 receiving response from command". Google has been fruitless. Any ideas?
You may want to try asking for help in the flatline NVFlash thread in the Development forum, I didn't have any problems and I don't know the components well enough to help you you out. Sorry.
Yeah, I did that. There was one other guy on there having the same problem and I never saw a resolution posted. Here goes though.
Ugh, this always happens to me! I have a problem, I post about it on topics started by the developers that people had been posting on all day every day since it was started, and suddenly the posts dry up.

[Q] New flatline (nvflash) JB edition recovery guide anyone?

Hi all, noob here. I used the new flatline-nvflash guide (linked to from this site) to create backup blobs and files for my TF201 running JB. Worked marvelously...JOY!!! After doing so I thought I had a recoverable tf201 in case of accidental bricking. So I went ahead and flashed a custom rom (CMB). Didn't realise that during the backup process my bootloader was changed and the flashing failed resulting in a brick. A long story but I only have APX access now, no recovery. I've tried to find a guide to how to use my flatline-nvflash generated recovery blobs and files but haven't been able to find one. There is an old guide for the ICS based nvflash recovery but not the spanking new JB flatline-nvflash recovery.
Help with finding a guide or advice on "how to do it" in the form of correct code and sequence would be much appreciated. Would change my TF201 from an attractive but expensive paperweight back to a functional unit.
I am Zurvan said:
Hi all, noob here. I used the new flatline-nvflash guide (linked to from this site) to create backup blobs and files for my TF201 running JB. Worked marvelously...JOY!!! After doing so I thought I had a recoverable tf201 in case of accidental bricking. So I went ahead and flashed a custom rom (CMB). Didn't realise that during the backup process my bootloader was changed and the flashing failed resulting in a brick. A long story but I only have APX access now, no recovery. I've tried to find a guide to how to use my flatline-nvflash generated recovery blobs and files but haven't been able to find one. There is an old guide for the ICS based nvflash recovery but not the spanking new JB flatline-nvflash recovery.
Help with finding a guide or advice on "how to do it" in the form of correct code and sequence would be much appreciated. Would change my TF201 from an attractive but expensive paperweight back to a functional unit.
Click to expand...
Click to collapse
I suggest you to contact with flumpster. He is one who knows about rom&recovery more than most of us
TacoNikky said:
I suggest you to contact with flumpster. He is one who knows about rom&recovery more than most of us
Click to expand...
Click to collapse
It doesn't matter how old the instructions are for nvflash, once you have your backups the restore method is all the same.
Here are instructions for the tf700 but they will apply to you also. Just get the tf201 firmware instead of tf700 where it says. This only uses nvflash to restore the parts you need to get fast boot working to do the rest.
http://forum.xda-developers.com/showthread.php?t=2538028
Here is an older one for the prime that uses nvflash and unblobed files to do it all. Take your pick.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash

[Q] Acer A210 unroot

Hi there,
Having happily and successfully followed the root instructions for my Acer A210 (http://forum.xda-developers.com/showthread.php?t=1999615), turns out I have a hardware fault on the screen causing occasional random dead spots.
Anyway before I can send it back, I need to put it back to normal.
So, again following the instructions to unroot, and of course they don't work. Other users in the thread see this as well, and therefore the post from:
http://forum.xda-developers.com/showpost.php?p=47359544&postcount=104 (Page 11 of the original thread)
shows that different files must be used, however the links to both sites are protected.
Does anyone have these correct files? If so can the original thread be fixed in the first place?
I have actually found a good recovery.img but when I try to use it to flash the latest rom zip from Acer, it fails with:
check.partition.size=["__PROP_UNDEFINED__"]
installation aborted.
It also does this when trying from CWM.
I have also tried deleting the first line in the updater script as some posts suggest, but this makes no difference either.
Any ideas?
Cheers
Dave

[Q] Stock TF201 routes to KitKat question

Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
mistral_blue said:
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
Click to expand...
Click to collapse
Man your asking for alot
Shoot me a PM lets see if we can point you in the right direction.....
Thx Josh
mistral_blue said:
(I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Click to expand...
Click to collapse
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Thanks for the quick replies gents... Restorer, I'll read up on the methods you suggest (thanks for the detailed list with links, exactly what I was after) and then Josh I'll be in touch to check I've not missed anything before I start following the Yellow BRICK road:laugh:
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
tim2min said:
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
Click to expand...
Click to collapse
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer said:
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Click to expand...
Click to collapse
Sorry just one more question, since I have a TF201 and and want to use this ROM, it seems I am essentially turning my Prime into aTF300, which is ok, now right after unlocking the boot loader and then running TWRP (2.7 TF300) it is at this point I flash the hairybean update or do the creation & backing up for NVFlash first then the hairybean?...sorry for the elemental question...just want to be sure!
Tim
tim2min said:
now right after unlocking the boot loader and then running TWRP (2.7 TF300)
Click to expand...
Click to collapse
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Taking The Plunge!
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Taking The Plunge!
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Why rename the the .img file to a .blob file ?
Not really the best thing you could do .....
Just boot to fastboot and run the command
Code:
fastboot flash recovery flatline_tf201.img
The blue bar will show up and fill on the write part of the command ...
Once that is done do this command .....
Code:
fastboot reboot-bootloader
Let the tablet reboot into bootloader and VOL up on RCK
Now your golden ......
Make sure you understand what need to be done in flatline ...
Thx Josh
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Restorer said:
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Click to expand...
Click to collapse
Does no one use auto-complete any more ......
Thx Josh
lj50036 said:
Does no one use auto-complete any more ......
Thx Josh
Click to expand...
Click to collapse
Haha, yes. Why do command windows have to be so primitive .
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
lj50036 said:
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Click to expand...
Click to collapse
Thx Josh
Taking The Plunge!
lj50036 said:
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
Thx Josh
Click to expand...
Click to collapse
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
tim2min said:
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
Click to expand...
Click to collapse
Sounds like another windows driver issue .....
I really cant help much here as I dont use windows ...
But there is a short term solution at least to get you booted up ....
@ne0zone75's flashable zip twrp
Download this and move it into your folder that contains the fastboot.exe ... Then rename it to twrp.zip
Then boot into the recovery and run this command from CMD window
Code:
adb push twrp.zip /sdcard
Let that happen should not take long, find the zip file under install and flash it .....
YOU MUST DO A REBOOT AFTER THIS NOT JUST A REBOOT INTO BOOTLOADER ...
So lets run this command ....
Code:
adb reboot
Let it fully boot into a bootloop then with the buttons get back to the bootloader screen and enter RCK ...
then once you have done that continue on your way ....
Let me know this works for you ....
Thx Josh
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
Josh has answered you. But this is another fine example of why people here keep banging on about reading things carefully and then following instructions to the letter .
Taking the Plunge
Well, after some "trying" moments I got this ROM on the Prime!...must say extremely excited seems like my TF201 has more than just a "heartbeat" left in her, shoot she may be able to run hard a little longer!. I must admit some EXTREME anxiety occured and I really got scared when after flashing hairybean/bootloader my computer could not find/see my tablet AT ALL!!. This lost of connection was madddding especially when Windows would add the tablet in device manager and you would hear the computer chime every time I connected/disconnect the USB cable from the computer while the other end was in the tablet. I had to fuss around with Android APD Interface/Android APX drivers until my computer settled on one that actually worked after running c:\fastboot>fastboot devices 50x's and if finally saw my tablet I literally shedded a tear, this is definetely not for the faint of heart...lol Needless to say I hurried up and finished going down the instructions just for fear my computer might "inexplicably " loose connection again!....lol
Many thanks to Restorer for chiming in with my question also Josh (especially for the step by step instructions) also to the whole team that made this ROM!
Just a question though: If you wanted to change the color theme on boot up (which now shows in blue "CROMBi-KK") how would I go about that?
Tim

LG G Tablet Stuck In Bootloop. Need nvflash_gtablet_2010110500.zip File

nvflash_gtablet_2010110500.zip
I have been trying to get my Gtab up and running. It's caught in a loop and looking in the forums here I gather that one of the files that I need to flash it is nvflash_gtablet_2010110500.zip. The link that I found to a drop box location is dead. Google takes me to the same drop box.
I also read that nvflash_gtablet_2010110500.zip can be referred to as bekit version 1105. Is this correct? I've searched for that file also with no result.
Anyone know where I might be able to obtain this file? Any help would be appreciated.
Don
i'm also looking for these old nvflash files
does anyone have them stashed away somewhere?
Checkout here on the last page. There should be a OneDrive zip download that has the NVFLASH files for bootloader 1.1 and 1.2. It also comes with APX drivers (the android_tegra_froyo_20101105.msi file). Hopefully this is what you where looking for.

Categories

Resources