Battery Charged in 30 Seconds? Maybe in 2016

Phones and tablets are getting more and more power hungry with each passing generation. Their … more

ZArchive Manages Your File Archives

Today smartphones are quite powerful devices that can handle multiple processes at once. In fact, some of … more

Regain Double Tap to Wake Functionality on the Nexus 6

A few months ago, Google announced its newest flagship device, the Nexus 6, alongside … more

Clean Your Recent Apps – XDA Xposed Tuesday

In this day and age, you have quite a few apps installed and running on your Android … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] New info (in OP bold txt), can you answer? - Power on/Reboot goes into APX mode

OP wha2do

16th February 2014, 08:09 PM   |  #1  
wha2do's Avatar
OP Member
Flag New Orleans
Thanks Meter: 13
 
82 posts
Join Date:Joined: Mar 2012
More
Sorry, other post is a bit hard to read, was trying to see if upgrading my TF300t (unlocked, rooted, nvflash run) to v9.4.3.30 would fix it - which unfortunately didn't.

I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post for added details is at:

Original post with more details


I'm thinking the AndroidRoot booloader I've been running from when I originally created my nvflash backups got corrupted. The update (via Install Zip in TWRP) does
not seem to have updated the bootloader. In reading even more posts, another user shows:

The Device is UnLocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.3.30-20120604" A03
Checking for android ota recovery

I see the exact same except my version is "WW_epad-9.4.3.30-20120604", which makes me think the bootloader isn't getting updated correctly & is still the original AndroidRoot
version which became corrupted? I also double checked the new EBT blob I'm flashing via a hex editor and it shows it has a US SKU! So does that mean nvflash isn't truly
flashing it? If not, how can I get it to take either with nvflash, ADB, or TWRP?


Also can see (lack of) progress below *sigh*
Last edited by wha2do; 19th February 2014 at 06:46 PM. Reason: New info, hoping simpler question/answer
18th February 2014, 04:05 AM   |  #2  
wha2do's Avatar
OP Member
Flag New Orleans
Thanks Meter: 13
 
82 posts
Join Date:Joined: Mar 2012
More
Quote:
Originally Posted by wha2do

Sorry, other post is a bit hard to read, was trying to see if upgrading to v9.4.3.30 would fix it - which unfortunately it didn't.

I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post is at:

Original post with more details

See (lack of) progress below.

Well, still need some suggestions/help. I've run:

nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 twrp2.5.0.0.img

Didn't do anything to fix the APX issue nor get my fastboot icon back. I'm wondering if I should try using
the bricksafe.img file I'd created before - not sure what exactly it contains and if it would be any different.

At this point I'm days away from seeing if I can return the tablet (under a 2 year warranty plan - thought it
was said if they can't fix, get my money back rather than a replacement) and look at something else.

I've read and read and not found anything useful yet and not much on the nvflash backup file use for restoring...

Help!
Last edited by wha2do; 18th February 2014 at 03:04 PM.
18th February 2014, 09:15 AM   |  #3  
Senior Member
Flag Munich
Thanks Meter: 407
 
511 posts
Join Date:Joined: Feb 2013
You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3

Sent from my TF300T using Tapatalk
18th February 2014, 03:01 PM   |  #4  
wha2do's Avatar
OP Member
Flag New Orleans
Thanks Meter: 13
 
82 posts
Join Date:Joined: Mar 2012
More
Quote:
Originally Posted by f69m

You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3

Sent from my TF300T using Tapatalk

Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash PartitionId 3 or adb's mount point /dev/block/mmcblk0p3? In
nvflash's partition table list, MSC (assuming this is the same "misc" partition) is listed as PartitionId 12...

When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?

Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...

I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!
Last edited by wha2do; 18th February 2014 at 03:21 PM. Reason: clarification
18th February 2014, 03:17 PM   |  #5  
Senior Member
Flag Munich
Thanks Meter: 407
 
511 posts
Join Date:Joined: Feb 2013
Quote:
Originally Posted by wha2do

Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash partition 3 or adb's mount point /dev/block/mmcblk0p3?

When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?

Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...

I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!

Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.

Sent from my TF300T using Tapatalk
18th February 2014, 03:32 PM   |  #6  
wha2do's Avatar
OP Member
Flag New Orleans
Thanks Meter: 13
 
82 posts
Join Date:Joined: Mar 2012
More
Quote:
Originally Posted by f69m

Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.

Sent from my TF300T using Tapatalk

No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:

PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096

So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:

nvflash --resume --rawdeviceread 317568 512 msc.img

Should back up what's there if need it afterwards...again being safe, lol!
18th February 2014, 03:43 PM   |  #7  
Senior Member
Flag Munich
Thanks Meter: 407
 
511 posts
Join Date:Joined: Feb 2013
Quote:
Originally Posted by wha2do

No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:

PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096

So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:

nvflash --resume --rawdeviceread 317568 512 msc.img

Should back up what's there if need it afterwards...again being safe, lol!

Yes, this looks like the right one. Unfortunately /proc/partitions does not give a start sector, but the name MSC matches. /proc/partitions gives the size at 2048, but that should be 1K blocks, so maching the 512 4K-blocks shown by nvflash.

Yeah, should be save to erase, but being careful and having a backup never hurts. Might even be interesting to have a glance at the contents.

Sent from my TF300T using Tapatalk
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes