The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for Nexus 7 & Nexus 7 3G (2012)
This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.
As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Credit goes to the AndroidRoot.Mobi team:
Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.
BrianXP7 said:
Ah yes! This makes updating the bootloader a less scary procedure. (It happened to me and I had to send an RMA request. Fortunately, they accepted it.) I do have a question. Are the blobs hardware specific for the Nexus 7? (Flashing someone's Nexus 7 dump to mine.)
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The blobs are device-specific. They will only works on your particular device and no one elses.
Otherwise, we would have just released pre-made blobs
Hi! I have tried to nvflash my TF300T with the new guide, but after generating the blob.bin and run whille I am getting an error:
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2d4228340213
[-] Incorrect BLOB selected. nverror: 0x4.
Seems like the bootloader didn't flash the first time - after the second try and regenerating the nvflash files it works.
so the guide on androidroots website should be followed before you start tinkering with your device? just wondering. I have an N7, but have never messed it up to the point where fastbooting the factory image doesn't work. only killed it due to a hardware error
Can you still use this if you can only access the APX mode due to a bricked tablet?
BrianXP7 said:
[/COLOR]I successfully backed up the blobs and partition images. I'm happy someone finally found a unbrickable solution. However, I tried flashing back the stock bootloader (4.23) but it displayed "Signature mismatch." in red on the top left corner and failed. (Luckily, I can still interactive with the bootloader menu.) Would flashing a ZIP with the image inside work as a workaround? Is there a special procedure that I have to perform? Are you going to release a modified 4.23 bootloader?
Click to expand...
Click to collapse
Try flashing the bootloader with nvflash rather than fastboot, flashing the bootloader from fastboot and recovery is subject to a signature check.
BrianXP7 said:
Wouldn't that flash the modified bootloader? Also, I can't find instructions on flashing the bootloader under NVFlash.
Click to expand...
Click to collapse
if you have any bootloader you can flash it with nvflash easily. nvflash -r --download 4 bootloader.bin and it will flash, this isn't just limited to the stock bootloaders either, you can use this to attempt porting other bootloaders like u-boot.
BrianXP7 said:
I ran out of thanks... Thanks...
Edit: So I rename "bootloader-grouper-4.23.img" from the factory image archive to "bootloader.bin" or is it something else entirely? Just double checking before I screw any partitions...again.
Click to expand...
Click to collapse
doesn't matter what it is called I just used bootloader.bin as an example
Code:
nvflash -r --download 4 $filename
is probably the most appropriate way to represent it where $filename is whatever you called the bootloader
Does this mean with this we would be able to make a bootloader with custom splash screens??
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
Does this mean with this we would be able to make a bootloader with custom splash screens??
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
if you wanted you could try yes. not too sure about the format the current splash is though
lilstevie said:
if you wanted you could try yes. not too sure about the format the current splash is though
Click to expand...
Click to collapse
Hmmm. This is great work do you know if anyone on any of the other Asus devices have succeeded in changing the splash screen? That may be a good place to start looking. I shall look into this
Sent from my Nexus 7 using Tapatalk 4
BrianXP7 said:
I risked and I screwed up. It's not recognised anymore... Any other suggestions? I hate having to send another RMA request...
Click to expand...
Click to collapse
you should be able to still hit APX as that is not controlled by the bootloader
heavy_metal_man said:
Hmmm. This is great work do you know if anyone on any of the other Asus devices have succeeded in changing the splash screen? That may be a good place to start looking. I shall look into this
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Nope, but afaik it is a standard format across tegra devices, so maybe look up other tegra based devices as a starting point
lilstevie said:
Nope, but afaik it is a standard format across tegra devices, so maybe look up other tegra based devices as a starting point
Click to expand...
Click to collapse
OK cool, any ideas on where I can get a start on decompiling the bootloader to have a look at its internals?
Sent from my Nexus 7 using Tapatalk 4
BrianXP7 said:
This is probably going to annoy you a lot. I tried holding the power button for more than 30 seconds and doing weird button combinations but it still wouldn't get recognized. Should I try draining the battery? (I have a feeling it might take quite some time...)
Click to expand...
Click to collapse
I'm one of the only androidroot members who doesn't own an N7 so I will have to defer to one of the others for where to go, but I do believe one of them has ended up in a similar situation but managed to get out of it.
heavy_metal_man said:
OK cool, any ideas on where I can get a start on decompiling the bootloader to have a look at its internals?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
IDA would be the best place to start
I know how to install the 4.23 bootloader...
Step 1: Get into fastboot by... Well if you don't know how to get into fastboot then why did you do this???
Step 2: Get the unmodified 4.13 bootloader (attached as 413bl.img ) and flash it by using" fastboot flash bootloader 413bl.IMG"
Step 3: Reboot into bootloader using volume keys
Step 4: Flash the 4.23 bootloader (attached as bootloader-grouper-4.23.img )
Step 5: Reboot
Step 6: ???
Step 7: Profit
Remove the battery and try again...
BrianXP7 said:
Alright, thanks. I'll keep updated on this topic for the solution.
I became way too courageous... I actually need my tablet for school so please find it soon. (No pressure. )
Click to expand...
Click to collapse
Pop off the back cover using a guitar pick or fingernails and remove the battery cable and try to get into NVflash. If you don't know how to unplug the battery go onto ifixit and search for N7 disassembly
BrianXP7 said:
Alright, thanks. I'll keep updated on this topic for the solution.
I became way too courageous... I actually need my tablet for school so please find it soon. (No pressure. )
Click to expand...
Click to collapse
Code:
18:10 <@RaYmAn> you have to hold down uhm, all buttons or something for like 10 seconds, while it's plugged in
18:10 <@RaYmAn> and then you have to let go of power and voldown at *just* the right time
but make sure you charge the battery for a bit first with the charger in case the battery is starting to run low
lkspooky said:
Step 1: Get into fastboot by... Well if you don't know how to get into fastboot then why did you do this???
Step 2: Get the unmodified 4.13 bootloader (attached as 413bl.img ) and flash it by using" fastboot flash bootloader 413bl.IMG"
Step 3: Reboot into bootloader using volume keys
Step 4: Flash the 4.23 bootloader (attached as bootloader-grouper-4.23.img )
Step 5: Reboot
Step 6: ???
Step 7: Profit
Click to expand...
Click to collapse
Is this after you have generated blobs with the modified bootloader ?
i.e. after you have generated your blobs with the androidroot.mobi bootloader you flash standard 4.13 b/l and then afterwards 4.23 ?
Post blob generation
wildestpixel said:
Is this after you have generated blobs with the modified bootloader ?
i.e. after you have generated your blobs with the androidroot.mobi bootloader you flash standard 4.13 b/l and then afterwards 4.23 ?
Click to expand...
Click to collapse
This is after you generate blobs
Related
I rooted the galaxy tab using nvflash when it first came out in the US. With nvflash we can flash rooted roms and do full backups. I am trying the same process with the TP but I have ran into some issues. First issue was the drivers would not install. I added the TP device id then I installed the drivers. I tried nvflash --sync command but get a unkown device message. We need a updated nvflash that supports tegra 3. If anyone has an updated version of nvflash please pm me.
Thanks
Shep
Edit: I checked online and dev package for tegra platform from nvidia but could not find a updated version of nvflash that supports TP. Are device does have APX & nflash support(Vol+ then power button then hold both 15 secs then release).
might be interesting to try the sbkcheck from rayman
http://forum.xda-developers.com/showthread.php?t=1290503
(note: IIRC there was a modified version at androidroot.mobi that could check for a "v3" SBK as well).
its not a driver issue. the drivers that come with the latest version of NVflash are the drivers supplied by ASUS, BUT the PID/VID
try adding these lines to the NvidiaUSB.inf under the x86 and amd64 lines
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
then force uninstall any drivers (you may even go as far as installing old google ADB drivers) and then try installing the nvflash drivers (with the new lines added)
i was trying to do this, but i cant find my device in hardware list. like literally its not that hahah
This will give us the ability to flash roms right?
Sent from my Transformer Prime TF201 using Tapatalk
biggem001 said:
its not a driver issue. the drivers that come with the latest version of NVflash are the drivers supplied by ASUS, BUT the PID/VID
try adding these lines to the NvidiaUSB.inf under the x86 and amd64 lines
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
then force uninstall any drivers (you may even go as far as installing old google ADB drivers) and then try installing the nvflash drivers (with the new lines added)
i was trying to do this, but i cant find my device in hardware list. like literally its not that hahah
Click to expand...
Click to collapse
I already got the drivers working. Nvflash says unknown device whe you try to use the sync command. We need new version of nvflash.
Wordlywisewiz said:
This will give us the ability to flash roms right?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Yes you can edit system partition and flash with root or custom rom but flashing recovery & boot loader is the main goal.
shep211 said:
Yes you can edit system partition and flash with root or custom rom but flashing recovery & boot loader is the main goal.
Click to expand...
Click to collapse
Yes! Can't wait to root! I had root then it forced the update on me!
Sent from my Transformer Prime TF201 using Tapatalk
So if you have root then apply the OTA, it hoses root?
Sent from my Galaxy Nexus using XDA App
Superguy said:
So if you have root then apply the OTA, it hoses root?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
yep, it wipes the /system/ directory
I have same issue it says unknown device, we need a new EXE. Hope to get one soon.
I went into NVFLASH and saw that it takes the USB PID of the device, and that tells how the device is what it is. so the TP needs to be added to NVFLASH.. im seeing if i can do it be playing with the exe
here is an nvflash that supports cardhu(tegra 3), this is for linux, its all use so all i have, i just issued the --sync command and have not gotten an unknown device error, just getting nvflash started, then it just sits there.
i havent used nvflash really at all, im just used to fastboot and adb, but hopefully this helps and i dont have much time today or tomorrow at all to mess with it.
Linux users- in your rules.d(android-rules-whtever you want to make it) first line will get ADB working with the prime, second should allow it to be seen in APX mode:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
Edit after messing with some nvflash commands I get a "USB write failed" error, which after Googling tells me Asus has used an SBK(secure boot key), rendering nvflash useless(unless asus gives it to us-128 bit encryption). Basically locked, encrypted bootloader and were f#$ked.
I really hope I'm wrong.
You are not wrong unfortunately. It's the same with the first Transformer. The first SBK was leaked, but they changed it and the second one is still unknown as far as I know. It's a real shame, because nvflash provides a lot of safety (you can reflash even almost bricked device).
Dammit! Isn't this against Google s open source license or something?
Sent from my Transformer Prime TF201 using Tapatalk
di11igaf said:
Edit after messing with some nvflash commands I get a "USB write failed" error, which after Googling tells me Asus has used an SBK(secure boot key), rendering nvflash useless(unless asus gives it to us-128 bit encryption). Basically locked, encrypted bootloader and were f#$ked.
I really hope I'm wrong.
Click to expand...
Click to collapse
If this is true, I will return it on principle. I don't buy locked devices, which is why I will never buy Motorola
Wordlywisewiz said:
Dammit! Isn't this against Google s open source license or something?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Lol, no. Heck, HC source is still private.
Well when it becomes ICS's won't they have to let us do whatever we want with it?
Sent from my PC36100 using Tapatalk
Wordlywisewiz said:
Well when it becomes ICS's won't they have to let us do whatever we want with it?
Click to expand...
Click to collapse
No, Asus dont have to release the source to their proprietary software unfortunately. You can have the source for ics from google, but doesnt mean you can get it on your device!
I cant imagine this being a problem for long. Even iphones get jailbreaked after some time and Apple is known for their locked system. They probably have a whole department just for locking up and preventing jailbreaks.
I really cant imagine that Asus is doing a better job than Apple in that matter and making it impossible to do some magic with it.. It'll probably take some time though.
Is there a good channel to reach Nvidia or Asus with our demands? Crying loud enough worked with HTC after all
clouds5 said:
Is there a good channel to reach Nvidia or Asus with our demands? Crying loud enough worked with HTC after all
Click to expand...
Click to collapse
+ 1
Sent from my Transformer Prime TF201 using xda premium
WSG
WabiSabiGeeks
Latest ROM: WSG UnBricker V1.0.3
Last Update: July 16, 2012
Type: Tools
Wabi-Sabi: Finding the beauty in, and embracing the imperfect!
Perfect is repeatable. Imperfect is Perfect
PLEASE NOTE: I am not responsible for anything that happens to your device. This includes acts of God, your wife/girlfriend breaking it over your head for using it too much, or jealous iPhone owners!
I bring to you a tool to help UnBrick your Brick Prime. This should be used has a last resort.
..:: Description ::..
This is a Full Fastboot based solution that should allow you to flash any partition.
The IMG's used are blob signed, which our devices require.
..::Audience::..
Anyone who has flash stock rom, messed with the kernel, or can access fastboot.
**Please try DiamondBack thread before attempting to use this tool**
**Before using please install Universal Naked Driver**
**Big THANKS to Doktaphex for fastboot command**
Extract it somewhere like your desktop, though anywhere will work.
when i say extract it i mean use extract all so you get my file structure do not move these files or it will break
Run / double click WSGFlasher.bat
The script displays the readme at startup. close it and continue.
Select what function you want to do and press [ENTER]
Please be careful as to what file you drag and drop when it prompts you
One final note do not give it a file from another device or a non .img file it will flash it anyway no matter what file you drag and drop once you press enter it flashes what ever was dragged onto the script. Also do not drag a radio img when it asks for recovery or in revers, bad things will happen Wile they are fixable by repeating the process I dont want anyone to mess up their device making such a simple mistake.
Download Link: WSG UnBricker V1.0.3
MD5: e2bf785939e98b74737f7eb0ad9c2c78
..::ChangeLog::..
Code:
WSG_UnBricker V1.0.3
[LIST]
[*]Fixed Coding mistakes
[*]Using a couple diff methods to Un-Brick
[*]Default IMG base from Stock Rom 9.4.2.18
[/LIST]
WSG_UnBricker V1.0.2
[LIST]
[*]Fixed System IMG size
[*]Clean up Code
[*]Default IMG base from Stock Rom 9.4.2.15
[/LIST]
More to Come.....
Further, if I get any parts wrong, PM me and I'll get those parts corrected.
Android Partition, SPL etc.
Partitions:
Followings are a list of partitions on your ASUS Transformer Prime (TF201).
misc - misc partition -
recovery - Recovery Partition - This is where the original CWM recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition also known has kernel
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the tablet, this area is wiped)
So, if you replace the recovery image, you are pretty much set for updates provided here at XDA.
ROM images will normally replace boot and system images at the same time and often time, userdata and cache too; reseting the phone completely.
SPL/Bootloader/Bricking Tablets:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
How do I know the tablet is bricked? A bricked tablet can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked tablet via adb or fastboot. You can only see one screen on the tablet and it will be the first splash screen.
Can see this coming in use sometime, so thanks in advance for when I screw up my tab
Wow... now I could root my prime and keep it. I was afraid of bricking it.
great tool I never unlocked my prime b/c the half assed asus implementation but now I think I will as this will be like my last resort Insurance if i mess up, saying that I've never killed any of my other devices or had to revive them but some reason never felt confident with my prime.
everyone should be in here hitting thanks it deserves more attention
big thanks from me any way
**I bring to you a tool to help UnBrick your Brick Prime. This should be used has a last resort.
Cool beans man. Is this how you got your bricked Prime up and running?
jaycustom said:
**I bring to you a tool to help UnBrick your Brick Prime. This should be used has a last resort.
Cool beans man. Is this how you got your bricked Prime up and running?
Click to expand...
Click to collapse
Yes...
Sent from my SPH-D710 using xda premium
Is this for like a hard brick?
Sent from my Nexus S 4G using Tapatalk 2
Techno Droid said:
Is this for like a hard brick?
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
this is for bricks that can't be fixed using Diamonbacks brick thread.
MasterZen88 said:
Yes...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
My main man with the master plan! Thanks for making this Zen, this is one piece of your software I hope I won't have to use......
Sent from my Transformer Prime TF201 using Tapatalk 2
MasterZen88 said:
WSG
WabiSabiGeeks
Latest ROM: WSG UnBricker V1.0
Last Update: Apr 14, 2012
Type: Tools
Wabi-Sabi: Finding the beauty in, and embracing the imperfect!
Perfect is repeatable. Imperfect is Perfect
PLEASE NOTE: I am not responsible for anything that happens to your device. This includes acts of God, your wife/girlfriend breaking it over your head for using it too much, or jealous iPhone owners!
I bring to you a tool to help UnBrick your Brick Prime. This should be used has a last resort.
**Please try DiamondBack thread before attempting to use this tool**
**Before using please install Universal Naked Driver**
Extract it somewhere like your desktop, though anywhere will work.
when i say extract it i mean use extract all so you get my file structure do not move these files or it will break
Run / double click WSGFlasher.bat
The script displays the readme at startup. close it and continue.
Select what function you want to do and press [ENTER]
Please be careful as to what file you drag and drop when it prompts you
One final note do not give it a file from another device or a non .img file it will flash it anyway no matter what file you drag and drop once you press enter it flashes what ever was dragged onto the script. Also do not drag a radio img when it asks for recovery or in revers, bad things will happen Wile they are fixable by repeating the process I dont want anyone to mess up their device making such a simple mistake.
Download Link: WSG_UnBricker V1.0
MD5: a71c8d24307a185145cb329e8f7d6c3e
Click to expand...
Click to collapse
I am very intrigued, could you please post more about exactly what this tool does, as your description is rather vague, to a certain extent.
Thank you for this tool. It's great to have so many great developers on the Prime. (and people said there would be no development because of it's secret sauce)
Doktaphex said:
I am very intrigued, could you please post more about exactly what this tool does, as your description is rather vague, to a certain extent.
Thank you for this tool. It's great to have so many great developers on the Prime. (and people said there would be no development because of it's secret sauce)
Click to expand...
Click to collapse
Yep, those people were wrong...haha
Basically this is a full fastboot solution that should be able to flash any partition on your tablet via a USB host. I used this method to recover my own tablet.
Please check out OP of more information.
Doktaphex said:
I am very intrigued, could you please post more about exactly what this tool does, as your description is rather vague, to a certain extent.
Thank you for this tool. It's great to have so many great developers on the Prime. (and people said there would be no development because of it's secret sauce)
Click to expand...
Click to collapse
Really I own you credit for figuring out the proper fastboot command "fastboot -i 0x0b05". I'll add it to OP!!! Thanks
Really nice script Zen!
Sent from my EPAD using Tapatalk 2
MasterZen88 said:
Really I own you credit for figuring out the proper fastboot command "fastboot -i 0x0b05". I'll add it to OP!!! Thanks
Click to expand...
Click to collapse
Hey! It wasn't me who figured that command out. I assume it was someone at androidroot.mobi or elsewhere. I mearly stumbled upon it with open arms. But thanks anyway.
If we can find out who first figured out that command then I'll be able to update my thread also.
If you have downloaded the WSG Unbricker please don't use it yet. I just realized once you unbrick, it will take you to stock .21 with NO ROOT access. I am currently in the process of fixing this and should have a new link up in about two hours.
Allmywut.jpeg
Now anything can be unbricked?
Devs here are scary how fast they can produce quality work.
Fixed. IT now gives you the option to flash your own img's or flash WSG Beta rom.
So, would this unbrick if you tried to flash a stock Asus Blob file via CWM (the type 2 Brick)? I have not bricked myself, but this seems to be the only hard brick method so far that can't be fixed.
Thanks for putting this together, you make people like me who are spoiled by Samsung and ODIN feel more comfortable with unlocking their devices.
Apologies for the noob question....
I have everything installed as per instructions, but your tool cannot communicate with my TFP since I cannot boot to bootloader (Unrecoverable bootloader error (0x00000004)).
Am I correct in assuming that this fix is not for me?
So, now it has caught me. Been careless when flashing the new version of TWRP and I've shot the Prime. Googled 6 hours and read and it seems indeed to be a hard brick. I'm not into recovery still in fastboot. Only the APX mode and it is also recognized by the PC. But I can not communicate with the PC with the Prime to revive it. All rescue proposals Netzt go with me not because you need to either fastboot or recovery. Also, I have no backup on NVFLASH because I did not know. Should really be the only way fit on Asus for 300 € a new motherboard if it were to allow the well worthwhile anymore. Since the device has a hardware defect but yes it is a software problem, yes, there ought to be some way. But unfortunately I have not found the solution.
follow this thred. You can download factory blobs and restore the 4 main partitions.
gophix said:
follow this thred. You can download factory blobs and restore the 4 main partitions.
Click to expand...
Click to collapse
Gophix, I have read you post the same sort of solution to what you think is the same problem on a few threads in the last few hours and you are wrong mate.
These people do not have blob files created by doing the nvflash process while on ICS. Using a blob file from a stock image is not the same as you need the boot.blob created by doing the nvflash process to even access wheelie and use nvflash.
I think you need to read up a bit more before advising people or at least test it yourself first.
gophix said:
follow this thred. You can download factory blobs and restore the 4 main partitions.
Click to expand...
Click to collapse
thx, but i've the Jellybean bootloader and so it ist not possible to do :crying:
sorry bavmouse. Like flumpster said - I have to read more attentive.
my prime is dead
bavmouse said:
my prime is dead
Click to expand...
Click to collapse
So you can confirm that you have no access to fastboot mode on the prime ?
marko! said:
So you can confirm that you have no access to fastboot mode on the prime ?
Click to expand...
Click to collapse
no fastboot, no recovery
bavmouse said:
no fastboot, no recovery
Click to expand...
Click to collapse
the nwithout the required NvFlash backup files there is not much that you can do.
marko! said:
the nwithout the required NvFlash backup files there is not much that you can do.
Click to expand...
Click to collapse
i know :crying:
bavmouse said:
i know :crying:
Click to expand...
Click to collapse
I'm sorry for your loss. Its never good to lose a device. You may be able to send it away to get fixed for a price. When i have some free time i would gladly go over 1 on 1 with you to see if there is any hope . just PM me
Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?
Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
arshileus said:
Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
Click to expand...
Click to collapse
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Davey126 said:
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Click to expand...
Click to collapse
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
arshileus said:
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
Click to expand...
Click to collapse
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Tossing out a few clarifications for future readers:
Yousucks2 said:
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
Click to expand...
Click to collapse
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yousucks2 said:
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
Click to expand...
Click to collapse
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
Yousucks2 said:
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Click to expand...
Click to collapse
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Davey126 said:
Tossing out a few clarifications for future readers:
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Click to expand...
Click to collapse
Can you show me any guidelines to understand how hard is it....
arshileus said:
Can you show me any guidelines to understand how hard is it....
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Not sure...
Davey126 said:
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Click to expand...
Click to collapse
This will only work if adb or fastboot can still connect,
but in that case I'd suggest to try 1-Click pre-release to
click through a web-UI. No reading required... (-;
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot? I suspect that flashify (or the OP) did more than just overwrite recovery, which can be _really_bad_ if the bootloader is still locked, since the key combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
In my experience 'yes' to boot although there are obviously exceptions including those running FireOS with a custom recovery on a locked (but still vulnerable) device. Whether the stock recovery contents are actually used or something else happens is unknown...at least to me. Symptom wise a borked recovery is almost always leads to boot issues.
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
Seems the issue I'm experiencing
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
arshileus said:
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
Click to expand...
Click to collapse
Same thread as previously linked (here). It is NOT a step-by-step idiot proof guide. You will need to do some advance reading. Suggest digesting the OP then reviewing the last 2-3 months of posts to get a 'feel' for what is required and the questions you may have.
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
arshileus said:
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
Click to expand...
Click to collapse
Can you help me?
arshileus said:
Can you help me?
Click to expand...
Click to collapse
Could be a borked device, unstable usb interface (either device) or bad cable. Work backwards by trying different cables, different ports on the host (avoid USB3 and hubs) and different hosts. If results are the same you may have a bad device. Good luck.