Database Info

New Brick!

Hi all,
I have successfully flashed ROMS for my Gtab for over a month now. Tonight, though I have a problem. I decided to to NVFlash back to stock (which I have done successfully several times), so APX mode works. However, THIS time, the Gtab does what I believe is that Bootloop thing. I have read threads about it, but I don't quite understand what I do to fix it.
So I get into APX mode - then what? Again - Again, I have tried NVFlash and this time it will not boot into stock - It just loops from the Viewsonic screen to the G Tablet screen over and over again.
I appreciate being rescued from my disaster.
Thanks!
Mark

mlinder1958,
I am understanding you have nvflashed and are having boot loops.
If so, you can usually re-partition with ClockWorkMod and that normally will
fix it.
http://forum.xda-developers.com/showthread.php?t=844088
When you get CWM installed, reboot into recovery (CWM) with power/volume+. Go to the
advanced menu and partition. Take a few minutes--don't panic. The Fix Permissions.
Then Wipe Dalvic Cache. The go back to the Main Menu and Wipe Cache and then
Wipe/Reset Factory Data. The reboot and hopefully you will come up running right.
If not, the re-do the nvflash back to stock.
Hope this helps.
Rev

Hi Rev,
Thanks for replying.
Here is the problem. When I enter APX mode, I hear the PC (Windows 7) make its little beep sound and the gtab screen goes blank, but there is no dos prompt window opening in windows unless I run the gtablet .bat file. This is where I am confused. Since i am getting into apx mode, how do i move put recoery and update.zip back onto the gtablet since no indication (drive letter) of the gtablet appears?
Again, I can run NVFlash and the dos prompt appears, showing the progress and the gtablet black screen displays the nvflash info at the top.
I know I need to get CWM back on there. I just don't know how to do it from APX mode withou a drive letter appearing.
Thanks again.
Mark

mlinder1958,
I gave you the CWM link so you could download the correct CWM file.
Now we need someone to come along who can tell you how to use nvflash
to load CWM into your tablet. I have never used that procedure as I have
used my microSD card in /SDCARD2 whenever I have needed it.
I will see if I can find the procedure, but you need to be looking too. If you
can flash CWM on the tablet, then you can follow my repair process.
Rev

To fash CWM recovery with nvflash, you follow the same procedure as flashing back to stock but replace part9.img in the stock image with the .img file extracted from the cwm zip download rnamed to part9.img.

So I rename update.zip to part9.img?

mlinder1958 said:
So I rename update.zip to part9.img?
Click to expand...
Click to collapse
Unzip and extract the recovery.img - then rename THAT to part9.img (and backup the old file first, of course).

roebeet,
Oh man, what an honor!
Anyway, when I extract the zip it gives me the recovery folder and the update.zip file, which I am famliar with. Howewver, I see no recovery.img file. Or did I find/unzip the wrong file?
sorry for the long drawn out call for HELP
Mark

confirmed. I am confused. I cannot find any file called recovery.img after I unzip the CWM 08 zip file.
any help is appreciated.
Mark

The recovery.img is inside the update.zip... keep extracting ;-)

The recovery.img is inside the update.zip. It's a "file inside a zip inside a zip". I used to do this early on, but later started using rar files to make it less confusing.
No worries on the thread - you made me blush.

Roebeet and Rev,
I AM DE-BRICKED!
Thank you so much for your help.
Maybe a oughtta tone down my flashing for awhile : )
You guys ROCK!
Mark

Glad to hear! Many thanks to Rev for all the good advise!

Everyone,
Let's just all celebrate.
When I read a post from someone with a major or hard problem and sense the sadness,
it really makes me sad too.
It is so great to help someone and see that sadness become joy!! Anybody that
wouldn't like that has to be a rock head!!
Mark, now just ENJOY!!
Rev

Thank you everyone who responded to this thread. This also fixed my problem of a bricked/looping system.

when i tried to go back to power + vol + a triangle with "!" shows up. any remedy?

ramerco said:
To fash CWM recovery with nvflash, you follow the same procedure as flashing back to stock but replace part9.img in the stock image with the .img file extracted from the cwm zip download rnamed to part9.img.
Click to expand...
Click to collapse
Do you rename it part9.img or 09_SOS.img?
It seems as if there is no 'part9.img' and just the latter
Edit*Ah part9 is the one in the normal NVFlash and I am trying out nvflash_gtablet_46 to fix my issues
edit2* didn't work for me, a shame

I'm in the same boat as Citi is. Still a no go for me. I have even tried what was described in this thread to no avail:
http://forum.xda-developers.com/showthread.php?t=974422
Here is one thing that I am seeing that I also didn't see mentioned.
{
"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"
}

