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?
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.
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 have an issue with the recovery. I tried flashing a blob, a img different versions of twrp. after several failures I "erased" recovery, and flashed again. I tried adb dd... mmcblk8, no go. All that did was erase my system which was still booting until then. I wanted to use my nvflash backups but wheelie won't start either. I reinstalled the binairy too, no go. So then I tried using a blob file until I realized I have androidroot's bootloader. So the answer is flash the raw image of recovery and bootloader right, except no windows tool to do it. Also whenever I try to flash something, I no longer get the little blue line. If I try to use recovery now, I get this:
Update
blade2k11 said:
I have an issue with the recovery. I tried flashing a blob, a img different versions of twrp. after several failures I "erased" recovery, and flashed again. I tried adb dd... mmcblk8, no go. All that did was erase my system which was still booting until then. I wanted to use my nvflash backups but wheelie won't start either. I reinstalled the binairy too, no go. So then I tried using a blob file until I realized I have androidroot's bootloader. So the answer is flash the raw image of recovery and bootloader right, except no windows tool to do it. Also whenever I try to flash something, I no longer get the little blue line. If I try to use recovery now, I get this:
Click to expand...
Click to collapse
Now managed to sort out nvflash binaries to get into it. but I get stuck when trying to flash anything, because it looks like it can't find any partitions. I have a "factory-config.img" would that restore my partition table, and if so how to flash it in nvflash. By the way, it's now stuck in APX mode.
blade2k11 said:
Now managed to sort out nvflash binaries to get into it. but I get stuck when trying to flash anything, because it looks like it can't find any partitions. I have a "factory-config.img" would that restore my partition table, and if so how to flash it in nvflash. By the way, it's now stuck in APX mode.
Click to expand...
Click to collapse
If you have nvflash backups that you made then you should be fine.
Look at the following thread and if the beginning instructions doesn't fix you then try the automated linux recovery, That does everything.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
flumpster said:
If you have nvflash backups that you made then you should be fine.
Look at the following thread and if the beginning instructions doesn't fix you then try the automated linux recovery, That does everything.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Can you tell me what I'm doing wrong. I put all the files in the Home folder, after I copies and pasted the commands in terminal. chmod wheelie did nothing, then wheelie gives me an error: "./wheelie: 1: ./wheelie: Syntax error: word unexpected (expecting ")")".
If it makes a difference, I'm running this from an Ubuntu. Thx.
Edit: nevermind, I was using the wrong wheelie binairies.The ones in Craig 's help page doesn't seem to work I got it from androidrootmobi. Props to kdmd for his post on this issue. I got it to send bootloader; I just about got it working when the battery ran out. So now I have to wait for it to recharge. Bummer!
Finally I get it working but I get system.img too large for partition? I didn't have it so used the one from Unbricker v1.03. Any one have an idea about how to reslove this? Thx.
.com
FINALLY, I got it solved. I was searching online for another system.img when I found this other Guide for nvflash on FrAndroid.com THX to bobby.bobby2 Merci cousin!. Basically the same as Craiggomez except for one critical step that was missing, flashing the bricksafe.img first and foremost, which according to our french counterparts restores the bootloader. From then on just continue with the same order of files to restore from nvflash, or reboot to fastboot and use unbricker.
If you don't mind the french here's the link to bobby.bobby2's guide:
http://forum.frandroid.com/topic/143483-tuto-nvflash-tf201-activation-et-debrickage/
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
I'm hoping that some kind soul can help me. I'm about 10 hours into trying to update what was a stock TF201 to KitKat or possibly Lollipop.
First, I unlocked the TF201 using the official unlocking app supplied by ASUS. I didn't attempt to root as I figured I could flash a ROM that was already rooted. I then installed ADB and Fastboot on my Win7 PC. I had a bunch of trouble getting ADB and Fastboot to work reliably, but after trying a number of different things, I eventually got them both working reliably. I am currently using what I believe is the stock ASUS bootloader (<1.00 e> released by "WW_epad-10.4.2.15-20120917" A03). Next, I finally got CM Recovery 5.8.3.4 installed and working. I tried to flash a couple of different CM ROMs (cm-9.0.0-tf201.zip, cm-9.1.0-tf201.zip, and cm-11-20140926-UNOFFICIAL-tf201.zip), all with the same result. They appeared to install correctly, but upon reboot, they would all hang indefinitely at the initial ASUS splashscreen that says "The Device is UnLocked" in the upper left corner. I tried leaving the tablet alone for up to an hour in hopes that it would eventually start, but no luck. I have a feeling that the current bootloader I'm using is incompatible with the various OS images that I tried to install, but I could obviously be wrong. Can anyone tell me what I'm doing wrong or if there's a different bootloader I should be using?
Thanks in advance for your help!
Please ignore this last post. Somehow I got it working. I wish I could share, but I really don't know how or why it started working again.
I had the same problem after flashing cm 11 to my tf201.
(i followed the guide to make my tf201 "unbrikable" by backing up blobs via nvflash.)
i thried a lot of things to get cm running, but then i choosed "wipe data" in the bootloader menue. after that my tf201 doesn't start at all.
i can see the android robot and a blue status bar for 1 second, then screen turns black 1 second, then the android robot comes back and so on. i can't stop this loop. Pulling down the power button simply starts this process new. can't start bootloader o.e.
What have i dun?? -.-
negRomino said:
I had the same problem after flashing cm 11 to my tf201.
(i followed the guide to make my tf201 "unbrikable" by backing up blobs via nvflash.)
i thried a lot of things to get cm running, but then i choosed "wipe data" in the bootloader menue. after that my tf201 doesn't start at all.
i can see the android robot and a blue status bar for 1 second, then screen turns black 1 second, then the android robot comes back and so on. i can't stop this loop. Pulling down the power button simply starts this process new. can't start bootloader o.e.
What have i dun?? -.-
Click to expand...
Click to collapse
Just restore via nvflash ?
Thx Josh
lj50036 said:
Just restore via nvflash ?
Thx Josh
Click to expand...
Click to collapse
After a long time of hating myself for bricking the tf201 i am about to give a new try to reset via nvflash.
I read the tutorial (http://forum.xda-developers.com/showthread.php?t=1927818) but the attached files for unblobd stock ROMs or the semi-automated complete recovery are not online anymore. anyone who can help me out with the files?
edit: APX driver works.
negRomino said:
After a long time of hating myself for bricking the tf201 i am about to give a new try to reset via nvflash.
I read the tutorial (http://forum.xda-developers.com/showthread.php?t=1927818) but the attached files for unblobd stock ROMs or the semi-automated complete recovery are not online anymore. anyone who can help me out with the files?
edit: APX driver works.
Click to expand...
Click to collapse
If you dont have your blob.bin its pointless..
This file is from your device (needed backed up before a brick) and only for your device......
Thx Josh
do not use CM Recovery ......... USE TWRP
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
YOU HAVE TO FLASH BOOTLOADER ON THE LINK
https://www.androidfilehost.com/?fid=23060877490002899
Check MD5 FEEA44BC7370116E1807DC943E2700B5
unzipit and copy "blob" in adb/fastbooy folder
fastboot flash boot blob
than reboot
YOU HAVE TO FLASH RECOVERY ON THE LINK
https://www.androidfilehost.com/?fid=95916177934539154
Check MD5 118eb4f530c99922126d11f71c981429
unzipit and copy "boot.blob" in adb/fastbooy folder
fastboot erase recovery
fastboot flash recovery boot.blob
reboot
Go to twrp/wipe/format data then type yes
It takes about 70 minutes to format
Make sure that your battery is full
Do Not interrupt format(if you do, it will brick)
After it's done go to Wipe//Advanced Wipe//Select Data
Tap “Repair or Change File System”//”Change File System//F2FS
Swipe to Change
Wipe dalvik cache, system, cache, data, internal storage
Flash KatKiss-5.1.1_TF201_030.zip from microsd card
Flash Supersu.zip
Flash Gapps.zip
Reboot