So I have a Prime that is stuck on the ASUS logo with a spinning circle. I want to try a few different things and can't seem to figure out fastboot for this device.
All the searched results say that I should see a USB icon when I hold Power+Down after I leave it be trying to get into RCK. However, I just see wipe data, and android. If I let it set, it cold boots.
At the top of the screen when holding Power+Down it also says
US-epad-9.4.2.15-20120221
If that helps.
Also, what do I name the ROM that I download to the MicroSD card to push in RCK? I know the TF300T is EP201_768_SDUPDATE but is it the same for the TF201?
kmad86 said:
So I have a Prime that is stuck on the ASUS logo with a spinning circle. I want to try a few different things and can't seem to figure out fastboot for this device.
All the searched results say that I should see a USB icon when I hold Power+Down after I leave it be trying to get into RCK. However, I just see wipe data, and android. If I let it set, it cold boots.
At the top of the screen when holding Power+Down it also says
US-epad-9.4.2.15-20120221
If that helps.
Also, what do I name the ROM that I download to the MicroSD card to push in RCK? I know the TF300T is EP201_768_SDUPDATE but is it the same for the TF201?
Click to expand...
Click to collapse
You are still on ICS and are in a unique position to do the nvflash process and make yourself brick proof before you do anything else.
Once you upgrade to jellybean you will no longer be able to do this.
Check out nvflash thread on Dev forum but if you are not going to do it most people on here would happily swap their fully updated custom primes with you to be able to get nvflash.
flumpster said:
You are still on ICS and are in a unique position to do the nvflash process and make yourself brick proof before you do anything else.
Once you upgrade to jellybean you will no longer be able to do this.
Check out nvflash thread on Dev forum but if you are not going to do it most people on here would happily swap their fully updated custom primes with you to be able to get nvflash.
Click to expand...
Click to collapse
Great, thanks! I will check it out.
Also, do you know on that file rename?
Oh, and I am trying to unlock it to get the fastboot option. Do you have any idea how to unlock if I can't boot into a rom with that ASUS unlock tool from their site?
Ok, so for those of you that have a problem and find this thread, I at least finally got it to take a rom thanks to the guidence of flumpster.
I went here and chose the same software I currently was on.
http://forum.xda-developers.com/showthread.php?t=1429873
and then put the once unzipped .zip on my MicroSD card and renamed it EP201_SDUPDATE (.zip but on win 7 that's default and some people end up with .zip.zip)
then I booted it with power and down held until I pushed up for RCK and it FINALLY took off.
I guess I was getting bad roms from all the other threads.
kmad86 said:
Ok, so for those of you that have a problem and find this thread, I at least finally got it to take a rom thanks to the guidence of flumpster.
I went here and chose the same software I currently was on.
http://forum.xda-developers.com/showthread.php?t=1429873
and then put the once unzipped .zip on my MicroSD card and renamed it EP201_SDUPDATE (.zip but on win 7 that's default and some people end up with .zip.zip)
then I booted it with power and down held until I pushed up for RCK and it FINALLY took off.
I guess I was getting bad roms from all the other threads.
Click to expand...
Click to collapse
Glad you got it all sorted mate :good:
flumpster said:
You are still on ICS and are in a unique position to do the nvflash process and make yourself brick proof before you do anything else.
Once you upgrade to jellybean you will no longer be able to do this.
Check out nvflash thread on Dev forum but if you are not going to do it most people on here would happily swap their fully updated custom primes with you to be able to get nvflash.
Click to expand...
Click to collapse
can you tell me what you mean by this. this is my first tab and there's a lot to read.
Sent from my Transformer Prime TF201 using xda premium
Related
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Gabewalters said:
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Click to expand...
Click to collapse
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
shreddintyres said:
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
Click to expand...
Click to collapse
I have only edited one /system/app file and it was to paste the Svoice app to see if it would work. I am pretty sure I deleted it though. Would this be why? And what do you mean by hitting the factory reset?
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
tkdsl said:
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
Click to expand...
Click to collapse
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
I checked the Sticky on the Dev Section and they don't cover this type of damage.
This means I have to send my prime to ASUS. dang it.
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Gabewalters said:
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
Click to expand...
Click to collapse
I tried restarting with the recovery kernel and I get an android logo laying down with red exclamation mark. not sure what that means how to fix that yet.
---------- Post added at 11:52 AM ---------- Previous post was at 11:44 AM ----------
MRCANNADY said:
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Click to expand...
Click to collapse
the only thing is, I did not change system files on my prime, I kept it stock. and I have received updates and updated them before. I just found out that the repair center for ASUS in Los Angeles does not service Primes.
The update may have bricked your prime. Although updates succeed with some devices they can fail with others. There is a long history of such issues across platforms.
Sent from my Transformer Prime TF201 using Tapatalk 2
try a hard reset.... insert a paperclip into the hole by the SD card to reset.
If not ping Gary Key or the other Rep, I forget the name and see if they can have an Asus tech offer some other solution. If not RMA it is..
just dont say its rooted
good luck!
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
sledgie said:
I just wanted to have a little post for those of you like me that may have tried updating after downloading the .28 OTA update, then the Prime freezing on the Asus Splash Screen and not rebooting...I found the solution after finally downloading the update this morning from Asus' TW site.
I only have the Prime as my computer and I have an Android phone. No PC for me - was going to try to use a friends last night to get into ADB but it just wasn't happening.
So for me - this is what I had to do.
If after your prime reboots you are still stuck on your asus splash screen, and nothing will get it to boot up - do this:
You must know your Prime's version of the update.
Goto ftp://ftp.asus.com.tw/pub/ASUS/EeePAD/TF201/ or check cky2000's thread right here
forum.xda-developers.com/showthread.php?t=1429873
Download the **COMPATIBLE** update of .28 (I tried .21 plenty of times - .21 would not update my Prime)
If on an Android phone (like I was) goto ES File Explorer and open the **UpdateLauncher.zip file
It should say something like **_epad-user.9.4.2.28.zip
Extract the file to the root directory of your microSD card
Now, goto your microSD card
rename the **_epad-user.9.4.2.28.zip to
EP201_SDUPDATE
**don't rewrite the extension so that it's EP201_SDUPDATE.zip.zip, ES File explorer will only allow you to rename the name, not file extension**
You should now have EP201_SDUPDATE.zip on your microsd
**make sure you charged your prime at least 30 min if it turned off previously**
Put microsd in your Prime
Hold the Volume Down button and the Power Button until it resets and something is written at the top asking if you want to boot into a certain mode press volume up.
Immediately press Volume Up. Make sure Microsd with EP201_UPDATE.zip is in Prime.
It will start to switch to the Android Operating Mode screen with the Android lying sideways with some nuclear fission animation going on.
Blue status bar should start within 3 minutes.
Reboot and rewrite should take approximately 5-10 minutes. When done, your About should show .28 update. Hope this helps anyone who was in the same boat as me. I believe my Prime was bricked a certain way - not sure how.
Click to expand...
Click to collapse
Sent from my VS910 4G using Tapatalk 2
I had the same problem. My Prime is on its way to Asus. Does anyone know what their procedure in these cases? Do they reinstall the system and ship the tablet back or is there more to it? I take it this is all under warranty since the tablets were not unlocked?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I don't need it, but it's nice to know with stock recovery. I thought recovery was just missing.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks! I had same issue, just fixed it using this guide! Many thanks to author too!
It's Alive and thank you again for the post and the link, I was really worried about the
If anyone else runs across this thread, you guys don't give up so early. If your prime shows a sign of power, it's fixable without the prime leaving your house.
Congratulations to the guys who are now back up and running. That's amazing. I know how scary that can be to brick an expensive device.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Dont you need to have to be unlocked to be able to install .zips from recovery?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Gabewalters said:
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Click to expand...
Click to collapse
He likely means make sure you download the proper sku version. For example, if you have a u.s. prime, can be seen in settings and about tablet info, then you need to download the version for u.s. primes. If you ww. Then you need to download version for ww. If you De. Version, then you need to download De version for your prime.
So I downloaded the right version but when you unzip it, you get a folder, not another zip file. Any help?
EDIT: Figured it out. Apparently unzipping and then moving to the sd card isnt the same as moving to the sd card and unzipping.
Not so recently, I messed up my Transformer Prime. I was trying to flash a new ROM so I decided to clean all the partitions, memory card, etc. Long story short, I'm nearly sure I deleted the ROM and the recovery... When I turn it on, It won't boot past the Eee Pad splash screen, and if I turn it on holding the volume down button and power button, the white text on the splash screen doesn't go past "Booting recovery kernel image". Is there any way I can fix this? I loved my Prime and I really want to fix it from it's current paper-weight position.
HuskyHamburger said:
Not so recently, I messed up my Transformer Prime. I was trying to flash a new ROM so I decided to clean all the partitions, memory card, etc. Long story short, I'm nearly sure I deleted the ROM and the recovery... When I turn it on, It won't boot past the Eee Pad splash screen, and if I turn it on holding the volume down button and power button, the white text on the splash screen doesn't go past "Booting recovery kernel image". Is there any way I can fix this? I loved my Prime and I really want to fix it from it's current paper-weight position.
Click to expand...
Click to collapse
Download the universal naked drivers in the dev thread and see if you can fastboot to it... then you will have to flash the recovery (through fastboot) then adb and push the rom to it....then install rom through recovery... suggest you use twrp just make sure you use an older version if you haven't used nvflash.... think you need 2.1.... I have a copy somewhere here or you can probably find it in the q&a section as I have posted it there at least once.....
Gage_Hero said:
Download the universal naked drivers in the dev thread and see if you can fastboot to it... then you will have to flash the recovery (through fastboot) then adb and push the rom to it....then install rom through recovery... suggest you use twrp just make sure you use an older version if you haven't used nvflash.... think you need 2.1.... I have a copy somewhere here or you can probably find it in the q&a section as I have posted it there at least once.....
Click to expand...
Click to collapse
my situation is even worse. i get the twrp boot loop, but can't enter fastboot. i can only work in the twrp menu. is there a way to unbrick it?
Gage_Hero said:
Download the universal naked drivers in the dev thread and see if you can fastboot to it... then you will have to flash the recovery (through fastboot) then adb and push the rom to it....then install rom through recovery... suggest you use twrp just make sure you use an older version if you haven't used nvflash.... think you need 2.1.... I have a copy somewhere here or you can probably find it in the q&a section as I have posted it there at least once.....
Click to expand...
Click to collapse
Not to sound like a noob or anything, but I'm not entirely sure how to do all of this. Could you help me or is there a guide or something?
HuskyHamburger said:
Not to sound like a noob or anything, but I'm not entirely sure how to do all of this. Could you help me or is there a guide or something?
Click to expand...
Click to collapse
Look here, if you need more detail, pm me and let me know....
http://forum.xda-developers.com/showthread.php?p=31616679#post31616679
I recently bricked my asus transformer prime by formatting data, system, and cache without checking if I had a rom on my sd card. Without the option in CWM to install from a rom real sd card I tried to install TWRP and now I have no recovery and the screen hangs at Eee Pad splash screen. I still have the ability to use fastboot. If anyone can unbrick my transformer for me I will pay you.
iamnot said:
I recently bricked my asus transformer prime by formatting data, system, and cache without checking if I had a rom on my sd card. Without the option in CWM to install from a rom real sd card I tried to install TWRP and now I have no recovery and the screen hangs at Eee Pad splash screen. I still have the ability to use fastboot. If anyone can unbrick my transformer for me I will pay you.
Click to expand...
Click to collapse
Show me the money lol
Only joking, on the screen where the fastboot icon is you have a line in the top left with bootloader written in it and a long number at the end. It either starts with a 9 or a 10. What is it?
Sorry for the delay had to take one last final, I'm not sure the device has been on all since it will not turn off so I am currently charging it. I will let you know in 30 mins or so.
9.4.2.15
iamnot said:
9.4.2.15
Click to expand...
Click to collapse
Ok, you are on the ICS bootloader at the moment. The first thing we are going to do is flash a version of TWRP recovery on there which will allow you to install a rom off the external SD.
Power off the prime and put yourself into fastboot mode by holding power button and volume down the same time until a few icons appear on the screen. At this point press volume down to go over to the usb icon and then press volume up. It will look like the prime has frozen. Plug the prime into pc and make sure you have the drivers installed. If you do not please install them from here. http://forum.xda-developers.com/showthread.php?t=1426502
Next follow this post to flash ICS twrp http://forum.xda-developers.com/showpost.php?p=34477681&postcount=5705
Only use the file in that link to install it while on ICS bootloader. Later on you are going to flash hairybean 1.51 which will take you up to Jellybean Bootloader. If you use this file after that you will brick your tablet.
You should now be able to boot into recovery again.
Go to the second post here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the "Upgrade Instructions for ICS"
Let me know how it goes.
Thanks for all the help my tablet is back up and running,I finishing the androwook install now.
iamnot said:
Thanks for all the help my tablet is back up and running,I finishing the androwook install now.
Click to expand...
Click to collapse
That will be 200 dollars please.. lol
Glad you're all back up and running mate.
flumpster said:
That will be 200 dollars please.. lol
Glad you're all back up and running mate.
Click to expand...
Click to collapse
the guy didn't even press thanks for ya!
This kinda happened to me. Just download the program to flash TWRP. It's somewhere in XDA. I can link you when I get home. Just put it into fastboot, and USB mode and start the program, and it will flash TWRP. Then use an SD card and put the ROM on it and flash
aznflawless said:
This kinda happened to me. Just download the program to flash TWRP. It's somewhere in XDA. I can link you when I get home. Just put it into fastboot, and USB mode and start the program, and it will flash TWRP. Then use an SD card and put the ROM on it and flash
Click to expand...
Click to collapse
Who are you speaking to? lol
PLEASE HELP ME!! My prime is stock in the first screen!!
Please i need help!! my transformer prime stock in the first screen after i use the ROM Manager to go to CWM...
Wasatronic said:
Please i need help!! my transformer prime stock in the first screen after i use the ROM Manager to go to CWM...
Click to expand...
Click to collapse
I blame rom manager for half of these bricks. It is letting people flash an ICS version of Cwm regardless of what bootloader they are on. Someone should speak to them.
Your tegra logo is in the bottom right meaning you are on the jellybean bootloader. You have flashed a ICS recovery on there and unless you have NVFlash backups or can get into fastboot then you are hard bricked.
So I am trying to get my TF201 from clockwork (running VirtiousPrime .21 4.0.3) to stock. I took the stock .21 blob and put it in ADB folder and ran.
fastboot -i 0x0b05 flash system blob
It just says "Waiting for Device"
That command was confirmed for a TF300, but I couldn't find what exactly to type for the TF201. Is that correct? If so, any idea why it says waiting for device and never continues.
I have some questions for you. Are you ICS or JB bootloader ?
Did you make the copy yourself or find one?
Are you able to use nvflash?
Sent from my LG-E970 using Tapatalk 2
ianwardell said:
I have some questions for you. Are you ICS or JB bootloader ?
Did you make the copy yourself or find one?
Are you able to use nvflash?
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
When I hold power and down the top says 9.4.2.15 then it goes to the screen of (Wipe Data, USB, Android). Maybe that helps on what bootloader I have.
I have never used nvflash before. I received the tablet just how I described and am just trying to go stock with her. The software on it just seems rather buggy and unstable.
kmad86 said:
When I hold power and down the top says 9.4.2.15 then it goes to the screen of (Wipe Data, USB, Android). Maybe that helps on what bootloader I have.
I have never used nvflash before. I received the tablet just how I described and am just trying to go stock with her. The software on it just seems rather buggy and unstable.
Click to expand...
Click to collapse
check a NVflash thread and see if you can do it that way. there are certain requirements needed before one can use it. so thats why im saying look it up.
(thats all i can write right now as my prof just started class)
ianwardell said:
check a NVflash thread and see if you can do it that way. there are certain requirements needed before one can use it. so thats why im saying look it up.
(thats all i can write right now as my prof just started class)
Click to expand...
Click to collapse
Aww man, so it's not going to be as simple as just typing a command in?
I'll read over NVflash thread again and maybe I can understand it now. I remember a few months back it was a little over my head.
If anyone here could offer any tips or advice, I would appreciate it.
I opened my gTab up to resolder the charge port and all went well. I am a very meticulous person. I even take pictures, go slow and do not make dumb mistakes. But... somewhere I did make a mistake, I guess.
Charge port connector works fine now. Wiggle the charge cable and no interruption or blinking on the indicator light.
But... after putting the motherboard back in and testing it, It sticks at the birds. Thought SOMEHOW I must have bricked it because the charge port repair went perfectly. All connectors snugly in their place and oriented correctly.
I have VeganTab 7.0 Ginger and an older CWM on it (non touch). (or rather I did) So I tried to redo a new rom, booting into CWM. I get the standard "recovery key detected" and "booting recovery kernel image" messages at top left.
But, it just sticks there.
So I decided to try the NVFlasher method here: http://raywaldo.com/2011/01/nvflash-for-dummies/
I tried both the 250 and 300 meg partition file.
Wow... went right into APX mode. (I did not expect it to) I ran the nvflasher file and it seemed to finish correctly and successfully.
When I tried to boot into the newer CWM that's in the package, I still see the older CWM come up and it sticks there as it did before.
I tried rewriting files a couple more times but got the same results.
Part of the prob is I guess, is that I don't remember what bootloader was on ot. 1.1 or 1.2.
Also... does the fact that the nvflasher could write to the internal sd card mean that it is ok and I did not screw something up when I did the charge port repair? Well... I mean, I can not verify that it wrote correctly but it seemed to and said "completed successfully".
I was supposed to be selling this to a lady at the Moose lodge today. She has already paid me money on it
Can anyone help me out here or is all lost?
Thank you for your time,
John Dumas
pede69 said:
I opened my gTab up to resolder the charge port and all went well. I am a very meticulous person. I even take pictures, go slow and do not make dumb mistakes. But... somewhere I did make a mistake, I guess.
Click to expand...
Click to collapse
Did you take the appropriate anti-ESD (electrostatic discharge--static electricity) precautions whilst working on the board? Other people here have--from their problem descriptions which match yours--I think, fried some component on their board while fixing the same charge port problem.
Part of the prob is I guess, is that I don't remember what bootloader was on ot. 1.1 or 1.2.
Click to expand...
Click to collapse
If you do a full nvflash (and the images were written correctly), then bootloader version doesn't matter since the bootloader and the kernels in the images will match.
Also... does the fact that the nvflasher could write to the internal sd card mean that it is ok and I did not screw something up when I did the charge port repair? Well... I mean, I can not verify that it wrote correctly but it seemed to and said "completed successfully".
Click to expand...
Click to collapse
Nvflash does not write to the internal SD card--only CWM or the ROM can manipulate it. Nvflash only works on the built-in NAND flash chip. Ie. There are 2 separate storage devices on the gTab.
Ordinarily, based on the on-screen error messages, I would've said that it was a bootloader/kernel mismatch problem, but, this quote of yours below makes me think that it might be a NAND flash problem:
When I tried to boot into the newer CWM that's in the package, I still see the older CWM come up and it sticks there as it did before.
I tried rewriting files a couple more times but got the same results.
Click to expand...
Click to collapse
Both Recovery and the ROM kernel are read from the NAND flash and then is booted into. So, if you can't get into CWM, then you'll have to:
1. Check if the NAND flash is OK by writing to the device partitions and then reading the important partitions back and comparing the resulting image files byte-for-byte. See this post for the read command to be used after doing a full nvflash.
2. If the NAND flash checks out OK, then use a custom kernel which prints diagnostics to see if it detects any other HW problems. See this post for that. The modified kernel is for bootloader version 1.1 only, so you'll have to be on that bootloader to run it.
Awesome reply... Thank you.
I have formated using nvflash and went to write the file but the zip file that I downloaded did not have a bat file in it to tell nvflash what to do. The files came from here:
http://forum.xda-developers.com/showthread.php?t=861950 >>> "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Neither has a bat file to start an nvflash write.
And no, I did not use an anti-static bag. I know it can happen but I have been repairing computers for 20 years and have not zapped anything yet
I'm getting confused now. Can you point me to the correct file to load with nvflash?
Oh yeah... how do I figure out which bootloader I'm on?
You are most awesome for helping, thank you very much.
John
pede69 said:
I have formated using nvflash and went to write the file but the zip file that I downloaded did not have a bat file in it to tell nvflash what to do. The files came from here:
http://forum.xda-developers.com/showthread.php?t=861950 >>> "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Neither has a bat file to start an nvflash write.
Click to expand...
Click to collapse
According to that thread, it does. The file is called "nvflash_gtablet.bat". You might try to: open a CMD.exe window, change to the correct directory and then type: .\nvflash_gtablet
And no, I did not use an anti-static bag. I know it can happen but I have been repairing computers for 20 years and have not zapped anything yet
Click to expand...
Click to collapse
"Yet"--Always a first time, no?
Oh yeah... how do I figure out which bootloader I'm on?
Click to expand...
Click to collapse
As I said, if you do a full nvflash (ie. create, format, and write all the partitions on the NAND flash), then bootloader version does not matter, as the nvflash zip package will have the bootloader and the correct boot and recovery kernels in the image files to match that bootloader. Still, if you want to determine your bootloader version, see this thread.
What you should do first is write bekit's nvflash package to the NAND, then read the important partitions back, then do a byte-compare. I don't use, or have, Windows, but, I recall a MS-DOS command called fc which might still be present on the newer Windows variants:
Code:
C:\SOME\PATH> [B]fc /b [I]file1.img[/I] [I]file2.img[/I][/B]
Do a file compare using fc on the original image file and the read-back image file. If fc reports that one of the files is smaller/larger but reports no differences, then that's OK because a NAND partition read using nvflash reads the whole partition and not just the image that needs to be written to that partition.
If fc reports that the files are the same, then you can move on to step 2 of post #2.
Thanks again for the info. I will try to absorb and apply what you suggest.
BTW... I only asked the bootloader question because of what you mentioned above... "custom kernel which prints diagnostics - only works with 1.1"
Thank you for being there for me. I'll see what I can do now.
John
PS - Here are the unzipped files from nvflash_gtablet_2010110500.zip
pede69 said:
BTW... I only asked the bootloader question because of what you mentioned above... "custom kernel which prints diagnostics - only works with 1.1"
Click to expand...
Click to collapse
If you write bekit's image files, then you'll be on a 1.1 bootloader.
PS - Here are the unzipped files from nvflash_gtablet_2010110500.zip
Click to expand...
Click to collapse
As the thread says, you need to download two zip files. The batch file is in the other one: nvflash_windows_20100500.zip.
OK... I ignored the windows one because there are no instructions to use it and I thought it was for setting up APX on Windows. So I will re-read the instructions again and see what I may have overlooked, and If I can figure out how to use the both of them.
Thank you,
John
OK... after I get my foot out of my mouth, I'll give it a whirl.
J
Well... put contents of both zip files in one folder and ran nvflash.
Said "Completed successfully"
Still boots to old CWM.
Will go read your other instructions now...
J
Well...
Linux is failing to complete.
The following link has some pics from the gTab screen and also three .img files that was created when running the command on the linked page you referred me to. I could not find a txt file that it created.
.\nvflash --bl bootloader.bin --read 4 ebt.img --read 9 rec.img --read 10 lnx.img
http://jaxehost.com/gtab/
So... I guess all is lost. Not sure how to proceed now.
Thanks,
John
pede69 said:
Said "Completed successfully"
Still boots to old CWM.
Click to expand...
Click to collapse
I'm slighty puzzled now--can you elaborate on this: How did you determine that your CWM is unchanged when you're always stuck at the 3 birds screen? Ie. When the gTab isn't booting into CWM where its version can be seen.
I had assumed thus far that you were going by the "Recovery key detected" & "Booting recovery kernel image" messages. Those are bootloader messages (not CWM!) and depending on the bootloader installed you can sometimes differentiate between different bootloaders by looking at what message is printed. But, this is not a definitive method as many bootloaders print the same messages.
pede69 said:
Linux is failing to complete.
The following link has some pics from the gTab screen...
...
So... I guess all is lost. Not sure how to proceed now.
Click to expand...
Click to collapse
The kernel is stopping at the same place as it is here. Except that it is taking ~20 seconds more than is usual to do so. I have to say that this is a HW problem--probably something on the board. The NAND might still be OK, though.
Inspect the place where you soldered, and around it, for stray solder traces or bridges. Otherwise, something on the board has gotten borked. Sorry.
Hey
Guess I'm giving up and giving the person their money back. Damn, I needed it...
What I was saying is that when I installed the old CWM, I used to access it my pressing the power + volume up button. I thought what I see now is what I seen before when it started it but I may be wrong.
Guess I'll koad bekit back on it.
So is there a file to load JUST the CWM script using nvflash?
Also... is there a diag program that I use nvflash to load that will do a NAND and SD Card test?
Thanks for everything,
John
pede69 said:
Guess I'm giving up and giving the person their money back. Damn, I needed it...
Click to expand...
Click to collapse
Technically, the tablet might not yet be a total loss. The error messages indicate that the soft-key controller (SO340010) is failing to respond. Assuming that this is the only HW problem (a big assumption--there might be other things wrong on the board), the kernels (both in the ROM and in CWM) could then be recompiled without that soft-key device driver. Neither CWM nor the newer ICS+ ROMs require those soft-keys anyway. If the new kernels boot, then the soft-key controller is the only problem. Otherwise, the error messages will again have to be looked at to see what else has failed.
As you can see, all this will involve a fair amount of diagnosing and work. You may be able to use the tablet because you know what's wrong and because you have a custom kernel for the ROM and CWM of your choice, however, I don't think the buyer would like to be stuck with only one choice of ROM. Also, if other critical controllers (the touchscreen or WiFi, for instance) have gone belly up, then there's little hope for any Android ROM.
What I was saying is that when I installed the old CWM, I used to access it my pressing the power + volume up button.
Click to expand...
Click to collapse
Recovery mode is always accessed using power and Vol +. These keys assignments, as far as I know, can't be changed.
Not entirely clear on what you're trying to say here...
So is there a file to load JUST the CWM script using nvflash?
Click to expand...
Click to collapse
This post.
Also... is there a diag program that I use nvflash to load that will do a NAND and SD Card test?
Click to expand...
Click to collapse
Because both the bootloader and both CWM and ROM kernels are loading and running, the NAND is very likely OK. If you want to check the NAND partitions, the standard method is to do a full nvflash, read back the partitions, then check the original and read-back images using fc as I've shown. Alternatively, you could try this technique (I haven't tried it, so tell me how well, or if, it works out):
Edit the batch file you're using to do the full nvflash, and add a --verifypart -1 to the nvflash command line, before the --create flag. Save and run the batch file as usual.
The SD card cannot be tested using nvflash. You need either CWM or a ROM for that.
Thanks rajeevvp...
I'll get back at this unit in a while. Between this and the S3 and Note II issues i'm going through, I need a break.
You any good with Verizon phones? hehe...
Thanks,
John
Thanks rajeevvp...
I'll get back at this unit in a while. Between this and the S3 and Note II issues i'm going through, I need a break.
You any good with Verizon phones? hehe...
Thanks,
John
pede69 said:
You any good with Verizon phones? hehe...
Click to expand...
Click to collapse
Sorry, no--can't help with hardware that I don't have.