The "Can't Mount" error has been consistant for a while. Also something else I forgot was that when connected through USB to the PC, I can't see the device in My Computer. It is there and does allow an NVFlash though.

My gTablet is in the same boat after reflashing it after using VeganTab v7.0. I'm going to try the recovery.img rename this afternoon to get it out of the bootloop.

[Q] New Boot Logo/Splash Screen Without NvFlash?

Is there a way to change that ugly ASUS boot splash logo screen whatever you wanna call it thingy? I'm sbkv2 so no nvflash.. but I'm rooted. Is there a file somewhere in /system/ that I can replace? Or?
Thanks for any help/guidance.

Not possible then?

To the best of my knowledge, you don't need nvflash to change the boot animation. Just get a new one, rename it to bootanimation.zip and place it in /data/local. Someone correct me if i'm wrong.

Saav said:
To the best of my knowledge, you don't need nvflash to change the boot animation. Just get a new one, rename it to bootanimation.zip and place it in /data/local. Someone correct me if i'm wrong.
Click to expand...
Click to collapse
I think he's talking about the splash screen, the one that appear before the bootanimation.

baseballfanz said:
I think he's talking about the splash screen, the one that appear before the bootanimation.
Click to expand...
Click to collapse
He is correct, I mean the splash screen,

I know it's gotta be possible! I just can't find an image in /system anywhere

The splash screen is in the bootloader/EBT. You can mod it and flash it through the staging partition. Whirly eyes has a thread in the dev section. I think it's much easier with nvflash since you can test it before writing it.
sent from my transformer

Thanks, I'll look for the thread, so I can do this with Sbkv2?

It should be possible, but I've never done it.
sent from my transformer

How would I go about flashing the new blob with the boot screen without NvFlash though, I have cwm I'm just a tad unsure and don't want to be accidentally flashing over something important... Thanks for the help

You can pack up just the EBT partition as a blob and flash it through the staging partition. It will only overwrite your recovery if you include an SOS partition in the blob. The relevant threads are in the dev section.
sent from my transformer

Awesome, so I can just flash certain sections, doesn't have to be all. Thanks for the help!

Okay, as far as which source to download, does it matter? Since I can't use NvFlash to extract mine I want to be extra careful.
I'm running AOKP Build 35 with Guevor v20 kernel or TestyMehIcs kernel.

I have a blob with just the EBT and the new screen made. It just says blob (not .EBT)
If I make this into a .zip and flash it, will it overwrite EVERYTHING or just .ebt? This is very important :/ I can't nvflash a brick and really want this to be clear. Should I rename it?

First off, there are no guarantees! As you said, without nvflash, you're screwed if you make a mistake, and it will be a real brick, not one of those, "help I turned off my tablet and I think it's bricked!"-type threads.
How did you pack the blob?
blobpack your_blob EBT blob_mod.EBT
You don't need to pack it up as a zip, you can just flash it through the staging partition. Not to sound condescending, but be sure you know what you are doing because the consequences are real. I truly think that it's great that you are heading down the Android! journey.
EDIT: I think I see where the confusion is coming from- most people think of the splash screen as the bootanimation. In this case, the splash screen is the Asus/nvidia logos without the spinning balls. If you change the bootanimation.zip, you will still see the splash screen.

Gah this is incredibly scary, damn Asus making Sbkv2 -_-!!
Sofar I havn't packed with blobpack, I've just used that spash image creator gui pointed to EBT then save as blob.
What I've done to this point:
Downloaded BlobTools.
Downloaded Latest .24 US
Unzip, Unzip, Copy blob
Use Blob unpack on blob
I did NOT get a blob.header for whatever reason? Or am I misreading something?
Found blob.ebt
Used This: http://forum.xda-developers.com/showthread.php?t=1232410&highlight=splash Splash screen patcher to open it.
Patched
Save as blob
I have a blob with no extention.
Did I do anything wrong? Now what?
Thanks!
Edit: Also the filesize of the blob before the patch and after is exactly the same. 1421KB

file extensions are a false indicator- what matters is the data format inside. A properly packed blob will start with msm-radio update, some blank space, and then some hex and text that indicates partitions and their size that are included in the blob. Take some blobs apart and see what's inside of them. Get a calculator and check the file sizes of the blobs inside. Then repack them to see if you get the same thing/order.

This is a screen of the EBT blob that was saved by the app, MSM-Radio-Update, some 0s, then a whole lot of gibberish.
{
"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"
}

