Please forgive me that im witing this in the DEVS section,
however please don't critic/blaming me or telling that it is impossible to be done.
I know that programming and/or pushing file via APX mode it's POSSIBLE! if NVFLASH can do this so there a way to get it done manualy.
and about the .blob files that NVFLASH[wheelie] needs is truley possible to get it by your self even in hardbrick.
all i want to know it's how?!
what exactly the goal/mean of wheelie? how can i unbrick my tf201 whithout NVFLASH? and if with NVFLASH how can i do it without wheelie?
and please don't tellme that it's impossible.please.
---
furthermore, in the samsung I9000 thereno way to hear something like "sorry you are unlucky, get a RMA num'" the devs of i9000 trying to help andmake new things and ways. why TF201 don't have something like a JIG[301K RES]? why don't we have TJAG or something?!?!?!?! i think we have to learn from them.
ApresVu said:
Please forgive me that im witing this in the DEVS section,
however please don't critic/blaming me or telling that it is impossible to be done.
I know that programming and/or pushing file via APX mode it's POSSIBLE! if NVFLASH can do this so there a way to get it done manualy.
and about the .blob files that NVFLASH[wheelie] needs is truley possible to get it by your self even in hardbrick.
all i want to know it's how?!
what exactly the goal/mean of wheelie? how can i unbrick my tf201 whithout NVFLASH? and if with NVFLASH how can i do it without wheelie?
and please don't tellme that it's impossible.please.
---
furthermore, in the samsung I9000 thereno way to hear something like "sorry you are unlucky, get a RMA num'" the devs of i9000 trying to help andmake new things and ways. why TF201 don't have something like a JIG[301K RES]? why don't we have TJAG or something?!?!?!?! i think we have to learn from them.
Click to expand...
Click to collapse
It doesn't belong in dev section. Telling people to not critique you for posting it in the wrong place does not make it any more dev related.
IF there is a way to do these things, I assure you, they would be out there. Wheelie obviously does some magic stuff to even be allowed to use nvflash, and I wouldn't expect anyone to ever find a way no involving generating device specific blobs as we do.
JIG is device-specific. Samsung explicitly created it for recovery purposes - there's no reason to think asus would include something similar.
JTAG is disabled on all production fuses Tegra devices, so there's really no way to get access to that (Even if you get access to the pins, it would just refuse access.)
all i want to know it's how?!
Click to expand...
Click to collapse
Seriously? You just want the holy grail handed to you and then you'd magically dev it?
I agree with what rayman says... rayman & the other folks at AndroidRoot have done us wonders with wheelie to enable nvFlash for our devices...
The truth of the matter is... you need to start by getting you basics right...nvFlash is the low-level utility for nVidia based devices & chipsets... I've used a Tegra 2 device before (GTablet) which was pretty much open and nvFlash worked out of the box... Here, however, Asus locked down things with very few ways to circumvent things...
With the information & knowledge available, wheelie is the only way to get nvFlash working.... why don't you read this amazing article written by the AndroidRoot team and understand the technicals of the situation.... http://androidroot.mobi/technical/tf-secure-boot-key/
craigacgomez said:
I agree with what rayman says... rayman & the other folks at AndroidRoot have done us wonders with wheelie to enable nvFlash for our devices...
The truth of the matter is... you need to start by getting you basics right...nvFlash is the low-level utility for nVidia based devices & chipsets... I've used a Tegra 2 device before (GTablet) which was pretty much open and nvFlash worked out of the box... Here, however, Asus locked down things with very few ways to circumvent things...
With the information & knowledge available, wheelie is the only way to get nvFlash working.... why don't you read this amazing article written by the AndroidRoot team and understand the technicals of the situation....
Click to expand...
Click to collapse
So it is impossible to unbrick Primes? Or anyone is working on it? Do You know?=)
I have searched around regarding this.
It seems that there is a SBK calculator made for the Acer A500 device.
This was made to generate blobs that match your device's CPUID.
If we could get this working on the Prime, it might perhaps unbrick it. (?)
DarkWader said:
I have searched around regarding this.
It seems that there is a SBK calculator made for the Acer A500 device.
This was made to generate blobs that match your device's CPUID.
If we could get this working on the Prime, it might perhaps unbrick it. (?)
Click to expand...
Click to collapse
Sadly, that won't work.
SBK generation is vendor-specific - there's no standard.
The SBK calculator for Acer A500 is extremely specific to A500 and won't work on other devices. (Acer ****ed up and the algorithm they used essentially got leaked).
It's possible something similar exists for ASUS devices, but it's pretty unlikely we'll get our hands on such a thing.
@ndrey said:
So it is impossible to unbrick Primes? Or anyone is working on it? Do You know?=)
Click to expand...
Click to collapse
Not if you have nvFlash enabled before you brick your device or upgrade to JB... if you have done [http://androidroot.mobi/t3_nvflash/], you should be able to recover from almost any brick...
craigacgomez said:
Not if you have nvFlash enabled before you brick your device or upgrade to JB... if you have done , you should be able to recover from almost any brick...
Click to expand...
Click to collapse
But if I dont? Bricked forever? :crying:
@ndrey said:
But if I dont? Bricked forever? :crying:
Click to expand...
Click to collapse
Quite possibly!!
Related
Hey guys,
I just wanted to put some information together on how to recover your bricked Prime (if possible).
DISCLAIMER
I am in no way responsible for what you do with your Prime, even when you are following these (my) instructions.
There is always the risk of making it worse and this risk is completely down to you!!!
Currently we know 4 states of bricked Primes whereas 3 are more or less widespread.
Brick 1a: You unlocked your Prime with ASUS' tool, did some stuff to it (like flashing a custom ROM) and now it always boots into recovery instead of your ROM.
You can't select to boot to fastboot or anything else. No matter what you do it's always the recovery. (happening to many users)
-> Please go to Option 1a
Brick 1b: You unlocked your Prime with ASUS' tool, did some stuff to it (like flashing a custom ROM) and now once you want to boot your new ROM it shows you the bootanimation but suddenly tells you something about an "unsuccessful encryption" (it's a real android screen, with a touch button etc.)
Once you hit the "Reset" button it restarts but you can't boot the ROM anymore, you are now caught in a CWM loop (much like Brick 1a)
-> Please go to Option 1b
Brick 2: When booting up your Prime hangs at the splashscreen (the screen with "EeePad" in the middle) and tells you something about an "unrecoverable bootloader error" (happened so far to at least 4 users)
-> Please go to Option 2
Brick 3: (After messing around with your Prime in recovery it won't boot any ROM anymore, you can however still access fastboot and the recovery)
Update: This particular brick happens due to a bad kernel flash. If you are flashing kernels via the ASUS /staging method, make sure /staging is unmounted before flashing stuff to it, otherwise it WILL faill and brick.
Update 2: It seems we can't use the old fix for this brick anymore. Sometimes it does more bad than good.
->Please go to Option 3
Option 1a
Don't be afraid, your Prime should be recoverable. This is the good news. The bad news is, that you need quite some knowledge of ADB.
To recover your Prime (most likely) you need the following:
A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
The USB-Cable to connect the Prime to your PC
A few minutes time
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Option 1b
Good news, this brick should be no problem.
Basically you need to first do Option 1a, but don't reboot the Prime just yet.
After executing the dd commands, you need to reboot your Prime to the bootloader menu and NOT the ROM itself.
To do this you need to reboot your device while holding down the Volume_Down key.
Once the white text in the top left corner appears release the buttons.
Now don't press anything until you can see a menu with 3 icons, an Android symbol, an USB symbol and a Wipe Data symbol.
Select the Wipe Data icon with pressing Volume_Down twice. Now press Volume_Up twice to reset the device to factory state.
WARNING: OF COURSE THIS WILL DELETE ALL YOUR DATA!!!! EVEN THE INTERNAL MEMORY AKA SDCARD!!! CURRENTLY I DON'T KNOW ANY OTHER WAY TO RECOVER FROM THIS BRICK!!!
After the wipe is done, you should be able to flash a new ROM or boot the existing ROM
Option 2
Sorry, but your Prime is most likely hard bricked.
This can happen if you try to apply a stock blob file after you installed CWM. There is currently no way to recover from this.
Option 3
If you are in this situation (Prime doesn't boot but you can access both recovery and fastboot) please go to #asus-transformer on freenode and ask for help there. We currently don't know if you can recover from this state.
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
We now found a way to un-brick this one too
This one is a bit more risky, so make sure you follow all instructions with a bit of extra care.
Update: It seems the old method for this brick could make things even worse on some Primes.
On some primes this can be easily fixed, however putting this in a guide could do more harm than good.
Troubleshooting
Problems getting ADB to work in recovery mode? Only seeing something like "Full Android on Emulator" in the device manager instead of your tablet?
Well I have a posible fix for you: Got to this thread and download the drivers. Then override the drivers for the Emulator device manually with the new ones. ADB should work now
--- Read here how to prevent future bricks and other common problems ---
Bits & pieces
You might want to have a look here for a possible solution for some bootloader errors (It's from a TF300):
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Credits:
thx to kmdm for his solution on Brick 1a and Brick 3
Sticky!
Sent from my Transformer Prime TF201 using xda premium
Thanks OP, now ive muster up the courage to root it and do everything else that's nice to it!
Thanks for the guide, very helpful. So I take it yours is still hard bricked?
Sent from my Transformer Prime TF201 using Tapatalk
Ultraman666 said:
Thanks for the guide, very helpful. So I take it yours is stuck on option 2 ?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
yes...
Update on a 4th option coming soon
Dude that sucks, hope you find a way to reverse it. Good luck
Sent from my Transformer Prime TF201 using Tapatalk
guy, come to diamondback channel so he can help you, seriously, he is so helpful, i cant even sleep for the whole night to figure out my problem, but after 10 mins with him, my tablet ready to rock and roll now, ty so much....
Any hope for JTAG?
Okay I added a 4th brick to the list. It's a variant of the first Brick and it is recoverable
How horrible would it be for Asus to provide the equivalent of odin for our devices?
I don't see what's so hard with embracing development.
You've got my back.
Thank you Diamondback. It's comforting to have this info available before I take the plunge.
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
chugger93 said:
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
Click to expand...
Click to collapse
Well because you can do way more stuff with Android phones
Ever run a different OS on the iPhone? Not that I am aware of
It's like having a full blown PC with BIOS and all versus having a Nintendo 64
Ever bricked a N64?
chugger93 said:
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
Click to expand...
Click to collapse
As Diamondback said, it's simply because we can do more with Android.
Rest assured that if the same type of modifications could be made to IOS, the risk of "bricking" would be the same.
A big help would be having a ported nvflash tool, or Smartflash.... Saved many guys on other Tegra devices like my phone for example.
chugger93 said:
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
Click to expand...
Click to collapse
This is a product of the Android fragmentation. Every device is different and uses different hardware/drivers. The Android OS assumes you know what you are doing and will actually let you do what ever you want. If you flash a ROM/Firmware that is designed for the Nexus on a Galaxy S II it will let you, you will brick the Galaxy S II, but it will let you do whatever you want.
That is also why everytime Google releases a new version of an OS it takes so long to apply it to all the different devices. The moment ICS was released, it was not compatible with every device out of the box. Every manufacturer has to create drivers, kernels, and libraries for it to work on their device.
You cannot brick an Iphone because it only has 1 OS to install and only 1 type of hardware to cater to
Good Read about the effort that goes into rolling out a new OS for the android space: http://www.extremetech.com/computin...nths-to-deliver-android-updates-to-your-phone
P.S. +1 to sticky
Does APX mode work in Option 2?
STICKY THIS! Very important information. Thank you Diamond Back and hope the best for you and your Prime
REAVER117 said:
Does APX mode work in Option 2?
Click to expand...
Click to collapse
Yes but that doesn't help anything thx to ASUS' encrypted bootloader partition....
This is a good thread, I hope to never need it.
The closest I've ever come to 'bricking' a device (or at least so I thought) was practically my first experience with android modification:
Rooted and Installed CWM on my Droid Incredible. Initiated install of a Rom from Rom Manager. I Had not realized that the Dinc had 2 different screens, AMOLED and something else. CWM was not configured to display anything for my type of screen! so I had a failed rom install and no visible CWM to do any recovery (womp womp). But did some research and some guys from the CM irc helped me use the google sdk to get up a snapshot on my computer of what was happening on my phone. BAM was able to see the recovery on my laptop and install a fix for it Was pretty scary.
Glad there are people like you out there to help others out when scary and rather Traumatic experiences like this happen
I'm resorting to xda developers because no longer know what to do and the more I read less i know!
I have a Asus Tf201 JB. Sometimes ago the screen broke, i buy one on ebay but when i assembly the new screen i got the x-axis reversed, so i google and found the fix to x axis reversed here on forum.
First i unlock the device with asus tool, after i root and use some android software (i cant remmember the name) to flash the x axis reversed fix patch.
My bad, i do something wrong, now it stuck on asus/nvidia logo screen.
My pc only recognize APX mode if power+upvolume nothing more.
Please help me and tell me:
Are permanently dead, can i fix or its garbage?Can here any expert solve me this problem!?I pay if necessary.
If it dead can i swap the motherboard and get the problem solved!?
Sorry about my English
Thanks in advance
Best Regards
im sorry to ask this while I can't help you, but im trying to root my Tf201 and I can't seem to figure out how. How did you? I've got it unlocked using the Asus tool, like you, but every way I've found to root has not worked for me.
Thanks, and sorry I couldn't help your issue.
Claymorb said:
im sorry to ask this while I can't help you, but im trying to root my Tf201 and I can't seem to figure out how. How did you? I've got it unlocked using the Asus tool, like you, but every way I've found to root has not worked for me.
Thanks, and sorry I couldn't help your issue.
Click to expand...
Click to collapse
Hi, i use Motochop it works fine for me, dont forget run app as admin!
Regards
The information is out there, but not always easy to find. I haven't had to recover my Prime yet, but I've done the backups before flashing to Androwook, and have read up on how to recover should anything go wrong. here is what I've found as a good resource:
*Note: Being able to get into APX mode is a good start*
Go to this thread, "[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201"
The step-by-step guide is self explanatory. It goes over getting the NVIDIA Naked Drivers, NVFLASH and Wheelie. And the best part, there are links to the stock "un BLOB'D" files, which you will need for a recovery. This is basically the stock rom you can download from the ASUS site, and broke out into the separate recoveries for all the partitions.
and to answer your last question about what to do if you cannot unbrick... yes, you would need to replace the motherboard as the last resort.
Good luck!
edit: Found a really good thread (saved to my favorites) showing step-by-step process to unbrick:
Post 16 from "Need help with APX mode" thread
Hello all.
I have an Asus TF201 bricked.
I readed a lot of forums, and nothing to do for now.
My Asus was fall in brick after install cwm, and now, only can reboot in APX.
When I reboot normal or fastboot, it only show logo and stop.
I can't enter in fastboot, adb dont detect my device.
Wheelie detect but I havn't got blob.bin, so I can´t use nvflash.
Arggg!
Is there any solutions?
arjona00 said:
Hello all.
I have an Asus TF201 bricked.
I readed a lot of forums, and nothing to do for now.
My Asus was fall in brick after install cwm, and now, only can reboot in APX.
When I reboot normal or fastboot, it only show logo and stop.
I can't enter in fastboot, adb dont detect my device.
Wheelie detect but I havn't got blob.bin, so I can´t use nvflash.
Arggg!
Is there any solutions?
Click to expand...
Click to collapse
I seem to have the same problem
Hi!
I have the same problem.
Somebody can hepl us please!! Thank you
I downloaded Tegra Android Developer Pack and image "dalmore" where are some utilities to generate encrypted necessary to enable executing commands in the boot. These are: nvsecuretool.exe or nvsbktool.exe.
but anyway the correct key is needed.
I used the calculator sbk but do not know if this works only for Acer tablet with tegra2.
A desperate chance. would take the sbkcalculator, and the apk asus application to unlock the boot, and test if there is any clue as to how you can make the sbk from cpuid on this model.
but I have no hopes for it.
I hope someone knows how to get the sbk from the cpuid for asus tf201.
why? why is so hard to find files to unbrick tf201?, ****ing secure boot, links deads
sometimes what is legal is not fair,
sorry but my skills are a dried **** as my translator
i try to find a .bct no encripted to build the blob.bin with my doubtful sbk from sbkCalc, but nothing,
I know it's possible, but I also realize that I will not be able to do.
alemap said:
why? why is so hard to find files to unbrick tf201?, ****ing secure boot, links deads
sometimes what is legal is not fair,
sorry but my skills are a dried **** as my translator
i try to find a .bct no encripted to build the blob.bin with my doubtful sbk from sbkCalc, but nothing,
I know it's possible, but I also realize that I will not be able to do.
Click to expand...
Click to collapse
I'm sorry, but it is only possible to un-brick a hard-bricked TF201 by using files that have been created on your own device with NVFlash.
Did you have nvflash enabled before you bricked? If not then you have a paper weight.
Check out my website for encouragement....
www.projectintercession.blogspot.com
Yes i enabled nvflash before brick, but i dont copied the blob.bin o any other file from the root backup folder to my pc.
i dont find it, maybe i delete carelessly when try install kitkat in the tablet.
tremendous fail !!.
If you bricked without having your NVflash blob files backed up, you're out of luck at the time of this writing. For a HARD BRICK, which you are experiencing, the ONLY way to recover if with those blob files. I have mine on google drive, dropbox, and on my PC for safekeeping.
I sold the prime I managed to brick for parts on ebay. I got $100 for it, but that was well over a year ago. There are better tablets out there, and most of them definitely put this old guy to shame. I would suggest upgrading your hardware, as the device you have is no longer usable.
I hate to be the bearer of bad news, but this is the chance you take when you unlock bootloaders, hack and flash ROMS, root, etc. Sometimes $h!7 happens. That's life.
Hello,
I have the same problem.
TF201 bricked !
Unable to go into the bootloader, so unable to go on fastboot !
I never activate nvflash so i dont have my blob file.
I'm sofwtare programmer, i think we could fin any way to hack nvflash or a wayt patch any blob file in order to be compatible for our device....
Please, union made strong ! We need to create or get a hack in order to use correctly APX!
---------- Post added at 08:35 PM ---------- Previous post was at 08:07 PM ----------
alemap said:
I downloaded Tegra Android Developer Pack and image "dalmore" where are some utilities to generate encrypted necessary to enable executing commands in the boot. These are: nvsecuretool.exe or nvsbktool.exe.
but anyway the correct key is needed.
I used the calculator sbk but do not know if this works only for Acer tablet with tegra2.
A desperate chance. would take the sbkcalculator, and the apk asus application to unlock the boot, and test if there is any clue as to how you can make the sbk from cpuid on this model.
but I have no hopes for it.
I hope someone knows how to get the sbk from the cpuid for asus tf201.
Click to expand...
Click to collapse
Interresting post...you could have the sbk on the tabs sticker...
But the question is...how patch a blob file in order to use the NVFlash....
I'm software programmer, maybe i can help you dude !!
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Restorer said:
I'm sorry, but it is only possible to un-brick a hard-bricked TF201 by using files that have been created on your own device with NVFlash.
Click to expand...
Click to collapse
There is probably a way to hack this file....to patch this....
I would like to compare two file in order to see differences....maybe it's simple to merge and patch.....
Wellcome to the Wall.
Hi folks,
I accidentally grabbed hold on a tablet Computer from Toshiba, where there's already an Android OS pre-installed. Luckily, this device seems not yet to be locked, so that it's still possible to install images using nvflash.
Now I would like to create my own Android from scratch, but I don't know how to start.
Building Android does not seem to be the biggest problem. It's rather taming the nvidia beast with its nvflash and all the partitions and the other nvidia-specific things.
Also, how to find out which devices this tablet consists of ? (But maybe this is covered in some oft the other threads I still need to work through...)
Most important for now would be how to get familiar with the tegra...
Any help would be highly appreciated!
Thanks in advance,
Boxy
unlocked Toshiba tablet with Nvidia T40
BoxyK said:
Hi folks,
I accidentally grabbed hold on a tablet Computer from Toshiba, where there's already an Android OS pre-installed. Luckily, this device seems not yet to be locked, so that it's still possible to install images using nvflash.
Now I would like to create my own Android from scratch, but I don't know how to start.
Building Android does not seem to be the biggest problem. It's rather taming the nvidia beast with its nvflash and all the partitions and the other nvidia-specific things.
Also, how to find out which devices this tablet consists of ? (But maybe this is covered in some oft the other threads I still need to work through...)
Most important for now would be how to get familiar with the tegra...
Any help would be highly appreciated!
Thanks in advance,
Boxy
Click to expand...
Click to collapse
Do you still have this unlocked Toshiba tablet with Nvidia T40?
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Click to expand...
Click to collapse
you are then able to flash another (custom) recovery, which would let you install unsigned zip-files, e.g. in order to get root.
Unfortunately, there is no recovery port by now.
I don't know if one could use the source code on Lenovo's website to port one, if not we would probably need an image dump directly from the device (if I'm not mistaken you need root to dump the recovery image).
I really would like to have root, but it still seems far away unless there's an experienced developer somewhere who owns the device.
I've already thought of starting a bounty thread...maybe enough people are willing to contribute so that developers might feel attracted.
Hello,
Do you think it would be possible to install Windows 10 on our android yoga book?
Thanks,
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
AndyVerne said:
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
Click to expand...
Click to collapse
can you tell me how to deal with it? I met the same problem.
Vsplorer said:
can you tell me how to deal with it? I met the same problem.
Click to expand...
Click to collapse
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
AndyVerne said:
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
Click to expand...
Click to collapse
can you tell me where to download the exe？ thanks a lot！
Vsplorer said:
can you tell me where to download the exe？ thanks a lot！
Click to expand...
Click to collapse
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
AndyVerne said:
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks！
Missing Something?
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
jasonccheng said:
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
Click to expand...
Click to collapse
See this post:
https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Same here with Linux... The adb devices command shows the device but the flash command ends in 'waiting for device' and thats it. Damn
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
zamzenos said:
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
Click to expand...
Click to collapse
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
danjac said:
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
Click to expand...
Click to collapse
Let me start at the top:
1. My comments on Lenovo are no reflection on the useful tools you have provided us here, for which I have thanked you more than once. So no need to be defensive on that score.
2. If the unlock warning had its source in Android itself, we could expect the warning to bear its logo. I assume it bears the Intel logo because Intel is the author of it. In itself, this is of no importance. What is profoundly irritating is the fact that the security warning is followed by a completely unjustfied 5 second suspension. This is a penalty. Perhaps many do not mind this interference with their use of their devices, but I do. I'm not used to that kind of treatment and I don't take kindly to it.
3. My opinion of Lenovo has always been low, especially since their attempts some years ago to spike their devices with spyware. I regard Lenovo as an exploitative bottom feeder, supplying workaday gear and screwing their customers every way they can for an extra buck or two. I offered the YB to several of my friends. All turned their noses up at the mention of the manufacturer. Don't blame them.
4. If you do want to be of further assistance here, perhaps you can use your obvious technical skills and knowhow to work out how we can replace the Intel penalty with something more benign. I have tried, but can't find where the Intel warning is hidden.
I have downloaded and extracted the apk of the system app remover you mentioned. But until I can get rid of the Intel warning I won't bother to re-root the YB and test if it will clear the junk.
#carepack: at the moment, you must buy the stock firmware (and won't it be expensive!). All part of lenny's screw.
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
carepack said:
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
Click to expand...
Click to collapse
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
zamzenos said:
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
Click to expand...
Click to collapse
According to this:
http://www.androidpolice.com/2016/1...views-cite-software-issues-incredible-design/
We'll receive the nougat Update.
Greetings