Hello everybody,
it seems that i have a bigger issue with nvflash. I looked through all threads wich could have information about my problem but i did not find anything useful.
To get to the point.
I tried to install a new rom to my tf201 through twrp. First i needed to upgrade to the jb bootloader. Tried to get there by installing a couple roms that should have it on board wich didnt really work.
After i had it installed i did not have the correct recovery anymore so i tried to install it through nvflash.
So i flashed into nvflash and tried to flash the Recovery from there.
Did all the stuff with flashing trough twrp or nvflash a lot of times before. Im kind of a flshoholic. Flashing my old desire almost weekly
Now my problem. After flashing the recovery through nvflash i rebootet by pressing the power button til it vibrates and waited for something to happen. Nothing happened. Then i tried to get back to nvflash for redoo the flash and sadly had to see that nvflash would not start anymore.
I am able to get into apx. Windows says so too. But when i start to copy wheelie it sends 100% but nothing happend black screen stays black.
I am also not able to get into any else mode. No Recovery, no fastboot no Android no bootscreen nothing. Just apx or Black screen.
It might bee that i did not flash the recovery over instead the bootloader. Used this command in nvflash for flashing the recovery:
nvflash.exe -r --download 4 twrp.img
I hope somebody here had a similar thing or maybe might know what i could or can do.
thank you for youre help and please excuse my bad writing and english. im from germany and not so good with the english spelling
Oh and that is what cmd says:
Waiting for device in APX mode...
[=] Chip UID: 0x15d0787512fea10
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Speedey said:
Hello everybody,
it seems that i have a bigger issue with nvflash. I looked through all threads wich could have information about my problem but i did not find anything useful.
To get to the point.
I tried to install a new rom to my tf201 through twrp. First i needed to upgrade to the jb bootloader. Tried to get there by installing a couple roms that should have it on board wich didnt really work.
After i had it installed i did not have the correct recovery anymore so i tried to install it through nvflash.
So i flashed into nvflash and tried to flash the Recovery from there.
Did all the stuff with flashing trough twrp or nvflash a lot of times before. Im kind of a flshoholic. Flashing my old desire almost weekly
Now my problem. After flashing the recovery through nvflash i rebootet by pressing the power button til it vibrates and waited for something to happen. Nothing happened. Then i tried to get back to nvflash for redoo the flash and sadly had to see that nvflash would not start anymore.
I am able to get into apx. Windows says so too. But when i start to copy wheelie it sends 100% but nothing happend black screen stays black.
I am also not able to get into any else mode. No Recovery, no fastboot no Android no bootscreen nothing. Just apx or Black screen.
It might bee that i did not flash the recovery over instead the bootloader. Used this command in nvflash for flashing the recovery:
nvflash.exe -r --download 4 twrp.img
I hope somebody here had a similar thing or maybe might know what i could or can do.
thank you for youre help and please excuse my bad writing and english. im from germany and not so good with the english spelling
Oh and that is what cmd says:
Waiting for device in APX mode...
[=] Chip UID: 0x15d0787512fea10
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Click to expand...
Click to collapse
I don't have much time at the moment but I can tell you that download 4 is the bootloader partition and that is why you probably can't get anywhere else any more. Download 5 is the recovery partition.
Try adding the -r into your wheelie command to see if it will let you in.
Problem solved
flumpster said:
I don't have much time at the moment but I can tell you that download 4 is the bootloader partition and that is why you probably can't get anywhere else any more. Download 5 is the recovery partition.
Try adding the -r into your wheelie command to see if it will let you in.
Click to expand...
Click to collapse
Thank you so much.
Used following command: wheelie.exe -r --blob.bin
Now after nvflash rescue everthing works again.
You are my hero.
If there is the possablitity to donate u a beer through paypal i will try this right away
fastboot problem
Hey its me again,
got a problem getting into recovery or fastboot.
After restarting the Tablet and holding volume down i get a response:
platform pre os boot configuration
cold-booting android
No option for choosing between fastboot or recovery what so ever.
Than it normally boots into Android and there everything works fine.
I tried rerooting the tf201 using vipermod but still the same problem.
Bootloader is unlocked.
Thanks for the Help
Speedey said:
Hey its me again,
got a problem getting into recovery or fastboot.
After restarting the Tablet and holding volume down i get a response:
platform pre os boot configuration
cold-booting android
No option for choosing between fastboot or recovery what so ever.
Than it normally boots into Android and there everything works fine.
I tried rerooting the tf201 using vipermod but still the same problem.
Bootloader is unlocked.
Thanks for the Help
Click to expand...
Click to collapse
This is probably because you overwrote your bootloader with the download 4 command you did in your first post.
You would need to flash back the correct bootloader.
nvflash.exe -r --download 4 blob.EBT
flumpster said:
This is probably because you overwrote your bootloader with the download 4 command you did in your first post.
You would need to flash back the correct bootloader.
nvflash.exe -r --download 4 blob.EBT
Click to expand...
Click to collapse
Jep did that a couple of times.
Tried the unblobed jb files also the ics files. nothing worked.
Speedey said:
Jep did that a couple of times.
Tried the unblobed jb files also the ics files. nothing worked.
Click to expand...
Click to collapse
At the moment can you still get into android ?
If you can I could try a way thru terminal emulator.
What version of android are you on at the moment? 4.1.1?
flumpster said:
At the moment can you still get into android ?
If you can I could try a way thru terminal emulator.
What version of android are you on at the moment? 4.1.1?
Click to expand...
Click to collapse
Yep can get into Android. Running 4.0.3.
Speedey said:
Yep can get into Android. Running 4.0.3.
Click to expand...
Click to collapse
I don't have files for ICS.
Have you gone thru the whole restore process of your nvflash backups?
wheelie.exe -r --blob blob.bin
nvflash.exe -r --download 4 blob.EBT
nvflash.exe -r --download 5 blob.SOS
nvflash.exe -r --download 6 blob.LNX
nvflash.exe -r --download 10 blob.APP
nvflash.exe -r --go
flumpster said:
I don't have files for ICS.
Have you gone thru the whole restore process of your nvflash backups?
wheelie.exe -r --blob blob.bin
nvflash.exe -r --download 4 blob.EBT
nvflash.exe -r --download 5 blob.SOS
nvflash.exe -r --download 6 blob.LNX
nvflash.exe -r --download 10 blob.APP
nvflash.exe -r --go
Click to expand...
Click to collapse
Yes done that allready.
Used this post:
http://forum.xda-developers.com/showthread.php?t=1927818
But still after flashing all the stuff for ics. Like usually where i can enter in all that i cant even get into fastboot it just says what i wrote before.
Speedey said:
Yes done that allready.
Used this post:
http://forum.xda-developers.com/showthread.php?t=1927818
But still after flashing all the stuff for ics. Like usually where i can enter in all that i cant even get into fastboot it just says what i wrote before.
Click to expand...
Click to collapse
It sounds like you might have messed up the partitions when you flashed that recovery to the bootloader by mistake.
Possibly the easiest way to fix this is to run the "SEMI-AUTOMATED COMPLETE RECOVERY - LINUX ONLY [Read Info Above Before Using This!!]" at the bottom of the post you linked me to.
This will reformat the whole prime to the correct partition sizes.
flumpster said:
It sounds like you might have messed up the partitions when you flashed that recovery to the bootloader by mistake.
Possibly the easiest way to fix this is to run the "SEMI-AUTOMATED COMPLETE RECOVERY - LINUX ONLY [Read Info Above Before Using This!!]" at the bottom of the post you linked me to.
This will reformat the whole prime to the correct partition sizes.
Click to expand...
Click to collapse
Ok will try that. Will take a while though cause ill nett a vbox setup first
But thanks.
Will report my sucsess
Speedey said:
Ok will try that. Will take a while though cause ill nett a vbox setup first
But thanks.
Will report my sucsess
Click to expand...
Click to collapse
If you are going to try it anyway and you don't mind if what I suggest works we can try one other thing first.
Do you want to go to the latest Hairybean rom which is 4.2.2?
flumpster said:
If you are going to try it anyway and you don't mind if what I suggest works we can try one other thing first.
Do you want to go to the latest Hairybean rom which is 4.2.2?
Click to expand...
Click to collapse
Should i not try the stuff u are saying to help me?
Sry for the late response did the semi automated recovery.
Worked all just fine got all my stuff back such as Fasboot.
Wanted to try this rom:
http://forum.xda-developers.com/showthread.php?t=2333171
What do You think about it?
Had trouble editing really big pdf for University with Hairybean got always stuck and really laggy.
Thank you again
Related
I can't get the silly thing to go into recovery mode. It says "recovery key detected" "booting recovery kernel image" and won't do anything else.
It used to be rooted and had a custom rom. Then I accidentally upgraded to a 1.2 rom - I forgot I had downgraded to 1.1. SO the darned thing was sorta bricked. I finally managed, through following several different sets of instructions, to get it back to stock. The tablet now works but I want to go back to a custom rom.
I've tried NVflash - my pc doesn't see the tablet. (it does see it when it's booted normally, just not in recovery mode).
I've tried loading CWM recovery via the SD card and it doesn't work.
I've read several instructions, including the G-tab for dummies but still can't get it to go to recovery. Suggestions on what to do next would be greatly appreciated.
Lanna
lmanalo said:
I can't get the silly thing to go into recovery mode. It says "recovery key detected" "booting recovery kernel image" and won't do anything else.
Click to expand...
Click to collapse
Those messages tell me that you have a 1.2 bootloader now, but, your recovery is still 1.1-based. So now, you'll have to load a version of CWM with a 1.2-based kernel: one of CWM-3.0.2.8rev5, CWM-4.0.1.5 (1.2 bl version), or CWM-5.5.0.4Beta15.
And, you'll have to load recovery using nvflash, like this:
1. Put the gTab into APX mode (for nvflash) by first powering it off, then powering it on by pressing both the Power button and the Vol [-] key. The splash screen with the 3 birds should appear, and then the screen should go blank.
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
3. Now look through the p.txt file for a partition named SOS. Assuming, now, that the partition no. is 9, load the new recovery image using nvflash:
Code:
C:\SOME\PATH> [B].\nvflash -r --download 9 [I]C:\SOME\PATH\recovery.img[/I][/B]
You can get the recovery.img file either from any of the various CWM zip files on the board, or, use one of the image files themselves. Make sure the image is for the 1.2 version of the bootloader, though.
4. After the command completes, power off the gTab, and try to boot into recovery mode as usual.
Thank you so much for your help!!
I followed your instructions and I'm still getting to the same point with the same messages. I verified that I am using an img file for 1.2 bootloader. Actually, I've tried 2 different ones.
I looked at the p.txt and there is a SOS partition and I checked the .cfg file and it lists SOS as 9. I even tried editing the cfg file and changing the name of the file called out in img9 to recovery.img (the CWM recovery image) and ran the complete NVFlash update. It rebooted into normal tablet mode just fine. I shut down and tried booting into recovery and it still doesn't get past those messages.
Is it possible that the partition is corrupt? If so, how do I go about restoring it or creating a new one? I've seen instructions for using CWM recovery but I can't get to it. Can bit be done with NVflash or another utility?
thanks again,
Lanna
lmanalo said:
I even tried editing the cfg file and changing the name of the file called out in img9 to recovery.img (the CWM recovery image) and ran the complete NVFlash update.
Click to expand...
Click to collapse
I would avoid a complete nvflash if at all possible. Otherwise, you risk turning a simple problem--like this one seems to be--into a major headache. The commands I gave are safe because they only read stuff and operate on single partitions--so they won't make your problem worse.
It rebooted into normal tablet mode just fine. I shut down and tried booting into recovery and it still doesn't get past those messages.
Click to expand...
Click to collapse
1. Which nvflash package did you use?
2. Which version of recovery did you load with the ``--download'' command I gave before?
3. Can you post the p.txt file?
4. Also post the *.img that this command produces somewhere so I can take a look at them:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --read 4 ebt.img --read 9 rec.img --read 10 lnx.img[/B]
Is it possible that the partition is corrupt? If so, how do I go about restoring it or creating a new one? I've seen instructions for using CWM recovery but I can't get to it. Can bit be done with NVflash or another utility?
Click to expand...
Click to collapse
Since you're now on the stock ROM you can load recovery only using nvflash--see last post for the command to be used. On rooted custom ROMs you could have used other commands to reload a recovery image.
5. In the stock ROM what TapUI version is displayed in Settings?
1. Which nvflash package did you use?
nvflash 1.2
2. Which version of recovery did you load with the ``--download'' command I gave before?
cwmod v_08
3. Can you post the p.txt file?
4. Also post the *.img that this command produces somewhere so I can take a look at them:
Ive posted them on dropbox but I don't have enough posts on the forum to be able to include the links. Suggestions?
5. In the stock ROM what TapUI version is displayed in Settings?[/QUOTE]
1.2 - 4349
Thanks again,
Lanna
lmanalo said:
1. Which nvflash package did you use?
nvflash 1.2
2. Which version of recovery did you load with the ``--download'' command I gave before?
cwmod v_08
Click to expand...
Click to collapse
No need to post your files. It's as I suspected: your bootloader is 1.2, but, you're trying to run a CWM with a 1.1 kernel on it (cwmod v_08).
See post #2 above and get the correct 1.2 versions mentioned there.
IT WORKED!!!
Now, what ROM do you suggest for 1.2?
Thanks so much.
Lanna
lmanalo said:
Now, what ROM do you suggest for 1.2?
Click to expand...
Click to collapse
That's up to you really. There are a range of 1.2-based ROMs from Froyo (Android 2.2) all the way up to ICS (Android 4.0.4) to choose from. Read the recommendations other people have made on the board when similar questions have been asked.
Hello rajeevvp,
I tried using NVFLASH to unbrick my device, but I get an error message, "USB Device not found".
I updated the APX driver. I can hear a system beep when I plug in my device and then go into APX mode. I tried download.bat and also the nvflash string. Still says no USB found.
Where did I go wrong?
Thanks for any help with this. I have been pretty lucky up to the point of bricking my device.
Thanks Steve.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
same problem.
rajeevvp said:
Those messages tell me that you have a 1.2 bootloader now, but, your recovery is still 1.1-based. So now, you'll have to load a version of CWM with a 1.2-based kernel: one of CWM-3.0.2.8rev5, CWM-4.0.1.5 (1.2 bl version), or CWM-5.5.0.4Beta15.
And, you'll have to load recovery using nvflash, like this:
1. Put the gTab into APX mode (for nvflash) by first powering it off, then powering it on by pressing both the Power button and the Vol [-] key. The splash screen with the 3 birds should appear, and then the screen should go blank.
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
3. Now look through the p.txt file for a partition named SOS. Assuming, now, that the partition no. is 9, load the new recovery image using nvflash:
Code:
C:\SOME\PATH> [B].\nvflash -r --download 9 [I]C:\SOME\PATH\recovery.img[/I][/B]
You can get the recovery.img file either from any of the various CWM zip files on the board, or, use one of the image files themselves. Make sure the image is for the 1.2 version of the bootloader, though.
4. After the command completes, power off the gTab, and try to boot into recovery mode as usual.
Click to expand...
Click to collapse
I have the same problem. I can boot into my custom ROM without a problem (running Smooth_Bean), however, when i try to boot into recovery mode (pressing power and vol+) my gTablet gets stuck on the "recovery key detected" "rebooting recovery kernel image" messages. I tried getting the table and got the p.txt file but its corrupted or something, I tried opening the file with different programs and different code languages but I could not for the life of me figure out which partition is the SOS located in. Thanks in advance!
rvmedina20 said:
I have the same problem. I can boot into my custom ROM without a problem (running Smooth_Bean), however, when i try to boot into recovery mode (pressing power and vol+) my gTablet gets stuck on the "recovery key detected" "rebooting recovery kernel image" messages.
Click to expand...
Click to collapse
If you can boot into a rooted ROM, then you can use the flash_image program to write to a new recovery:
1. Copy the file containing the recovery image (some filename.img) to the SD card.
2. Open a Terminal Emulator window and type these commands (only the stuff in bold):
Code:
$ [B]su[/B]
# [B]/system/bin/flash_image recovery [I]/SOME/PATH/filename[/I].img[/B]
I tried getting the table and got the p.txt file but its corrupted or something, I tried opening the file with different programs and different code languages but I could not for the life of me figure out which partition is the SOS located in.
Click to expand...
Click to collapse
The file is OK--it's just in binary format. The nvflash program you used has created a binary NAND partition table layout file instead of the usual plain text one. The SOS partition is still #9 as per that file.
Try a different nvflash program the next time.
Anyone have the commands to unbrick a Prime that has all the needed files backed up prior to bricking. my tablet isnt bricked but it cant really find a list with the commands in order to unbrick. Figured it could help me and many others to just have one list. Anyone?
Depends on the kind of brick... but for the most case, you could do this...
1. Download a ROM from the Asus site and extract the blob using BlobTools (blobunpack)
2. Enter APX mode [Power + Vol-Up]
3. Run wheelie to start nvFlash mode [This is the blob.bin specific to your device generated while enabling nvFlash]
Code:
wheelie --blob blob.bin
4. Flash the bootloader
Code:
nvflash -r --download 4 blob.EBT
5. Flash the recovery image
Code:
nvflash -r --download 5 blob.SOS
6. Flash the kernel image
Code:
nvflash -r --download 6 blob.LNX
5. Flash the system image
Code:
nvflash -r --download 10 blob.APP
6. Reboot [This should reboot your device, else long-press the power button to reboot]
Code:
nvflash -r --go
If you still cannot recover your device, get in touch with the AndroidRoot folks and they will give you instruction to use the bricksafe images you backed-up...
craigacgomez said:
Depends on the kind of brick... but for the most case, you could do this...
1. Download a ROM from the Asus site and extract the blob using BlobTools (blobunpack)
2. Enter APX mode [Power + Vol-Up]
3. Run wheelie to start nvFlash mode [This is the blob.bin specific to your device generated while enabling nvFlash]
Code:
wheelie --blob blob.bin
4. Flash the bootloader
Code:
nvflash -r --download 4 blob.EBT
5. Flash the recovery image
Code:
nvflash -r --download 5 blob.SOS
6. Flash the kernel image
Code:
nvflash -r --download 6 blob.LNX
5. Flash the system image
Code:
nvflash -r --download 10 blob.APP
6. Reboot [This should reboot your device, else long-press the power button to reboot]
Code:
nvflash -r --go
If you still cannot recover your device, get in touch with the AndroidRoot folks and they will give you instruction to use the bricksafe images you backed-up...
Click to expand...
Click to collapse
How are the Blob tools supposed to be used? If I downloaded the right file from AndroidRoot's Github, the file for downloading is a zip. I didn't see any .exe files in it for Windows. If we're supposed to use linux is there a command line to use the files? I'm downloading some file (I think it's the Official JB ROM from Asus website for TF201) right now. It's about 300 mb in size. A quick guide on the extracting blobs from the ROM would be helpful. Thanks
[UPDATE] Ok so the new instructions help, however, where are the stock files for ICS and which are JB? Any help would be nice... I'm stuck at the 2nd step.
andrewjt19 said:
How are the Blob tools supposed to be used? If I downloaded the right file from AndroidRoot's Github, the file for downloading is a zip. I didn't see any .exe files in it for Windows. If we're supposed to use linux is there a command line to use the files? I'm downloading some file (I think it's the Official JB ROM from Asus website for TF201) right now. It's about 300 mb in size. A quick guide on the extracting blobs from the ROM would be helpful. Thanks
[UPDATE] Ok so the new instructions help, however, where are the stock files for ICS and which are JB? Any help would be nice... I'm stuck at the 2nd step.
Click to expand...
Click to collapse
So I got my tablet booting up again, but I have no way to get into Recovery or fastboot. I used the recovery.bct file I made when I first backed up my tablet using nvflash and such and it worked. However, here's what I am wondering, since I was on an ICS ROM when I did (the first time I went through the nvflash/wheelie process to make it unbrickable) and now I am on a JB ROM. I am pretty sure that what I did was flashed the wrong twrp (the one for ICS and/or Asus bootloader, not the AndroidRoot bootloader) image which caused my boot loop initially. So I think from here the only way I can get back to square one again, is flash the ICS or JB (not sure which one) stock ROM's. However, I don't know how to pull the individual "blob" files out of the zip...
andrewjt19 said:
How are the Blob tools supposed to be used? If I downloaded the right file from AndroidRoot's Github, the file for downloading is a zip. I didn't see any .exe files in it for Windows. If we're supposed to use linux is there a command line to use the files? I'm downloading some file (I think it's the Official JB ROM from Asus website for TF201) right now. It's about 300 mb in size. A quick guide on the extracting blobs from the ROM would be helpful. Thanks
[UPDATE] Ok so the new instructions help, however, where are the stock files for ICS and which are JB? Any help would be nice... I'm stuck at the 2nd step.
Click to expand...
Click to collapse
Just to make it easy for people... I've done the unblob steps and made this a guide... http://forum.xda-developers.com/showthread.php?p=32558144
Hello There Everyone, I hope someone knowledgeable from XDA would help me out a little, I have been having trouble with my prime since I tried to install a new Rom into it, to cut thing short, I am now only able to get into Fastboot on my Prime, I tried flashing TWRP or CWM but they dont show up and only shows the two icons, the fastboot and wipe data. This is really frustrating, I tried to use NVFlash but not sure how do I extract the blob files from the AndroidRoot folder in the internal sd, I have been trying for hours but none of the method works, I really need some guidance on how do I actually restore stock Roms and get it running again! I really hope anyone would help me here..Please! Thank you in Advance!
five_secondskin said:
Hello There Everyone, I hope someone knowledgeable from XDA would help me out a little, I have been having trouble with my prime since I tried to install a new Rom into it, to cut thing short, I am now only able to get into Fastboot on my Prime, I tried flashing TWRP or CWM but they dont show up and only shows the two icons, the fastboot and wipe data. This is really frustrating, I tried to use NVFlash but not sure how do I extract the blob files from the AndroidRoot folder in the internal sd, I have been trying for hours but none of the method works, I really need some guidance on how do I actually restore stock Roms and get it running again! I really hope anyone would help me here..Please! Thank you in Advance!
Click to expand...
Click to collapse
if you are able to get into fastboot mode then it should be easy to get things fixed.
-you are unlocked correct?
-download the twrp.blob appropriate for you bootloader
- fastboot (-i 0x0b05) flash boot twrp.blob
- hold power and volume down,
-press volume up,
-use adb to push a rom to your prime
-factory reset then flash the rom
marko! said:
if you are able to get into fastboot mode then it should be easy to get things fixed.
-you are unlocked correct?
-download the twrp.blob appropriate for you bootloader
- fastboot (-i 0x0b05) flash boot twrp.blob
- hold power and volume down,
-press volume up,
-use adb to push a rom to your prime
-factory reset then flash the rom
Click to expand...
Click to collapse
If he could manage to get twrp on there he wouldn't need to adb push a rom because he would be able to load a rom from an external sd instead which would be easier and faster.
five_secondskin, if you cannot get twrp to work and you did the nvflash process and have the backup files on the internal sd from when you did it then send me a pm and I will give you my google talk name and I will talk you thru it mate.
If you nvflashed and have your files backed up, and can get into APX mode this is how you solve it :
Do you have it NVFlashed with the blobs backed up? If so here's your solution :
1. Download a ROM from the Asus site and extract the blob using BlobTools (blobunpack)
2. Enter APX mode [Power + Vol-Up]
3. Run wheelie to start nvFlash mode [This is the blob.bin specific to your device generated while enabling nvFlash]
Code:
wheelie --blob blob.bin
4. Flash the bootloader
Code:
nvflash -r --download 4 blob.EBT
5. Flash the recovery image
Code:
nvflash -r --download 5 blob.SOS
6. Flash the kernel image
Code:
nvflash -r --download 6 blob.LNX
5. Flash the system image
Code:
nvflash -r --download 10 blob.APP
6. Reboot [This should reboot your device, else long-press the power button to reboot]
Code:
nvflash -r --go
I am trying to repair Galaxy Tab 10.1 3G which don't want to start.
It always start to screen where you can select between recovery and download but nothing happens if I try to select.
If I keep power button long enough pressed, it starts again. (can't poweroff)
I can start in APX mode and read & write memory with nvflash.
I did full wipe with nvflash --create but after that only APX mode was available and screen was black.
nvflash --rawdevicewrite for partitions 2, 3 and 4 returned it back to previous state.
I have also tried to write recovery (cwm and original) with nvflash but no luck.
Any ideas what I can try? Or is it now bricked?
I want to understand how boot process works.
So, I flashed something "wrong" to partition 4 (bootloader):
nvflash --bl bootloader.bin --download 4 boot.img
After this reboot => screen is always blank and only APX mode is available. So: at least it is reading bootloader.
Flashing correct bootloader (backup):
nvflash --bl bootloader.bin --download 4 part-4.img
But But what it should do next, after bootloader? Run kernel from partition 9 or recovery-kernel from partition 8?
If I select download mode, is it still using bootloader or should it run something from recovery partition? Or other partition?
Doh, maybe this tab have faulty hardware but how to detect this??
narska said:
I want to understand how boot process works.
So, I flashed something "wrong" to partition 4 (bootloader):
nvflash --bl bootloader.bin --download 4 boot.img
After this reboot => screen is always blank and only APX mode is available. So: at least it is reading bootloader.
Flashing correct bootloader (backup):
nvflash --bl bootloader.bin --download 4 part-4.img
But But what it should do next, after bootloader? Run kernel from partition 9 or recovery-kernel from partition 8?
If I select download mode, is it still using bootloader or should it run something from recovery partition? Or other partition?
Doh, maybe this tab have faulty hardware but how to detect this??
Click to expand...
Click to collapse
Maybe putting "download-mode-stuff" on any but the bootloader-partition, and putting correct bootloader-stuff in it's partition might help you to get into download-mode. Anyway,... I'm not sure, if your NAND-partition-table is still correct. Try to get into download-mode first and once that's done, try flashing it back to stock with a full image.
I don't think it is fully "hard-bricked" (would APX work then?) but it is also not a "soft-brick".
The NAND, or part of it's content doesn't seem to be as it should and you mentioned working with the stuff on, or even with the partitions.
TnA.Plastic said:
Maybe putting "download-mode-stuff" on any but the bootloader-partition, and putting correct bootloader-stuff in it's partition might help you to get into download-mode. Anyway,... I'm not sure, if your NAND-partition-table is still correct. Try to get into download-mode first and once that's done, try flashing it back to stock with a full image.
I don't think it is fully "hard-bricked" (would APX work then?) but it is also not a "soft-brick".
The NAND, or part of it's content doesn't seem to be as it should and you mentioned working with the stuff on, or even with the partitions.
Click to expand...
Click to collapse
I have spent several days trying to put this in download mode.
Problem is, I have no idea where is "download-mode-stuff", is it inside of recovery partiton?
And I don't know how to setup bootloader so it will start this downloader.
Should I download bootloader source code (u-boot?) and compile it with custom settings?
Is there source & settings available for P7500 original (or custom) bootloader?
Fixed!
It was hardware issue: cleaned system board and now it works just fine!
There was some kind of liquid. soda? juice?
Hello expert,
i try to go from stock asus JB to KitKat 4.4.4-CROMBi-kk-R1-Oct 1
i have tried to follow up the provided instruction http://forum.xda-developers.com/showthread.php?t=2773812 #4
- root the tablet (for titanium)
- i have unlock the bootloader and retrieved nvflash blob (so i should be able to unbrick if necessary)
- i have fastboot twrp_tf201t.blob --> OK
- adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard --> OK
- flash this with TWRP --> OK
so far so good!
Now i reboot and i have the blue bar filled very fast and then it reboot but on android not on TWRP recovery -> ? --> I force the recovery mode to load by power and vol down + RCY
i tried adb reboot-bootloader but it makes the tablet reboot to android . if i restart with power and vol down i still have the USB icon so it seems that i can't upgrade the bootloader
Do i missed something or can i try something else? ( i already tried to wipe dalvik, cache, data, ( even system and they i had to restore my backup)
So i'm not bricked but cannot go forward
thanks for help
(and Sorry for my poor english )
lemicp said:
Hello expert,
i try to go from stock asus JB to KitKat 4.4.4-CROMBi-kk-R1-Oct 1
i have tried to follow up the provided instruction http://forum.xda-developers.com/showthread.php?t=2773812 #4
- root the tablet (for titanium)
- i have unlock the bootloader and retrieved nvflash blob (so i should be able to unbrick if necessary)
- i have fastboot twrp_tf201t.blob --> OK
- adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard --> OK
- flash this with TWRP --> OK
so far so good!
Now i reboot and i have the blue bar filled very fast and then it reboot but on android not on TWRP recovery -> ? --> I force the recovery mode to load by power and vol down + RCY
i tried adb reboot-bootloader but it makes the tablet reboot to android . if i restart with power and vol down i still have the USB icon so it seems that i can't upgrade the bootloader
Do i missed something or can i try something else? ( i already tried to wipe dalvik, cache, data, ( even system and they i had to restore my backup)
So i'm not bricked but cannot go forward
thanks for help
(and Sorry for my poor english )
Click to expand...
Click to collapse
Check bootloader version; should read something like 10.6.1.27.1-20130711. That is a tf300t bl, so you shouldn't flash a tf201 recovery on this but a TWRP for tf300t.
As first aid I would try to flash newest available TWRP from here:
http://forum.xda-developers.com/showthread.php?t=2772093
If this doesn't help, go back to stock ROM following this (mutatis mutandis):
http://forum.xda-developers.com/tra...te-bootloader-to-install-cyanagenmod-t3026252
Then you can start anew with flashing Hairy Bean bootloader.
----> holy @lj50036 give me the link I saw once, where you made up some zips with the tf300t bootloader for tf201 and newer TWRP to get rid of that outdated Hairy Bean crap.
Thank a lot for fast answer :good:
will try asap
I tried yesterday evening.
The bootloader was in version 10.4.2.15 so stock JB. not able to manage to upgrade this Booloader to the 10.6.1.27.1-20130711 that is supposed to install when i flash HairyBean_Bootloader_TWRP2.5.zip
on reboot of bootloader I always have "signature match" message on top a short blue bar and then a reboot .
bootloder keep being the same.
I will try to go back with the second method tonight and see if it help
Deleted!
Hello,
As I have the nvflash blobs, will never complain about someone who try to help and spent time to provide a solution and also like to live dangerously
I will give try to the provided method.
I'll keep you posted if it works or not
Thanks
Well No chance: I flashed the blob but after fastboot reboot i wait a long time but it was freeze saying rebooting in fastboot shell. I did reboot the tab and still the same bootloader . Seems that I will stay with the CM 11 that run much better than the stock JB
thanks for trying
lemicp said:
Well No chance: I flashed the blob but after fastboot reboot i wait a long time but it was freeze saying rebooting in fastboot shell. I did reboot the tab and still the same bootloader . Seems that I will stay with the CM 11 that run much better than the stock JB
thanks for trying
Click to expand...
Click to collapse
Your tab system seems to be a lttle messed up.
As you have your nvflash blobs I would advise to make a complete reset and play back the essential nvflash blobs using:
Code:
wheelie --blob blob.bin
nvflash -r --rawdevicewrite 0 2944 bricksafe.img
That will put partition system back to original (when you pulled the nvflash files).
If you have the blobs of stock separately (search in threads or unblob yourself) play back the partitions you need one by one using:
Code:
wheelie --blob blob.bin
nvflash -r --download 4 blob.ebt
.... [after every nvflash you have to reboot to apx mode]
nvflash -r --download 5 blob.sos
nvflash -r --download 6 blob.lnx
nvflash -r --download 10 blob.app
and try to flash Hairy Bean zip or mine, I provided for changing bootloader again.
.... or play back ASUS stock blob using flashboot command:
Code:
flashboot -i 0x0b05 staging blob
... and then try changing bootloader as above mentioned.
I succeded with any of the methods overcoming a handful of soft bricks.
Good luck!
BCT is invalid or corrupted (code: 12)
Hello,
After some hesitation, i tryed to restore my TF201
but on the first nvflash after wheelie i have the above error . Any way to restore/ correct issue. Is it bricked?
sudo ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4748121b
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
sudo ./nvflash -r --download 4 blob.EBT
Nvflash v1.13.87205 started
[resume mode]
sending file: blob.EBT
blob.EBT sent successfully
bootloader status: BCT is invalid or corrupted (code: 12) message: flags: 0
command failure: bootloader error
lemicp said:
Hello,
After some hesitation, i tryed to restore my TF201
but on the first nvflash after wheelie i have the above error . Any way to restore/ correct issue. Is it bricked?
sudo ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4748121b
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
sudo ./nvflash -r --download 4 blob.EBT
Nvflash v1.13.87205 started
[resume mode]
sending file: blob.EBT
blob.EBT sent successfully
bootloader status: BCT is invalid or corrupted (code: 12) message: flags: 0
command failure: bootloader error
Click to expand...
Click to collapse
As long you have your blob.bin to which wheelie responds, you are not lost.
1. Can you still fastboot, or just flash via APX?
2. What nvflash files do you have? Have you got bricksave.img.
3. What was the version of your bootloader when you pulled nvflash files?
das chaos said:
As long you have your blob.bin to which wheelie responds, you are not lost.
1. Can you still fastboot, or just flash via APX?
2. What nvflash files do you have? Have you got bricksave.img.
3. What was the version of your bootloader when you pulled nvflash files?
Click to expand...
Click to collapse
Hi, OK I found out the reason of above issue ( the file was name bootloader.EBT and not blob.EBT
I have been able to flash the bricksafe.img and the n the bootloader.ebt file then the tablet restart in APX and no more access
wheelie say
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x140737488354528
[-] RCM_Receive communication failure.
- Only APX mode available, no fastboot
- nvflash version 1.5.66719
- the bootloader was in version 10.4.2.15 when i create the blob and bricksafe.img
lemicp said:
Hi, OK I found out the reason of above issue ( the file was name bootloader.EBT and not blob.EBT
I have been able to flash the bricksafe.img and the n the bootloader.ebt file then the tablet restart in APX and no more access
wheelie say
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x140737488354528
[-] RCM_Receive communication failure.
- Only APX mode available, no fastboot
- nvflash version 1.5.66719
- the bootloader was in version 10.4.2.15 when i create the blob and bricksafe.img
Click to expand...
Click to collapse
You are almost there:
Just flash 'bricksafe.img' only with rawdevicewrite! bootloader.ebt is not boot.ebt (thought it also a while ago). by flashing it you messed up bl again; outcome was foreseeable.
bricksafe.img contains PT, EBT, and BCT. After flashing this you should be set to continue with fastboot flashing new TWRP.
Good luck!
das chaos said:
You are almost there:
Just flash 'bricksafe.img' only with rawdevicewrite! bootloader.ebt is not boot.ebt (thought it also a while ago). by flashing it you messed up bl again; outcome was foreseeable.
bricksafe.img contains PT, EBT, and BCT. After flashing this you schould be set to continue with fastboot flashing new TWRP.
Good luck!
Click to expand...
Click to collapse
There is Hope! I managed to make wheelie respond (sudo ./ wheelie --blob blob.bin and restart APX mode while wheelie was waiting
then i did sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
Now my tf201 is able to restart. ( Still has the rom 4.4 cyanogen unofficial that i did flash before trying to use nvflash)
I guess that now i have to reapply the other files to get the initial state
the files I have after wheelie/nvflash backup are
blob.bin ( this is for wheelie for nvflash bootstrap if i did correctly understood)
bricksafe.img this is the one i just flash
bootloader.ebt
create.bct
factory-config.img
recovery.bct
unlock-token.img
not sure if i have to flash another of the above file before trying to flash your file to try change bootloader again
or if i have to flash blob.EBT, blob.LNX, blob.SOS, blob.APP as you describe above ( i managed to retrieved those file from another thread that says they are from stock tf201)
If you can give me a hint, I will wait your advise before to go further (I was really thinking my TF was hard bricked )
Anyway thanks a lot for your help
lemicp said:
There is Hope! I managed to make wheelie respond (sudo ./ wheelie --blob blob.bin and restart APX mode while wheelie was waiting
then i did sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
Now my tf201 is able to restart. ( Still has the rom 4.4 cyanogen unofficial that i did flash before trying to use nvflash)
I guess that now i have to reapply the other files to get the initial state
the files I have after wheelie/nvflash backup are
blob.bin ( this is for wheelie for nvflash bootstrap if i did correctly understood)
bricksafe.img this is the one i just flash
bootloader.ebt
create.bct
factory-config.img
recovery.bct
unlock-token.img
not sure if i have to flash another of the above file before trying to flash your file to try change bootloader again
or if i have to flash blob.EBT, blob.LNX, blob.SOS, blob.APP as you describe above ( i managed to retrieved those file from another thread that says they are from stock tf201)
If you can give me a hint, I will wait your advise before to go further (I was really thinking my TF was hard bricked )
Anyway thanks a lot for your help
Click to expand...
Click to collapse
Glad to see you up and running!
1. Normally you don't need nvflash no more, you can proceed now with fastboot. You can flash the above said blobs, and would come to stock ROM with bootloader 10.4.2.15.
2. You can also flash newest (and for tf201 last) stock ROM 10.4.2.18, downloading from ASUS site via fasboot or TWRP (will guide you).
3. If you want one of them new and shiny Kitkat and Lollipoop ROMs available on tf300t section, you have to upgrade to so called Hairy Bean bootloader, which is in fact bootloader of tf300t and makes your tf201 effectively a tf300t. Don't flash my file!; it's not working (tried myself).
So it's up to you, to choose your next step (don't forget to mark this thread as [SOLVED] and push the thankbutton of the people, that helped you).
das chaos said:
Glad to see you up and running!
1. Normally you don't need nvflash no more, you can proceed now with fastboot. You can flash the above said blobs, and would come to stock ROM with bootloader 10.4.2.15.
2. You can also flash newest (and for tf201 last) stock ROM 10.4.2.18, downloading from ASUS site via fasboot or TWRP (will guide you).
3. If you want one of them new and shiny Kitkat and Lollipoop ROMs available on tf300t section, you have to upgrade to so called Hairy Bean bootloader, which is in fact bootloader of tf300t and makes your tf201 effectively a tf300t. Don't flash my file!; it's not working (tried myself).
So it's up to you, to choose your next step (don't forget to mark this thread as [SOLVED] and push the thankbutton of the people, that helped you).
Click to expand...
Click to collapse
If you would like to PM me with a version of the newest TWRP (or most stable) that works on my Hairybean bootloader I will make you a zip that will upgrade the bootloader and TWRP the same time. I wont be able to test it but I'm sure you could
flumpster said:
If you would like to PM me with a version of the newest TWRP (or most stable) that works on my Hairybean bootloader I will make you a zip that will upgrade the bootloader and TWRP the same time. I wont be able to test it but I'm sure you could
Click to expand...
Click to collapse
vBulletin Message
flumpster has chosen not to receive private messages or may not be allowed to receive private messages. Therefore you may not send your message to him/her.
Click to expand...
Click to collapse
Would love to test zip for you, @flumpster; I can be pm'd. Make sure you don't enblob official v. 2.8.5.0 because it is reported to have flaws in f2fs conversion via repair/change fs. Not sure whether it's the command or the f2fs tool package.
das chaos said:
Would love to test zip for you, @flumpster; I can be pm'd. Make sure you don't enblob official v. 2.8.5.0 because it is reported to have flaws in f2fs conversion via repair/change fs. Not sure whether it's the command or the f2fs tool package.
Click to expand...
Click to collapse
Gimme 5 let me see what is up with my PMs.
Edit : All the settings seem normal and I have room for another 1000 messages so I don't get it. Can someone else try and send me a PM please.
Edit 2 : Just tried to send one to myself and got the same message. Gonna look into it.
Edit 3 : Fixed. You had to be one of my contacts to stop people messaging me all the time. I have turned that off now.
Try this one mate. This is using 2.8.4.0 as you suggested.
To test it you would need to run the downgrade zip first to put you back on the stock bootloader and then try installing this one.
I do not want to upgrade the Hairybean thread with this one as the one Included there works just fine for Hairybean and a lot of people like the theme. You can link them to this version if it works ok.
https://www.androidfilehost.com/?fid=95916177934537044
MD5 : 5b1452e0c968c6e26b14a0abd9c53df6
Let me know if it works ok.
flumpster said:
Try this one mate. This is using 2.8.4.0 as you suggested.
To test it you would need to run the downgrade zip first to put you back on the stock bootloader and then try installing this one.
I do not want to upgrade the Hairybean thread with this one as the one Included there works just fine for Hairybean and a lot of people like the theme. You can link them to this version if it works ok.
https://www.androidfilehost.com/?fid=95916177934537044
MD5 : 5b1452e0c968c6e26b14a0abd9c53df6
Let me know if it works ok.
Click to expand...
Click to collapse
1. Flashed bricksafe.img with stock 10.4.2.15 bootloader. Tab is now softbricked - bootloop (of course).
2. Flashed your upgrade zip: flashed without error msg.
3. No blue progress bar - no success!
Will try to upgrade with your old HB zip.
das chaos said:
1. Flashed bricksafe.img with stock 10.4.2.15 bootloader. Tab is now softbricked - bootloop (of course).
2. Flashed your upgrade zip: flashed without error msg.
3. No blue progress bar - no success!
Will try to upgrade with your old HB zip.
Click to expand...
Click to collapse
Did you check md5? That should have worked but there is a possibility I missed something.
Edit: I just noticed I left the theme ui.zip in that package so twrp might look still themed but I can remove that afterwards. Need to make sure it works first.
Edit 2 : looks like I am not writing the theme in the script so that wouldn't effect anything.
Edit 3. Making a new one. Give me 5.
---------- Post added at 09:16 PM ---------- Previous post was at 08:56 PM ----------
Try this one.
https://www.androidfilehost.com/?fid=95916177934537081
MD5 : afb219f4ecc7f4206ff2c5f558ef3963
If this doesn't work I'm not sure what is going on and might need to get hold of a tablet to try it on.