Related
I have installed the apx drivers and put the tab in nvflash mode. I can sync tab with nvflash --sync command. I got recovery.img from this thread. Can anyone confirm the recovery.img is good and post a bootloader.bin please?
I/O bootloader:
http://droidbasement.com/galaxy/sys-backup/bootloader.zip
Hi everyone
2-3 weeks ago i bought my TF from usa amazon and i decided to root it, i followed the guide in here and user brk rootkit v 6.3 for usa 8.6.5.9 firmware after some tries i got it installed and was running it pretty nice.
the problems started like 3-4 days ago, first time it just suddenly restarted, then after that it would power off alone and after a lot of tries pressing power button for like 20 sec and all combinations like power + vol up power + vol down it will power on again....
but now it wont even power on no matter how much i press power button so i thought it was bricked and followed this guide
thing is when i put it on APX mode and execute download bat file it will start but it will close again right when it says "waiting for bootloader to initialize"
i dont know what else to do and im starting to panick i dont even know whats wrong with my TF, if its bricked or not
please any help will be deeply appreciated
thanks
sorry cant post link yet
i see your new here but please post in the correct section.
as for your transformer. do you get any recognition from the computer at all? And are you still in apx mode? if you are in apx then no worries just restart your computor and your transformer and then just follow these again http://forum.xda-developers.com/showthread.php?t=1123429
if not and if it is completely bricked you might be able to send it back to asus. if they cant get it to work they cant say you rooted it so you might be able to get them to fix it as a software problem
sorry for using the wrong sections..
yea i also followed that guide but happens just the same when i execute download bat file
i cant restart my transformer becuz it wont power on how do i restart it
you should just have to hold power for 20~ seconds. have you tried a highspeed usb port? or a different computor?
i have held down power for many times 20 secs but still nothing.... gonna try on another port, i was trying on my case usb port
Run download.bat in a cmd window and it will show you the error
Sent from my MB855 using XDA App
how do i do that? sorry for being so newbish
Make Sure the TF is fully charged. Also make sure the charger is charging. The wall unit should be very warm if it is charging. If it is not, you may not be charging and have a low or dead battery.
windows->run program->cmd
then in the command directory cd to the one with download.bat, then type download.bat
yeah it does get hot when its charging so its not charging issues and this is the CMD error i get
C:\Users\TONY\Desktop\WINDOWS>cd C:\Users\TONY\Desktop\WINDOWS\
C:\Users\TONY\Desktop\WINDOWS>"nvflash.exe" --bct transformer.bct --setbct --con
figfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682
CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c7005405ff0d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 2
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
- 1361037/1361037 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
3 (0x3) flags: 0
what could it be?
do you have all three of the required files in the nvflash directory?
i believe so ...
i got boot img, recovery img and system img is there anything else requires? or any drivers besides de usbpc
Hello,
First excuse me for my english, my post here is my last chance, i've posted in a french forum but nobody could help me.
My tablet was in a stock rom ics, i've flashed it manually a few days after the release of ics and since i never flash it again.
A day i put my tablet in standby, the day after it was shutted down, when i tried to turn it on i've got this message : "Secure boot : image LNX checksum fail!".
So i tried to turn it on in recovery power button/vol- i've got this message :"Secure boot : image SOS checksum fail!".
I used a tutorial founded here to find my cpuid (ubuntu method) after that i used the "EUUs_SBK_Acer_A500_1.016.05_COM_GEN1" tool to repair my tablet, everything ok, i've got the "PASS" message at the end. So i shut it down and on and now my tablet will boot only in apx mode.
Please help me to unlock my tablet. Thanks.
You should be able to run that EUU again,
Turn tab off and enter apx mode manually using the reset/power button combo. Hook up to yr pc and run the EUU.
Or
use apx flash tool by blackthund3r using bundle 17 from the bundle market inside the app itself. This will flash the unlocked v8 bootloader and cwm so u can flash any custom ics/jb rom. The EUU u used will take u back to stock Acer 3.1.
Good luck!
Sent from my GT-I9300 using Tapatalk 2
Thank you for your answer.
I've tried your second method with apx flash tool. It's blocked here : "Flashing Bootloader (EBT) stage two - uploading image..." and the nvflash command prompt shows "Nvflash started [resume mode]" what can i do ?
Go to the root guide in my sig.
D/l babsector.rar follow these steps here posted by danny2 http://forum.xda-developers.com/showthread.php?t=1624645.....
Sent from my GT-I9300 using Tapatalk 2
I've tried your post 3 in your Beginners Guide - Rooting, Flashing, Unbricking.
Here is the result :
Code:
C:\Users\Arnaud\Desktop\Restore A500\nvflash-A500>nvflash --bct bct.bct --setbct
--bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xE933000
0 0xFF25F106 0xC7061504 0x7C302103 --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0288414542c0d0d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x4 (0x4) flags: 0
Edit : After that i used Babsector, run A501 A.bat -> everything ok, reboot my tablet still in apx mode impossible to enter recovery, run A501 B.bat -> everything ok but the same problem...
But after i run nvflash and flashed a new bootloader, recovery, new boot with no error but i'm still stuck in apx mode.
Edit2 : I retried the "EUUs_SBK_Acer_A500_1.016.05_COM_GEN1" tool : I've got the Pass message but below in red "Secure boot : image LNX checksum fail!". And when i reboot still stuck in apx.
I don't have much time atm, will post later...but u need to flash an ics rom and do the wipes in between running the 2 bat files...did u do this?
Yr issue is two fold. Being stuck in apx and having the checksum error. And also a partition error...mIt will be a matter of trying the tools until it finally works..it does not sound like a hardware fault, so keep trying....
Oh, Ubuntu works when windows won't...u can run the nvflash command direct from there, see lcd047 solution in cpuid guide.
And you must put yr tab in apx mode using the button combo,
Sent from my GT-I9300 using Tapatalk 2
---------- Post added at 10:40 AM ---------- Previous post was at 10:33 AM ----------
arno911 said:
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x4 (0x4) flags: 0
[/CODE]
The 0x4 error....check yr cpuid
Make sure the boot recovery drivers are also installed. ...dl the mini sdk zip in the first post of the cpuid guide
Click to expand...
Click to collapse
dibb_nz said:
[...]u need to flash an ics rom and do the wipes in between running the 2 bat files...did u do this?
Click to expand...
Click to collapse
No i've just launched the 2 bat files. With what tool should i flash the ics rom ?
dibb_nz said:
Oh, Ubuntu works when windows won't...u can run the nvflash command direct from there, see lcd047 solution in cpuid guide.
Click to expand...
Click to collapse
I will try everything under ubuntu now.
Edit : I didn't find how to run nvflash under ubuntu...
dibb_nz said:
And you must put yr tab in apx mode using the button combo
Click to expand...
Click to collapse
Can you explain me this method ? Before i was stucked in apx mode i entered this mode by pressing the reset button + power button 3 seconds. And now i didn't even need to press the reset button my tablet boot on directly in apx mode and is recognized so in windows.
dibb_nz said:
The 0x4 error....check yr cpuid
Click to expand...
Click to collapse
How can i check it ? I got it under ubuntu the only method possible for me.
dibb_nz said:
Make sure the boot recovery drivers are also installed. ...dl the mini sdk zip in the first post of the cpuid guide
Click to expand...
Click to collapse
I don't know how to do that... I have downloaded the mini sdk zip what should i do with ?
Edit : I tried with "V8-UNL-ICS-HC-bootloader-MULTI-cwm" and have a new error maybe it can help...
Code:
**********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Appuyez sur une touche pour continuer...
Flashing HC-Bootloader...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
arno911 said:
How can i check it ? I got it under ubuntu the only method possible for me.
Click to expand...
Click to collapse
The SBK is fine.
If it was not, nvflash would fail already on getting the system information.
Code:
**********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Appuyez sur une touche pour continuer...
[COLOR="Red"]Flashing HC-Bootloader...[/COLOR]
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
Flashing HC-Bootloader???????
Next thing, are u putting your tab in apx mode before you do this???
"...If your tab does not dispay text like "Acer Iconia a500 Download Mode then your tab is not in "apx mode"
i know all thes modes are confusing, but your tab must display "download mode" for the flash to be successful.
There is a great solution recently posted by another user, who like you, got stuck in apx mode....he used nvflash with ubuntu and has written a post on how he went about it....http://forum.xda-developers.com/showthread.php?p=39673261#post39673261
Put your tab in APX Mode
You enter APX mode by holding down the Reset button(with paper clip).
Do not release it.
Hold down power for 3 secs and then release it.
After another second, release the reset button.
Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed.
If you do not have an APX USB device listed in your system tray, you cannot proceed.
The screen of your tablet is black and the Power Light is ON.
dibb_nz said:
There is a great solution recently posted by another user, who like you, got stuck in apx mode....he used nvflash with ubuntu and has written a post on how he went about it....http://forum.xda-developers.com/show...1#post39673261
Click to expand...
Click to collapse
Yes i've just saw it and try. But the same error occured :
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0288414542c0d0d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14) message: nverror:0x4 (0x4) flags: 0
dibb_nz said:
Flashing HC-Bootloader???????
Next thing, are u putting your tab in apx mode before you do this???
"...If your tab does not dispay text like "Acer Iconia a500 Download Mode then your tab is not in "apx mode"
Click to expand...
Click to collapse
Yes my tab was in apx mode at this moment.
How to know if the problem is not hardware, I'm starting to lose hope...
In the past I has installed several custom ROMs on my A500. Mostly civato's variants. I most recently had CM10-FLEX_V6Supercharged_Rev3.3 installed with the v8 ICS Bootloader.
I then tried to do a dirty install of CM10-FLEX_V6Supercharged_Rev3.4. The thought that this would be ok as it was only a single dot release.
The a500 booted and things appeared to be normal. I did not do a whole lot with the tablet at the time. Later I came back and found the tablet was off. When I tried to reboot, I got stuck at the v8 bootloader screen.
Next I figured I might as well put the v9 bootloader on, wipe everything out, and do a clean install of CM10-FLEX_V6Supercharged_Rev3.4.
Upon first boot, the exact thing happened, except this time the table was stuck on the v9 boot screen.
The is when the journey began. I have tried about everything I have been able to find. I have had times where the only thing that works on my tablet is manual APX mode.
The only thing that somewhat works consistently to bring the table back to life is using Timothy's Tool (not sure why this nvflash is different), and running this command:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <mykey> --go
Most times this will get me to a stock-like ROM. Sometimes the nvflash fails. At different spots, so I do not know what is going on there. The most frequent error is the below error, right after checksum.img sent successfully:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
If the flash is successful, I can boot stock rom.
From there I try a myriad of things to put on a patched custom boot loader. I have used the apxflash tool, and nvflash with several of the .bat files you can find. It looks like I can get v8 and v9 of the ICS boot loader installed and can still boot the stock ROM that gets installed with Timorthy's tool. With either the v8 or v9 bootloader installed I can boot stock rom, custom recovery, or quickboot menu.
From there is where things are bad. I have tried to install several custom ROMs from Recovery (Thor 1.7.3) and they appear to install fine. The aroma installer installs the ROMs. If I try to format a file-system (ie., /system,/data,/cache,/flexrom) those all appear to work fine. Unfortunately after I install any custom ROM (RE-FLEXxx-ShellSHOCK-Rev7.0-CuZ-Edition, CM10-FLEX_V6Supercharged_Rev3.4, CM10-FLEX_V6Supercharged_Rev3.3, cm-10.1-20130606-UNOFFICIAL-a500), the same thing happens. I get stuck at the boot screen where it is trying to boot the primary kernel image. It does not matter if v8 or v9 of the Bootloader is installed. The exact same thing happens.
I have been down every rabbit hole I have been able to find, but I cannot find a solution. Has anyone else run into this issue? Anyone have any suggestions?
Thank You.
gemneye said:
In the past I has installed several custom ROMs on my A500. Mostly civato's variants. I most recently had CM10-FLEX_V6Supercharged_Rev3.3 installed with the v8 ICS Bootloader.
I then tried to do a dirty install of CM10-FLEX_V6Supercharged_Rev3.4. The thought that this would be ok as it was only a single dot release.
The a500 booted and things appeared to be normal. I did not do a whole lot with the tablet at the time. Later I came back and found the tablet was off. When I tried to reboot, I got stuck at the v8 bootloader screen.
Next I figured I might as well put the v9 bootloader on, wipe everything out, and do a clean install of CM10-FLEX_V6Supercharged_Rev3.4.
Upon first boot, the exact thing happened, except this time the table was stuck on the v9 boot screen.
The is when the journey began. I have tried about everything I have been able to find. I have had times where the only thing that works on my tablet is manual APX mode.
The only thing that somewhat works consistently to bring the table back to life is using Timothy's Tool (not sure why this nvflash is different), and running this command:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <mykey> --go
Most times this will get me to a stock-like ROM. Sometimes the nvflash fails. At different spots, so I do not know what is going on there. The most frequent error is the below error, right after checksum.img sent successfully:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
If the flash is successful, I can boot stock rom.
From there I try a myriad of things to put on a patched custom boot loader. I have used the apxflash tool, and nvflash with several of the .bat files you can find. It looks like I can get v8 and v9 of the ICS boot loader installed and can still boot the stock ROM that gets installed with Timorthy's tool. With either the v8 or v9 bootloader installed I can boot stock rom, custom recovery, or quickboot menu.
From there is where things are bad. I have tried to install several custom ROMs from Recovery (Thor 1.7.3) and they appear to install fine. The aroma installer installs the ROMs. If I try to format a file-system (ie., /system,/data,/cache,/flexrom) those all appear to work fine. Unfortunately after I install any custom ROM (RE-FLEXxx-ShellSHOCK-Rev7.0-CuZ-Edition, CM10-FLEX_V6Supercharged_Rev3.4, CM10-FLEX_V6Supercharged_Rev3.3, cm-10.1-20130606-UNOFFICIAL-a500), the same thing happens. I get stuck at the boot screen where it is trying to boot the primary kernel image. It does not matter if v8 or v9 of the Bootloader is installed. The exact same thing happens.
I have been down every rabbit hole I have been able to find, but I cannot find a solution. Has anyone else run into this issue? Anyone have any suggestions?
Thank You.
Click to expand...
Click to collapse
Ok to start off.....
timmy deans euu tool. If u run this and its successful you will be back to stock HC 3.2.1. You will be rooted and you will have cwm recovery mode.
Now, once u r back on HC, you can now begin to think about which rom you want to install. Put it on yr ext sd card. With the troubs you are having try civatos pre-rooted stock ics rom.
Next step is to flash the v8. Use the apxflash method.
Choose to dump yr own bct....
Once you get the PASS...boot direct to recovery mode and complete the full wipes....then flash the rom...done!!!
If you complete each step as it is written here you should be good.
Good luck
dibb
Sent from my GT-I9300 using Tapatalk 4 Beta
dibb_nz said:
Ok to start off.....
timmy deans euu tool. If u run this and its successful you will be back to stock HC 3.2.1. You will be rooted and you will have cwm recovery mode.
Now, once u r back on HC, you can now begin to think about which rom you want to install. Put it on yr ext sd card. With the troubs you are having try civatos pre-rooted stock ics rom.
Next step is to flash the v8. Use the apxflash method.
Choose to dump yr own bct....
Once you get the PASS...boot direct to recovery mode and complete the full wipes....then flash the rom...done!!!
If you complete each step as it is written here you should be good.
Good luck
dibb
Click to expand...
Click to collapse
Yes, I have been down every one of those steps as mentioned in my first post. I can not run timmy deans euu tool (root-3.2.1_v4) as documented, because I can not boot my tablet. What I can do is change to the Image directory on Timmy dean's tool, and manually run --
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <my_key> --go
I have gotten stock booting from v8 and v9 patched boot loaders. It is the next step after that. I do a wipe (factory reset). Do a "real" delete of /data, and go through the Aroma installer (which appears to finish without any problem).
When I boot, it never gets past the bootloader screen. It does not go black or anything. It just shows the booting primary kernel image message and hangs.
Now, I am not even able to run the nvflash command. I am starting to wonder if there is a hardware storage problem. I can't even create the partitons.
After u run timmydeans, can u boot to the OS
Sent from my GT-I9300 using Tapatalk 4 Beta
---------- Post added at 06:12 AM ---------- Previous post was at 06:00 AM ----------
gemneye said:
...
It is the next step after that. I do a wipe (factory reset). Do a "real" delete of /data, and go through the Aroma installer (which appears to finish without any problem).
When I boot, it never gets past the bootloader screen. It does not go black or anything. It just shows the booting primary kernel image message and hangs.
.
Click to expand...
Click to collapse
Tell me which recovery you sre using...cwm 1.7.3 works best. Forget aroma and use that pre rooted stock rom until we get u sorted.
I know u said youve done everything over and over but please run thru those steps EXACTLY as i wrote them
Yes it maybe the chip...can't tell without nvflash output...the only one u posted showed bct error....which apxflash tool fixes
Sent from my GT-I9300 using Tapatalk 4 Beta
About to throw in the towel
dibb_nz said:
After u run timmydeans, can u boot to the OS
---------- Post added at 06:12 AM ---------- Previous post was at 06:00 AM ----------
Click to expand...
Click to collapse
After Timmy's tool, I was able to boot just fine. I got to this point a few times. There was no patched boot loader or no custom recovery. Basically I had a bootable tablet running what looked to be a STOCK ROM.
I could then install v8 or v9 patched ICS loader and custom recovery (CWM THOR 1.7.3). I could boot custom recovery (Vol-down + Power), Quick Menu (Vol-up + Power), or the Stock ROM (Primary Kernel Image). This would work consistently.
Then I would install a custom ROM (tried many of them, even ones that had worked previously) and I could never get the ROM to boot. I would get stuck on the boot loader screen stating Primary Kernel was trying to boot.
Since then I can no longer use Timmy's tool. I am now consistently getting this error:
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) message: nverror:0x42008 (0x6042008) flags: 0
Except for getting the tablet to boot a few times after using Timmy's tool, I would venture to guess there is an underlying hardware issue. Once I had it booted to Stock I think it gave me false hope. Now that I am consistently getting storage device type errors using different combinations of nvflash, I am thinking there might be a more serious issue.
I just spent half an hour on a reply, and its not showing. ...grrrrr ... its past my bedtime so I'll get bsck to you in the morning! !!
Sent from my GT-I9300 using Tapatalk 4 Beta
gemneye said:
The only thing that somewhat works consistently to bring the table back to life is using Timothy's Tool (not sure why this nvflash is different), and running this command:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <mykey> --go
Click to expand...
Click to collapse
This was the only thing that worked to get my a500 out of APX mode! I thought for sure she was a gonner.
dibb_nz said:
Ok to start off.....
timmy deans euu tool. If u run this and its successful you will be back to stock HC 3.2.1. You will be rooted and you will have cwm recovery mode.
Now, once u r back on HC, you can now begin to think about which rom you want to install. Put it on yr ext sd card. With the troubs you are having try civatos pre-rooted stock ics rom.
Next step is to flash the v8. Use the apxflash method.
Choose to dump yr own bct....
Once you get the PASS...boot direct to recovery mode and complete the full wipes....then flash the rom...done!!!
If you complete each step as it is written here you should be good.
Good luck
dibb
Click to expand...
Click to collapse
I have the similar issue to gemneye.
I can use timmy deans euu tool to get to stock hc 3.2.1 and can boot without issues.
I can flash the v8 using apxflash and I install cwm thor 1.7.3.
Still boots up fine after flashing v8/recovery.
No matter what rom I install at this point I am stuck at the screen with "Booting primary kernel image". Even civato's stock rom won't go past this screen.
The only part of your instructions that I have an error is when trying to dumb the bct. I would have to guess that this is the reason I'm stuck. While trying to dumb the bct APX Flash tool pops up and says "Could not find file bct.dec" I can't find any other tool to fix the bct. Any ideas?
RedOmega said:
I have the similar issue to gemneye.
I can use timmy deans euu tool to get to stock hc 3.2.1 and can boot without issues.
I can flash the v8 using apxflash and I install cwm thor 1.7.3.
Still boots up fine after flashing v8/recovery.
No matter what rom I install at this point I am stuck at the screen with "Booting primary kernel image". Even civato's stock rom won't go past this screen.
The only part of your instructions that I have an error is when trying to dumb the bct. I would have to guess that this is the reason I'm stuck. While trying to dumb the bct APX Flash tool pops up and says "Could not find file bct.dec" I can't find any other tool to fix the bct. Any ideas?
Click to expand...
Click to collapse
There is a specific order to doing things successfully with the Acer, any deviation at all and things wont work as they should. You must flash your rom directly after flashing the v8.
Flash the v8/cwm 1.7.3
Boot directly to cwm and complete a full wipe
Flash your rom
reboot.
If u run the v8 from HC and reboot without flashing an ICS rom first you will get stuck with booting primary kernel image...Why?? cos you have HC rom with the unlocked bootloader - the unlocked bootloader will only work with ICS/JB roms!! I'm assuming this is the reason for the "bct.dec" error as well. Try it again in the order I posted above
dibb_nz said:
There is a specific order to doing things successfully with the Acer, any deviation at all and things wont work as they should. You must flash your rom directly after flashing the v8.
Flash the v8/cwm 1.7.3
Boot directly to cwm and complete a full wipe
Flash your rom
reboot.
If u run the v8 from HC and reboot without flashing an ICS rom first you will get stuck with booting primary kernel image...Why?? cos you have HC rom with the unlocked bootloader - the unlocked bootloader will only work with ICS/JB roms!! I'm assuming this is the reason for the "bct.dec" error as well. Try it again in the order I posted above
Click to expand...
Click to collapse
Keep getting format errors when trying to flash anything now. APXFlash would hang repeatedly when trying to flash v8/cwm 1.7.3. Couldn't see any error messages in the cmd windows/debug but some of them closed so fast I may have missed it. So I went back to trying the manual return to 3.2.1 that OP used earlier and now I can't even get that to complete without errors.
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --crea
te --bl bootloader.bin --sbk 0x4CA71E00 0x74B3D706 0x9BFA3304 0xA02A2103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c61c04240f357
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) me
ssage: nverror:0x42008 (0x6042008) flags: 0
I've tried babsector and manuall install of v8 using v8.bat as well and get error messages with those too.
Babsector gives me this:
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
v8.bat gives me some different errors:
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c61c04240f357
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42004 (0x42004
) flags: 0
*****************************************************************
* Press any key when your A500/501/G100W is in bootloader mode *
*****************************************************************
Press any key to continue . . .
Flashing bootloader: bootloader_v8.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Reading some of your replies in other posts Dibb, I'm guessing you'd say memory chip issue and that tab is toast?
Oh darn
Yep your conclusions are correct.
Maybe pickup new one off ebay they were going reasonably cheap awhile back sub US$80???
Sent from my GT-I9300 using Tapatalk 4
I followed androidroot.mobi's guide to pulling nvflash blobs for a Nexus 7. I was able to successfully do this, but I had problems trying to go back to stock. I flashed the stock recovery and then tried to flash the stock bootloader; first I used "fastboot flash boot bootloader.img" using the bootloader.img from JDQ39 but the bootloader version did not change. I then used "fastboot flash bootloader bootloader.img" and got the signature mismatch error mentioned elsewhere in the guide thread.
By this point for some reason the device would not boot to Android though the bootloader continued to work. I've tried to "unbrick" using wheelie --blob <path to blob.bin> --unbrick <path to bricksafe.img>
It gets stuck here:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d4a826d48040b
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
And now the bootloader doesn't seem to work; I can't get into anything other than APX.
This is just a comedy of errors, and of course it isn't my device; I didn't have any trouble with mine. :/ Any ideas on how to recover?
heterodoxy said:
I flashed the stock recovery and then tried to flash the stock bootloader; first I used "fastboot flash boot bootloader.img" using the bootloader.img from JDQ39 but the bootloader version did not change. I then used "fastboot flash bootloader bootloader.img" and got the signature mismatch error mentioned elsewhere in the guide thread.
Click to expand...
Click to collapse
After some more research I'm really starting to suspect that I borked the kernel by doing this (boot vs. bootloader, why was flashing a bootloader to the former allowed?!) and that wheelie then borked the bootloader. If I can get the bootloader back I can get the kernel back, but I need help with the misbehaving nvflash...
U need to rma your tablet to get it fixed and about bootloader flashing every thing u do to your device is your choice no one is forcing u to do so. Thats y every op say i am not responsible.
Please ignore my spelling mistakes. English is not my native language.
xateeq said:
U need to rma your tablet to get it fixed
Click to expand...
Click to collapse
It'd be quicker to do it myself and it should be possible; that's the whole point of the guide to gaining nvflash access (on androidroot.mobi), with which you may or may not be familiar. There's no hardware problem that would make an RMA the only option; I just need a little better of an idea of how to proceed from here with nvflash specifically.
xateeq said:
and about bootloader flashing every thing u do to your device is your choice no one is forcing u to do so.
Click to expand...
Click to collapse
That's a little apropos of nothing. I don't disagree, and I've never said that flashing boot instead of bootloader was anything but a screw-up on my part. But my impression was that this is a community of developers like myself, all of whom I dare say have screwed up at least once (I know this isn't the first time for me), and I figured someone else may have learned or may know the right incantation to recover from this particular situation and may be able to pass it on.
It'd probably have been easier for me to post in the thread that concerns gaining nvflash access and supports some of the tools therefor, but I can't do that yet as it's in a development forum, so I can only hope for the right person to stumble across this thread.
Thanks.
heterodoxy said:
It'd be quicker to do it myself and it should be possible; that's the whole point of the guide to gaining nvflash access (on androidroot.mobi), with which you may or may not be familiar. There's no hardware problem that would make an RMA the only option; I just need a little better of an idea of how to proceed from here with nvflash specifically.
That's a little apropos of nothing. I don't disagree, and I've never said that flashing boot instead of bootloader was anything but a screw-up on my part. But my impression was that this is a community of developers like myself, all of whom I dare say have screwed up at least once (I know this isn't the first time for me), and I figured someone else may have learned or may know the right incantation to recover from this particular situation and may be able to pass it on.
It'd probably have been easier for me to post in the thread that concerns gaining nvflash access and supports some of the tools therefor, but I can't do that yet as it's in a development forum, so I can only hope for the right person to stumble across this thread.
Thanks.
Click to expand...
Click to collapse
Please i mean no disrespect but every night i go to Q&A section and ever were i see is people having bricked device because of screwed bootloader that they flashed wrong, and i have yet to see a proper solution.
Only solution i have seen is that u do a backup of it before u doing any thing and to backup ur device specific files u again need to load custom bootloader and that on its own is scary.
So there isn't a easy way to backup the device specific files? And I tried the nvflash method and flashed the stock bootloader without any issue... I guess I was just lucky to get away with it...
TheDj408 said:
So there isn't a easy way to backup the device specific files? And I tried the nvflash method and flashed the stock bootloader without any issue... I guess I was just lucky to get away with it...
Click to expand...
Click to collapse
If you have correct files then it shouldn't be a problem. If u flash wrong file the **** hits the fan.
Please ignore my spelling mistakes. English is not my native language.
I have exactly the same Problem as the TO...
TheDj408 said:
So there isn't a easy way to backup the device specific files? And I tried the nvflash method and flashed the stock bootloader without any issue... I guess I was just lucky to get away with it...
Click to expand...
Click to collapse
How exactly did you do this? And can you upload the wheelie binary you used, maybe theres only something wrong with our wheelie version...
Partitionator said:
I have exactly the same Problem as the TO...
How exactly did you do this? And can you upload the wheelie binary you used, maybe theres only something wrong with our wheelie version...
Click to expand...
Click to collapse
You're getting the Sending BCT hang/Error 3 with wheelie?
I think there's definitely something wrong with wheelie in general. I've tried the two versions on androidroot.mobi's Web site and the 0.2 version of wheelie posted elsewhere on this forum and had no success with any of them, at least on the bricked device. On a regular device (I'm trying them side by side) it's fine, so there's that.
With the bricked device I've been having more success (and been learning more) just using nvflash with the --blob parameter. I still get errors, but they're actually errors from the device or from the bootloader instead of a generic error sending information to/receiving a response from the device.
Partitionator said:
I have exactly the same Problem as the TO...
How exactly did you do this? And can you upload the wheelie binary you used, maybe theres only something wrong with our wheelie version...
Click to expand...
Click to collapse
I did the method right... I was able to see the files in tab but failed to get them in pc... So Iflashed ooriginal stock bootloader... I meant this...
Yeeeeeaaaaaaaaahhhhhhhhhhhh
I think my Nexus isn't dead... I experimented all day and all night long with nvflash, read much about the emmc partitions and finally something worked... Now it shows Google with the unlock symbol
I think the rest sould be easy..
First I created a flash.cfg. You can do that under linux with bct_dump under Linux. (I used recovery.bct which was created with the blob.bin)
Than I had to remove the line that starts with type= in thefirst section of the flash.cfg file.
here ist my flash.cfg file (16GB Nexus 7)
Code:
[device]
instance=3
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.EBT
[partition]
name=SOS
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.SOS
[partition]
name=LNX
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.LNX
[partition]
name=BAK
id=7
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=GP1
id=8
type=GP1
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=536870912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.APP
[partition]
name=CAC
id=10
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=MSC
id=11
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=USP
id=12
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=PER
id=13
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=YTU
id=14
type=data
allocation_policy=sequential
filesystem_type=basic
size=524288
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=UDA
id=15
type=data
allocation_policy=sequential
filesystem_type=ext3
size=18432
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x808
percent_reserved=0
[partition]
name=GPT
id=16
type=GPT
allocation_policy=sequential
filesystem_type=basic
size=0xFFFFFFFFFFFFFFFF
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
After that I ran this command:
Code:
./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
bäääm some output in the terminal (and Google flashed up on the device):
Code:
[email protected]:/home/jan/APX# ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
Nvflash v1.13.87205 started
Using blob v1.13.00000
USB device not found
[email protected]:/home/jan/APX# ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
Nvflash v1.13.87205 started
Using blob v1.13.00000
chip uid from BR is: 0x0000000000000000015d2bc285340e0f
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d2bc285340e0f
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 1
device config fuse: 17
sdram config strap: 0
sending file: recovery.bct
- 6128/6128 bytes sent
recovery.bct sent successfully
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.ebt
- 2146912/2146912 bytes sent
bootloader.ebt sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 0 3
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: specified device is invalid (code: 6) message: nverror:0x4 (0x4) flags: 0
[email protected]:/home/jan/APX#
But you can see there is still a error and I use the create command what should earse everthing so you should only do this if you habe a backup of all imortant partition. But I recommend that you wait while I will test what I can do with that, and look what that error means.
EDIT: Very good in this state I have nvflash acess and can flash partitions...
EDIT2: Yeeeees its booting again, with all data on it, that means no wipe . First i flashed many partitions (i don think that flashing most of them was unecessary). Tomrrow I will brick my device again and then test what exactly to do...
EDIT3:
heterodoxy said:
You're getting the Sending BCT hang/Error 3 with wheelie?
I think there's definitely something wrong with wheelie in general. I've tried the two versions on androidroot.mobi's Web site and the 0.2 version of wheelie posted elsewhere on this forum and had no success with any of them, at least on the bricked device. On a regular device (I'm trying them side by side) it's fine, so there's that.
With the bricked device I've been having more success (and been learning more) just using nvflash with the --blob parameter. I still get errors, but they're actually errors from the device or from the bootloader instead of a generic error sending information to/receiving a response from the device.
Click to expand...
Click to collapse
Sorry I overread your Post... Yes it was the same error (3)
EDIT4: read here for unbricking: http://forum.xda-developers.com/showpost.php?p=48507424&postcount=16
Partitionator said:
Yeeeeeaaaaaaaaahhhhhhhhhhhh
Click to expand...
Click to collapse
You need a CSI gif there.
Partitionator said:
EDIT2: Yeeeees its booting again, with all data on it, that means no wipe . First i flashed many partitions (i don think that flashing most of them was unecessary). Tomrrow I will brick my device again and then test what exactly to do...
Click to expand...
Click to collapse
You are made of brilliant. I think I was on the same track as you but I didn't know about bct_dump and so I don't think my flash.cfg is exactly right. I'll be experimenting all night too. On my working device I backed up ALL THE PARTITIONS but on this device I only have what was pulled during the creation of the blobs (blob.bin, bootloader.ebt, create.bct, recovery.bct, etc.)
Cheers!
heterodoxy said:
You need a CSI gif there.
You are made of brilliant. I think I was on the same track as you but I didn't know about bct_dump and so I don't think my flash.cfg is exactly right. I'll be experimenting all night too. On my working device I backed up ALL THE PARTITIONS but on this device I only have what was pulled during the creation of the blobs (blob.bin, bootloader.ebt, create.bct, recovery.bct, etc.)
Cheers!
Click to expand...
Click to collapse
So ist your device working again? If not:
I think the missing partitions shouldn't be a Problem... if you haf the 1GB Version it think you can use my BCT (I learned of the existence of this tool somewere on the third page on google, aftere reading all pages before). After you habe it on nvflash mode, try holding vol down and nflash --resume --go and it should go into fastboot mode were you can reflash the bootloader from the last Kitkat factory Image... I don't tested this way but i think it should work...
And would you mind hitting the Thanks Button? It costed me many houres to find out how to get it in nvflash mode again and I wrote the post before I rewrote my bootloader
EDIT: OK my device is now bricked again (wrote zeros to mmcblk0boot0) First I made the bootstrap command better:
Code:
./nvflash --setbct --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin --go
as you can see I removed --create and addet --go. The create command made the error (an because that my device wasn't wiped). I addet the go because without that I got "no command error". The go command dosen't do anything in my case, so i think the way i mentioned before in this post wouldn't work... And you need to flash something before...
EDIT2: ok the command above doesn't work because the --go command makes it leave nvflash mode, so the command with create in it is the best I found. Creat will fail but, but that ist good (so no wipe), but it was the only one I found that let you use setbct. And you can generate your flash.cfg file from create.bct. If you use create.bct instead auf recovery.bct for generating your flash.cfg file you don't have to remove this one line...
Partitionator said:
So ist your device working again?
Click to expand...
Click to collapse
Yes and no. When I tried the command you gave last night it bounced to the Google screen, which almost made me cry of happy because some of the errors I'd been getting had me dreading the possibility that the blob could have been good but the bootloader.ebt/BCT files weren't. I got "battery is too low" repeated over and over which I've seen before; not surprising given how much I've played with the thing. Wasn't returned to command prompt and --resume commands in another prompt didn't work. Wasn't at all sure that it'd charge in this mode (especially with the screen on) but plugged it into a 2A charger and hoped for the best.
It was off when I got up a few hours later and I had a minor heart attack, but if I run the command now, it bounces to the Google screen and returns me to the command prompt and as you noted, I can download partitions which is HUGE and I'm backing them all up now, UDA first. (As I mentioned, this wasn't my device, so I was dreading having to wipe user data though if that's what it took to unbrick it I'd obviously do it in a heartbeat.)
nvflash --resume --go doesn't seem to be putting me in fastboot with the Vol- button held down, unfortunately. I'm not sure if that functionality is in the bootloader itself or in another partition (e.g. does the bootloader for the Tegra 3 chain to the Android bootloader or is it the same thing?). So I'm going to poke at the partitions on my other device and see what matches bootloader-grouper-*.img and see if it works after I flash that (and boot.img) from the factory image the device was using (JDQ39).
On a technical side note, the flash.cfg you provided is interesting, though clearly it works. I had been basing mine off the partition table of a working device and not only were sizes (which I got by multiplying sectors by sector size) different but IDs were too (e.g. PT was 524288 for me, 4096 for you, partition 5 is SOS for you but EKS for me? Which is somewhat backed up by the androidroot.mobi guide when it suggests backing up partition 5 as EKS. But it may not matter as long as the sizes and numbers are right...)
Partitionator said:
And would you mind hitting the Thanks Button? It costed me many houres to find out how to get it in nvflash mode again and I wrote the post before I rewrote my bootloader
Click to expand...
Click to collapse
Absolutely; in fact, if you have a PayPal (you can PM me), I'd like to buy you a beer or something. I appreciate your help over the holidays after I was feeling ignored (and at a certain point, ridiculed) for a couple days. We're developers, we play with things we're not supposed to, and sometimes that means we brick our devices. But I've certainly learned a lot.
TheDj408 said:
I did the method right... I was able to see the files in tab but failed to get them in pc... So Iflashed ooriginal stock bootloader... I meant this...
Click to expand...
Click to collapse
I'm glad that worked for you! For the record I got a signature verification error when I tried to do this originally; some other users on the androidroot.mobi thread got one too. As mentioned, if you have issues flashing the bootloader with fastboot you can do it with nvflash --download 4; another user said this precluded using fastboot again in the future but I find that somewhat dubious.
How to unbrick
So here is the shorten way to recover your device from a Fullbrick:
First: I´m not an expert for that and this is the result of many houres of testing, so I don´t think its the best way to unbrick, but at the moment its the only one and it works.
And I can saftly say if you don't have the blob bin and you screwed up your bootloader I can't help you, nobody can help you, you have to buy a new Mainboard. If you have your blobs follow this guide:
you need:
your blob.bin with bootloader.ebt and recovery.bct
Linux (only to generate your flash.cfg)
nvflash binarays from here: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
a working bootloader.img from a factory image and a boot.img (you can use one from a factory image) (I used 4.4, the bootloaders in 4.3 and 4.4.2 are corrupt!)
I recommed to use the boot.img of your actual installed rom/kernel.
First you need to generate your flash.cfg. I've done this wit dump_bcd under Linux. I got this with the package cbootimage under Kubuntu.
I generated it from my recovery.bct. After that you have to remove the line that starts with type from the device section in the flash.cfg.
(maybe someone wants to write this part more accurate because bct_dump doesn't work anymore on my PC)
If you have a 16GB Nexus 7, I think you can use the attached one (you have to rename it), but no guarantee if it doesn't work.
Than you put all this files together in a folder (nvflash, blob.bin, bootloader.ebt, recovery.bct, boot.img, bootloader.img/bootloader-grouper-4.23.img, flash.cfg).
Than you go with a terminal there. Under windows you just have to remove the sudo ./ at the begining of the commands and maybe you should run it as Admin.
First we bootstrap it to the nvflashmode. Of cause your device has to be in APX Mode.
WARNING: If you execute this command you have to reflash the bootloader even if you have a working installed because it will wipe your installed bootloader (I think)
Code:
sudo ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
You can see I used the --creatte command there. It will fail (so nothing will be wiped, but im not responsibile if it will wipe something) and its only there to allow me to use the --setbct command.
After this command you should see Google on your device and your terminal should produce a output like that (the error ist as said from create):
Code:
Nvflash v1.13.87205 started
Using blob v1.13.00000
chip uid from BR is: 0x0000000000000000015d2bc285340e0f
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d2bc285340e0f
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 1
device config fuse: 17
sdram config strap: 0
sending file: recovery.bct
- 6128/6128 bytes sent
recovery.bct sent successfully
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.ebt
- 2146912/2146912 bytes sent
bootloader.ebt sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 0 3
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: specified device is invalid (code: 6) message: nverror:0x4 (0x4) flags: 0
The next command will flash a kernel (however without flashing a kernel it won't go to fastboot mode) and than bring set your device into fastboot mode. You have to hold Vol- after/while hitting enter till its in fastboot mode. If you don't hold vol- it will boot to android and you have to start from the begining.
Code:
sudo ./nvflash --resume --download 8 boot.img --go
Now you should be in fastboot mode and the last step is very easy:
simply reflash the bootloader:
Code:
fastboot flash bootloader bootloader.img
or in case of the lastet bootloader
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
Now your device should be unbricked
If not you can try to bootstrap it again to nvflash mode and than flash your bricksafe.img
Code:
nvflash --resume --rawdevicewrite 0 2688 bricksafe.img
And if you need you can reflash the other backed up Partitions too:
Code:
nvflash --resume --download 5 eks.img
nvflash --resume --download 13 factory-config.img
nvflash --resume --download 14 mda.img
After that your device should at least go to fastboot mode again If not let me know and I will try to help you.
If I helped you please hit the thank button, it took me a few days to test this all and it was a lot of work to write this. And please thank the guys that created flatline too, they are the true geniuses .
EDIT: If you have trouble with this way, try (in nvflashmode) to download the flatline recovery to partition 7 (it will straigth boot to ist) and reinstall the flatlinebootloader.
I onetime I unbricked my device the firstway I hat terrible lags, after, and the only way I found to fix them was to reflash the flatlinebootloader (after that i could flash any bootloader without lags)...
heterodoxy said:
Absolutely; in fact, if you have a PayPal (you can PM me), I'd like to buy you a beer or something. I appreciate your help over the holidays after I was feeling ignored (and at a certain point, ridiculed) for a couple days. We're developers, we play with things we're not supposed to, and sometimes that means we brick our devices. But I've certainly learned a lot.
Click to expand...
Click to collapse
I don't have a Paypal account at the moment but if I had I would donate this http://forum.xda-developers.com/member.php?u=2677399 for his nexushd2 roms. So if you want you can do this donation for me
Or you donate direkt to the flatline guys, as I said they are the true geniuses...
heterodoxy said:
I'm glad that worked for you! For the record I got a signature verification error when I tried to do this originally; some other users on the androidroot.mobi thread got one too. As mentioned, if you have issues flashing the bootloader with fastboot you can do it with nvflash --download 4; another user said this precluded using fastboot again in the future but I find that somewhat dubious.
Click to expand...
Click to collapse
I made download 4 many times for testing with my own backup of this partition. The first time it bricked my device. I made the backup with unlocked bootloader but flashed it back with locked bootloader... You should definetly make the bricksafe.img and a Backup of all Partitions before you flash on this... But after I bricked my device with that I was still able to boot with wheelie and the blob.
But for you I will try to flash an old bootloader on this part an see what happens
EDIT: the 4.3 (JWR66Y) Factory Image for nakasi has a broken bootloader. And if you try to flash it you will get a signature missmatch... (for that reason i recommed the 4.4.2 factory image) Maybe he only tryed to flash this bootloader... And I'm very angry on Google because this faulty bootloader is still online maybe you want to leave a Feedback on the download Page of the factory images: https://developers.google.com/android/nexus/images?hl=de#nakasijwr66y
EDIT2: I flashed bootloader 3.41 via nvflash. It worked and the bootloader booted. But as I tryed to flash the 4.23 from 4.4.2 (KOT49H) and got signature missmatch. But I could reflash the 3.41 again via fastboot now I will try diffrent bootloaders...
EDIT3: Bootloader 4.18 from 4.2.2 (JDQ39) works to... It seems there is something wrong with the 4.23 Bootloader google puts in it factory images...
EDIT4: Bootloader 4.23 from 4.4 (KRT16S) works but 4.23 from 4.4.2 (KOT49H) and 4.23 from 4.3 (JWR66Y) not...
Partitionator said:
The next command will flash a kernel (however without flashing a kernel it won't go to fastboot mode) and than bring set your device into fastboot mode. You have to hold vol- after/while hitting enter till its in fastboot mode. If you don't hold vol- it will boot to android and you have to start from the begining.
Code:
sudo ./nvflash --resume --download 8 boot.img --go
Now you should be in fastboot mode and the last step is very easy:
simply reflash the bootloader:
Code:
fastboot flash bootloader bootloader.img
or in case of the lastet bootloader
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
Now your device should be unbricked
Click to expand...
Click to collapse
Brilliant! Of course I missed the HOLD VOL- part the first time (bolding for everyone else ) and it booted straight into Android, but the fact that it could even do that filled me with glee. Did it again and it put me in the 4.13 bootloader. I flashed the 4.18 stock bootloader that had been on the device before and for some reason it said "Signature match." this time! Don't know why but not complaining!
These instructions should be stickied; we had a guide for getting the nvflash blobs but not for what to do with them, especially when wheelie doesn't work! (I did try --rawdevicewrite early on to flash bricksafe.img back and for some reason it didn't work, but these steps are even more intuitive.) Thanks for saving my life!
heterodoxy said:
Brilliant! Of course I missed the HOLD VOL- part the first time (bolding for everyone else ) and it booted straight into Android, but the fact that it could even do that filled me with glee. Did it again and it put me in the 4.13 bootloader. I flashed the 4.18 stock bootloader that had been on the device before and for some reason it said "Signature match." this time! Don't know why but not complaining!
These instructions should be stickied; we had a guide for getting the nvflash blobs but not for what to do with them, especially when wheelie doesn't work! (I did try --rawdevicewrite early on to flash bricksafe.img back and for some reason it didn't work, but these steps are even more intuitive.) Thanks for saving my life!
Click to expand...
Click to collapse
Read the last edits in my post before: many 4.23 Bootloaders are brocken and that is causing the signiture missmatch, because of that your 4.18 bootloader worked... You can use 4.23 Bootloader from the 4.4 Factory Image
But now the irony: it seems that I fullbricked my device with forcing a flash of a brocken bootloader via nvflash :S I can´t even enter the APX Mode it doesn´t shows up in any kind...
EDIT: Got APX Mode again
EDIT2: Oh you said 4.13 and not 4.23 Bootloader... Where did you get this bootloader from? I couldn´t find one with that version in a Factory image. Or did you used that modified Bootloader that was used to dump the blobs? Because that would make sense, this Bootloader is modified and so the Googles signiture is brocken
EDIT3: After testing all of the grouper factory-images (and indentifying the Bootloader from 4.3 and 4.4.2 as brocken I want to test ALL the OTA Updates from here: http://forum.xda-developers.com/showthread.php?t=1745781 First by flashing the bootloader it contains with fastboot, than flashing the whole OTA-Package over adb-sideload (of course I have to flash the corresponding Android Version before) and than via nvflash...
If you want you can help me, because I have to do things for school and so I don´t have more time for playig with bootloaders, but you should make a Backup of every bit of your device .
And every time I brick my device via flashing a brocken bootloader via nvflash I have trouble entering APX Mode....
EDIT4: I´m not able to enter APX Mode again... I feel just to dump to press two buttons...
EDIT5: I´m trying hard since a houre to get in APX Mode but nothing ;( - but why? APX must work, its in the ROM...
Partitionator said:
Read the last edits in my post before: many 4.23 Bootloaders are brocken and that is causing the signiture missmatch, because of that your 4.18 bootloader worked... You can use 4.23 Bootloader from the 4.4 Factory Image
Click to expand...
Click to collapse
I only ever tried to flash the 4.18 bootloader that was previously on the device. I knew there was a possibility others were broken as mentioned in the original thread. It gave me a signature mismatch before, it doesn't now. Again, I don't know why but c'est la vie.
Partitionator said:
But now the irony: it seems that I fullbricked my device with forcing a flash of a brocken bootloader via nvflash :S I can´t even enter the APX Mode it doesn´t shows up in any kind...
Click to expand...
Click to collapse
Oh no! As we just proved, that shouldn't be able to happen!
Partitionator said:
EDIT2: Oh you said 4.13 and not 4.23 Bootloader... Where did you get this bootloader from? I couldn´t find one with that version in a Factory image. Or did you used that modified Bootloader that was used to dump the blobs? Because that would make sense, this Bootloader is modified and so the Googles signiture is brocken
Click to expand...
Click to collapse
The one on the device (and I guess in bootloader.ebt) was the flatline 4.13 bootloader. I was trying to put 4.18 on top of it. I would think the signature mismatch would be done on the new bootloader not the existing one. But either way, flashing the exact same bootloader on top of the exact same bootloader works now.
Partitionator said:
If you want you can help me, because I have to do things for school and so I don´t have more time for playig with bootloaders, but you should make a Backup of every bit of your device .
Click to expand...
Click to collapse
Sure, I'll try to do that when I have time.
Partitionator said:
EDIT5: I´m trying hard since a houre to get in APX Mode but nothing ;( - buty whay APX must work its in the ROM...
Click to expand...
Click to collapse
I'm wondering if you're just in some really strange run state. Have you tried disconnecting the battery, leaving it disconnected for a minute, re-connecting it, and then trying to boot into APX mode again?