That looks like a packed blob. I guess whirly eye's program packs it up for flashing. Notice the EBT part in the second line, and the fact that there aren't any other partitions like SOS, LNX, or APP.
sent while running with scissors

I unpacked just the EBT blob that I unpacked with blobunpack and opened it with his patcher then edited. Should be fine then I hope, if nothing messed up.
Scrolling through the rest, it just looks like EBT, I saw whirleyes left a watermark in quotes about the patcher before the image, and a section with the display text "cold-booting linux, unsupported bootloader, error, wipe data" (The options stuff) rest was blank or gibberish.
Is this primed to flash then? You said to flash through the staging partition, how would I go about this in Cmw Rouge xm recovery, do I need to pack a .zip, or what is the command to run?
Thanks majorly for all the help!

[GUIDE] How to do a FULL low level backup of your Android Device

This Guide is simple and is straight the point, but is helpful and may come in handy for those who experience a hard-bricked phone or missing file in your phone like I did. Basically, nandroid is not a FULL backup, it only backs up your system, data, sd-secure, and boot partitions. A low level backup does every partition on your phone (even low level ones) and puts it on your sdcard. Now note that a full backup can create quite a large backup size total.
Credits to XDA user closeone for teaching me how to do this:
In a terminal emulator app perform this command in your terminal:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
(Quoted from closeone)
That command is a disk to file command with the parameter if (Input file) of mmcblk0 (the entire device) and the parameter of (output file) to the SD Card as a file called mmcblk0.img
Click to expand...
Click to collapse
the "0" basically says "the whole phone" and as such backs it up. This will back up your radios, system, data, and every other partition you didnt even know existed in your phone.
I have been around android for a long time, but I did not know this, I hope this helps someone.

A couple of things you should mention: you're not responsible for any issues which may or may not arise or user errors.
Secondly, if the if= and the of= get reversed, well it would overwrite the phone's info, at least to the point DD can't run or encounters an error and stops.
Sent from my LG-P999 using xda premium

How do you restore this back to the device?
and if this restores without an issue, this might be a solution to the infamous ICS Brick bug in Samsung Galaxy Note and Galaxy SII.

Reverse the if= and the of= "if" is input file "of" output file. Think of this as being similar to making an ISO of a CD or DVD. And depending on what utilities are available and how the device is recognized, it could be a solution. If the device is recognized by a program which can flash .img files, for example for my phone we have nvflash which can. CWM can also be scripted to write them.
Sent from my LG-P999 using xda premium

Волк said:
Reverse the if= and the of= "if" is input file "of" output file. Think of this as being similar to making an ISO of a CD or DVD. And depending on what utilities are available and how the device is recognized, it could be a solution. If the device is recognized by a program which can flash .img files, for example for my phone we have nvflash which can. CWM can also be scripted to write them.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I am not sure about the reverse... a working file system needs to be remounted as read+write before it can be overwritten. I am guessing this COULD be done in recovery mode using adb shell but still quite risky. If anything, I have a feeling it can hardbrick the device unless the boot and recovery partitions are left untouched. Comments?

Thank you, this is what I was looking for!
I want to encrypt my device, thus I won´t be able to backup with Clockworkmod afterwards.
Does this command also backup /sdcard1? That would be odd somehow, because you cannot write the backup to a partition you are just about to backup itself...
How can I issue this command with adb?
I would like to connect my device to my Linux workstation, use adb to issue the backup command and write the backup to my local harddrive. How could I do that with adb?
Best regards

papperlapapp said:
Thank you, this is what I was looking for!
I want to encrypt my device, thus I won´t be able to backup with Clockworkmod afterwards.
Does this command also backup /sdcard1? That would be odd somehow, because you cannot write the backup to a partition you are just about to backup itself...
How can I issue this command with adb?
I would like to connect my device to my Linux workstation, use adb to issue the backup command and write the backup to my local harddrive. How could I do that with adb?
Best regards
Click to expand...
Click to collapse
Wow talk about a blast from the past lol. Honestly man I left the dev scene for about a good year and some months up until.... two days ago lol, so I'm rusty as all get out. I'd have to get back on my stuff to answer it for you to be honest. Even at the time of my creating this, I didn't necessarily KNOW how to do it, closeone just taught me how and I felt like this could have possibly saved someone from a potentially disastrous encounter, I wasn't knowledgeable enough to tell you much is what I'm trying to say.

I have a generic rooted tablet and im unable to find a custom recovery and i want to send my rom to a dev who can or want to made cwm/twrp for me, so this is my question: is it a safe way to copy my actual rom? Im asking that cuz im scared to brick my tablet. Thanks

