lenovo K1 bricked - General Questions and Answers

screen says "booting recovery kernel image" nothing ever happens after...
I have NVFlash
I have APX driver installed ok
I have lenovo k1 OTA.zip
now what?
I understand that there is a key not cracked yet. Is there a way to put back ota imgs/boot ?
All the nvflash GUIDES pertain to specific tablets/phones. I feel like Im close to understanding what im missing.
I read to try and repair this brand new k1 every day and have joined 6 forums and have been asking guidance.
I fell like I got a secret since noone is really interested in the k1 development/rooting. I would have thought since it was the first with netflix loaded that everyone would be playing with these tbt's.
I bought mine for my 5 year old son with nflix in mind...
I did factory data reset and then update and <boink> "booting recovery kernel image"
Can I use nvflash and Ota.zip to fix this? What am I missing here?
Thank you in advance devpeeps

chrisnk1 said:
I have APX driver installed ok
I
Click to expand...
Click to collapse
HI
Can you please upload the APX driver here ...
Thanks

I am having similar issues

Ditto.
Can't find the apx drivers anywhere.
---------- Post added at 05:39 PM ---------- Previous post was at 05:08 PM ----------
Look what I found!!
Goto goo and search for nvflash/nvflash_windows.zip or just nvflash.
Running Jellybean right now!!

Related

[Q] Xoom Wifi from 3.0.1 to 3.2? NOT rooted

Hello-
I have a Wifi Xoom with Android 3.0.1. It is not rooted as I have some more reading to do before I go down that road.
Anyway, I want to take my unrooted Xoom and update it to 3.2. When I go through the settings to update it, it doesn't work. I get the following message:
"Your device is up to date! No update is necessary at this time." with an OK button.
So what do I need to do to update my Wifi Xoom to the latest Android OS?
If you don't mind losing your data, do a factory reset. I got my Xoom 2 days ago and it had the updates available right out of the box.
brandogg said:
If you don't mind losing your data, do a factory reset. I got my Xoom 2 days ago and it had the updates available right out of the box.
Click to expand...
Click to collapse
Thanks. I got my Xoom from a "daily deals" website. Although it was new, it might have been sitting on a shelf somewhere for quite a while.
I spent a few hours playing with it and setting it up so I'd like to avoid a factory reset for now.
ualdriver said:
Thanks. I got my Xoom from a "daily deals" website. Although it was new, it might have been sitting on a shelf somewhere for quite a while.
I spent a few hours playing with it and setting it up so I'd like to avoid a factory reset for now.
Click to expand...
Click to collapse
That's exactly why you got no help...lol
You're in the wrong place if you are tidy about resetting up things lol
rooting xoom wifi 3.2
sorry, i know this is totally unrelated but i need anybody's help urgently.
please i need your help.
im stuck at "fastboot flash boot rootboot.img"
after unlocking, im supposed to put that code into cmd but it gives error: cannot load 'rootboot.img'.
you look like u successfully rooted yors, please help. i've been trying for hours with no luck. please tell me what i'm missing...thanks in advance.
Reinstall stock ROM
dirtysexyrodney said:
sorry, i know this is totally unrelated but i need anybody's help urgently.
please i need your help.
im stuck at "fastboot flash boot rootboot.img"
after unlocking, im supposed to put that code into cmd but it gives error: cannot load 'rootboot.img'.
you look like u successfully rooted yors, please help. i've been trying for hours with no luck. please tell me what i'm missing...thanks in advance.
Click to expand...
Click to collapse
I will find a link that saved my chops.
---------- Post added at 06:01 PM ---------- Previous post was at 05:55 PM ----------
Check this out and follow:
It will take you back to stock then just update.
It worked first time
http://forum.xda-developers.com/showthread.php?t=1394563

[Q] (Q) my eee pad stuck at asus welcome screen why!?

