Hello.
I've run into some troubles with my device, and apparently what's wrong with it is incorrect mmcblk0p values. I did something wrong with it. And now I want to try restoring it back to the default state since I can't boot into any ROM due to boot looping. Both stock and TWRP recoveries are still accessible.
Another problem that might've come along with it is that whenever I select "continue" in the bootloader menu, it says "cold booting linux".
Thanks in advance.
EDIT:
I ask for the file from the new version of the Nvidia Shield Tablet, 16GB specifically. The one that came out without the pen.
HERE'S THE INSTRUCTION ON HOW TO COPY THE FILE:
1. Enter TWRP
2. Mount System if necessary
3. Advanced -> File Manager
4. Path to the file - /dev/block/mmcblk0p24 (you can simply copy it straight to /sdcard)
IN CASE YOU HAVE mmcblk0p25 AS WELL, MENTION IT!
That's it! Nothing bad is going to happen to your device. Simply copy the file!
It also would be very nice of someone to fully upload the "/blocks" folder. It could be very useful for restoring the tablet for other people!
Nvidia Shield K1 16GB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try flashing stock factory ROM from twrp. You can find stock factory images here on XDA or on nvidia website. Search for nomoreota and kill switch here on XDA to see if you need to flash a patch immediately after you flash the stock factory image to prevent nvidia kill switch hard bricking your device.
jemail said:
Try flashing stock factory ROM from twrp. You can find stock factory images here on XDA or on nvidia website. Search for nomoreota and kill switch here on XDA to see if you need to flash a patch immediately after you flash the stock factory image to prevent nvidia kill switch hard bricking your device.
Click to expand...
Click to collapse
My device doesn't have killswitch, I'm using the newer
K1 version. And I tried flashing stock images multiple times. It doesn't help. I'm pretty sure all I need is the stock mmcblk0p, mmcblk0p24 in particular, since I modified exactly that. I remember that the new values I get when I use "cat /proc/partitions" in recovery or adb shell on PC differ from original ones.
lilmonkw said:
My device doesn't have killswitch, I'm using the newer
K1 version. And I tried flashing stock images multiple times. It doesn't help. I'm pretty sure all I need is the stock mmcblk0p, mmcblk0p24 in particular, since I modified exactly that. I remember that the new values I get when I use "cat /proc/partitions" in recovery or adb shell on PC differ from original ones.
Click to expand...
Click to collapse
I only have the OG nVidia Shield Tablet. But here is my mmcblk0p24 (512KB)
https://mega.nz/file/Z0t30KAT#XC4JuGKYTT74K1b3hUl1aCr61G_xID_zdFfLbnoKfoo
Hopefully someone with the K1 can upload the necessary files.
Good Luck.
jemail said:
I only have the OG nVidia Shield Tablet. But here is my mmcblk0p24 (512KB)
https://mega.nz/file/Z0t30KAT#XC4JuGKYTT74K1b3hUl1aCr61G_xID_zdFfLbnoKfoo
Hopefully someone with the K1 can upload the necessary files.
Good Luck.
Click to expand...
Click to collapse
Thanks, I also hope for someone with K1 to come in
lilmonkw said:
Thanks, I also hope for someone with K1 to come in
Click to expand...
Click to collapse
Post a request with the information you posted here, in some of the shield tablet development threads, look for the threads that have the most recent activity. In particular threads that user steel01 has started or has posted in.
I know someone who has a K1 shield but I can't get to it due to covid lockdown. When I finally do get access to it I'll get the block files, but I can't promise when that will be.
Good luck.
Here's the file. My shield is now finally working. Thanks for helping me out, Scavenger87!
Related
I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
Repartition 2048 and 0.
Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.
Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Congrats, man. I think you're the first to truly brick his gtab.
tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.
Thanks KJ, I will try those when I get home this evening.
Disclaimer: Searching for this brings up far too many results to be useful.
Just attempted a Root of 3.2 using http://forum.xda-developers.com/showthread.php?t=1185104
I'd post this there, but don't have access rights.
Anyways, process went well, rebooted, but once the initial splash screen has cleared, this happens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried using the same tool to restore to stock, but nothing doing at the moment. Help would be appreciated.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
i had the same thing happening to mine when i first rooted to 1.4 prime. however now ive upgraded the rom to 1.6 and so far no artifacts
I had the same problem. I found it was able to fix it by downloading the latest version of the batch script root method zip file and using it to flash my tablet. You need to MAKE SURE you are using the latest version v5 beta5 because the older version had a problem flashing HC3.2 and gave me that error.
here's the link to the forum entry
http://forum.xda-developers.com/showthread.php?t=1185104
here's the link to v5 beta5
http://www.mediafire.com/?59rzqn61jl445lh
Speedstra said:
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
Click to expand...
Click to collapse
I had actually attempted to flash the 3.1 image instead of the 3.2 image. Thus the reason for edit on the original post.
The latest version of the tool should restore it.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
Click to expand...
Click to collapse
Please stop using the incorrect term for 'brick.' IT IS NOT A BRICK when your device turns on. Just stop, please.
Just had this same issue, got the same screen - blood pressure went through the roof, had to go water the plants to calm down
I was following this procedure: http://forum.xda-developers.com/showthread.php?p=14760983#post14760983
My mistake was not replacing the boot.img in the root folder with the newer 8659 .img file (linked at the top of the post, but not called out in the otherwise very detailed instructions).
HOWEVER: I did have an issue in that after flashing the wrong .img and getting the "oh sh!t" screen, I could not get adb to list a connected device, which kind of threw me. I could get it into APX mode by holding down the vol-up and power keys (and paying close attention to the "usb connected" notification sound - hold them down for about 10 seconds, hear the "disconnected" sound, then almost immediately hear the "connected" sound and let them go. The screen should stay dark instead of going to the boot logo) and I could see the driver being used, but "adb devices" returned nothing.
So I just ran root.bat again, as I had nothing to lose - and BOOM! Success!
Followed the rest of the procedure with no issues. Hope this helps someone!
Cheers
PatMan
Hi
Here are the nvflash versions for the .17 update. For those that wanna go back to stock for warrenty or have a dualboot this can come in handy.
I've tested the WW version on my on transformer and it worked (got a B70 with SBK1) created the US and TW version the sameway with the same config files so it should work! LET ME KNOW IF IT WORKS FOR YOU
But remember i'm not responsible for any bricks flashing my causes and you do this on your own riks.
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
I'm hosting them on my own server:
http://www.xdafileserver.nl/
*Added US version, and TW version
Thanks
.
Worked great on a B60 and a B70.
Thank you.
Sent from my Transformer TF101 using Tapatalk
not for TF101G - B90 ?
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Korumera said:
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Click to expand...
Click to collapse
oow.. thanks for the reply..
mine still in stock, but HC 3.2.1.. i thought ICS for TF101G already available for certain countries..
thanks a lot anyway..
@Korumera
I want to create JP version.
Can you tell me how to create ?
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
rdosti said:
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
Click to expand...
Click to collapse
Yes
NVFLASH'ing removes every partition and restores the orignal one.
Windows won't allow me to install the driver. It says the third-party INF does not contain digital signature information, and it doesn't give me an ignore and proceed anyway option. Any ideas? I'm doing this from device manager.
Edit: if anyone else has this happen, rebooting to boot options (the screen that lets you boot into safe mode and such) there is a setting to disable signed drivers. That worked for me.
This is so useful. Thanks.
Really good job! Thanks man!
nicely done! I was thinking about creating one for this version but I got tied up with work.
No problem
Hope it comes in handy!
and chadster214 work comes first at least they say so haha
Hi!
ROM: NVFLASH_ICS_9.2.1.21_WW_NOROOT
CWM Recovery ICS - Stock?
Edit: When i press power+volume down for 7 seconds (aprox) show this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Thanks a lot. Fixed a issue for me. No matter what I flashed I couldn't get the wifi to work again. Just stayed in a state of trying to turn on.
Tried and tested the WW version; no problem at all.
Korumera said:
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Click to expand...
Click to collapse
I install the new NVFLASH_ICS_9.2.1.24_WW_NOROOT
My recovery it's the same, how is the recovery stock? you have screens?
I read that is normal in stock (android with admiration sign)
Thanks in advance, sorry for my english
This process works fine. A few things to keep in mind:
1) Unzip the .7z file in a folder in a folder at the root of your hard drive: I typically open my Windows boot drive, create a new folder, name it "nvflash" and dump the archive's contents into it. This avoids getting errors as a result of the Windows folder/file path being too long.
2) Timing is important when connecting the tablet to the computer: on Windows 7, I simply press the power on+volume up buttons for 2-3 seconds (up until the "new hardware found" bubble appears in the tray area), I then let go and make sure the screen remains off (*VERY IMPORTANT*).
3) To install the Windows driver for my TF101, I go to Device Manager, right-click on the APX icon (it should show a yellow exclamation point), update the driver by pointing Windows to the /usbpcdriver folder (e.g. c:\nvflash\usbpcdriver, for example), let Windows finish the install and ONLY then start the flashing process by running download.bat in Administrator mode.
Today I got my Eken T10A, and I installed Playstore/superuser with a root tool everything is fine until I tried to install some other apps and android is giving the error ''could not install internal storage full''
And then I looked at the Storage info and saw this.
See first attached img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I Though oke weird bug lets reset the tablet, and I put it in Recovery mode and saw this...
second attached img
I'm out of options tried everything, ICS is even resetting now at every reboot to the stock settings, wizard and all....
Does anyone know how to Reflash the tablet? or some sort?
After many trial and error's I've seem to have it fixed
I just installed a CWM recovery.img wiped the /system reformat the partition, and flashed a new os .img with livesuit 1.09
That simple I could even think of it....
42dpi said:
Today I got my Eken T10A, and I installed Playstore/superuser with a root tool everything is fine until I tried to install some other apps and android is giving the error ''could not install internal storage full''
And then I looked at the Storage info and saw this.
See first attached img
So I Though oke weird bug lets reset the tablet, and I put it in Recovery mode and saw this...
second attached img
I'm out of options tried everything, ICS is even resetting now at every reboot to the stock settings, wizard and all....
Does anyone know how to Reflash the tablet? or some sort?
After many trial and error's I've seem to have it fixed
I just installed a CWM recovery.img wiped the /system reformat the partition, and flashed a new os .img with livesuit 1.09
That simple I could even think of it....
Click to expand...
Click to collapse
Where did you get CWM for Ekin T10A? Thanks in advance
homen3 said:
Where did you get CWM for Ekin T10A? Thanks in advance
Click to expand...
Click to collapse
I used this script(i can insert links PM me for the link),beware it's not perfect it's a recovery.img from a novel 7 device so buttons won't work, I used a USB keyboard 1=back 2=enter 3=up
If something fails you can always flash it back with livesuit, I just used CWM for partition format en deleting partitions.
42dpi said:
I used this script(i can insert links PM me for the link),beware it's not perfect it's a recovery.img from a novel 7 device so buttons won't work, I used a USB keyboard 1=back 2=enter 3=up
If something fails you can always flash it back with livesuit, I just used CWM for partition format en deleting partitions.
Click to expand...
Click to collapse
hi,
send you a pm for link, thanks
About Eken t10a
danisath said:
hi,
send you a pm for link, thanks
Click to expand...
Click to collapse
Hi guys,
I have eken t10a and it isn't start up. always showing android logo. does anybody knows there i can get firmware and hot to upgrade it? I try downloading from eken website but the download takes 2days.
Thanks
bushass said:
Hi guys,
I have eken t10a and it isn't start up. always showing android logo. does anybody knows there i can get firmware and hot to upgrade it? I try downloading from eken website but the download takes 2days.
Thanks
Click to expand...
Click to collapse
sorry for delay: you can use it: http://www.ekoore.com/web/it/prodotti/tablet/pike/download-3.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*TLDR version.
Good After Mornin/Evening,
Am I missing any roms from my collection?
*Long Version.
I'm writing an application in processing.org for my tablet. I have an FPS counter in it, and for whatever reason, I seem to get different results in different roms.
The version of the ROM for what I need it for really doesn't matter. I just need one that does what I need and I'll be good. Battery life seems to also be an issue with other releases too, not sure what that is about. I have experienced the later lineage 16x versions have issues with one of the cpu's not entering sleep state *or something to that account*
I am using another piece of software called *Automate by LamaLabs, free on the play store. It's a really cool app if you have not heard about it. It allows you to Automate things *Pun*
When my tablet is powered via USB, it auto unlocks, connects to a specific AP, launches my app.
When the tablet is unpowered via USB, it auto kills the app and does a soft power off.
Really I don't even need to touch the screen, its quite amazing.
With that said, Not sure if its my old tablet, I bought 5 off ebay, because they are all old, I can't tell if the batteries are just getting weak or the usage is high when in the soft off mode. I have lots of linux experience, and about the only thing I can think of is adb into it, then run top and see if anything is chewing up CPU... or if there are other methods.
Another option would be
USB adapter powered by bench top psu, and just run various roms, with a glance at the current usage.
Anyway, Thanks again,
**Infact it would be pretty cool to be able to try the last fireHD rom if there is an easy way to download the firmware and some how load it up with TWRP? I bet it's not as easy as I would think..
likwidchz said:
bet it's not as easy as I would think..
Click to expand...
Click to collapse
Thats easy, just grab one of this bin files, rename to zip and flash it with twrp.
[FIRMWARE / Update][Stock] Fire HD 10 - 7th Gen
Fire HD10 (7th Generation) OS 5.6.0.0 : https://fireos-tablet-src.s3.amazonaws.com/nachheflb20tca1zcilvlco11ae49hnab/update-kindle-40.5.9.5_user_595457320.bin Fire HD10 (7th Generation) OS 5.6.0.1...
forum.xda-developers.com
Then the OTA updater will download/install the latest one for you.
Maybe take a full TWRP backup infront of any stock rom flash, in case something gets wrong.
Sus_i said:
Thats easy, just grab one of this bin files, rename to zip and flash it with twrp.
[FIRMWARE / Update][Stock] Fire HD 10 - 7th Gen
Fire HD10 (7th Generation) OS 5.6.0.0 : https://fireos-tablet-src.s3.amazonaws.com/nachheflb20tca1zcilvlco11ae49hnab/update-kindle-40.5.9.5_user_595457320.bin Fire HD10 (7th Generation) OS 5.6.0.1...
forum.xda-developers.com
Then the OTA updater will download/install the latest one for you.
Maybe take a full TWRP backup infront of any stock rom flash, in case something gets wrong.
Click to expand...
Click to collapse
You serious on the bin file ordeal?
I rename the bin file to a zip and flash with TWRP. I have an unrooted oem OS but the ability to wipe it out with TWRP later? My gut says it's not that easy... I mean, its worth a try right? the worst that can happen is it will fail at flashing or just not boot.
Thank you,
Is there anyway I can download the latest bin without the OTA update? I think the OTA update will probably overwrite TWRP right?
Thanks again.
likwidchz said:
I rename the bin file to a zip and flash with TWRP.
Click to expand...
Click to collapse
Yes, thats the way we flash all roms...
likwidchz said:
I have an unrooted oem OS but the ability to wipe it out with TWRP later? My gut says it's not that easy... I mean, its worth a try right? the worst that can happen is it will fail at flashing or just not boot.
Click to expand...
Click to collapse
You have a tablet with an unlocked bootloader and TWRP.
Doesn't matter if your OS is rooted, because if you flash a new rom the old one gets wiped...
likwidchz said:
Is there anyway I can download the latest bin without the OTA update? I think the OTA update will probably overwrite TWRP right?
Click to expand...
Click to collapse
Yes, you can also search for updates in the stock rom settings while capturing the whole logcat via adb, then you can see the OTA URL in the logcat.
The OTA will not wipe TWRP, it will use TWRP to install the update and TWRP will protect itself / prohibits any flash to the recovery partition, so thats not a problem.
likwidchz said:
Thanks again.
Click to expand...
Click to collapse