Database Users

Help me port CWM Recovery to my tab! VZW SCH-I705

Hi all,
I've got a VZW G Tab 2 7.0 Got it rooted and now looking to port CWM over to it.
I found This guide to port cwm, however he states it won't work for Samsung devices. I also attempted using the Recovery Builder with no luck. It wouldn't boot into CWM at all.
My question is.. can somebody give me some tips on how to port CWM to my tab? I've got some experience with programming/scripting/linux, but no idea where to start!
Thanks in advance

That guide is old, so it should work for Samsung devices now. Back in the days of the original SGS phones, it didn't due to a different recovery/kernel setup. If you can pull the boot.img and recovery.img from the tablet, it should be relatively easy to get it to work. Seeing as people have rooted the I705, that should be easy enough to do.

Ah ok that's good to know. I have already pulled all of the stock partitions for my own keepsake. I'll do what I can. Thanks man.

Well I followed the guide to exactly and got a recovery.img.. same result as I had using the 'builder'. The device reboots, little blue words saying 'recovery booting'. Screen goes black, then lights up with black background, flashes once, then reboots normally.
recovery.fstab has the correct values for this tab.
Code:
/boot emmc /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p14
/data ext4 /dev/block/mmcblk0p15 length=-16384
/cache ext4 /dev/block/mmcblk0p17
/recovery emmc /dev/block/mmcblk0p18
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/mmcblk0p11
/modem emmc /dev/block/mmcblk0p1
Would a locked bootloader prevent a CWM from booting? How would I tell if it is? In 'download mode', in the top left corner it says the following:
ODIN MODE
PRODUCT NAME: SCH-I705
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: Enabled
Then in the middle of the screen it says 'Downloading.. do not turn off...'
Don't know if this means the BL is locked or not, though.
My recovery.img download
If anyone want's me to post any more info let me know.
EDIT: What else needs to be done to build a successful recovery? I hardly think it's as easy as it is in the guide.. though I could be wrong.

http://forum.xda-developers.com/showpost.php?p=31671148&postcount=21 No feedback? Fail?

ketut.kumajaya said:
http://forum.xda-developers.com/showpost.php?p=31671148&postcount=21 No feedback? Fail?
Click to expand...
Click to collapse
Didn't notice that! I stopped following since It seemed the others did as well. Yes... fail. I'll check that out.
I'd like to know more about the process, though. So my questions still stand

I have my own scripts to unpack and repack boot.img or recovery.img using unpackbootimg and mkbootfs tools. What I've done:
1. Unpack yours stock recovery
2. Add CWM's /res/keys contents to yours recovery /res/keys
3. Repack the recovery
Code:
$ unpackbootimg.sh recovery.img
Edit /res/keys
Code:
$ repackbootimg.sh recovery.img

I'm getting the same reboot issue after trying to access recovery using yours. :/