acuicultor said:
I have a generic rooted tablet and im unable to find a custom recovery and i want to send my rom to a dev who can or want to made cwm/twrp for me, so this is my question: is it a safe way to copy my actual rom? Im asking that cuz im scared to brick my tablet. Thanks
Click to expand...
Click to collapse
Is the tablet rooted? I might be able to look at it, give me a PM.
Sent from my HTC One using xda app-developers app

{
"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"
}
These are the specs. Thanks

Is this possible to do without a rooted phone? What about via adb shell or as an external device?

http://forum.xda-developers.com/showthread.php?t=1818321 showed more advance function for low level backup.

would you please explain how you reach the point where you can run the dd command?

awambawamb said:
would you please explain how you reach the point where you can run the dd command?
Click to expand...
Click to collapse
dd is a Linux command, so you should do adb shell from your Windows Command Prompt. Obviously abd should be installed beforehand.
http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/
Well, I am beginner, if this is not what you asked, sorry in advance

I need mmcblk0.img from someone please for htc m8s if anyone has ir can get a hold of cheers ?

[Q] Partition Persist formated

Hello,
This is the question and the answer on the same post. (I hope I'm posting on the right place)
As you can read from this post and next three pages since, I have problems with persist partition after being formated by accident with CWM
The problem with formating PERSIST partition is that you will kill your wifi. And will not turn on anymore, buttons will look grayed out, etc. There are many threads about, here on XDA.
And of course, you will be unable to re-flash the partition with rsd or fastboot. (Flashing back your original and full stock will not help)
I was pointed to the fix for this accident which is on this post on Atrix HD section. (credit to the guys who helped me)
And thanks to post above I was able to fix my phone´s wifi and bring back to life.
But, after decompress the IMG file of persist partition I saw the WCNSS_qcom_wlan_nv from stock XT925 ROM has only 28 KB. So small compared with Atrix file. On the post fix above you will find the same file but with 1.7 MB
I tested the fix using both. And any file will work. The one from Atrix thread or the one from your own persist partition or the ones here.
Brief instructions:
You have to copy the file WCNSS_qcom_wlan_nv to the persist partition on home root, aka /persist
(Don't worry if you see an empty folder)
{
"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"
}
Then. Apply the permissions as follows
Then. Restart. your phone will create the rest of the files and links there.
That's it .
Below you will find four files extracted of several Roms. Rename it to delete the words up to W.
However, all files has the same size and same md5. So. Code is the same for each.
Anyway, is up to you.
One interesting thing I watch with this problem is: the MAC Address did not change at all.
You can change between the files and MAC will remain.

Linuxser said:
Hello,
This is the question and the answer on the same post. (I hope I'm posting on the right place)
As you can read from this post and next three pages since, I have problems with persist partition after being formated by accident with CWM
The problem with formating PERSIST partition is that you will kill your wifi. And will not turn on anymore, buttons will look grayed out, etc. There are many threads about, here on XDA.
And of course, you will be unable to re-flash the partition with rsd or fastboot. (Flashing back your original and full stock will not help)
I was pointed to the fix for this accident which is on this post on Atrix HD section. (credit to the guys who helped me)
And thanks to post above I was able to fix my phone´s wifi and bring back to life.
But, after decompress the IMG file of persist partition I saw the WCNSS_qcom_wlan_nv from stock XT925 ROM has only 28 KB. So small compared with Atrix file. On the post fix above you will find the same file but with 1.7 MB
I tested the fix using both. And any file will work. The one from Atrix thread or the one from your own persist partition or the ones here.
Brief instructions:
You have to copy the file WCNSS_qcom_wlan_nv to the persist partition on home root, aka /persist
(Don't worry if you see an empty folder)
View attachment 2661839
Then. Apply the permissions as follows
View attachment 2661840
Then. Restart. your phone will create the rest of the files and links there.
That's it .
Below you will find four files extracted of several Roms. Rename it to delete the words up to W.
However, all files has the same size and same md5. So. Code is the same for each.
Anyway, is up to you.
One interesting thing I watch with this problem is: the MAC Address did not change at all.
You can change between the files and MAC will remain.
Click to expand...
Click to collapse
hello!
I do not understand because if everyone could fix with this method , I could not . I've tried on es explorer, root explorer, x plore and the permissions part too. but the wifi still gret and i not turn on ... Might you know what this happening? can be the own wifi problem (chip ) into the phone?

Hi.
What was you triyng for?
Did you lost the file?
Remember this file is for JB.

stock mmcvlk0p table for SHIELD K1 16GB

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!