[Q] HTC Hero bricked when rooting - General Questions and Answers

Hi,
I'm not sure if I'm asking in the right place. Please advise me if I need to post it elsewhere.
I was trying to root my HTC Hero with firmware version 3.36.405.1 (latest, came from factory with it). I tried using Android Universal Root and z4root. I've used these methods before, but I had my phone serviced some time ago and they changed the board, so it came with a new board and the firmware above (the latest from HTC as far as I know. I had never tried to root this new board. I wanted to install a new version of android (2.2 or later) so my wife could sync her music back and forth with her new Samsung Galaxy Tab 2.0 7.
After several tries (Universal Root said the phone was rooted, but after that I couldn't do anything that needed su and root checker always tells me it isn't rooted; z4root never seemed to complete the task), one of those times (z4root) the phone was stuck in rebooting in z4root and I left the app (pressed back button) and it rebooted the phone. And now it doesn't start. I gets to a screen with an image of the phone and a red triangle and an exclamation mark. I can only leave this screen by removing the battery.
I already tried to erase the device using the volume down + power button method (several times) and I also tied to flash new firmware using the same method and placing the new firmware in the sdcard root and renaming it to one of the filenames that the phone tries to find when I use the method below. I even tried to flash it using the RUU downloaded from HTC, but the only firmware available from HTC is below my firmware version and it refuses to flash because the version doesn't match.
I tried to search several forums (xda was one of those) and used Google to try to find the correct RUU file, but couldn't find anything that would work. And I couldn't even find any original ROMs to flash using the volume down + power button method because all the ones I've found are not HTC original files and, after loading them, the phone refuses them. (At least I believe that's the reason.)
Did I really brick my phone forever? Can someone help me? If I take it to HTC, probably they can do something about it, but I can't go there because it's out of warranty now and they'd probably discover that I was trying to root the phone, charge me and do nothing.
Any advice? Can you get me the RUU program file I need?
Thanks in advance.
Jojobach

Related

2.31.651.7 fix.... No computers... No flash backs... Just root, recover and flash!!!