If the SGS3 for Verizon is any indication, it may very well be that the Verizon GTab2 has a locked bootloader, which doesnt allow unsigned recovery images. You were doing the right steps to test though.
Here is my suggestion (I don't own this tablet, but im trying to see if I can help you out)
First, Use the image you built using recovery builder
open odin
uncheck "Auto Reboot"
Flash your Recovery Image
Make sure it didnt say "Failed" under Message, if it did, its probably locked. If not, read on
At this point, close Odin, but leave your tab attached to the PC
Hold down the power button until you get the "battery charging" image
Unplug from the PC
Hold Volume Up + Power until the first Samsung Splash appears then let go
See if CWM loads
Once you exit, CWM SHOULD tell you that ROM will overwrite it, if you want to fix that, pick Yes
You now have CWM (crossing fingers)
report back and let me know

It failed.. so I'm assuming it is locked then..

MrHyde03 said:
ODIN MODE
PRODUCT NAME: SCH-I705
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: Enabled
Click to expand...
Click to collapse
I haven't used a Qualcomm chipped device, but I'm going to guess that the above highlighted part is your issue. Until that says "Disabled" you get to have fun with whatever VZW gives you and nothing more.

Well my gs3 says that also and i have the bootloader unlocked. Both devices show it greyed out.

Being that its Verizon I will go ahead and say its locked. That means unless someone finds an exploit you won't get a custom.recovery to work.
Sent from my DROID X2 using xda premium

Yeah... that's what I was afraid of.. had high hopes though! I may never be able to crack it myself... but I'm not gonna give up. Besides, gotta learn somewhere so what better place to start. I'll probably start off by studying the gs3 unlock... seems sensible. Anyone have some tips for a noob 'developer'?

MrHyde03 said:
Yeah... that's what I was afraid of.. had high hopes though! I may never be able to crack it myself... but I'm not gonna give up. Besides, gotta learn somewhere so what better place to start. I'll probably start off by studying the gs3 unlock... seems sensible. Anyone have some tips for a noob 'developer'?
Click to expand...
Click to collapse
If you don't know where to start, I wouldn't start with the bootloader. Also, the best person to talk to would probably be Adam Outler. As far as I know, the unlocked VZW SGS3 is because they got lucky and someone sent them, or someone found, an unlocked bootloader that could be flashed to the device.

I was reading through the original s3 bootloader thread and they were saying that even with the bootloader locked, you would still be able to load a recovery and flash TW roms etc. /boot is encrypted and /recovery is not. That still prevents ODIN flashes, but not using dd from ADB. If this device is anything like the s3 (which so far as I, it is) than the same *should* apply here.
Most of the attempts I've had were from ADB using dd. Any truth to this? I don't care to have custom kernels or even CM10. Just would like to make backups and I'd like to get started with ROM development.
I kinda believe my recovery is NOT encrypted/locked because if it was I'd assume I'd get that nasty VZW Warning screen which I don't.. thus I should be able to load custom recoveries.

You still would need an exploit in order to even attempt a custom recovery. Pretty much anything out of Verizon will be locked even the sgs3 needed an exploit in order to load recovery I be leave. Your best bet as mentioned before would be to contact one of the experienced devs to see if they can help.
Sent from my GT-P3113 using xda premium

I don't think there needs to be an exploit for recovery. I've been reading up on all the original dev on that device and there were recoveries before it was unlocked.

I tryed these steps. Now I have a brink device that won't even turn on at all.. I have tryed everything I can.. Does anyone have any clues how to get this thing back up and running..

What steps? This isnt a tutorial and there currently isnt a working recovery for this tab.
Im currently compiling another one with some modifications. We'll see..
Sent from my SCH-i705 using xda app-developers app

[Q] My A500 Bricked itself...literally...

Hi guys,
I'm not new to the xda forum, used it for ages for bits of info and things and as a result successfully rooted an Orange Barcelona and an Alcatel One, but the problem I have has made me sign up to ask
My A500 was happily playing some music in my bedroom while I was in the bath, when I came out it had switched itself off. Odd I thought, so I tried to turn it on and it got stuck with the flashing android logo. Again odd, so I attempted a reset, same thing, tried a factory rest and got a bootloader error, poo I thought, must have done some wierd update and broke its bootloader.
So starts an ENTIRE day of searching the xda forum looking for a way to unbrick the thing.
So first thing, do I have APX mode - yes.
Do I have an SBK and UUID - no, thats a problem.
So, i've been through ALL these threads, meticulously...
http://forum.xda-developers.com/showthread.php?t=1829731
http://forum.xda-developers.com/showpost.php?p=23783875&postcount=9
http://forum.xda-developers.com/showthread.php?p=32464439
http://forum.xda-developers.com/showthread.php?t=1585907
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
http://forum.xda-developers.com/showthread.php?t=1998650
http://forum.xda-developers.com/showthread.php?t=1762991&page=2
Blackthunders flash tool causes the tab to disconnect and doesn't flash.
V8-UNL-ICS-HC-bootloader-MULTI-cwm generates an error (usb write fail) and causes the tab to disconnect.
I've determined that SBCALC is not generating the correct SBK from the UUID generated by eppeP's apx code. I compiled it several times on a 32bit Ubuntu 13.04 system and again on an 64bit Ubuntu 13.04 system altering this line of code to reflect the relevent OS
printf("uid: %#016lx\n", *(uint64_t*)data);
In one of the threads i found eppeP had offered three versions. The 32bit lines generated UUID's that were too long, the 64bit line generated the correct length but caused the flash tools to fail. I've tried omitting the preceding 0x SBKCalc says check CPUID or just leaving off the 0, that gives me an SBK but still causes the tools to fail, so again, I think it isn;t generating the correct SBK or the apx tool by eppeP isn't retrieving the correct CPUID.
Throughout the whole day I managed to get the tab to factory reset ONCE, got it to boot, got as far as entering my WIFI PSK then it crashed and went back to 'i'm not going to boot so nah nah' mode.
So status is, tab powers and hangs with the Acer logo, and still has APX mode available.
What, if anything, can any of you wonderful people offer as a next step short of calling Acer Monday and paying silly amounts of money for them to unbrick it. (Amusing anecdote, this is my second A500, it was a replacement for a unit I sent in for repair which came back bricked BY ACER.....)
I'm tearing my hair out now, so help greatly appreciated.

Wee update,
Successfully got a working CPUID and SBK by building eppeP's Visual Studio project, had to update it to VC++2012 libraries as I have Visual Studio 2012 Ultimate through my university.
Trying to flash now, so far I've got a wee message saying nvflash started and nothing else, been sat for a good 2 minutes, is it supposed to go faster?

Kess_Tacy said:
Wee update,
Successfully got a working CPUID and SBK by building eppeP's Visual Studio project, had to update it to VC++2012 libraries as I have Visual Studio 2012 Ultimate through my university.
Trying to flash now, so far I've got a wee message saying nvflash started and nothing else, been sat for a good 2 minutes, is it supposed to go faster?
Click to expand...
Click to collapse
Do u have an apx device listed in device manager or safely remove Hardware icon???
I'd say you'll need to d/ babsector.rar to reset yr partitions. Usually its the only thing that works when yr tab has spontaneously bricked itself. You can get the file and instructions from post #2 of the root guide n my sig...probably the only thread u never posted above
good luck
dibb
Sent from my GT-I9300 using Tapatalk 4

All good with device manager, device is seen ok.
RIght, with BabSector, I get failure to read/write mass storage (code: 9) nverror: 0x8 (0x19000008).
I believe this indicates a physical problem with the internal sdcard requiring a motherboard replacement.
Well, that sucks but I've had this two years so I guess it's had a fairly decent run

Kess_Tacy said:
All good with device manager, device is seen ok.
RIght, with BabSector, I get failure to read/write mass storage (code: 9) nverror: 0x8 (0x19000008).
I believe this indicates a physical problem with the internal sdcard requiring a motherboard replacement.
Well, that sucks but I've had this two years so I guess it's had a fairly decent run
Click to expand...
Click to collapse
I got around this very same problem with Timmy Deans solution. Because of the bad blocks of memory, this was the only way I was able to solve. I don't remember which bat file I used. There were two, depending on whether you were doing single or dual partition. But the limitation was that BCT partition that was being format was larger than available. Once I used his script it worked and my brick A500 is still working well today.

EDIT: @Kess_Tacy
could try contacting acer...someone else just recently had some joy with them. They paid shipping both ways and repaired for free!! Worth a shot

[Q] Is my tablet beyond hope?

For the last two weeks, I've tried pretty much everything I can think of to get my TPT booted again. Symptoms of its current illness include:
Lots of error messages when booting into CWM recovery ("E:Can't mount /sdcard" for example)
If I attempt to boot normally, I get stuck on the Lenovo logo screen.
Randomly I'll boot into CWM recovery and get its logo on the screen, and a line of text, but no menus.
Other times I'll attempt to boot into CWM recovery, and just get a blank screen
So last night I used nvflash to put a new CWM recovery into partition 6: after which I was able to boot into CWM with no errors. (Yay) However, when I tried to reinstall CynogenMod (whose zip file was sitting on my external sd card), it hung during the installation. I rebooted anyway; this time it got as far as the CyanogenMod spinning logo and hung there. I went to bed, and seven hours later it was still spinning away.
Then I rebooted into CWM (without errors) and managed to install CM ROM this time also with no errors. However, again I can't boot. I get as far as the Lenovo logo, and if I boot into CWM recovery I have all the mount errors again.
Along the way I've erased the cache; done a factory reset, etc.
So: nvflash, new CWM recovery (but still errors), reinstalled CM ROM, but can't boot into it.
Any suggestions? Has this machine packed it in - is its hardware faulty in some way? Or is there something I could try which I haven't already?
Thanks folks - I think I've reached the limits of my fixing ability, and would be very gratefiul of some advice.
Thanks again,
Al

In CWM check to see if your /System folder is mounted with read-write privileges or only with read-only. If the former, then your bootloader may have locked itself. Also, what is your device model? If you have a have a US device then it cannot be unlocked as it has been encrypted by Lenovo...
Sent from my ThinkPad Tablet using Tapatalk

Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.

amca1960 said:
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
Click to expand...
Click to collapse
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...

eKeith said:
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
Click to expand...
Click to collapse
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.

amca1960 said:
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
Click to expand...
Click to collapse
No offense intended but you are somewhat peculiar as you are familiar with NVFlash, can determine which partitions to flash with the correct images but you don't have a record of, or can't find your device's model number? Check on your SD Card port flap (or your invoice). Then check out this page for details.
However if you decide to replace the motherboard then search eBay for "thinkpad tablet motherboard" and choose either of the 1838 or 1839 options. Any will fit and work but you probably won't get your (non-US) choice of replacement motherboard so will probably just have to get what's available.
See here for some basic dis-assembly instructions. Then just take you time and the rest will be obvious. Good luck!

Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?

amca1960 said:
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
Click to expand...
Click to collapse
No problem at all.
"I'm in the same boat": I replaced my motherboard with another US version about 6 weeks ago, rooted, installed CWM recovery and steady so far... "with fingers crossed"...
Let us know how it goes...

[Q&A] Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G)

