hi guys,
it looks that accidentally i've booted my device into apx mode!
...uploading screens...
br
condi
What do you mean with apx mode?
Where are the screenshots?
How did you reach this?
i didnt wanted to get into apx... accidentally when trying to get root again (after reflash stock rom).. WOW
suddenly device automattically came out from it - still blank-black screen.. some sort of timeout when idle? gr....
now we've got to find out how to enter it with purpose!
will upload mobile-camera photo of that..
Hey its a good news, because APX mode is needed for NVFlash.
As i know with NV flash we can flash our tablet
so the bootloop can be repaired, and more things can be done.
We have to find out how to enter into APX mode.
norberto_ said:
Hey its a good news, because APX mode is needed for NVFlash.
As i know with NV flash we can flash our tablet
so the bootloop can be repaired, and more things can be done.
We have to find out how to enter into APX mode.
Click to expand...
Click to collapse
yeeeeeeeah i was so excited, even wanted to put charger, and keep it in apx mode as long as we could get and make some good things... but it just turned off.
ehhh how did i done it? it was another of several tries to make root, i experimented with turning on/off mtp device in device manager, first of screenshots shows, when apx mode jumped in. i think its concerned in correct rebooting device, but there should be some combination/scenario of behavior to get into apx mode.
C:\Users\Admin\Downloads\NVFlash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
-------------------------------------
only this is what i got before it went out.
Condi,
I also got apx mode once by chance, but i didnt manage to do it again.
I entered into recovery several times while rebooting and pressing the recovery buttons, one of the times it just got into apx...
skoperst said:
Condi,
I also got apx mode once by chance, but i didnt manage to do it again.
I entered into recovery several times while rebooting and pressing the recovery buttons, one of the times it just got into apx...
Click to expand...
Click to collapse
Hi friend,
thanks for confirmation about it, now i've got hope that we'll discover how to enter apx mode
interesting... now we can find a way to use NVFLASH files to flash custom recoveries/kernels...
i had told ppl to test out stuff regarding NVFLASH:
http://forum.xda-developers.com/showthread.php?p=20889203&highlight=nvflash#post20889203
http://forum.xda-developers.com/showthread.php?p=20973791&highlight=nvflash#post20973791
http://forum.xda-developers.com/showthread.php?p=21716011&highlight=nvflash#post21716011
i am busy currently... but when i am free might need some willing users to test out a few things
Any chance the reset button might have something to do with it?
It "seems" to kill all power, yet pressing it whilst on makes it flash the red led a couple times.. so ovbiously there is some power.
Also, when it connected to your pc and was recognised as an Nvidia devices etc, how did the drivers install? Was it something handled automatically by auto update, or had you previously installed drivers yourself trying to find it another time?
Edit: Just too add, has anyone tried contacting Nvidia about it? I sent them an email about it, they just refferred me to their dev section (which ended up being a section for games developers! ) I'm pretty sure they confused APX with APEX. So I email again but no response since.. perhaps if a few of us send through they might sweat a bit and give the answer . Figured we'd possibly have more luck dealing with them than Sony (even though I realise Sony would be the all-knowing in this)
OK, I just stumbled onto this thread where defsix has found a switch inside the tablet.
I can't see the picture but could this potentially be a s-off switch or something like that, that could allow us to either flash unsigned zips or get into APX/NVflash stuff?
this could lead to an unbrick?? do you think that i may better wait for this (or for any other way to unrick) or to go and try to make it replecade by another one?
Well... I recommend waiting just a little bit more, my reasoning being:
There are only 2 potential outcomes for taking it in:
1. All sweet, they fix it or replace it
2. They send it away, discover you've messed with it, log your serial number and label your warranty as void.
If this can't fix it soon enough I'd recommend just sending it back and taking a chance - I mean what the use in still having a warranty for a perma-brick when you could chance having it fixed only risking your warranty (not like they can just keep it after they check it out).
I'll check it out tonight possibly (aus time mind you/+10 hour GMT) if the gf isn't raging at me and see what it let us do!
well then, one day or two days doesn't change anything, i can esaly wait till tuesday/wednesday, if i have to send it to them, and the warranty void...well then...it's just my fault after all...but i can wait 2days..
'mount' command from recovery shell:
Code:
$ /system/xbin/mount
/system/xbin/mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p4 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,dat
a=ordered)
/dev/block/mmcblk0p3 on /system type ext4 (rw,nodev,noatime,nodiratime,barrier=1
,data=ordered)
still no recovery here hmm...
so, if i try to update the firmware via recovery, when it says that it has had an error (the classic of base or sku), adb will be accessible?
sapphire88 said:
so, if i try to update the firmware via recovery, when it says that it has had an error (the classic of base or sku), adb will be accessible?
Click to expand...
Click to collapse
unfortunately not, but maybe something can be discovered through that way
OK so i got home early and just cracked it open (quite literally - a little tab snapped )
So all I can gather so far is that switching this switch to "off" just kills all power. The tab will boot with ac adapter connected but not without it.
All the combos I could think of failed ie
- power on + vol up
- Power on + vol down
- power on + vol up + vol down
- power on +reset
- power on + reset + vol up
- power on + reset + vol down
- power on + reset + vol up + vol down
Nothings changing besides the fact it need ac adapter to turn on
(usb has been plugged in too)
Any ideas?
DreadPirateDan said:
OK so i got home early and just cracked it open (quite literally - a little tab snapped )
So all I can gather so far is that switching this switch to "off" just kills all power. The tab will boot with ac adapter connected but not without it.
All the combos I could think of failed ie
- power on + vol up
- Power on + vol down
- power on + vol up + vol down
- power on +reset
- power on + reset + vol up
- power on + reset + vol down
- power on + reset + vol up + vol down
Nothings changing besides the fact it need ac adapter to turn on
(usb has been plugged in too)
Any ideas?
Click to expand...
Click to collapse
Looking at that original post, I'm pretty sure that's actually just a battery power kill switch. Between the fairly obvious PCB labelling and the position on the board, it would seem to be a purely hardware function. If I got a closer look at the whole PCB (don't want to open mine up just yet), we might be able to see something enlightening, but at this point, I think its just a power switch.
Yeah my thoughts are similar to that. There is nothing else visible at that level of tear down, It must be there simply for sony techs to quickly turn off the battery without dismantling everything.
And until someone gives us a solid reason to pursue the internels, I'd recommend staying away from opening your own tabs. The way the tablet is clipped/taped together, it's either gunna come off easy, or be a ***** like it did for me and snap something. (there's double sided tape as well as clips.. took some firm force to peel it away and when it finally caved, it snapped open in the blink of an eye snapping 2 tabs! booo.)
I can't imagine there's really any promising hardware to boot to apx mode, when people have already gotten there on software alone
yeah, i also think that is related to battery. i disassembled my tab few times, tried some combinations with on/off internal switch, no luck with apx. also tried to ground 'charging' socket - all one by one pins of it. without result. also tried special service microusb cable, with 3 options with resistors - which i use for example for galaxy s - to force download mode - without luck on sony..
about grounding - testpoint - a lot of sony ericsson phones had backdoor in that way, simple grounding one point of service interface.
today i thought about nfx services - they're involved in all of that recovery mistery, decrypting update.zip, and i think that also in apx thing.
apx mode appeared when i was trying to get root - again after hmmm... 5-10 failed try. so maybe nfx logged some number of reboots, reboots in random time, when copying, when some adb commands where running, and forced device to apx mode?
of course its just a theory
Related
Well, after spending almost 11 hours trying to boot into recovery or download, I know for sure that there is something going on with my phone re: hardware locked. The date on my box is 7-16. It is an early Vibrant. But no matter what I do, I cannot get into download or recovery which means my ****ing phone is literally worthless.
I have tried all possible thousands of combination's of buttons, batteries, and cords while booting and nothing happens.
The Vibrant logo shows, then it shows the pink, annoying as hell T-mobile logo, than goes to the Galaxy S logo which loads for a little bit and then just leads me to a black screen. Eventually the 4 buttons on the front of the phone turn on and then nothing else happens. It will just sit like this forever.
I know all I need to do is get a working ROM loaded but it is literally impossible to do so.
Can anyone offer any suggestions? Or are anyone else having the same problem?
I guess the only way I can get a working phone is to get in touch with T-mobile and do a Warranty exchange. That's a damn shame too, because I will be without a working phone for a week.
What about using adb?
adb reboot recovery -or- adb reboot download ?
I had a hw locked vibrant, never tried the adb reboot download, recovery did work.. I added another line on my account last night for somone, who got a vibrant, theirs wasn't hw locked, so I traded 'em ;P
Agree with the above poster I have been stuck on the vibrant screen or dark screen and adb still worked to save me
when i try to use adb, it just tells me that it cant find the device. i'm not able to boot into android OS at all.... screen just hangs. so my computer is never getting a chance to see my phone hence why i cant use adb to reboot it into recovery or download.
I believe your device has to go into recovery mode then check with and devices and if you see a device I THINK it is and reboot download, I am 90% certain
Sent from my SGH-T959 using Tapatalk
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
98classic said:
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
Click to expand...
Click to collapse
i do believe i have the correct drivers installed. i was able to use adb to run lagfixes before i was having this problem. when i boot my phone, i get a sound from my computer saying that it recognizes a usb device. the two drives in the vibrant show up in My Computer but i cannot access them as windows says they are not accessable at the moment.
at what point will adb be able to recognize my phone when booting? no matter what i do when i try adb shell i get error: device not found
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Same problem here. I probably just have to sell it fast on ebay or something. Hopefully some kind of fix starts by the end of the week. First phone in my smartphone life to brick from a simple Voodoo lag fix. Please XDA gods find a solution.
crazycaveman said:
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Click to expand...
Click to collapse
nope, no go. adb will not recognize my device no matter what. and the device isnt loading the OS so i cannot turn debugging on. i guess this is a real "brick" then.
This sounds like a rant rather than a question. Just sayin'.
DKYang said:
This sounds like a rant rather than a question. Just sayin'.
Click to expand...
Click to collapse
fixed that. my bad.
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
renocivik said:
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
Click to expand...
Click to collapse
thanks for the suggestion. i found your thread and went through the steps in the OP... still no luck. no matter what i do, i cannot get passed the black screen the loads after the galaxy s logo. i also cannot get into download mode or recovery no matter what combination of button presses i use.
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
core99 said:
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
Click to expand...
Click to collapse
this isnt working either. :-(
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
atoz350 said:
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
Click to expand...
Click to collapse
this is exactly the method i want to try. but unfortunately i cannot get the phone into recovery or download mode. i have tried at least 100 times now with many different combination's of plugging the usb cord in and pressing the volume and power buttons.
two ideas: one, is it possible that i wiped recovery and download mode from my phone on accident? the reason why i ask is that i was super tired and flashing roms and kernels to my phone. i flashed back to my original stock rom and then i flashed the kernel. for some reason, i selected wipe date/cache in Rom Manager before flashing the kernel. i have no idea why i did this. seriously. totally noob move. so im assuming i have a kernel flashed but now there is no ROM installed for the phone to boot into.
two, if above is not the issue, than im going to assume that the phone is not recognizing any button presses while its off, so when i turn it on it just recognizes that the power was pressed and ignores the volume presses, thus not booting the phone into recovery or download.
edit: i should mention again that at no time does adb recognize my device. so i cannot use adb to reboot the phone into the mode i need.
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
byt3b0mb said:
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
Click to expand...
Click to collapse
I understand what you mean. I appreciate your criticism of my original post. Let me say that I wrote it while frustrated. But I know that isn't an excuse.
The device is fantastic. I know that I did this to it myself. It's unfortunate.
Anyways, I received a replacement phone. I will be more careful this time.
Sometimes my I5500 won't turn on.
This has already happened 2 times (with two different firmwares I5500XWJPL and I5503TTLPJP9). The phone shows absolutely no signs of life - screen is black, no sounds, nothing.
I tried everything: pressing VolumeDown+Center+Power, VolumeDown+Home+Power, with or without battery/SIM/charger/SD. Tried removing battery for 30 minutes, charging battery in external charger.
Sometimes when charger is connected, it shows green battery on the screen, but still won't boot.
Last times I spent several hours fiddling with it until it finally turned on..
Can someone tell my if there is a fast way to revive the phone next time this happens?
Maybe your arm11boot is damaged, but still partly working. You need replace that partition. I saw arm11boot partition image in one Russian FW. I can't remember actual name. You can try that, but caution. You might brick your phone compleatly!
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Rigardi said:
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Click to expand...
Click to collapse
Take your battery out, put it back in and turn your phone on, then it will boot up into recovery mode. I also have this problem from time to time, sometimes it boots into recovery, sometimes not and i have to remove/replace the battery.
I actually thought that this might be a useful feature for say - if you wanted to upgrade a friends phone to cyanogenmod in the pub, for example.
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Rigardi said:
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Click to expand...
Click to collapse
In that case then this also happened to me - While exploring the rom manager application after first ever flashing my phone i accidentally selected the wrong phone model from the 'flash clockworkmod recovery' option and my phone was gone forever. Perhaps your problem is similar.
(Luckily it was under warranty and they replaced it. The method worked so well in fact it happened 'accidentally' a second time i acquired a 3rd i5500 out of the box )
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Rigardi said:
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Click to expand...
Click to collapse
what about the Emergency DLoad Mode, which is not the Download Mode? Did you try it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
how do I access emergency d/l mode?
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
ops, sorry: I miss your previous message!!
Now I got it and read this last post.. let some time to think about it, I'll replay soon.. but, generally speaking, at this point there's not so much you can do..
If you can get it into Download or Recovery mode, then you should be fine.
Sent from my GT-I5500 using XDA App
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
download mode is Vol - / Central Button / Power..
Im aware of that. However, Vol- + Menu + Power is the only key combination that the phone will react upon.
Anyway. Brought it to a mobile phone shop on friday, called them on monday and according to them, the phone should be fixed by tomorrow, wednesday. Seems like ROM manager has done damage that cant be undone without knowing how to handle a JTAG device. But at least its not completely broken. Learning that will cost me 25 Euros, though.
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Rigardi said:
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Click to expand...
Click to collapse
... for only 25 €!!!
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
All,
I inherited a seriously injured HTC surround, and I have decided to use it as a project phone.
Current status - Half Bricked on the bootloader + when it boots it immediately asks to be connected to restore backup. Unfortunately I have no zune backup and neither does the original owner of the device.
So I have read everything I could find on the half-brick issue and it seems that some folks are having success using the goldcard method to over write their boot loader with various HTC devices. I am will to try this but all the vids I have seen tutorials etc show that you have to put the device into enter usb host mode (blue writing on white screen)
Only problem is ....I have no idea how to do this on the Surround. I have tried every button combo on boot and cannot find it.
Someone here must know how to do this in return I will post my findings on whether or not the Goldcard trick works to repair a 1/2 brick surround.
Thanks
rob243 said:
All,
I inherited a seriously injured HTC surround, and I have decided to use it as a project phone.
Current status - Half Bricked on the bootloader + when it boots it immediately asks to be connected to restore backup. Unfortunately I have no zune backup and neither does the original owner of the device.
So I have read everything I could find on the half-brick issue and it seems that some folks are having success using the goldcard method to over write their boot loader with various HTC devices. I am will to try this but all the vids I have seen tutorials etc show that you have to put the device into enter usb host mode (blue writing on white screen)
Only problem is ....I have no idea how to do this on the Surround. I have tried every button combo on boot and cannot find it.
Someone here must know how to do this in return I will post my findings on whether or not the Goldcard trick works to repair a 1/2 brick surround.
Thanks
Click to expand...
Click to collapse
Hi,
Power off the device
Press and HOLD both camera and volume down buttons
Press power on button and KEEP holding both battery and volume down buttons
After boot screen will follow the usb screen
Now release battery and volume down buttons
Regards, ansar
Ok I can only get to the tricolor screen showing the 1/2 brick spl. is the the usb host mode? Because I see on some videos on youtube a white screen with blue writing that says enter usb host mode. This is what I am trying to achieve.
Or if this is the USB host mode should I just attempt to do the flash via gold card and see if I can get rid of teh 1/2 brick?
USB Host mode
To enter USB host mode turn off the phone, then press and hold VOL down + camera buttons, then press power.
But the phone will not enter USB host mode if you only see one line en the tricolor screen (this state is half bricked). For the phone to be able to enter USB host mode, the tricolor screen must have more than 1 line but the only missing part must be Serial/USB at the bottom. Check well the videos on youtube, and you will notice before entering USB host mode that the tricolor screen have more than 1 line (someone call this state small half bricked).
My phone is also half bricked (one line in the tricolor screen), the only solution I have found is to do an HTC OEM update, either by waiting for HTC to release an update (that includes a bootloader) through zune or by forcing it (for this the phone needs to be developer unlocked).
P.S. ChevronWP7 is not selling more unlocking tokens at the moment, and the $99 AppHub membership is too expensive for me.
Thanks Guys
After reading your posts I tried it out on my good surround and sure enough was dumped directly into Enter USB Host Mode screen
So now I am sitting here wondering what can I do with this thing it will not boot to anything but the screen to connect to restore backup.
Could I give anyone here anything useful about the device? Maybe disect it and post pics? Maybe someone could find these jtag posts? Or keep it for spare parts? Seems like a waste to just chuck it
Maybe you can repair it
rob243 said:
After reading your posts I tried it out on my good surround and sure enough was dumped directly into Enter USB Host Mode screen
So now I am sitting here wondering what can I do with this thing it will not boot to anything but the screen to connect to restore backup.
Could I give anyone here anything useful about the device? Maybe disect it and post pics? Maybe someone could find these jtag posts? Or keep it for spare parts? Seems like a waste to just chuck it
Click to expand...
Click to collapse
rob243, you can try to install a new firmware, depending if the firmware is a version inferior to 2250.21.40500.502. You can use a tool called Cab Sender (http://forum.xda-developers.com/showthread.php?t=1306415) to send firmware version mondrian_2250.21.40500.502.cab (search in xda-developers), for the enter the phone to recovery mode (just press and hold CAMERA, then power, ang then release the 2 buttons).
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Conrad-007 said:
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Click to expand...
Click to collapse
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
aicjofs said:
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
Click to expand...
Click to collapse
Thanks for your reply, aicjofs.
In my case it happens always, no matter if charging or not... and it's annoying.
Would rooting and installing a custom ROM solve the problem? If yes, is there a custom ROM dedicated to kids, similar with the stock one?
Conrad
Wrong Section Buddy !!!
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
and why ???
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
:thumbdown:
Ignore this guy. I have a friend with the same power on issue with her Nabi 2, and I'm interested to read the solution here.
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Conrad-007 said:
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Click to expand...
Click to collapse
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Conrad-007 said:
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Click to expand...
Click to collapse
The latest TWRP should have a section under the wipe menu where you can repair the file system which is probably easiest, although you need to be careful what you are doing in there as it is called the "wipe" tab for a reason. Should be able to go to wipe menu, select data partition checkbox, select change or repair filesystem(don't swipe to wipe, click the words check/repair etc) and select check in the next screen.
To do a filesystem check the partition can not be mounted so you do it from recovery not in Android. Since stock recovery you can't use ADB you pretty much need TWRP one way or another.
If you don't want to use the graphical interface in TWRP you can do it over USB with ADB and use e2fsck on the partitions after unmounting them, but it's going to be doing the same thing you will just see a more verbose version if you do it over adb.
Thanks a lot, aicjofs.
I will try to root and install first TWRP, as my Nabi is still untouched.
One thing I remarked: at the moment, when I go in the (stock) recovery and want to do a "Wipe data/factory reset", 2 lines are displayed before "-- Wipping data...": "E: missing bitmap stage_empty (Code -l)" and "E:missing bitmap stage_fill (Code -l)". After that, the wiping process seems to run normal, as I get the message "Data wipe complete." at the end.
Do you know what that lines are meaning? Could those lines help to debug the main problem ?
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Conrad-007 said:
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Click to expand...
Click to collapse
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Conrad-007 said:
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Click to expand...
Click to collapse
I dont have Nabi2's anymore but both my kids tablets did the same thing. I never really found a solution. I did buy a cable from Nabi store that has the orange braid covering. It seemed to make a difference, but it still happened from time to time.
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
... aicjofs, please... help
Conrad-007 said:
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
Click to expand...
Click to collapse
You can't repair the partition table from adb/TWRP. It's read only. You could through nvflash but I don't think the partition table could possibly cause the issue. I think you are meaning fix super blocks and inodes of the filesystem? Even that is a stretch if it's happening how you describe it but with a try. Did you try repair filesystem like we talked about earlier? If not backup all the data and try a wipe data. That will make sure to blow away and reformat the data partition.
It could be hardware. I know for sure the charging system causes it when plugged in but not about the first boot stuff or when it's not charging.
Thank you aicjofs for your answer,
yes, I did attempt to repair the system, data, cache and it was successfully. I did it several times. I also wiped everything a few times and installed the Nabixus ROM afterwards. Nothing helped. It's like the operating system needs to "get warm" somehow, because I have to try to power on the system many times, until I get it work... but after that, if the Nabi goes in standby, I have to start the whole thing over
How can I check for damaged blocks, etc.? If I can do it and find some, could they be marked as "bad" and isolated? Would it make sense?
So I have already unlocked and installed "[Guide/tutorial] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat" using the thread and have been very happy.
I ordered a new battery and after putting in I noticed the touch screen wasn't well...ok I didn't get the ribbon cable in correctly no biggy.
I opened back up and indeed the cable wasn't in properly. I reinserted and put back together. I pressed the power button and the transformer would power cycle. I pressed the power and + button and got to the TEAMWIN screen and that has where it has remained.
No matter what i do with the power and volume I can't get to any other screen.
I did do this:
4 - PREVENT BRICK : NVFlash
This step is optional but highly highly highly recommended, your tab will never be bricked after it !!!.
I have read other threads about the getting stuck on the splash screen but they all say to plug into computer, connect to tablet and power cycle and Start your device in APX mode [Power On + Volume Up]. But i can't get to the selection page at boot-up.
Any ideas? I thought maybe I disconnected a cable when I opened back up but i have since opened back up looking for any ribbon that came out.
I am going to try this.....https://forum.xda-developers.com/showthread.php?t=1927818
used this to get in APX mode:
https://forum.xda-developers.com/showthread.php?t=2034866
and after trying https://forum.xda-developers.com/showthread.php?t=1927818 multiple times I could get the "nvflash.exe -r --go" to work so I tried "If you device does not reboot after you see the text, force a reboot (long press the Power button)" also no go. I did learn that every time I ran a blob and the Tab rebooted I would have to rerun "wheelie --blob blob.bin" to get back into nvflash mode.
I tried a new tactic and used this thread, https://forum.xda-developers.com/showthread.php?t=2538028, and even though it was for a TF700 I used substituted my files from, 4 - PREVENT BRICK at this thread, https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237.
and happy days when I did this, At this point if it will not reboot or shut down do this
hold power button and volume down to boot into fastboot, it actually went into fastboot!! which was what I was not able to do before.
Hopefully some of my learning and searching is helping someone. oh another learned point, I don't do as well after having whiskey, beer, or wine!
Now I am back to, [Guide/tutorial] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat, and Tab DID NOT reboot and launch the HairyBean TWRP recovery (androwook). It also does not want to recognize ADB it wants to be an MPX device. I tried this:
"2 - INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code: shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual."
but it did not like both INF files. On Win 7 I did not have a problem but with WIN 10 it is being more difficult. So I have some more troubleshooting to do. Unless of course someone has found a way to get both android_winusb.inf AND android_apxusb.inf to work correctly.
I fully recovered to stock by back to backing the two threads, first this one..https://forum.xda-developers.com/showthread.php?t=1927818 then this one..https://forum.xda-developers.com/showthread.php?t=2538028
Whatever i did worked as I am back to unlocked stock.