Hi everyone,
Yesterday I tried to install stock rom again by following a tutorial which is on this forum too but since I don't have enough posts to post an post in development section. I decided to post it here
Since I installed the stock rom and kernel on my device I can't boot up anymore It just stuck at the begin screen of asus;s I tried to use NvFlash but without succes because everytime I put my device in APX mode(this works) and then run the .bat file apx mode removes and the bat file says no device found;s
So then I tried wiping all data by using some volume button, tried to cold boot but didn't work neither. Tried to get into recovery but can't boot after that.
SO I would really appreciate it if someone could help me
P.S. I tried this unrooting/stock rom method:
http://forum.xda-developers.com/showthread.php?t=1154947
And I was running Revolver ROM.(latest update)
Yours Kasper
This post would not belong in the development section FYI..you are in the right place, only post in Dev section if you are developing something.
What is your serial number? B70 and later cannot use NVflash from what I understand so if you are B70 or later you may be bricked..
Thanks for your fast reaction! and where can I find my serial number? and if I am bricked is there any way to get un bricked?
kaspertje100 said:
Thanks for your fast reaction! and where can I find my serial number? and if I am bricked is there any way to get un bricked?
Click to expand...
Click to collapse
Look near the charging port, should be a sticker that start with a "B".
Also on the back of the box if you still have it.
Sent from my Transformer TF101 using Tapatalk
Kay thanks, but I removed all my stickers and had to threw away the box when I left America with the plane;s (didn't fit in my bag) So I guess im 70b+ else NvFlash would work? But is there maybe some other way to get my device unbricked or is the only thing I can do is waiting untill Nvflash supports 70b +?
baseballfanz said:
Look near the charging port, should be a sticker that start with a "B".
Also on the back of the box if you still have it.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
It can also start with a "C" (newest TF's)
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
kaspertje100 said:
Kay thanks, but I removed all my stickers and had to threw away the box when I left America with the plane;s (didn't fit in my bag) So I guess im 70b+ else NvFlash would work? But is there maybe some other way to get my device unbricked or is the only thing I can do is waiting untill Nvflash supports 70b +?
Click to expand...
Click to collapse
You can determine if you can use nvflash. See here
gls9 said:
It can also start with a "C" (newest TF's)
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
You can determine if you can use nvflash. See here
Click to expand...
Click to collapse
well does this only work on linux cuz i can't run this on windows? or how should I run that
Are you stuck on the very first screen that says Eee Pad or the second one that just has a silve ASUS in the middle? Cause if it's the second...it's the bootanimation so couldn't you just go into recovery and clear and reflash?
its the silver I can get into recovery but wiping or cold-booting only results in freeze;s and trying to install a new ROM (EVEN THE official of asus rom) it gives an error the Yellow Triangle above the android man;ss
kaspertje100 said:
its the silver I can get into recovery but wiping or cold-booting only results in freeze;s and trying to install a new ROM (EVEN THE official of asus rom) it gives an error the Yellow Triangle above the android man;ss
Click to expand...
Click to collapse
Assuming you have CWM Recovery...did you try using the Format option...then reinstalling a ROM? Just a thought.
SiNJiN76 said:
Assuming you have CWM Recovery...did you try using the Format option...then reinstalling a ROM? Just a thought.
Click to expand...
Click to collapse
Well I don't have clockwork;s I have stock asus recovery;p

No CWM for WT19i???

Hi...
I have been searching the net for about a week now and couldn't find CWM recovery for my SE Live WT19i. Maybe i am looking in the wrong places. phone runs on 2.3.4 with 4.0.2.A.0.62 (rooted). Also please name any good Roms for the phone...
Please help.
Thanks...
c4capricorn said:
Hi...
I have been searching the net for about a week now and couldn't find CWM recovery for my SE Live WT19i. Maybe i am looking in the wrong places. phone runs on 2.3.4 with 4.0.2.A.0.62 (rooted). Also please name any good Roms for the phone...
Please help.
Thanks...
Click to expand...
Click to collapse
take a look
link1
link2
link3
link4
you need an unlocked bootloader instructions above
use a laptop on battery when flashing to protect from bootloader errors
if something wrong when flashing bootloader your phone is bricked
you have to use service tools to solve this problem
(screen is black phone looks like dead)
install this:
https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
rajmi said:
install this:
https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
Click to expand...
Click to collapse
I installed it but says the phone is not supported...
get SE_Extreme_Tweak_Installer_1.8.... It works
---------- Post added at 04:20 PM ---------- Previous post was at 04:15 PM ----------
get SE_Extreme_Tweak_Installer_1.8.... It works
to enter into recovery mod, turn off ur phone and press volume down key multiple times while turning on

How to downgrade nvidia shield from 4.4.2 to 4.3?

Hi guys. I want to know how to do what the title says cause the new update sucks really bad. Games fps is lower, can't use SD card anymore, full screen is not really full screen anymore. Well yeah thanks
ALLEN2 said:
Hi guys. I want to know how to do what the title says cause the new update sucks really bad. Games fps is lower, can't use SD card anymore, full screen is not really full screen anymore. Well yeah thanks
Click to expand...
Click to collapse
GO here http://forum.xda-developers.com/showthread.php?t=2661067
Follow the instructions on getting the bootloader unlocked and getting rooted by flashing CWM.. after all those steps. re open the program and choose Flash BONE STOCK. You will be right back in Android 4.3 update 68 i think from Nvidia. which is right back to when you purchase it from Gamestop. Get it quick before the developer update it to The latest update which is the one your on, 4.4.2.
As long as you follow the instructions and get the Universal Ghost Driver installed properly. It works. I've tried this out already, I em back on Android 4.3..
DJFresh82 said:
GO here http://forum.xda-developers.com/showthread.php?t=2661067
Follow the instructions on getting the bootloader unlocked and getting rooted by flashing CWM.. after all those steps. re open the program and choose Flash BONE STOCK. You will be right back in Android 4.3 update 68 i think from Nvidia. which is right back to when you purchase it from Gamestop. Get it quick before the developer update it to The latest update which is the one your on, 4.4.2.
As long as you follow the instructions and get the Universal Ghost Driver installed properly. It works. I've tried this out already, I em back on Android 4.3..
Click to expand...
Click to collapse
Alright, do I loose all my data and is there I way I can update to the update before this 4.4.2 update?
Note CMW development its dead and dont know what happens if you install CMW recovery on kiktat,try to install another recovery.
ALLEN2 said:
Alright, do I loose all my data and is there I way I can update to the update before this 4.4.2 update?
Click to expand...
Click to collapse
unfortunately you will lose everything if you go through with this method unless most of your personal stuff is on the MicroSD Card, as it reflashes your original clean untouched recovery... Maybe in the near future there might be another simpler method.
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
alexei_gp said:
Note CMW development its dead and dont know what happens if you install CMW recovery on kiktat,try to install another recovery.
Click to expand...
Click to collapse
It boots up to CWM and it seems to be working normal as far as doing a nandroid backup to MicroSD.. I haven't encountered any issues yet when i had KitKat.. I had the CWM running normal as far as I can tell. Well i'm still sort of a newbie, here you guys are the experts..... thanks for the great dev for another great device
DJFresh82 said:
unfortunately you will lose everything if you go through with this method unless most of your personal stuff is on the MicroSD Card, as it reflashes your original clean untouched recovery... Maybe in the near future there might be another simpler method.
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
It boots up to CWM and it seems to be working normal as far as doing a nandroid backup to MicroSD.. I haven't encountered any issues yet when i had KitKat.. I had the CWM running normal as far as I can tell. Well i'm still sort of a newbie, here you guys are the experts..... thanks for the great dev for another great device
Click to expand...
Click to collapse
I m not a dev xDDD when i install CMW recovery on my nvidia shield i have problems to update to 4.3 .Searching on the thread of CMW i realize the CMW recovery its dead , no update no oficial development nothing and the worse you cant download the recovery on that thread,
alexei_gp said:
I m not a dev xDDD when i install CMW recovery on my nvidia shield i have problems to update to 4.3 .Searching on the thread of CMW i realize the CMW recovery its dead , no update no oficial development nothing and the worse you cant download the recovery on that thread,
Click to expand...
Click to collapse
Even though CWM is dead. in order to root using the Shield 1.0 method, CWM is still needed to flash SuperSU.zip.. unless you another method to root, the CWM isn't nessessary to flash. as long as you boot loader is unlocked of course and your rooted. you can use the Bone Stock method, and it will restore the shield back to 4.3.... this is the only way i know of as of now... I'm sure in the near future there might be another simpler method...........
DJFresh82 said:
Even though CWM is dead. in order to root using the Shield 1.0 method, CWM is still needed to flash SuperSU.zip.. unless you another method to root, the CWM isn't nessessary to flash. as long as you boot loader is unlocked of course and your rooted. you can use the Bone Stock method, and it will restore the shield back to 4.3.... this is the only way i know of as of now... I'm sure in the near future there might be another simpler method...........
Click to expand...
Click to collapse
I dont need to use the script SHIELD 1.0, i used minimal adb fastboot to root it using a image root on github,CWM its not required to flash SuperSU.zip
Once you're on kitkat I dont think you can go back to jellybean. I could be totally wrong but I tried going back to 4.3 and it bricked my shield, wouldn't boot. I didn't spend much time on seeing why it happened, so like I said I Could be totally wrong. I could of had bad files for all I know.
alexei_gp said:
I dont need to use the script SHIELD 1.0, i used minimal adb fastboot to root it using a image root on github,CWM its not required to flash SuperSU.zip
Click to expand...
Click to collapse
I didn't say u had to use that SHield 1.0 method to root, I said only if your using that method. I know there are other methods to root. The point I was making is that once your rooted and bootloader unlocked. you can still use shield 1.0 to reflash the update 68 i beleive which is android 4.3.. out of the box state from gamestop.... It worked for me having the same latest kitkat OTA that you have......
---------- Post added at 08:43 PM ---------- Previous post was at 08:31 PM ----------
hexitnow said:
Once you're on kitkat I dont think you can go back to jellybean. I could be totally wrong but I tried going back to 4.3 and it bricked my shield, wouldn't boot. I didn't spend much time on seeing why it happened, so like I said I Could be totally wrong. I could of had bad files for all I know.
Click to expand...
Click to collapse
It does seem like that.. but using SHIELD 1.0.. it worked for me, I'm back on 4.3 update 68 from NVIDIA. Using this mainly for emulators.. I'm sure there will be some type of fix in the near future for kitkat though, when it is, i will update mines back to that...
DJFresh82 said:
I didn't say u had to use that SHield 1.0 method to root, I said only if your using that method. I know there are other methods to root. The point I was making is that once your rooted and bootloader unlocked. you can still use shield 1.0 to reflash the update 68 i beleive which is android 4.3.. out of the box state from gamestop.... It worked for me having the same latest kitkat OTA that you have......
---------- Post added at 08:43 PM ---------- Previous post was at 08:31 PM ----------
It does seem like that.. but using SHIELD 1.0.. it worked for me, I'm back on 4.3 update 68 from NVIDIA. Using this mainly for emulators.. I'm sure there will be some type of fix in the near future for kitkat though, when it is, i will update mines back to that...
Click to expand...
Click to collapse
Ok thats good to know i used fastboot to flash the update 68 files.
you are soo wrong, you arent briked
just set up the ghost drivers on your computer, get fastboot working, download kwonggers toolkit, follow the instructions on screen of your computer to set your shield back to 4.2.2 because the toolkit hasn't been updated and everthing shield is almost as dead as the ouya or worse, so I might just sell the shield from the lack of audience and support and get a bloody snapdragon 801 phone, if NVidia wants to keep this relevant, they need to work with the developer community more, unless shield will die, I have made my choice, now what's yours?
hexitnow said:
Ok thats good to know i used fastboot to flash the update 68 files.
Click to expand...
Click to collapse
That's Awesome.....
mudflap2.0 said:
just set up the ghost drivers on your computer, get fastboot working, download kwonggers toolkit, follow the instructions on screen of your computer to set your shield back to 4.2.2 because the toolkit hasn't been updated and everthing shield is almost as dead as the ouya or worse, so I might just sell the shield from the lack of audience and support and get a bloody snapdragon 801 phone, if NVidia wants to keep this relevant, they need to work with the developer community more, unless shield will die, I have made my choice, now what's yours?
Click to expand...
Click to collapse
I just got the Shield mainly for emulators, so will stick with 4.22 since that is what the device had out of box. Works great and no need to root or any other hassle for the intended use.

AT&T Tab 4 8" T337A Temp Root

This is a temp root and will be removed every hard boot.
I am not responsible if you break your device!
You have been warned.​
Knox is not tripped​
Hello All, I Have found a temp root process for those who have the AT&T Tab 4 with the kernel build Thu Aug 13 17:01:34 KST 2015.
Download Tab 4(Temp root), you will have 3 files. Odin 3.07, boot(LP_fix).tar and Kingroot-4.1.apk.
Install KingRoot on your tablet run and click Start Root. After the first time the process of checked for root will take longer as su will still be installed.
You will now have KingUser installed in /system/app/
When uninstalling bloatware, do it in one go.
When you have to reboot, reboot into download mode or you will get the AT&T unauthorized screen.
Use Odin to Flash PDA with the boot(LP_fix).tar, this will wipe the su links so the kernel doesn't see it and will boot. You will reboot automatically back to the launcher and will be able to reboot without using Odin.
Need help furthering permanent root as this is beyond my skills.
Update 1/27/16 14:35
Deleting all knox related apps is safe so far, setting build.prop ro.build.selinux=0 and a soft reboot seems to put kernel in permissive mode. Download a soft reboot app from the play store for reboots.
Don't let you tablet die and you don't have to keep doing this process!
Thanks to CocaFoca for the boot(LP_fix).tar.
Thanks for the dev(s) of KingRoot.
Does it work
Anyone try this yet?
---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------
Seems kind of weird no one is commenting on this, wonder if it works
I see this on a few different sites but no comments on any of them. I use my tab for work and can't afford to be Guinea pig and turn tab into hockey puck so have to wait a while I guess. If anyone can confirm that this works let us know please
Seeing as how the author wont even reply its not worth the risk to me
This works just no hard boots. No knox trips either. Still working on recovery methods maybe someone can help upload there build.prop.
TechNyne66 said:
This works just no hard boots. No knox trips either. Still working on recovery methods maybe someone can help upload there build.prop.
Click to expand...
Click to collapse
what soft boot app did you use?
---------- Post added at 05:30 PM ---------- Previous post was at 05:22 PM ----------
I didn't realize there was no odin firmware yet. kind of scary, anything goes wrong and I'm screwed
gonzo6962001 said:
what soft boot app did you use?
---------- Post added at 05:30 PM ---------- Previous post was at 05:22 PM ----------
I didn't realize there was no odin firmware yet. kind of scary, anything goes wrong and I'm screwed
Click to expand...
Click to collapse
Just search soft reboot in play store and it has red arrows in a circle motion. As long as you don't mess with build prop you will be fine.
on your notes on the 27th you put to do.... setting build.prop ro.build.selinux=0...... do I still do that? The last message you sent said as long as I dont mess with build prop I will be fine...
gonzo6962001 said:
on your notes on the 27th you put to do.... setting build.prop ro.build.selinux=0...... do I still do that? The last message you sent said as long as I don't mess with build prop I will be fine...
Click to expand...
Click to collapse
If you know what your doing you can change build.prop, do you need permissive kernel? All it does is disables SElinux for stuff like xsposed which isn't supported yet. Its aimed more to someone who will help farther to permanent root. The build prop is really good for this device.
I cant get that odin to open will 3.09 work? I already have that one installed
---------- Post added at 07:13 PM ---------- Previous post was at 06:44 PM ----------
IT WORKED!!!!!! Thank you............................................................................ Soft reboot after doing build prop adjustment and it worked. Bout had a stroke when it said starting apps but couple seconds later started up with ROOT.......................
---------- Post added at 07:34 PM ---------- Previous post was at 07:13 PM ----------
dumb question, I want viper4android and most say to flash in custom recovery. Can I still go into stock recovery without screwing things up? Then if I can I would have to go into download and flash through odin and then reroot right?
---------- Post added at 07:36 PM ---------- Previous post was at 07:34 PM ----------
TechNyne66 said:
If you know what your doing you can change build.prop, do you need permissive kernel? All it does is disables SElinux for stuff like xsposed which isn't supported yet. Its aimed more to someone who will help farther to permanent root. The build prop is really good for this device.
Click to expand...
Click to collapse
dumb question, I want viper4android and most say to flash in custom recovery. Can I still go into stock recovery without screwing things up? Then if I can I would have to go into download and flash through odin and then reroot right?
well it does work but twice it rebooted on its own and luckily I got it into download before the bootloader got it. I think Im gonna quit playing with fire before I get burnt
gonzo6962001 said:
I cant get that odin to open will 3.09 work? I already have that one installed
---------- Post added at 07:13 PM ---------- Previous post was at 06:44 PM ----------
IT WORKED!!!!!! Thank you............................................................................ Soft reboot after doing build prop adjustment and it worked. Bout had a stroke when it said starting apps but couple seconds later started up with ROOT.......................
---------- Post added at 07:34 PM ---------- Previous post was at 07:13 PM ----------
dumb question, I want viper4android and most say to flash in custom recovery. Can I still go into stock recovery without screwing things up? Then if I can I would have to go into download and flash through odin and then reroot right?
---------- Post added at 07:36 PM ---------- Previous post was at 07:34 PM ----------
dumb question, I want viper4android and most say to flash in custom recovery. Can I still go into stock recovery without screwing things up? Then if I can I would have to go into download and flash through odin and then reroot right?
Click to expand...
Click to collapse
No custom recovery yet as I was told bootloader is locked, until someone confirms custom recovery works in am staying away as there's no Odin firmware and I need warranty. Yes Odin 3.09 will work but it will remove root really no need unless a hard reboot is needed your your tablet dies. Just keep with soft reboots. As for viper I would stay away soundalive is way better. Stock recovery will not work.
Better than viper4android? I highly doubt that. Don't think that is possible
First, just want to say thanks for sharing this info & zip. It brought my tab back from the dead after i rooted. (initially i was unaware it had a locked bootloader until after i rooted). I just have a cpl questions maybe someone in here can answer.
1. Has anyone tried using Flashify or Root Rashr to flash the boot_LP_fix.tar before powering off? I personally have never used either app so i dont know if either can flash .tar files. I know Mobile Odin would probably work, buy it doesn't support LP. 2. Has anyone installed busbox? 3. Do any of the "Hide Root" type apps function in such a way as to let the tab reboot? Those were just a few questions i had about this. Thanks for any info.
lbcary said:
First, just want to say thanks for sharing this info & zip. It brought my tab back from the dead after i rooted. (initially i was unaware it had a locked bootloader until after i rooted). I just have a cpl questions maybe someone in here can answer.
1. Has anyone tried using Flashify or Root Rashr to flash the boot_LP_fix.tar before powering off? I personally have never used either app so i dont know if either can flash .tar files. I know Mobile Odin would probably work, buy it doesn't support LP. 2. Has anyone installed busbox? 3. Do any of the "Hide Root" type apps function in such a way as to let the tab reboot? Those were just a few questions i had about this. Thanks for any info.
Click to expand...
Click to collapse
Hide root does not work has to do with the kernel checking for root or sumlinks, busy box installs and works but no idea on flashify.
Thanks. Appreciate the info. Im only looking for a way to safely power down bcuz about 2 or 3 times a week my tab doesnt get plugged I into a charged so it gets shut off. My girlfriends mother & son play with it & use it to stream movies. It would be great if there was a functional equivalent of Mobile Odin Pro so when i was done busing it i vould simply flash the tar. file so it would boot. Maybe ill do a little experimenting & see what happens. Thanks again
Can someone with a rooted SM-T337A do a system dump with these files included modem.bin, NON-HLOS.bin, recovery.img, a cache dump, and the PIT file??? Please
Thanks worked
I think I dun goofed :c. Was working fine, then I had to reboot, flashed the .tar, but I think I was a second late on catching it, because now it doesn't boot :c Hangs on ATT screen. HEEELP :C
Does anyone have a tar file for the t337a?

Categories

Resources