Hey guys,
I have some problem with my Folio (surprised?).
I flashed a lot of Roms on it but the last time when i flashed the TntMod something went wrong...
The flash was smooth but on the second reboot my Tablet storage seems bricked and when I tried to flash another Rom I noticed that my recovery came back to stock (before i had CWM).
It doesn't matter to me.
But when I try to flash something (recovery, gapps, another rom, update of tntmod, partition table exc) it doesn't work: it prints a lot of errors such as "E: can't mout CACHE: recovery/log" or similiar and then "installation aborted".
So, i tried to do that with fastboot but adb (and fastboot script also) don't recognize the tablet thought windows recognize the devices like "ADB device" (I installed the adb drivers before).
Maybe it's because the Tntmod doesn't keep the settings about Debugging mode (everytime i reboot the Folio i find this set disabled, USB mass storage doesn't work and windows doesn't recognize ADB interface thought Debugging mode is on ).
The icing on the cake is that i red somewhere about bootloader mode and now my screen is totally black (neither toshiba logo ) and windows recognizes it like "APX"... I found nvflash utility and driver (oh my god Folio is recognized by dos script O_O it's incredible!) but when i launch a command nvflash says: "Nvflash started".... End, nothing else happen...
So, any suggestion about some (or every) of these problem? =\
Please start with the way to exit from the bootloader mode (APX) =\
up is quiet urgent
Reformat partitions via fasboot
Sent from my Xoom using Tapatalk
Jon2555 said:
Reformat partitions via fasboot
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Tried, but adb and fastboot script don't recognize my device, windows does it, but scripts not (tried on windows 7 and xp also).
Are you in APX mode?
Sent from my Xoom using Tapatalk
Actually yes, how can i come out from that?
Turn off tablet(long press) or pull out battery?
Sent from my Xoom using Tapatalk
Jon2555 said:
Turn off tablet(long press) or pull out battery?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
I tried it too but it didn't work o.o i think there is another way to get out from apx mode, no one knows it?
You can reboot via Nvflash but I'm not familar with it.
Sent from my Xoom using Tapatalk
I saw the Dexter 3d where he had a problem like mine.
Another user dumped the bct for him but i'm not understanding how i can use that partitiontable..
Oh...that's the problem. You lost partitions on your device. You need to reflash them with Nvflash but, I said before, I'm not familar with Nvflash, sorry.
Sent from my Xoom using Tapatalk
Jon2555 said:
Oh...that's the problem. You lost partitions on your device. You need to reflash them with Nvflash but, I said before, I'm not familar with Nvflash, sorry.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Ok mt partiontable is fine just now, but the tablet says only one GB of memory avaiable. And i can't install anything. Any idea?
Sent from my FUSIONideos using Tapatalk
RAM or internal memory?
Jon2555 said:
RAM or internal memory?
Click to expand...
Click to collapse
Internal storage, not RAM
Sent from my FUSIONideos using Tapatalk
You have to reformat one partition to fat but I don't know where to find vfat command for android
Alright so i flashed this
http://forum.xda-developers.com/showthread.php?t=1418721
on my evo 3D with hboot 1.5 s-on using adb commands:
adb reboot bootloader
then
fastboot boot recovery.img
then i flashed the rom, now the problem is that when i plug in my phone to my computer it trys to install mtp usb divice but it doesnt find any drivers for it. my adb commands no longer work it always gives me
error: device not found
fastboot commands do the same.
i have tryed to reinstall htc sync still no good. and i have tryed to install another kernal and rom, no good.
i have tryed flashimg gui to flash a kernel then flash another rom, no good.
if anyone could tell me how to use fastboot again that would be great i need to flash a kernel trough fastboot, the recovery
Just reboot it in recovery and then use adb. That's what I do if I feel like flashing a new version of an ics rom.
Problem your encountering is the lack of drivers from HTC for ICS I believe. None the less, the method I stated above will work.
Sent from my PG86100 using XDA App
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Just manually boot into bootloader then use fastboot commands to get into recovery. Didn't look which Rom you flashed but 2 if the Ics rims native USB doesn't work.
Sent from my PG8610000 using xda premium
I fought for days with my fastboot, and drove several folks a bit crazy with my incessant problems. What was eventually figured out to be my problem was that I had easytether running in the background, and it was messing with the fastboot/adb connection. Make sure you dont have anything extra running that might be trying to access your usb ports or your phone while trying to use fastboot. I learned the hard way. Also you might want to try uninstalling htcsync, and installing just the htc drivers, and turning off any antivirus you have running as well as any firewall. hope maybe this helps!
I tried [ROM][AOSP] Evervolv-ICS 2.1.0p6 [IML74K] 01/06/2011 and it was not booting on my end, I have 1.5 Unlocked and the only ones that work on my end are
1. http://forum.xda-developers.com/showthread.php?t=1411185
And
2. http://forum.xda-developers.com/showthread.php?t=1411461
I am running jelly bean and have an unlocked bootloader. Never been rooted either. I'm trying to install twrp but can't seem to get past the part where I put it into fasboot. I boot into the bootloader and go over to the USB symbol and select it. I then go to adb and try to run the command to install twrp and it can't find my prime. I can get adb to work fine when my prime is running normally. I've tried different drivers and USB ports but still can't get to work. Any suggestions?
Sent from my HTC One XL using xda app-developers app
kmankin5344 said:
I am running jelly bean and have an unlocked bootloader. Never been rooted either. I'm trying to install twrp but can't seem to get past the part where I put it into fasboot. I boot into the bootloader and go over to the USB symbol and select it. I then go to adb and try to run the command to install twrp and it can't find my prime. I can get adb to work fine when my prime is running normally. I've tried different drivers and USB ports but still can't get to work. Any suggestions?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=34359560&postcount=5497
Thanks a ton. I tried to solve this problem for hours. Took me two minutes with that.
As mentioned I stupidly wiped everything on my nexus 4 and now only have Team win recovery project left. No os. I tried to adb push, but it gave me a protocol failure and I saw a solution with fastboot, but I don't seem to have that either.
I have tried a lot of things I found on similar threads, but none worked for me. I don't have the knowledge to try anymore. Your help would be very much appreciated.
Thank you very much.
I'm not familiar with your phone. But can you flash it to stock using odin?
Sent from my SGH-T989 using xda app-developers app
murtillon said:
I'm not familiar with your phone. But can you flash it to stock using odin?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
What is Odin? Sorry I know very little about this
So basically the problem is I have no rom on my phone so I cannot flash anything. I would need to get the files onto my phone.
Somebody_007 said:
What is Odin? Sorry I know very little about this
So basically the problem is I have no rom on my phone so I cannot flash anything. I would need to get the files onto my phone.
Click to expand...
Click to collapse
How did you get TWRP on it without odin?
Odin is for Samsung, don't bother trying on your n4
Right now you need to sideload a ROM (+gapps usually)
Boot to recovery, choose sideload
Then use adb to sideload the ROM from your pc
Or you can always use fastboot to flash the ROM as well
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Odin is for Samsung, don't bother trying on your n4
Right now you need to sideload a ROM (+gapps usually)
Boot to recovery, choose sideload
Then use adb to sideload the ROM from your pc
Or you can always use fastboot to flash the ROM as well
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I just tried sideload. And I get a protocol fault somewehere between 0 and 40% of de procces. I looked around but I cannot seem to get to recognize my phone with "adb fastboot" how exactly should I do that?
after trying every setting and driver sideload somehow worked. Thanks sooooo much:
You made me a happy man!
I have a Nexus 4, and my ultimate goal is to get a custom kernel running on it. After the first attempt failed (predictably), I tried to boot a stock boot.img - one pulled from my device's boot partition, and the other downloaded from the Google stock images.
I am using 'fastboot boot' to boot the image, on Windows 7 64-bit. The command outputs that the downloading and booting process went OKAY, and the phone continues booting, but after the Google logo disappears I just get a black screen. The phone does start though, since my computer then picks up the adb interface, and I set up an SSH server to start when the phone starts. So the phone still works, just I get a black screen with backlight on.
Obviously the first step is to get a stock image booting properly. After that I can attempt to get a custom-built kernel working, but that is a whole other problem. Is there any way to figure out what is going wrong during boot? I can get any log files from the device if needed. It is running stock Android, rooted, with CWMR v6.0.2.3.
Thanks!
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Click to expand...
Click to collapse
Well ideally I want to keep the stock ROM - while the N4 is supported by Google I don't want to mess with it too much. The kernel can be 'easily' tested without flashing, which is why I don't want to flash just yet. Are you saying though that the ROM could be to blame for this? Surely though, if the kernel, initrd and configuration are identical the boot should just work straight away? It works fine booting normally - just when fastboot is used graphics don't work.
So you are saying you are running a stock ROM and kernel and when you take the exact kernel from this ROM and use fastboot to boot that kernel you have no GUI?
Something is wrong here then as this should cause no issues. Well first step is to pull a logcat and see if it will show you why there's only a black screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
My exact procedure:
Get a boot.img by cat'ing the boot partition
Start adb logcat
Use fastboot boot boot.img to boot the image
Hopefully I got that right. Unfortunately since I'm under 10 posts I can't post links, but if you put this at the end of the Pastebin URL you can access the logcat: C2Q0eR4k
I'm not sure what cating the boot partition means and logcat hast to be started after booting the kernel, but here is what I would do
Take stock ROM source and take boot.img from it
Be sure I'm using the exact same stock ROM as this kernel
Boot to fastboot
fastboot boot boot.img
Now it will start booting and in the terminal/cmd I would then run adb logcat (probably define my logcat more but whatever)
And then see what happens
But again, there is no reason that an untouched stock kernel won't boot through fastboot or give you issues as its the exact same kernel you are currently using so with this I'm confused as there must be something else missing here, either using a different ROM that the kernel booting is not meant for (different versions or whatever) or really not to sure whatelse.
Try the above again and when I get near a PC I'll peek at your logcat
Sent from my Nexus 4 using XDA Premium 4 mobile app
I have already tried using a boot.img taken directly from the Google Nexus 4 stock, but with exactly the same results. I could post a logcat of that if you want, but I strongly suspect it will be exactly the same. It wouldn't be the recovery changing something, would it? CWMR asked me if I want to prevent Android from overwriting it - I answered 'yes', naturally, but I don't suppose it broke something?
I can rule out the software on my PC being a problem, since both Linux and Windows do the same thing. It could possibly be the USB cable, but I highly doubt it.
'cat' is a utility on Linux that reads files - that's why logcat is called what it is, since it reads the logs. By cat'ing the boot partition I literally read the boot partition, then saved the result into a file - boot.img. A form of copy, if you will.
Recovery should have no effect when booting a kernel through fastboot, I highly suspect the kernel you are trying to boot is for a different stock ROM than you are running right now. Feel free to post logcats and I can look when I'm near a pc
Sent from my Nexus 4 using XDA Premium 4 mobile app
It is the identical stock ROM to the one I'm using on my phone at the moment. For that reason, and based on the fact that the symptoms are exactly the same, I can guess that the logcats will be identical.
How is the logcat looking, by the way? I wish I knew more about Android...
Still haven't gotten near a PC, most of the time I'm mobile but hopefully tonight if I don't get back too late
Is your phone running properly when booting normally then? Or if you flash rather than boot the kernel.img with fastboot?
Sent from my Nexus 4 using XDA Premium 4 mobile app
The phone works perfectly normally - using the same boot.img that I have been unsuccessfully trying to fastboot. It is really strange, almost as if the phone is rejecting the fastboot. And I don't dare flash using fastboot, in case my phone boots without graphics and forces me to flash a new ROM. Although it wouldn't be disasterous, I don't have the time at the moment to go about fixing it if something does go wrong.
Just make a backup of ROM in recovery, then fastboot flash the kernel you've been trying to boot, if there is an issue then just wipe clean and install the nandroid
This whole process will take less than 10 min and will let you know if there is an issue with your kernel.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hmm, assuming fastboot isn't lying to me, it seems to have worked. I ran 'flashboot flash boot boot.img' (to which fastboot reported OK) and then continued with the boot in the bootloader. It booted, graphics work, along with all other basic functions like wireless and touch input. To confirm, that is with the boot.img that previously did not work with 'fastboot boot', and the one that I pulled from the device itself.
Any ideas why 'fastboot boot' isn't working properly, while 'fastboot flash boot' works? I guess I can test my custom kernel by seeing if the device boots without graphics, but ideally I would like to test the whole system, not just the kernel after booting. Besides, what happens if my kernel change does in fact break the graphics - I would assume that the fastboot broke the graphics, but when it comes to flashing it would still be broken.
I'm not marking this thread as solved until some kind of answer is to be had over this problem, but I will give 'thanks' to you for giving me the courage to properly mess with my phone and come out of the other side unscathed. Having that backup there will certainly give some reassurance in case something does go wrong!
This is indeed very strange and I can't attest to why flashing the boot works while booting it doesn't as I've never experienced this issue
Its possible you may need to update fastboot on PC but I doubt this
Maybe try to boot another kernel, a recovery would do
Grab a compatible recovery.img for your phone but different than the one you currently have installed and do the same procedure you did for the kernel
fastboot boot recoveryname.img
Now see if it boots you to a different recovery temporarily
Sent from my Nexus 4 using XDA Premium 4 mobile app
I just tried with TWRP 2.6.3.0. Same issue - it seems like the recovery has booted (Windows starts trying to install device drivers) but I just get a black screen.
Then this issue is baffling, never seen it before. I would update or reflash bootloader and update or reinstall fastboot.exe, the issue seems to lie in here but I can't say what it is off hand
Sent from my Nexus 4 using XDA Premium 4 mobile app
As mentioned earlier, I doubt it is the fastboot binary, since I get exactly the same problem on both Windows and Linux (different binaries, from different places). I don't really want to start messing around with the bootloader since as far as I'm aware if something goes wrong with that the only method of recovery is JTAG on the board.
True but it is hard to brick a nexus.
the phone side of fastboot resides within the bootloader so if your issue is here flashing a new one will be the only remedy I can think of, I will say I have flashed bootloader literally hundreds of times (used to buy and sell android phones) and never once bricked one. I used fastboot most every time for this purpose as it is the safest method and even though you seemed to be having an issue with fastboot I can't imagine flashing an appropriate bootloader through fastboot will cause you a brick but it also may not fix anything
But of course this choice is yours to do (I have flashed bootloaders many of times on my n4 without fail) and I can't think of anything else that would cause the problems you're having
Sent from my Nexus 4 using XDA Premium 4 mobile app
Where should I get the bootloader image from? Just from the Google stock ROMs, or is there a thread here on XDA?
In related news, by using the 'fudge' testing method (the kernel works if Windows starts installing drivers and the backlight fluctuates), I have managed to create a working custom kernel! At last I should be able to run LXC on it. Just need to work out why the display keeps tearing...
Great news!
Either extract the hboot from stock ROM (linked at Google dev) or look in the nexus 4 threads for someone who posted it ( they usually do) just be sure to check md5sum or sha1 first
Another note i see I never posted this
http://forum.xda-developers.com/showthread.php?t=2277112
May not help you much anymore but there will be a few tips for fastboot for ya
Sent from my Nexus 4 using XDA Premium 4 mobile app