Related
Greetings,
my sisters qtek 8500 suddenly started to freeze after the PIN code, at the startupslash screen and it doesn't go any further. therefore my intention was to reinstall it, via a new and better rom, but unfortunately the phone isn't Super CID, and so that my screen doesn't work (although active sync does recognize the phone and it is possible to explore the files) it is impossible to do it via this itsutl thing (I tried it and it always throws out the same kind of error - "ERROR: Unable to open WinCE file '\windows' - Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence". it obviously is because of me being unable to access the screen.
so that it is impossible to install a newer ROM and I cannot hard reset the device (not able to go the clear storage and moreover somehow the hard reset via pressing both soft buttons doesn't work either), I wanted to ask whether someone has somewhere around lying a link for the old qtek 8500 ROM 1.02.252.1 ? I could try to install it once again on the phone and hope that it could fix this issue. or maybe any other ideas what to do? I would really appreciate it.
As far as i know you don't have to do anything on the phone itself when you use the update utility provided with the ROM.
You could give the last official Qtek ROM a try, you can download it via the Wikipedia topic from this forum (sticky) or the qtek support site:
http://www.qtek.nl/8500_updates.asp
(sorry....in dutch...but doesn't matter for the ROM, it's the last download link on the page)
Hope it works,
Karin
I had tried out this ROM already several times, and it still gives the "INVALID VENDER ID" error at the 4%, it's a bit weird, because it is the official ROM, but still - no idea, why.
hoping that someone has the old ROM
How to flash:
1) make an application unlock
1.5) make a SuperCID (optional)
2) copy content of SSPL folder (in the archive) to the root of your device
3) run SPL.lnk
4) run ROM Update Utility.exe (from RUU directory in the archive) on your PC
5) follow the instructions
6) wait until flash process will be completed
steps from 2 to 4
of course, I do know how to do it, have done it many times on my ppc, but the thing is - I cannot make it Super CID, because of being unable to access my screen. therefore I am searching for a rom , for which I do not need a Super CID.
How about just do a hard reset?
Turn the device off. Press and hold both the left and right soft keys while powering the phone on. You will get a request to enter 0 to continue, pressing 0 will perform a hard reset.
that's another weird thing - it doesn't work. I am sure I am doing it correctly with holding the soft keys and turning it on, but still it doesn't work with these hard resets. I'm really confused, googled it up a much and found none else with such a problem.
maybe you got an idea how to make a hard reset without the clear storage or holding these soft keys or is it simply impossible?
it's actually a bit more weird - while I am performing everything for a hard reset (both soft keys and turning on) it goes into the boatloader screen
somehow got it into a hard reset, now waiting how it will react.
FINALLY it worked - everything is okey, you can lock this thread.
fyi on factory reset
the correct way to factory reset is to press and release the power button, then press the 2 dash keys, hold until instructions appear then press 0
Hello,
this will be a pretty extensive post, but I want to give you as much info as I can so you can help me
I got a second had EU HD2 with a stock bootloader, radio, rom, ect.
Bootloader: 1.42.0000
Rom: 1.66.479.2 (76641) WWE
Radio: 2.07.51.22_2
Protocol: 15.32.50.07U
I read the forum for a couple of years now and I'm pretty familiar with all the procedures for flashing (I own a couple more htcs,
flashed in every possible way)
The problem is that the battery life is very poor: after a hard reset, so no previously installed apps, not using gps, BT, WiFi, or
anything (even phone in airplane mode), I get 6-7 hrs battery life. Even in standby the battery drains at almost the same rate.
SpoonCharge says -140ma - -150ma with no app or anything in airplane mode. I tried 2 more batteries known to go over 2 days with other
hd2s.
So, I decide the problem might be in the rom and go ahead to flash to a new one:
I chose the Artemis v.65 - http://forum.xda-developers.com/showthread.php?t=612580
I read all the instructions and all other linked to them threads. Started flashing to the stock LEO-S 3.14 with the instructions here -
http://forum.xda-developers.com/showpost.php?p=8776196&postcount=26465
Flashed to SPL 1.66.0000, as said in step 2.
Tried to enter bootloader with VolDown and PowerOn, but it just starts the OS. From inside the OS I can enter bootloader with the EndKey
from johcos but ONLY that way! I tried another bootloader, 1.66HSPL, 2.08 SPL and HSPL, 3.03 SPL - nothing - I cant enter bootloader
manually - only through the EndKey with booted OS.
SO - why the hell??
I can go into bootloader through the EndKey, but I fear flashing because if something happens and the flashing doesn't go as expected I
wont be able to enter bootloader and fix things, no matter with USB sync or SD!
At one (brave) point I tried to flash the RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship from here -
http://forum.xda-developers.com/showthread.php?t=623283 - but it got to 1% and displayed an error: "Update utility not compatible with
device" or something similar.
So, bottom line after this long read:
1. Why/How can't/can I get into bootloader manually?
2. Why at the first place the batt life is so poor with all processes around 0%?
Thank you for the time spent reading my story!
and
Thanks in advance for any help!
here's some "hepl"
1- post in the corect section. The general forum is for these questions you know. it's quite odd for someone who've read the forums for years to make such mistake.
2- Since it's a second hand device, god knows what the previous owner did to it.
3- Does the volume down hardware key work when WinMo is running?
4- Do you turn on the device while holding down the volume down key, or do you press it after it starts, or release it before it starts?
5- I'm pretty sure the artemis build you're trying to get needs SPL 3.03 which you can get here: http://forum.xda-developers.com/showpost.php?p=11499585&postcount=3
6- try your device with SD removed. And make sure you haven't installed any program that runs in the background on the SD.
that's all I can help with
I'm very sorry for the wrong section. I was late and I was frustrated with many hours of struggling with the hd2. Please someone move it where it belongs.
@Dr.Move - thanks for trying to help!
I got it from a friend of mine and can assure I has handled well and it's never been to any kind of repair. It was never even flashed.
All keys work in WinMo.
I hold the VolDown key before pressing the PowerOn key. Tried also holding both keys together, holding VolDown and reseting with the reset button. Manual hard reset with VolUp and VolDown and PowerOn also doesn't work.
Artemis does need SPL3.03, but the flashing instructions say flashing SPL 1.66.0000, than stock 3.14-S which flashes to SPL 3.03.0000 and radio 2.15 .50.14, than Artemis. But that doesn't really matter right now, as it has nothing to do with me not being able to manually enter bootloader or hard reset.
Tried with SD in and out, formatted it (not quick) - all the same.
A thing I forgot to mention. My friend said the hard buttons didn't work, before I got the device. It happened a year ago, when we had no htc service in our country (Bulgaria) and the device had to be sent abroad, so he ditched it and got a new one. He couldn't remember what was wrong with the buttons, but it surely wasn't not being able to enter bootloader, as he doesn't even know what that is.
When I power up the device all the buttons worked and still work. (He was surprised and said "Well - good for you ).
So I'm starting to think the problem might be in the VolDown button, but the PowerOn obviously works. How can it be the buttons work in the OS and not before it boots up??
Ok, update.
I know what you're going to say, I did probably the dummest thing I could. I know now...
I did task 29, wiped the NAND. VolDown + PowerOn still doesnt work.
So empty nand and cant enter bootloader.
Is there anything I can try, what can be the reason the VolDown doesn't work (the button itself DID work in WinMo).
Can something be done or i got myself a shiny black brick?
damn
Sorry for that bro, I think you should move to the general forum now and ask there.
make sure you state your problem in the title clearly, much like you did here.
I'm sorry I can't help you any further as I'm not a developer/electrician. but seems I don't need to tell you that you shouldn't have done that before making sure the buttons worked.
Hi, I unfortunately don't know a lot about what I am doing here (the root of all my trouble), I'll try to get the info straight:
Motorola Droid Razr (XT910), bought in Dubai, using it in UK, so I didn't receive OTA updates. I decided to try update to ICS using RSD Lite, but the flashing got stuck at system_signed. I gave it a lot of time (hours) before I switched off the phone and tried again, which is when things started going haywire:
During my following attempts, the battery ran low, so I couldn't go on trying (soft brick). I made a patched "factory cable" as per instructions in this forum somewhere, the cable works and powers the phone for flashing.
Now all it does is coming up with the fastboot screen, which reads:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C
[...]
Device is LOCKED. Status code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
...which suggests to me it would be ok to be flashed, if only I could get it to accept the files. Being a big numpty, I am unfortunately not quite sure what was the exact version that was on there before (big mistake, I know that now), it was 2.3.6 and I suspect it must have been a MEA version, since it was bought there(? - also, when I first switched it on, all was in arabic).
What I have tried so far was:
* using several different fastboot firmware files with RSD Lite 5.7, all of which do not get over the step '1/xx flash cdt.bin "cdt.bin_signed"' - it just hangs supposedly "In process..." forever. I noticed all of these have an "ota" folder (although they vary considerably in size between <1 and 2.5 GB) - maybe all the ones I downloaded are only updates? Is there an actual, base operating system image somewhere?
After many failed attempts, I got desperate and tried files for different regions at random. The ones I tried so far:
SPDREM_U_01.6.5.1-73_SPU-11-M1-2_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.5.1-73_SPU-11-M1-2-ULB_1C.85P_0A.6B_DATDE_CFC_HWp2b_SIGNED.xml
SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_ASIA_RETAIL_HKTW.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_MEA_RETAIL.xml
The only thing I am quite sure about is that it is not LATAM.
* I tried manually flashing the various image files with moto-fastboot, fastboot, and eprj-mfastboot, both the Windows and the Linux versions, with pretty much always the same result: it would flash some files (e.g. ebr, mbr, devtree), but not what I think are the crucial ones: boot, system, also logo.bin. As there are so many possible combinations, I have not tried every file from every firmware I downloaded with every possible program, but as far as I can tell, the results were the same. I did get some error messages about signing (indicating wrong region) sometimes, but most of the time it just hangs forever while supposedly transferring the files.
* I also tried the DroidRAZRUtility, both 1.51 and 1.6, which both invariably fail at the first step of flashing the "allow-mbmloader-flashing-mbm.bin" file on there.
So, I am out of ideas now. Please, someone tell me I have overlooked something obvious. Also, please tell me I haven't bricked the thing for good.
Is there not a way to write something new into it's memory on an even more basic level (I am thinking Linux' dd here), or to read out which region it is currently locked to? I repeat, all I get is the Fastboot screen, I can get into the Fastboot menu, but none of the options gets me anywhere else, (stock) recovery does not work... My last idea is that it might still be a power issue despite the "factory cable", and to try and crack it open and power it at the battery contacts for flashing - but the fact that some flashing works, and the other files don't fail because it goes dead, but because it rejects them, suggests to me it is not a power problem.
Any suggestions appreciated, thanks!
Try flashing SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot
with rsd lite.
Those failures are because of two things:
1. You are trying wrong sbf for another region
2 and/or you are trying to flash an older firmware.
Please note that now your only bet is to flash ICS firmware, and try various regions untill you find your right one.
Also if you manually flash use eprj-mfastboot , others fail to flash corectly.
Again for the power issue, when RSD throws an error , look at the phone, if it says "Low battery, cannot program" then the factory cable is bad, if not there is no power problem.
Don't worry your phone is not dead, you only need to find the correct sbf file, try more variants with rsd lite, it must work.
Mine had problems flashing correct sbf's, it was my system. Even with correct drivers and lastest RSD it would not work, nor with my other laptop, but working fine on my old xp install on a macbook. I could however install stuff individually using fastboot flash command. Sorry that I dont have a solution but I just wanted to let you know that sometimes it can be your computer/os install.
still trying
@Killer2k8: Thanks for the encouragement, I will try with the file you suggested with eprj-mfastboot.
As per power: I seem to have tried so many times that the battery is way deeply uncharged (I hope it isn't permanently damaged once I get the phone to charge at all again), so anyway, I crack'd'er open and tried powering directly at the battery contacts (battery disconnected, of course). As you would guess from what you wrote, that did not make any difference to my problems... But also, it proves my factory cable is good, as I can even flash the few files that work if no power is connected at the battery contacts, powering through the cable only. Some files will transfer correctly, and when it says "writing", the phone will just reboot, causing an error - that's why I thought of power issue, e.g. the actual flashing process requiring more power than just the transfer... Anyway, that issue did not go away even with direct power. - Will see what happens once I find the right files for me...
I'm good with flashing ICS, that's what I wanted to do in the first place. And thanks for the encouragement!
@drolgnir: Thanks, I had the same idea, as initially I had tried everything from Win7 running in VirtualBox (at first, I only found all the tools for Win, should've really researched better before starting this), I thought maybe it doesn't have the proper low-level access to the USB ports. Anyway, since trouble hit me, I tried also on three different Linux machines (2 different dirtros), and also again on the virtual Win, and on many, many different USB ports on these (just in case it was a USB power issue), all to no avail. I guess Killer2k8's suggestion sounds most promising at the moment... Cheers anyway.
no luck - situation deteriorating..?
Sorry for the many posts, I hope someone is still reading this...
So, I tried the file you suggested. I flashed manually, not RSD, with "fastboot" from eternity project, which is the Linux equivalent to "eprj-mfastboot.exe", as far as I can tell (download from the same post as the Win version).
I could flash cdt.bin, ebr, mbr. Note that these are all just 16kB.
When trying logo.bin, it sent it ok, but during 'writing logo.bin...', the phone just switched off. After restart, same again. Same also with boot_signed.
Since then, things got worse: whenever I try to switch on now, it flashes ~1/4 of the red "M" logo, then flashes the AP fastboot screen, and repeats that a few times before staying off (sometimes not, just switches off right away). I can still get into the Boot Mode Selection menu by holding all three buttons, but selecting AP fastboot there has the same effect. Starting with power&Vol- button shows the fastboot screen immediately, but again only for a flash...
The only thing that will stay on is the SBF Flash screen, but I don't know what to do with that..?
So, I still smell a power problem, but neither applying external power, nor using the factory cable alone made a difference. The cable is ok, I re-checked. The fact that the SBF Flash screen stays on suggests that it is not a stuck power button (someone had that problem, apparently), am I right?
So, any suggestions from here? Thanks..
Although this doesn't help, I have pretty much the exact same issue. However, I do know what/where my phone is from, it requires the central Europe update. But apart from that the issues are identical; it only boots into the flash failed fastboot menu, and any RSD attempts have failed at cdt.bin, while using the fastboot tool does not work either as I get preinfovalidation flash errors. The utilities don't work either.
Now, as you did, I also tried quite a few different versions of the firmware, and none of them worked. So what I was wondering is, is there a way for us to find out exactly what version the phone 'thinks' it is on, so we can find the same/a newer version of the firmware to update it to? Because I am quite certain I am using the files from the right region, so it must be the version that is too old.
update: still struggling, but giant leap further! Please read my tale...
...just in case anyone might find this useful, I'd like to give an update on my "patient":
I actually managed to flash ICS on there! Kind of.. What I did, was:
With the battery unplugged, I supplied external power to the phone, additional to the factory cable. The issue was that it would often flash small files, but for larger files would successfully "send" them, but in the "writing" phase the phone would just switch off. So, I supplied carefully monitored 3.7V to the contacts, which seemed to make a difference, but in the "writing" phase, Voltage dropped to below 3V where it would again switch off. Ok, you can charge a LiIon battery with max. 4.2V, and you should normally charge the battery before flashing, so I tried again while providing 4.2V. And - Success!! Voltage would drop to ~4V during "writing", but it stayed on, and allowed me to further test which Firmware the device would actually accept.
I do not believe that applying 5V from an USB cable directly to the (plugged-in) battery contacts, as mentioned in the forums somewhere, is very healthy for the battery. I reconnected the battery and tried charging it directly from the contacts, but I made sure the Voltage would always stay below 4.2V. Occasionally in my exploits, the charging circuitry would actually spring into action (confirmed by a drop and fluctuations in Voltage, and the faintest of noises from the phone itself), and I used that of course to squeeze some life back in, but most of the time it would not charge at all. I can not say what combination of flashing attempts, rebooting, un- and replugging the cable, switching and changing the charging current,... actually triggered the charging process occasionally, sorry. I could not reliably reproduce it.
In the process, I also tried the DroidRazrUtility 1.8, which interestingly flashed the AP fastboot to v 0A.74, but of course failed further on...
With the new AP fastboot, I thought maybe something more might now work, and at last I found it would now miraculously accept:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml and
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
Fantastic!
First thing, before any actual booting, was to try if I could finally charge my battery again, and at last - yes!
At about 70%, I got adventurous, and unplugged the charger to put it in another power outlet. This made the phone actually boot up, but I thought that's not too bad now... But:
Now I have the following issue: After being freshly flashed (I tried several times now), it will charge as long as I don't actually switch it on, ONCE, but when it boots, after asking the setup questions and a little while on, it will switch off on its own, and then it's stuck in some variation of the bootloop (M dual core logo, pulsing M forever, OR rebooting ever and ever again at the pulsing M, OR just stuck at the M dual core). At least I now have a recovery menu. Erasing cache and data DON'T solve the issue (as proposed many times in the forums). I read a hint that it might be a kernel issue, or that it might be caused by a wrong radio.img (CDMA on a GSM phone). I checked and tested the latter by deactivating the radio in the extended settings, but it would still switch off after a short while (and it had defaulted to GSM, as it should).
So...am I stuck to wait for some new Firmware to come out, that might fix the issue? Or what should I try? Thanks in advance...
Resolved!
Long read, but I finally managed to do it. Basically, I am not 100% sure what happened, but I have a hunch:
After I thought I had solved the power issues by at least being able to charge the battery once after each re-flashing, I tried to fix the issue about the phone randomly switching off (and on - it wouldn't stay off!). I read that it might have to do with flashing failures (no error message??), or incorrect kernel or radio images...
Not long, and I ran into familiar problems again: It would flash the smaller files, but not system and cdrom; it would successfully "send" the files, but never stop "writing" them (I waited for somewhere between 10 min and an hour at each attempt), only way to stop the process was to switch off the phone, which certainly is not healthy during flashing...
...so battery started to go down again and I started to more and more clearly face a power issue again (I had disconnected the external power and didn't want to risk that McGyver approach again). As it happened, I also 'got some new USB 3.0 external hard drives at this time. I found that one would readily power up on all my USB ports, the other one could not get enough power even from some supposed 3.0 ports..
...which made me try flashing the very same firmware I was just trying (with the factory cable, of course), all the smaller files of which worked on the one computer but not the large ones (indicating I had the right firmware, at least):
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_ Service1FF_fastboot.xml
, on another computer, on the one USB 3.0 port that had proven to supply the most power - and taa-daa! It wrote it, very quickly, without complaining!
And it booted alright (after charging it first, just in case). And it stayed on (and off, when I eventually rebooted it). I am running that ever since, and it seems ok...
Originally, I had aimed for:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b _Service1FF_fastboot.xml
, but I think the differences are minimal and I don't want to risk anything going wrong again, right now.
In conclusion, to me the main issues were
- finding the right firmware, stupidly not having paid attention to the original version number, and
- all sorts of different power issues!
The factory cable did not solve all of my problems.
Recharging the battery (eventually) did not solve my problems.
ADDITIONALLY, it needs to be flashed from a USB port supplying sufficient power!
This might point into the direction drolgnir suggested, but for me, it was not an OS/driver problem, but definitely power (same, fresh install of Fedora Linux on the two machines that did, and didn't work, one of them alternatively running Win 8; the Linux Mint computer I also tried doesn't have USB 3.0, the USB 2.0 ports - including an externally powered USB hub - did not work). @drolgnir: maybe it was power for you too, but you didn't notice because it was a different OS too?
...I hope this overly detailed report might help someone else too...
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh:
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.