Q&A for Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Where do saved files go?
Hello,
Before I bricked my N7 - I saved off all files per the instructions.
After the 'accident' - I can't find the files.
Can you tell me some of the usual locations that I can look - they are not under the \program files...\dir.
The tool told me the files had been saved off before I proceeded - I didn't double-check at the time since I thought all was well.
=== (from another post)
N7 Bricked
Hello,
My N7 bricked as well - stuck in APX mode. Don't know if the SBK is based on the CPU ID or not, and what the correct algorithm would be to recover it.
I did do a backup with NRT before all of this happened - but I can't seem to find those files at the moment.
I also got the 'too many links' message when I tried to flash the N7. It tried to boot; appeared to be running fine; and then did a screen blank; looked like one of the old
b&w TV's.
I did find the following mentioned elsewhere on this site - and I think it describes what may have happened when I was trying to get my N7 out of the infinite boot loop.
==
...the newly flashed BOOTLOADER inherits the crypto-signed details of the pre-existing BOOTLOADER, which exists (or FASTBOOT wouldn't work) and is 'tied' to that specific Nexus 7 via a unique ID.
But if the flash goes wrong, say as a result of a bad USB connection... the old BOOTLOADER is partially/wholly erased, the replacement may successfully flash, but FAILS to acquire the SECURE BOOT KEY (SBK) from the old BOOTLOADER.
The new BOOTLOADER then fails its crypto-sign in check against the Nexus 7's unique device ID when the device is next booted...
===
I did ask NVidia about this - they said I have to talk to ASUS. I have done that and they want $100 for the RMA. Since I got this N7 at the ESC 2103 Android Seminar/Certification Class -
I wonder if it'll cost more to fix once ASUS gets it.
Does anyone know how the SBK is generated for the N7? I get this with nvflash:
e:\NVPACK\Android_OS_Images\Pluto\android_k_pluto_ os_image-17.0r0>nvflash.exe --wait --bct
flash_encrypt_encrypt_encrypt.bct --setbct --odmdata 0x40098008 --configfile flash.cfg --
create --bl bootloader_encrypt.bin --go
Nvflash 3.10.1700 started
chip uid from BR is: 0x0000000000000000015d28569018120c
rcm version 0X4
Command send failed (usb write failed)
I encrypted bct and bootloader_encrypt.bin with this SBK:
0x76B66E00 0x6B991000 0x6362F302 0x9C266D03
but I do not know if that is accurate.
Does NRT have the capability to save off the SBK someplace? Just wondering.
===== talked to ASUS today - they want $200 for the RMA.
Thanks in advance,
jwestmoreland

jwestmoreland said:
Hello,
Before I bricked my N7 - I saved off all files per the instructions.
After the 'accident' - I can't find the files.
Can you tell me some of the usual locations that I can look - they are not under the \program files...\dir.
The tool told me the files had been saved off before I proceeded - I didn't double-check at the time since I thought all was well.
Click to expand...
Click to collapse
The files are saved onto your device, the instructions we provide then tell you to grab those files off your device and store them somewhere safe.
jwestmoreland said:
...the newly flashed BOOTLOADER inherits the crypto-signed details of the pre-existing BOOTLOADER, which exists (or FASTBOOT wouldn't work) and is 'tied' to that specific Nexus 7 via a unique ID.
But if the flash goes wrong, say as a result of a bad USB connection... the old BOOTLOADER is partially/wholly erased, the replacement may successfully flash, but FAILS to acquire the SECURE BOOT KEY (SBK) from the old BOOTLOADER.
The new BOOTLOADER then fails its crypto-sign in check against the Nexus 7's unique device ID when the device is next booted...
Click to expand...
Click to collapse
The newly flashed bootloader doesn't inherit anything. The bootloader is encrypted with the SBK during the flashing process. The SBK is handled at a lower level (from bootrom) and is actually a hardware security feature.
There is also no "partial flashing" that occurs. A blob has integrity checks (signatures) which are ignored when using flatline and checksums (not ignored ever) before a flash begins. Usually if the sigcheck fails the bootloader will not flash. Our secret sauce means this signature check never happens, but before a blob is flashed its checksum is verified. This remains in tact even with our methods, and we would never ignore it because it is pretty reckless to allow such a dangerous operation to occur without safeguards.
If a bad upload due to say a bad usb connection occurred the device would reject the image and not flash it. Also as explained before the SBK is not acquired by the new bootloader. The SBK is burned into a one time programmable e-fuse.
jwestmoreland said:
I did ask NVidia about this - they said I have to talk to ASUS. I have done that and they want $100 for the RMA. Since I got this N7 at the ESC 2103 Android Seminar/Certification Class -
I wonder if it'll cost more to fix once ASUS gets it.
Click to expand...
Click to collapse
Of course they did. nVidia are the chip manufacturer not the ODM. They provide guidelines for the ODM's to integrate nvflash for recovery and bringup but ultimately once they have sold the chip to ASUS it is up to them to implement and no longer in nV's hands.
jwestmoreland said:
Does anyone know how the SBK is generated for the N7?
Click to expand...
Click to collapse
No. nVidia supply a set of guidelines but whether or not they were followed we do not know. For instance the Acer Iconia A500 used an algorithm based off the chipid which leaked .
jwestmoreland said:
I get this with nvflash:
e:\NVPACK\Android_OS_Images\Pluto\android_k_pluto_ os_image-17.0r0>nvflash.exe --wait --bct
flash_encrypt_encrypt_encrypt.bct --setbct --odmdata 0x40098008 --configfile flash.cfg --
create --bl bootloader_encrypt.bin --go
Nvflash 3.10.1700 started
chip uid from BR is: 0x0000000000000000015d28569018120c
rcm version 0X4
Command send failed (usb write failed)
I encrypted bct and bootloader_encrypt.bin with this SBK:
0x76B66E00 0x6B991000 0x6362F302 0x9C266D03
but I do not know if that is accurate.
Click to expand...
Click to collapse
Just picking a random sbk is futile. There are 6.27 * 10^57 possible keys. The chances of picking it at random are very very slim. the 0x4 error is because when you encrypt with the wrong key the bootrom will not have a bar of it and shuts down the USB port. Also bct and bootloader are not enough. There is a first stage bootstrap which also requires encrypting. The process is rather complicated.
jwestmoreland said:
Does NRT have the capability to save off the SBK someplace? Just wondering.
Click to expand...
Click to collapse
No

I've seen discussion of this as well - the 'too many links' error or message popped up when using NRT - I've seen posts that said it was nothing to worry about - but
I guess in this case it did appear to be something to worry about.
The N7 did boot the new image - all looked fine for a few minutes. The screen did one of those things that looked like an old B&W TV losing the channel - then poof. The N7 was in APX/brick mode.
Have you heard of anything like that happening?
Oh, and ASUS wants $200 - not $100. The $100 is apparently just for a battery fix. They will swap the MB for $200. A new N7 can be ordered off of Amazon cheaper than that - plus a new (or used)
MB can be acquired via eBay for much less than that.
lilstevie said:
The files are saved onto your device, the instructions we provide then tell you to grab those files off your device and store them somewhere safe.
The newly flashed bootloader doesn't inherit anything. The bootloader is encrypted with the SBK during the flashing process. The SBK is handled at a lower level (from bootrom) and is actually a hardware security feature.
There is also no "partial flashing" that occurs. A blob has integrity checks (signatures) which are ignored when using flatline and checksums (not ignored ever) before a flash begins. Usually if the sigcheck fails the bootloader will not flash. Our secret sauce means this signature check never happens, but before a blob is flashed its checksum is verified. This remains in tact even with our methods, and we would never ignore it because it is pretty reckless to allow such a dangerous operation to occur without safeguards.
If a bad upload due to say a bad usb connection occurred the device would reject the image and not flash it. Also as explained before the SBK is not acquired by the new bootloader. The SBK is burned into a one time programmable e-fuse.
Of course they did. nVidia are the chip manufacturer not the ODM. They provide guidelines for the ODM's to integrate nvflash for recovery and bringup but ultimately once they have sold the chip to ASUS it is up to them to implement and no longer in nV's hands.
No. nVidia supply a set of guidelines but whether or not they were followed we do not know. For instance the Acer Iconia A500 used an algorithm based off the chipid which leaked .
Just picking a random sbk is futile. There are 6.27 * 10^57 possible keys. The chances of picking it at random are very very slim. the 0x4 error is because when you encrypt with the wrong key the bootrom will not have a bar of it and shuts down the USB port. Also bct and bootloader are not enough. There is a first stage bootstrap which also requires encrypting. The process is rather complicated.
No
Click to expand...
Click to collapse

Error 3 on wheelie command
Code:
C:\Users\Anton\AppData\Local\Android\android-sdk\platform-tools\nvflash-tools-wi
n32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d4a8220240205
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error 3 sending command
My device bricked by itself when I was just transferring a big file from my tablet to PC. I backed up my blob files months ago and now im stuck with this.

@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img

nervChris said:
@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img
Click to expand...
Click to collapse
hey hello, sorry for the late answer, but it doesn't matter as whatever i try to flash ends up in a FAILED <FileWriteFailed> message (bootloaders, recoverys, stock images etc ... )

nervChris said:
@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img
Click to expand...
Click to collapse
the problem is that i cannot flash anything, i always get a FileWriteFailed

[Q] Bricked Nexus 4

Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.

Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?

audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.

Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.

From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.

audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:

Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.

audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?

This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.

audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.

tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.

nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.

tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service