I recently bricked my tablet after having it rooted for a very long time...a Samsung-issued update apparently screwed with something crucial.
Anyway, I tried the nvflash recovery methods as mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1130574
However, it seems that I have what they called a "locked" tablet. I get the 0x4 error he mentions and absolutely nothing happens when I send the command in nvflash.
Is there any update on this recovery method with locked tabs? I tried seeking paid services where they hook up devices to a JTAG and whatnot, but I've only seen that for the original Galaxy and not the 10.1--if you have any information about that route, that would help too.
Thanks!
you can try flashing a old rom if you can thats what i did and it worked for me
samwest39 said:
you can try flashing a old rom if you can thats what i did and it worked for me
Click to expand...
Click to collapse
The thing is I can't flash to different ROMs or even get the Tablet to boot up into download mode...
go to recovery mode
I can't get into recovery mode too. All of the partitions are screwed, and the only way of reviving this device is by flash through the NVidia Recovery Console (nvflash). The thing is, my device is one of the lucky ones that are locked..Thus, it requires a special key to unlock it before I can do anything in nvflash.
I have no idea if this would work, but you could try it ...
A few months ago I was flashing a ROM on a friends phone and something went wrong, the phone wouldn't even boot up any more, the screen stayed blank all the time, no matter which combination of buttons I pressed of how long I held them down for. ODIN didn't recognise it being connected to the PC etc... nothing worked.
Then I tried hooking the phone to the PC again and tried to do something with adb. And somehow, the phone was connected on adb. Tried an adb restart-to-download command and after a minute or two, the phone booted up and I could flash through ODIN again.
I have no idea why it worked, but it did ... lucky me .
So while I doubt it will work, it might still be worth a try. And if adb connects in any way you could maybe figure what was wrong and somehow fix it?
I also heard about some phones being locked out in a similar way and a procedure in the lines of "take the battery out, hold down 3 buttons, slide the battery in WHILE STILL HOLDING the buttons" worked, maybe there's something similarly "hidden" on the tab?
I hope you find your answer!
Related
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10
Hi there, i'm only really posting this out of desperation, I'm at my absolute wit's end with this tablet and i honestly can't suss out what's wrong with it anymore
I followed http://forum.xda-developers.com/showpost.php?p=20032494&postcount=2 to try and install CWM and it worked, CWM is running and uses 6.0.12 i believe the version is without looking.
UNFORTUNATELY now i can't access anything via CWM, i can't mount, open or format any of the internal stuff like system, cache, log, emmc ect. I've tried reflashing different versions of CWM with no success via ADB, they just quite simply don't seem to be taking hold no matter how many times i reboot or reflash and also i can't boot into the OS anymore, which really sucks since it won't accept anything i try flash to it.
Now here's the real slap in the testes, The original firmware recovery seems to be now gone meaning i can't put the device into software update or firmware recovery or anything to try flashing with Livesuit, i'm sure there's something i'm missing somewhere can anybody help? Livesuit definately detects SOMETHING is going on when i hold the volume buttons and hammer the power button, my system beeps and LiveSuit pops up, but it only displays a blank error message which i'll take a screenie of, from there it refuses to do anything else.
I've also tried using USBDeview or whatever it's called to remove every trace of a driver related to anything remotely Android and gone that route but no luck again.
I've looked into and read (and re-re-re-re-read) every single post i can find about this but the threads have either gone or died out
EDIT - Another quick think i forgot to mention was that if i try to view the partitions or hardware info via ADB i get extremely limited info back which i'll post in as well when i get chance
Well, I have a d2pad SN 201301 on the back so its somewhat new
It uses rk2829 rockchip.
Anyways Ive been trying to get recovery on it for the past couple hours to use a new rom, finally got recovery working, did everything installed my rom, and let it restart.
Well, The rom isnt compatible, there was a later version a few pages into the thread that might have been, but the one I got wasnt.
So now I'm stuck, at the intro d2 logo
I only have 1 button and it is power.
Ive tried to get adb working, because it at least says its connected, but with no success anyone have any ideas?
wzzupp548 said:
Well, I have a d2pad SN 201301 on the back so its somewhat new
It uses rk2829 rockchip.
Anyways Ive been trying to get recovery on it for the past couple hours to use a new rom, finally got recovery working, did everything installed my rom, and let it restart.
Well, The rom isnt compatible, there was a later version a few pages into the thread that might have been, but the one I got wasnt.
So now I'm stuck, at the intro d2 logo
I only have 1 button and it is power.
Ive tried to get adb working, because it at least says its connected, but with no success anyone have any ideas?
Click to expand...
Click to collapse
Hey, I realize that it's been a couple years since you posted this question. I never saw any responses. So how did it all end?
Also, there was one critical piece of information you failed to share with the XDA community...you said you worked on getting into recovery with a device that only had a power button and no volume buttons. May I ask how on earth you managed to get into recovery using only a power button? Reason I ask is that I am now facing this situation. NTech Alexis RX3HD8 tablet, rockchip RK2928 processor, power button and no volume buttons! I need to get into recovery but I cannot turn on USB debugging (and the tablet is pattern locked but the pattern was entered too many times....so I am locked out).
At this point, if I cannot enter recovery mode, the tablet is a permanently soft-bricked which is, for all intents and purposes, the same as a hard-brick.
I think what happened for me was, wanted to install new rom, got into recovery to install it, then it bricked my tab, after that I was at the logo
in my case i fixed everything by getting a rkflasher, to reinstall it, and contacting support for the factory image, which is lucky they new something about it, some companies abandon support, or dont know enoguh about what they sell, lol
as for your situation
these are the things i'd try
1. If it has google play, and is connected wifi even if its locked you can try this page
https://www.google.com/android/devicemanager
and then pick ur device and factory reset it is an option (although ive never tried it)
2. search around on the internet for 1 button recovery methods, I've seen quite a few weird tablets, and some I can think of with 1 button recovery
A. a pin hole thats not the reset button or the mic, was an actual button, and that was used to get into recovery with a safety pin, and doing the normal holding it while powering on method
B.. holding the power button, and instead of letting go when u see a logo, keep holding it, till it shuts off again, then power it on
C. plug it in to pc via usb, and turn it on, while its booting, see if ur pc recognizes it at any point during the startup and try to run some commands, ive had a brand of tabs, that give u adb access during boot, but then remove it after finished booting
4. their website is in spanish, and they dont have firmware/manual links available for your tablet
You could contact support for recovery instructions or reflash instructions,, and hope they speak english or you speak Spanish
Most of the time with 1 button tablets, if theirs no info of similar ones online, unless you can contact support, you might be out of luck
PS, my edit:
also, I saw ur post on the youtube video while looking up stuff about this tablet, if that guy can get you a firmware, you have another option of trying to get to download mode too
my tablet, with rk2928 uses these instructions to get it to show up in the RKBatchTool.
https://www.d2pad.info/docs/OSFirmwareInstallInstruction_D2-721.pdf
maybe they can help you get into download mode on urs
all of this being said, I hope my first suggestion will work, IDK if wifi is disabled during pattern lock, or if u can factory reset any tablet, I just know I always see that option when I'm using it to find my devices ect.
CVAngelo said:
Hey, I realize that it's been a couple years since you posted this question. I never saw any responses. So how did it all end?
Also, there was one critical piece of information you failed to share with the XDA community...you said you worked on getting into recovery with a device that only had a power button and no volume buttons. May I ask how on earth you managed to get into recovery using only a power button? Reason I ask is that I am now facing this situation. NTech Alexis RX3HD8 tablet, rockchip RK2928 processor, power button and no volume buttons! I need to get into recovery but I cannot turn on USB debugging (and the tablet is pattern locked but the pattern was entered too many times....so I am locked out).
At this point, if I cannot enter recovery mode, the tablet is a permanently soft-bricked which is, for all intents and purposes, the same as a hard-brick.
Click to expand...
Click to collapse
Without ADB a soft-brick can become permanent state!
wzzupp548 said:
I think what happened for me was, wanted to install new rom, got into recovery to install it, then it bricked my tab, after that I was at the logo
in my case i fixed everything by getting a rkflasher, to reinstall it, and contacting support for the factory image, which is lucky they new something about it, some companies abandon support, or dont know enoguh about what they sell, lol
as for your situation
these are the things i'd try
1. If it has google play, and is connected wifi even if its locked you can try this page
https://www.google.com/android/devicemanager
and then pick ur device and factory reset it is an option (although ive never tried it)
2. search around on the internet for 1 button recovery methods, I've seen quite a few weird tablets, and some I can think of with 1 button recovery
A. a pin hole thats not the reset button or the mic, was an actual button, and that was used to get into recovery with a safety pin, and doing the normal holding it while powering on method
B.. holding the power button, and instead of letting go when u see a logo, keep holding it, till it shuts off again, then power it on
C. plug it in to pc via usb, and turn it on, while its booting, see if ur pc recognizes it at any point during the startup and try to run some commands, ive had a brand of tabs, that give u adb access during boot, but then remove it after finished booting
4. their website is in spanish, and they dont have firmware/manual links available for your tablet
You could contact support for recovery instructions or reflash instructions,, and hope they speak english or you speak Spanish
Most of the time with 1 button tablets, if theirs no info of similar ones online, unless you can contact support, you might be out of luck
PS, my edit:
also, I saw ur post on the youtube video while looking up stuff about this tablet, if that guy can get you a firmware, you have another option of trying to get to download mode too
my tablet, with rk2928 uses these instructions to get it to show up in the RKBatchTool.
https://www.d2pad.info/docs/OSFirmwareInstallInstruction_D2-721.pdf
maybe they can help you get into download mode on urs
all of this being said, I hope my first suggestion will work, IDK if wifi is disabled during pattern lock, or if u can factory reset any tablet, I just know I always see that option when I'm using it to find my devices ect.
Click to expand...
Click to collapse
Hey thanks for getting back to me. You've been extremely helpful and your response may hopefully be found in future by others who have the same problem.
Here's how it's working out for me with this device:
1. It has Google Play but unfortunately the wifi is turned off and there's no way to connect. But in any event, the little kid whose tablet it is (I'm working on the tablet at the request of her father who is my friend), she doesn't remember the Gmail account name or password.
2. I've searched the entire Internet (LOL) including Spanish and Chinese websites/videos but no luck. I can't find anything about putting this badboy into recovery. The reset button is just for show...it only turns the tablet off in case the power button is unresponsive.
3. I've been to the website of "manufacturer". It's a Portuguese company (I speak the language) but they haven't responded to any contact requests. And they appear to offer the firmware for the devices but download link is dead. So I cannot even get the firmware to flash it. The dude on YouTube has not sent me any link to firmware.
But the bigger problem and the key to the issue is that I cannot get the tablet to be recognized by the computer no matter what I've tried. I've tried all kinds of combinations of power button play but I never get that satisfying BEEP that indicates that there is a connection open. You see, I have the drivers for the tablet but there is no way to install them without the tablet giving the opening (even if it would come back as Unknown Device). So, I'm crap out of luck with this soft-brick.
Again, thanks for your help. After 3 days and probably 15 hours spent trying to reset this thing, I'm going to have to throw in the towel. Important lessons learned:
#1. NEVER PURCHASE AN ANDROID DEVICE THAT HAS NO VOLUME KEYS (or without knowing how to get into recovery). You're only asking for trouble if anything should go wrong. And believe me, this is the THIRD TIME I've seen a device that cannot go into recovery. In one case, I was able to flash new firmware directly on bootup off the external SD card (it was an Android laptop with WM8505 chip). I guess one out of three ain't bad odds...but they are not the kind of odds you want with expensive devices.
#2. ALWAYS TURN ON USB DEBUGGING WITH ANY ANDROID DEVICE YOU OWN AND TELL YOUR FRIENDS TO DO THE SAME. One day, it may end up being the savior of the life of that device because it usually means you can access the device via ADB in case of a soft-brick. LOL.
CVAngelo said:
Hey thanks for getting back to me. You've been extremely helpful and your response may hopefully be found in future by others who have the same problem.
Here's how it's working out for me with this device:
1. It has Google Play but unfortunately the wifi is turned off and there's no way to connect. But in any event, the little kid whose tablet it is (I'm working on the tablet at the request of her father who is my friend), she doesn't remember the Gmail account name or password.
2. I've searched the entire Internet (LOL) including Spanish and Chinese websites/videos but no luck. I can't find anything about putting this badboy into recovery. The reset button is just for show...it only turns the tablet off in case the power button is unresponsive.
3. I've been to the website of "manufacturer". It's a Portuguese company (I speak the language) but they haven't responded to any contact requests. And they appear to offer the firmware for the devices but download link is dead. So I cannot even get the firmware to flash it. The dude on YouTube has not sent me any link to firmware.
But the bigger problem and the key to the issue is that I cannot get the tablet to be recognized by the computer no matter what I've tried. I've tried all kinds of combinations of power button play but I never get that satisfying BEEP that indicates that there is a connection open. You see, I have the drivers for the tablet but there is no way to install them without the tablet giving the opening (even if it would come back as Unknown Device). So, I'm crap out of luck with this soft-brick.
Again, thanks for your help. After 3 days and probably 15 hours spent trying to reset this thing, I'm going to have to throw in the towel. Important lessons learned:
#1. NEVER PURCHASE AN ANDROID DEVICE THAT HAS NO VOLUME KEYS (or without knowing how to get into recovery). You're only asking for trouble if anything should go wrong. And believe me, this is the THIRD TIME I've seen a device that cannot go into recovery. In one case, I was able to flash new firmware directly on bootup off the external SD card (it was an Android laptop with WM8505 chip). I guess one out of three ain't bad odds...but they are not the kind of odds you want with expensive devices.
#2. ALWAYS TURN ON USB DEBUGGING WITH ANY ANDROID DEVICE YOU OWN AND TELL YOUR FRIENDS TO DO THE SAME. One day, it may end up being the savior of the life of that device because it usually means you can access the device via ADB in case of a soft-brick. LOL.
Click to expand...
Click to collapse
At last, did we find at last how to enter in recovery mode if there is only one button (power). I am in the same situation with @CVAngelo .Is it possible not to exist recovery mode at all? My tablet is BENEVE R708G with Rockchip RK2928. I tried every combination with power button and reset button but no luck at all.I have boot loop after trying to change the bootanimation.The weird thing is that the new boot animation ''works'' but after that it goes on boot loop forever.
So I admit I am an idiot and did this to myself. I installed the latest FireOS OTA through TWRP then thought to keep TWRP I would install it before I rebooted. I know I probably should have read threads about keeping root and the horribleness of 5.6.0.1 but I did not. So I can boot into the OS and I can boot to bootloader but I have no recovery at all. Any one know how to recover from this? Found out the unbrick method I have used before does not work. Fastboot give me an error about locked hw.
Been working on this anyone know or have a fastboot zip or image. I am getting a errors trying to flash the amazon bin with fastboot.
I know I am the only one posting here. I read through a bunch of threads that seem to be people in the same issue. I have now managed to get it stuck in demo mode. I also cannot seem to accomplish much from fastboot because I get a locked hw error. Bought a couple for parts HD6s off ebay. So hopefully I can make something work and get at least one working tablet. This has really put a damper on trying to create a device tree to try and build cm12.
Closer to being a brick. Some how I managed to have root in adb and managed to wipe all. Which I guess really meant all. Now all I get is the amazon logo. No desktop. No adb. No way to get to fastboot.
So ebay tablets came in, bout a lot that had 2. The one was listed as a demo model, so a simple ;demo in the search and resell the device and viola fully working tablet. It still had 4.1.1 on it so a simple update to 4.5.3, Kingroot, and TWRP install and back on CM11. The second was "black screen" so I assumed bricked as it did not seem to turn on when plugged in, initially. Tried running through unbrick but nothing from ./reader.sh so assumed on newer FireOS that blocked that function. After setting the first up I was rearranging my stack on now 2, what I thought where, badly bricked devices. Hit the power button and booted to lock screen with 7% battery. So I now have an extra HD6 to mess with. Best part is I got both of them for $20 total.