After receiving my second Hero I had noticed something weird about its software version... From what I remembered, it started with 2.27 on the last one I had and raised my curiosity/concern. I had heard about a root patch that was being sent out OTA by Sprint and after a little digging found the extremes that everyone was going through to achieve a successful root. The most common was to flash back .6 then to .5 which doesn't have the patch. I spent over an hour trying to find ANY copy of the 2.31.651.6 update and could not find anything. Then there where methods using the SDK which I'm sure could work, however the bootloader was a b!tch to access. I thought it would be entertaining to see If Sprint's new .7 root patched could be broken simply by the android market and third party developers; no use of Odin, unrevoked, HTC sync, no messing with debugging, not custom 2.31.651.7 (careful) and absolutely no flash backs! So here it is... enjoy.
All you will need ready is:
1).zip file of whichever OS you plan to flash. (I prefer the cm build's).
2)Rom Manager from the market (work's well with clockwork and cm).
3)Heroroot101.apk (Don't remember if it's on the market or third party).
4)NANDROID!!!!!!
All you do is run heroroot010 and push the root me button.
Reboot your phone and let it fully boot back up (give it a minute or two).
Turn it off and boot into recovery by holding down volume button and power.
I'll be damned there is a recovery image now by darchstar.
At this time there is no need to wipe just choose and flash rootme.zip
When you reboot you will see that sprint know's you're rooted already and wants to update you... This is fine.
Open Rom Manager, flash Clockwork (replacing darchstar) reboot into recovery mode and flash your new OS (DON'T FORGET TO WIPE).
I like your detailed method, but SuperOneClick was really easy too.
Install HTC Sync (v2 for Hero)
Enable USB debugging
Open SOC
Click Root
Plug in phone when prompted
Wait a bit.... then done.
There really is alot of outdated information on these forums. All versions of the stock ROMs can be rooted one way or another.
Above is two possible solutions
I agree with porkrinds but y would you replace Darchstar Recovery its the best IMO Thanks Darchstar
Root-Hack-Mod-Always™
Porkrinds said:
There really is alot of outdated information on these forums. All versions of the stock ROMs can be rooted one way or another.
Above is two possible solutions
Click to expand...
Click to collapse
Forum update, prune, re-sticky time?
I used one click method & there's no recovery image.
Great Way to Root Hero with 2.31
Used this without a hitch, has recovery & all took about 2 minutes...
http://forum.xda-developers.com/forumdisplay.php?f=643
cybertimber2007 said:
I like your detailed method, but SuperOneClick was really easy too.
Install HTC Sync (v2 for Hero)
Enable USB debugging
Open SOC
Click Root
Plug in phone when prompted
Wait a bit.... then done.
Click to expand...
Click to collapse
Hey man I just used your little posts instructions to root my Wife's hero (my evo is already rooted)
I can't believe how easy that was thanks so much everything appears to be working I have superuser authority and am going to try flashing a new rom momentarily

[Q] Cannot Root With Unrevoked

Ok so I am having a strange issue here. I tried to root my buddy's incredible using the newest version of unrevoked. It went through successfully but I noticed when going into the bootloader that it still states S-ON. Also, when I click on Recovery, it takes me to a black screen with white lines on the side. I have tried flashing the recovery multiple times by using the PB31IMG.zip method to no avail. I am guessing at this time the root did not take. So when I try to use Unrevoked again it tells me that root is unsuccessful, my software may be too new (or something to that affect. I have tried it 3 more times, no dice. Just for ****s, I downloaded terminal and it works, I can get superuser access. I tried flashing a recovery at that point with the flash_image method and that doesnt work either, it says image not found or something like that. I dont know if it rooted and didnt turn S-OFF, or if it isn't rooted at all. I tried downloading and just going back to an unrooted stock rom and it said that the software version is older and failed. I have been at it for hours. Please someone help. Thanks in advance.

Did somethign wrong, need help quick!

So I rooted my phone with the ace hack kit a while ago, put a rom on it and all was good. Well earlier I got a galaxy s2 skyrocket and was giving my old one to a family member, I hit factory restore in the setting and it did what it was supposed to then got stuck on this black screen that says android in a shining letters. I tried rest from Hboot, soft reset(battery out), and running the original software. my computer however refuses to connect to the computer, so I can't flash the original software to it. once I get to Hboot, it just sits there.
Any ideas on what to do to fix this?
Also, I need to get rid of the root and all custom stuff. So I just need a way to connect it to my computer and flash the original software onto it.
crossfire027 said:
Also, I need to get rid of the root and all custom stuff. So I just need a way to connect it to my computer and flash the original software onto it.
Click to expand...
Click to collapse
Of course when you go into hboot it will stay there. You have to use volume keys for option ex. recovery, shut down. You have to use the ace hack kit to unroot and s-on , you can not just take the official from and install it when rooted. You have to unroot phone. You can just place stock rooted rom on phone. Just place in root of sd card then boot into hboot and when it ask volume up for yes and let it do its thing then reboot when told to.
http://db.tt/Usbm7yCw
Do not rename zip
Sent from my Desire HD using xda premium
crossfire027 said:
Also, I need to get rid of the root and all custom stuff. So I just need a way to connect it to my computer and flash the original software onto it.
Click to expand...
Click to collapse
If you factory reseted the phone you erased the usb debugging...you won´t be able to connect it then. Just flash a RUU, and that will revert to stock rom. Then, run the Hack Kit to revert to S-ON.

Rooting HTC One X ATT

Hello, I understand that there are topics about rooting process and I have went and done as asked in guides however I seem to have ran into a problem.
I have managed to successfully unlock my HTC one X as what is being stated by the bootloader. I however cannot get it rooted.
I have used the new one X root 2.20 version made by Max but at the point where it is in fastboot USB and is where you do the flash recovery openxxxxxxxxxxx version name, it just keeps saying failed. I've done it over 20 times if not 30, no success.
I then tried to redo the entire process, still no luck. Then I used the guide that says 2000 on top, it guides you step by step on how to get unlock code and register and unlock phone and at the last part when you are installing the root software, can't remember the name but everyone is using it to install custom roms, it just kept saying device not found. I have looked into device manager and I had the drivers already installed and working.
I have tried to simply go into recovery but after the green sync it showed the red triangle with exclamation mark and then just rebooted itself back to lock screen.
So my question is, what could be the problem and has anyone else encountered something like this and fixed it?
If there is a post that I wasnt able to find that explains this, please do guide me to it.
Thank you all for any help.
Sent from my HTC One X using xda app-developers app
If your phone is properly seen (no errors) in Device Manager, but is offline or not present in adb/fastboot, try using another USB cable and/or port.
ValtheBatman said:
Hello, I understand that there are topics about rooting process and I have went and done as asked in guides however I seem to have ran into a problem.
I have managed to successfully unlock my HTC one X as what is being stated by the bootloader. I however cannot get it rooted.
I have used the new one X root 2.20 version made by Max but at the point where it is in fastboot USB and is where you do the flash recovery openxxxxxxxxxxx version name, it just keeps saying failed. I've done it over 20 times if not 30, no success.
I then tried to redo the entire process, still no luck. Then I used the guide that says 2000 on top, it guides you step by step on how to get unlock code and register and unlock phone and at the last part when you are installing the root software, can't remember the name but everyone is using it to install custom roms, it just kept saying device not found. I have looked into device manager and I had the drivers already installed and working.
I have tried to simply go into recovery but after the green sync it showed the red triangle with exclamation mark and then just rebooted itself back to lock screen.
So my question is, what could be the problem and has anyone else encountered something like this and fixed it?
If there is a post that I wasnt able to find that explains this, please do guide me to it.
Thank you all for any help.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
1. Make sure you have installed HTC Sync
2. Make sure HTC Sync is not running in the taskbar
If you're bootloader unlocked you don't need root, just flash a recovery from fastboot with a "fastboot flash recovery <insert TWRP recovery>
You can then flash root from recovery or flash one of the custom roms that already has root.
From memory that root method is only a temp root so you can bootloader unlock if you were on the 2.20 FW with 1.14hboot and were with AT&T since they couldn't BL unlock.
So they needed temp access to change their CID to SuperCID 1111111 so then they could unlock through htcdev.
ValtheBatman said:
at the last part when you are installing the root software, can't remember the name but everyone is using it to install custom roms, it just kept saying device not found. I have looked into device manager and I had the drivers already installed and working.
I have tried to simply go into recovery but after the green sync it showed the red triangle with exclamation mark and then just rebooted itself back to lock screen.
Click to expand...
Click to collapse
Red triangle with exclamation mark is stock recovery. TWRP is a custom recovery not "root software". If it failed to install, then obviously you cannot boot into custom recovery (TWRP).
Agree with the responses above that this is probably a drivers issue (PC is not "seeing" the phone).

root for the rct6303w87dk w/ 5.0 lollipop

hey, i just registered here to inform you all that ive figured out a way to root the new rca viking pro, but i cant seem to get supersu to install its updated binaries... i went about it like this, i searched google for kingroot app, installed it, followed the instructions it came with, and for my own benefit, i ran it twice just to make sure it worked. and wala, root! but the downside is they have their own form of su called king user. and i hate it. i hope this info helps someone, as ive came to this site on so many occaisions and everytime something on here bailed me out of a jam, i figured it was bout time i gave to a site that contributed so much to me. i love xda, and i hope someone here can get some nice things going with this tablet. thanks for your time... May
info on the RCT6303W87DK
also, FOR YOUR OWN GOOD, DO NOT CHANGE THE GENERIC.kl file on this device!!! the keyboard that comes with it, and the volume and power buttons on the device will NO LONGER function!!! just got a replacement from wallyworld because of my epic failure.... YOU HAVE BEEN WARNED!!! :good:
I tried a few different methods last night to install supersu binaries effectively breaking root a few times all resulting in using king root to "reroot". The main issue I'm having is it immediately has an update to version 1.9.1 (tablet firmware).. To get around this prompt lock the tablet, turn screen back on but unlock it with camera (bottom right). After doing this you get home rows back. Now since root I'm getting failures to install the update and every time it comes on I'm promoted for the update multiple times. Any ideas?
reemobeens19 said:
I tried a few different methods last night to install supersu binaries effectively breaking root a few times all resulting in using king root to "reroot". The main issue I'm having is it immediately has an update to version 1.9.1 (tablet firmware).. To get around this prompt lock the tablet, turn screen back on but unlock it with camera (bottom right). After doing this you get home rows back. Now since root I'm getting failures to install the update and every time it comes on I'm promoted for the update multiple times. Any ideas?
Click to expand...
Click to collapse
you have to be unrooted to apply system updates... then re root. king root should have an unroot option in app, so un rooting isnt hard. or you can hook the tab to your pc and use kingo to unroot. it will unroot, but it wont root...
I can confirm that kingroot does in fact have an option to unroot. I can also confirm that it is able to reroot after the 1.9.1 update.
Mine updated to that the first time I turned it on and I lost the update file. Can anyone tell a difference before and after the update?
I'm going to do a full stock ROM dump tonight to share. Just in case me or anyone else screws theirs up. I want to install a custom recovery and don't want to take any chances with it. Locked mtk bootloaders are ugly. Especially on these newer chipsets which cannot be unlocked as easily as the old ones.
Btw, before I finally found kingroot I must have tried about thirty different ways to root this thing. I tried several on phone root apps and a bunch of ones which required a pc connection to work and I came up short.
I got partial root with iroot 1.7 something for PC. It installed kingroot and would say that it was granting root to apps but noting actually had root.
Finally I found the latest version of vroot. V1.8 something, it had the same root database number as the earlier iroot which I had, though. Then I installed the pdanet drivers and ran the vroot and it worked! Finally! I spent hours on the stupid thing.
I did try the kingroot (iroot) apk and it couldn't root it and suggested I try the PC version.
What I'm getting at is that possibly fw 1.9.1 is just a security patch that makes it harder to root. Because when I tried the apk it couldn't handle it and I had to use the PC version with pdanet drivers to get it to work. While the apk worked for you on v1.9.0 (mine updated the first time I powered it on).
So if you install the update you might want to watch out for that.
It may be possible to stop the forced ota with fotakill. Just Google the apk and place it in your /system/app folder, then delete it rename the update in your cache folder and restart.
That has always worked for me so far on all of my other Android devices.
Cheers,
-SS
Used titanium back up to freeze the updater. Went to Dev options, enabled show processor usage or something to that nature.. Watched for any thing popping up that said update. I don't remember the exact apk but a simple search with in titanium for the word update returns the only app containing it. This did indeed solve my problem about the constant update. Also another work around to bypass the update, tell it to "download and install" then immediately his stop/cancel download. This will be my last post for now on the device as I no longer own it.
Have a blessed day!
For those wanting wired controller support, tincore works wonderfully. Im using an official xbox360 control and it controls the ui and a majority of my games. Emulators as well. This is pretty much the only way to use a wired control on this tablet as far as i know. I've tried dozens of methods to no avail. Still trying to get su up and running as well. King root does function but id prefer something im used to. Anyone know of a custom recovery that'd work on this thing???
simstimstar said:
I can confirm that kingroot does in fact have an option to unroot. I can also confirm that it is able to reroot after the 1.9.1 update.
Mine updated to that the first time I turned it on and I lost the update file. Can anyone tell a difference before and after the update?
I'm going to do a full stock ROM dump tonight to share. Just in case me or anyone else screws theirs up. I want to install a custom recovery and don't want to take any chances with it. Locked mtk bootloaders are ugly. Especially on these newer chipsets which cannot be unlocked as easily as the old ones.
Btw, before I finally found kingroot I must have tried about thirty different ways to root this thing. I tried several on phone root apps and a bunch of ones which required a pc connection to work and I came up short.
I got partial root with iroot 1.7 something for PC. It installed kingroot and would say that it was granting root to apps but noting actually had root.
Finally I found the latest version of vroot. V1.8 something, it had the same root database number as the earlier iroot which I had, though. Then I installed the pdanet drivers and ran the vroot and it worked! Finally! I spent hours on the stupid thing.
I did try the kingroot (iroot) apk and it couldn't root it and suggested I try the PC version.
What I'm getting at is that possibly fw 1.9.1 is just a security patch that makes it harder to root. Because when I tried the apk it couldn't handle it and I had to use the PC version with pdanet drivers to get it to work. While the apk worked for you on v1.9.0 (mine updated the first time I powered it on).
So if you install the update you might want to watch out for that.
It may be possible to stop the forced ota with fotakill. Just Google the apk and place it in your /system/app folder, then delete it rename the update in your cache folder and restart.
That has always worked for me so far on all of my other Android devices.
Cheers,
-SS
Click to expand...
Click to collapse
When I first got the tablet, i let it update then got the kingroot apk, installed it and it rooted. The one i used is in chinese but it had instructions and i followed them to the t. It worked. And the back up of the rom would be greatly appreciated by ALOT of us trust me. Especially me...?
Overall, this is a pretty nice tablet to own. The space alone is worth the price of admission. The specs are decent as well. Quad core, mali gpu, one gb ram, the detachable keyboard, oh i could go on. Im a heavy gamer and this is perfect for me. I have all the power i need to run everything i use. And with a 32 gb sdcard and 32gb internal, thats plenty storage for pretty much anything. I recommend this device to anyone looking for performance on a budget. 10/10
Yes, I'ts very nice. I couldn't find anything else that would even come close to it in that price range. Even used ones....
I was able to edit some config files for mrkdroidtools and got it working properly with mt8127 for the most part. At least now it will create the proper scatter file (in the correct format) for mt8127. Even though it's working properly to create the scatter, you have to use Windows enabler to allow to click the greyed out scatter file button. Before if you did that it would create a scatter in the old format without correctly identifying partition types and even not setting the correct partition sizes in the scatter. Also the chip was identified incorrectly before and now it's not.
All of the mt8127 scatters I have seen use scatter v1.1.2 (not the old format) and now I got it to output that. With proper scatter you can manually pull each partition correctly in spft.
Mtkdroidtools will now partially work for backup. It will pull firmware.info, mounts.info, and phone.info. along with NVRAM and /system only. Can't pull the others because the partitionsions are locked. Even with insecure adb (root ADB) and selinux set to permissive.. You can get old style scatter from firmware.info and mtk studio, but better to let mtkdroidtools pull the correct one.
It will try to make the CWM recovery but fails out. Magic twrp will now create the correct recovery and push it to the phone (with files from spft backup) but the recovery won't work due to the locked loader.
At least I know my backup works now because I was able to reflash the original recovery with it (this is how I screwed up my first one, which ended up going back to Wal-Mart). That first one stopped booting, but it was still recognized by spft. I just had no backup to fix it with. If they rma it, I'm sure it can be reflashed with original firmware and resold.
I will be putting this all in a toolkit and uploading. This can benefit all devices with mt8127, not just us. I also have the latest spft and I even found the checksum.exe in another package somewhere. This can be used to generate the firmware checksums for spft so you don't have to flash with checksum turned off (safer).
Haven't tried to reroot with mtkdroidtools because I think the supersu is pretty old. Don't think it will work properly in lollipop.
I wish there was a way to unlock the bootloader. I poked around in my backup of it and it clearly references files from NVRAM. Files with checksums and lists. I would think that there would be some other tablet sold under a different brand which is unlocked out there
Somewhere which is the same as ours.
Gotta run. I'll try to upload the toolkit after work if there is time. I need to clean up my backup to remove personal files from data before uploading. If it's an emergency and someone needs backup without /data I can provide now. Don't know if it will work though because kingroot resides on data. Perhaps it will work just can't authorize root.
Cheers!
-SimStim
Again, with the new one I got I couldn't root with the latest iRoot from the PC until pdanet was installed on the phone. Then it worked fine.
Without pdanet it will get temp root, then restart and when kingroot automatic root check runs it says no root and will try again and again in a loop.
With pdanet, temp root, reboot, and it's permanent root.
Just in case anyone is trying to root via this method.
Cheers!
-SimStim
simstimstar said:
Again, with the new one I got I couldn't root with the latest iRoot from the PC until pdanet was installed on the phone. Then it worked fine.
Without pdanet it will get temp root, then restart and when kingroot automatic root check runs it says no root and will try again and again in a loop.
With pdanet, temp root, reboot, and it's permanent root.
Just in case anyone is trying to root via this method.
Cheers!
-SimStim
Click to expand...
Click to collapse
You may be right... The first one i had i let kingoroot on the pc download and install some drivers. And i used pdanet awhile ago for a previous rca tab and never deleted the drivers, so maybe thats why it worked flawlessly the second time. If you have a custom recovery installed, which did you use and how'd you install it?
I tried the "magic" auto-build of CWM and TWRP, but neither one works because of the locked boot loader.
Which also makes me wonder if my backup would work on someone else's tab... The 7" RCA tab on here with the prerooted ROM works because they found another tablet which was the same and had an unlocked bootloader. At least that's what understood from it. I could be wrong though. I didn't read all 35 pages (or however many).
I'll try and double check that
Cheers,
-SimStim
simstimstar said:
I tried the "magic" auto-build of CWM and TWRP, but neither one works because of the locked boot loader.
Which also makes me wonder if my backup would work on someone else's tab... The 7" RCA tab on here with the prerooted ROM works because they found another tablet which was the same and had an unlocked bootloader. At least that's what understood from it. I could be wrong though. I didn't read all 35 pages (or however many).
I'll try and double check that
Cheers,
-SimStim
Click to expand...
Click to collapse
any progress yet? ive been searching hi and lo for custom recoveries that work to no avail. i want to try and unlock the bootloader but im afraid i may screw somthing up if i cant restore a backup. i guess its a chance im willing to take if it furthers development on this tablet. i honestly want to rip lollipop off of here and run jb 4.2.2. personally i think thats the best version of android yet. at least with funcionality. and the fact you can just plug and play on that version is a plus for me!!! hope you come across something....
may
I'm planning to return mine. I started looking around at tablets in this price range and have decided to buy a Pipo M9S instead. The price is pretty close and it absolutely spanks this device in hardware specs.
I'm somewhat biased, because I have an Android tv device based on the RK3288 and I know how fast it is. The hardware video decoder is the best I've seen yet. Plus it is so nice not to have to deal with the locked bootloader.
I wanted an RK3288 based tablet before, but was put off by the $200-300 price range which I had seen on the Pipo P9 and the P1. Then just recently I found that I could get a p7 for ~150 and an M9S for ~$175, so I've decided that I would much rather go that way(M9S).
I will hang on to my backup of this device in case it will come in handy for anyone else in the future.
Cheers,
-SimStim
simstimstar said:
Yes, I'ts very nice. I couldn't find anything else that would even come close to it in that price range. Even used ones....
I was able to edit some config files for mrkdroidtools and got it working properly with mt8127 for the most part. At least now it will create the proper scatter file (in the correct format) for mt8127. Even though it's working properly to create the scatter, you have to use Windows enabler to allow to click the greyed out scatter file button. Before if you did that it would create a scatter in the old format without correctly identifying partition types and even not setting the correct partition sizes in the scatter. Also the chip was identified incorrectly before and now it's not.
All of the mt8127 scatters I have seen use scatter v1.1.2 (not the old format) and now I got it to output that. With proper scatter you can manually pull each partition correctly in spft.
Mtkdroidtools will now partially work for backup. It will pull firmware.info, mounts.info, and phone.info. along with NVRAM and /system only. Can't pull the others because the partitionsions are locked. Even with insecure adb (root ADB) and selinux set to permissive.. You can get old style scatter from firmware.info and mtk studio, but better to let mtkdroidtools pull the correct one.
It will try to make the CWM recovery but fails out. Magic twrp will now create the correct recovery and push it to the phone (with files from spft backup) but the recovery won't work due to the locked loader.
At least I know my backup works now because I was able to reflash the original recovery with it (this is how I screwed up my first one, which ended up going back to Wal-Mart). That first one stopped booting, but it was still recognized by spft. I just had no backup to fix it with. If they rma it, I'm sure it can be reflashed with original firmware and resold.
I will be putting this all in a toolkit and uploading. This can benefit all devices with mt8127, not just us. I also have the latest spft and I even found the checksum.exe in another package somewhere. This can be used to generate the firmware checksums for spft so you don't have to flash with checksum turned off (safer).
Haven't tried to reroot with mtkdroidtools because I think the supersu is pretty old. Don't think it will work properly in lollipop.
I wish there was a way to unlock the bootloader. I poked around in my backup of it and it clearly references files from NVRAM. Files with checksums and lists. I would think that there would be some other tablet sold under a different brand which is unlocked out there
Somewhere which is the same as ours.
Gotta run. I'll try to upload the toolkit after work if there is time. I need to clean up my backup to remove personal files from data before uploading. If it's an emergency and someone needs backup without /data I can provide now. Don't know if it will work though because kingroot resides on data. Perhaps it will work just can't authorize root.
Cheers!
-SimStim
Click to expand...
Click to collapse
if you still have it, can you upload that stock image and the tools you have? or send them to me via email? ive done something terrible and i wish to go back to stock until i figure something else out. if you can do it via email, heres my [email protected]- thanks
How can I contribute
While I haven't had any issues with my DK on v1.9.1, I'm always interested in the latest and greatest Android ROM. I've got my fingers crossed for you on making restore images so you can get another ROM built on this. So, if I can contribute, even if it is paypal'ing $20 to pay toward a second tablet for you to work on, let me know.
Regards,
David
Is anyone working on unlocking the bootloader of this device? Fastboot allows me to see the "press volume up key to unlock" screen using fastboot oem unlock, however it does not respond to volume keys. Being that I got that far could it possibly succeed if it didn't have to prompt for permission?
It's going to be really tough to try and crack it. The RCA 7" tablet here on xda that got an unlocked loader because they found out that there was a Cube branded tablet which was identical, except it had an unlocked boot loader.
RCA is not the actual manufacturer (I forget who is, but cpu-z will tell you I think). Perhaps if someone were to contact the manufacturer and find out which other companies they OEM that tablet hardware to. Then check them out for unlocked bootloaders.
I would be willing to bet that they may not reveal that info so easily, so try looking around for similar hardware.
I found on a benchmarking site that the RCA 10" which doesn't have the keyboard is also the same spec and model number as a model sold by gigabyte. I don't know the status of the bootloader, though. If you flash it you risk bricking your tablet.
MTK is pretty much the opposite of rockchip, who has made their devices nearly brick proof. MTK devices with locked bootloaders are very likely to brick because of the security measures built in, odd and often encrypted filesystems with specific hashes for certain partitions, write protection on the main system partions. It's really a massive pain in the neck. Those are the reasons why I decided to get rid of mine.
It's rooted and someone who doesn't want to build custom ROMs will be perfectly happy with it. Me, I want full access! Really the tablet is pretty nice. Just not if you want custom recovery, kennel, unofficial ROMs, etc.
I'm still looking. It's probably out there somewhere. I'll be sure to post if I see anything.
Cheers,
-SS
How do you know the bootloader is locked? I see walmart has cut the price on them, I haven't seen any rca tablets with bootloader locked.

Categories

Resources